From 26fa0b60ff4d4be38252ecb1fcc28dcf39de303c Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Wed, 4 Jun 2025 00:33:16 +0200 Subject: [PATCH 01/10] Device product pages --- docs/devices-next/chargers/abb-terra-ac.mdx | 36 + docs/devices-next/chargers/abl-em4-sbcx.mdx | 38 + docs/devices-next/chargers/abl-emh1.mdx | 36 + docs/devices-next/chargers/abl-emh2.mdx | 36 + .../devices-next/chargers/abl-sursum-emh2.mdx | 33 + .../devices-next/chargers/abl-sursum-emh3.mdx | 33 + .../devices-next/chargers/abl-sursum-emh4.mdx | 33 + docs/devices-next/chargers/alfen-eve.mdx | 33 + .../chargers/alphatec-ladesaule-twin.mdx | 38 + .../chargers/alphatec-wallbox-mini-power.mdx | 38 + .../amperfied-wallbox-connectbusiness.mdx | 28 + .../amperfied-wallbox-connecthome.mdx | 28 + .../amperfied-wallbox-connectsolar.mdx | 28 + .../amperfied-wallbox-energy-control.mdx | 38 + docs/devices-next/chargers/ampure-live.mdx | 31 + docs/devices-next/chargers/ampure-next.mdx | 27 + docs/devices-next/chargers/ampure-unite.mdx | 31 + .../chargers/audi-audi-wallbox-pro.mdx | 29 + .../chargers/audi-wallbox-plus.mdx | 31 + .../chargers/autel-ac-compact.mdx | 41 + .../chargers/autel-ac-maxicharger.mdx | 41 + .../chargers/autoaid-business-wallbox.mdx | 33 + .../chargers/autoaid-intelligent-wallbox.mdx | 33 + docs/devices-next/chargers/avm-fritzdect.mdx | 36 + docs/devices-next/chargers/bender-cc612.mdx | 31 + docs/devices-next/chargers/bender-cc613.mdx | 31 + docs/devices-next/chargers/bender-icc1314.mdx | 31 + docs/devices-next/chargers/bender-icc1324.mdx | 31 + docs/devices-next/chargers/bmw-i-wallbox.mdx | 41 + docs/devices-next/chargers/bosch-sg-ready.mdx | 27 + docs/devices-next/chargers/bosch-x-change.mdx | 28 + .../chargers/buderus-sg-ready.mdx | 27 + .../chargers/cfos-power-brain-solar.mdx | 29 + .../chargers/cfos-power-brain.mdx | 29 + .../chargers/charge-amps-halo.mdx | 33 + docs/devices-next/chargers/compleo-ebox.mdx | 28 + .../devices-next/chargers/cubos-c11e-c22e.mdx | 31 + .../chargers/cupra-charger-connect-2.mdx | 29 + .../chargers/cupra-charger-connect.mdx | 31 + .../chargers/cupra-charger-pro-2.mdx | 29 + .../cupra-charger-pro-eichrecht-2.mdx | 29 + .../chargers/cupra-charger-pro.mdx | 29 + .../chargers/dadapower-premium-wallbox.mdx | 28 + .../chargers/daheimladen-wallbox.mdx | 25 + .../chargers/daikin-homehub-sg-ready.mdx | 27 + .../chargers/delta-ac-max-basic.mdx | 64 + .../chargers/delta-ac-max-smart.mdx | 64 + .../chargers/delta-slim-charger.mdx | 64 + .../chargers/delta-ultra-fast-charger.mdx | 64 + docs/devices-next/chargers/demo-charger.mdx | 34 + .../chargers/e3dc-easy-connect.mdx | 31 + .../chargers/easee-charge-core.mdx | 27 + .../chargers/easee-charge-lite.mdx | 27 + docs/devices-next/chargers/easee-charge.mdx | 27 + docs/devices-next/chargers/easee-home.mdx | 27 + docs/devices-next/chargers/ebee-wallbox.mdx | 31 + docs/devices-next/chargers/echarge-cph1.mdx | 31 + .../chargers/echarge-cph2-cpm2.mdx | 23 + .../chargers/ecoharmony-evse-epc-20-plus.mdx | 39 + .../chargers/edgetech-smart-evse.mdx | 33 + .../chargers/eebus-compatible.mdx | 22 + docs/devices-next/chargers/elecq-biz.mdx | 33 + docs/devices-next/chargers/elecq-home.mdx | 33 + docs/devices-next/chargers/elecq-station.mdx | 33 + docs/devices-next/chargers/eledio-go.mdx | 36 + .../chargers/elli-charger-connect-2.mdx | 29 + .../chargers/elli-charger-connect.mdx | 31 + .../chargers/elli-charger-pro-2.mdx | 29 + .../chargers/elli-charger-pro-eichrecht-2.mdx | 29 + .../chargers/elli-charger-pro.mdx | 29 + docs/devices-next/chargers/em2go-home.mdx | 24 + .../chargers/em2go-pro-power-ocpponc.mdx | 29 + .../chargers/en-ac-ev-charger.mdx | 33 + docs/devices-next/chargers/enercab-smart.mdx | 36 + .../chargers/ensto-chago-wallbox.mdx | 31 + .../chargers/entratek-power-dot-fix.mdx | 33 + .../chargers/entratek-power-dot-pro-2.mdx | 33 + docs/devices-next/chargers/eon-drive-ebox.mdx | 28 + docs/devices-next/chargers/eon-drive-vbox.mdx | 31 + .../devices-next/chargers/esl-walli-light.mdx | 31 + .../chargers/esystems-ghostone.mdx | 29 + docs/devices-next/chargers/etrel-inch-duo.mdx | 33 + docs/devices-next/chargers/etrel-inch.mdx | 27 + docs/devices-next/chargers/evbox-elvi.mdx | 34 + docs/devices-next/chargers/evbox-livo.mdx | 25 + docs/devices-next/chargers/evse-din.mdx | 33 + docs/devices-next/chargers/evse-wifi.mdx | 21 + .../chargers/free2move-eprowallbox.mdx | 35 + .../free2move-esolutions-eprowallbox.mdx | 33 + .../chargers/fronius-wattpilot.mdx | 33 + .../chargers/garo-glb-glb-ls4-ls4-compact.mdx | 31 + .../chargers/go-e-charger-gemini.mdx | 33 + .../chargers/go-e-charger-home.mdx | 28 + .../chargers/go-e-charger-homefix.mdx | 26 + .../chargers/go-e-charger-pro.mdx | 33 + .../devices-next/chargers/go-e-charger-v3.mdx | 33 + .../devices-next/chargers/hardybarth-cph1.mdx | 31 + .../chargers/hardybarth-cph2-cpm2.mdx | 23 + .../chargers/heidelberg-energy-control.mdx | 38 + .../chargers/hesotec-esat-ebox.mdx | 28 + .../chargers/home-assistant-switch.mdx | 36 + .../chargers/homecharge-homecharger.mdx | 38 + docs/devices-next/chargers/homematic-ip.mdx | 41 + docs/devices-next/chargers/homewizard.mdx | 30 + .../huawei-scharger-7ks-s0-22kt-s0.mdx | 33 + docs/devices-next/chargers/idm.mdx | 27 + docs/devices-next/chargers/index.mdx | 1962 +++++++++++++++++ docs/devices-next/chargers/innogy-ebox.mdx | 28 + docs/devices-next/chargers/inro-pantabox.mdx | 21 + .../chargers/juice-charger-me.mdx | 31 + .../chargers/junkers-sg-ready.mdx | 27 + ...-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx | 31 + .../keba-kecontact-p20-p30-cx-series.mdx | 41 + .../chargers/keba-kecontact-p40-p40-pro.mdx | 41 + .../chargers/kermi-x-center-pro.mdx | 28 + .../chargers/kontron-solar-charger.mdx | 29 + docs/devices-next/chargers/kostal-enector.mdx | 40 + docs/devices-next/chargers/kse-wbx16.mdx | 35 + .../chargers/ladefoxx-evload-mikro-20.mdx | 36 + .../chargers/lambda-eu-l-series.mdx | 34 + .../chargers/lrt-home-essential.mdx | 38 + .../chargers/mennekes-amedio-professional.mdx | 31 + .../mennekes-amtron-4business-700.mdx | 31 + .../chargers/mennekes-amtron-4you-300.mdx | 40 + .../chargers/mennekes-amtron-4you-500.mdx | 31 + .../mennekes-amtron-chargecontrol.mdx | 31 + .../chargers/mennekes-amtron-compact-20s.mdx | 40 + .../chargers/mennekes-amtron-premium.mdx | 28 + .../chargers/mennekes-amtron-professional.mdx | 31 + .../chargers/mennekes-amtron-xtra.mdx | 28 + .../mennekes-emobility-gateway-acu.mdx | 38 + .../chargers/mennekes-smart-acu.mdx | 38 + .../chargers/mennekes-smart-t-acu.mdx | 38 + .../devices-next/chargers/my-pv-ac-elwa-2.mdx | 29 + .../chargers/my-pv-ac-thor-ac-thor-9s.mdx | 30 + docs/devices-next/chargers/mystrom-switch.mdx | 30 + .../devices-next/chargers/nrgkick-connect.mdx | 26 + docs/devices-next/chargers/nrgkick-gen2.mdx | 38 + .../chargers/obo-bettermann-ion.mdx | 39 + .../ocpp-16j-compatible-smart-charging.mdx | 54 + docs/devices-next/chargers/openevse.mdx | 26 + docs/devices-next/chargers/openwb-pro.mdx | 21 + docs/devices-next/chargers/openwb-series2.mdx | 30 + .../chargers/openwb-software-2x.mdx | 44 + .../chargers/optec-mobility-one.mdx | 31 + docs/devices-next/chargers/orbis-viaris.mdx | 33 + .../chargers/pc-electric-garo.mdx | 27 + .../peblar-home-home-plus-business.mdx | 31 + .../chargers/phoenix-contact-charx.mdx | 36 + .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 26 + ...ix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 31 + ...oenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 31 + ...nix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 31 + ...hoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 31 + .../chargers/phoenix-contact-ev-ser.mdx | 33 + docs/devices-next/chargers/plugchoice.mdx | 40 + .../porsche-mobile-charger-connect.mdx | 22 + .../chargers/porsche-mobile-charger-plus.mdx | 22 + .../devices-next/chargers/porsche-wallbox.mdx | 29 + .../devices-next/chargers/pracht-alpha-xt.mdx | 66 + docs/devices-next/chargers/pracht-mono-xt.mdx | 66 + docs/devices-next/chargers/pracht-pni.mdx | 66 + docs/devices-next/chargers/pracht-xt.mdx | 66 + .../chargers/pulsares-simplebox.mdx | 33 + docs/devices-next/chargers/pulsatrix.mdx | 23 + .../chargers/qcells-qhome-edrive-a.mdx | 38 + .../chargers/schneider-evlink-pro.mdx | 28 + .../chargers/schrack-i-charge-cion.mdx | 33 + .../chargers/senec-wallbox-pro-s.mdx | 38 + .../chargers/senec-wallbox-pro.mdx | 36 + docs/devices-next/chargers/shelly.mdx | 36 + .../chargers/siemens-versicharge-gen3.mdx | 31 + .../chargers/skoda-charger-connect.mdx | 29 + .../chargers/skoda-charger-pro-eichrecht.mdx | 29 + .../chargers/skoda-charger-pro.mdx | 29 + .../chargers/skoda-iv-charger-connect.mdx | 29 + .../chargers/sma-ev-charger-echarger.mdx | 28 + .../chargers/smartfox-pro-charger.mdx | 33 + docs/devices-next/chargers/smartwb.mdx | 21 + .../chargers/solaredge-home-ev-charger.mdx | 41 + docs/devices-next/chargers/solax-x3-evc.mdx | 38 + .../chargers/sonnen-sonnencharger.mdx | 27 + .../chargers/spelsberg-wallbox-smart-pro.mdx | 31 + .../chargers/stark-in-strom-easy.mdx | 33 + .../stiebel-eltron-lwalwz-sg-ready.mdx | 27 + .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 27 + .../chargers/sungrow-ac011e-01.mdx | 41 + docs/devices-next/chargers/sungrow-ac011e.mdx | 33 + .../chargers/tasmota-single-phase.mdx | 36 + .../chargers/tecalor-thz-sg-ready.mdx | 27 + .../chargers/technisat-technivolt.mdx | 31 + docs/devices-next/chargers/tesla-twc3.mdx | 24 + docs/devices-next/chargers/tessie.mdx | 26 + .../chargers/tigo-go-ev-charger.mdx | 38 + .../chargers/tinkerforge-warp-charger-pro.mdx | 38 + .../tinkerforge-warp-charger-smart.mdx | 38 + .../tinkerforge-warp3-charger-pro.mdx | 36 + .../tinkerforge-warp3-charger-smart.mdx | 33 + .../chargers/tp-link-h-series-smart-plug.mdx | 30 + .../tp-link-tapo-p-series-smart-plug.mdx | 34 + .../chargers/ubitricity-heinz.mdx | 31 + docs/devices-next/chargers/v2c-trydan.mdx | 26 + .../chargers/vaillant-sensonet-sg-ready.mdx | 28 + .../vestel-evc04-home-smart-connect-plus.mdx | 31 + .../victron-ev-charging-station-via-gx.mdx | 29 + .../chargers/victron-ev-charging-station.mdx | 29 + .../chargers/viessmann-heatpump-sg-ready.mdx | 30 + .../chargers/viridian-ev-evse-epc-20-plus.mdx | 39 + .../chargers/volkswagen-charger-connect-2.mdx | 29 + .../chargers/volkswagen-charger-pro-2.mdx | 29 + .../volkswagen-charger-pro-eichrecht-2.mdx | 29 + .../volkswagen-id-charger-connect.mdx | 31 + .../chargers/volkswagen-id-charger-pro.mdx | 29 + docs/devices-next/chargers/volt-time-one.mdx | 24 + .../chargers/volt-time-source-2.mdx | 24 + .../chargers/volt-time-source-2s.mdx | 24 + .../chargers/volt-time-source.mdx | 24 + docs/devices-next/chargers/wallbe-eco-20s.mdx | 31 + docs/devices-next/chargers/wallbe-eco.mdx | 31 + docs/devices-next/chargers/wallbe-pro.mdx | 31 + .../chargers/wallbox-commander-2-fw-5x.mdx | 42 + .../chargers/wallbox-commander-2.mdx | 42 + .../chargers/wallbox-copper-sb-fw-5x.mdx | 42 + .../chargers/wallbox-copper-sb.mdx | 42 + .../chargers/wallbox-pulsar-max-fw-5x.mdx | 42 + .../chargers/wallbox-pulsar-max.mdx | 42 + .../chargers/wallbox-pulsar-plus-fw-5x.mdx | 42 + .../chargers/wallbox-pulsar-plus.mdx | 42 + .../chargers/walther-werke-basic-evo-pro.mdx | 38 + docs/devices-next/chargers/webasto-live.mdx | 31 + docs/devices-next/chargers/webasto-next.mdx | 27 + docs/devices-next/chargers/webasto-unite.mdx | 31 + .../chargers/weidmuller-ac-smart.mdx | 23 + docs/devices-next/chargers/zaptec-go-2.mdx | 25 + docs/devices-next/chargers/zaptec-go.mdx | 25 + docs/devices-next/chargers/zaptec-pro.mdx | 25 + .../chargers/zewotherm-eu-l-series.mdx | 34 + .../chargers/zj-beny-bcp-ev-charger.mdx | 33 + docs/devices-next/meters/a-tronix.mdx | 139 ++ .../meters/abb-a43-a44-b23-b24.mdx | 62 + .../acrel-adw300-wireless-metering-meter.mdx | 102 + docs/devices-next/meters/ads-tec-storaxe.mdx | 38 + .../meters/alpha-ess-storion-smile.mdx | 182 ++ .../meters/ampere-amperestoragepro.mdx | 179 ++ .../meters/anker-micro-inverter.mdx | 40 + docs/devices-next/meters/apsystems-ez1.mdx | 22 + docs/devices-next/meters/avm-fritzdect.mdx | 44 + .../meters/axitec-axihycon-12-15h.mdx | 120 + .../meters/bernecker-engineering-mpm3pm.mdx | 62 + docs/devices-next/meters/bgetech-ds100.mdx | 130 ++ docs/devices-next/meters/bgetech-ws100.mdx | 130 ++ .../meters/bosch-bpt-s-5-hybrid.mdx | 54 + .../meters/bosswerk-micro-inverter.mdx | 40 + .../meters/carlo-gavazzi-em110111112.mdx | 62 + .../meters/carlo-gavazzi-em24.mdx | 65 + .../meters/carlo-gavazzi-em24e1.mdx | 52 + .../meters/carlo-gavazzi-em330em340.mdx | 74 + .../meters/carlo-gavazzi-em530em540.mdx | 74 + .../meters/carlo-gavazzi-et112.mdx | 62 + .../meters/carlo-gavazzi-et330et340.mdx | 74 + .../meters/cfos-powerbrain-meter.mdx | 29 + docs/devices-next/meters/demo-battery.mdx | 38 + docs/devices-next/meters/demo-meter.mdx | 97 + .../meters/deye-3p-hybrid-inverter.mdx | 179 ++ .../meters/deye-hp3-hybrid-inverter.mdx | 185 ++ .../meters/deye-micro-inverter.mdx | 40 + .../meters/deye-storage-hybrid-inverter.mdx | 126 ++ .../meters/deye-string-inverter.mdx | 40 + docs/devices-next/meters/discovergy.mdx | 42 + docs/devices-next/meters/dsmr.mdx | 30 + docs/devices-next/meters/dzg-dvh4013.mdx | 34 + docs/devices-next/meters/e3dc.mdx | 97 + .../meters/eastron-sdm120-modbus.mdx | 84 + .../devices-next/meters/eastron-sdm220230.mdx | 62 + .../meters/eastron-sdm630-modbus.mdx | 62 + docs/devices-next/meters/eastron-sdm72d-m.mdx | 62 + .../meters/eastron-sdm72dm-v2.mdx | 62 + docs/devices-next/meters/enphase-iq-envoy.mdx | 76 + .../meters/esphome-dlms-meter-austria.mdx | 32 + docs/devices-next/meters/esphome-dsmr.mdx | 28 + docs/devices-next/meters/fenecon.mdx | 73 + .../foxess-h1-series-hybrid-inverter.mdx | 74 + .../foxess-h3-series-hybrid-inverter.mdx | 179 ++ ...foxess-h3-smart-series-hybrid-inverter.mdx | 179 ++ docs/devices-next/meters/fronius-ohmpilot.mdx | 28 + .../meters/fronius-primo-gen24-plus.mdx | 73 + .../fronius-smartmeter-via-inverter.mdx | 48 + .../meters/fronius-solar-api-v1.mdx | 69 + .../meters/fronius-symo-gen24-plus.mdx | 73 + ...nlong-solis-hybrid-inverter-rhi-series.mdx | 120 + ...ginlong-solis-hybrid-inverter-s-series.mdx | 120 + .../meters/ginlong-solis-inverter.mdx | 62 + docs/devices-next/meters/go-e-controller.mdx | 38 + .../goodwe-etehbhbt-hybrid-inverter.mdx | 155 ++ .../meters/goodwe-goodwe-over-wifi.mdx | 48 + .../meters/goodwe-sdtdt-inverter.mdx | 40 + .../meters/growatt-hybrid-inverter.mdx | 156 ++ .../meters/growatt-tl-xh-hybrid-inverter.mdx | 150 ++ docs/devices-next/meters/homematic-ip.mdx | 90 + .../meters/homewizard-kwh-meter.mdx | 38 + .../meters/homewizard-wi-fi-p1-meter.mdx | 22 + ...hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 23 + ...hoymiles-hm-and-hms-series-via-opendtu.mdx | 22 + docs/devices-next/meters/huawei-emma.mdx | 74 + .../meters/huawei-smartlogger.mdx | 104 + .../meters/huawei-sun2000-sdongle.mdx | 32 + docs/devices-next/meters/huawei-sun2000.mdx | 189 ++ docs/devices-next/meters/iammeter-wem3080.mdx | 52 + .../iammeter-wem3080twem3046twem3050t.mdx | 52 + .../meters/igen-tech-solarman-logger.mdx | 24 + docs/devices-next/meters/index.mdx | 1626 ++++++++++++++ .../devices-next/meters/inepro-pro380-mod.mdx | 62 + docs/devices-next/meters/iometer.mdx | 22 + .../meters/janitza-b-series-umg-series.mdx | 74 + .../meters/keba-kecontact-e10.mdx | 27 + .../meters/kostal-energy-meter-c-kem-c.mdx | 74 + .../meters/kostal-energy-meter-p-kem-p.mdx | 62 + .../meters/kostal-piko-hybrid.mdx | 54 + .../meters/kostal-piko-legacy.mdx | 24 + .../meters/kostal-piko-mp-plus.mdx | 22 + .../meters/kostal-piko-piko-ba.mdx | 38 + ...ncl-grid-charging-of-the-house-battery.mdx | 80 + .../meters/kostal-plenticore-hybrid.mdx | 82 + ...kostal-smart-energy-meter-via-inverter.mdx | 30 + .../meters/kostal-smart-energy-meter.mdx | 27 + docs/devices-next/meters/lg-ess-home-15.mdx | 79 + docs/devices-next/meters/lg-ess-home-810.mdx | 82 + .../devices-next/meters/loxone-miniserver.mdx | 74 + .../meters/m-tec-energy-butler-gen2.mdx | 84 + .../meters/m-tec-energy-butler-gen3.mdx | 126 ++ .../meters/marstek-venus-battery-storage.mdx | 57 + .../meters/mhendriks-p1-dongle.mdx | 28 + docs/devices-next/meters/my-pv-ac-elwa-2.mdx | 22 + docs/devices-next/meters/my-pv-ac-elwa-e.mdx | 22 + docs/devices-next/meters/my-pv-acthor.mdx | 22 + docs/devices-next/meters/my-pv-wifi-meter.mdx | 27 + docs/devices-next/meters/mystrom-switch.mdx | 38 + docs/devices-next/meters/openems.mdx | 73 + .../meters/orno-or-we-516-or-we-517.mdx | 62 + docs/devices-next/meters/p1monitor.mdx | 22 + docs/devices-next/meters/plexlog.mdx | 77 + docs/devices-next/meters/powerdog.mdx | 48 + .../meters/powerfox-poweropti.mdx | 54 + .../meters/qcells-hybrid-inverter-cloud.mdx | 63 + .../meters/qcells-qhome-ess-hyb-g3.mdx | 183 ++ docs/devices-next/meters/rct-power.mdx | 77 + .../saia-burgess-controls-ale3-awd3.mdx | 62 + .../saj-h1-series-hybrid-solar-inverter.mdx | 78 + .../saj-h2-series-hybrid-solar-inverter.mdx | 179 ++ .../meters/saj-r5-series-solar-inverter.mdx | 34 + docs/devices-next/meters/sax-homespeicher.mdx | 48 + .../schneider-electric-iem3xxx-modbus.mdx | 62 + docs/devices-next/meters/senec-home.mdx | 58 + .../senergy-se-456ktl-s1g2-inverter.mdx | 27 + ...pm-em-plug-s-pro-3em-in-monophase-mode.mdx | 57 + docs/devices-next/meters/shelly-3em.mdx | 69 + docs/devices-next/meters/shelly-pro-3-em.mdx | 54 + docs/devices-next/meters/siemens-7kt1665.mdx | 74 + .../siemens-junelight-smart-battery.mdx | 77 + docs/devices-next/meters/siemens-pac-2200.mdx | 74 + ...-sigen-hybridsigen-pv-maxsigenstore-ec.mdx | 65 + docs/devices-next/meters/sma-data-manager.mdx | 77 + docs/devices-next/meters/sma-energy-meter.mdx | 50 + .../meters/sma-inverter-speedwire.mdx | 47 + .../sma-smart-energy-hybrid-inverter.mdx | 72 + .../sma-sunny-boy-storage-152025-modbus.mdx | 40 + .../sma-sunny-boy-storage-375060-modbus.mdx | 40 + .../meters/sma-sunny-home-manager-20.mdx | 28 + .../meters/sma-sunny-island-modbus.mdx | 40 + docs/devices-next/meters/sma-webbox.mdx | 27 + .../meters/sma-wechselrichter-modbus.mdx | 27 + .../meters/smartfox-box-reg-reg-extended.mdx | 51 + ...o-light-pro-light-2-light-em2-firmware.mdx | 69 + .../meters/sofarsolar-hyd-36k-ep.mdx | 180 ++ .../meters/sofarsolar-hyd-520k-3ph.mdx | 180 ++ .../sofarsolar-inverter-hybrid-inverter.mdx | 126 ++ .../meters/sofarsolar-sofar-524ktl-g3.mdx | 180 ++ .../meters/sofarsolar-sofar-80136ktl.mdx | 180 ++ docs/devices-next/meters/solaranzeige.mdx | 64 + .../meters/solaredge-hybrid-inverter.mdx | 186 ++ .../meters/solaredge-inverter.mdx | 79 + docs/devices-next/meters/solarlog.mdx | 44 + ...olarmax-maxstorage-maxstorage-ultimate.mdx | 101 + .../meters/solarmax-solarmax-smt.mdx | 27 + .../meters/solarmax-sp-series-inverter.mdx | 27 + ...arwatt-energymanager-energymanager-pro.mdx | 54 + .../meters/solarwatt-manager-flex.mdx | 57 + ...myreserve-matrix-lan-oder-powergateway.mdx | 58 + .../meters/solarwatt-myreserve.mdx | 54 + .../meters/solax-hybrid-inverter-cloud.mdx | 63 + .../meters/solax-hybrid-x1x3-g3g4.mdx | 183 ++ .../meters/solax-inverter-cloud.mdx | 28 + docs/devices-next/meters/solinteng.mdx | 139 ++ .../sonnen-comfort-eco-5-eco-6-oem-65.mdx | 74 + .../meters/sonnen-sonnenbatterie.mdx | 67 + docs/devices-next/meters/st-ems.mdx | 139 ++ .../meters/steca-coolcept-flex.mdx | 22 + .../meters/sungrow-sg-series-inverter.mdx | 74 + .../sungrow-sh-series-hybrid-inverter.mdx | 159 ++ .../meters/sunspec-battery-model-124.mdx | 65 + .../meters/sunspec-battery-model-802.mdx | 66 + .../meters/sunspec-hybrid-inverter.mdx | 150 ++ docs/devices-next/meters/sunspec-inverter.mdx | 126 ++ docs/devices-next/meters/sunspec-meter.mdx | 48 + .../meters/sunsynk-3p-hybrid-inverter.mdx | 179 ++ .../meters/sunsynk-hp3-hybrid-inverter.mdx | 185 ++ .../meters/sunsynk-micro-inverter.mdx | 40 + .../sunsynk-storage-hybrid-inverter.mdx | 126 ++ .../meters/sunsynk-string-inverter.mdx | 40 + docs/devices-next/meters/sunway.mdx | 139 ++ ...sml-ir-reader-for-smartmeters-eg-hichi.mdx | 91 + .../tasmota-tasmota-1-phase-sml-meter.mdx | 70 + .../meters/tasmota-three-phase.mdx | 69 + docs/devices-next/meters/tesla-powerwall.mdx | 95 + docs/devices-next/meters/tibber-pulse.mdx | 23 + .../meters/tp-link-h-series-smart-plug.mdx | 22 + .../tp-link-tapo-p-series-smart-plug.mdx | 24 + .../meters/tq-energy-manager-em2xxem3xx.mdx | 24 + .../meters/tq-energy-manager-em420.mdx | 25 + .../meters/varta-pulse-pulse-neo-element.mdx | 61 + docs/devices-next/meters/victron-em24.mdx | 65 + docs/devices-next/meters/victron-em24e1.mdx | 52 + .../meters/victron-em530em540.mdx | 74 + docs/devices-next/meters/victron-energy.mdx | 82 + docs/devices-next/meters/victron-et340.mdx | 74 + ...volkszahler-http-api-import-and-export.mdx | 24 + .../meters/volkszahler-http-api.mdx | 23 + .../meters/volkszahler-websocket-api.mdx | 24 + docs/devices-next/meters/vzlogger.mdx | 42 + docs/devices-next/meters/wago-879-30xx.mdx | 62 + docs/devices-next/meters/wattsonic.mdx | 139 ++ .../meters/weidmuller-em110-rtu-2p.mdx | 62 + .../meters/weidmuller-em111-rtu-2p.mdx | 62 + .../meters/weidmuller-em120-rtu-2p.mdx | 62 + .../meters/weidmuller-em122-rtu-2p.mdx | 62 + .../meters/youless-energy-monitor.mdx | 41 + .../zcs-azzurro-inverter-hybrid-inverter.mdx | 126 ++ .../meters/zendure-hyper-2000.mdx | 53 + .../zuidwijk-slimmelezer-in-luxembourg.mdx | 25 + .../meters/zuidwijk-slimmelezer-v2.mdx | 25 + .../meters/zuidwijk-slimmelezer.mdx | 28 + docs/devices-next/tariffs/amber-electric.mdx | 32 + docs/devices-next/tariffs/awattar.mdx | 28 + .../electricity-maps-commercial-api.mdx | 26 + .../tariffs/electricity-maps-free-api.mdx | 25 + docs/devices-next/tariffs/energinet.mdx | 28 + docs/devices-next/tariffs/enever.mdx | 31 + docs/devices-next/tariffs/entso-e.mdx | 34 + docs/devices-next/tariffs/forecastsolar.mdx | 39 + docs/devices-next/tariffs/fraunhofer-ise.mdx | 31 + .../tariffs/green-grid-compass.mdx | 25 + .../tariffs/groupe-e-vario-plus.mdx | 26 + docs/devices-next/tariffs/grunstromindex.mdx | 25 + docs/devices-next/tariffs/index.mdx | 202 ++ .../tariffs/national-grid-eso.mdx | 22 + .../tariffs/nordpool-spot-prices.mdx | 33 + .../tariffs/octopus-energy-api.mdx | 25 + .../tariffs/octopus-energy-product-code.mdx | 23 + docs/devices-next/tariffs/open-meteo.mdx | 43 + docs/devices-next/tariffs/ostrom.mdx | 26 + docs/devices-next/tariffs/pun-orario.mdx | 29 + .../tariffs/smartenergy-smartcontrol.mdx | 26 + docs/devices-next/tariffs/solcast.mdx | 33 + docs/devices-next/tariffs/spotty-energie.mdx | 30 + docs/devices-next/tariffs/tibber.mdx | 33 + .../tariffs/victron-vrm-solar-forecast.mdx | 31 + docs/devices-next/vehicles/aiways.mdx | 39 + docs/devices-next/vehicles/audi.mdx | 39 + docs/devices-next/vehicles/bmw.mdx | 47 + docs/devices-next/vehicles/citroen.mdx | 44 + docs/devices-next/vehicles/dacia.mdx | 41 + docs/devices-next/vehicles/ds.mdx | 44 + docs/devices-next/vehicles/evnotify.mdx | 36 + docs/devices-next/vehicles/fiat.mdx | 43 + docs/devices-next/vehicles/ford.mdx | 43 + .../vehicles/generic-vehicle-without-api.mdx | 32 + .../vehicles/hyundai-bluelink.mdx | 44 + docs/devices-next/vehicles/index.mdx | 378 ++++ docs/devices-next/vehicles/iobrokerbmw.mdx | 42 + docs/devices-next/vehicles/iso15118.mdx | 38 + docs/devices-next/vehicles/jeep.mdx | 43 + docs/devices-next/vehicles/kia-bluelink.mdx | 44 + docs/devices-next/vehicles/mercedes-benz.mdx | 46 + docs/devices-next/vehicles/mg.mdx | 40 + docs/devices-next/vehicles/mg2mqtt.mdx | 41 + docs/devices-next/vehicles/mini.mdx | 47 + docs/devices-next/vehicles/mz2mqtt.mdx | 38 + docs/devices-next/vehicles/nissan-ariya.mdx | 39 + .../vehicles/nissan-leaf-pre-2019.mdx | 39 + docs/devices-next/vehicles/nissan-leaf.mdx | 39 + docs/devices-next/vehicles/niu-e-scooter.mdx | 24 + docs/devices-next/vehicles/opel.mdx | 44 + .../open-vehicle-monitoring-system.mdx | 43 + docs/devices-next/vehicles/peugeot.mdx | 44 + docs/devices-next/vehicles/polestar.mdx | 39 + .../vehicles/psa-car-controller.mdx | 40 + docs/devices-next/vehicles/renault.mdx | 40 + ...nect-gen3-ateca-leon-formentor-tarraco.mdx | 39 + ...raconnect-gen4-born-formentor-tavascan.mdx | 41 + docs/devices-next/vehicles/skoda-enyaq.mdx | 41 + docs/devices-next/vehicles/smart-eq.mdx | 46 + docs/devices-next/vehicles/smart.mdx | 41 + docs/devices-next/vehicles/tesla-ble.mdx | 41 + docs/devices-next/vehicles/tesla.mdx | 59 + docs/devices-next/vehicles/teslalogger.mdx | 41 + docs/devices-next/vehicles/teslamate.mdx | 37 + docs/devices-next/vehicles/tessie.mdx | 39 + docs/devices-next/vehicles/toyota.mdx | 42 + docs/devices-next/vehicles/tronity.mdx | 41 + .../vehicles/volkswagen-we-connect-id.mdx | 44 + docs/devices-next/vehicles/volvo.mdx | 52 + docs/devices-next/vehicles/volvo2mqtt.mdx | 39 + .../vehicles/zero-motorcycles.mdx | 39 + .../devices-next/chargers/abb-terra-ac.mdx | 36 + .../devices-next/chargers/abl-em4-sbcx.mdx | 38 + .../devices-next/chargers/abl-emh1.mdx | 36 + .../devices-next/chargers/abl-emh2.mdx | 36 + .../devices-next/chargers/abl-sursum-emh2.mdx | 33 + .../devices-next/chargers/abl-sursum-emh3.mdx | 33 + .../devices-next/chargers/abl-sursum-emh4.mdx | 33 + .../devices-next/chargers/alfen-eve.mdx | 33 + .../chargers/alphatec-ladesaule-twin.mdx | 38 + .../chargers/alphatec-wallbox-mini-power.mdx | 38 + .../amperfied-wallbox-connectbusiness.mdx | 28 + .../amperfied-wallbox-connecthome.mdx | 28 + .../amperfied-wallbox-connectsolar.mdx | 28 + .../amperfied-wallbox-energy-control.mdx | 38 + .../devices-next/chargers/ampure-live.mdx | 31 + .../devices-next/chargers/ampure-next.mdx | 27 + .../devices-next/chargers/ampure-unite.mdx | 31 + .../chargers/audi-audi-wallbox-pro.mdx | 29 + .../chargers/audi-wallbox-plus.mdx | 31 + .../chargers/autel-ac-compact.mdx | 41 + .../chargers/autel-ac-maxicharger.mdx | 41 + .../chargers/autoaid-business-wallbox.mdx | 33 + .../chargers/autoaid-intelligent-wallbox.mdx | 33 + .../devices-next/chargers/avm-fritzdect.mdx | 36 + .../devices-next/chargers/bender-cc612.mdx | 31 + .../devices-next/chargers/bender-cc613.mdx | 31 + .../devices-next/chargers/bender-icc1314.mdx | 31 + .../devices-next/chargers/bender-icc1324.mdx | 31 + .../devices-next/chargers/bmw-i-wallbox.mdx | 41 + .../devices-next/chargers/bosch-sg-ready.mdx | 27 + .../devices-next/chargers/bosch-x-change.mdx | 28 + .../chargers/buderus-sg-ready.mdx | 27 + .../chargers/cfos-power-brain-solar.mdx | 29 + .../chargers/cfos-power-brain.mdx | 29 + .../chargers/charge-amps-halo.mdx | 33 + .../devices-next/chargers/compleo-ebox.mdx | 28 + .../devices-next/chargers/cubos-c11e-c22e.mdx | 31 + .../chargers/cupra-charger-connect-2.mdx | 29 + .../chargers/cupra-charger-connect.mdx | 31 + .../chargers/cupra-charger-pro-2.mdx | 29 + .../cupra-charger-pro-eichrecht-2.mdx | 29 + .../chargers/cupra-charger-pro.mdx | 29 + .../chargers/dadapower-premium-wallbox.mdx | 28 + .../chargers/daheimladen-wallbox.mdx | 25 + .../chargers/daikin-homehub-sg-ready.mdx | 27 + .../chargers/delta-ac-max-basic.mdx | 64 + .../chargers/delta-ac-max-smart.mdx | 64 + .../chargers/delta-slim-charger.mdx | 64 + .../chargers/delta-ultra-fast-charger.mdx | 64 + .../devices-next/chargers/demo-charger.mdx | 34 + .../chargers/e3dc-easy-connect.mdx | 31 + .../chargers/easee-charge-core.mdx | 27 + .../chargers/easee-charge-lite.mdx | 27 + .../devices-next/chargers/easee-charge.mdx | 27 + .../devices-next/chargers/easee-home.mdx | 27 + .../devices-next/chargers/ebee-wallbox.mdx | 31 + .../devices-next/chargers/echarge-cph1.mdx | 31 + .../chargers/echarge-cph2-cpm2.mdx | 23 + .../chargers/ecoharmony-evse-epc-20-plus.mdx | 39 + .../chargers/edgetech-smart-evse.mdx | 33 + .../chargers/eebus-compatible.mdx | 22 + .../devices-next/chargers/elecq-biz.mdx | 33 + .../devices-next/chargers/elecq-home.mdx | 33 + .../devices-next/chargers/elecq-station.mdx | 33 + .../devices-next/chargers/eledio-go.mdx | 36 + .../chargers/elli-charger-connect-2.mdx | 29 + .../chargers/elli-charger-connect.mdx | 31 + .../chargers/elli-charger-pro-2.mdx | 29 + .../chargers/elli-charger-pro-eichrecht-2.mdx | 29 + .../chargers/elli-charger-pro.mdx | 29 + .../devices-next/chargers/em2go-home.mdx | 24 + .../chargers/em2go-pro-power-ocpponc.mdx | 29 + .../chargers/en-ac-ev-charger.mdx | 33 + .../devices-next/chargers/enercab-smart.mdx | 36 + .../chargers/ensto-chago-wallbox.mdx | 31 + .../chargers/entratek-power-dot-fix.mdx | 33 + .../chargers/entratek-power-dot-pro-2.mdx | 33 + .../devices-next/chargers/eon-drive-ebox.mdx | 28 + .../devices-next/chargers/eon-drive-vbox.mdx | 31 + .../devices-next/chargers/esl-walli-light.mdx | 31 + .../chargers/esystems-ghostone.mdx | 29 + .../devices-next/chargers/etrel-inch-duo.mdx | 33 + .../devices-next/chargers/etrel-inch.mdx | 27 + .../devices-next/chargers/evbox-elvi.mdx | 34 + .../devices-next/chargers/evbox-livo.mdx | 25 + .../devices-next/chargers/evse-din.mdx | 33 + .../devices-next/chargers/evse-wifi.mdx | 21 + .../chargers/free2move-eprowallbox.mdx | 35 + .../free2move-esolutions-eprowallbox.mdx | 33 + .../chargers/fronius-wattpilot.mdx | 33 + .../chargers/garo-glb-glb-ls4-ls4-compact.mdx | 31 + .../chargers/go-e-charger-gemini.mdx | 33 + .../chargers/go-e-charger-home.mdx | 28 + .../chargers/go-e-charger-homefix.mdx | 26 + .../chargers/go-e-charger-pro.mdx | 33 + .../devices-next/chargers/go-e-charger-v3.mdx | 33 + .../devices-next/chargers/hardybarth-cph1.mdx | 31 + .../chargers/hardybarth-cph2-cpm2.mdx | 23 + .../chargers/heidelberg-energy-control.mdx | 38 + .../chargers/hesotec-esat-ebox.mdx | 28 + .../chargers/home-assistant-switch.mdx | 36 + .../chargers/homecharge-homecharger.mdx | 38 + .../devices-next/chargers/homematic-ip.mdx | 41 + .../devices-next/chargers/homewizard.mdx | 30 + .../huawei-scharger-7ks-s0-22kt-s0.mdx | 33 + .../current/devices-next/chargers/idm.mdx | 27 + .../current/devices-next/chargers/index.mdx | 1962 +++++++++++++++++ .../devices-next/chargers/innogy-ebox.mdx | 28 + .../devices-next/chargers/inro-pantabox.mdx | 21 + .../chargers/juice-charger-me.mdx | 31 + .../chargers/junkers-sg-ready.mdx | 27 + ...-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx | 31 + .../keba-kecontact-p20-p30-cx-series.mdx | 41 + .../chargers/keba-kecontact-p40-p40-pro.mdx | 41 + .../chargers/kermi-x-center-pro.mdx | 28 + .../chargers/kontron-solar-charger.mdx | 29 + .../devices-next/chargers/kostal-enector.mdx | 40 + .../devices-next/chargers/kse-wbx16.mdx | 35 + .../chargers/ladefoxx-evload-mikro-20.mdx | 36 + .../chargers/lambda-eu-l-series.mdx | 34 + .../chargers/lrt-home-essential.mdx | 38 + .../chargers/mennekes-amedio-professional.mdx | 31 + .../mennekes-amtron-4business-700.mdx | 31 + .../chargers/mennekes-amtron-4you-300.mdx | 40 + .../chargers/mennekes-amtron-4you-500.mdx | 31 + .../mennekes-amtron-chargecontrol.mdx | 31 + .../chargers/mennekes-amtron-compact-20s.mdx | 40 + .../chargers/mennekes-amtron-premium.mdx | 28 + .../chargers/mennekes-amtron-professional.mdx | 31 + .../chargers/mennekes-amtron-xtra.mdx | 28 + .../mennekes-emobility-gateway-acu.mdx | 38 + .../chargers/mennekes-smart-acu.mdx | 38 + .../chargers/mennekes-smart-t-acu.mdx | 38 + .../devices-next/chargers/my-pv-ac-elwa-2.mdx | 29 + .../chargers/my-pv-ac-thor-ac-thor-9s.mdx | 30 + .../devices-next/chargers/mystrom-switch.mdx | 30 + .../devices-next/chargers/nrgkick-connect.mdx | 26 + .../devices-next/chargers/nrgkick-gen2.mdx | 38 + .../chargers/obo-bettermann-ion.mdx | 39 + .../ocpp-16j-compatible-smart-charging.mdx | 54 + .../devices-next/chargers/openevse.mdx | 26 + .../devices-next/chargers/openwb-pro.mdx | 21 + .../devices-next/chargers/openwb-series2.mdx | 30 + .../chargers/openwb-software-2x.mdx | 44 + .../chargers/optec-mobility-one.mdx | 31 + .../devices-next/chargers/orbis-viaris.mdx | 33 + .../chargers/pc-electric-garo.mdx | 27 + .../peblar-home-home-plus-business.mdx | 31 + .../chargers/phoenix-contact-charx.mdx | 36 + .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 26 + ...ix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 31 + ...oenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 31 + ...nix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 31 + ...hoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 31 + .../chargers/phoenix-contact-ev-ser.mdx | 33 + .../devices-next/chargers/plugchoice.mdx | 40 + .../porsche-mobile-charger-connect.mdx | 22 + .../chargers/porsche-mobile-charger-plus.mdx | 22 + .../devices-next/chargers/porsche-wallbox.mdx | 29 + .../devices-next/chargers/pracht-alpha-xt.mdx | 66 + .../devices-next/chargers/pracht-mono-xt.mdx | 66 + .../devices-next/chargers/pracht-pni.mdx | 66 + .../devices-next/chargers/pracht-xt.mdx | 66 + .../chargers/pulsares-simplebox.mdx | 33 + .../devices-next/chargers/pulsatrix.mdx | 23 + .../chargers/qcells-qhome-edrive-a.mdx | 38 + .../chargers/schneider-evlink-pro.mdx | 28 + .../chargers/schrack-i-charge-cion.mdx | 33 + .../chargers/senec-wallbox-pro-s.mdx | 38 + .../chargers/senec-wallbox-pro.mdx | 36 + .../current/devices-next/chargers/shelly.mdx | 36 + .../chargers/siemens-versicharge-gen3.mdx | 31 + .../chargers/skoda-charger-connect.mdx | 29 + .../chargers/skoda-charger-pro-eichrecht.mdx | 29 + .../chargers/skoda-charger-pro.mdx | 29 + .../chargers/skoda-iv-charger-connect.mdx | 29 + .../chargers/sma-ev-charger-echarger.mdx | 28 + .../chargers/smartfox-pro-charger.mdx | 33 + .../current/devices-next/chargers/smartwb.mdx | 21 + .../chargers/solaredge-home-ev-charger.mdx | 41 + .../devices-next/chargers/solax-x3-evc.mdx | 38 + .../chargers/sonnen-sonnencharger.mdx | 27 + .../chargers/spelsberg-wallbox-smart-pro.mdx | 31 + .../chargers/stark-in-strom-easy.mdx | 33 + .../stiebel-eltron-lwalwz-sg-ready.mdx | 27 + .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 27 + .../chargers/sungrow-ac011e-01.mdx | 41 + .../devices-next/chargers/sungrow-ac011e.mdx | 33 + .../chargers/tasmota-single-phase.mdx | 36 + .../chargers/tecalor-thz-sg-ready.mdx | 27 + .../chargers/technisat-technivolt.mdx | 31 + .../devices-next/chargers/tesla-twc3.mdx | 24 + .../current/devices-next/chargers/tessie.mdx | 26 + .../chargers/tigo-go-ev-charger.mdx | 38 + .../chargers/tinkerforge-warp-charger-pro.mdx | 38 + .../tinkerforge-warp-charger-smart.mdx | 38 + .../tinkerforge-warp3-charger-pro.mdx | 36 + .../tinkerforge-warp3-charger-smart.mdx | 33 + .../chargers/tp-link-h-series-smart-plug.mdx | 30 + .../tp-link-tapo-p-series-smart-plug.mdx | 34 + .../chargers/ubitricity-heinz.mdx | 31 + .../devices-next/chargers/v2c-trydan.mdx | 23 + .../chargers/vaillant-sensonet-sg-ready.mdx | 28 + .../vestel-evc04-home-smart-connect-plus.mdx | 31 + .../victron-ev-charging-station-via-gx.mdx | 29 + .../chargers/victron-ev-charging-station.mdx | 29 + .../chargers/viessmann-heatpump-sg-ready.mdx | 30 + .../chargers/viridian-ev-evse-epc-20-plus.mdx | 39 + .../chargers/volkswagen-charger-connect-2.mdx | 29 + .../chargers/volkswagen-charger-pro-2.mdx | 29 + .../volkswagen-charger-pro-eichrecht-2.mdx | 29 + .../volkswagen-id-charger-connect.mdx | 31 + .../chargers/volkswagen-id-charger-pro.mdx | 29 + .../devices-next/chargers/volt-time-one.mdx | 24 + .../chargers/volt-time-source-2.mdx | 24 + .../chargers/volt-time-source-2s.mdx | 24 + .../chargers/volt-time-source.mdx | 24 + .../devices-next/chargers/wallbe-eco-20s.mdx | 31 + .../devices-next/chargers/wallbe-eco.mdx | 31 + .../devices-next/chargers/wallbe-pro.mdx | 31 + .../chargers/wallbox-commander-2-fw-5x.mdx | 42 + .../chargers/wallbox-commander-2.mdx | 42 + .../chargers/wallbox-copper-sb-fw-5x.mdx | 42 + .../chargers/wallbox-copper-sb.mdx | 42 + .../chargers/wallbox-pulsar-max-fw-5x.mdx | 42 + .../chargers/wallbox-pulsar-max.mdx | 42 + .../chargers/wallbox-pulsar-plus-fw-5x.mdx | 42 + .../chargers/wallbox-pulsar-plus.mdx | 42 + .../chargers/walther-werke-basic-evo-pro.mdx | 38 + .../devices-next/chargers/webasto-live.mdx | 31 + .../devices-next/chargers/webasto-next.mdx | 27 + .../devices-next/chargers/webasto-unite.mdx | 31 + .../chargers/weidmuller-ac-smart.mdx | 23 + .../devices-next/chargers/zaptec-go-2.mdx | 25 + .../devices-next/chargers/zaptec-go.mdx | 25 + .../devices-next/chargers/zaptec-pro.mdx | 25 + .../chargers/zewotherm-eu-l-series.mdx | 34 + .../chargers/zj-beny-bcp-ev-charger.mdx | 33 + .../current/devices-next/meters/a-tronix.mdx | 139 ++ .../meters/abb-a43-a44-b23-b24.mdx | 62 + .../acrel-adw300-wireless-metering-meter.mdx | 102 + .../devices-next/meters/ads-tec-storaxe.mdx | 38 + .../meters/alpha-ess-storion-smile.mdx | 182 ++ .../meters/ampere-amperestoragepro.mdx | 179 ++ .../meters/anker-micro-inverter.mdx | 40 + .../devices-next/meters/apsystems-ez1.mdx | 22 + .../devices-next/meters/avm-fritzdect.mdx | 44 + .../meters/axitec-axihycon-12-15h.mdx | 120 + .../meters/bernecker-engineering-mpm3pm.mdx | 62 + .../devices-next/meters/bgetech-ds100.mdx | 130 ++ .../devices-next/meters/bgetech-ws100.mdx | 130 ++ .../meters/bosch-bpt-s-5-hybrid.mdx | 54 + .../meters/bosswerk-micro-inverter.mdx | 40 + .../meters/carlo-gavazzi-em110111112.mdx | 62 + .../meters/carlo-gavazzi-em24.mdx | 65 + .../meters/carlo-gavazzi-em24e1.mdx | 52 + .../meters/carlo-gavazzi-em330em340.mdx | 74 + .../meters/carlo-gavazzi-em530em540.mdx | 74 + .../meters/carlo-gavazzi-et112.mdx | 62 + .../meters/carlo-gavazzi-et330et340.mdx | 74 + .../meters/cfos-powerbrain-meter.mdx | 29 + .../devices-next/meters/demo-battery.mdx | 38 + .../devices-next/meters/demo-meter.mdx | 97 + .../meters/deye-3p-hybrid-inverter.mdx | 179 ++ .../meters/deye-hp3-hybrid-inverter.mdx | 185 ++ .../meters/deye-micro-inverter.mdx | 40 + .../meters/deye-storage-hybrid-inverter.mdx | 126 ++ .../meters/deye-string-inverter.mdx | 40 + .../devices-next/meters/discovergy.mdx | 42 + .../current/devices-next/meters/dsmr.mdx | 30 + .../devices-next/meters/dzg-dvh4013.mdx | 34 + .../current/devices-next/meters/e3dc.mdx | 97 + .../meters/eastron-sdm120-modbus.mdx | 84 + .../devices-next/meters/eastron-sdm220230.mdx | 62 + .../meters/eastron-sdm630-modbus.mdx | 62 + .../devices-next/meters/eastron-sdm72d-m.mdx | 62 + .../meters/eastron-sdm72dm-v2.mdx | 62 + .../devices-next/meters/enphase-iq-envoy.mdx | 76 + .../meters/esphome-dlms-meter-austria.mdx | 32 + .../devices-next/meters/esphome-dsmr.mdx | 28 + .../current/devices-next/meters/fenecon.mdx | 73 + .../foxess-h1-series-hybrid-inverter.mdx | 74 + .../foxess-h3-series-hybrid-inverter.mdx | 179 ++ ...foxess-h3-smart-series-hybrid-inverter.mdx | 179 ++ .../devices-next/meters/fronius-ohmpilot.mdx | 28 + .../meters/fronius-primo-gen24-plus.mdx | 73 + .../fronius-smartmeter-via-inverter.mdx | 48 + .../meters/fronius-solar-api-v1.mdx | 69 + .../meters/fronius-symo-gen24-plus.mdx | 73 + ...nlong-solis-hybrid-inverter-rhi-series.mdx | 120 + ...ginlong-solis-hybrid-inverter-s-series.mdx | 120 + .../meters/ginlong-solis-inverter.mdx | 62 + .../devices-next/meters/go-e-controller.mdx | 38 + .../goodwe-etehbhbt-hybrid-inverter.mdx | 155 ++ .../meters/goodwe-goodwe-over-wifi.mdx | 48 + .../meters/goodwe-sdtdt-inverter.mdx | 40 + .../meters/growatt-hybrid-inverter.mdx | 156 ++ .../meters/growatt-tl-xh-hybrid-inverter.mdx | 150 ++ .../devices-next/meters/homematic-ip.mdx | 90 + .../meters/homewizard-kwh-meter.mdx | 38 + .../meters/homewizard-wi-fi-p1-meter.mdx | 22 + ...hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 23 + ...hoymiles-hm-and-hms-series-via-opendtu.mdx | 22 + .../devices-next/meters/huawei-emma.mdx | 74 + .../meters/huawei-smartlogger.mdx | 104 + .../meters/huawei-sun2000-sdongle.mdx | 32 + .../devices-next/meters/huawei-sun2000.mdx | 189 ++ .../devices-next/meters/iammeter-wem3080.mdx | 52 + .../iammeter-wem3080twem3046twem3050t.mdx | 52 + .../meters/igen-tech-solarman-logger.mdx | 24 + .../current/devices-next/meters/index.mdx | 1626 ++++++++++++++ .../devices-next/meters/inepro-pro380-mod.mdx | 62 + .../current/devices-next/meters/iometer.mdx | 22 + .../meters/janitza-b-series-umg-series.mdx | 74 + .../meters/keba-kecontact-e10.mdx | 27 + .../meters/kostal-energy-meter-c-kem-c.mdx | 74 + .../meters/kostal-energy-meter-p-kem-p.mdx | 62 + .../meters/kostal-piko-hybrid.mdx | 54 + .../meters/kostal-piko-legacy.mdx | 24 + .../meters/kostal-piko-mp-plus.mdx | 22 + .../meters/kostal-piko-piko-ba.mdx | 38 + ...ncl-grid-charging-of-the-house-battery.mdx | 80 + .../meters/kostal-plenticore-hybrid.mdx | 82 + ...kostal-smart-energy-meter-via-inverter.mdx | 30 + .../meters/kostal-smart-energy-meter.mdx | 27 + .../devices-next/meters/lg-ess-home-15.mdx | 79 + .../devices-next/meters/lg-ess-home-810.mdx | 82 + .../devices-next/meters/loxone-miniserver.mdx | 74 + .../meters/m-tec-energy-butler-gen2.mdx | 84 + .../meters/m-tec-energy-butler-gen3.mdx | 126 ++ .../meters/marstek-venus-battery-storage.mdx | 57 + .../meters/mhendriks-p1-dongle.mdx | 28 + .../devices-next/meters/my-pv-ac-elwa-2.mdx | 22 + .../devices-next/meters/my-pv-ac-elwa-e.mdx | 22 + .../devices-next/meters/my-pv-acthor.mdx | 22 + .../devices-next/meters/my-pv-wifi-meter.mdx | 27 + .../devices-next/meters/mystrom-switch.mdx | 38 + .../current/devices-next/meters/openems.mdx | 73 + .../meters/orno-or-we-516-or-we-517.mdx | 62 + .../current/devices-next/meters/p1monitor.mdx | 22 + .../current/devices-next/meters/plexlog.mdx | 77 + .../current/devices-next/meters/powerdog.mdx | 48 + .../meters/powerfox-poweropti.mdx | 54 + .../meters/qcells-hybrid-inverter-cloud.mdx | 63 + .../meters/qcells-qhome-ess-hyb-g3.mdx | 183 ++ .../current/devices-next/meters/rct-power.mdx | 77 + .../saia-burgess-controls-ale3-awd3.mdx | 62 + .../saj-h1-series-hybrid-solar-inverter.mdx | 78 + .../saj-h2-series-hybrid-solar-inverter.mdx | 179 ++ .../meters/saj-r5-series-solar-inverter.mdx | 34 + .../devices-next/meters/sax-homespeicher.mdx | 48 + .../schneider-electric-iem3xxx-modbus.mdx | 62 + .../devices-next/meters/senec-home.mdx | 58 + .../senergy-se-456ktl-s1g2-inverter.mdx | 27 + ...pm-em-plug-s-pro-3em-in-monophase-mode.mdx | 57 + .../devices-next/meters/shelly-3em.mdx | 69 + .../devices-next/meters/shelly-pro-3-em.mdx | 54 + .../devices-next/meters/siemens-7kt1665.mdx | 74 + .../siemens-junelight-smart-battery.mdx | 77 + .../devices-next/meters/siemens-pac-2200.mdx | 74 + ...-sigen-hybridsigen-pv-maxsigenstore-ec.mdx | 65 + .../devices-next/meters/sma-data-manager.mdx | 77 + .../devices-next/meters/sma-energy-meter.mdx | 50 + .../meters/sma-inverter-speedwire.mdx | 47 + .../sma-smart-energy-hybrid-inverter.mdx | 72 + .../sma-sunny-boy-storage-152025-modbus.mdx | 40 + .../sma-sunny-boy-storage-375060-modbus.mdx | 40 + .../meters/sma-sunny-home-manager-20.mdx | 28 + .../meters/sma-sunny-island-modbus.mdx | 40 + .../devices-next/meters/sma-webbox.mdx | 27 + .../meters/sma-wechselrichter-modbus.mdx | 27 + .../meters/smartfox-box-reg-reg-extended.mdx | 51 + ...o-light-pro-light-2-light-em2-firmware.mdx | 69 + .../meters/sofarsolar-hyd-36k-ep.mdx | 180 ++ .../meters/sofarsolar-hyd-520k-3ph.mdx | 180 ++ .../sofarsolar-inverter-hybrid-inverter.mdx | 126 ++ .../meters/sofarsolar-sofar-524ktl-g3.mdx | 180 ++ .../meters/sofarsolar-sofar-80136ktl.mdx | 180 ++ .../devices-next/meters/solaranzeige.mdx | 64 + .../meters/solaredge-hybrid-inverter.mdx | 186 ++ .../meters/solaredge-inverter.mdx | 79 + .../current/devices-next/meters/solarlog.mdx | 44 + ...olarmax-maxstorage-maxstorage-ultimate.mdx | 101 + .../meters/solarmax-solarmax-smt.mdx | 27 + .../meters/solarmax-sp-series-inverter.mdx | 27 + ...arwatt-energymanager-energymanager-pro.mdx | 54 + .../meters/solarwatt-manager-flex.mdx | 57 + ...myreserve-matrix-lan-oder-powergateway.mdx | 58 + .../meters/solarwatt-myreserve.mdx | 54 + .../meters/solax-hybrid-inverter-cloud.mdx | 63 + .../meters/solax-hybrid-x1x3-g3g4.mdx | 183 ++ .../meters/solax-inverter-cloud.mdx | 28 + .../current/devices-next/meters/solinteng.mdx | 139 ++ .../sonnen-comfort-eco-5-eco-6-oem-65.mdx | 74 + .../meters/sonnen-sonnenbatterie.mdx | 67 + .../current/devices-next/meters/st-ems.mdx | 139 ++ .../meters/steca-coolcept-flex.mdx | 22 + .../meters/sungrow-sg-series-inverter.mdx | 74 + .../sungrow-sh-series-hybrid-inverter.mdx | 159 ++ .../meters/sunspec-battery-model-124.mdx | 65 + .../meters/sunspec-battery-model-802.mdx | 66 + .../meters/sunspec-hybrid-inverter.mdx | 150 ++ .../devices-next/meters/sunspec-inverter.mdx | 126 ++ .../devices-next/meters/sunspec-meter.mdx | 48 + .../meters/sunsynk-3p-hybrid-inverter.mdx | 179 ++ .../meters/sunsynk-hp3-hybrid-inverter.mdx | 185 ++ .../meters/sunsynk-micro-inverter.mdx | 40 + .../sunsynk-storage-hybrid-inverter.mdx | 126 ++ .../meters/sunsynk-string-inverter.mdx | 40 + .../current/devices-next/meters/sunway.mdx | 139 ++ ...sml-ir-reader-for-smartmeters-eg-hichi.mdx | 91 + .../tasmota-tasmota-1-phase-sml-meter.mdx | 70 + .../meters/tasmota-three-phase.mdx | 69 + .../devices-next/meters/tesla-powerwall.mdx | 95 + .../devices-next/meters/tibber-pulse.mdx | 23 + .../meters/tp-link-h-series-smart-plug.mdx | 22 + .../tp-link-tapo-p-series-smart-plug.mdx | 24 + .../meters/tq-energy-manager-em2xxem3xx.mdx | 24 + .../meters/tq-energy-manager-em420.mdx | 25 + .../meters/varta-pulse-pulse-neo-element.mdx | 61 + .../devices-next/meters/victron-em24.mdx | 65 + .../devices-next/meters/victron-em24e1.mdx | 52 + .../meters/victron-em530em540.mdx | 74 + .../devices-next/meters/victron-energy.mdx | 82 + .../devices-next/meters/victron-et340.mdx | 74 + ...volkszahler-http-api-import-and-export.mdx | 24 + .../meters/volkszahler-http-api.mdx | 23 + .../meters/volkszahler-websocket-api.mdx | 24 + .../current/devices-next/meters/vzlogger.mdx | 42 + .../devices-next/meters/wago-879-30xx.mdx | 62 + .../current/devices-next/meters/wattsonic.mdx | 139 ++ .../meters/weidmuller-em110-rtu-2p.mdx | 62 + .../meters/weidmuller-em111-rtu-2p.mdx | 62 + .../meters/weidmuller-em120-rtu-2p.mdx | 62 + .../meters/weidmuller-em122-rtu-2p.mdx | 62 + .../meters/youless-energy-monitor.mdx | 41 + .../zcs-azzurro-inverter-hybrid-inverter.mdx | 126 ++ .../meters/zendure-hyper-2000.mdx | 53 + .../zuidwijk-slimmelezer-in-luxembourg.mdx | 25 + .../meters/zuidwijk-slimmelezer-v2.mdx | 25 + .../meters/zuidwijk-slimmelezer.mdx | 28 + .../devices-next/tariffs/amber-electric.mdx | 32 + .../current/devices-next/tariffs/awattar.mdx | 28 + .../electricity-maps-commercial-api.mdx | 26 + .../tariffs/electricity-maps-free-api.mdx | 25 + .../devices-next/tariffs/energinet.mdx | 28 + .../current/devices-next/tariffs/enever.mdx | 31 + .../current/devices-next/tariffs/entso-e.mdx | 34 + .../devices-next/tariffs/forecastsolar.mdx | 39 + .../devices-next/tariffs/fraunhofer-ise.mdx | 31 + .../tariffs/green-grid-compass.mdx | 25 + .../tariffs/groupe-e-vario-plus.mdx | 26 + .../devices-next/tariffs/grunstromindex.mdx | 25 + .../current/devices-next/tariffs/index.mdx | 202 ++ .../tariffs/national-grid-eso.mdx | 22 + .../tariffs/nordpool-spot-prices.mdx | 33 + .../tariffs/octopus-energy-api.mdx | 25 + .../tariffs/octopus-energy-product-code.mdx | 23 + .../devices-next/tariffs/open-meteo.mdx | 43 + .../current/devices-next/tariffs/ostrom.mdx | 26 + .../devices-next/tariffs/pun-orario.mdx | 29 + .../tariffs/smartenergy-smartcontrol.mdx | 26 + .../current/devices-next/tariffs/solcast.mdx | 33 + .../devices-next/tariffs/spotty-energie.mdx | 30 + .../current/devices-next/tariffs/tibber.mdx | 33 + .../tariffs/victron-vrm-solar-forecast.mdx | 31 + .../current/devices-next/vehicles/aiways.mdx | 39 + .../current/devices-next/vehicles/audi.mdx | 39 + .../current/devices-next/vehicles/bmw.mdx | 47 + .../current/devices-next/vehicles/citroen.mdx | 44 + .../current/devices-next/vehicles/dacia.mdx | 41 + .../current/devices-next/vehicles/ds.mdx | 44 + .../devices-next/vehicles/evnotify.mdx | 36 + .../current/devices-next/vehicles/fiat.mdx | 43 + .../current/devices-next/vehicles/ford.mdx | 43 + .../vehicles/generic-vehicle-without-api.mdx | 32 + .../vehicles/hyundai-bluelink.mdx | 44 + .../current/devices-next/vehicles/index.mdx | 378 ++++ .../devices-next/vehicles/iobrokerbmw.mdx | 42 + .../devices-next/vehicles/iso15118.mdx | 38 + .../current/devices-next/vehicles/jeep.mdx | 43 + .../devices-next/vehicles/kia-bluelink.mdx | 44 + .../devices-next/vehicles/mercedes-benz.mdx | 46 + .../current/devices-next/vehicles/mg.mdx | 40 + .../current/devices-next/vehicles/mg2mqtt.mdx | 41 + .../current/devices-next/vehicles/mini.mdx | 47 + .../current/devices-next/vehicles/mz2mqtt.mdx | 38 + .../devices-next/vehicles/nissan-ariya.mdx | 39 + .../vehicles/nissan-leaf-pre-2019.mdx | 39 + .../devices-next/vehicles/nissan-leaf.mdx | 39 + .../devices-next/vehicles/niu-e-scooter.mdx | 24 + .../current/devices-next/vehicles/opel.mdx | 44 + .../open-vehicle-monitoring-system.mdx | 43 + .../current/devices-next/vehicles/peugeot.mdx | 44 + .../devices-next/vehicles/polestar.mdx | 39 + .../vehicles/psa-car-controller.mdx | 40 + .../current/devices-next/vehicles/renault.mdx | 40 + ...nect-gen3-ateca-leon-formentor-tarraco.mdx | 39 + ...raconnect-gen4-born-formentor-tavascan.mdx | 41 + .../devices-next/vehicles/skoda-enyaq.mdx | 41 + .../devices-next/vehicles/smart-eq.mdx | 46 + .../current/devices-next/vehicles/smart.mdx | 41 + .../devices-next/vehicles/tesla-ble.mdx | 41 + .../current/devices-next/vehicles/tesla.mdx | 59 + .../devices-next/vehicles/teslalogger.mdx | 41 + .../devices-next/vehicles/teslamate.mdx | 37 + .../current/devices-next/vehicles/tessie.mdx | 39 + .../current/devices-next/vehicles/toyota.mdx | 42 + .../current/devices-next/vehicles/tronity.mdx | 41 + .../vehicles/volkswagen-we-connect-id.mdx | 44 + .../current/devices-next/vehicles/volvo.mdx | 52 + .../devices-next/vehicles/volvo2mqtt.mdx | 39 + .../vehicles/zero-motorcycles.mdx | 39 + package-lock.json | 555 ++++- package.json | 12 +- sidebars.js | 11 - src/components/DeviceCard.module.css | 130 ++ src/components/DeviceCard.tsx | 94 + src/generateDevicesNext.ts | 467 ++++ static/img/devices/placeholder.svg | 6 + tsconfig.json | 19 + 1034 files changed, 59635 insertions(+), 22 deletions(-) create mode 100644 docs/devices-next/chargers/abb-terra-ac.mdx create mode 100644 docs/devices-next/chargers/abl-em4-sbcx.mdx create mode 100644 docs/devices-next/chargers/abl-emh1.mdx create mode 100644 docs/devices-next/chargers/abl-emh2.mdx create mode 100644 docs/devices-next/chargers/abl-sursum-emh2.mdx create mode 100644 docs/devices-next/chargers/abl-sursum-emh3.mdx create mode 100644 docs/devices-next/chargers/abl-sursum-emh4.mdx create mode 100644 docs/devices-next/chargers/alfen-eve.mdx create mode 100644 docs/devices-next/chargers/alphatec-ladesaule-twin.mdx create mode 100644 docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx create mode 100644 docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx create mode 100644 docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx create mode 100644 docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx create mode 100644 docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx create mode 100644 docs/devices-next/chargers/ampure-live.mdx create mode 100644 docs/devices-next/chargers/ampure-next.mdx create mode 100644 docs/devices-next/chargers/ampure-unite.mdx create mode 100644 docs/devices-next/chargers/audi-audi-wallbox-pro.mdx create mode 100644 docs/devices-next/chargers/audi-wallbox-plus.mdx create mode 100644 docs/devices-next/chargers/autel-ac-compact.mdx create mode 100644 docs/devices-next/chargers/autel-ac-maxicharger.mdx create mode 100644 docs/devices-next/chargers/autoaid-business-wallbox.mdx create mode 100644 docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx create mode 100644 docs/devices-next/chargers/avm-fritzdect.mdx create mode 100644 docs/devices-next/chargers/bender-cc612.mdx create mode 100644 docs/devices-next/chargers/bender-cc613.mdx create mode 100644 docs/devices-next/chargers/bender-icc1314.mdx create mode 100644 docs/devices-next/chargers/bender-icc1324.mdx create mode 100644 docs/devices-next/chargers/bmw-i-wallbox.mdx create mode 100644 docs/devices-next/chargers/bosch-sg-ready.mdx create mode 100644 docs/devices-next/chargers/bosch-x-change.mdx create mode 100644 docs/devices-next/chargers/buderus-sg-ready.mdx create mode 100644 docs/devices-next/chargers/cfos-power-brain-solar.mdx create mode 100644 docs/devices-next/chargers/cfos-power-brain.mdx create mode 100644 docs/devices-next/chargers/charge-amps-halo.mdx create mode 100644 docs/devices-next/chargers/compleo-ebox.mdx create mode 100644 docs/devices-next/chargers/cubos-c11e-c22e.mdx create mode 100644 docs/devices-next/chargers/cupra-charger-connect-2.mdx create mode 100644 docs/devices-next/chargers/cupra-charger-connect.mdx create mode 100644 docs/devices-next/chargers/cupra-charger-pro-2.mdx create mode 100644 docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx create mode 100644 docs/devices-next/chargers/cupra-charger-pro.mdx create mode 100644 docs/devices-next/chargers/dadapower-premium-wallbox.mdx create mode 100644 docs/devices-next/chargers/daheimladen-wallbox.mdx create mode 100644 docs/devices-next/chargers/daikin-homehub-sg-ready.mdx create mode 100644 docs/devices-next/chargers/delta-ac-max-basic.mdx create mode 100644 docs/devices-next/chargers/delta-ac-max-smart.mdx create mode 100644 docs/devices-next/chargers/delta-slim-charger.mdx create mode 100644 docs/devices-next/chargers/delta-ultra-fast-charger.mdx create mode 100644 docs/devices-next/chargers/demo-charger.mdx create mode 100644 docs/devices-next/chargers/e3dc-easy-connect.mdx create mode 100644 docs/devices-next/chargers/easee-charge-core.mdx create mode 100644 docs/devices-next/chargers/easee-charge-lite.mdx create mode 100644 docs/devices-next/chargers/easee-charge.mdx create mode 100644 docs/devices-next/chargers/easee-home.mdx create mode 100644 docs/devices-next/chargers/ebee-wallbox.mdx create mode 100644 docs/devices-next/chargers/echarge-cph1.mdx create mode 100644 docs/devices-next/chargers/echarge-cph2-cpm2.mdx create mode 100644 docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx create mode 100644 docs/devices-next/chargers/edgetech-smart-evse.mdx create mode 100644 docs/devices-next/chargers/eebus-compatible.mdx create mode 100644 docs/devices-next/chargers/elecq-biz.mdx create mode 100644 docs/devices-next/chargers/elecq-home.mdx create mode 100644 docs/devices-next/chargers/elecq-station.mdx create mode 100644 docs/devices-next/chargers/eledio-go.mdx create mode 100644 docs/devices-next/chargers/elli-charger-connect-2.mdx create mode 100644 docs/devices-next/chargers/elli-charger-connect.mdx create mode 100644 docs/devices-next/chargers/elli-charger-pro-2.mdx create mode 100644 docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx create mode 100644 docs/devices-next/chargers/elli-charger-pro.mdx create mode 100644 docs/devices-next/chargers/em2go-home.mdx create mode 100644 docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx create mode 100644 docs/devices-next/chargers/en-ac-ev-charger.mdx create mode 100644 docs/devices-next/chargers/enercab-smart.mdx create mode 100644 docs/devices-next/chargers/ensto-chago-wallbox.mdx create mode 100644 docs/devices-next/chargers/entratek-power-dot-fix.mdx create mode 100644 docs/devices-next/chargers/entratek-power-dot-pro-2.mdx create mode 100644 docs/devices-next/chargers/eon-drive-ebox.mdx create mode 100644 docs/devices-next/chargers/eon-drive-vbox.mdx create mode 100644 docs/devices-next/chargers/esl-walli-light.mdx create mode 100644 docs/devices-next/chargers/esystems-ghostone.mdx create mode 100644 docs/devices-next/chargers/etrel-inch-duo.mdx create mode 100644 docs/devices-next/chargers/etrel-inch.mdx create mode 100644 docs/devices-next/chargers/evbox-elvi.mdx create mode 100644 docs/devices-next/chargers/evbox-livo.mdx create mode 100644 docs/devices-next/chargers/evse-din.mdx create mode 100644 docs/devices-next/chargers/evse-wifi.mdx create mode 100644 docs/devices-next/chargers/free2move-eprowallbox.mdx create mode 100644 docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx create mode 100644 docs/devices-next/chargers/fronius-wattpilot.mdx create mode 100644 docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-gemini.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-home.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-homefix.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-pro.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-v3.mdx create mode 100644 docs/devices-next/chargers/hardybarth-cph1.mdx create mode 100644 docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx create mode 100644 docs/devices-next/chargers/heidelberg-energy-control.mdx create mode 100644 docs/devices-next/chargers/hesotec-esat-ebox.mdx create mode 100644 docs/devices-next/chargers/home-assistant-switch.mdx create mode 100644 docs/devices-next/chargers/homecharge-homecharger.mdx create mode 100644 docs/devices-next/chargers/homematic-ip.mdx create mode 100644 docs/devices-next/chargers/homewizard.mdx create mode 100644 docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx create mode 100644 docs/devices-next/chargers/idm.mdx create mode 100644 docs/devices-next/chargers/index.mdx create mode 100644 docs/devices-next/chargers/innogy-ebox.mdx create mode 100644 docs/devices-next/chargers/inro-pantabox.mdx create mode 100644 docs/devices-next/chargers/juice-charger-me.mdx create mode 100644 docs/devices-next/chargers/junkers-sg-ready.mdx create mode 100644 docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx create mode 100644 docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx create mode 100644 docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx create mode 100644 docs/devices-next/chargers/kermi-x-center-pro.mdx create mode 100644 docs/devices-next/chargers/kontron-solar-charger.mdx create mode 100644 docs/devices-next/chargers/kostal-enector.mdx create mode 100644 docs/devices-next/chargers/kse-wbx16.mdx create mode 100644 docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx create mode 100644 docs/devices-next/chargers/lambda-eu-l-series.mdx create mode 100644 docs/devices-next/chargers/lrt-home-essential.mdx create mode 100644 docs/devices-next/chargers/mennekes-amedio-professional.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-4business-700.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-4you-300.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-4you-500.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-premium.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-professional.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-xtra.mdx create mode 100644 docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx create mode 100644 docs/devices-next/chargers/mennekes-smart-acu.mdx create mode 100644 docs/devices-next/chargers/mennekes-smart-t-acu.mdx create mode 100644 docs/devices-next/chargers/my-pv-ac-elwa-2.mdx create mode 100644 docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx create mode 100644 docs/devices-next/chargers/mystrom-switch.mdx create mode 100644 docs/devices-next/chargers/nrgkick-connect.mdx create mode 100644 docs/devices-next/chargers/nrgkick-gen2.mdx create mode 100644 docs/devices-next/chargers/obo-bettermann-ion.mdx create mode 100644 docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx create mode 100644 docs/devices-next/chargers/openevse.mdx create mode 100644 docs/devices-next/chargers/openwb-pro.mdx create mode 100644 docs/devices-next/chargers/openwb-series2.mdx create mode 100644 docs/devices-next/chargers/openwb-software-2x.mdx create mode 100644 docs/devices-next/chargers/optec-mobility-one.mdx create mode 100644 docs/devices-next/chargers/orbis-viaris.mdx create mode 100644 docs/devices-next/chargers/pc-electric-garo.mdx create mode 100644 docs/devices-next/chargers/peblar-home-home-plus-business.mdx create mode 100644 docs/devices-next/chargers/phoenix-contact-charx.mdx create mode 100644 docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx create mode 100644 docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx create mode 100644 docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx create mode 100644 docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx create mode 100644 docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx create mode 100644 docs/devices-next/chargers/phoenix-contact-ev-ser.mdx create mode 100644 docs/devices-next/chargers/plugchoice.mdx create mode 100644 docs/devices-next/chargers/porsche-mobile-charger-connect.mdx create mode 100644 docs/devices-next/chargers/porsche-mobile-charger-plus.mdx create mode 100644 docs/devices-next/chargers/porsche-wallbox.mdx create mode 100644 docs/devices-next/chargers/pracht-alpha-xt.mdx create mode 100644 docs/devices-next/chargers/pracht-mono-xt.mdx create mode 100644 docs/devices-next/chargers/pracht-pni.mdx create mode 100644 docs/devices-next/chargers/pracht-xt.mdx create mode 100644 docs/devices-next/chargers/pulsares-simplebox.mdx create mode 100644 docs/devices-next/chargers/pulsatrix.mdx create mode 100644 docs/devices-next/chargers/qcells-qhome-edrive-a.mdx create mode 100644 docs/devices-next/chargers/schneider-evlink-pro.mdx create mode 100644 docs/devices-next/chargers/schrack-i-charge-cion.mdx create mode 100644 docs/devices-next/chargers/senec-wallbox-pro-s.mdx create mode 100644 docs/devices-next/chargers/senec-wallbox-pro.mdx create mode 100644 docs/devices-next/chargers/shelly.mdx create mode 100644 docs/devices-next/chargers/siemens-versicharge-gen3.mdx create mode 100644 docs/devices-next/chargers/skoda-charger-connect.mdx create mode 100644 docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx create mode 100644 docs/devices-next/chargers/skoda-charger-pro.mdx create mode 100644 docs/devices-next/chargers/skoda-iv-charger-connect.mdx create mode 100644 docs/devices-next/chargers/sma-ev-charger-echarger.mdx create mode 100644 docs/devices-next/chargers/smartfox-pro-charger.mdx create mode 100644 docs/devices-next/chargers/smartwb.mdx create mode 100644 docs/devices-next/chargers/solaredge-home-ev-charger.mdx create mode 100644 docs/devices-next/chargers/solax-x3-evc.mdx create mode 100644 docs/devices-next/chargers/sonnen-sonnencharger.mdx create mode 100644 docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx create mode 100644 docs/devices-next/chargers/stark-in-strom-easy.mdx create mode 100644 docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx create mode 100644 docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx create mode 100644 docs/devices-next/chargers/sungrow-ac011e-01.mdx create mode 100644 docs/devices-next/chargers/sungrow-ac011e.mdx create mode 100644 docs/devices-next/chargers/tasmota-single-phase.mdx create mode 100644 docs/devices-next/chargers/tecalor-thz-sg-ready.mdx create mode 100644 docs/devices-next/chargers/technisat-technivolt.mdx create mode 100644 docs/devices-next/chargers/tesla-twc3.mdx create mode 100644 docs/devices-next/chargers/tessie.mdx create mode 100644 docs/devices-next/chargers/tigo-go-ev-charger.mdx create mode 100644 docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx create mode 100644 docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx create mode 100644 docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx create mode 100644 docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx create mode 100644 docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx create mode 100644 docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx create mode 100644 docs/devices-next/chargers/ubitricity-heinz.mdx create mode 100644 docs/devices-next/chargers/v2c-trydan.mdx create mode 100644 docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx create mode 100644 docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx create mode 100644 docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx create mode 100644 docs/devices-next/chargers/victron-ev-charging-station.mdx create mode 100644 docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx create mode 100644 docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx create mode 100644 docs/devices-next/chargers/volkswagen-charger-connect-2.mdx create mode 100644 docs/devices-next/chargers/volkswagen-charger-pro-2.mdx create mode 100644 docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx create mode 100644 docs/devices-next/chargers/volkswagen-id-charger-connect.mdx create mode 100644 docs/devices-next/chargers/volkswagen-id-charger-pro.mdx create mode 100644 docs/devices-next/chargers/volt-time-one.mdx create mode 100644 docs/devices-next/chargers/volt-time-source-2.mdx create mode 100644 docs/devices-next/chargers/volt-time-source-2s.mdx create mode 100644 docs/devices-next/chargers/volt-time-source.mdx create mode 100644 docs/devices-next/chargers/wallbe-eco-20s.mdx create mode 100644 docs/devices-next/chargers/wallbe-eco.mdx create mode 100644 docs/devices-next/chargers/wallbe-pro.mdx create mode 100644 docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wallbox-commander-2.mdx create mode 100644 docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wallbox-copper-sb.mdx create mode 100644 docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wallbox-pulsar-max.mdx create mode 100644 docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wallbox-pulsar-plus.mdx create mode 100644 docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx create mode 100644 docs/devices-next/chargers/webasto-live.mdx create mode 100644 docs/devices-next/chargers/webasto-next.mdx create mode 100644 docs/devices-next/chargers/webasto-unite.mdx create mode 100644 docs/devices-next/chargers/weidmuller-ac-smart.mdx create mode 100644 docs/devices-next/chargers/zaptec-go-2.mdx create mode 100644 docs/devices-next/chargers/zaptec-go.mdx create mode 100644 docs/devices-next/chargers/zaptec-pro.mdx create mode 100644 docs/devices-next/chargers/zewotherm-eu-l-series.mdx create mode 100644 docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx create mode 100644 docs/devices-next/meters/a-tronix.mdx create mode 100644 docs/devices-next/meters/abb-a43-a44-b23-b24.mdx create mode 100644 docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx create mode 100644 docs/devices-next/meters/ads-tec-storaxe.mdx create mode 100644 docs/devices-next/meters/alpha-ess-storion-smile.mdx create mode 100644 docs/devices-next/meters/ampere-amperestoragepro.mdx create mode 100644 docs/devices-next/meters/anker-micro-inverter.mdx create mode 100644 docs/devices-next/meters/apsystems-ez1.mdx create mode 100644 docs/devices-next/meters/avm-fritzdect.mdx create mode 100644 docs/devices-next/meters/axitec-axihycon-12-15h.mdx create mode 100644 docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx create mode 100644 docs/devices-next/meters/bgetech-ds100.mdx create mode 100644 docs/devices-next/meters/bgetech-ws100.mdx create mode 100644 docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx create mode 100644 docs/devices-next/meters/bosswerk-micro-inverter.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em110111112.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em24.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em24e1.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em330em340.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em530em540.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-et112.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-et330et340.mdx create mode 100644 docs/devices-next/meters/cfos-powerbrain-meter.mdx create mode 100644 docs/devices-next/meters/demo-battery.mdx create mode 100644 docs/devices-next/meters/demo-meter.mdx create mode 100644 docs/devices-next/meters/deye-3p-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/deye-micro-inverter.mdx create mode 100644 docs/devices-next/meters/deye-storage-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/deye-string-inverter.mdx create mode 100644 docs/devices-next/meters/discovergy.mdx create mode 100644 docs/devices-next/meters/dsmr.mdx create mode 100644 docs/devices-next/meters/dzg-dvh4013.mdx create mode 100644 docs/devices-next/meters/e3dc.mdx create mode 100644 docs/devices-next/meters/eastron-sdm120-modbus.mdx create mode 100644 docs/devices-next/meters/eastron-sdm220230.mdx create mode 100644 docs/devices-next/meters/eastron-sdm630-modbus.mdx create mode 100644 docs/devices-next/meters/eastron-sdm72d-m.mdx create mode 100644 docs/devices-next/meters/eastron-sdm72dm-v2.mdx create mode 100644 docs/devices-next/meters/enphase-iq-envoy.mdx create mode 100644 docs/devices-next/meters/esphome-dlms-meter-austria.mdx create mode 100644 docs/devices-next/meters/esphome-dsmr.mdx create mode 100644 docs/devices-next/meters/fenecon.mdx create mode 100644 docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/fronius-ohmpilot.mdx create mode 100644 docs/devices-next/meters/fronius-primo-gen24-plus.mdx create mode 100644 docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx create mode 100644 docs/devices-next/meters/fronius-solar-api-v1.mdx create mode 100644 docs/devices-next/meters/fronius-symo-gen24-plus.mdx create mode 100644 docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx create mode 100644 docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx create mode 100644 docs/devices-next/meters/ginlong-solis-inverter.mdx create mode 100644 docs/devices-next/meters/go-e-controller.mdx create mode 100644 docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx create mode 100644 docs/devices-next/meters/goodwe-sdtdt-inverter.mdx create mode 100644 docs/devices-next/meters/growatt-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/homematic-ip.mdx create mode 100644 docs/devices-next/meters/homewizard-kwh-meter.mdx create mode 100644 docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx create mode 100644 docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx create mode 100644 docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx create mode 100644 docs/devices-next/meters/huawei-emma.mdx create mode 100644 docs/devices-next/meters/huawei-smartlogger.mdx create mode 100644 docs/devices-next/meters/huawei-sun2000-sdongle.mdx create mode 100644 docs/devices-next/meters/huawei-sun2000.mdx create mode 100644 docs/devices-next/meters/iammeter-wem3080.mdx create mode 100644 docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx create mode 100644 docs/devices-next/meters/igen-tech-solarman-logger.mdx create mode 100644 docs/devices-next/meters/index.mdx create mode 100644 docs/devices-next/meters/inepro-pro380-mod.mdx create mode 100644 docs/devices-next/meters/iometer.mdx create mode 100644 docs/devices-next/meters/janitza-b-series-umg-series.mdx create mode 100644 docs/devices-next/meters/keba-kecontact-e10.mdx create mode 100644 docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx create mode 100644 docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx create mode 100644 docs/devices-next/meters/kostal-piko-hybrid.mdx create mode 100644 docs/devices-next/meters/kostal-piko-legacy.mdx create mode 100644 docs/devices-next/meters/kostal-piko-mp-plus.mdx create mode 100644 docs/devices-next/meters/kostal-piko-piko-ba.mdx create mode 100644 docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx create mode 100644 docs/devices-next/meters/kostal-plenticore-hybrid.mdx create mode 100644 docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx create mode 100644 docs/devices-next/meters/kostal-smart-energy-meter.mdx create mode 100644 docs/devices-next/meters/lg-ess-home-15.mdx create mode 100644 docs/devices-next/meters/lg-ess-home-810.mdx create mode 100644 docs/devices-next/meters/loxone-miniserver.mdx create mode 100644 docs/devices-next/meters/m-tec-energy-butler-gen2.mdx create mode 100644 docs/devices-next/meters/m-tec-energy-butler-gen3.mdx create mode 100644 docs/devices-next/meters/marstek-venus-battery-storage.mdx create mode 100644 docs/devices-next/meters/mhendriks-p1-dongle.mdx create mode 100644 docs/devices-next/meters/my-pv-ac-elwa-2.mdx create mode 100644 docs/devices-next/meters/my-pv-ac-elwa-e.mdx create mode 100644 docs/devices-next/meters/my-pv-acthor.mdx create mode 100644 docs/devices-next/meters/my-pv-wifi-meter.mdx create mode 100644 docs/devices-next/meters/mystrom-switch.mdx create mode 100644 docs/devices-next/meters/openems.mdx create mode 100644 docs/devices-next/meters/orno-or-we-516-or-we-517.mdx create mode 100644 docs/devices-next/meters/p1monitor.mdx create mode 100644 docs/devices-next/meters/plexlog.mdx create mode 100644 docs/devices-next/meters/powerdog.mdx create mode 100644 docs/devices-next/meters/powerfox-poweropti.mdx create mode 100644 docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx create mode 100644 docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx create mode 100644 docs/devices-next/meters/rct-power.mdx create mode 100644 docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx create mode 100644 docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx create mode 100644 docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx create mode 100644 docs/devices-next/meters/saj-r5-series-solar-inverter.mdx create mode 100644 docs/devices-next/meters/sax-homespeicher.mdx create mode 100644 docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx create mode 100644 docs/devices-next/meters/senec-home.mdx create mode 100644 docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx create mode 100644 docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx create mode 100644 docs/devices-next/meters/shelly-3em.mdx create mode 100644 docs/devices-next/meters/shelly-pro-3-em.mdx create mode 100644 docs/devices-next/meters/siemens-7kt1665.mdx create mode 100644 docs/devices-next/meters/siemens-junelight-smart-battery.mdx create mode 100644 docs/devices-next/meters/siemens-pac-2200.mdx create mode 100644 docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx create mode 100644 docs/devices-next/meters/sma-data-manager.mdx create mode 100644 docs/devices-next/meters/sma-energy-meter.mdx create mode 100644 docs/devices-next/meters/sma-inverter-speedwire.mdx create mode 100644 docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx create mode 100644 docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx create mode 100644 docs/devices-next/meters/sma-sunny-home-manager-20.mdx create mode 100644 docs/devices-next/meters/sma-sunny-island-modbus.mdx create mode 100644 docs/devices-next/meters/sma-webbox.mdx create mode 100644 docs/devices-next/meters/sma-wechselrichter-modbus.mdx create mode 100644 docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx create mode 100644 docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx create mode 100644 docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx create mode 100644 docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx create mode 100644 docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx create mode 100644 docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx create mode 100644 docs/devices-next/meters/solaranzeige.mdx create mode 100644 docs/devices-next/meters/solaredge-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/solaredge-inverter.mdx create mode 100644 docs/devices-next/meters/solarlog.mdx create mode 100644 docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx create mode 100644 docs/devices-next/meters/solarmax-solarmax-smt.mdx create mode 100644 docs/devices-next/meters/solarmax-sp-series-inverter.mdx create mode 100644 docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx create mode 100644 docs/devices-next/meters/solarwatt-manager-flex.mdx create mode 100644 docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx create mode 100644 docs/devices-next/meters/solarwatt-myreserve.mdx create mode 100644 docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx create mode 100644 docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx create mode 100644 docs/devices-next/meters/solax-inverter-cloud.mdx create mode 100644 docs/devices-next/meters/solinteng.mdx create mode 100644 docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx create mode 100644 docs/devices-next/meters/sonnen-sonnenbatterie.mdx create mode 100644 docs/devices-next/meters/st-ems.mdx create mode 100644 docs/devices-next/meters/steca-coolcept-flex.mdx create mode 100644 docs/devices-next/meters/sungrow-sg-series-inverter.mdx create mode 100644 docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sunspec-battery-model-124.mdx create mode 100644 docs/devices-next/meters/sunspec-battery-model-802.mdx create mode 100644 docs/devices-next/meters/sunspec-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sunspec-inverter.mdx create mode 100644 docs/devices-next/meters/sunspec-meter.mdx create mode 100644 docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sunsynk-micro-inverter.mdx create mode 100644 docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sunsynk-string-inverter.mdx create mode 100644 docs/devices-next/meters/sunway.mdx create mode 100644 docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx create mode 100644 docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx create mode 100644 docs/devices-next/meters/tasmota-three-phase.mdx create mode 100644 docs/devices-next/meters/tesla-powerwall.mdx create mode 100644 docs/devices-next/meters/tibber-pulse.mdx create mode 100644 docs/devices-next/meters/tp-link-h-series-smart-plug.mdx create mode 100644 docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx create mode 100644 docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx create mode 100644 docs/devices-next/meters/tq-energy-manager-em420.mdx create mode 100644 docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx create mode 100644 docs/devices-next/meters/victron-em24.mdx create mode 100644 docs/devices-next/meters/victron-em24e1.mdx create mode 100644 docs/devices-next/meters/victron-em530em540.mdx create mode 100644 docs/devices-next/meters/victron-energy.mdx create mode 100644 docs/devices-next/meters/victron-et340.mdx create mode 100644 docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx create mode 100644 docs/devices-next/meters/volkszahler-http-api.mdx create mode 100644 docs/devices-next/meters/volkszahler-websocket-api.mdx create mode 100644 docs/devices-next/meters/vzlogger.mdx create mode 100644 docs/devices-next/meters/wago-879-30xx.mdx create mode 100644 docs/devices-next/meters/wattsonic.mdx create mode 100644 docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx create mode 100644 docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx create mode 100644 docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx create mode 100644 docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx create mode 100644 docs/devices-next/meters/youless-energy-monitor.mdx create mode 100644 docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/zendure-hyper-2000.mdx create mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx create mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx create mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer.mdx create mode 100644 docs/devices-next/tariffs/amber-electric.mdx create mode 100644 docs/devices-next/tariffs/awattar.mdx create mode 100644 docs/devices-next/tariffs/electricity-maps-commercial-api.mdx create mode 100644 docs/devices-next/tariffs/electricity-maps-free-api.mdx create mode 100644 docs/devices-next/tariffs/energinet.mdx create mode 100644 docs/devices-next/tariffs/enever.mdx create mode 100644 docs/devices-next/tariffs/entso-e.mdx create mode 100644 docs/devices-next/tariffs/forecastsolar.mdx create mode 100644 docs/devices-next/tariffs/fraunhofer-ise.mdx create mode 100644 docs/devices-next/tariffs/green-grid-compass.mdx create mode 100644 docs/devices-next/tariffs/groupe-e-vario-plus.mdx create mode 100644 docs/devices-next/tariffs/grunstromindex.mdx create mode 100644 docs/devices-next/tariffs/index.mdx create mode 100644 docs/devices-next/tariffs/national-grid-eso.mdx create mode 100644 docs/devices-next/tariffs/nordpool-spot-prices.mdx create mode 100644 docs/devices-next/tariffs/octopus-energy-api.mdx create mode 100644 docs/devices-next/tariffs/octopus-energy-product-code.mdx create mode 100644 docs/devices-next/tariffs/open-meteo.mdx create mode 100644 docs/devices-next/tariffs/ostrom.mdx create mode 100644 docs/devices-next/tariffs/pun-orario.mdx create mode 100644 docs/devices-next/tariffs/smartenergy-smartcontrol.mdx create mode 100644 docs/devices-next/tariffs/solcast.mdx create mode 100644 docs/devices-next/tariffs/spotty-energie.mdx create mode 100644 docs/devices-next/tariffs/tibber.mdx create mode 100644 docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx create mode 100644 docs/devices-next/vehicles/aiways.mdx create mode 100644 docs/devices-next/vehicles/audi.mdx create mode 100644 docs/devices-next/vehicles/bmw.mdx create mode 100644 docs/devices-next/vehicles/citroen.mdx create mode 100644 docs/devices-next/vehicles/dacia.mdx create mode 100644 docs/devices-next/vehicles/ds.mdx create mode 100644 docs/devices-next/vehicles/evnotify.mdx create mode 100644 docs/devices-next/vehicles/fiat.mdx create mode 100644 docs/devices-next/vehicles/ford.mdx create mode 100644 docs/devices-next/vehicles/generic-vehicle-without-api.mdx create mode 100644 docs/devices-next/vehicles/hyundai-bluelink.mdx create mode 100644 docs/devices-next/vehicles/index.mdx create mode 100644 docs/devices-next/vehicles/iobrokerbmw.mdx create mode 100644 docs/devices-next/vehicles/iso15118.mdx create mode 100644 docs/devices-next/vehicles/jeep.mdx create mode 100644 docs/devices-next/vehicles/kia-bluelink.mdx create mode 100644 docs/devices-next/vehicles/mercedes-benz.mdx create mode 100644 docs/devices-next/vehicles/mg.mdx create mode 100644 docs/devices-next/vehicles/mg2mqtt.mdx create mode 100644 docs/devices-next/vehicles/mini.mdx create mode 100644 docs/devices-next/vehicles/mz2mqtt.mdx create mode 100644 docs/devices-next/vehicles/nissan-ariya.mdx create mode 100644 docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx create mode 100644 docs/devices-next/vehicles/nissan-leaf.mdx create mode 100644 docs/devices-next/vehicles/niu-e-scooter.mdx create mode 100644 docs/devices-next/vehicles/opel.mdx create mode 100644 docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx create mode 100644 docs/devices-next/vehicles/peugeot.mdx create mode 100644 docs/devices-next/vehicles/polestar.mdx create mode 100644 docs/devices-next/vehicles/psa-car-controller.mdx create mode 100644 docs/devices-next/vehicles/renault.mdx create mode 100644 docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx create mode 100644 docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx create mode 100644 docs/devices-next/vehicles/skoda-enyaq.mdx create mode 100644 docs/devices-next/vehicles/smart-eq.mdx create mode 100644 docs/devices-next/vehicles/smart.mdx create mode 100644 docs/devices-next/vehicles/tesla-ble.mdx create mode 100644 docs/devices-next/vehicles/tesla.mdx create mode 100644 docs/devices-next/vehicles/teslalogger.mdx create mode 100644 docs/devices-next/vehicles/teslamate.mdx create mode 100644 docs/devices-next/vehicles/tessie.mdx create mode 100644 docs/devices-next/vehicles/toyota.mdx create mode 100644 docs/devices-next/vehicles/tronity.mdx create mode 100644 docs/devices-next/vehicles/volkswagen-we-connect-id.mdx create mode 100644 docs/devices-next/vehicles/volvo.mdx create mode 100644 docs/devices-next/vehicles/volvo2mqtt.mdx create mode 100644 docs/devices-next/vehicles/zero-motorcycles.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx create mode 100644 src/components/DeviceCard.module.css create mode 100644 src/components/DeviceCard.tsx create mode 100644 src/generateDevicesNext.ts create mode 100644 static/img/devices/placeholder.svg create mode 100644 tsconfig.json diff --git a/docs/devices-next/chargers/abb-terra-ac.mdx b/docs/devices-next/chargers/abb-terra-ac.mdx new file mode 100644 index 0000000000..610d44db70 --- /dev/null +++ b/docs/devices-next/chargers/abb-terra-ac.mdx @@ -0,0 +1,36 @@ +--- +title: ABB Terra AC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB Terra AC + + + +https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/abl-em4-sbcx.mdx b/docs/devices-next/chargers/abl-em4-sbcx.mdx new file mode 100644 index 0000000000..927c8ff2bf --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-sbcx.mdx @@ -0,0 +1,38 @@ +--- +title: ABL eM4 (SBCx) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 (SBCx) + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/abl-emh1.mdx b/docs/devices-next/chargers/abl-emh1.mdx new file mode 100644 index 0000000000..d31bf40a9e --- /dev/null +++ b/docs/devices-next/chargers/abl-emh1.mdx @@ -0,0 +1,36 @@ +--- +title: ABL eMH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH1 + + + + + + + diff --git a/docs/devices-next/chargers/abl-emh2.mdx b/docs/devices-next/chargers/abl-emh2.mdx new file mode 100644 index 0000000000..69c6d982e8 --- /dev/null +++ b/docs/devices-next/chargers/abl-emh2.mdx @@ -0,0 +1,36 @@ +--- +title: ABL eMH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH2 + + + + + + + diff --git a/docs/devices-next/chargers/abl-sursum-emh2.mdx b/docs/devices-next/chargers/abl-sursum-emh2.mdx new file mode 100644 index 0000000000..78016cb9be --- /dev/null +++ b/docs/devices-next/chargers/abl-sursum-emh2.mdx @@ -0,0 +1,33 @@ +--- +title: ABL Sursum eMH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL Sursum eMH2 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/abl-sursum-emh3.mdx b/docs/devices-next/chargers/abl-sursum-emh3.mdx new file mode 100644 index 0000000000..4fae7d9112 --- /dev/null +++ b/docs/devices-next/chargers/abl-sursum-emh3.mdx @@ -0,0 +1,33 @@ +--- +title: ABL Sursum eMH3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL Sursum eMH3 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/abl-sursum-emh4.mdx b/docs/devices-next/chargers/abl-sursum-emh4.mdx new file mode 100644 index 0000000000..99997e002f --- /dev/null +++ b/docs/devices-next/chargers/abl-sursum-emh4.mdx @@ -0,0 +1,33 @@ +--- +title: ABL Sursum eMH4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL Sursum eMH4 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/alfen-eve.mdx b/docs/devices-next/chargers/alfen-eve.mdx new file mode 100644 index 0000000000..2e921d2a97 --- /dev/null +++ b/docs/devices-next/chargers/alfen-eve.mdx @@ -0,0 +1,33 @@ +--- +title: Alfen Eve +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alfen Eve + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx new file mode 100644 index 0000000000..6c4d67a324 --- /dev/null +++ b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -0,0 +1,38 @@ +--- +title: Alphatec Ladesäule Twin +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Ladesäule Twin + + + +The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. + + + + + + diff --git a/docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx b/docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx new file mode 100644 index 0000000000..7e9e4b416e --- /dev/null +++ b/docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx @@ -0,0 +1,38 @@ +--- +title: Alphatec Wallbox Mini, Power +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Wallbox Mini, Power + + + +The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. + + + + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx b/docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx new file mode 100644 index 0000000000..6a4d20c236 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx @@ -0,0 +1,28 @@ +--- +title: Amperfied Wallbox connect.business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.business + + + + + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx b/docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx new file mode 100644 index 0000000000..a0db0963ae --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx @@ -0,0 +1,28 @@ +--- +title: Amperfied Wallbox connect.home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.home + + + + + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx b/docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx new file mode 100644 index 0000000000..257e44333f --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx @@ -0,0 +1,28 @@ +--- +title: Amperfied Wallbox connect.solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.solar + + + + + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx new file mode 100644 index 0000000000..d619a95a86 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -0,0 +1,38 @@ +--- +title: Amperfied Wallbox Energy Control +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox Energy Control + + + +Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). + + + + + + diff --git a/docs/devices-next/chargers/ampure-live.mdx b/docs/devices-next/chargers/ampure-live.mdx new file mode 100644 index 0000000000..b08adcbcbd --- /dev/null +++ b/docs/devices-next/chargers/ampure-live.mdx @@ -0,0 +1,31 @@ +--- +title: Ampure Live +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampure Live + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/ampure-next.mdx b/docs/devices-next/chargers/ampure-next.mdx new file mode 100644 index 0000000000..13ec4a7ed7 --- /dev/null +++ b/docs/devices-next/chargers/ampure-next.mdx @@ -0,0 +1,27 @@ +--- +title: Ampure NEXT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampure NEXT + + + +Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. + + + + + + diff --git a/docs/devices-next/chargers/ampure-unite.mdx b/docs/devices-next/chargers/ampure-unite.mdx new file mode 100644 index 0000000000..6213c1998a --- /dev/null +++ b/docs/devices-next/chargers/ampure-unite.mdx @@ -0,0 +1,31 @@ +--- +title: Ampure Unite +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampure Unite + + + +1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. + + + + + + diff --git a/docs/devices-next/chargers/audi-audi-wallbox-pro.mdx b/docs/devices-next/chargers/audi-audi-wallbox-pro.mdx new file mode 100644 index 0000000000..4794b9c8f4 --- /dev/null +++ b/docs/devices-next/chargers/audi-audi-wallbox-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Audi Audi Wallbox pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi Audi Wallbox pro + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + + + diff --git a/docs/devices-next/chargers/audi-wallbox-plus.mdx b/docs/devices-next/chargers/audi-wallbox-plus.mdx new file mode 100644 index 0000000000..f7ad4d001f --- /dev/null +++ b/docs/devices-next/chargers/audi-wallbox-plus.mdx @@ -0,0 +1,31 @@ +--- +title: Audi Wallbox plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi Wallbox plus + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + + + + diff --git a/docs/devices-next/chargers/autel-ac-compact.mdx b/docs/devices-next/chargers/autel-ac-compact.mdx new file mode 100644 index 0000000000..c2b7b6a680 --- /dev/null +++ b/docs/devices-next/chargers/autel-ac-compact.mdx @@ -0,0 +1,41 @@ +--- +title: AUTEL AC Compact +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AUTEL AC Compact + + + +Setup Guide: +* In the Autel Charge app, click on “OCPP Server” +* In the search bar type “Custom” and select it. +* Server URL: ws://[evcc-address]:8887/ (local network connection) +* Charger ID: Leave empty (for use the serial number) or set custom value which is reused in configuration as *stationid* +* Authorisation Key: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/autel-ac-maxicharger.mdx b/docs/devices-next/chargers/autel-ac-maxicharger.mdx new file mode 100644 index 0000000000..ed565a398b --- /dev/null +++ b/docs/devices-next/chargers/autel-ac-maxicharger.mdx @@ -0,0 +1,41 @@ +--- +title: AUTEL AC MaxiCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AUTEL AC MaxiCharger + + + +Setup Guide: +* In the Autel Charge app, click on “OCPP Server” +* In the search bar type “Custom” and select it. +* Server URL: ws://[evcc-address]:8887/ (local network connection) +* Charger ID: Leave empty (for use the serial number) or set custom value which is reused in configuration as *stationid* +* Authorisation Key: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/autoaid-business-wallbox.mdx b/docs/devices-next/chargers/autoaid-business-wallbox.mdx new file mode 100644 index 0000000000..f3ebdcd934 --- /dev/null +++ b/docs/devices-next/chargers/autoaid-business-wallbox.mdx @@ -0,0 +1,33 @@ +--- +title: Autoaid Business Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Autoaid Business Wallbox + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx new file mode 100644 index 0000000000..f1197df4e4 --- /dev/null +++ b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -0,0 +1,33 @@ +--- +title: Autoaid Intelligent Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Autoaid Intelligent Wallbox + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/avm-fritzdect.mdx b/docs/devices-next/chargers/avm-fritzdect.mdx new file mode 100644 index 0000000000..512b4eaa37 --- /dev/null +++ b/docs/devices-next/chargers/avm-fritzdect.mdx @@ -0,0 +1,36 @@ +--- +title: AVM FritzDECT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/fritzdect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AVM FritzDECT + + + + + diff --git a/docs/devices-next/chargers/bender-cc612.mdx b/docs/devices-next/chargers/bender-cc612.mdx new file mode 100644 index 0000000000..6508279477 --- /dev/null +++ b/docs/devices-next/chargers/bender-cc612.mdx @@ -0,0 +1,31 @@ +--- +title: Bender CC612 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender CC612 + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/bender-cc613.mdx b/docs/devices-next/chargers/bender-cc613.mdx new file mode 100644 index 0000000000..3ee32ed758 --- /dev/null +++ b/docs/devices-next/chargers/bender-cc613.mdx @@ -0,0 +1,31 @@ +--- +title: Bender CC613 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender CC613 + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/bender-icc1314.mdx b/docs/devices-next/chargers/bender-icc1314.mdx new file mode 100644 index 0000000000..4f6fc17647 --- /dev/null +++ b/docs/devices-next/chargers/bender-icc1314.mdx @@ -0,0 +1,31 @@ +--- +title: Bender ICC1314 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender ICC1314 + + + +The configuration option 'External Energy Management' must be enabled. + + + + + + diff --git a/docs/devices-next/chargers/bender-icc1324.mdx b/docs/devices-next/chargers/bender-icc1324.mdx new file mode 100644 index 0000000000..1b77bdbae2 --- /dev/null +++ b/docs/devices-next/chargers/bender-icc1324.mdx @@ -0,0 +1,31 @@ +--- +title: Bender ICC1324 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender ICC1324 + + + +The configuration option 'External Energy Management' must be enabled. + + + + + + diff --git a/docs/devices-next/chargers/bmw-i-wallbox.mdx b/docs/devices-next/chargers/bmw-i-wallbox.mdx new file mode 100644 index 0000000000..b07c221f63 --- /dev/null +++ b/docs/devices-next/chargers/bmw-i-wallbox.mdx @@ -0,0 +1,41 @@ +--- +title: BMW i Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BMW i Wallbox + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + + + diff --git a/docs/devices-next/chargers/bosch-sg-ready.mdx b/docs/devices-next/chargers/bosch-sg-ready.mdx new file mode 100644 index 0000000000..0377aaafd1 --- /dev/null +++ b/docs/devices-next/chargers/bosch-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Bosch SG Ready +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bosch SG Ready + + + +Integrated via [EMSESP](https://emsesp.org/) + + + + diff --git a/docs/devices-next/chargers/bosch-x-change.mdx b/docs/devices-next/chargers/bosch-x-change.mdx new file mode 100644 index 0000000000..11131a1911 --- /dev/null +++ b/docs/devices-next/chargers/bosch-x-change.mdx @@ -0,0 +1,28 @@ +--- +title: Bösch x-change +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bösch x-change + + + + + diff --git a/docs/devices-next/chargers/buderus-sg-ready.mdx b/docs/devices-next/chargers/buderus-sg-ready.mdx new file mode 100644 index 0000000000..f9585b1b71 --- /dev/null +++ b/docs/devices-next/chargers/buderus-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Buderus SG Ready +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Buderus SG Ready + + + +Integrated via [EMSESP](https://emsesp.org/) + + + + diff --git a/docs/devices-next/chargers/cfos-power-brain-solar.mdx b/docs/devices-next/chargers/cfos-power-brain-solar.mdx new file mode 100644 index 0000000000..4942eb8304 --- /dev/null +++ b/docs/devices-next/chargers/cfos-power-brain-solar.mdx @@ -0,0 +1,29 @@ +--- +title: cFos Power Brain Solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# cFos Power Brain Solar + + + +S0 meters must be configured separately as charge meter. +Phase switching is only available with the Solar variant and must be enabled by the user: +1) Home -> disable Load Balancing (Monitoring Mode) +2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) + + + + + + diff --git a/docs/devices-next/chargers/cfos-power-brain.mdx b/docs/devices-next/chargers/cfos-power-brain.mdx new file mode 100644 index 0000000000..7102e5d0bd --- /dev/null +++ b/docs/devices-next/chargers/cfos-power-brain.mdx @@ -0,0 +1,29 @@ +--- +title: cFos Power Brain +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# cFos Power Brain + + + +S0 meters must be configured separately as charge meter. +Phase switching is only available with the Solar variant and must be enabled by the user: +1) Home -> disable Load Balancing (Monitoring Mode) +2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) + + + + + + diff --git a/docs/devices-next/chargers/charge-amps-halo.mdx b/docs/devices-next/chargers/charge-amps-halo.mdx new file mode 100644 index 0000000000..82cfbb5cbb --- /dev/null +++ b/docs/devices-next/chargers/charge-amps-halo.mdx @@ -0,0 +1,33 @@ +--- +title: Charge Amps Halo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-chargeamps.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Charge Amps Halo + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-chargeamps + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/compleo-ebox.mdx b/docs/devices-next/chargers/compleo-ebox.mdx new file mode 100644 index 0000000000..c09694e8f9 --- /dev/null +++ b/docs/devices-next/chargers/compleo-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: Compleo eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Compleo eBox + + + + + + + diff --git a/docs/devices-next/chargers/cubos-c11e-c22e.mdx b/docs/devices-next/chargers/cubos-c11e-c22e.mdx new file mode 100644 index 0000000000..08907f488c --- /dev/null +++ b/docs/devices-next/chargers/cubos-c11e-c22e.mdx @@ -0,0 +1,31 @@ +--- +title: CUBOS C11E, C22E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CUBOS C11E, C22E + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/cupra-charger-connect-2.mdx b/docs/devices-next/chargers/cupra-charger-connect-2.mdx new file mode 100644 index 0000000000..687e757119 --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-connect-2.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Connect 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Connect 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/cupra-charger-connect.mdx b/docs/devices-next/chargers/cupra-charger-connect.mdx new file mode 100644 index 0000000000..1feebf1fc3 --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-connect.mdx @@ -0,0 +1,31 @@ +--- +title: Cupra Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Connect + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + + + + diff --git a/docs/devices-next/chargers/cupra-charger-pro-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-2.mdx new file mode 100644 index 0000000000..1160e8afe6 --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-pro-2.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Pro 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx new file mode 100644 index 0000000000..dd497ad9e8 --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Pro Eichrecht 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Pro Eichrecht 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/cupra-charger-pro.mdx b/docs/devices-next/chargers/cupra-charger-pro.mdx new file mode 100644 index 0000000000..71975f01ef --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Pro + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + + + diff --git a/docs/devices-next/chargers/dadapower-premium-wallbox.mdx b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx new file mode 100644 index 0000000000..0d871b2d82 --- /dev/null +++ b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -0,0 +1,28 @@ +--- +title: Dadapower Premium Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/dadapower.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Dadapower Premium Wallbox + + + + + + + diff --git a/docs/devices-next/chargers/daheimladen-wallbox.mdx b/docs/devices-next/chargers/daheimladen-wallbox.mdx new file mode 100644 index 0000000000..94b16f8c4e --- /dev/null +++ b/docs/devices-next/chargers/daheimladen-wallbox.mdx @@ -0,0 +1,25 @@ +--- +title: DaheimLaden Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daheimladen-mb.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DaheimLaden Wallbox + + + +Wallbox must be operated with a recent firmware including Modbus support. Furthermore, “Nachladen” (Smart) or “RSDA” (Touch) must be activated in settings. + + + + diff --git a/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx new file mode 100644 index 0000000000..dc34312833 --- /dev/null +++ b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Daikin HomeHub (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daikin-homehub.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Daikin HomeHub (SG Ready) + + + + + diff --git a/docs/devices-next/chargers/delta-ac-max-basic.mdx b/docs/devices-next/chargers/delta-ac-max-basic.mdx new file mode 100644 index 0000000000..0899099e7a --- /dev/null +++ b/docs/devices-next/chargers/delta-ac-max-basic.mdx @@ -0,0 +1,64 @@ +--- +title: Delta AC Max Basic +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta AC Max Basic + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/delta-ac-max-smart.mdx b/docs/devices-next/chargers/delta-ac-max-smart.mdx new file mode 100644 index 0000000000..e35400f760 --- /dev/null +++ b/docs/devices-next/chargers/delta-ac-max-smart.mdx @@ -0,0 +1,64 @@ +--- +title: Delta AC MAX Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta AC MAX Smart + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/delta-slim-charger.mdx b/docs/devices-next/chargers/delta-slim-charger.mdx new file mode 100644 index 0000000000..d1af7483e7 --- /dev/null +++ b/docs/devices-next/chargers/delta-slim-charger.mdx @@ -0,0 +1,64 @@ +--- +title: Delta SLIM Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta SLIM Charger + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/delta-ultra-fast-charger.mdx b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx new file mode 100644 index 0000000000..e8e290aaac --- /dev/null +++ b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -0,0 +1,64 @@ +--- +title: Delta Ultra Fast Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta Ultra Fast Charger + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/demo-charger.mdx b/docs/devices-next/chargers/demo-charger.mdx new file mode 100644 index 0000000000..19a91fd024 --- /dev/null +++ b/docs/devices-next/chargers/demo-charger.mdx @@ -0,0 +1,34 @@ +--- +title: Demo charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/demo-charger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Demo charger + + + +For demonstration purposes. Charger with a fixed set of values. + + + + diff --git a/docs/devices-next/chargers/e3dc-easy-connect.mdx b/docs/devices-next/chargers/e3dc-easy-connect.mdx new file mode 100644 index 0000000000..5d17d6537a --- /dev/null +++ b/docs/devices-next/chargers/e3dc-easy-connect.mdx @@ -0,0 +1,31 @@ +--- +title: E3/DC Easy Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC Easy Connect + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/easee-charge-core.mdx b/docs/devices-next/chargers/easee-charge-core.mdx new file mode 100644 index 0000000000..948df12c5a --- /dev/null +++ b/docs/devices-next/chargers/easee-charge-core.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Charge Core +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Charge Core + + + + + + + diff --git a/docs/devices-next/chargers/easee-charge-lite.mdx b/docs/devices-next/chargers/easee-charge-lite.mdx new file mode 100644 index 0000000000..aa3e7ef412 --- /dev/null +++ b/docs/devices-next/chargers/easee-charge-lite.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Charge Lite +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Charge Lite + + + + + + + diff --git a/docs/devices-next/chargers/easee-charge.mdx b/docs/devices-next/chargers/easee-charge.mdx new file mode 100644 index 0000000000..fee1d7ee64 --- /dev/null +++ b/docs/devices-next/chargers/easee-charge.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Charge +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Charge + + + + + + + diff --git a/docs/devices-next/chargers/easee-home.mdx b/docs/devices-next/chargers/easee-home.mdx new file mode 100644 index 0000000000..69326be221 --- /dev/null +++ b/docs/devices-next/chargers/easee-home.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Home + + + + + + + diff --git a/docs/devices-next/chargers/ebee-wallbox.mdx b/docs/devices-next/chargers/ebee-wallbox.mdx new file mode 100644 index 0000000000..36e31cb966 --- /dev/null +++ b/docs/devices-next/chargers/ebee-wallbox.mdx @@ -0,0 +1,31 @@ +--- +title: Ebee Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ebee Wallbox + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/echarge-cph1.mdx b/docs/devices-next/chargers/echarge-cph1.mdx new file mode 100644 index 0000000000..6931953a1a --- /dev/null +++ b/docs/devices-next/chargers/echarge-cph1.mdx @@ -0,0 +1,31 @@ +--- +title: echarge cPH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPH1 + + + +Charge mode must be configured as `manual` + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/echarge-cph2-cpm2.mdx b/docs/devices-next/chargers/echarge-cph2-cpm2.mdx new file mode 100644 index 0000000000..32d6f23561 --- /dev/null +++ b/docs/devices-next/chargers/echarge-cph2-cpm2.mdx @@ -0,0 +1,23 @@ +--- +title: echarge cPH2, cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPH2, cPμ2 + + + + + + + diff --git a/docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx b/docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx new file mode 100644 index 0000000000..2b99761d93 --- /dev/null +++ b/docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx @@ -0,0 +1,39 @@ +--- +title: EcoHarmony EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EcoHarmony EVSE EPC 2.0 Plus + + + + + diff --git a/docs/devices-next/chargers/edgetech-smart-evse.mdx b/docs/devices-next/chargers/edgetech-smart-evse.mdx new file mode 100644 index 0000000000..d9f3b3f146 --- /dev/null +++ b/docs/devices-next/chargers/edgetech-smart-evse.mdx @@ -0,0 +1,33 @@ +--- +title: Edgetech Smart EVSE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartevse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Edgetech Smart EVSE + + + + + diff --git a/docs/devices-next/chargers/eebus-compatible.mdx b/docs/devices-next/chargers/eebus-compatible.mdx new file mode 100644 index 0000000000..13ee920779 --- /dev/null +++ b/docs/devices-next/chargers/eebus-compatible.mdx @@ -0,0 +1,22 @@ +--- +title: EEBUS compatible +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eebus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EEBUS compatible + + + + + diff --git a/docs/devices-next/chargers/elecq-biz.mdx b/docs/devices-next/chargers/elecq-biz.mdx new file mode 100644 index 0000000000..afc8e3e56a --- /dev/null +++ b/docs/devices-next/chargers/elecq-biz.mdx @@ -0,0 +1,33 @@ +--- +title: Elecq Biz +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elecq Biz + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/elecq-home.mdx b/docs/devices-next/chargers/elecq-home.mdx new file mode 100644 index 0000000000..ab4b3618b7 --- /dev/null +++ b/docs/devices-next/chargers/elecq-home.mdx @@ -0,0 +1,33 @@ +--- +title: Elecq Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elecq Home + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/elecq-station.mdx b/docs/devices-next/chargers/elecq-station.mdx new file mode 100644 index 0000000000..c11adaef5c --- /dev/null +++ b/docs/devices-next/chargers/elecq-station.mdx @@ -0,0 +1,33 @@ +--- +title: Elecq Station +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elecq Station + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/eledio-go.mdx b/docs/devices-next/chargers/eledio-go.mdx new file mode 100644 index 0000000000..f5b4da2250 --- /dev/null +++ b/docs/devices-next/chargers/eledio-go.mdx @@ -0,0 +1,36 @@ +--- +title: eledio go +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# eledio go + + + +https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/elli-charger-connect-2.mdx b/docs/devices-next/chargers/elli-charger-connect-2.mdx new file mode 100644 index 0000000000..7b1040423f --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-connect-2.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Connect 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Connect 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/elli-charger-connect.mdx b/docs/devices-next/chargers/elli-charger-connect.mdx new file mode 100644 index 0000000000..fcdae5d8ca --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-connect.mdx @@ -0,0 +1,31 @@ +--- +title: Elli Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Connect + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + + + + diff --git a/docs/devices-next/chargers/elli-charger-pro-2.mdx b/docs/devices-next/chargers/elli-charger-pro-2.mdx new file mode 100644 index 0000000000..08027242a5 --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-pro-2.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Pro 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx new file mode 100644 index 0000000000..7130dfa9bc --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Pro Eichrecht 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Pro Eichrecht 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/elli-charger-pro.mdx b/docs/devices-next/chargers/elli-charger-pro.mdx new file mode 100644 index 0000000000..f02937069c --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Pro + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + + + diff --git a/docs/devices-next/chargers/em2go-home.mdx b/docs/devices-next/chargers/em2go-home.mdx new file mode 100644 index 0000000000..533ae90c11 --- /dev/null +++ b/docs/devices-next/chargers/em2go-home.mdx @@ -0,0 +1,24 @@ +--- +title: EM2GO Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go-home.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EM2GO Home + + + +Requires FW Version >= E3C_V1.1. mA regulation requires FW version >= E3C_V1.3. + + + + diff --git a/docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx b/docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx new file mode 100644 index 0000000000..95ac09a448 --- /dev/null +++ b/docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx @@ -0,0 +1,29 @@ +--- +title: EM2GO Pro Power, OCPP/ONC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EM2GO Pro Power, OCPP/ONC + + + +Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15) + + + + diff --git a/docs/devices-next/chargers/en-ac-ev-charger.mdx b/docs/devices-next/chargers/en-ac-ev-charger.mdx new file mode 100644 index 0000000000..f4e3854946 --- /dev/null +++ b/docs/devices-next/chargers/en-ac-ev-charger.mdx @@ -0,0 +1,33 @@ +--- +title: EN+ AC EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EN+ AC EV Charger + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/enercab-smart.mdx b/docs/devices-next/chargers/enercab-smart.mdx new file mode 100644 index 0000000000..0729ea0aa3 --- /dev/null +++ b/docs/devices-next/chargers/enercab-smart.mdx @@ -0,0 +1,36 @@ +--- +title: enercab smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# enercab smart + + + +https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/ensto-chago-wallbox.mdx b/docs/devices-next/chargers/ensto-chago-wallbox.mdx new file mode 100644 index 0000000000..c59d4ed91f --- /dev/null +++ b/docs/devices-next/chargers/ensto-chago-wallbox.mdx @@ -0,0 +1,31 @@ +--- +title: Ensto Chago Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ensto Chago Wallbox + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/entratek-power-dot-fix.mdx b/docs/devices-next/chargers/entratek-power-dot-fix.mdx new file mode 100644 index 0000000000..b6913b5778 --- /dev/null +++ b/docs/devices-next/chargers/entratek-power-dot-fix.mdx @@ -0,0 +1,33 @@ +--- +title: EntraTek Power Dot Fix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EntraTek Power Dot Fix + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx new file mode 100644 index 0000000000..fae5d66726 --- /dev/null +++ b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -0,0 +1,33 @@ +--- +title: EntraTek Power Dot Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EntraTek Power Dot Pro 2 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/eon-drive-ebox.mdx b/docs/devices-next/chargers/eon-drive-ebox.mdx new file mode 100644 index 0000000000..9fa1d98fbf --- /dev/null +++ b/docs/devices-next/chargers/eon-drive-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: E.ON Drive eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive eBox + + + + + + + diff --git a/docs/devices-next/chargers/eon-drive-vbox.mdx b/docs/devices-next/chargers/eon-drive-vbox.mdx new file mode 100644 index 0000000000..63221599d7 --- /dev/null +++ b/docs/devices-next/chargers/eon-drive-vbox.mdx @@ -0,0 +1,31 @@ +--- +title: E.ON Drive vBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive vBox + + + +1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. + + + + + + diff --git a/docs/devices-next/chargers/esl-walli-light.mdx b/docs/devices-next/chargers/esl-walli-light.mdx new file mode 100644 index 0000000000..270671e5df --- /dev/null +++ b/docs/devices-next/chargers/esl-walli-light.mdx @@ -0,0 +1,31 @@ +--- +title: ESL Walli LIGHT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ESL Walli LIGHT + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/esystems-ghostone.mdx b/docs/devices-next/chargers/esystems-ghostone.mdx new file mode 100644 index 0000000000..778d9f08a5 --- /dev/null +++ b/docs/devices-next/chargers/esystems-ghostone.mdx @@ -0,0 +1,29 @@ +--- +title: eSystems ghostONE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# eSystems ghostONE + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/etrel-inch-duo.mdx b/docs/devices-next/chargers/etrel-inch-duo.mdx new file mode 100644 index 0000000000..2c26c9cf8d --- /dev/null +++ b/docs/devices-next/chargers/etrel-inch-duo.mdx @@ -0,0 +1,33 @@ +--- +title: Etrel INCH Duo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel-duo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Etrel INCH Duo + + + +The charger must be switched to "Power" charging mode. + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/etrel-inch.mdx b/docs/devices-next/chargers/etrel-inch.mdx new file mode 100644 index 0000000000..5b58e5c7b1 --- /dev/null +++ b/docs/devices-next/chargers/etrel-inch.mdx @@ -0,0 +1,27 @@ +--- +title: Etrel INCH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Etrel INCH + + + +The charger must be switched to "Power" charging mode. + + + + + + diff --git a/docs/devices-next/chargers/evbox-elvi.mdx b/docs/devices-next/chargers/evbox-elvi.mdx new file mode 100644 index 0000000000..dcf125e4e9 --- /dev/null +++ b/docs/devices-next/chargers/evbox-elvi.mdx @@ -0,0 +1,34 @@ +--- +title: EVBox Elvi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-evbox-elvi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVBox Elvi + + + +:8887/. Most charging stations automatically add the ID internally. (optional) + meter: true # optional`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-evbox-elvi + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + meter: true # optional + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/evbox-livo.mdx b/docs/devices-next/chargers/evbox-livo.mdx new file mode 100644 index 0000000000..f4c0b4f6e3 --- /dev/null +++ b/docs/devices-next/chargers/evbox-livo.mdx @@ -0,0 +1,25 @@ +--- +title: EVBox Livo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/livo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVBox Livo + + + +The device requires a fixed IP addres. It's important to set up EEBus first. After setting up EEBus the charger will recognize evcc as a HEMS device on the network. Please use the installer tool to select evcc as HEMS. After this has been done, copy the given SKI from the Install app and add it to your yaml. + + + + diff --git a/docs/devices-next/chargers/evse-din.mdx b/docs/devices-next/chargers/evse-din.mdx new file mode 100644 index 0000000000..66343afe2a --- /dev/null +++ b/docs/devices-next/chargers/evse-din.mdx @@ -0,0 +1,33 @@ +--- +title: EVSE DIN +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVSE DIN + + + + + diff --git a/docs/devices-next/chargers/evse-wifi.mdx b/docs/devices-next/chargers/evse-wifi.mdx new file mode 100644 index 0000000000..d661e95728 --- /dev/null +++ b/docs/devices-next/chargers/evse-wifi.mdx @@ -0,0 +1,21 @@ +--- +title: EVSE-WiFi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evsewifi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVSE-WiFi + + + + + diff --git a/docs/devices-next/chargers/free2move-eprowallbox.mdx b/docs/devices-next/chargers/free2move-eprowallbox.mdx new file mode 100644 index 0000000000..fa1915c2c6 --- /dev/null +++ b/docs/devices-next/chargers/free2move-eprowallbox.mdx @@ -0,0 +1,35 @@ +--- +title: Free2Move eProWallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Free2Move eProWallbox + + + + + + + diff --git a/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx new file mode 100644 index 0000000000..8c593c8999 --- /dev/null +++ b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -0,0 +1,33 @@ +--- +title: Free2move eSolutions eProWallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-esolutions.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Free2move eSolutions eProWallbox + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-esolutions + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/fronius-wattpilot.mdx b/docs/devices-next/chargers/fronius-wattpilot.mdx new file mode 100644 index 0000000000..0e46a80065 --- /dev/null +++ b/docs/devices-next/chargers/fronius-wattpilot.mdx @@ -0,0 +1,33 @@ +--- +title: Fronius Wattpilot +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Wattpilot + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx b/docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx new file mode 100644 index 0000000000..3f640dca66 --- /dev/null +++ b/docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx @@ -0,0 +1,31 @@ +--- +title: Garo GLB, GLB+, LS4, LS4 compact +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo GLB, GLB+, LS4, LS4 compact + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/go-e-charger-gemini.mdx b/docs/devices-next/chargers/go-e-charger-gemini.mdx new file mode 100644 index 0000000000..6576568234 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-gemini.mdx @@ -0,0 +1,33 @@ +--- +title: go-e Charger Gemini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger Gemini + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/go-e-charger-home.mdx b/docs/devices-next/chargers/go-e-charger-home.mdx new file mode 100644 index 0000000000..f8d50f6d24 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-home.mdx @@ -0,0 +1,28 @@ +--- +title: go-e Charger HOME+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger HOME+ + + + +Requires firmware 052.1 or later. +Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. +The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). + + + + + + diff --git a/docs/devices-next/chargers/go-e-charger-homefix.mdx b/docs/devices-next/chargers/go-e-charger-homefix.mdx new file mode 100644 index 0000000000..f50e131f9d --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-homefix.mdx @@ -0,0 +1,26 @@ +--- +title: go-e Charger HOMEfix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger HOMEfix + + + +Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. + + + + + + diff --git a/docs/devices-next/chargers/go-e-charger-pro.mdx b/docs/devices-next/chargers/go-e-charger-pro.mdx new file mode 100644 index 0000000000..4494d18b1a --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-pro.mdx @@ -0,0 +1,33 @@ +--- +title: go-e Charger PRO +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger PRO + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/go-e-charger-v3.mdx b/docs/devices-next/chargers/go-e-charger-v3.mdx new file mode 100644 index 0000000000..f999ca3c9a --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-v3.mdx @@ -0,0 +1,33 @@ +--- +title: go-e Charger V3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger V3 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/hardybarth-cph1.mdx b/docs/devices-next/chargers/hardybarth-cph1.mdx new file mode 100644 index 0000000000..5b0ae4d8e8 --- /dev/null +++ b/docs/devices-next/chargers/hardybarth-cph1.mdx @@ -0,0 +1,31 @@ +--- +title: HardyBarth cPH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HardyBarth cPH1 + + + +Charge mode must be configured as `manual` + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx b/docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx new file mode 100644 index 0000000000..f22698bc11 --- /dev/null +++ b/docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx @@ -0,0 +1,23 @@ +--- +title: HardyBarth cPH2, cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HardyBarth cPH2, cPμ2 + + + + + + + diff --git a/docs/devices-next/chargers/heidelberg-energy-control.mdx b/docs/devices-next/chargers/heidelberg-energy-control.mdx new file mode 100644 index 0000000000..9446adc0c3 --- /dev/null +++ b/docs/devices-next/chargers/heidelberg-energy-control.mdx @@ -0,0 +1,38 @@ +--- +title: Heidelberg Energy Control +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Heidelberg Energy Control + + + +Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). + + + + + + diff --git a/docs/devices-next/chargers/hesotec-esat-ebox.mdx b/docs/devices-next/chargers/hesotec-esat-ebox.mdx new file mode 100644 index 0000000000..815f7bf64a --- /dev/null +++ b/docs/devices-next/chargers/hesotec-esat-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: Hesotec eSat, eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hesotec eSat, eBox + + + + + + + diff --git a/docs/devices-next/chargers/home-assistant-switch.mdx b/docs/devices-next/chargers/home-assistant-switch.mdx new file mode 100644 index 0000000000..b925ff9f0f --- /dev/null +++ b/docs/devices-next/chargers/home-assistant-switch.mdx @@ -0,0 +1,36 @@ +--- +title: Home Assistant Switch +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homeassistant-switch.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Home Assistant Switch + + + + + diff --git a/docs/devices-next/chargers/homecharge-homecharger.mdx b/docs/devices-next/chargers/homecharge-homecharger.mdx new file mode 100644 index 0000000000..aeda593af8 --- /dev/null +++ b/docs/devices-next/chargers/homecharge-homecharger.mdx @@ -0,0 +1,38 @@ +--- +title: Homecharge Homecharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-homecharge.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Homecharge Homecharger + + + +The charger must be equipped with a built-in meter (models HC11L/HC22L Energy or Profi). +For the OCPP configuration, you need to access the EFR-SECC charge controller at http://host/secc. +For login credentials, ask your dealer or the vendor EFR (www.efr.de). + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-homecharge + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/homematic-ip.mdx b/docs/devices-next/chargers/homematic-ip.mdx new file mode 100644 index 0000000000..ac56889015 --- /dev/null +++ b/docs/devices-next/chargers/homematic-ip.mdx @@ -0,0 +1,41 @@ +--- +title: Homematic IP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homematic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Homematic IP + + + + + diff --git a/docs/devices-next/chargers/homewizard.mdx b/docs/devices-next/chargers/homewizard.mdx new file mode 100644 index 0000000000..9362080e33 --- /dev/null +++ b/docs/devices-next/chargers/homewizard.mdx @@ -0,0 +1,30 @@ +--- +title: HomeWizard +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homewizard.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HomeWizard + + + + + diff --git a/docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx b/docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx new file mode 100644 index 0000000000..f29a63101d --- /dev/null +++ b/docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx @@ -0,0 +1,33 @@ +--- +title: Huawei SCharger-7KS-S0 / 22KT-S0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SCharger-7KS-S0 / 22KT-S0 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/idm.mdx b/docs/devices-next/chargers/idm.mdx new file mode 100644 index 0000000000..525683ef76 --- /dev/null +++ b/docs/devices-next/chargers/idm.mdx @@ -0,0 +1,27 @@ +--- +title: IDM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/idm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IDM + + + + + diff --git a/docs/devices-next/chargers/index.mdx b/docs/devices-next/chargers/index.mdx new file mode 100644 index 0000000000..2ea8ff4f7c --- /dev/null +++ b/docs/devices-next/chargers/index.mdx @@ -0,0 +1,1962 @@ +--- +title: Chargers +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Chargers + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/docs/devices-next/chargers/innogy-ebox.mdx b/docs/devices-next/chargers/innogy-ebox.mdx new file mode 100644 index 0000000000..f2e013c84a --- /dev/null +++ b/docs/devices-next/chargers/innogy-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: Innogy eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Innogy eBox + + + + + + + diff --git a/docs/devices-next/chargers/inro-pantabox.mdx b/docs/devices-next/chargers/inro-pantabox.mdx new file mode 100644 index 0000000000..d6d24e490a --- /dev/null +++ b/docs/devices-next/chargers/inro-pantabox.mdx @@ -0,0 +1,21 @@ +--- +title: INRO Pantabox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pantabox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# INRO Pantabox + + + + + diff --git a/docs/devices-next/chargers/juice-charger-me.mdx b/docs/devices-next/chargers/juice-charger-me.mdx new file mode 100644 index 0000000000..9aeafcdefb --- /dev/null +++ b/docs/devices-next/chargers/juice-charger-me.mdx @@ -0,0 +1,31 @@ +--- +title: Juice Charger Me +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Juice Charger Me + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/junkers-sg-ready.mdx b/docs/devices-next/chargers/junkers-sg-ready.mdx new file mode 100644 index 0000000000..2a17db6485 --- /dev/null +++ b/docs/devices-next/chargers/junkers-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Junkers SG Ready +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Junkers SG Ready + + + +Integrated via [EMSESP](https://emsesp.org/) + + + + diff --git a/docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx new file mode 100644 index 0000000000..a4b83dd447 --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx @@ -0,0 +1,31 @@ +--- +title: Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E + + + +The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 + + + + + + diff --git a/docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx b/docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx new file mode 100644 index 0000000000..f2c26147a0 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx @@ -0,0 +1,41 @@ +--- +title: KEBA KeContact P20, P30, C/X Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P20, P30, C/X Series + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + + + diff --git a/docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx b/docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx new file mode 100644 index 0000000000..8e5be0fabf --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx @@ -0,0 +1,41 @@ +--- +title: KEBA KeContact P40, P40 Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P40, P40 Pro + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + + + diff --git a/docs/devices-next/chargers/kermi-x-center-pro.mdx b/docs/devices-next/chargers/kermi-x-center-pro.mdx new file mode 100644 index 0000000000..d6d6d8f5d4 --- /dev/null +++ b/docs/devices-next/chargers/kermi-x-center-pro.mdx @@ -0,0 +1,28 @@ +--- +title: Kermi x-center pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kermi x-center pro + + + + + diff --git a/docs/devices-next/chargers/kontron-solar-charger.mdx b/docs/devices-next/chargers/kontron-solar-charger.mdx new file mode 100644 index 0000000000..bc62f59708 --- /dev/null +++ b/docs/devices-next/chargers/kontron-solar-charger.mdx @@ -0,0 +1,29 @@ +--- +title: Kontron Solar Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kontron Solar Charger + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/kostal-enector.mdx b/docs/devices-next/chargers/kostal-enector.mdx new file mode 100644 index 0000000000..4142b5b186 --- /dev/null +++ b/docs/devices-next/chargers/kostal-enector.mdx @@ -0,0 +1,40 @@ +--- +title: Kostal Enector +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Enector + + + +The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). +No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. +For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. + + + + + + diff --git a/docs/devices-next/chargers/kse-wbx16.mdx b/docs/devices-next/chargers/kse-wbx16.mdx new file mode 100644 index 0000000000..0dfbe570c2 --- /dev/null +++ b/docs/devices-next/chargers/kse-wbx16.mdx @@ -0,0 +1,35 @@ +--- +title: KSE wBX16 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KSE wBX16 + + + + + + + diff --git a/docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx b/docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx new file mode 100644 index 0000000000..eb53e26083 --- /dev/null +++ b/docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx @@ -0,0 +1,36 @@ +--- +title: LadeFoxx EvLoad, Mikro 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LadeFoxx EvLoad, Mikro 2.0 + + + +1 loadpoint), optional`} /> + diff --git a/docs/devices-next/chargers/lambda-eu-l-series.mdx b/docs/devices-next/chargers/lambda-eu-l-series.mdx new file mode 100644 index 0000000000..86745e765d --- /dev/null +++ b/docs/devices-next/chargers/lambda-eu-l-series.mdx @@ -0,0 +1,34 @@ +--- +title: Lambda EU-L Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Lambda EU-L Series + + + +Energy management settings of the device: + +- E-Meter communication type: "ModBus Client" +- E-Meter measuring point: "Pos. E-Überschuss" + + + + diff --git a/docs/devices-next/chargers/lrt-home-essential.mdx b/docs/devices-next/chargers/lrt-home-essential.mdx new file mode 100644 index 0000000000..30e92389a7 --- /dev/null +++ b/docs/devices-next/chargers/lrt-home-essential.mdx @@ -0,0 +1,38 @@ +--- +title: LRT HOME Essential+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LRT HOME Essential+ + + + +The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amedio-professional.mdx b/docs/devices-next/chargers/mennekes-amedio-professional.mdx new file mode 100644 index 0000000000..620f5b0c5f --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amedio-professional.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMEDIO Professional +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMEDIO Professional + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx new file mode 100644 index 0000000000..7e6f2715b9 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON 4Business 700 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON 4Business 700 + + + +The configuration option 'External Energy Management' must be enabled. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx new file mode 100644 index 0000000000..127b00ed4f --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -0,0 +1,40 @@ +--- +title: Mennekes AMTRON 4You 300 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON 4You 300 + + + +The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). +No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. +For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx new file mode 100644 index 0000000000..6f9cdefcb9 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON 4You 500 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON 4You 500 + + + +The configuration option 'External Energy Management' must be enabled. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx new file mode 100644 index 0000000000..01bd814290 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON ChargeControl +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON ChargeControl + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx b/docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx new file mode 100644 index 0000000000..33832b5df9 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx @@ -0,0 +1,40 @@ +--- +title: Mennekes AMTRON Compact 2.0s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Compact 2.0s + + + +The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). +No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. +For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-premium.mdx b/docs/devices-next/chargers/mennekes-amtron-premium.mdx new file mode 100644 index 0000000000..96b0d859a3 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-premium.mdx @@ -0,0 +1,28 @@ +--- +title: Mennekes AMTRON Premium +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Premium + + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-professional.mdx b/docs/devices-next/chargers/mennekes-amtron-professional.mdx new file mode 100644 index 0000000000..4ee7f9931a --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-professional.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON Professional +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Professional + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-xtra.mdx b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx new file mode 100644 index 0000000000..4aa744660a --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -0,0 +1,28 @@ +--- +title: Mennekes AMTRON Xtra +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Xtra + + + + + + + diff --git a/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx new file mode 100644 index 0000000000..8f68d6b9e8 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -0,0 +1,38 @@ +--- +title: Mennekes eMobility Gateway (ACU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes eMobility Gateway (ACU) + + + +To configure, open the web interface of the ACU. +Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J +Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/mennekes-smart-acu.mdx b/docs/devices-next/chargers/mennekes-smart-acu.mdx new file mode 100644 index 0000000000..4178279094 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-smart-acu.mdx @@ -0,0 +1,38 @@ +--- +title: Mennekes Smart (ACU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes Smart (ACU) + + + +To configure, open the web interface of the ACU. +Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J +Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/mennekes-smart-t-acu.mdx b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx new file mode 100644 index 0000000000..0373b0eb1e --- /dev/null +++ b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -0,0 +1,38 @@ +--- +title: Mennekes Smart T (ACU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes Smart T (ACU) + + + +To configure, open the web interface of the ACU. +Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J +Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx new file mode 100644 index 0000000000..e8831dd3ce --- /dev/null +++ b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -0,0 +1,29 @@ +--- +title: my-PV AC ELWA 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-elwa-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC ELWA 2 + + + + + + + diff --git a/docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx b/docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx new file mode 100644 index 0000000000..0a0cca3b32 --- /dev/null +++ b/docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx @@ -0,0 +1,30 @@ +--- +title: my-PV AC THOR, AC THOR 9s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC THOR, AC THOR 9s + + + + + + + diff --git a/docs/devices-next/chargers/mystrom-switch.mdx b/docs/devices-next/chargers/mystrom-switch.mdx new file mode 100644 index 0000000000..bfdd79a7ea --- /dev/null +++ b/docs/devices-next/chargers/mystrom-switch.mdx @@ -0,0 +1,30 @@ +--- +title: myStrom Switch +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mystrom.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# myStrom Switch + + + + + diff --git a/docs/devices-next/chargers/nrgkick-connect.mdx b/docs/devices-next/chargers/nrgkick-connect.mdx new file mode 100644 index 0000000000..98f4383cf0 --- /dev/null +++ b/docs/devices-next/chargers/nrgkick-connect.mdx @@ -0,0 +1,26 @@ +--- +title: NRGKick Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrgkick-connect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# NRGKick Connect + + + +NRGkick charging unit via HTTP (older than 2022/2023) + + + + diff --git a/docs/devices-next/chargers/nrgkick-gen2.mdx b/docs/devices-next/chargers/nrgkick-gen2.mdx new file mode 100644 index 0000000000..214ba5b881 --- /dev/null +++ b/docs/devices-next/chargers/nrgkick-gen2.mdx @@ -0,0 +1,38 @@ +--- +title: NRGKick Gen2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrggen2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# NRGKick Gen2 + + + + + + + diff --git a/docs/devices-next/chargers/obo-bettermann-ion.mdx b/docs/devices-next/chargers/obo-bettermann-ion.mdx new file mode 100644 index 0000000000..229ff8177a --- /dev/null +++ b/docs/devices-next/chargers/obo-bettermann-ion.mdx @@ -0,0 +1,39 @@ +--- +title: OBO Bettermann Ion +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OBO Bettermann Ion + + + + + diff --git a/docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx b/docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx new file mode 100644 index 0000000000..c9afc5e3e2 --- /dev/null +++ b/docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx @@ -0,0 +1,54 @@ +--- +title: OCPP 1.6J compatible (Smart Charging) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OCPP 1.6J compatible (Smart Charging) + + + +With OCPP the connection will be established from charger (client) to evcc (server). +The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. +By default, the first incoming connection with any station identifier is used. +In order to be able to clearly assign several charging points, the respective station identifier (`stationid: `) and connector number (`connector: `) must be configured. +Many wallboxes automatically add the `station id` to the backend URL, some have to do this manually `ws://:8887/`. +If the charger supports sending metering values, try to adjust the interval to a short time span (< 10s) . +Use your RFID tags (this allows e.g. vehicle identification) or set your charger to "free charging" or "autostart" to generate the transaction required for charging release. + +If the charger does not offer any option to start transactions locally, the `remotestart` advanced option can be used to automatically start a transaction as soon as a vehicle is connected. +This should only be necessary in exceptional cases. + +Requirements: +* If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration +* Backend URL (Central System) in the charger configuration: `ws://[evcc-adresse]:8887/` (possibly add `stationid`) +* Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar +* No encryption, no authentication, no password +* Local network connection + +The specific configuration and the actual usable functionality depend on the charger model and its software. + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/openevse.mdx b/docs/devices-next/chargers/openevse.mdx new file mode 100644 index 0000000000..64af434add --- /dev/null +++ b/docs/devices-next/chargers/openevse.mdx @@ -0,0 +1,26 @@ +--- +title: OpenEVSE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openevse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OpenEVSE + + + +Requires firmware 7.0 or later. + + + + diff --git a/docs/devices-next/chargers/openwb-pro.mdx b/docs/devices-next/chargers/openwb-pro.mdx new file mode 100644 index 0000000000..cf77c4efb5 --- /dev/null +++ b/docs/devices-next/chargers/openwb-pro.mdx @@ -0,0 +1,21 @@ +--- +title: openWB Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-pro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB Pro + + + + + diff --git a/docs/devices-next/chargers/openwb-series2.mdx b/docs/devices-next/chargers/openwb-series2.mdx new file mode 100644 index 0000000000..835974275d --- /dev/null +++ b/docs/devices-next/chargers/openwb-series2.mdx @@ -0,0 +1,30 @@ +--- +title: openWB series2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB series2 + + + +The wallbox has to be configured as loadpoint. + + +1 loadpoint), optional + phases1p3p: false # Charger is equipped with phase switching feature, optional`} /> + diff --git a/docs/devices-next/chargers/openwb-software-2x.mdx b/docs/devices-next/chargers/openwb-software-2x.mdx new file mode 100644 index 0000000000..3b51269df8 --- /dev/null +++ b/docs/devices-next/chargers/openwb-software-2x.mdx @@ -0,0 +1,44 @@ +--- +title: openWB Software 2.x +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB Software 2.x + + + +Requires [`Software 2.x`](https://github.com/openWB/core). +The following changes are necessary under the 'Einstellungen' tab: + +* Steuerungsmodus: `secondary` +* Steuerung über Modbus als secondary: `An` + + +1 loadpoint), optional + phases1p3p: true # Charger is equipped with phase switching feature, optional`} /> + diff --git a/docs/devices-next/chargers/optec-mobility-one.mdx b/docs/devices-next/chargers/optec-mobility-one.mdx new file mode 100644 index 0000000000..6b0bee3b72 --- /dev/null +++ b/docs/devices-next/chargers/optec-mobility-one.mdx @@ -0,0 +1,31 @@ +--- +title: Optec Mobility One +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Optec Mobility One + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/orbis-viaris.mdx b/docs/devices-next/chargers/orbis-viaris.mdx new file mode 100644 index 0000000000..6c17a188a0 --- /dev/null +++ b/docs/devices-next/chargers/orbis-viaris.mdx @@ -0,0 +1,33 @@ +--- +title: Orbis Viaris +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-orbis.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Orbis Viaris + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-orbis + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/pc-electric-garo.mdx b/docs/devices-next/chargers/pc-electric-garo.mdx new file mode 100644 index 0000000000..b4b633622c --- /dev/null +++ b/docs/devices-next/chargers/pc-electric-garo.mdx @@ -0,0 +1,27 @@ +--- +title: PC Electric Garo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pcelectric-garo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# PC Electric Garo + + + +Only devices configured as master can be used right now! + + + + + + diff --git a/docs/devices-next/chargers/peblar-home-home-plus-business.mdx b/docs/devices-next/chargers/peblar-home-home-plus-business.mdx new file mode 100644 index 0000000000..8680cfccbc --- /dev/null +++ b/docs/devices-next/chargers/peblar-home-home-plus-business.mdx @@ -0,0 +1,31 @@ +--- +title: Peblar Home, Home Plus, Business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Home, Home Plus, Business + + + +Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. + + + + + + diff --git a/docs/devices-next/chargers/phoenix-contact-charx.mdx b/docs/devices-next/chargers/phoenix-contact-charx.mdx new file mode 100644 index 0000000000..c3dee86377 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-charx.mdx @@ -0,0 +1,36 @@ +--- +title: Phoenix Contact CHARX +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact CHARX + + + +1 loadpoint), optional`} /> + diff --git a/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx new file mode 100644 index 0000000000..a22dc03947 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -0,0 +1,26 @@ +--- +title: Phoenix Contact EM-CP-PP-ETH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-em-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EM-CP-PP-ETH + + + + + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx new file mode 100644 index 0000000000..1cb5960aab --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx new file mode 100644 index 0000000000..7abb20dca7 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx new file mode 100644 index 0000000000..4a3f15b160 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx new file mode 100644 index 0000000000..6182d82ef9 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx new file mode 100644 index 0000000000..1dce994e0f --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -0,0 +1,33 @@ +--- +title: Phoenix Contact EV-SER +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-ser.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-SER + + + + + diff --git a/docs/devices-next/chargers/plugchoice.mdx b/docs/devices-next/chargers/plugchoice.mdx new file mode 100644 index 0000000000..9f42589588 --- /dev/null +++ b/docs/devices-next/chargers/plugchoice.mdx @@ -0,0 +1,40 @@ +--- +title: Plugchoice +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/plugchoice.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Plugchoice + + + +Chargers connected through Plugchoice can leverage its OCPP proxy functionality to establish a connection to other backoffices while maintaining full control through EVCC. This allows seamless management of Plugchoice-registered chargers directly from EVCC. + +For improved meter readings, it is recommended to configure the following settings in the Plugchoice portal under the configuration tab: + +- Set `MeterValueSampleInterval` to 10 seconds (or another interval according to your preference). +- Set `MeterValuesSampledData` to `Energy.Active.Import.Register,Current.Offered,Current.Import,Voltage`. + +These adjustments enable more frequent and detailed reporting of charging data to EVCC. + + +1 loadpoint), Connector ID (usually 1)`} /> + + + diff --git a/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx new file mode 100644 index 0000000000..b527a29b6b --- /dev/null +++ b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -0,0 +1,22 @@ +--- +title: Porsche Mobile Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Porsche Mobile Charger Connect + + + + + diff --git a/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx new file mode 100644 index 0000000000..a95fa8f605 --- /dev/null +++ b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -0,0 +1,22 @@ +--- +title: Porsche Mobile Charger Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Porsche Mobile Charger Plus + + + + + diff --git a/docs/devices-next/chargers/porsche-wallbox.mdx b/docs/devices-next/chargers/porsche-wallbox.mdx new file mode 100644 index 0000000000..ee24b4fe1d --- /dev/null +++ b/docs/devices-next/chargers/porsche-wallbox.mdx @@ -0,0 +1,29 @@ +--- +title: Porsche Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/porsche-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Porsche Wallbox + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/pracht-alpha-xt.mdx b/docs/devices-next/chargers/pracht-alpha-xt.mdx new file mode 100644 index 0000000000..7484f59800 --- /dev/null +++ b/docs/devices-next/chargers/pracht-alpha-xt.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht Alpha XT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht Alpha XT + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/pracht-mono-xt.mdx b/docs/devices-next/chargers/pracht-mono-xt.mdx new file mode 100644 index 0000000000..ab4dc66a68 --- /dev/null +++ b/docs/devices-next/chargers/pracht-mono-xt.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht Mono XT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht Mono XT + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/pracht-pni.mdx b/docs/devices-next/chargers/pracht-pni.mdx new file mode 100644 index 0000000000..d32088d39e --- /dev/null +++ b/docs/devices-next/chargers/pracht-pni.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht PNI +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht PNI + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/pracht-xt.mdx b/docs/devices-next/chargers/pracht-xt.mdx new file mode 100644 index 0000000000..2a637437e4 --- /dev/null +++ b/docs/devices-next/chargers/pracht-xt.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht XT+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht XT+ + + + +1 loadpoint), optional`} /> + + + diff --git a/docs/devices-next/chargers/pulsares-simplebox.mdx b/docs/devices-next/chargers/pulsares-simplebox.mdx new file mode 100644 index 0000000000..4b9dbce34f --- /dev/null +++ b/docs/devices-next/chargers/pulsares-simplebox.mdx @@ -0,0 +1,33 @@ +--- +title: Pulsares SimpleBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsares.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pulsares SimpleBox + + + + + diff --git a/docs/devices-next/chargers/pulsatrix.mdx b/docs/devices-next/chargers/pulsatrix.mdx new file mode 100644 index 0000000000..f2668a3a2a --- /dev/null +++ b/docs/devices-next/chargers/pulsatrix.mdx @@ -0,0 +1,23 @@ +--- +title: Pulsatrix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsatrix.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pulsatrix + + + + + + + diff --git a/docs/devices-next/chargers/qcells-qhome-edrive-a.mdx b/docs/devices-next/chargers/qcells-qhome-edrive-a.mdx new file mode 100644 index 0000000000..158eec5f10 --- /dev/null +++ b/docs/devices-next/chargers/qcells-qhome-edrive-a.mdx @@ -0,0 +1,38 @@ +--- +title: Qcells Q.HOME EDRIVE A +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME EDRIVE A + + + +The charger must be in “Fast” mode and decoupled from the inverter system. + + + + + + diff --git a/docs/devices-next/chargers/schneider-evlink-pro.mdx b/docs/devices-next/chargers/schneider-evlink-pro.mdx new file mode 100644 index 0000000000..46e0ecba3f --- /dev/null +++ b/docs/devices-next/chargers/schneider-evlink-pro.mdx @@ -0,0 +1,28 @@ +--- +title: Schneider EVlink Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/schneider-evlink-v3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Schneider EVlink Pro + + + + + + + diff --git a/docs/devices-next/chargers/schrack-i-charge-cion.mdx b/docs/devices-next/chargers/schrack-i-charge-cion.mdx new file mode 100644 index 0000000000..823e8052be --- /dev/null +++ b/docs/devices-next/chargers/schrack-i-charge-cion.mdx @@ -0,0 +1,33 @@ +--- +title: Schrack i-CHARGE CION +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Schrack i-CHARGE CION + + + + + diff --git a/docs/devices-next/chargers/senec-wallbox-pro-s.mdx b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx new file mode 100644 index 0000000000..3d5c3cd5fe --- /dev/null +++ b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -0,0 +1,38 @@ +--- +title: SENEC Wallbox pro s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SENEC Wallbox pro s + + + +Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). + + + + + + diff --git a/docs/devices-next/chargers/senec-wallbox-pro.mdx b/docs/devices-next/chargers/senec-wallbox-pro.mdx new file mode 100644 index 0000000000..9c71e1864d --- /dev/null +++ b/docs/devices-next/chargers/senec-wallbox-pro.mdx @@ -0,0 +1,36 @@ +--- +title: SENEC Wallbox pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SENEC Wallbox pro + + + + + + + diff --git a/docs/devices-next/chargers/shelly.mdx b/docs/devices-next/chargers/shelly.mdx new file mode 100644 index 0000000000..dc26ad8ed6 --- /dev/null +++ b/docs/devices-next/chargers/shelly.mdx @@ -0,0 +1,36 @@ +--- +title: Shelly +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly + + + + + diff --git a/docs/devices-next/chargers/siemens-versicharge-gen3.mdx b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx new file mode 100644 index 0000000000..b740df3281 --- /dev/null +++ b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -0,0 +1,31 @@ +--- +title: Siemens Versicharge GEN3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/versicharge.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens Versicharge GEN3 + + + +Requires firmware >= 2.135 + + + + + + diff --git a/docs/devices-next/chargers/skoda-charger-connect.mdx b/docs/devices-next/chargers/skoda-charger-connect.mdx new file mode 100644 index 0000000000..0d74b6386b --- /dev/null +++ b/docs/devices-next/chargers/skoda-charger-connect.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Charger Connect + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx new file mode 100644 index 0000000000..7e6f2eca75 --- /dev/null +++ b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda Charger Pro Eichrecht +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Charger Pro Eichrecht + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/skoda-charger-pro.mdx b/docs/devices-next/chargers/skoda-charger-pro.mdx new file mode 100644 index 0000000000..9cdf03b1cb --- /dev/null +++ b/docs/devices-next/chargers/skoda-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Charger Pro + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/skoda-iv-charger-connect.mdx b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx new file mode 100644 index 0000000000..fe7ec34cee --- /dev/null +++ b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda iV Charger Connect+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda iV Charger Connect+ + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + + + diff --git a/docs/devices-next/chargers/sma-ev-charger-echarger.mdx b/docs/devices-next/chargers/sma-ev-charger-echarger.mdx new file mode 100644 index 0000000000..9a9ecbbb1e --- /dev/null +++ b/docs/devices-next/chargers/sma-ev-charger-echarger.mdx @@ -0,0 +1,28 @@ +--- +title: SMA EV Charger, eCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA EV Charger, eCharger + + + +The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. + + + + + + diff --git a/docs/devices-next/chargers/smartfox-pro-charger.mdx b/docs/devices-next/chargers/smartfox-pro-charger.mdx new file mode 100644 index 0000000000..61f6c01afe --- /dev/null +++ b/docs/devices-next/chargers/smartfox-pro-charger.mdx @@ -0,0 +1,33 @@ +--- +title: Smartfox Pro Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro Charger + + + + + diff --git a/docs/devices-next/chargers/smartwb.mdx b/docs/devices-next/chargers/smartwb.mdx new file mode 100644 index 0000000000..b7fc1c9b65 --- /dev/null +++ b/docs/devices-next/chargers/smartwb.mdx @@ -0,0 +1,21 @@ +--- +title: smartWB +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartwb.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# smartWB + + + + + diff --git a/docs/devices-next/chargers/solaredge-home-ev-charger.mdx b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx new file mode 100644 index 0000000000..569ed4870e --- /dev/null +++ b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -0,0 +1,41 @@ +--- +title: SolarEdge Home EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarEdge Home EV Charger + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + + + diff --git a/docs/devices-next/chargers/solax-x3-evc.mdx b/docs/devices-next/chargers/solax-x3-evc.mdx new file mode 100644 index 0000000000..0b93d79a4f --- /dev/null +++ b/docs/devices-next/chargers/solax-x3-evc.mdx @@ -0,0 +1,38 @@ +--- +title: Solax X3-EVC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax X3-EVC + + + +The charger must be in “Fast” mode and decoupled from the inverter system. + + + + + + diff --git a/docs/devices-next/chargers/sonnen-sonnencharger.mdx b/docs/devices-next/chargers/sonnen-sonnencharger.mdx new file mode 100644 index 0000000000..521a9c68a5 --- /dev/null +++ b/docs/devices-next/chargers/sonnen-sonnencharger.mdx @@ -0,0 +1,27 @@ +--- +title: Sonnen sonnenCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen sonnenCharger + + + +The charger must be switched to "Power" charging mode. + + + + + + diff --git a/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx new file mode 100644 index 0000000000..057ec3a6a0 --- /dev/null +++ b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -0,0 +1,31 @@ +--- +title: Spelsberg Wallbox Smart Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Spelsberg Wallbox Smart Pro + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/stark-in-strom-easy.mdx b/docs/devices-next/chargers/stark-in-strom-easy.mdx new file mode 100644 index 0000000000..17e1380699 --- /dev/null +++ b/docs/devices-next/chargers/stark-in-strom-easy.mdx @@ -0,0 +1,33 @@ +--- +title: Stark in Strom Easy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stark in Strom Easy + + + + + diff --git a/docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx new file mode 100644 index 0000000000..5981a905f5 --- /dev/null +++ b/docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Stiebel Eltron LWA/LWZ (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stiebel Eltron LWA/LWZ (SG Ready) + + + + + diff --git a/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx new file mode 100644 index 0000000000..e3f028ce05 --- /dev/null +++ b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Stiebel Eltron WPM (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-wpm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stiebel Eltron WPM (SG Ready) + + + + + diff --git a/docs/devices-next/chargers/sungrow-ac011e-01.mdx b/docs/devices-next/chargers/sungrow-ac011e-01.mdx new file mode 100644 index 0000000000..3ee7b944e7 --- /dev/null +++ b/docs/devices-next/chargers/sungrow-ac011e-01.mdx @@ -0,0 +1,41 @@ +--- +title: Sungrow AC011E-01 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow AC011E-01 + + + + + + + diff --git a/docs/devices-next/chargers/sungrow-ac011e.mdx b/docs/devices-next/chargers/sungrow-ac011e.mdx new file mode 100644 index 0000000000..0085ad67d8 --- /dev/null +++ b/docs/devices-next/chargers/sungrow-ac011e.mdx @@ -0,0 +1,33 @@ +--- +title: Sungrow AC011E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-sungrow.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow AC011E + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-sungrow + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/tasmota-single-phase.mdx b/docs/devices-next/chargers/tasmota-single-phase.mdx new file mode 100644 index 0000000000..d354fb6e01 --- /dev/null +++ b/docs/devices-next/chargers/tasmota-single-phase.mdx @@ -0,0 +1,36 @@ +--- +title: Tasmota single phase +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tasmota.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota single phase + + + + + diff --git a/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx new file mode 100644 index 0000000000..958dc68017 --- /dev/null +++ b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Tecalor THZ (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tecalor THZ (SG Ready) + + + + + diff --git a/docs/devices-next/chargers/technisat-technivolt.mdx b/docs/devices-next/chargers/technisat-technivolt.mdx new file mode 100644 index 0000000000..4b18531e82 --- /dev/null +++ b/docs/devices-next/chargers/technisat-technivolt.mdx @@ -0,0 +1,31 @@ +--- +title: TechniSat Technivolt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TechniSat Technivolt + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/tesla-twc3.mdx b/docs/devices-next/chargers/tesla-twc3.mdx new file mode 100644 index 0000000000..5d35924b92 --- /dev/null +++ b/docs/devices-next/chargers/tesla-twc3.mdx @@ -0,0 +1,24 @@ +--- +title: Tesla TWC3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla TWC3 + + + +The TWC wallbox cannot be controlled directly. Control is via the vehicle. The vehicle must be selected at the TWC3 loadpoint. At this time only [Tesla vehicles](https://docs.evcc.io/en/docs/devices/vehicles#tesla) are supported. + + + + diff --git a/docs/devices-next/chargers/tessie.mdx b/docs/devices-next/chargers/tessie.mdx new file mode 100644 index 0000000000..ee8d2a75f1 --- /dev/null +++ b/docs/devices-next/chargers/tessie.mdx @@ -0,0 +1,26 @@ +--- +title: Tessie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tessie.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tessie + + + +Charger connected via the Tessie API. Allows control of charging state and configuration of maximum current. + + + + diff --git a/docs/devices-next/chargers/tigo-go-ev-charger.mdx b/docs/devices-next/chargers/tigo-go-ev-charger.mdx new file mode 100644 index 0000000000..0cd12013c9 --- /dev/null +++ b/docs/devices-next/chargers/tigo-go-ev-charger.mdx @@ -0,0 +1,38 @@ +--- +title: Tigo GO EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tigo GO EV Charger + + + +The charger must be in “Fast” mode and decoupled from the inverter system. + + + + + + diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx new file mode 100644 index 0000000000..5103b14ee3 --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -0,0 +1,38 @@ +--- +title: TinkerForge WARP Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP Charger Pro + + + +WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. + + + + diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx new file mode 100644 index 0000000000..38276ada0d --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -0,0 +1,38 @@ +--- +title: TinkerForge WARP Charger Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP Charger Smart + + + +WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. + + + + diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx new file mode 100644 index 0000000000..03878b054d --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -0,0 +1,36 @@ +--- +title: TinkerForge WARP3 Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP3 Charger Pro + + + +The automatic phase switching for 1p vehicles must be deactivated. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. + + + + diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx new file mode 100644 index 0000000000..74187543d4 --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -0,0 +1,33 @@ +--- +title: TinkerForge WARP3 Charger Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3-smart.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP3 Charger Smart + + + + + diff --git a/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx new file mode 100644 index 0000000000..4aea80806c --- /dev/null +++ b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,30 @@ +--- +title: TP-Link H-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tplink.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link H-Series Smart Plug + + + + + diff --git a/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx new file mode 100644 index 0000000000..4dc26af931 --- /dev/null +++ b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,34 @@ +--- +title: TP-Link Tapo P-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tapo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link Tapo P-Series Smart Plug + + + + + diff --git a/docs/devices-next/chargers/ubitricity-heinz.mdx b/docs/devices-next/chargers/ubitricity-heinz.mdx new file mode 100644 index 0000000000..34251b42fa --- /dev/null +++ b/docs/devices-next/chargers/ubitricity-heinz.mdx @@ -0,0 +1,31 @@ +--- +title: Ubitricity Heinz +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ubitricity Heinz + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/v2c-trydan.mdx b/docs/devices-next/chargers/v2c-trydan.mdx new file mode 100644 index 0000000000..cfd7e27643 --- /dev/null +++ b/docs/devices-next/chargers/v2c-trydan.mdx @@ -0,0 +1,26 @@ +--- +title: V2C Trydan +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/trydan.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# V2C Trydan + + + +V2C trydan + + + + + + diff --git a/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx new file mode 100644 index 0000000000..6837d1e4c8 --- /dev/null +++ b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -0,0 +1,28 @@ +--- +title: Vaillant SensoNET (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vaillant.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vaillant SensoNET (SG Ready) + + + +The boost function heats hot water or a boost zone. The boost zone is identified by the ID. The boost temperature is specified in degrees Celsius. If boost temperature is specified, the boost zone is activated, otherwise hot water. + + + + diff --git a/docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx b/docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx new file mode 100644 index 0000000000..b4017e6146 --- /dev/null +++ b/docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx @@ -0,0 +1,31 @@ +--- +title: Vestel EVC04 Home Smart, Connect Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vestel EVC04 Home Smart, Connect Plus + + + +1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. + + + + + + diff --git a/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx new file mode 100644 index 0000000000..cfdf9be1f6 --- /dev/null +++ b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -0,0 +1,29 @@ +--- +title: Victron EV Charging Station (via GX) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EV Charging Station (via GX) + + + +Enter the host of the GX device (not the charger). The charger has to be in manual mode and Modbus has to be configured for ID 100. + + + + diff --git a/docs/devices-next/chargers/victron-ev-charging-station.mdx b/docs/devices-next/chargers/victron-ev-charging-station.mdx new file mode 100644 index 0000000000..279b15ac6f --- /dev/null +++ b/docs/devices-next/chargers/victron-ev-charging-station.mdx @@ -0,0 +1,29 @@ +--- +title: Victron EV Charging Station +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron-evcs.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EV Charging Station + + + +Enter the host of the charger (not the GX device) and ensure that the charger is in manual mode. + + + + diff --git a/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx new file mode 100644 index 0000000000..6be19915df --- /dev/null +++ b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -0,0 +1,30 @@ +--- +title: Viessmann Heatpump (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/viessmann.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Viessmann Heatpump (SG Ready) + + + +One-time hot water preparation to a configurable target temperature. The device automatically decides whether to use the heat pump or the auxiliary electric heater (if available). + + + Settings -> Communication module -> Serial number) + installation_id: # Installation ID, Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...
Prerequisites: curl, jq, and the following parameters: \`\`\` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= \`\`\` Then execute the following (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): \`\`\` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" \`\`\` + device_id: 0 # Device ID, typically \`0\` + target_temperature: 45 # Target temperature for one-time charge (°C), max. 60°C`} /> + diff --git a/docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx b/docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx new file mode 100644 index 0000000000..3325e35d37 --- /dev/null +++ b/docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx @@ -0,0 +1,39 @@ +--- +title: Viridian EV EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Viridian EV EVSE EPC 2.0 Plus + + + + + diff --git a/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx new file mode 100644 index 0000000000..5fb962f0d1 --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen Charger Connect 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen Charger Connect 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx new file mode 100644 index 0000000000..855460ed3e --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen Charger Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen Charger Pro 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx new file mode 100644 index 0000000000..cfb145ecd7 --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen Charger Pro Eichrecht 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen Charger Pro Eichrecht 2 + + + +The device has to be used in the normal charging mode. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + + diff --git a/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx new file mode 100644 index 0000000000..638ea822f1 --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -0,0 +1,31 @@ +--- +title: Volkswagen ID. Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen ID. Charger Connect + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + + + + diff --git a/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx new file mode 100644 index 0000000000..8a01e16e67 --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen ID. Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen ID. Charger Pro + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + + + diff --git a/docs/devices-next/chargers/volt-time-one.mdx b/docs/devices-next/chargers/volt-time-one.mdx new file mode 100644 index 0000000000..f713f15255 --- /dev/null +++ b/docs/devices-next/chargers/volt-time-one.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time One +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time One + + + + + + + diff --git a/docs/devices-next/chargers/volt-time-source-2.mdx b/docs/devices-next/chargers/volt-time-source-2.mdx new file mode 100644 index 0000000000..6d9361f8bb --- /dev/null +++ b/docs/devices-next/chargers/volt-time-source-2.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time Source 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time Source 2 + + + + + + + diff --git a/docs/devices-next/chargers/volt-time-source-2s.mdx b/docs/devices-next/chargers/volt-time-source-2s.mdx new file mode 100644 index 0000000000..840306719f --- /dev/null +++ b/docs/devices-next/chargers/volt-time-source-2s.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time Source 2s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time Source 2s + + + + + + + diff --git a/docs/devices-next/chargers/volt-time-source.mdx b/docs/devices-next/chargers/volt-time-source.mdx new file mode 100644 index 0000000000..da5906e2df --- /dev/null +++ b/docs/devices-next/chargers/volt-time-source.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time Source +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time Source + + + + + + + diff --git a/docs/devices-next/chargers/wallbe-eco-20s.mdx b/docs/devices-next/chargers/wallbe-eco-20s.mdx new file mode 100644 index 0000000000..0eec5dca5b --- /dev/null +++ b/docs/devices-next/chargers/wallbe-eco-20s.mdx @@ -0,0 +1,31 @@ +--- +title: Wallbe Eco 2.0(s) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Eco 2.0(s) + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/wallbe-eco.mdx b/docs/devices-next/chargers/wallbe-eco.mdx new file mode 100644 index 0000000000..b457fa53e3 --- /dev/null +++ b/docs/devices-next/chargers/wallbe-eco.mdx @@ -0,0 +1,31 @@ +--- +title: Wallbe Eco +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Eco + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/wallbe-pro.mdx b/docs/devices-next/chargers/wallbe-pro.mdx new file mode 100644 index 0000000000..da4b49eeb1 --- /dev/null +++ b/docs/devices-next/chargers/wallbe-pro.mdx @@ -0,0 +1,31 @@ +--- +title: Wallbe Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Pro + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + + + diff --git a/docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx b/docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx new file mode 100644 index 0000000000..e9f2041b67 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Commander 2 (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Commander 2 (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/wallbox-commander-2.mdx b/docs/devices-next/chargers/wallbox-commander-2.mdx new file mode 100644 index 0000000000..f257f43bd6 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-commander-2.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Commander 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Commander 2 + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx b/docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx new file mode 100644 index 0000000000..efd7140aa7 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Copper SB (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Copper SB (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/wallbox-copper-sb.mdx b/docs/devices-next/chargers/wallbox-copper-sb.mdx new file mode 100644 index 0000000000..a6d59c6f73 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-copper-sb.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Copper SB +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Copper SB + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx new file mode 100644 index 0000000000..fd8fd6e574 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Max (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Max (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/wallbox-pulsar-max.mdx b/docs/devices-next/chargers/wallbox-pulsar-max.mdx new file mode 100644 index 0000000000..b0c82f209c --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-max.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Max +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Max + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx new file mode 100644 index 0000000000..f26625c4d7 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Plus (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Plus (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx new file mode 100644 index 0000000000..80d3b1ba3b --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Plus + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx new file mode 100644 index 0000000000..c30691684b --- /dev/null +++ b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -0,0 +1,38 @@ +--- +title: Walther Werke Basic Evo Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Walther Werke Basic Evo Pro + + + +Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). + + + + + + diff --git a/docs/devices-next/chargers/webasto-live.mdx b/docs/devices-next/chargers/webasto-live.mdx new file mode 100644 index 0000000000..b7fcbe8395 --- /dev/null +++ b/docs/devices-next/chargers/webasto-live.mdx @@ -0,0 +1,31 @@ +--- +title: Webasto Live +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Webasto Live + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + diff --git a/docs/devices-next/chargers/webasto-next.mdx b/docs/devices-next/chargers/webasto-next.mdx new file mode 100644 index 0000000000..da12321ff5 --- /dev/null +++ b/docs/devices-next/chargers/webasto-next.mdx @@ -0,0 +1,27 @@ +--- +title: Webasto NEXT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Webasto NEXT + + + +Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. + + + + + + diff --git a/docs/devices-next/chargers/webasto-unite.mdx b/docs/devices-next/chargers/webasto-unite.mdx new file mode 100644 index 0000000000..ec59f0020e --- /dev/null +++ b/docs/devices-next/chargers/webasto-unite.mdx @@ -0,0 +1,31 @@ +--- +title: Webasto Unite +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Webasto Unite + + + +1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. + + + + + + diff --git a/docs/devices-next/chargers/weidmuller-ac-smart.mdx b/docs/devices-next/chargers/weidmuller-ac-smart.mdx new file mode 100644 index 0000000000..f70dc919fa --- /dev/null +++ b/docs/devices-next/chargers/weidmuller-ac-smart.mdx @@ -0,0 +1,23 @@ +--- +title: Weidmüller AC Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/weidmüller.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller AC Smart + + + + + + + diff --git a/docs/devices-next/chargers/zaptec-go-2.mdx b/docs/devices-next/chargers/zaptec-go-2.mdx new file mode 100644 index 0000000000..cd0fc3a973 --- /dev/null +++ b/docs/devices-next/chargers/zaptec-go-2.mdx @@ -0,0 +1,25 @@ +--- +title: Zaptec Go 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Go 2 + + + + + + + diff --git a/docs/devices-next/chargers/zaptec-go.mdx b/docs/devices-next/chargers/zaptec-go.mdx new file mode 100644 index 0000000000..62d22e899b --- /dev/null +++ b/docs/devices-next/chargers/zaptec-go.mdx @@ -0,0 +1,25 @@ +--- +title: Zaptec Go +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Go + + + + + + + diff --git a/docs/devices-next/chargers/zaptec-pro.mdx b/docs/devices-next/chargers/zaptec-pro.mdx new file mode 100644 index 0000000000..b4ffb2db1e --- /dev/null +++ b/docs/devices-next/chargers/zaptec-pro.mdx @@ -0,0 +1,25 @@ +--- +title: Zaptec Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Pro + + + + + + + diff --git a/docs/devices-next/chargers/zewotherm-eu-l-series.mdx b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx new file mode 100644 index 0000000000..7627e86901 --- /dev/null +++ b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -0,0 +1,34 @@ +--- +title: Zewotherm EU-L Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zewotherm EU-L Series + + + +Energy management settings of the device: + +- E-Meter communication type: "ModBus Client" +- E-Meter measuring point: "Pos. E-Überschuss" + + + + diff --git a/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx new file mode 100644 index 0000000000..796d04b3c5 --- /dev/null +++ b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -0,0 +1,33 @@ +--- +title: ZJ Beny BCP EV charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-beny.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZJ Beny BCP EV charger + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-beny + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + diff --git a/docs/devices-next/meters/a-tronix.mdx b/docs/devices-next/meters/a-tronix.mdx new file mode 100644 index 0000000000..575b8ae48f --- /dev/null +++ b/docs/devices-next/meters/a-tronix.mdx @@ -0,0 +1,139 @@ +--- +title: A-Tronix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# A-Tronix + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/abb-a43-a44-b23-b24.mdx b/docs/devices-next/meters/abb-a43-a44-b23-b24.mdx new file mode 100644 index 0000000000..f77804a0a1 --- /dev/null +++ b/docs/devices-next/meters/abb-a43-a44-b23-b24.mdx @@ -0,0 +1,62 @@ +--- +title: ABB A43, A44, B23, B24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB A43, A44, B23, B24 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx b/docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx new file mode 100644 index 0000000000..7f7abf5af1 --- /dev/null +++ b/docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx @@ -0,0 +1,102 @@ +--- +title: Acrel ADW300 Wireless Metering Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Acrel ADW300 Wireless Metering Meter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/ads-tec-storaxe.mdx b/docs/devices-next/meters/ads-tec-storaxe.mdx new file mode 100644 index 0000000000..e4494d8611 --- /dev/null +++ b/docs/devices-next/meters/ads-tec-storaxe.mdx @@ -0,0 +1,38 @@ +--- +title: Ads-tec StoraXe +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/storaxe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ads-tec StoraXe + + + + + diff --git a/docs/devices-next/meters/alpha-ess-storion-smile.mdx b/docs/devices-next/meters/alpha-ess-storion-smile.mdx new file mode 100644 index 0000000000..917d1ea264 --- /dev/null +++ b/docs/devices-next/meters/alpha-ess-storion-smile.mdx @@ -0,0 +1,182 @@ +--- +title: Alpha ESS Storion SMILE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/alpha-ess-smile.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alpha ESS Storion SMILE + + + +To use active battery control, times for grid charging must be defined once via the web interface or app. (Settings->Function settings->Grid charging/discharging) A continuous time period should be entered here (e.g.: Charging time 1 00:00-23:00, Charging time 2 23:00-00:00). However, deactivate the "Grid charging" switch. The actual control takes place via evcc. Discharge stop is realized via a scheduled grid charge with a target SoC of 10%. Alternatively, it can also be configured via Modbus. To do this, set the registers `2134,2142,2135,2136,2144,2137,2175` to the values `0,0,23,0,23,0,0,0,0`. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/ampere-amperestoragepro.mdx b/docs/devices-next/meters/ampere-amperestoragepro.mdx new file mode 100644 index 0000000000..6961a948db --- /dev/null +++ b/docs/devices-next/meters/ampere-amperestoragepro.mdx @@ -0,0 +1,179 @@ +--- +title: Ampere Ampere.StoragePro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampere Ampere.StoragePro + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/anker-micro-inverter.mdx b/docs/devices-next/meters/anker-micro-inverter.mdx new file mode 100644 index 0000000000..440d80e22e --- /dev/null +++ b/docs/devices-next/meters/anker-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Anker Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Anker Micro inverter + + + + + diff --git a/docs/devices-next/meters/apsystems-ez1.mdx b/docs/devices-next/meters/apsystems-ez1.mdx new file mode 100644 index 0000000000..a0acbca3db --- /dev/null +++ b/docs/devices-next/meters/apsystems-ez1.mdx @@ -0,0 +1,22 @@ +--- +title: APsystems EZ1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/apsystems-ez1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# APsystems EZ1 + + + + + diff --git a/docs/devices-next/meters/avm-fritzdect.mdx b/docs/devices-next/meters/avm-fritzdect.mdx new file mode 100644 index 0000000000..56e8148c14 --- /dev/null +++ b/docs/devices-next/meters/avm-fritzdect.mdx @@ -0,0 +1,44 @@ +--- +title: AVM FritzDECT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fritzdect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AVM FritzDECT + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/axitec-axihycon-12-15h.mdx b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx new file mode 100644 index 0000000000..fd0ece0833 --- /dev/null +++ b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -0,0 +1,120 @@ +--- +title: Axitec AXIhycon 12-15H +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Axitec AXIhycon 12-15H + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx new file mode 100644 index 0000000000..43fa4c33b7 --- /dev/null +++ b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -0,0 +1,62 @@ +--- +title: Bernecker Engineering MPM3PM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mpm3pm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bernecker Engineering MPM3PM + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/bgetech-ds100.mdx b/docs/devices-next/meters/bgetech-ds100.mdx new file mode 100644 index 0000000000..70a31f4e26 --- /dev/null +++ b/docs/devices-next/meters/bgetech-ds100.mdx @@ -0,0 +1,130 @@ +--- +title: BGEtech DS100 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ds100.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BGEtech DS100 + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/bgetech-ws100.mdx b/docs/devices-next/meters/bgetech-ws100.mdx new file mode 100644 index 0000000000..3565b4d584 --- /dev/null +++ b/docs/devices-next/meters/bgetech-ws100.mdx @@ -0,0 +1,130 @@ +--- +title: BGEtech WS100 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ws100.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BGEtech WS100 + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx new file mode 100644 index 0000000000..ee7c21405c --- /dev/null +++ b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -0,0 +1,54 @@ +--- +title: Bosch BPT-S 5 Hybrid +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bosch-bpt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bosch BPT-S 5 Hybrid + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/bosswerk-micro-inverter.mdx b/docs/devices-next/meters/bosswerk-micro-inverter.mdx new file mode 100644 index 0000000000..3e097c9564 --- /dev/null +++ b/docs/devices-next/meters/bosswerk-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Bosswerk Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bosswerk Micro inverter + + + + + diff --git a/docs/devices-next/meters/carlo-gavazzi-em110111112.mdx b/docs/devices-next/meters/carlo-gavazzi-em110111112.mdx new file mode 100644 index 0000000000..2c0f809f50 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em110111112.mdx @@ -0,0 +1,62 @@ +--- +title: Carlo Gavazzi EM110/111/112 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM110/111/112 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/carlo-gavazzi-em24.mdx b/docs/devices-next/meters/carlo-gavazzi-em24.mdx new file mode 100644 index 0000000000..0261a2cfa8 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em24.mdx @@ -0,0 +1,65 @@ +--- +title: Carlo Gavazzi EM24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM24 + + + +EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/carlo-gavazzi-em24e1.mdx b/docs/devices-next/meters/carlo-gavazzi-em24e1.mdx new file mode 100644 index 0000000000..9deaa48d4c --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em24e1.mdx @@ -0,0 +1,52 @@ +--- +title: Carlo Gavazzi EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM24_E1 + + + +EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. +The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/carlo-gavazzi-em330em340.mdx b/docs/devices-next/meters/carlo-gavazzi-em330em340.mdx new file mode 100644 index 0000000000..40f8f37575 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em330em340.mdx @@ -0,0 +1,74 @@ +--- +title: Carlo Gavazzi EM330/EM340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM330/EM340 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/carlo-gavazzi-em530em540.mdx b/docs/devices-next/meters/carlo-gavazzi-em530em540.mdx new file mode 100644 index 0000000000..3138e7897f --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em530em540.mdx @@ -0,0 +1,74 @@ +--- +title: Carlo Gavazzi EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM530/EM540 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/carlo-gavazzi-et112.mdx b/docs/devices-next/meters/carlo-gavazzi-et112.mdx new file mode 100644 index 0000000000..03e0ba9f5d --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-et112.mdx @@ -0,0 +1,62 @@ +--- +title: Carlo Gavazzi ET112 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi ET112 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/carlo-gavazzi-et330et340.mdx b/docs/devices-next/meters/carlo-gavazzi-et330et340.mdx new file mode 100644 index 0000000000..487039c3ed --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-et330et340.mdx @@ -0,0 +1,74 @@ +--- +title: Carlo Gavazzi ET330/ET340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi ET330/ET340 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/cfos-powerbrain-meter.mdx b/docs/devices-next/meters/cfos-powerbrain-meter.mdx new file mode 100644 index 0000000000..4f8f0459bd --- /dev/null +++ b/docs/devices-next/meters/cfos-powerbrain-meter.mdx @@ -0,0 +1,29 @@ +--- +title: cFos PowerBrain Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cfos.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# cFos PowerBrain Meter + + + + + + + diff --git a/docs/devices-next/meters/demo-battery.mdx b/docs/devices-next/meters/demo-battery.mdx new file mode 100644 index 0000000000..b65fe9a5e6 --- /dev/null +++ b/docs/devices-next/meters/demo-battery.mdx @@ -0,0 +1,38 @@ +--- +title: Demo battery +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-battery.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Demo battery + + + +For demonstration purposes. Battery with a fixed set of values. + + + + diff --git a/docs/devices-next/meters/demo-meter.mdx b/docs/devices-next/meters/demo-meter.mdx new file mode 100644 index 0000000000..4e4c525ecc --- /dev/null +++ b/docs/devices-next/meters/demo-meter.mdx @@ -0,0 +1,97 @@ +--- +title: Demo meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Demo meter + + + +For demonstration purposes. Meter with a fixed set of values. + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx new file mode 100644 index 0000000000..a933df3bdd --- /dev/null +++ b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: Deye 3p hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye 3p hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx new file mode 100644 index 0000000000..d28f600321 --- /dev/null +++ b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -0,0 +1,185 @@ +--- +title: Deye hp3 hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye hp3 hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/deye-micro-inverter.mdx b/docs/devices-next/meters/deye-micro-inverter.mdx new file mode 100644 index 0000000000..ecdbcc3b76 --- /dev/null +++ b/docs/devices-next/meters/deye-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Deye Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye Micro inverter + + + + + diff --git a/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx new file mode 100644 index 0000000000..1e91b51b28 --- /dev/null +++ b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: Deye Storage (hybrid) inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye Storage (hybrid) inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/deye-string-inverter.mdx b/docs/devices-next/meters/deye-string-inverter.mdx new file mode 100644 index 0000000000..a2c6861fe6 --- /dev/null +++ b/docs/devices-next/meters/deye-string-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Deye String inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye String inverter + + + + + diff --git a/docs/devices-next/meters/discovergy.mdx b/docs/devices-next/meters/discovergy.mdx new file mode 100644 index 0000000000..9465b60a25 --- /dev/null +++ b/docs/devices-next/meters/discovergy.mdx @@ -0,0 +1,42 @@ +--- +title: Discovergy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/discovergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Discovergy + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/dsmr.mdx b/docs/devices-next/meters/dsmr.mdx new file mode 100644 index 0000000000..626d791b0f --- /dev/null +++ b/docs/devices-next/meters/dsmr.mdx @@ -0,0 +1,30 @@ +--- +title: DSMR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dsmr.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DSMR + + + + + diff --git a/docs/devices-next/meters/dzg-dvh4013.mdx b/docs/devices-next/meters/dzg-dvh4013.mdx new file mode 100644 index 0000000000..2aa2c5fae7 --- /dev/null +++ b/docs/devices-next/meters/dzg-dvh4013.mdx @@ -0,0 +1,34 @@ +--- +title: DZG DVH4013 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dzg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DZG DVH4013 + + + + + diff --git a/docs/devices-next/meters/e3dc.mdx b/docs/devices-next/meters/e3dc.mdx new file mode 100644 index 0000000000..ab879e5e70 --- /dev/null +++ b/docs/devices-next/meters/e3dc.mdx @@ -0,0 +1,97 @@ +--- +title: E3/DC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC + + + +Username and password are identical to Web Portal or My E3/DC App access. Key (=RSCP-Password) must be set in the E3/DC system at Personalize/User Profile. The IP adresses of evcc and E3/DC system must be in the same subnet. + +**Note**: Active battery control will override Smart-Power/Operating Range settings. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/eastron-sdm120-modbus.mdx b/docs/devices-next/meters/eastron-sdm120-modbus.mdx new file mode 100644 index 0000000000..89196e71b9 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm120-modbus.mdx @@ -0,0 +1,84 @@ +--- +title: Eastron SDM120-Modbus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm120.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM120-Modbus + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/eastron-sdm220230.mdx b/docs/devices-next/meters/eastron-sdm220230.mdx new file mode 100644 index 0000000000..01c6237991 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm220230.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM220/230 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM220/230 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/eastron-sdm630-modbus.mdx b/docs/devices-next/meters/eastron-sdm630-modbus.mdx new file mode 100644 index 0000000000..c8c4de88e3 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm630-modbus.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM630-Modbus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM630-Modbus + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/eastron-sdm72d-m.mdx b/docs/devices-next/meters/eastron-sdm72d-m.mdx new file mode 100644 index 0000000000..cd58bb9e71 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm72d-m.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM72D-M +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm72.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM72D-M + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/eastron-sdm72dm-v2.mdx b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx new file mode 100644 index 0000000000..6368042b3f --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM72DM-V2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM72DM-V2 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/enphase-iq-envoy.mdx b/docs/devices-next/meters/enphase-iq-envoy.mdx new file mode 100644 index 0000000000..214fa28ccb --- /dev/null +++ b/docs/devices-next/meters/enphase-iq-envoy.mdx @@ -0,0 +1,76 @@ +--- +title: Enphase IQ Envoy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/enphase.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Enphase IQ Envoy + + + +Only batteries of type "AC Battery" are currently supported by Enphase-API. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/esphome-dlms-meter-austria.mdx b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx new file mode 100644 index 0000000000..903fac0bd9 --- /dev/null +++ b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -0,0 +1,32 @@ +--- +title: ESPHome DLMS Meter Austria +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/esphome-dlms-austria.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ESPHome DLMS Meter Austria + + + +Requires an ESPHome node running the `dlms_meter` component (e.g., from `github://SimonFischer04/esphome@dlms-meter`), +configured for Austrian DLMS meters. + + + + diff --git a/docs/devices-next/meters/esphome-dsmr.mdx b/docs/devices-next/meters/esphome-dsmr.mdx new file mode 100644 index 0000000000..67a15d0e68 --- /dev/null +++ b/docs/devices-next/meters/esphome-dsmr.mdx @@ -0,0 +1,28 @@ +--- +title: ESPHome DSMR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ESPHome DSMR + + + + + diff --git a/docs/devices-next/meters/fenecon.mdx b/docs/devices-next/meters/fenecon.mdx new file mode 100644 index 0000000000..2b884218ac --- /dev/null +++ b/docs/devices-next/meters/fenecon.mdx @@ -0,0 +1,73 @@ +--- +title: FENECON +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FENECON + + + +A commercial license is required for FEMS FENECON systems for active battery control. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..10ab1a56f7 --- /dev/null +++ b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -0,0 +1,74 @@ +--- +title: FoxESS H1 Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FoxESS H1 Series Hybrid Inverter + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..cc9f33352e --- /dev/null +++ b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: FoxESS H3 Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FoxESS H3 Series Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..1a1a3f17b2 --- /dev/null +++ b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: FoxESS H3-Smart Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3-smart.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FoxESS H3-Smart Series Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/fronius-ohmpilot.mdx b/docs/devices-next/meters/fronius-ohmpilot.mdx new file mode 100644 index 0000000000..c723d09994 --- /dev/null +++ b/docs/devices-next/meters/fronius-ohmpilot.mdx @@ -0,0 +1,28 @@ +--- +title: Fronius Ohmpilot +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-ohmpilot.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Ohmpilot + + + + + diff --git a/docs/devices-next/meters/fronius-primo-gen24-plus.mdx b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx new file mode 100644 index 0000000000..06cbb41124 --- /dev/null +++ b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -0,0 +1,73 @@ +--- +title: Fronius Primo GEN24 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Primo GEN24 Plus + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx new file mode 100644 index 0000000000..2dd20b9c8d --- /dev/null +++ b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -0,0 +1,48 @@ +--- +title: Fronius Smartmeter (via Inverter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Smartmeter (via Inverter) + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/fronius-solar-api-v1.mdx b/docs/devices-next/meters/fronius-solar-api-v1.mdx new file mode 100644 index 0000000000..1968483c3e --- /dev/null +++ b/docs/devices-next/meters/fronius-solar-api-v1.mdx @@ -0,0 +1,69 @@ +--- +title: Fronius Solar API V1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-solarapi-v1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Solar API V1 + + + +Solar API should only be used as fallback. Integration via Modbus is preferred. + +Username and password are only required for active battery control. + +**Attention**: Active battery control should only be used if no other settings for time-dependent battery control were made in the inverter configuration under "Energy Management" - "Battery Management", as existing settings will be overwritten. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/fronius-symo-gen24-plus.mdx b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx new file mode 100644 index 0000000000..8b2fee86e9 --- /dev/null +++ b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -0,0 +1,73 @@ +--- +title: Fronius Symo GEN24 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Symo GEN24 Plus + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx new file mode 100644 index 0000000000..1cf1c61c77 --- /dev/null +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -0,0 +1,120 @@ +--- +title: Ginlong Solis Hybrid Inverter (RHI series) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ginlong Solis Hybrid Inverter (RHI series) + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx new file mode 100644 index 0000000000..e491558b99 --- /dev/null +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -0,0 +1,120 @@ +--- +title: Ginlong Solis Hybrid Inverter (S Series) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ginlong Solis Hybrid Inverter (S Series) + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/ginlong-solis-inverter.mdx b/docs/devices-next/meters/ginlong-solis-inverter.mdx new file mode 100644 index 0000000000..2ea9f54b02 --- /dev/null +++ b/docs/devices-next/meters/ginlong-solis-inverter.mdx @@ -0,0 +1,62 @@ +--- +title: Ginlong Solis Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ginlong Solis Inverter + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/go-e-controller.mdx b/docs/devices-next/meters/go-e-controller.mdx new file mode 100644 index 0000000000..7cb9c07265 --- /dev/null +++ b/docs/devices-next/meters/go-e-controller.mdx @@ -0,0 +1,38 @@ +--- +title: go-e Controller +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/go-e-controller.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Controller + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx b/docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx new file mode 100644 index 0000000000..71a3d1d055 --- /dev/null +++ b/docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx @@ -0,0 +1,155 @@ +--- +title: GoodWe ET/EH/BH/BT Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe ET/EH/BH/BT Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx new file mode 100644 index 0000000000..ea89fb96a6 --- /dev/null +++ b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -0,0 +1,48 @@ +--- +title: GoodWe GoodWe over Wifi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-wifi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe GoodWe over Wifi + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/goodwe-sdtdt-inverter.mdx b/docs/devices-next/meters/goodwe-sdtdt-inverter.mdx new file mode 100644 index 0000000000..0809d0ea25 --- /dev/null +++ b/docs/devices-next/meters/goodwe-sdtdt-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: GoodWe SDT/DT Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe SDT/DT Inverter + + + + + diff --git a/docs/devices-next/meters/growatt-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-hybrid-inverter.mdx new file mode 100644 index 0000000000..80c237c732 --- /dev/null +++ b/docs/devices-next/meters/growatt-hybrid-inverter.mdx @@ -0,0 +1,156 @@ +--- +title: Growatt Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Growatt Hybrid Inverter + + + +To use the active battery control, a one-time manual setup is necessary. +The modbus registers `1100, 1101, 1102` need to be set to the values `0, 5947, 0` at the same time (via "write multiple", FC 16). +This can be done by e.g. using the [Modbus CLI](https://github.com/favalex/modbus-cli): `modbus [...] H@1100=0 H@1101=5947 H@1102=0`. +The active battery control uses the first "Battery first" timeslot, so it cannot be used otherwise. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx new file mode 100644 index 0000000000..bd80b22b42 --- /dev/null +++ b/docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx @@ -0,0 +1,150 @@ +--- +title: Growatt TL-X(H) Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Growatt TL-X(H) Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/homematic-ip.mdx b/docs/devices-next/meters/homematic-ip.mdx new file mode 100644 index 0000000000..f7d4042c5a --- /dev/null +++ b/docs/devices-next/meters/homematic-ip.mdx @@ -0,0 +1,90 @@ +--- +title: Homematic IP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homematic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Homematic IP + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/homewizard-kwh-meter.mdx b/docs/devices-next/meters/homewizard-kwh-meter.mdx new file mode 100644 index 0000000000..5fa5226da4 --- /dev/null +++ b/docs/devices-next/meters/homewizard-kwh-meter.mdx @@ -0,0 +1,38 @@ +--- +title: HomeWizard kWh Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard-kwh.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HomeWizard kWh Meter + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx new file mode 100644 index 0000000000..3ccdd6bb8e --- /dev/null +++ b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -0,0 +1,22 @@ +--- +title: HomeWizard Wi-Fi P1 Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HomeWizard Wi-Fi P1 Meter + + + + + diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx new file mode 100644 index 0000000000..fe4d31452e --- /dev/null +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -0,0 +1,23 @@ +--- +title: Hoymiles HM & HMS Series (via AhoyDTU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-ahoydtu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hoymiles HM & HMS Series (via AhoyDTU) + + + + Inverter #[ID], optional`} /> + diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx new file mode 100644 index 0000000000..002634479b --- /dev/null +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -0,0 +1,22 @@ +--- +title: Hoymiles HM & HMS Series (via OpenDTU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-opendtu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hoymiles HM & HMS Series (via OpenDTU) + + + + + diff --git a/docs/devices-next/meters/huawei-emma.mdx b/docs/devices-next/meters/huawei-emma.mdx new file mode 100644 index 0000000000..32031c5d8d --- /dev/null +++ b/docs/devices-next/meters/huawei-emma.mdx @@ -0,0 +1,74 @@ +--- +title: Huawei EMMA +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-emma.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei EMMA + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/huawei-smartlogger.mdx b/docs/devices-next/meters/huawei-smartlogger.mdx new file mode 100644 index 0000000000..c9ee4b2adb --- /dev/null +++ b/docs/devices-next/meters/huawei-smartlogger.mdx @@ -0,0 +1,104 @@ +--- +title: Huawei SmartLogger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-smartlogger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SmartLogger + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/huawei-sun2000-sdongle.mdx b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx new file mode 100644 index 0000000000..86b5ce911b --- /dev/null +++ b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -0,0 +1,32 @@ +--- +title: Huawei SUN2000 (SDongle) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-dongle.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SUN2000 (SDongle) + + + +Needs "Modbus/TCP". Activation using "maintenance access" within the communication settings of the inverter. +See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + + + + diff --git a/docs/devices-next/meters/huawei-sun2000.mdx b/docs/devices-next/meters/huawei-sun2000.mdx new file mode 100644 index 0000000000..f855498d80 --- /dev/null +++ b/docs/devices-next/meters/huawei-sun2000.mdx @@ -0,0 +1,189 @@ +--- +title: Huawei SUN2000 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-sun2000.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SUN2000 + + + +Grid and Battery require the PowerSensor. +Modbus/TCP requires activation using "maintenance access" within the communication settings of the inverter. +See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/iammeter-wem3080.mdx b/docs/devices-next/meters/iammeter-wem3080.mdx new file mode 100644 index 0000000000..6f46a62192 --- /dev/null +++ b/docs/devices-next/meters/iammeter-wem3080.mdx @@ -0,0 +1,52 @@ +--- +title: IAMMETER WEM3080 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IAMMETER WEM3080 + + + +3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. +See https://www.iammeter.com/newsshow/net-energy-metering + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx b/docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx new file mode 100644 index 0000000000..12b5100e10 --- /dev/null +++ b/docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx @@ -0,0 +1,52 @@ +--- +title: IAMMETER WEM3080T/WEM3046T/WEM3050T +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IAMMETER WEM3080T/WEM3046T/WEM3050T + + + +3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. +See https://www.iammeter.com/newsshow/net-energy-metering + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/igen-tech-solarman-logger.mdx b/docs/devices-next/meters/igen-tech-solarman-logger.mdx new file mode 100644 index 0000000000..8840cadc89 --- /dev/null +++ b/docs/devices-next/meters/igen-tech-solarman-logger.mdx @@ -0,0 +1,24 @@ +--- +title: IGEN Tech Solarman Logger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarman.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IGEN Tech Solarman Logger + + + + + diff --git a/docs/devices-next/meters/index.mdx b/docs/devices-next/meters/index.mdx new file mode 100644 index 0000000000..16c41c852f --- /dev/null +++ b/docs/devices-next/meters/index.mdx @@ -0,0 +1,1626 @@ +--- +title: Meters +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Meters + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/docs/devices-next/meters/inepro-pro380-mod.mdx b/docs/devices-next/meters/inepro-pro380-mod.mdx new file mode 100644 index 0000000000..ff07157d4a --- /dev/null +++ b/docs/devices-next/meters/inepro-pro380-mod.mdx @@ -0,0 +1,62 @@ +--- +title: inepro PRO380-MOD +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/inepro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# inepro PRO380-MOD + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/iometer.mdx b/docs/devices-next/meters/iometer.mdx new file mode 100644 index 0000000000..dd0312178b --- /dev/null +++ b/docs/devices-next/meters/iometer.mdx @@ -0,0 +1,22 @@ +--- +title: IOmeter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iometer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IOmeter + + + + + diff --git a/docs/devices-next/meters/janitza-b-series-umg-series.mdx b/docs/devices-next/meters/janitza-b-series-umg-series.mdx new file mode 100644 index 0000000000..e997390c3c --- /dev/null +++ b/docs/devices-next/meters/janitza-b-series-umg-series.mdx @@ -0,0 +1,74 @@ +--- +title: Janitza B series, UMG series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Janitza B series, UMG series + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/keba-kecontact-e10.mdx b/docs/devices-next/meters/keba-kecontact-e10.mdx new file mode 100644 index 0000000000..95a5cde714 --- /dev/null +++ b/docs/devices-next/meters/keba-kecontact-e10.mdx @@ -0,0 +1,27 @@ +--- +title: KEBA KeContact E10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/keba-kecontact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact E10 + + + + + diff --git a/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx new file mode 100644 index 0000000000..175faa5299 --- /dev/null +++ b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -0,0 +1,74 @@ +--- +title: Kostal Energy Meter C (KEM-C) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Energy Meter C (KEM-C) + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx new file mode 100644 index 0000000000..e41937076f --- /dev/null +++ b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -0,0 +1,62 @@ +--- +title: Kostal Energy Meter P (KEM-P) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Energy Meter P (KEM-P) + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/kostal-piko-hybrid.mdx b/docs/devices-next/meters/kostal-piko-hybrid.mdx new file mode 100644 index 0000000000..54aeb380fd --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-hybrid.mdx @@ -0,0 +1,54 @@ +--- +title: Kostal Piko Hybrid +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko Hybrid + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/kostal-piko-legacy.mdx b/docs/devices-next/meters/kostal-piko-legacy.mdx new file mode 100644 index 0000000000..a828caff51 --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-legacy.mdx @@ -0,0 +1,24 @@ +--- +title: Kostal Piko (legacy) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-legacy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko (legacy) + + + + + diff --git a/docs/devices-next/meters/kostal-piko-mp-plus.mdx b/docs/devices-next/meters/kostal-piko-mp-plus.mdx new file mode 100644 index 0000000000..5075b80f29 --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-mp-plus.mdx @@ -0,0 +1,22 @@ +--- +title: Kostal Piko MP Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko MP Plus + + + + + diff --git a/docs/devices-next/meters/kostal-piko-piko-ba.mdx b/docs/devices-next/meters/kostal-piko-piko-ba.mdx new file mode 100644 index 0000000000..60d38e4df1 --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-piko-ba.mdx @@ -0,0 +1,38 @@ +--- +title: Kostal Piko, Piko BA +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko, Piko BA + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx new file mode 100644 index 0000000000..eeb43849db --- /dev/null +++ b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -0,0 +1,80 @@ +--- +title: Kostal Plenticore Hybrid, incl. grid charging of the house battery +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore-gen2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Plenticore Hybrid, incl. grid charging of the house battery + + + +Only a single system may access the inverter! For active battery control, the feature external battery control via modbus must be activated using installer access. **_Can basically be used for various inverter generations (G1/G2/G3)._** +**The function for grid charging the battery is available using this template, but is currently incompatible with some older inverters - _test carefully_!** +_see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx new file mode 100644 index 0000000000..b677be849c --- /dev/null +++ b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -0,0 +1,82 @@ +--- +title: Kostal Plenticore Hybrid +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Plenticore Hybrid + + + +Only a single system may access the inverter! For active battery control the function external battery control via Modbus must be activated using installer access. +**Grid charging is not available!** _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx new file mode 100644 index 0000000000..a33a15612d --- /dev/null +++ b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -0,0 +1,30 @@ +--- +title: Kostal Smart Energy Meter (via inverter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Smart Energy Meter (via inverter) + + + +The energy meter must be installed in sensor position 2 (grid connection). Sensor position 1 (House consumption) is not supported. + + + + diff --git a/docs/devices-next/meters/kostal-smart-energy-meter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter.mdx new file mode 100644 index 0000000000..ef381a7bf3 --- /dev/null +++ b/docs/devices-next/meters/kostal-smart-energy-meter.mdx @@ -0,0 +1,27 @@ +--- +title: Kostal Smart Energy Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Smart Energy Meter + + + + + diff --git a/docs/devices-next/meters/lg-ess-home-15.mdx b/docs/devices-next/meters/lg-ess-home-15.mdx new file mode 100644 index 0000000000..5a5c67f0be --- /dev/null +++ b/docs/devices-next/meters/lg-ess-home-15.mdx @@ -0,0 +1,79 @@ +--- +title: LG ESS Home 15 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-15.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LG ESS Home 15 + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/lg-ess-home-810.mdx b/docs/devices-next/meters/lg-ess-home-810.mdx new file mode 100644 index 0000000000..a1b72aeed6 --- /dev/null +++ b/docs/devices-next/meters/lg-ess-home-810.mdx @@ -0,0 +1,82 @@ +--- +title: LG ESS Home 8/10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LG ESS Home 8/10 + + + +To use the battery control, a firmware version greater than or equal to 10.05.7433 / R2155 is required + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/loxone-miniserver.mdx b/docs/devices-next/meters/loxone-miniserver.mdx new file mode 100644 index 0000000000..61741fc010 --- /dev/null +++ b/docs/devices-next/meters/loxone-miniserver.mdx @@ -0,0 +1,74 @@ +--- +title: Loxone Miniserver +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/loxone.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Loxone Miniserver + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx new file mode 100644 index 0000000000..e80f29828c --- /dev/null +++ b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -0,0 +1,84 @@ +--- +title: M-TEC Energy Butler GEN2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# M-TEC Energy Butler GEN2 + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx new file mode 100644 index 0000000000..38cf0bf105 --- /dev/null +++ b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -0,0 +1,126 @@ +--- +title: M-TEC Energy Butler GEN3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# M-TEC Energy Butler GEN3 + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/marstek-venus-battery-storage.mdx b/docs/devices-next/meters/marstek-venus-battery-storage.mdx new file mode 100644 index 0000000000..5e68739167 --- /dev/null +++ b/docs/devices-next/meters/marstek-venus-battery-storage.mdx @@ -0,0 +1,57 @@ +--- +title: Marstek Venus Battery Storage +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/marstek-venus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Marstek Venus Battery Storage + + + + + diff --git a/docs/devices-next/meters/mhendriks-p1-dongle.mdx b/docs/devices-next/meters/mhendriks-p1-dongle.mdx new file mode 100644 index 0000000000..37377a34be --- /dev/null +++ b/docs/devices-next/meters/mhendriks-p1-dongle.mdx @@ -0,0 +1,28 @@ +--- +title: mhendriks P1 dongle +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# mhendriks P1 dongle + + + + + diff --git a/docs/devices-next/meters/my-pv-ac-elwa-2.mdx b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx new file mode 100644 index 0000000000..468cf368b4 --- /dev/null +++ b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -0,0 +1,22 @@ +--- +title: my-PV AC ELWA 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC ELWA 2 + + + + + diff --git a/docs/devices-next/meters/my-pv-ac-elwa-e.mdx b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx new file mode 100644 index 0000000000..acec8a304a --- /dev/null +++ b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -0,0 +1,22 @@ +--- +title: my-PV AC ELWA-E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-e.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC ELWA-E + + + + + diff --git a/docs/devices-next/meters/my-pv-acthor.mdx b/docs/devices-next/meters/my-pv-acthor.mdx new file mode 100644 index 0000000000..84c0712713 --- /dev/null +++ b/docs/devices-next/meters/my-pv-acthor.mdx @@ -0,0 +1,22 @@ +--- +title: my-PV AC•THOR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR + + + + + diff --git a/docs/devices-next/meters/my-pv-wifi-meter.mdx b/docs/devices-next/meters/my-pv-wifi-meter.mdx new file mode 100644 index 0000000000..50b9dea362 --- /dev/null +++ b/docs/devices-next/meters/my-pv-wifi-meter.mdx @@ -0,0 +1,27 @@ +--- +title: my-PV WiFi Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mypv-wifi-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV WiFi Meter + + + + + diff --git a/docs/devices-next/meters/mystrom-switch.mdx b/docs/devices-next/meters/mystrom-switch.mdx new file mode 100644 index 0000000000..af9907f637 --- /dev/null +++ b/docs/devices-next/meters/mystrom-switch.mdx @@ -0,0 +1,38 @@ +--- +title: myStrom Switch +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mystrom.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# myStrom Switch + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/openems.mdx b/docs/devices-next/meters/openems.mdx new file mode 100644 index 0000000000..41630a404f --- /dev/null +++ b/docs/devices-next/meters/openems.mdx @@ -0,0 +1,73 @@ +--- +title: OpenEMS +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OpenEMS + + + +A commercial license is required for FEMS FENECON systems for active battery control. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/orno-or-we-516-or-we-517.mdx b/docs/devices-next/meters/orno-or-we-516-or-we-517.mdx new file mode 100644 index 0000000000..2ff44ce2d6 --- /dev/null +++ b/docs/devices-next/meters/orno-or-we-516-or-we-517.mdx @@ -0,0 +1,62 @@ +--- +title: Orno OR-WE-516, OR-WE-517 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Orno OR-WE-516, OR-WE-517 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/p1monitor.mdx b/docs/devices-next/meters/p1monitor.mdx new file mode 100644 index 0000000000..d56dfbd294 --- /dev/null +++ b/docs/devices-next/meters/p1monitor.mdx @@ -0,0 +1,22 @@ +--- +title: P1Monitor P1 Monitor +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# P1Monitor P1 Monitor + + + + + diff --git a/docs/devices-next/meters/plexlog.mdx b/docs/devices-next/meters/plexlog.mdx new file mode 100644 index 0000000000..269d0fd2b4 --- /dev/null +++ b/docs/devices-next/meters/plexlog.mdx @@ -0,0 +1,77 @@ +--- +title: Plexlog +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/plexlog.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Plexlog + + + +The values are updated approximately every 15 seconds, hence the evcc `interval` should not be less than 30 seconds. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/powerdog.mdx b/docs/devices-next/meters/powerdog.mdx new file mode 100644 index 0000000000..9446f980b4 --- /dev/null +++ b/docs/devices-next/meters/powerdog.mdx @@ -0,0 +1,48 @@ +--- +title: Powerdog +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerdog.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Powerdog + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/powerfox-poweropti.mdx b/docs/devices-next/meters/powerfox-poweropti.mdx new file mode 100644 index 0000000000..1e0ac55700 --- /dev/null +++ b/docs/devices-next/meters/powerfox-poweropti.mdx @@ -0,0 +1,54 @@ +--- +title: Powerfox Poweropti +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerfox-poweropti.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Powerfox Poweropti + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx new file mode 100644 index 0000000000..8e32f43c27 --- /dev/null +++ b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -0,0 +1,63 @@ +--- +title: QCells Hybrid-Inverter (Cloud) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/qcells-hybrid-cloud.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# QCells Hybrid-Inverter (Cloud) + + + +The QCells hybrid inverter has to be registered in the QCellsCloud. + +**Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx b/docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx new file mode 100644 index 0000000000..8e9f578b3c --- /dev/null +++ b/docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx @@ -0,0 +1,183 @@ +--- +title: Qcells Q.HOME ESS HYB-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME ESS HYB-G3 + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/rct-power.mdx b/docs/devices-next/meters/rct-power.mdx new file mode 100644 index 0000000000..b93a9d1fa1 --- /dev/null +++ b/docs/devices-next/meters/rct-power.mdx @@ -0,0 +1,77 @@ +--- +title: RCT Power +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/rct-power.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# RCT Power + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx b/docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx new file mode 100644 index 0000000000..77e3fec27f --- /dev/null +++ b/docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx @@ -0,0 +1,62 @@ +--- +title: Saia-Burgess Controls ALE3, AWD3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Saia-Burgess Controls ALE3, AWD3 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx new file mode 100644 index 0000000000..99a8fdab21 --- /dev/null +++ b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -0,0 +1,78 @@ +--- +title: SAJ H1 Series Hybrid Solar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAJ H1 Series Hybrid Solar Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx new file mode 100644 index 0000000000..c4bbd2fd41 --- /dev/null +++ b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: SAJ H2 Series Hybrid Solar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAJ H2 Series Hybrid Solar Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx new file mode 100644 index 0000000000..be836300ca --- /dev/null +++ b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -0,0 +1,34 @@ +--- +title: SAJ R5 Series Solar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-r5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAJ R5 Series Solar Inverter + + + + + diff --git a/docs/devices-next/meters/sax-homespeicher.mdx b/docs/devices-next/meters/sax-homespeicher.mdx new file mode 100644 index 0000000000..8fde7219f6 --- /dev/null +++ b/docs/devices-next/meters/sax-homespeicher.mdx @@ -0,0 +1,48 @@ +--- +title: SAX Homespeicher +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAX Homespeicher + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx new file mode 100644 index 0000000000..68e36d98ce --- /dev/null +++ b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -0,0 +1,62 @@ +--- +title: Schneider Electric iEM3xxx Modbus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/schneider-iem3000.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Schneider Electric iEM3xxx Modbus + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/senec-home.mdx b/docs/devices-next/meters/senec-home.mdx new file mode 100644 index 0000000000..a3c851b442 --- /dev/null +++ b/docs/devices-next/meters/senec-home.mdx @@ -0,0 +1,58 @@ +--- +title: SENEC .Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senec-home.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SENEC .Home + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx b/docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx new file mode 100644 index 0000000000..d26588fdbf --- /dev/null +++ b/docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx @@ -0,0 +1,27 @@ +--- +title: Senergy SE 4/5/6KTL-S1/G2 Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Senergy SE 4/5/6KTL-S1/G2 Inverter + + + + + diff --git a/docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx b/docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx new file mode 100644 index 0000000000..c57cbb81e0 --- /dev/null +++ b/docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx @@ -0,0 +1,57 @@ +--- +title: Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/shelly-3em.mdx b/docs/devices-next/meters/shelly-3em.mdx new file mode 100644 index 0000000000..e225573d88 --- /dev/null +++ b/docs/devices-next/meters/shelly-3em.mdx @@ -0,0 +1,69 @@ +--- +title: Shelly 3EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-3em.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 3EM + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/shelly-pro-3-em.mdx b/docs/devices-next/meters/shelly-pro-3-em.mdx new file mode 100644 index 0000000000..b65782f38b --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-3-em.mdx @@ -0,0 +1,54 @@ +--- +title: Shelly Pro 3 EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-pro-3em.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 3 EM + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/siemens-7kt1665.mdx b/docs/devices-next/meters/siemens-7kt1665.mdx new file mode 100644 index 0000000000..a9815304c2 --- /dev/null +++ b/docs/devices-next/meters/siemens-7kt1665.mdx @@ -0,0 +1,74 @@ +--- +title: Siemens 7KT1665 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-7kt1665.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens 7KT1665 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/siemens-junelight-smart-battery.mdx b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx new file mode 100644 index 0000000000..b25f6fee52 --- /dev/null +++ b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -0,0 +1,77 @@ +--- +title: Siemens Junelight Smart Battery +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-junelight.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens Junelight Smart Battery + + + +The battery has to be set to Loxone with the installer account. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/siemens-pac-2200.mdx b/docs/devices-next/meters/siemens-pac-2200.mdx new file mode 100644 index 0000000000..cd228bffb5 --- /dev/null +++ b/docs/devices-next/meters/siemens-pac-2200.mdx @@ -0,0 +1,74 @@ +--- +title: Siemens PAC 2200 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-pac2200.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens PAC 2200 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx b/docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx new file mode 100644 index 0000000000..000b5aa928 --- /dev/null +++ b/docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx @@ -0,0 +1,65 @@ +--- +title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC + + + +The electrician needs to enable the Modbus via TCP/IP in their service app before the setup is functional. This is not available in the customers mySigen app. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sma-data-manager.mdx b/docs/devices-next/meters/sma-data-manager.mdx new file mode 100644 index 0000000000..9361cf11c5 --- /dev/null +++ b/docs/devices-next/meters/sma-data-manager.mdx @@ -0,0 +1,77 @@ +--- +title: SMA Data Manager +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-data-manager.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Data Manager + + + +In the web interface of the SMA Data Manager you need to activate "Modbus Server activated" in the section "External communication". + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sma-energy-meter.mdx b/docs/devices-next/meters/sma-energy-meter.mdx new file mode 100644 index 0000000000..9e605b4070 --- /dev/null +++ b/docs/devices-next/meters/sma-energy-meter.mdx @@ -0,0 +1,50 @@ +--- +title: SMA Energy Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-energy-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Energy Meter + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sma-inverter-speedwire.mdx b/docs/devices-next/meters/sma-inverter-speedwire.mdx new file mode 100644 index 0000000000..89de5718fd --- /dev/null +++ b/docs/devices-next/meters/sma-inverter-speedwire.mdx @@ -0,0 +1,47 @@ +--- +title: SMA Inverter (Speedwire) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-speedwire.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Inverter (Speedwire) + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx new file mode 100644 index 0000000000..852ac254de --- /dev/null +++ b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -0,0 +1,72 @@ +--- +title: SMA Smart Energy Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Smart Energy Hybrid Inverter + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx new file mode 100644 index 0000000000..5d32ffaf65 --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx @@ -0,0 +1,40 @@ +--- +title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) + + + + + diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx new file mode 100644 index 0000000000..1e90164620 --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx @@ -0,0 +1,40 @@ +--- +title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) + + + + + diff --git a/docs/devices-next/meters/sma-sunny-home-manager-20.mdx b/docs/devices-next/meters/sma-sunny-home-manager-20.mdx new file mode 100644 index 0000000000..9de48da6c9 --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-home-manager-20.mdx @@ -0,0 +1,28 @@ +--- +title: SMA Sunny Home Manager 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Home Manager 2.0 + + + + + diff --git a/docs/devices-next/meters/sma-sunny-island-modbus.mdx b/docs/devices-next/meters/sma-sunny-island-modbus.mdx new file mode 100644 index 0000000000..34deb14402 --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-island-modbus.mdx @@ -0,0 +1,40 @@ +--- +title: SMA Sunny Island (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-si-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Island (Modbus) + + + + + diff --git a/docs/devices-next/meters/sma-webbox.mdx b/docs/devices-next/meters/sma-webbox.mdx new file mode 100644 index 0000000000..f10b8ce114 --- /dev/null +++ b/docs/devices-next/meters/sma-webbox.mdx @@ -0,0 +1,27 @@ +--- +title: SMA WebBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-webbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA WebBox + + + + + diff --git a/docs/devices-next/meters/sma-wechselrichter-modbus.mdx b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx new file mode 100644 index 0000000000..ab7199b1f5 --- /dev/null +++ b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -0,0 +1,27 @@ +--- +title: SMA Wechselrichter (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Wechselrichter (Modbus) + + + + + diff --git a/docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx b/docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx new file mode 100644 index 0000000000..b1e69f10a3 --- /dev/null +++ b/docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx @@ -0,0 +1,51 @@ +--- +title: Smartfox Box, Reg, Reg extended +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Box, Reg, Reg extended + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx b/docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx new file mode 100644 index 0000000000..812290df4b --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx @@ -0,0 +1,69 @@ +--- +title: Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx b/docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx new file mode 100644 index 0000000000..b756880eed --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar HYD 3…6K-EP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 3…6K-EP + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx b/docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx new file mode 100644 index 0000000000..566fe90bf7 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar HYD 5…20K-3PH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 5…20K-3PH + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx b/docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx new file mode 100644 index 0000000000..123d02bab2 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: SofarSolar Inverter, Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar Inverter, Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx b/docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx new file mode 100644 index 0000000000..1cd2aafbef --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar SOFAR 5…24KTL-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 5…24KTL-G3 + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx b/docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx new file mode 100644 index 0000000000..c5300ca81b --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar SOFAR 80…136KTL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 80…136KTL + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solaranzeige.mdx b/docs/devices-next/meters/solaranzeige.mdx new file mode 100644 index 0000000000..6eed5d6d9e --- /dev/null +++ b/docs/devices-next/meters/solaranzeige.mdx @@ -0,0 +1,64 @@ +--- +title: Solaranzeige Solaranzeige +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solaranzeige Solaranzeige + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solaredge-hybrid-inverter.mdx b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx new file mode 100644 index 0000000000..6ecafc9d28 --- /dev/null +++ b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -0,0 +1,186 @@ +--- +title: SolarEdge Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarEdge Hybrid Inverter + + + +Only one system can and may have a Modbus TCP connection to the inverter at the same time! +For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Remote". + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solaredge-inverter.mdx b/docs/devices-next/meters/solaredge-inverter.mdx new file mode 100644 index 0000000000..c013c75139 --- /dev/null +++ b/docs/devices-next/meters/solaredge-inverter.mdx @@ -0,0 +1,79 @@ +--- +title: SolarEdge Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarEdge Inverter + + + +Only one system may access the inverter! + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solarlog.mdx b/docs/devices-next/meters/solarlog.mdx new file mode 100644 index 0000000000..2d94cec90b --- /dev/null +++ b/docs/devices-next/meters/solarlog.mdx @@ -0,0 +1,44 @@ +--- +title: Solarlog +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarlog.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarlog + + + +We recommend to use this device for grid power values only, if no other device is available providing this data. +If you have a home battery installed, please do not use this device at all for grid power values. + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx b/docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx new file mode 100644 index 0000000000..59a26af390 --- /dev/null +++ b/docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx @@ -0,0 +1,101 @@ +--- +title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax MAX.STORAGE / MAX.STORAGE Ultimate + + + +For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solarmax-solarmax-smt.mdx b/docs/devices-next/meters/solarmax-solarmax-smt.mdx new file mode 100644 index 0000000000..5b22bd5fb9 --- /dev/null +++ b/docs/devices-next/meters/solarmax-solarmax-smt.mdx @@ -0,0 +1,27 @@ +--- +title: SolarMax SolarMax SMT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-smt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax SolarMax SMT + + + + + diff --git a/docs/devices-next/meters/solarmax-sp-series-inverter.mdx b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx new file mode 100644 index 0000000000..bf77b4110b --- /dev/null +++ b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -0,0 +1,27 @@ +--- +title: SolarMax SP Series Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax SP Series Inverter + + + + + diff --git a/docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx b/docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx new file mode 100644 index 0000000000..e0c50e1af2 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx @@ -0,0 +1,54 @@ +--- +title: Solarwatt EnergyManager, EnergyManager Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt EnergyManager, EnergyManager Pro + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solarwatt-manager-flex.mdx b/docs/devices-next/meters/solarwatt-manager-flex.mdx new file mode 100644 index 0000000000..83d149b69f --- /dev/null +++ b/docs/devices-next/meters/solarwatt-manager-flex.mdx @@ -0,0 +1,57 @@ +--- +title: Solarwatt Manager flex +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-flex.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt Manager flex + + + +Combines data of all connected PV inverters or batteries. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx new file mode 100644 index 0000000000..107f04ea22 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -0,0 +1,58 @@ +--- +title: Solarwatt MyReserve Matrix (LAN oder PowerGateway) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-myreserve-matrix.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt MyReserve Matrix (LAN oder PowerGateway) + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solarwatt-myreserve.mdx b/docs/devices-next/meters/solarwatt-myreserve.mdx new file mode 100644 index 0000000000..cc22037ed8 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-myreserve.mdx @@ -0,0 +1,54 @@ +--- +title: Solarwatt MyReserve +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt MyReserve + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx new file mode 100644 index 0000000000..b248b2c9bc --- /dev/null +++ b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -0,0 +1,63 @@ +--- +title: Solax Hybrid-Inverter (Cloud) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-hybrid-cloud.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax Hybrid-Inverter (Cloud) + + + +The Solax hybrid inverter has to be registered in the SolaxCloud. + +**Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. + + + + + + Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of \`tokenID\` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number`} /> + + + + + Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of \`tokenID\` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number`} /> + + + + + Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of \`tokenID\` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number`} advanced={`meters: + - name: my_battery + type: template + template: solax-hybrid-cloud + usage: battery + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of \`tokenID\` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + capacity: 50 # Battery capacity (kWh), optional`} /> + + + + diff --git a/docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx b/docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx new file mode 100644 index 0000000000..0873052f76 --- /dev/null +++ b/docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx @@ -0,0 +1,183 @@ +--- +title: Solax Hybrid X1/X3 G3/G4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax Hybrid X1/X3 G3/G4 + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/solax-inverter-cloud.mdx b/docs/devices-next/meters/solax-inverter-cloud.mdx new file mode 100644 index 0000000000..b7a9d8eb54 --- /dev/null +++ b/docs/devices-next/meters/solax-inverter-cloud.mdx @@ -0,0 +1,28 @@ +--- +title: Solax Inverter (Cloud) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-inverter-cloud.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax Inverter (Cloud) + + + +The Solax inverter has to be registered in the SolaxCloud. + +**Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. + + + Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of \`tokenID\` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number`} /> + diff --git a/docs/devices-next/meters/solinteng.mdx b/docs/devices-next/meters/solinteng.mdx new file mode 100644 index 0000000000..3dfe513494 --- /dev/null +++ b/docs/devices-next/meters/solinteng.mdx @@ -0,0 +1,139 @@ +--- +title: Solinteng +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solinteng + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx b/docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx new file mode 100644 index 0000000000..27a377851f --- /dev/null +++ b/docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx @@ -0,0 +1,74 @@ +--- +title: Sonnen comfort, eco 5, eco 6, oem 6.5 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen comfort, eco 5, eco 6, oem 6.5 + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sonnen-sonnenbatterie.mdx b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx new file mode 100644 index 0000000000..d4c6806660 --- /dev/null +++ b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -0,0 +1,67 @@ +--- +title: Sonnen sonnenBatterie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen sonnenBatterie + + + +For active battery control, the "JSON Write API" must be activated via the sonnenBatterie web interface (under Software-Integration) and the API token generated there must be entered in the battery configuration under `token`. +The two operating modes supported for the sonnenBatterie are “self-consumption” (default) and “time-of-use”. The mode can be adapted to the configuration of the sonnenBatterie via the 'defaultmode' parameter. +The power for grid charging can be adapted to the inverter power of the sonnenBatterie via the `maxchargepower` parameter. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/st-ems.mdx b/docs/devices-next/meters/st-ems.mdx new file mode 100644 index 0000000000..ca9e00fed2 --- /dev/null +++ b/docs/devices-next/meters/st-ems.mdx @@ -0,0 +1,139 @@ +--- +title: St-ems +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# St-ems + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/steca-coolcept-flex.mdx b/docs/devices-next/meters/steca-coolcept-flex.mdx new file mode 100644 index 0000000000..c72fb7271f --- /dev/null +++ b/docs/devices-next/meters/steca-coolcept-flex.mdx @@ -0,0 +1,22 @@ +--- +title: Steca coolcept fleX +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Steca coolcept fleX + + + + + diff --git a/docs/devices-next/meters/sungrow-sg-series-inverter.mdx b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx new file mode 100644 index 0000000000..de772b59f6 --- /dev/null +++ b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -0,0 +1,74 @@ +--- +title: Sungrow SG Series Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow SG Series Inverter + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..088e8fb891 --- /dev/null +++ b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -0,0 +1,159 @@ +--- +title: Sungrow SH Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow SH Series Hybrid Inverter + + + +Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmware. Older versions do not provide all required data (power, state of charge). + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sunspec-battery-model-124.mdx b/docs/devices-next/meters/sunspec-battery-model-124.mdx new file mode 100644 index 0000000000..19db0ad988 --- /dev/null +++ b/docs/devices-next/meters/sunspec-battery-model-124.mdx @@ -0,0 +1,65 @@ +--- +title: SunSpec Battery (Model 124) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter-control.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Battery (Model 124) + + + + + diff --git a/docs/devices-next/meters/sunspec-battery-model-802.mdx b/docs/devices-next/meters/sunspec-battery-model-802.mdx new file mode 100644 index 0000000000..eb0b4c5bb5 --- /dev/null +++ b/docs/devices-next/meters/sunspec-battery-model-802.mdx @@ -0,0 +1,66 @@ +--- +title: SunSpec Battery (Model 802) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-battery-control.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Battery (Model 802) + + + + + diff --git a/docs/devices-next/meters/sunspec-hybrid-inverter.mdx b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx new file mode 100644 index 0000000000..9e5b86a1d3 --- /dev/null +++ b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -0,0 +1,150 @@ +--- +title: SunSpec Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sunspec-inverter.mdx b/docs/devices-next/meters/sunspec-inverter.mdx new file mode 100644 index 0000000000..a872d35dc3 --- /dev/null +++ b/docs/devices-next/meters/sunspec-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: SunSpec Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sunspec-meter.mdx b/docs/devices-next/meters/sunspec-meter.mdx new file mode 100644 index 0000000000..f1bb229ba2 --- /dev/null +++ b/docs/devices-next/meters/sunspec-meter.mdx @@ -0,0 +1,48 @@ +--- +title: SunSpec Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Meter + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx new file mode 100644 index 0000000000..03d3e7ff13 --- /dev/null +++ b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: Sunsynk 3p hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk 3p hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx new file mode 100644 index 0000000000..59f1a2bb2d --- /dev/null +++ b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -0,0 +1,185 @@ +--- +title: Sunsynk hp3 hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk hp3 hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sunsynk-micro-inverter.mdx b/docs/devices-next/meters/sunsynk-micro-inverter.mdx new file mode 100644 index 0000000000..dde97fc54c --- /dev/null +++ b/docs/devices-next/meters/sunsynk-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Sunsynk Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk Micro inverter + + + + + diff --git a/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx new file mode 100644 index 0000000000..8c6b0f2f8c --- /dev/null +++ b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: Sunsynk Storage (hybrid) inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk Storage (hybrid) inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/sunsynk-string-inverter.mdx b/docs/devices-next/meters/sunsynk-string-inverter.mdx new file mode 100644 index 0000000000..ed155ffd63 --- /dev/null +++ b/docs/devices-next/meters/sunsynk-string-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Sunsynk String inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk String inverter + + + + + diff --git a/docs/devices-next/meters/sunway.mdx b/docs/devices-next/meters/sunway.mdx new file mode 100644 index 0000000000..f0ab49c8d1 --- /dev/null +++ b/docs/devices-next/meters/sunway.mdx @@ -0,0 +1,139 @@ +--- +title: Sunway +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunway + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx new file mode 100644 index 0000000000..36348858be --- /dev/null +++ b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx @@ -0,0 +1,91 @@ +--- +title: Tasmota SML IR-reader for smartmeters e.g. Hichi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota SML IR-reader for smartmeters e.g. Hichi + + + +To be able to read the values of the smart meter for evcc correctly, the IR reader script must be changed so that the following JSON tags are generated: +- **SML** as the group name of the read parameters +- **Total_in** for the total consumption in KWh (4 decimal places) +- **Total_out** for the total feed-in in KWh (4 decimal places) +- **Power_curr** for the current consumption or the current feed-in in W (0 decimal places) + +A corresponding IR reader script looks like this: +``` +>D +>B +=>sensor53 r +>M 1 +// highlight-next-line ++1,3,s,16,9600,SML +// highlight-next-line +1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 +// highlight-next-line +1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 +// highlight-next-line +1,77070100100700ff@1,Verbrauch,W,Power_curr,0 +1,77070100600100ff@#,Zählernummer,,Meter_Id,0 +# +``` + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx b/docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx new file mode 100644 index 0000000000..84d7d76495 --- /dev/null +++ b/docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx @@ -0,0 +1,70 @@ +--- +title: Tasmota Tasmota (1 Phase + SML Meter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota Tasmota (1 Phase + SML Meter) + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/tasmota-three-phase.mdx b/docs/devices-next/meters/tasmota-three-phase.mdx new file mode 100644 index 0000000000..90b20adb5e --- /dev/null +++ b/docs/devices-next/meters/tasmota-three-phase.mdx @@ -0,0 +1,69 @@ +--- +title: Tasmota three phase +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-3p.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota three phase + + + +Meter channels 1,2,3 must be used. + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/tesla-powerwall.mdx b/docs/devices-next/meters/tesla-powerwall.mdx new file mode 100644 index 0000000000..ef925a48b0 --- /dev/null +++ b/docs/devices-next/meters/tesla-powerwall.mdx @@ -0,0 +1,95 @@ +--- +title: Tesla Powerwall +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tesla-powerwall.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla Powerwall + + + +To use the optional battery control you need to generate a `refresh` token for communicating with the Tesla API. + +The following apps allow to create the token: +- [Auth app for Tesla (iOS)](https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613#?platform=iphone) +- [Tesla Tokens (Android)](https://play.google.com/store/apps/details?id=net.leveugle.teslatokens) +- [Tesla Auth (macOS, Linux)](https://github.com/adriankumpf/tesla_auth) + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/tibber-pulse.mdx b/docs/devices-next/meters/tibber-pulse.mdx new file mode 100644 index 0000000000..774b3942f6 --- /dev/null +++ b/docs/devices-next/meters/tibber-pulse.mdx @@ -0,0 +1,23 @@ +--- +title: Tibber Pulse +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tibber-pulse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tibber Pulse + + + + + diff --git a/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx new file mode 100644 index 0000000000..6ba99a46a3 --- /dev/null +++ b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,22 @@ +--- +title: TP-Link H-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tplink.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link H-Series Smart Plug + + + + + diff --git a/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx new file mode 100644 index 0000000000..e3f0a0e34c --- /dev/null +++ b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,24 @@ +--- +title: TP-Link Tapo P-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tapo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link Tapo P-Series Smart Plug + + + + + diff --git a/docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx b/docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx new file mode 100644 index 0000000000..f61385462d --- /dev/null +++ b/docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx @@ -0,0 +1,24 @@ +--- +title: TQ Energy Manager EM2xx/EM3xx +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TQ Energy Manager EM2xx/EM3xx + + + + + diff --git a/docs/devices-next/meters/tq-energy-manager-em420.mdx b/docs/devices-next/meters/tq-energy-manager-em420.mdx new file mode 100644 index 0000000000..1b00749fdd --- /dev/null +++ b/docs/devices-next/meters/tq-energy-manager-em420.mdx @@ -0,0 +1,25 @@ +--- +title: TQ Energy Manager EM420 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em420.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TQ Energy Manager EM420 + + + + Data Endpoint (optional) + token: ey... # Access token, Access token for EM420 (Create in Profile -> Access tokens)`} /> + diff --git a/docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx b/docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx new file mode 100644 index 0000000000..c4d3dccdb3 --- /dev/null +++ b/docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx @@ -0,0 +1,61 @@ +--- +title: VARTA pulse, pulse neo, element +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA pulse, pulse neo, element + + + +PV only available with PV sensor + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/victron-em24.mdx b/docs/devices-next/meters/victron-em24.mdx new file mode 100644 index 0000000000..bd3408e6cf --- /dev/null +++ b/docs/devices-next/meters/victron-em24.mdx @@ -0,0 +1,65 @@ +--- +title: Victron EM24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM24 + + + +EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/victron-em24e1.mdx b/docs/devices-next/meters/victron-em24e1.mdx new file mode 100644 index 0000000000..3c5c9d793f --- /dev/null +++ b/docs/devices-next/meters/victron-em24e1.mdx @@ -0,0 +1,52 @@ +--- +title: Victron EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM24_E1 + + + +EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. +The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/victron-em530em540.mdx b/docs/devices-next/meters/victron-em530em540.mdx new file mode 100644 index 0000000000..f6e9cd487d --- /dev/null +++ b/docs/devices-next/meters/victron-em530em540.mdx @@ -0,0 +1,74 @@ +--- +title: Victron EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM530/EM540 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/victron-energy.mdx b/docs/devices-next/meters/victron-energy.mdx new file mode 100644 index 0000000000..89ee78ae08 --- /dev/null +++ b/docs/devices-next/meters/victron-energy.mdx @@ -0,0 +1,82 @@ +--- +title: Victron Energy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/victron-energy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron Energy + + + +For grid usage, a grid meter VRM instance is require to enabled load management. + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/victron-et340.mdx b/docs/devices-next/meters/victron-et340.mdx new file mode 100644 index 0000000000..3cad3678a7 --- /dev/null +++ b/docs/devices-next/meters/victron-et340.mdx @@ -0,0 +1,74 @@ +--- +title: Victron ET340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron ET340 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx new file mode 100644 index 0000000000..8121597c44 --- /dev/null +++ b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -0,0 +1,24 @@ +--- +title: Volkszähler HTTP API, Import & Export +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-importexport.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkszähler HTTP API, Import & Export + + + + + diff --git a/docs/devices-next/meters/volkszahler-http-api.mdx b/docs/devices-next/meters/volkszahler-http-api.mdx new file mode 100644 index 0000000000..c91f6f7260 --- /dev/null +++ b/docs/devices-next/meters/volkszahler-http-api.mdx @@ -0,0 +1,23 @@ +--- +title: Volkszähler HTTP API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-http.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkszähler HTTP API + + + + + diff --git a/docs/devices-next/meters/volkszahler-websocket-api.mdx b/docs/devices-next/meters/volkszahler-websocket-api.mdx new file mode 100644 index 0000000000..67e11eea78 --- /dev/null +++ b/docs/devices-next/meters/volkszahler-websocket-api.mdx @@ -0,0 +1,24 @@ +--- +title: Volkszähler WebSocket API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-ws.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkszähler WebSocket API + + + + + diff --git a/docs/devices-next/meters/vzlogger.mdx b/docs/devices-next/meters/vzlogger.mdx new file mode 100644 index 0000000000..cb354b6df1 --- /dev/null +++ b/docs/devices-next/meters/vzlogger.mdx @@ -0,0 +1,42 @@ +--- +title: vzlogger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/vzlogger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# vzlogger + + + + + diff --git a/docs/devices-next/meters/wago-879-30xx.mdx b/docs/devices-next/meters/wago-879-30xx.mdx new file mode 100644 index 0000000000..5903b20a53 --- /dev/null +++ b/docs/devices-next/meters/wago-879-30xx.mdx @@ -0,0 +1,62 @@ +--- +title: Wago 879-30xx +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wago-879-30xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wago 879-30xx + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/wattsonic.mdx b/docs/devices-next/meters/wattsonic.mdx new file mode 100644 index 0000000000..903b59a496 --- /dev/null +++ b/docs/devices-next/meters/wattsonic.mdx @@ -0,0 +1,139 @@ +--- +title: Wattsonic +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wattsonic + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx new file mode 100644 index 0000000000..7b6cb2571c --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM110-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM110-RTU-2P + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx new file mode 100644 index 0000000000..59d3a1d638 --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM111-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM111-RTU-2P + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx new file mode 100644 index 0000000000..e90cc3f695 --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM120-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM120-RTU-2P + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx new file mode 100644 index 0000000000..ec24869654 --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM122-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM122-RTU-2P + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/youless-energy-monitor.mdx b/docs/devices-next/meters/youless-energy-monitor.mdx new file mode 100644 index 0000000000..749b03c1ff --- /dev/null +++ b/docs/devices-next/meters/youless-energy-monitor.mdx @@ -0,0 +1,41 @@ +--- +title: Youless Energy Monitor +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/youless.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Youless Energy Monitor + + + +An externally connected S0 generation meter is required to record the solar production. + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx new file mode 100644 index 0000000000..f01fc07703 --- /dev/null +++ b/docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: ZCS Azzurro Inverter, Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZCS Azzurro Inverter, Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/zendure-hyper-2000.mdx b/docs/devices-next/meters/zendure-hyper-2000.mdx new file mode 100644 index 0000000000..b62c4750f4 --- /dev/null +++ b/docs/devices-next/meters/zendure-hyper-2000.mdx @@ -0,0 +1,53 @@ +--- +title: Zendure Hyper 2000 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/zendure.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zendure Hyper 2000 + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx new file mode 100644 index 0000000000..a5938fb7a8 --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx @@ -0,0 +1,25 @@ +--- +title: Zuidwijk SlimmeLezer(+) in Luxembourg +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) in Luxembourg + + + +Slimmelezer devices use different sensor names in Luxembourg. + + + + diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx new file mode 100644 index 0000000000..2835de85da --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx @@ -0,0 +1,25 @@ +--- +title: Zuidwijk SlimmeLezer(+) V2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) V2 + + + +More recent slimmelezer devices use a different configuration. Try this template if the other one fails. + + + + diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer.mdx new file mode 100644 index 0000000000..22a6369aed --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer.mdx @@ -0,0 +1,28 @@ +--- +title: Zuidwijk SlimmeLezer(+) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) + + + + + diff --git a/docs/devices-next/tariffs/amber-electric.mdx b/docs/devices-next/tariffs/amber-electric.mdx new file mode 100644 index 0000000000..dfd75521bc --- /dev/null +++ b/docs/devices-next/tariffs/amber-electric.mdx @@ -0,0 +1,32 @@ +--- +title: Amber Electric +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/amber.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amber Electric + + + + + diff --git a/docs/devices-next/tariffs/awattar.mdx b/docs/devices-next/tariffs/awattar.mdx new file mode 100644 index 0000000000..c79a84f5ed --- /dev/null +++ b/docs/devices-next/tariffs/awattar.mdx @@ -0,0 +1,28 @@ +--- +title: Awattar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/awattar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Awattar + + + + + diff --git a/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx new file mode 100644 index 0000000000..b193512531 --- /dev/null +++ b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -0,0 +1,26 @@ +--- +title: Electricity Maps Commercial API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Electricity Maps Commercial API + + + +CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. + + + + diff --git a/docs/devices-next/tariffs/electricity-maps-free-api.mdx b/docs/devices-next/tariffs/electricity-maps-free-api.mdx new file mode 100644 index 0000000000..1ede6a4222 --- /dev/null +++ b/docs/devices-next/tariffs/electricity-maps-free-api.mdx @@ -0,0 +1,25 @@ +--- +title: Electricity Maps Free API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps-free.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Electricity Maps Free API + + + +CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. + + + + diff --git a/docs/devices-next/tariffs/energinet.mdx b/docs/devices-next/tariffs/energinet.mdx new file mode 100644 index 0000000000..39424d692a --- /dev/null +++ b/docs/devices-next/tariffs/energinet.mdx @@ -0,0 +1,28 @@ +--- +title: Energinet +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energinet.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Energinet + + + + + diff --git a/docs/devices-next/tariffs/enever.mdx b/docs/devices-next/tariffs/enever.mdx new file mode 100644 index 0000000000..d8bb6a6ffd --- /dev/null +++ b/docs/devices-next/tariffs/enever.mdx @@ -0,0 +1,31 @@ +--- +title: Enever +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/enever.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Enever + + + + + diff --git a/docs/devices-next/tariffs/entso-e.mdx b/docs/devices-next/tariffs/entso-e.mdx new file mode 100644 index 0000000000..48a2f9d3db --- /dev/null +++ b/docs/devices-next/tariffs/entso-e.mdx @@ -0,0 +1,34 @@ +--- +title: ENTSO-E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/entsoe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ENTSO-E + + + +Day-ahead prices for the European electricity market. See https://transparency.entsoe.eu for more information. +Basis for many dynamic tariffs. + + + + diff --git a/docs/devices-next/tariffs/forecastsolar.mdx b/docs/devices-next/tariffs/forecastsolar.mdx new file mode 100644 index 0000000000..ffc8669d16 --- /dev/null +++ b/docs/devices-next/tariffs/forecastsolar.mdx @@ -0,0 +1,39 @@ +--- +title: Forecast.Solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Forecast.Solar + + + +[forecast.solar](https://forecast.solar) can be used for free. Paid plans can also be used by specifying an API key. + + + + diff --git a/docs/devices-next/tariffs/fraunhofer-ise.mdx b/docs/devices-next/tariffs/fraunhofer-ise.mdx new file mode 100644 index 0000000000..f4b9825c5b --- /dev/null +++ b/docs/devices-next/tariffs/fraunhofer-ise.mdx @@ -0,0 +1,31 @@ +--- +title: Fraunhofer ISE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energy-charts-api.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fraunhofer ISE + + + +Day-ahead forecast of energy prices (per kWh) on the exchange. No prior registration for https://api.energy-charts.info/ necessary. Can be used for dynamic electricity tariffs, for example, where the supplier does not yet offer a price forecast on the customer interface. + + + + diff --git a/docs/devices-next/tariffs/green-grid-compass.mdx b/docs/devices-next/tariffs/green-grid-compass.mdx new file mode 100644 index 0000000000..2a08dc19d7 --- /dev/null +++ b/docs/devices-next/tariffs/green-grid-compass.mdx @@ -0,0 +1,25 @@ +--- +title: Green Grid Compass +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/green-grid-compass.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Green Grid Compass + + + +European CO₂ intensity data from [greengrid-compass.eu](https://www.greengrid-compass.eu). Provides forecasts for the next hours and is free of charge after registration. + + + + diff --git a/docs/devices-next/tariffs/groupe-e-vario-plus.mdx b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx new file mode 100644 index 0000000000..ea4defe600 --- /dev/null +++ b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -0,0 +1,26 @@ +--- +title: Groupe E Vario Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/groupe-e.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Groupe E Vario Plus + + + + + diff --git a/docs/devices-next/tariffs/grunstromindex.mdx b/docs/devices-next/tariffs/grunstromindex.mdx new file mode 100644 index 0000000000..73118929b8 --- /dev/null +++ b/docs/devices-next/tariffs/grunstromindex.mdx @@ -0,0 +1,25 @@ +--- +title: Grünstromindex +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/grünstromindex.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Grünstromindex + + + +Regional emission data from https://gruenstromindex.de + + + + diff --git a/docs/devices-next/tariffs/index.mdx b/docs/devices-next/tariffs/index.mdx new file mode 100644 index 0000000000..6afb0ee71a --- /dev/null +++ b/docs/devices-next/tariffs/index.mdx @@ -0,0 +1,202 @@ +--- +title: Tariffs +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Tariffs + +
+ + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/docs/devices-next/tariffs/national-grid-eso.mdx b/docs/devices-next/tariffs/national-grid-eso.mdx new file mode 100644 index 0000000000..ad95fa4239 --- /dev/null +++ b/docs/devices-next/tariffs/national-grid-eso.mdx @@ -0,0 +1,22 @@ +--- +title: National Grid ESO +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ngeso.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# National Grid ESO + + + + + diff --git a/docs/devices-next/tariffs/nordpool-spot-prices.mdx b/docs/devices-next/tariffs/nordpool-spot-prices.mdx new file mode 100644 index 0000000000..b754f73fc2 --- /dev/null +++ b/docs/devices-next/tariffs/nordpool-spot-prices.mdx @@ -0,0 +1,33 @@ +--- +title: Nordpool spot prices +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/nordpool.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nordpool spot prices + + + +Nordpool spot prices in day-ahead market for all markets in the Nordpool region. + + + + diff --git a/docs/devices-next/tariffs/octopus-energy-api.mdx b/docs/devices-next/tariffs/octopus-energy-api.mdx new file mode 100644 index 0000000000..f1628fe52c --- /dev/null +++ b/docs/devices-next/tariffs/octopus-energy-api.mdx @@ -0,0 +1,25 @@ +--- +title: Octopus Energy API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-api.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Octopus Energy API + + + +You can get the API key in the Octopus portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access + + + + diff --git a/docs/devices-next/tariffs/octopus-energy-product-code.mdx b/docs/devices-next/tariffs/octopus-energy-product-code.mdx new file mode 100644 index 0000000000..620611ff49 --- /dev/null +++ b/docs/devices-next/tariffs/octopus-energy-product-code.mdx @@ -0,0 +1,23 @@ +--- +title: Octopus Energy Product Code +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-productcode.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Octopus Energy Product Code + + + + + diff --git a/docs/devices-next/tariffs/open-meteo.mdx b/docs/devices-next/tariffs/open-meteo.mdx new file mode 100644 index 0000000000..c63ef9cf94 --- /dev/null +++ b/docs/devices-next/tariffs/open-meteo.mdx @@ -0,0 +1,43 @@ +--- +title: Open-Meteo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/open-meteo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Open-Meteo + + + +Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open-source weather API and offers free access for non-commercial use. No API key required. + + + + diff --git a/docs/devices-next/tariffs/ostrom.mdx b/docs/devices-next/tariffs/ostrom.mdx new file mode 100644 index 0000000000..016c687e81 --- /dev/null +++ b/docs/devices-next/tariffs/ostrom.mdx @@ -0,0 +1,26 @@ +--- +title: Ostrom +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ostrom.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ostrom + + + +Create a 'Production Client' in the Ostrom developer portal: https://developer.ostrom-api.io/ + + + + diff --git a/docs/devices-next/tariffs/pun-orario.mdx b/docs/devices-next/tariffs/pun-orario.mdx new file mode 100644 index 0000000000..a49676fd08 --- /dev/null +++ b/docs/devices-next/tariffs/pun-orario.mdx @@ -0,0 +1,29 @@ +--- +title: PUN Orario +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/pun.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# PUN Orario + + + +Price data from https://www.mercatoelettrico.org/it/. Often used for feeding into the grid. + + + + diff --git a/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx new file mode 100644 index 0000000000..7f4d04cfb7 --- /dev/null +++ b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -0,0 +1,26 @@ +--- +title: SmartEnergy smartCONTROL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/smartenergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SmartEnergy smartCONTROL + + + + + diff --git a/docs/devices-next/tariffs/solcast.mdx b/docs/devices-next/tariffs/solcast.mdx new file mode 100644 index 0000000000..122760dd28 --- /dev/null +++ b/docs/devices-next/tariffs/solcast.mdx @@ -0,0 +1,33 @@ +--- +title: Solcast +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/solcast.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solcast + + + +Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) account. The free "Home User" tier is often sufficient for private use. This plan has an API limit of 10 requests per day. + + + + diff --git a/docs/devices-next/tariffs/spotty-energie.mdx b/docs/devices-next/tariffs/spotty-energie.mdx new file mode 100644 index 0000000000..a69400e446 --- /dev/null +++ b/docs/devices-next/tariffs/spotty-energie.mdx @@ -0,0 +1,30 @@ +--- +title: Spotty Energie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/spottyenergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Spotty Energie + + + + + diff --git a/docs/devices-next/tariffs/tibber.mdx b/docs/devices-next/tariffs/tibber.mdx new file mode 100644 index 0000000000..55f139a2f7 --- /dev/null +++ b/docs/devices-next/tariffs/tibber.mdx @@ -0,0 +1,33 @@ +--- +title: Tibber +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/tibber.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tibber + + + +Get your API token from the Tibber developer portal: https://developer.tibber.com/ + + + + diff --git a/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx new file mode 100644 index 0000000000..faa19fc55a --- /dev/null +++ b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -0,0 +1,31 @@ +--- +title: Victron VRM Solar Forecast +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/victron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron VRM Solar Forecast + + + +[vrm.victronenergy.com](https://vrm.victronenergy.com) get the 2-days-forecast from your installation in VRM portal. You need a free user access token. + + +Integrations`} advanced={`tariffs: + solar: + - type: template + template: victron + idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" + token: # API access token, Tokens can be created in VRM in Preferences->Integrations + interval: 1h # optional`} /> + diff --git a/docs/devices-next/vehicles/aiways.mdx b/docs/devices-next/vehicles/aiways.mdx new file mode 100644 index 0000000000..c65e070b5a --- /dev/null +++ b/docs/devices-next/vehicles/aiways.mdx @@ -0,0 +1,39 @@ +--- +title: Aiways +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/aiways.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Aiways + + + diff --git a/docs/devices-next/vehicles/audi.mdx b/docs/devices-next/vehicles/audi.mdx new file mode 100644 index 0000000000..1ef9502a5a --- /dev/null +++ b/docs/devices-next/vehicles/audi.mdx @@ -0,0 +1,39 @@ +--- +title: Audi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/audi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi + + + diff --git a/docs/devices-next/vehicles/bmw.mdx b/docs/devices-next/vehicles/bmw.mdx new file mode 100644 index 0000000000..62a0da7c9a --- /dev/null +++ b/docs/devices-next/vehicles/bmw.mdx @@ -0,0 +1,47 @@ +--- +title: BMW +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/bmw.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BMW + +Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. + + + + diff --git a/docs/devices-next/vehicles/citroen.mdx b/docs/devices-next/vehicles/citroen.mdx new file mode 100644 index 0000000000..429286ed1e --- /dev/null +++ b/docs/devices-next/vehicles/citroen.mdx @@ -0,0 +1,44 @@ +--- +title: Citroën +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/citroen.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Citroën + +Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + + + + diff --git a/docs/devices-next/vehicles/dacia.mdx b/docs/devices-next/vehicles/dacia.mdx new file mode 100644 index 0000000000..f7f0346884 --- /dev/null +++ b/docs/devices-next/vehicles/dacia.mdx @@ -0,0 +1,41 @@ +--- +title: Dacia +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/dacia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Dacia + + + diff --git a/docs/devices-next/vehicles/ds.mdx b/docs/devices-next/vehicles/ds.mdx new file mode 100644 index 0000000000..67af522764 --- /dev/null +++ b/docs/devices-next/vehicles/ds.mdx @@ -0,0 +1,44 @@ +--- +title: DS +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ds.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DS + +Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + + + + diff --git a/docs/devices-next/vehicles/evnotify.mdx b/docs/devices-next/vehicles/evnotify.mdx new file mode 100644 index 0000000000..a511614830 --- /dev/null +++ b/docs/devices-next/vehicles/evnotify.mdx @@ -0,0 +1,36 @@ +--- +title: evNotify +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/evnotify.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# evNotify + + + diff --git a/docs/devices-next/vehicles/fiat.mdx b/docs/devices-next/vehicles/fiat.mdx new file mode 100644 index 0000000000..6c69c79844 --- /dev/null +++ b/docs/devices-next/vehicles/fiat.mdx @@ -0,0 +1,43 @@ +--- +title: Fiat +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fiat + + + diff --git a/docs/devices-next/vehicles/ford.mdx b/docs/devices-next/vehicles/ford.mdx new file mode 100644 index 0000000000..4dba08939b --- /dev/null +++ b/docs/devices-next/vehicles/ford.mdx @@ -0,0 +1,43 @@ +--- +title: Ford +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ford-connect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ford + + + diff --git a/docs/devices-next/vehicles/generic-vehicle-without-api.mdx b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx new file mode 100644 index 0000000000..8c2fc02fad --- /dev/null +++ b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -0,0 +1,32 @@ +--- +title: Generic vehicle (without API) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/offline.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Generic vehicle (without API) + + + diff --git a/docs/devices-next/vehicles/hyundai-bluelink.mdx b/docs/devices-next/vehicles/hyundai-bluelink.mdx new file mode 100644 index 0000000000..da17034532 --- /dev/null +++ b/docs/devices-next/vehicles/hyundai-bluelink.mdx @@ -0,0 +1,44 @@ +--- +title: Hyundai Bluelink +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/hyundai.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hyundai Bluelink + +Some models (e.g. Kona) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. + + + + diff --git a/docs/devices-next/vehicles/index.mdx b/docs/devices-next/vehicles/index.mdx new file mode 100644 index 0000000000..71ec18fc58 --- /dev/null +++ b/docs/devices-next/vehicles/index.mdx @@ -0,0 +1,378 @@ +--- +title: Vehicles +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Vehicles + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/docs/devices-next/vehicles/iobrokerbmw.mdx b/docs/devices-next/vehicles/iobrokerbmw.mdx new file mode 100644 index 0000000000..d8c2750002 --- /dev/null +++ b/docs/devices-next/vehicles/iobrokerbmw.mdx @@ -0,0 +1,42 @@ +--- +title: ioBroker.bmw +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ioBroker.bmw.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ioBroker.bmw + +ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api + + + + diff --git a/docs/devices-next/vehicles/iso15118.mdx b/docs/devices-next/vehicles/iso15118.mdx new file mode 100644 index 0000000000..6aaa231ec5 --- /dev/null +++ b/docs/devices-next/vehicles/iso15118.mdx @@ -0,0 +1,38 @@ +--- +title: ISO15118 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/iso15118.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ISO15118 + +Only supported if the vehicle can provide the state of charge (Soc) to the connected charger. +Using ISO15118 with some VW group vehicles, e.g. Porsche Taycan, requires additional configuration in the vehicle. +This requires an active location-based charging profile with the lowest minimum charge (25%) and direct charging disabled. +Otherwise the vehicle cannot be put into sleep mode. + + + + diff --git a/docs/devices-next/vehicles/jeep.mdx b/docs/devices-next/vehicles/jeep.mdx new file mode 100644 index 0000000000..77f6a2b580 --- /dev/null +++ b/docs/devices-next/vehicles/jeep.mdx @@ -0,0 +1,43 @@ +--- +title: Jeep +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Jeep + + + diff --git a/docs/devices-next/vehicles/kia-bluelink.mdx b/docs/devices-next/vehicles/kia-bluelink.mdx new file mode 100644 index 0000000000..ef54efdaf4 --- /dev/null +++ b/docs/devices-next/vehicles/kia-bluelink.mdx @@ -0,0 +1,44 @@ +--- +title: Kia Bluelink +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/kia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kia Bluelink + +Some models (e.g. Niro EV) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. + + + + diff --git a/docs/devices-next/vehicles/mercedes-benz.mdx b/docs/devices-next/vehicles/mercedes-benz.mdx new file mode 100644 index 0000000000..ab09b0c5e4 --- /dev/null +++ b/docs/devices-next/vehicles/mercedes-benz.mdx @@ -0,0 +1,46 @@ +--- +title: Mercedes-Benz +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mercedes.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mercedes-Benz + +Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/mbapi2020helptoken. + + + + diff --git a/docs/devices-next/vehicles/mg.mdx b/docs/devices-next/vehicles/mg.mdx new file mode 100644 index 0000000000..be2503dc94 --- /dev/null +++ b/docs/devices-next/vehicles/mg.mdx @@ -0,0 +1,40 @@ +--- +title: MG +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# MG + + + diff --git a/docs/devices-next/vehicles/mg2mqtt.mdx b/docs/devices-next/vehicles/mg2mqtt.mdx new file mode 100644 index 0000000000..5089bef531 --- /dev/null +++ b/docs/devices-next/vehicles/mg2mqtt.mdx @@ -0,0 +1,41 @@ +--- +title: mg2mqtt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg2mqtt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# mg2mqtt + +Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway or https://github.com/SAIC-iSmart-API/saic-java-client) + + + + diff --git a/docs/devices-next/vehicles/mini.mdx b/docs/devices-next/vehicles/mini.mdx new file mode 100644 index 0000000000..6bda216cec --- /dev/null +++ b/docs/devices-next/vehicles/mini.mdx @@ -0,0 +1,47 @@ +--- +title: Mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mini.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mini + +Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. + + + + diff --git a/docs/devices-next/vehicles/mz2mqtt.mdx b/docs/devices-next/vehicles/mz2mqtt.mdx new file mode 100644 index 0000000000..185d2cb80a --- /dev/null +++ b/docs/devices-next/vehicles/mz2mqtt.mdx @@ -0,0 +1,38 @@ +--- +title: mz2mqtt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mz2mqtt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# mz2mqtt + +myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation https://github.com/C64Axel/mz2mqtt. + + + + diff --git a/docs/devices-next/vehicles/nissan-ariya.mdx b/docs/devices-next/vehicles/nissan-ariya.mdx new file mode 100644 index 0000000000..35f5c15ef1 --- /dev/null +++ b/docs/devices-next/vehicles/nissan-ariya.mdx @@ -0,0 +1,39 @@ +--- +title: Nissan Ariya +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan-ariya.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nissan Ariya + + + diff --git a/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx new file mode 100644 index 0000000000..668fab14bb --- /dev/null +++ b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -0,0 +1,39 @@ +--- +title: Nissan Leaf (pre 2019) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/carwings.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nissan Leaf (pre 2019) + + + diff --git a/docs/devices-next/vehicles/nissan-leaf.mdx b/docs/devices-next/vehicles/nissan-leaf.mdx new file mode 100644 index 0000000000..e3e18ed656 --- /dev/null +++ b/docs/devices-next/vehicles/nissan-leaf.mdx @@ -0,0 +1,39 @@ +--- +title: Nissan Leaf +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nissan Leaf + + + diff --git a/docs/devices-next/vehicles/niu-e-scooter.mdx b/docs/devices-next/vehicles/niu-e-scooter.mdx new file mode 100644 index 0000000000..0661329040 --- /dev/null +++ b/docs/devices-next/vehicles/niu-e-scooter.mdx @@ -0,0 +1,24 @@ +--- +title: NIU E-Scooter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/niu-e-scooter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# NIU E-Scooter + + + diff --git a/docs/devices-next/vehicles/opel.mdx b/docs/devices-next/vehicles/opel.mdx new file mode 100644 index 0000000000..e6c7004492 --- /dev/null +++ b/docs/devices-next/vehicles/opel.mdx @@ -0,0 +1,44 @@ +--- +title: Opel +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/opel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Opel + +Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + + + + diff --git a/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx new file mode 100644 index 0000000000..8dbb58863d --- /dev/null +++ b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -0,0 +1,43 @@ +--- +title: Open Vehicle Monitoring System +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ovms.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Open Vehicle Monitoring System + +Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Vehicle Monitoring System](http://api.openvehicles.com/). + + + + diff --git a/docs/devices-next/vehicles/peugeot.mdx b/docs/devices-next/vehicles/peugeot.mdx new file mode 100644 index 0000000000..90b6167b5f --- /dev/null +++ b/docs/devices-next/vehicles/peugeot.mdx @@ -0,0 +1,44 @@ +--- +title: Peugeot +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/peugeot.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peugeot + +Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + + + + diff --git a/docs/devices-next/vehicles/polestar.mdx b/docs/devices-next/vehicles/polestar.mdx new file mode 100644 index 0000000000..a55cc9f6d8 --- /dev/null +++ b/docs/devices-next/vehicles/polestar.mdx @@ -0,0 +1,39 @@ +--- +title: Polestar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/polestar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Polestar + + + diff --git a/docs/devices-next/vehicles/psa-car-controller.mdx b/docs/devices-next/vehicles/psa-car-controller.mdx new file mode 100644 index 0000000000..0c52d668db --- /dev/null +++ b/docs/devices-next/vehicles/psa-car-controller.mdx @@ -0,0 +1,40 @@ +--- +title: PSA Car Controller +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/flobz.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# PSA Car Controller + +Remote Control of PSA car https://github.com/flobz/psa_car_controller + + + + diff --git a/docs/devices-next/vehicles/renault.mdx b/docs/devices-next/vehicles/renault.mdx new file mode 100644 index 0000000000..62af5d8465 --- /dev/null +++ b/docs/devices-next/vehicles/renault.mdx @@ -0,0 +1,40 @@ +--- +title: Renault +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/renault.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Renault + + + diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx new file mode 100644 index 0000000000..8f58026bfe --- /dev/null +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -0,0 +1,39 @@ +--- +title: Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/seat.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) + + + diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx new file mode 100644 index 0000000000..2b0ecabc22 --- /dev/null +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -0,0 +1,41 @@ +--- +title: Seat CupraConnect Gen4 (Born, Formentor, Tavascan) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/cupra.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Seat CupraConnect Gen4 (Born, Formentor, Tavascan) + + + diff --git a/docs/devices-next/vehicles/skoda-enyaq.mdx b/docs/devices-next/vehicles/skoda-enyaq.mdx new file mode 100644 index 0000000000..cbdf283450 --- /dev/null +++ b/docs/devices-next/vehicles/skoda-enyaq.mdx @@ -0,0 +1,41 @@ +--- +title: Skoda Enyaq +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/enyaq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Enyaq + + + diff --git a/docs/devices-next/vehicles/smart-eq.mdx b/docs/devices-next/vehicles/smart-eq.mdx new file mode 100644 index 0000000000..e2908cf38e --- /dev/null +++ b/docs/devices-next/vehicles/smart-eq.mdx @@ -0,0 +1,46 @@ +--- +title: Smart EQ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smart EQ + +Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + + + + diff --git a/docs/devices-next/vehicles/smart.mdx b/docs/devices-next/vehicles/smart.mdx new file mode 100644 index 0000000000..801cd0529d --- /dev/null +++ b/docs/devices-next/vehicles/smart.mdx @@ -0,0 +1,41 @@ +--- +title: Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smart + + + diff --git a/docs/devices-next/vehicles/tesla-ble.mdx b/docs/devices-next/vehicles/tesla-ble.mdx new file mode 100644 index 0000000000..40dcffe600 --- /dev/null +++ b/docs/devices-next/vehicles/tesla-ble.mdx @@ -0,0 +1,41 @@ +--- +title: Tesla BLE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla-ble.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla BLE + +Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy + + + + diff --git a/docs/devices-next/vehicles/tesla.mdx b/docs/devices-next/vehicles/tesla.mdx new file mode 100644 index 0000000000..f09ea4d2d2 --- /dev/null +++ b/docs/devices-next/vehicles/tesla.mdx @@ -0,0 +1,59 @@ +--- +title: Tesla +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla + +Tesla offers an official, but paid vehicle API. +For private use, you can create a [Tesla Developer Account](https://developer.tesla.com/) and receive a monthly API credit of $10. +This is usually sufficient for the common evcc use cases. + +The [myteslamate.com](https://www.myteslamate.com/tesla-api-application-registration/) guide explains the process and generates a free Access and Refresh Token. +With this token pair and your Client ID created in the Tesla Developer Account, evcc can directly communicate with the Tesla API. +You can see your used credit in the Tesla Developer Dashboard. + +To use a Tesla Wall Connector, you need a public Command Proxy Server. +[myteslamate.com](https://app.myteslamate.com/) provides such a service with per-use pricing. +Configure the Command permissions at myteslamate.com and enter the Proxy Token here. +Start, stopp and current commands are sent to Tesla via this proxy. + +More information and alternatives can be found in [our blog post](https://docs.evcc.io/en/blog/2025/01/20/tesla-api-update). + + + + diff --git a/docs/devices-next/vehicles/teslalogger.mdx b/docs/devices-next/vehicles/teslalogger.mdx new file mode 100644 index 0000000000..dd0582ab1e --- /dev/null +++ b/docs/devices-next/vehicles/teslalogger.mdx @@ -0,0 +1,41 @@ +--- +title: TeslaLogger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslalogger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TeslaLogger + +Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger + + + + diff --git a/docs/devices-next/vehicles/teslamate.mdx b/docs/devices-next/vehicles/teslamate.mdx new file mode 100644 index 0000000000..cc5c79f0f2 --- /dev/null +++ b/docs/devices-next/vehicles/teslamate.mdx @@ -0,0 +1,37 @@ +--- +title: TeslaMate +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslamate.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TeslaMate + +Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT broker required. + + + + diff --git a/docs/devices-next/vehicles/tessie.mdx b/docs/devices-next/vehicles/tessie.mdx new file mode 100644 index 0000000000..4bc93d2f84 --- /dev/null +++ b/docs/devices-next/vehicles/tessie.mdx @@ -0,0 +1,39 @@ +--- +title: Tessie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tessie.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tessie + +Connect your Tesla using the Tessie API. This will never wake up the car, polling can be set to "always" and interval "1M". If the vehicle is awake, the data is usually less than 15 seconds old. If the vehicle is asleep, the data is from the time the vehicle went to sleep. Get your token at https://dash.tessie.com/settings/api + + + + diff --git a/docs/devices-next/vehicles/toyota.mdx b/docs/devices-next/vehicles/toyota.mdx new file mode 100644 index 0000000000..ec1ba5771b --- /dev/null +++ b/docs/devices-next/vehicles/toyota.mdx @@ -0,0 +1,42 @@ +--- +title: Toyota +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/toyota.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Toyota + +Requires Toyota Connected Services Account. + + + + diff --git a/docs/devices-next/vehicles/tronity.mdx b/docs/devices-next/vehicles/tronity.mdx new file mode 100644 index 0000000000..34feaf523d --- /dev/null +++ b/docs/devices-next/vehicles/tronity.mdx @@ -0,0 +1,41 @@ +--- +title: Tronity +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tronity.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tronity + + + + + diff --git a/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx new file mode 100644 index 0000000000..01590a0805 --- /dev/null +++ b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -0,0 +1,44 @@ +--- +title: Volkswagen We Connect ID +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/vw.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen We Connect ID + +e-Golf, e-Up, ID family + + + + diff --git a/docs/devices-next/vehicles/volvo.mdx b/docs/devices-next/vehicles/volvo.mdx new file mode 100644 index 0000000000..dd4e473fe4 --- /dev/null +++ b/docs/devices-next/vehicles/volvo.mdx @@ -0,0 +1,52 @@ +--- +title: Volvo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo-connected.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volvo + +To use with EVCC, you need a Volvo account and a Volvo Connected Car API Key. +To do this, create a new application on the [Account page](https://developer.volvocars.com/account/) and save the primary VCC API key. +Now publish your application and select the permissions "Connected Vehicle API -> conve:vehicle-relation" and "Energy API -> (everything)" under "Scopes". +You must enter the URL of your EVCC instance as the redirect URL, e.g. "http://evcc.local:7070/oauth/callback". +Once the application is created, it will be displayed as "Publication under Review". This is not a problem, it still works. +When adding the vehicle via the UI, an error message is displayed. +Check the log for the message "registering oauth provider at /oauth/login?..." and open the link "http://evcc.local:7070/oauth/login?..." in a new tab. +Log in with your Volvo account and allow access to the data. If the authorization is successful, the vehicle can be added. + + + + diff --git a/docs/devices-next/vehicles/volvo2mqtt.mdx b/docs/devices-next/vehicles/volvo2mqtt.mdx new file mode 100644 index 0000000000..7964106228 --- /dev/null +++ b/docs/devices-next/vehicles/volvo2mqtt.mdx @@ -0,0 +1,39 @@ +--- +title: volvo2mqtt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo2mqtt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# volvo2mqtt + +Requires MQTT broker configuration and a volvo2mqtt installation https://github.com/Dielee/volvo2mqtt + + + + diff --git a/docs/devices-next/vehicles/zero-motorcycles.mdx b/docs/devices-next/vehicles/zero-motorcycles.mdx new file mode 100644 index 0000000000..8ebd7d9217 --- /dev/null +++ b/docs/devices-next/vehicles/zero-motorcycles.mdx @@ -0,0 +1,39 @@ +--- +title: Zero Motorcycles +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/zero.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zero Motorcycles + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx new file mode 100644 index 0000000000..c8239304ef --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx @@ -0,0 +1,36 @@ +--- +title: ABB Terra AC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB Terra AC + + + +https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx new file mode 100644 index 0000000000..3daa17da9c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx @@ -0,0 +1,38 @@ +--- +title: ABL eM4 (SBCx) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 (SBCx) + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx new file mode 100644 index 0000000000..e4a22d768e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx @@ -0,0 +1,36 @@ +--- +title: ABL eMH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH1 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx new file mode 100644 index 0000000000..f7a78501ed --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx @@ -0,0 +1,36 @@ +--- +title: ABL eMH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH2 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx new file mode 100644 index 0000000000..07a6893b96 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx @@ -0,0 +1,33 @@ +--- +title: ABL Sursum eMH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL Sursum eMH2 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx new file mode 100644 index 0000000000..dad4fdff0c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx @@ -0,0 +1,33 @@ +--- +title: ABL Sursum eMH3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL Sursum eMH3 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx new file mode 100644 index 0000000000..1e815a9890 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx @@ -0,0 +1,33 @@ +--- +title: ABL Sursum eMH4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL Sursum eMH4 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx new file mode 100644 index 0000000000..ef2fc08e37 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx @@ -0,0 +1,33 @@ +--- +title: Alfen Eve +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alfen Eve + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx new file mode 100644 index 0000000000..764aa447b8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -0,0 +1,38 @@ +--- +title: Alphatec Ladesäule Twin +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Ladesäule Twin + + + +Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx new file mode 100644 index 0000000000..4a48cf8e2a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx @@ -0,0 +1,38 @@ +--- +title: Alphatec Wallbox Mini, Power +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Wallbox Mini, Power + + + +Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx new file mode 100644 index 0000000000..6a4d20c236 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx @@ -0,0 +1,28 @@ +--- +title: Amperfied Wallbox connect.business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.business + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx new file mode 100644 index 0000000000..a0db0963ae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx @@ -0,0 +1,28 @@ +--- +title: Amperfied Wallbox connect.home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.home + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx new file mode 100644 index 0000000000..257e44333f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx @@ -0,0 +1,28 @@ +--- +title: Amperfied Wallbox connect.solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.solar + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx new file mode 100644 index 0000000000..4bb565d640 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -0,0 +1,38 @@ +--- +title: Amperfied Wallbox Energy Control +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox Energy Control + + + +Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx new file mode 100644 index 0000000000..d3b883090f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx @@ -0,0 +1,31 @@ +--- +title: Ampure Live +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampure Live + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx new file mode 100644 index 0000000000..71cc322316 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx @@ -0,0 +1,27 @@ +--- +title: Ampure NEXT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampure NEXT + + + +Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx new file mode 100644 index 0000000000..a57d49de16 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx @@ -0,0 +1,31 @@ +--- +title: Ampure Unite +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampure Unite + + + +1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx new file mode 100644 index 0000000000..cf2a7e674f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Audi Audi Wallbox pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi Audi Wallbox pro + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx new file mode 100644 index 0000000000..29c68ef04a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx @@ -0,0 +1,31 @@ +--- +title: Audi Wallbox plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi Wallbox plus + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx new file mode 100644 index 0000000000..f160eaff25 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx @@ -0,0 +1,41 @@ +--- +title: AUTEL AC Compact +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AUTEL AC Compact + + + +Anleitung: +* In der Autel Charge app, klicken sie auf “OCPP Server” +* Geben Sie "Custom" in das Feld ein und wählen Sie "Personalisierung" darunter +* Server-URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladegerät-ID: Leer lassen (zur Verwendung der Seriennummer) oder einen benutzerdefinierten Wert definieren, der in der Konfiguration als *stationid* wiederverwendet wird +* Autorisierungsschlüssel: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx new file mode 100644 index 0000000000..23c030fcba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx @@ -0,0 +1,41 @@ +--- +title: AUTEL AC MaxiCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AUTEL AC MaxiCharger + + + +Anleitung: +* In der Autel Charge app, klicken sie auf “OCPP Server” +* Geben Sie "Custom" in das Feld ein und wählen Sie "Personalisierung" darunter +* Server-URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladegerät-ID: Leer lassen (zur Verwendung der Seriennummer) oder einen benutzerdefinierten Wert definieren, der in der Konfiguration als *stationid* wiederverwendet wird +* Autorisierungsschlüssel: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx new file mode 100644 index 0000000000..efa46fcc4a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx @@ -0,0 +1,33 @@ +--- +title: Autoaid Business Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Autoaid Business Wallbox + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx new file mode 100644 index 0000000000..632cff33cb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -0,0 +1,33 @@ +--- +title: Autoaid Intelligent Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Autoaid Intelligent Wallbox + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx new file mode 100644 index 0000000000..5d596badae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx @@ -0,0 +1,36 @@ +--- +title: AVM FritzDECT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/fritzdect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AVM FritzDECT + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx new file mode 100644 index 0000000000..e80c6b9658 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx @@ -0,0 +1,31 @@ +--- +title: Bender CC612 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender CC612 + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx new file mode 100644 index 0000000000..b4e514540d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx @@ -0,0 +1,31 @@ +--- +title: Bender CC613 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender CC613 + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx new file mode 100644 index 0000000000..cf8c96eaf0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx @@ -0,0 +1,31 @@ +--- +title: Bender ICC1314 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender ICC1314 + + + +Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx new file mode 100644 index 0000000000..b0292cb722 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx @@ -0,0 +1,31 @@ +--- +title: Bender ICC1324 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bender ICC1324 + + + +Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx new file mode 100644 index 0000000000..02f6d14440 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx @@ -0,0 +1,41 @@ +--- +title: BMW i Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BMW i Wallbox + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx new file mode 100644 index 0000000000..a869361774 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Bosch SG Ready +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bosch SG Ready + + + +Eingebunden via [EMSESP](https://emsesp.org/) + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx new file mode 100644 index 0000000000..ea15cfdde8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx @@ -0,0 +1,28 @@ +--- +title: Bösch x-change +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bösch x-change + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx new file mode 100644 index 0000000000..93e33c8321 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Buderus SG Ready +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Buderus SG Ready + + + +Eingebunden via [EMSESP](https://emsesp.org/) + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx new file mode 100644 index 0000000000..35995cd704 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx @@ -0,0 +1,29 @@ +--- +title: cFos Power Brain Solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# cFos Power Brain Solar + + + +Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. +Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: +1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) +2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx new file mode 100644 index 0000000000..00d8848185 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx @@ -0,0 +1,29 @@ +--- +title: cFos Power Brain +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# cFos Power Brain + + + +Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. +Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: +1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) +2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx new file mode 100644 index 0000000000..40c0f82189 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx @@ -0,0 +1,33 @@ +--- +title: Charge Amps Halo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-chargeamps.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Charge Amps Halo + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-chargeamps + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx new file mode 100644 index 0000000000..c09694e8f9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: Compleo eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Compleo eBox + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx new file mode 100644 index 0000000000..7d0db981ea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx @@ -0,0 +1,31 @@ +--- +title: CUBOS C11E, C22E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CUBOS C11E, C22E + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx new file mode 100644 index 0000000000..07f0d79d40 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Connect 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Connect 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx new file mode 100644 index 0000000000..b31b4c6bce --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx @@ -0,0 +1,31 @@ +--- +title: Cupra Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Connect + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx new file mode 100644 index 0000000000..879b03b8ac --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Pro 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx new file mode 100644 index 0000000000..532da112f8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Pro Eichrecht 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Pro Eichrecht 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx new file mode 100644 index 0000000000..344b8f534e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Cupra Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Cupra Charger Pro + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx new file mode 100644 index 0000000000..0d871b2d82 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -0,0 +1,28 @@ +--- +title: Dadapower Premium Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/dadapower.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Dadapower Premium Wallbox + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx new file mode 100644 index 0000000000..2651375a8e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx @@ -0,0 +1,25 @@ +--- +title: DaheimLaden Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daheimladen-mb.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DaheimLaden Wallbox + + + +Die Wallbox muss über eine aktuelle Firmware mit Modbus-Unterstützung verfügen. In den Einstellungen muss "Nachladen" (Smart) bzw. "RSDA" (Touch) aktiviert sein + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx new file mode 100644 index 0000000000..fc17322427 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Daikin HomeHub (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daikin-homehub.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Daikin HomeHub (SG Ready) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx new file mode 100644 index 0000000000..5c317e2163 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx @@ -0,0 +1,64 @@ +--- +title: Delta AC Max Basic +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta AC Max Basic + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx new file mode 100644 index 0000000000..9264c3b98e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx @@ -0,0 +1,64 @@ +--- +title: Delta AC MAX Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta AC MAX Smart + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx new file mode 100644 index 0000000000..712c74c969 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx @@ -0,0 +1,64 @@ +--- +title: Delta SLIM Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta SLIM Charger + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx new file mode 100644 index 0000000000..622fd76e87 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -0,0 +1,64 @@ +--- +title: Delta Ultra Fast Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Delta Ultra Fast Charger + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx new file mode 100644 index 0000000000..fa4065da89 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx @@ -0,0 +1,34 @@ +--- +title: Demowallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/demo-charger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Demowallbox + + + +Zu Demonstrationszwecken. Wallbox mit festen Werten. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx new file mode 100644 index 0000000000..c374d2a493 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx @@ -0,0 +1,31 @@ +--- +title: E3/DC Easy Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC Easy Connect + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx new file mode 100644 index 0000000000..457329d5ae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Charge Core +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Charge Core + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx new file mode 100644 index 0000000000..448d566c6e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Charge Lite +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Charge Lite + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx new file mode 100644 index 0000000000..b16d62d0bd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Charge +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Charge + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx new file mode 100644 index 0000000000..dd33b0fae7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx @@ -0,0 +1,27 @@ +--- +title: Easee Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Easee Home + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx new file mode 100644 index 0000000000..597efd2665 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx @@ -0,0 +1,31 @@ +--- +title: Ebee Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ebee Wallbox + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx new file mode 100644 index 0000000000..fc08f2bca0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx @@ -0,0 +1,31 @@ +--- +title: echarge cPH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPH1 + + + +Als Betriebsmodus muss `manual` ausgewählt sein + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx new file mode 100644 index 0000000000..21d39bf964 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx @@ -0,0 +1,23 @@ +--- +title: echarge cPH2, cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPH2, cPμ2 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx new file mode 100644 index 0000000000..2b99761d93 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx @@ -0,0 +1,39 @@ +--- +title: EcoHarmony EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EcoHarmony EVSE EPC 2.0 Plus + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx new file mode 100644 index 0000000000..d9f3b3f146 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx @@ -0,0 +1,33 @@ +--- +title: Edgetech Smart EVSE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartevse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Edgetech Smart EVSE + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx new file mode 100644 index 0000000000..9559d9b4c4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx @@ -0,0 +1,22 @@ +--- +title: EEBUS kompatibel +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eebus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EEBUS kompatibel + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx new file mode 100644 index 0000000000..6555c5d030 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx @@ -0,0 +1,33 @@ +--- +title: Elecq Biz +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elecq Biz + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx new file mode 100644 index 0000000000..d4b9cb2b1d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx @@ -0,0 +1,33 @@ +--- +title: Elecq Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elecq Home + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx new file mode 100644 index 0000000000..88b6e95cba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx @@ -0,0 +1,33 @@ +--- +title: Elecq Station +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elecq Station + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx new file mode 100644 index 0000000000..dcee848127 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx @@ -0,0 +1,36 @@ +--- +title: eledio go +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# eledio go + + + +https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx new file mode 100644 index 0000000000..cd7341d763 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Connect 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Connect 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx new file mode 100644 index 0000000000..b4e7b608e2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx @@ -0,0 +1,31 @@ +--- +title: Elli Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Connect + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx new file mode 100644 index 0000000000..7c96c6e5a6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Pro 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx new file mode 100644 index 0000000000..65082823ca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Pro Eichrecht 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Pro Eichrecht 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx new file mode 100644 index 0000000000..234d71f3f0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Elli Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elli Charger Pro + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx new file mode 100644 index 0000000000..90d7722850 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx @@ -0,0 +1,24 @@ +--- +title: EM2GO Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go-home.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EM2GO Home + + + +Benötigt FW version >= E3C_V1.1. mA Regelung benötigt FW version >= E3C_V1.3. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx new file mode 100644 index 0000000000..465546684d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx @@ -0,0 +1,29 @@ +--- +title: EM2GO Pro Power, OCPP/ONC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EM2GO Pro Power, OCPP/ONC + + + +Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP/ONC: 3.15) + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx new file mode 100644 index 0000000000..ebbf437be2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx @@ -0,0 +1,33 @@ +--- +title: EN+ AC EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EN+ AC EV Charger + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx new file mode 100644 index 0000000000..04fe3749f2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx @@ -0,0 +1,36 @@ +--- +title: enercab smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# enercab smart + + + +https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx new file mode 100644 index 0000000000..0ce47cbff5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx @@ -0,0 +1,31 @@ +--- +title: Ensto Chago Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ensto Chago Wallbox + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx new file mode 100644 index 0000000000..34b172692c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx @@ -0,0 +1,33 @@ +--- +title: EntraTek Power Dot Fix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EntraTek Power Dot Fix + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx new file mode 100644 index 0000000000..973bfc6056 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -0,0 +1,33 @@ +--- +title: EntraTek Power Dot Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EntraTek Power Dot Pro 2 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx new file mode 100644 index 0000000000..9fa1d98fbf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: E.ON Drive eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive eBox + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx new file mode 100644 index 0000000000..df665bef5d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx @@ -0,0 +1,31 @@ +--- +title: E.ON Drive vBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive vBox + + + +1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx new file mode 100644 index 0000000000..f997dfda9f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx @@ -0,0 +1,31 @@ +--- +title: ESL Walli LIGHT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ESL Walli LIGHT + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx new file mode 100644 index 0000000000..a1234d1645 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx @@ -0,0 +1,29 @@ +--- +title: eSystems ghostONE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# eSystems ghostONE + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx new file mode 100644 index 0000000000..917ebda6aa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx @@ -0,0 +1,33 @@ +--- +title: Etrel INCH Duo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel-duo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Etrel INCH Duo + + + +Die Wallbox muss sich im "Power" Modus befinden. + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx new file mode 100644 index 0000000000..c6e0dd292d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx @@ -0,0 +1,27 @@ +--- +title: Etrel INCH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Etrel INCH + + + +Die Wallbox muss sich im "Power" Modus befinden. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx new file mode 100644 index 0000000000..f34690357f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx @@ -0,0 +1,34 @@ +--- +title: EVBox Elvi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-evbox-elvi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVBox Elvi + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # optional`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-evbox-elvi + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # optional + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx new file mode 100644 index 0000000000..3dc1991fa8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx @@ -0,0 +1,25 @@ +--- +title: EVBox Livo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/livo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVBox Livo + + + +Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzurichten. Danach erkennt das Ladegerät evcc als HEMS-Gerät im Netzwerk. Verwende das Installationstool, um evcc als HEMS auszuwählen. Kopiere anschließend den angegebenen SKI aus der Installations-App und fügen ihn zu Ihrem YAML hinzu. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx new file mode 100644 index 0000000000..66343afe2a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx @@ -0,0 +1,33 @@ +--- +title: EVSE DIN +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVSE DIN + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx new file mode 100644 index 0000000000..720e20a4b4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx @@ -0,0 +1,21 @@ +--- +title: EVSE-WiFi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evsewifi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EVSE-WiFi + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx new file mode 100644 index 0000000000..fa1915c2c6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx @@ -0,0 +1,35 @@ +--- +title: Free2Move eProWallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Free2Move eProWallbox + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx new file mode 100644 index 0000000000..56ca6cd792 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -0,0 +1,33 @@ +--- +title: Free2move eSolutions eProWallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-esolutions.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Free2move eSolutions eProWallbox + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-esolutions + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx new file mode 100644 index 0000000000..bb728764bb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx @@ -0,0 +1,33 @@ +--- +title: Fronius Wattpilot +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Wattpilot + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx new file mode 100644 index 0000000000..8dadfcb8f7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx @@ -0,0 +1,31 @@ +--- +title: Garo GLB, GLB+, LS4, LS4 compact +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo GLB, GLB+, LS4, LS4 compact + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx new file mode 100644 index 0000000000..44b5105cfa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx @@ -0,0 +1,33 @@ +--- +title: go-e Charger Gemini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger Gemini + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx new file mode 100644 index 0000000000..f1aec89ca1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx @@ -0,0 +1,28 @@ +--- +title: go-e Charger HOME+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger HOME+ + + + +Benötigt mindestens Firmware 052.1 oder neuer. +Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". +In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx new file mode 100644 index 0000000000..5c26e6487e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx @@ -0,0 +1,26 @@ +--- +title: go-e Charger HOMEfix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger HOMEfix + + + +Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx new file mode 100644 index 0000000000..b21c0f1dad --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx @@ -0,0 +1,33 @@ +--- +title: go-e Charger PRO +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger PRO + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx new file mode 100644 index 0000000000..6e98ee746f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx @@ -0,0 +1,33 @@ +--- +title: go-e Charger V3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger V3 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx new file mode 100644 index 0000000000..b992f86a44 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx @@ -0,0 +1,31 @@ +--- +title: HardyBarth cPH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HardyBarth cPH1 + + + +Als Betriebsmodus muss `manual` ausgewählt sein + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx new file mode 100644 index 0000000000..d5282058c8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx @@ -0,0 +1,23 @@ +--- +title: HardyBarth cPH2, cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HardyBarth cPH2, cPμ2 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx new file mode 100644 index 0000000000..4158348201 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx @@ -0,0 +1,38 @@ +--- +title: Heidelberg Energy Control +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Heidelberg Energy Control + + + +Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx new file mode 100644 index 0000000000..815f7bf64a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: Hesotec eSat, eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hesotec eSat, eBox + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx new file mode 100644 index 0000000000..5c3160a3ba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx @@ -0,0 +1,36 @@ +--- +title: Home Assistant Schalter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homeassistant-switch.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Home Assistant Schalter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx new file mode 100644 index 0000000000..6ef7a0d2b1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx @@ -0,0 +1,38 @@ +--- +title: Homecharge Homecharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-homecharge.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Homecharge Homecharger + + + +Die Verwendung mit evcc erfordert einen eingebauten Stromzähler (Ausführungen HC11L/HC22L Energy oder Profi). +Die OCPP-Konfiguration erfolgt über den EFR-SECC-Ladecontroller über die URL http://host/secc. +Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händler. + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-homecharge + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx new file mode 100644 index 0000000000..765f81fd06 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx @@ -0,0 +1,41 @@ +--- +title: Homematic IP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homematic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Homematic IP + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx new file mode 100644 index 0000000000..974c6e90f0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx @@ -0,0 +1,30 @@ +--- +title: HomeWizard +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homewizard.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HomeWizard + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx new file mode 100644 index 0000000000..a29c21fadb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx @@ -0,0 +1,33 @@ +--- +title: Huawei SCharger-7KS-S0 / 22KT-S0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SCharger-7KS-S0 / 22KT-S0 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx new file mode 100644 index 0000000000..db410ccdea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx @@ -0,0 +1,27 @@ +--- +title: IDM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/idm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IDM + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx new file mode 100644 index 0000000000..3ac91cf6fa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx @@ -0,0 +1,1962 @@ +--- +title: Chargers +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Chargers + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx new file mode 100644 index 0000000000..f2e013c84a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx @@ -0,0 +1,28 @@ +--- +title: Innogy eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Innogy eBox + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx new file mode 100644 index 0000000000..ecc499bd64 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx @@ -0,0 +1,21 @@ +--- +title: INRO Pantabox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pantabox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# INRO Pantabox + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx new file mode 100644 index 0000000000..7a7aa20ec3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx @@ -0,0 +1,31 @@ +--- +title: Juice Charger Me +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Juice Charger Me + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx new file mode 100644 index 0000000000..add5607e18 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Junkers SG Ready +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Junkers SG Ready + + + +Eingebunden via [EMSESP](https://emsesp.org/) + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx new file mode 100644 index 0000000000..576315e128 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx @@ -0,0 +1,31 @@ +--- +title: Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E + + + +Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx new file mode 100644 index 0000000000..5563e413cc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx @@ -0,0 +1,41 @@ +--- +title: KEBA KeContact P20, P30, C/X Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P20, P30, C/X Series + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx new file mode 100644 index 0000000000..6779ab31aa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx @@ -0,0 +1,41 @@ +--- +title: KEBA KeContact P40, P40 Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P40, P40 Pro + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx new file mode 100644 index 0000000000..5cbdc0b7b5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx @@ -0,0 +1,28 @@ +--- +title: Kermi x-center pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kermi x-center pro + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx new file mode 100644 index 0000000000..7dd39d743e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx @@ -0,0 +1,29 @@ +--- +title: Kontron Solar Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kontron Solar Charger + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx new file mode 100644 index 0000000000..86348fbd8d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx @@ -0,0 +1,40 @@ +--- +title: Kostal Enector +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Enector + + + +Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). +Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. +Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx new file mode 100644 index 0000000000..0dfbe570c2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx @@ -0,0 +1,35 @@ +--- +title: KSE wBX16 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KSE wBX16 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx new file mode 100644 index 0000000000..ae8a1f0277 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx @@ -0,0 +1,36 @@ +--- +title: LadeFoxx EvLoad, Mikro 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LadeFoxx EvLoad, Mikro 2.0 + + + +1 Ladepunkt), optional`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx new file mode 100644 index 0000000000..294f6bd8b1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx @@ -0,0 +1,34 @@ +--- +title: Lambda EU-L Serie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Lambda EU-L Serie + + + +Energiemanagementeinstellungen am Gerät: + +- E-Meter Kommunikationsart: "ModBus Client" +- E-Meter Messpunkt: "Pos. E-Überschuss" + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx new file mode 100644 index 0000000000..4cc424b501 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx @@ -0,0 +1,38 @@ +--- +title: LRT HOME Essential+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LRT HOME Essential+ + + + +Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx new file mode 100644 index 0000000000..7a3553001b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMEDIO Professional +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMEDIO Professional + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx new file mode 100644 index 0000000000..4bfe3ffffb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON 4Business 700 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON 4Business 700 + + + +Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx new file mode 100644 index 0000000000..8df966c59b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -0,0 +1,40 @@ +--- +title: Mennekes AMTRON 4You 300 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON 4You 300 + + + +Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). +Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. +Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx new file mode 100644 index 0000000000..fc9715e9cb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON 4You 500 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON 4You 500 + + + +Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx new file mode 100644 index 0000000000..4694b8715e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON ChargeControl +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON ChargeControl + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx new file mode 100644 index 0000000000..cf8d55ea1f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx @@ -0,0 +1,40 @@ +--- +title: Mennekes AMTRON Compact 2.0s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Compact 2.0s + + + +Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). +Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. +Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx new file mode 100644 index 0000000000..96b0d859a3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx @@ -0,0 +1,28 @@ +--- +title: Mennekes AMTRON Premium +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Premium + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx new file mode 100644 index 0000000000..2a83abd777 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx @@ -0,0 +1,31 @@ +--- +title: Mennekes AMTRON Professional +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Professional + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx new file mode 100644 index 0000000000..4aa744660a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -0,0 +1,28 @@ +--- +title: Mennekes AMTRON Xtra +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Xtra + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx new file mode 100644 index 0000000000..84022299a3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -0,0 +1,38 @@ +--- +title: Mennekes eMobility Gateway (ACU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes eMobility Gateway (ACU) + + + +Zur Konfiguration die Weboberfläche der ACU aufrufen. +Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J +Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx new file mode 100644 index 0000000000..255f35deab --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx @@ -0,0 +1,38 @@ +--- +title: Mennekes Smart (ACU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes Smart (ACU) + + + +Zur Konfiguration die Weboberfläche der ACU aufrufen. +Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J +Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx new file mode 100644 index 0000000000..32f5c63e10 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -0,0 +1,38 @@ +--- +title: Mennekes Smart T (ACU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes Smart T (ACU) + + + +Zur Konfiguration die Weboberfläche der ACU aufrufen. +Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J +Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx new file mode 100644 index 0000000000..7d6b77542e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -0,0 +1,29 @@ +--- +title: my-PV AC ELWA 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-elwa-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC ELWA 2 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx new file mode 100644 index 0000000000..51c16355db --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx @@ -0,0 +1,30 @@ +--- +title: my-PV AC THOR, AC THOR 9s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC THOR, AC THOR 9s + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx new file mode 100644 index 0000000000..af51c6d3b9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx @@ -0,0 +1,30 @@ +--- +title: myStrom Switch +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mystrom.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# myStrom Switch + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx new file mode 100644 index 0000000000..c2cb820d14 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx @@ -0,0 +1,26 @@ +--- +title: NRGKick Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrgkick-connect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# NRGKick Connect + + + +NRGkick Ladeeinheit via HTTP (älter als 2022/2023) + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx new file mode 100644 index 0000000000..0cac5e27bd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx @@ -0,0 +1,38 @@ +--- +title: NRGKick Gen2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrggen2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# NRGKick Gen2 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx new file mode 100644 index 0000000000..229ff8177a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx @@ -0,0 +1,39 @@ +--- +title: OBO Bettermann Ion +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OBO Bettermann Ion + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx new file mode 100644 index 0000000000..62e94ade0e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx @@ -0,0 +1,54 @@ +--- +title: OCPP 1.6J kompatibel (Smart Charging) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OCPP 1.6J kompatibel (Smart Charging) + + + +Bei OCPP verbindet sich die Wallbox (Client) zu evcc (Server). +Die Wallbox muss daher evcc via Hostname (funktionierende DNS-Auflösung erforderlich!) oder über die IP-Adresse auf Port 8887 erreichen können. +Standardmäßig wird die erste eingehende Verbindung mit einer beliebigen Ladepunktkennung verwendet. +Um mehrere Ladepunkte eindeutig zuordnen zu können müssen die jeweilige Stationskennung (`stationid: `) und Anschlussnummer (`connector: `) hinterlegt werden. +Viele Wallboxen fügen die `stationid` automatisch der Backend-URL hinzu, bei manchen muss dies manuell geschehen `ws://:8887/`. +Für Zählermesswerte sollte in der Wallbox wenn möglich ein kurzes Zeitintervall (< 10s) konfiguriert werden. +Nutzen Sie Ihre RFID-Tags (dies ermöglicht z. B. eine Fahrzeugidentifizierung) oder setzen Sie Ihre Wallbox auf "freies Laden" oder "Autostart" um die für die Ladefreigabe benötigte Transaktion zu erzeugen. + +Falls die Wallbox keine Möglichkeit bietet die Transaktionen lokal zu starten, kann die erweiterte Option `remotestart` genutzt werden um automatisch eine Transaktion zu starten sobald ein Fahrzeug angeschlossen wird. +Dies sollte nur in Ausnahmefällen erforderlich sein. + +Voraussetzungen: +* Ggf. zuvor konfigurierte OCPP-Profile (z.B. durch eine andere Backend-Anbindung) in der Wallboxkonfiguration entfernen +* Backend-URL (Central System) in der Wallboxkonfiguration: `ws://[evcc-adresse]:8887/` (eventuell noch um `stationid` erweitern) +* Protokoll: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// o.ä. +* Keine Verschlüsselung, keine Authentifizierung, kein Passwort +* Verbindung über das lokale Netzwerk + +Die konkrete Konfiguration und der tatsächlich nutzbare Funktionsumfang hängen vom Wallbox-Modell und dessen Software ab. + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx new file mode 100644 index 0000000000..3d6de169c3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx @@ -0,0 +1,26 @@ +--- +title: OpenEVSE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openevse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OpenEVSE + + + +Benötigt mindestens Firmware 7.0 oder neuer. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx new file mode 100644 index 0000000000..fbd569aa01 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx @@ -0,0 +1,21 @@ +--- +title: openWB Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-pro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB Pro + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx new file mode 100644 index 0000000000..4ba305dfc2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx @@ -0,0 +1,30 @@ +--- +title: openWB series2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB series2 + + + +Die Wallbox muss als Ladepunkt konfiguriert sein. + + +1 Ladepunkt), optional + phases1p3p: false # Phasenumschaltung vorhanden, optional`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx new file mode 100644 index 0000000000..d9746900f6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx @@ -0,0 +1,44 @@ +--- +title: openWB Software 2.x +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB Software 2.x + + + +Erfordert [`Software 2.x`](https://github.com/openWB/core). +Folgende Änderungen sind unter dem `Einstellungen`-Reiter erforderlich: + +* Steuerungsmodus: `secondary` +* Steuerung über Modbus als secondary: `An` + + +1 Ladepunkt), optional + phases1p3p: true # Phasenumschaltung vorhanden, optional`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx new file mode 100644 index 0000000000..336896e3d6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx @@ -0,0 +1,31 @@ +--- +title: Optec Mobility One +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Optec Mobility One + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx new file mode 100644 index 0000000000..62c438bd9e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx @@ -0,0 +1,33 @@ +--- +title: Orbis Viaris +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-orbis.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Orbis Viaris + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-orbis + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx new file mode 100644 index 0000000000..0798c42b6c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx @@ -0,0 +1,27 @@ +--- +title: PC Electric Garo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pcelectric-garo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# PC Electric Garo + + + +Es können momentan nur als Master konfigurierte Geräte verwendet werden! + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx new file mode 100644 index 0000000000..c1b9e64dab --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx @@ -0,0 +1,31 @@ +--- +title: Peblar Home, Home Plus, Business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Home, Home Plus, Business + + + +Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx new file mode 100644 index 0000000000..70a17c8f50 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx @@ -0,0 +1,36 @@ +--- +title: Phoenix Contact CHARX +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact CHARX + + + +1 Ladepunkt), optional`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx new file mode 100644 index 0000000000..a22dc03947 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -0,0 +1,26 @@ +--- +title: Phoenix Contact EM-CP-PP-ETH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-em-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EM-CP-PP-ETH + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx new file mode 100644 index 0000000000..1ce4dfef3a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx new file mode 100644 index 0000000000..8b1d2bd42b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx new file mode 100644 index 0000000000..da755f7761 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx new file mode 100644 index 0000000000..13bd5e578d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -0,0 +1,31 @@ +--- +title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx new file mode 100644 index 0000000000..1dce994e0f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -0,0 +1,33 @@ +--- +title: Phoenix Contact EV-SER +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-ser.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Phoenix Contact EV-SER + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx new file mode 100644 index 0000000000..d9b0a30cba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx @@ -0,0 +1,40 @@ +--- +title: Plugchoice +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/plugchoice.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Plugchoice + + + +Über Plugchoice angeschlossene Ladegeräte können die OCPP-Proxy-Funktionalität nutzen, um eine Verbindung zu anderen Backoffices herzustellen und gleichzeitig die volle Kontrolle über EVCC zu behalten. Dies ermöglicht eine nahtlose Verwaltung der bei Plugchoice registrierten Ladegeräte direkt vom EVCC aus. + +Für eine optimierte Zählerablesung empfehlen wir, die folgenden Einstellungen im Plugchoice-Portal unter `Konfiguration` zu konfigurieren: + +– Stellen Sie `MeterValueSampleInterval` auf 10 Sekunden (oder ein anderes Intervall Ihrer Wahl) ein. +– Stellen Sie `MeterValuesSampledData` auf `Energy.Active.Import.Register,Current.Offered,Current.Import,Voltage` ein. + +Diese Anpassungen ermöglichen eine häufigere und detailliertere Meldung der Ladedaten an EVCC. + + +1 Ladepunkt), Anschluss-ID (üblicherweise 1)`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx new file mode 100644 index 0000000000..21fbffc3ff --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -0,0 +1,22 @@ +--- +title: Porsche Mobile Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Porsche Mobile Charger Connect + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx new file mode 100644 index 0000000000..38702225a8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -0,0 +1,22 @@ +--- +title: Porsche Mobile Charger Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Porsche Mobile Charger Plus + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx new file mode 100644 index 0000000000..f95f2f6e01 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx @@ -0,0 +1,29 @@ +--- +title: Porsche Wallbox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/porsche-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Porsche Wallbox + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx new file mode 100644 index 0000000000..b636ea9625 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht Alpha XT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht Alpha XT + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx new file mode 100644 index 0000000000..97a070820a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht Mono XT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht Mono XT + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx new file mode 100644 index 0000000000..f3c8ef3e99 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht PNI +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht PNI + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx new file mode 100644 index 0000000000..f0394a0ac3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx @@ -0,0 +1,66 @@ +--- +title: Pracht XT+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht XT+ + + + +1 Ladepunkt), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx new file mode 100644 index 0000000000..4b9dbce34f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx @@ -0,0 +1,33 @@ +--- +title: Pulsares SimpleBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsares.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pulsares SimpleBox + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx new file mode 100644 index 0000000000..3b44162c12 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx @@ -0,0 +1,23 @@ +--- +title: Pulsatrix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsatrix.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pulsatrix + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx new file mode 100644 index 0000000000..d107a6d43c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx @@ -0,0 +1,38 @@ +--- +title: Qcells Q.HOME EDRIVE A +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME EDRIVE A + + + +Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx new file mode 100644 index 0000000000..46e0ecba3f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx @@ -0,0 +1,28 @@ +--- +title: Schneider EVlink Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/schneider-evlink-v3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Schneider EVlink Pro + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx new file mode 100644 index 0000000000..823e8052be --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx @@ -0,0 +1,33 @@ +--- +title: Schrack i-CHARGE CION +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Schrack i-CHARGE CION + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx new file mode 100644 index 0000000000..c5b75790d0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -0,0 +1,38 @@ +--- +title: SENEC Wallbox pro s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SENEC Wallbox pro s + + + +Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx new file mode 100644 index 0000000000..90c4df5132 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx @@ -0,0 +1,36 @@ +--- +title: SENEC Wallbox pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SENEC Wallbox pro + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx new file mode 100644 index 0000000000..8430a32a58 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx @@ -0,0 +1,36 @@ +--- +title: Shelly +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx new file mode 100644 index 0000000000..a95fbec292 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -0,0 +1,31 @@ +--- +title: Siemens Versicharge GEN3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/versicharge.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens Versicharge GEN3 + + + +Erfordert Firmware >= 2.135 + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx new file mode 100644 index 0000000000..ce2c96e2ea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Charger Connect + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx new file mode 100644 index 0000000000..a12627c2af --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda Charger Pro Eichrecht +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Charger Pro Eichrecht + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx new file mode 100644 index 0000000000..2290c464a1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Charger Pro + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx new file mode 100644 index 0000000000..b7dc6b671e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -0,0 +1,29 @@ +--- +title: Skoda iV Charger Connect+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda iV Charger Connect+ + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx new file mode 100644 index 0000000000..b813a61d22 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx @@ -0,0 +1,28 @@ +--- +title: SMA EV Charger, eCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA EV Charger, eCharger + + + +Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx new file mode 100644 index 0000000000..61f6c01afe --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx @@ -0,0 +1,33 @@ +--- +title: Smartfox Pro Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro Charger + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx new file mode 100644 index 0000000000..1bd8cafd72 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx @@ -0,0 +1,21 @@ +--- +title: smartWB +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartwb.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# smartWB + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx new file mode 100644 index 0000000000..24f535390d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -0,0 +1,41 @@ +--- +title: SolarEdge Home EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarEdge Home EV Charger + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx new file mode 100644 index 0000000000..d120715344 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx @@ -0,0 +1,38 @@ +--- +title: Solax X3-EVC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax X3-EVC + + + +Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx new file mode 100644 index 0000000000..58d7bb72c3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx @@ -0,0 +1,27 @@ +--- +title: Sonnen sonnenCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen sonnenCharger + + + +Die Wallbox muss sich im "Power" Modus befinden. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx new file mode 100644 index 0000000000..b187ccf0ea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -0,0 +1,31 @@ +--- +title: Spelsberg Wallbox Smart Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Spelsberg Wallbox Smart Pro + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx new file mode 100644 index 0000000000..17e1380699 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx @@ -0,0 +1,33 @@ +--- +title: Stark in Strom Easy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stark in Strom Easy + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx new file mode 100644 index 0000000000..0e82b0b167 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Stiebel Eltron LWA/LWZ (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stiebel Eltron LWA/LWZ (SG Ready) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx new file mode 100644 index 0000000000..06d76f6cc1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Stiebel Eltron WPM (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-wpm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stiebel Eltron WPM (SG Ready) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx new file mode 100644 index 0000000000..3ee7b944e7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx @@ -0,0 +1,41 @@ +--- +title: Sungrow AC011E-01 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow AC011E-01 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx new file mode 100644 index 0000000000..c19099b74b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx @@ -0,0 +1,33 @@ +--- +title: Sungrow AC011E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-sungrow.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow AC011E + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-sungrow + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx new file mode 100644 index 0000000000..3f8e724bf4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx @@ -0,0 +1,36 @@ +--- +title: Tasmota einphasig +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tasmota.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota einphasig + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx new file mode 100644 index 0000000000..af8cb81b98 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -0,0 +1,27 @@ +--- +title: Tecalor THZ (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tecalor THZ (SG Ready) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx new file mode 100644 index 0000000000..7ed51d2d09 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx @@ -0,0 +1,31 @@ +--- +title: TechniSat Technivolt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TechniSat Technivolt + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx new file mode 100644 index 0000000000..50c87660ab --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx @@ -0,0 +1,24 @@ +--- +title: Tesla TWC3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla TWC3 + + + +Die TWC Wallbox ist nicht direkt regelbar. Die Regelung erfolgt über das Fahrzeug. Das Fahrzeug muss am TWC3 Ladepunkt ausgewählt sein. Aktuell ausschließlich mit [Tesla Fahrzeugen](https://docs.evcc.io/docs/devices/vehicles#tesla) nutzbar. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx new file mode 100644 index 0000000000..b9009a1e18 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx @@ -0,0 +1,26 @@ +--- +title: Tessie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tessie.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tessie + + + +Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung des Ladezustands und die Konfiguration des maximalen Stroms. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx new file mode 100644 index 0000000000..7453e94e74 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx @@ -0,0 +1,38 @@ +--- +title: Tigo GO EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tigo GO EV Charger + + + +Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx new file mode 100644 index 0000000000..cbfeaa496d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -0,0 +1,38 @@ +--- +title: TinkerForge WARP Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP Charger Pro + + + +WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx new file mode 100644 index 0000000000..63b110d8bd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -0,0 +1,38 @@ +--- +title: TinkerForge WARP Charger Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP Charger Smart + + + +WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx new file mode 100644 index 0000000000..a2087d6d2b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -0,0 +1,36 @@ +--- +title: TinkerForge WARP3 Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP3 Charger Pro + + + +Die automatische Phasenumschaltung bei 1p Fahrzeugen muss deaktiviert sein. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx new file mode 100644 index 0000000000..69846404ec --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -0,0 +1,33 @@ +--- +title: TinkerForge WARP3 Charger Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3-smart.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TinkerForge WARP3 Charger Smart + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx new file mode 100644 index 0000000000..e577e404c2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,30 @@ +--- +title: TP-Link H-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tplink.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link H-Series Smart Plug + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx new file mode 100644 index 0000000000..e061ba0e87 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,34 @@ +--- +title: TP-Link Tapo P-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tapo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link Tapo P-Series Smart Plug + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx new file mode 100644 index 0000000000..d52f371489 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx @@ -0,0 +1,31 @@ +--- +title: Ubitricity Heinz +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ubitricity Heinz + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx new file mode 100644 index 0000000000..e82c26347e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx @@ -0,0 +1,23 @@ +--- +title: V2C Trydan +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/trydan.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# V2C Trydan + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx new file mode 100644 index 0000000000..e5d4e67049 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -0,0 +1,28 @@ +--- +title: Vaillant SensoNET (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vaillant.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vaillant SensoNET (SG Ready) + + + +Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird durch die ID identifiziert. Die Boost Temperatur wird in Grad Celsius angegeben. Ist eine Boost Temperatur angegeben, wird die Boostzone aktiviert, anderenfalls Warmwasser. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx new file mode 100644 index 0000000000..ea9ecb7d05 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx @@ -0,0 +1,31 @@ +--- +title: Vestel EVC04 Home Smart, Connect Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vestel EVC04 Home Smart, Connect Plus + + + +1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx new file mode 100644 index 0000000000..c1c5da1cb9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -0,0 +1,29 @@ +--- +title: Victron EV Charging Station (via GX) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EV Charging Station (via GX) + + + +Trage den Host des GX-Gerätes (nicht der Wallbox) ein. Die Wallbox muss sich im Modus "Manual" befinden und Modbus ID 100 konfiguriert sein. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx new file mode 100644 index 0000000000..0e1ebfc8c3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx @@ -0,0 +1,29 @@ +--- +title: Victron EV Charging Station +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron-evcs.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EV Charging Station + + + +Trage den Host der Wallbox (nicht des GX-Geräts) ein und stelle sicher, dass die Wallbox sich im Modus "Manual" befindet. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx new file mode 100644 index 0000000000..18ffb396a7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -0,0 +1,30 @@ +--- +title: Viessmann Heatpump (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/viessmann.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Viessmann Heatpump (SG Ready) + + + +Einmalige Warmwasserbereitung auf eine konfigurierbare Solltemperatur. Das Gerät entscheidet eigenständig, ob die Wärmepumpe oder die elektrische Zusatzheizung (falls vorhanden) genutzt wird. + + + Einstellungen -> Kommunikationsmodul -> Seriennummer) + installation_id: # Installation ID, siehe https://docs.evcc.io/en/docs/devices/heating#viessmann + device_id: 0 # Device ID, normalerweise \`0\` + target_temperature: 45 # Zieltemperatur für Einmal-Warmwasser-Zubereitung (°C), max. 60°C`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx new file mode 100644 index 0000000000..3325e35d37 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx @@ -0,0 +1,39 @@ +--- +title: Viridian EV EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Viridian EV EVSE EPC 2.0 Plus + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx new file mode 100644 index 0000000000..b6fdaf99b8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen Charger Connect 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen Charger Connect 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx new file mode 100644 index 0000000000..6b06fbf8f8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen Charger Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen Charger Pro 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx new file mode 100644 index 0000000000..c99e491002 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen Charger Pro Eichrecht 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen Charger Pro Eichrecht 2 + + + +Die Wallbox muss im normalen Lademodus betrieben werden. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx new file mode 100644 index 0000000000..c62c584763 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -0,0 +1,31 @@ +--- +title: Volkswagen ID. Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen ID. Charger Connect + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx new file mode 100644 index 0000000000..fab670518c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -0,0 +1,29 @@ +--- +title: Volkswagen ID. Charger Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen ID. Charger Pro + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx new file mode 100644 index 0000000000..e767e9d7a5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time One +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time One + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx new file mode 100644 index 0000000000..e71f1369fb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time Source 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time Source 2 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx new file mode 100644 index 0000000000..f71a1d8e70 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time Source 2s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time Source 2s + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx new file mode 100644 index 0000000000..8cba9adbb9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx @@ -0,0 +1,24 @@ +--- +title: Volt Time Source +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volt Time Source + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx new file mode 100644 index 0000000000..d7dd84203c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx @@ -0,0 +1,31 @@ +--- +title: Wallbe Eco 2.0(s) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Eco 2.0(s) + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx new file mode 100644 index 0000000000..c7e188c01f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx @@ -0,0 +1,31 @@ +--- +title: Wallbe Eco +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Eco + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx new file mode 100644 index 0000000000..8a1336f455 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx @@ -0,0 +1,31 @@ +--- +title: Wallbe Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Pro + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx new file mode 100644 index 0000000000..45cfcedde7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Commander 2 (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Commander 2 (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx new file mode 100644 index 0000000000..970f13a9b1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Commander 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Commander 2 + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx new file mode 100644 index 0000000000..6c147c884e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Copper SB (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Copper SB (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx new file mode 100644 index 0000000000..33a94a6b01 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Copper SB +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Copper SB + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx new file mode 100644 index 0000000000..7ca98d6ee5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Max (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Max (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx new file mode 100644 index 0000000000..70a81a7dc2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Max +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Max + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx new file mode 100644 index 0000000000..172fb23942 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Plus (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Plus (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx new file mode 100644 index 0000000000..904fab7f39 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -0,0 +1,42 @@ +--- +title: wallbox Pulsar Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Plus + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx new file mode 100644 index 0000000000..2d4eeaf490 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -0,0 +1,38 @@ +--- +title: Walther Werke Basic Evo Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Walther Werke Basic Evo Pro + + + +Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx new file mode 100644 index 0000000000..6d3990bb06 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx @@ -0,0 +1,31 @@ +--- +title: Webasto Live +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Webasto Live + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx new file mode 100644 index 0000000000..cc3bbed86a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx @@ -0,0 +1,27 @@ +--- +title: Webasto NEXT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Webasto NEXT + + + +Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx new file mode 100644 index 0000000000..0440efb17b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx @@ -0,0 +1,31 @@ +--- +title: Webasto Unite +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Webasto Unite + + + +1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx new file mode 100644 index 0000000000..97fa1efa45 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx @@ -0,0 +1,23 @@ +--- +title: Weidmüller AC Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/weidmüller.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller AC Smart + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx new file mode 100644 index 0000000000..ec8e3c7796 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx @@ -0,0 +1,25 @@ +--- +title: Zaptec Go 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Go 2 + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx new file mode 100644 index 0000000000..892f2dbeff --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx @@ -0,0 +1,25 @@ +--- +title: Zaptec Go +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Go + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx new file mode 100644 index 0000000000..83b19e4d18 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx @@ -0,0 +1,25 @@ +--- +title: Zaptec Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Pro + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx new file mode 100644 index 0000000000..64d20c8755 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -0,0 +1,34 @@ +--- +title: Zewotherm EU-L Serie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zewotherm EU-L Serie + + + +Energiemanagementeinstellungen am Gerät: + +- E-Meter Kommunikationsart: "ModBus Client" +- E-Meter Messpunkt: "Pos. E-Überschuss" + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx new file mode 100644 index 0000000000..f88bb2b3b8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -0,0 +1,33 @@ +--- +title: ZJ Beny BCP EV charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-beny.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZJ Beny BCP EV charger + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-beny + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx new file mode 100644 index 0000000000..05e6f82e57 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx @@ -0,0 +1,139 @@ +--- +title: A-Tronix +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# A-Tronix + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx new file mode 100644 index 0000000000..0598b30e97 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx @@ -0,0 +1,62 @@ +--- +title: ABB A43, A44, B23, B24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB A43, A44, B23, B24 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx new file mode 100644 index 0000000000..97d8372e11 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx @@ -0,0 +1,102 @@ +--- +title: Acrel ADW300 Wireless Metering Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Acrel ADW300 Wireless Metering Meter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx new file mode 100644 index 0000000000..1767123f8d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx @@ -0,0 +1,38 @@ +--- +title: Ads-tec StoraXe +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/storaxe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ads-tec StoraXe + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx new file mode 100644 index 0000000000..e8200aa134 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx @@ -0,0 +1,182 @@ +--- +title: Alpha ESS Storion SMILE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/alpha-ess-smile.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alpha ESS Storion SMILE + + + +Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder App Zeiten für das Netzladen definiert werden. (Einstellungen->Funktionseinstellungen->Netzladen/Entladen) Hier sollte ein durchgehender Zeitraum (z.B: Ladezeit 1 00:00-23:00, Ladezeit 2 23:00-00:00) eingetragen werden. Den Schalter "Netzladen" aber deaktivieren. Die eigentliche Steuerung erfolgt über evcc. Der Entladestopp wird über eine geplante Netzladung mit einem Ziel-SoC von 10% realisiert. Alternativ können die Zeiten auch über Modbus konfiguriert werden. Dafür die Register `2134,2142,2135,2136,2144,2137,2175` auf die Werte `0,0,23,0,23,0,0,0` setzen. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx new file mode 100644 index 0000000000..f130e884b1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx @@ -0,0 +1,179 @@ +--- +title: Ampere Ampere.StoragePro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampere Ampere.StoragePro + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx new file mode 100644 index 0000000000..440d80e22e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Anker Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Anker Micro inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx new file mode 100644 index 0000000000..3269bbd6d1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx @@ -0,0 +1,22 @@ +--- +title: APsystems EZ1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/apsystems-ez1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# APsystems EZ1 + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx new file mode 100644 index 0000000000..b1e741b5af --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx @@ -0,0 +1,44 @@ +--- +title: AVM FritzDECT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fritzdect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# AVM FritzDECT + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx new file mode 100644 index 0000000000..c41d0e73cd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -0,0 +1,120 @@ +--- +title: Axitec AXIhycon 12-15H +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Axitec AXIhycon 12-15H + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx new file mode 100644 index 0000000000..8316da5f1c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -0,0 +1,62 @@ +--- +title: Bernecker Engineering MPM3PM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mpm3pm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bernecker Engineering MPM3PM + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx new file mode 100644 index 0000000000..c647d3f014 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx @@ -0,0 +1,130 @@ +--- +title: BGEtech DS100 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ds100.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BGEtech DS100 + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx new file mode 100644 index 0000000000..0b5dce5c2d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx @@ -0,0 +1,130 @@ +--- +title: BGEtech WS100 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ws100.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BGEtech WS100 + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx new file mode 100644 index 0000000000..608638a888 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -0,0 +1,54 @@ +--- +title: Bosch BPT-S 5 Hybrid +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bosch-bpt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bosch BPT-S 5 Hybrid + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx new file mode 100644 index 0000000000..3e097c9564 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Bosswerk Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Bosswerk Micro inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx new file mode 100644 index 0000000000..2c0f809f50 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx @@ -0,0 +1,62 @@ +--- +title: Carlo Gavazzi EM110/111/112 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM110/111/112 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx new file mode 100644 index 0000000000..8060895e58 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx @@ -0,0 +1,65 @@ +--- +title: Carlo Gavazzi EM24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM24 + + + +EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx new file mode 100644 index 0000000000..bcd372e093 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx @@ -0,0 +1,52 @@ +--- +title: Carlo Gavazzi EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM24_E1 + + + +EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. +Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx new file mode 100644 index 0000000000..183343d433 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx @@ -0,0 +1,74 @@ +--- +title: Carlo Gavazzi EM330/EM340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM330/EM340 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx new file mode 100644 index 0000000000..fde201846d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx @@ -0,0 +1,74 @@ +--- +title: Carlo Gavazzi EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM530/EM540 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx new file mode 100644 index 0000000000..03e0ba9f5d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx @@ -0,0 +1,62 @@ +--- +title: Carlo Gavazzi ET112 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi ET112 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx new file mode 100644 index 0000000000..df0fd9dd0b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx @@ -0,0 +1,74 @@ +--- +title: Carlo Gavazzi ET330/ET340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi ET330/ET340 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx new file mode 100644 index 0000000000..4f8f0459bd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx @@ -0,0 +1,29 @@ +--- +title: cFos PowerBrain Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cfos.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# cFos PowerBrain Meter + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx new file mode 100644 index 0000000000..4913718983 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx @@ -0,0 +1,38 @@ +--- +title: Demobatterie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-battery.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Demobatterie + + + +Zu Demonstrationszwecken. Hausbatterie mit festen Werten. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx new file mode 100644 index 0000000000..a9eea10c5e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx @@ -0,0 +1,97 @@ +--- +title: Demozähler +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Demozähler + + + +Zu Demonstrationszwecken. Zähler mit festen Werten. + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx new file mode 100644 index 0000000000..b54b13284c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: Deye 3p hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye 3p hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx new file mode 100644 index 0000000000..a8c602e952 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -0,0 +1,185 @@ +--- +title: Deye hp3 hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye hp3 hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx new file mode 100644 index 0000000000..ecdbcc3b76 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Deye Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye Micro inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx new file mode 100644 index 0000000000..bd3e96b7a6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: Deye Storage (hybrid) inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye Storage (hybrid) inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx new file mode 100644 index 0000000000..a2c6861fe6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Deye String inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Deye String inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx new file mode 100644 index 0000000000..ced4a791da --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx @@ -0,0 +1,42 @@ +--- +title: Discovergy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/discovergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Discovergy + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx new file mode 100644 index 0000000000..6e777f338f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx @@ -0,0 +1,30 @@ +--- +title: DSMR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dsmr.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DSMR + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx new file mode 100644 index 0000000000..2aa2c5fae7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx @@ -0,0 +1,34 @@ +--- +title: DZG DVH4013 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dzg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DZG DVH4013 + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx new file mode 100644 index 0000000000..721deb28a5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx @@ -0,0 +1,97 @@ +--- +title: E3/DC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC + + + +Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key (=RSCP-Passwort) muss im Hauskraftwerk unter Personalisieren/Benutzerprofil angelegt werden. Die IP-Adressen von evcc und des Hauskraftwerks müssen sich im selben Subnetz befinden. + +**Achtung**: Die aktive Batteriesteuerung überschreibt Einstellungen im Smart-Power/Betriebsbereich. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx new file mode 100644 index 0000000000..29837af174 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx @@ -0,0 +1,84 @@ +--- +title: Eastron SDM120-Modbus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm120.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM120-Modbus + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx new file mode 100644 index 0000000000..38337014d0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM220/230 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM220/230 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx new file mode 100644 index 0000000000..9dff8a8c0c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM630-Modbus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM630-Modbus + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx new file mode 100644 index 0000000000..a2408b439d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM72D-M +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm72.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM72D-M + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx new file mode 100644 index 0000000000..25c8b12d1a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -0,0 +1,62 @@ +--- +title: Eastron SDM72DM-V2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM72DM-V2 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx new file mode 100644 index 0000000000..8d461098e3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx @@ -0,0 +1,76 @@ +--- +title: Enphase IQ Envoy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/enphase.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Enphase IQ Envoy + + + +Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vom Typ "AC Battery" unterstützt. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx new file mode 100644 index 0000000000..8ee11a4d1d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -0,0 +1,32 @@ +--- +title: ESPHome DLMS Meter Austria +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/esphome-dlms-austria.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ESPHome DLMS Meter Austria + + + +Benötigt ein ESPHome Gerät mit der `dlms_meter` Komponente (z.B. von `github://SimonFischer04/esphome@dlms-meter`), +konfiguriert für österreichische DLMS-Zähler. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx new file mode 100644 index 0000000000..a1d4d8c87e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx @@ -0,0 +1,28 @@ +--- +title: ESPHome DSMR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ESPHome DSMR + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx new file mode 100644 index 0000000000..5665d4f5b1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx @@ -0,0 +1,73 @@ +--- +title: FENECON +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FENECON + + + +Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..dd45265132 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -0,0 +1,74 @@ +--- +title: FoxESS H1 Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FoxESS H1 Series Hybrid Inverter + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..0a83251695 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: FoxESS H3 Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FoxESS H3 Series Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..db5cff44fa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: FoxESS H3-Smart Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3-smart.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# FoxESS H3-Smart Series Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx new file mode 100644 index 0000000000..aeb56e21b6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx @@ -0,0 +1,28 @@ +--- +title: Fronius Ohmpilot +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-ohmpilot.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Ohmpilot + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx new file mode 100644 index 0000000000..515353965c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -0,0 +1,73 @@ +--- +title: Fronius Primo GEN24 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Primo GEN24 Plus + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx new file mode 100644 index 0000000000..3c6dbc17c6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -0,0 +1,48 @@ +--- +title: Fronius Smartmeter (über Wechselrichter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Smartmeter (über Wechselrichter) + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx new file mode 100644 index 0000000000..ebfa339507 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx @@ -0,0 +1,69 @@ +--- +title: Fronius Solar API V1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-solarapi-v1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Solar API V1 + + + +Solar API sollte nur als Fallback genutzt werden. Die Integration über Modbus ist bevorzugt. + +Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt. + +**Achtung**: Die aktive Batteriesteuerung sollte nur verwendet werden, wenn keine weiteren Einstellungen für die zeitabhängige Batteriesteuerung in der Wechselrichter-Konfiguration unter "Energiemanagement" - "Batteriemanagement" getätigt wurden, denn bestehende Einstellungen werden überschrieben. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx new file mode 100644 index 0000000000..20b404c71e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -0,0 +1,73 @@ +--- +title: Fronius Symo GEN24 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Symo GEN24 Plus + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx new file mode 100644 index 0000000000..cbd10dd517 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -0,0 +1,120 @@ +--- +title: Ginlong Solis Hybrid Inverter (RHI series) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ginlong Solis Hybrid Inverter (RHI series) + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx new file mode 100644 index 0000000000..cd8b88c9a8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -0,0 +1,120 @@ +--- +title: Ginlong Solis Hybrid Inverter (S Series) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ginlong Solis Hybrid Inverter (S Series) + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx new file mode 100644 index 0000000000..645a149fcd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx @@ -0,0 +1,62 @@ +--- +title: Ginlong Solis Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ginlong Solis Inverter + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx new file mode 100644 index 0000000000..87c3ba9b15 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx @@ -0,0 +1,38 @@ +--- +title: go-e Controller +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/go-e-controller.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Controller + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx new file mode 100644 index 0000000000..64eb78fef2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx @@ -0,0 +1,155 @@ +--- +title: GoodWe ET/EH/BH/BT Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe ET/EH/BH/BT Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx new file mode 100644 index 0000000000..60119199fc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -0,0 +1,48 @@ +--- +title: GoodWe GoodWe over Wifi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-wifi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe GoodWe over Wifi + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx new file mode 100644 index 0000000000..0809d0ea25 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: GoodWe SDT/DT Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe SDT/DT Inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx new file mode 100644 index 0000000000..4f78e350b4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx @@ -0,0 +1,156 @@ +--- +title: Growatt Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Growatt Hybrid Inverter + + + +Um die aktive Ladesteuerung nutzen zu können ist eine einmalige manuelle Einrichtung notwendig. +Es müssen die Modbusregister `1100, 1101, 1102` gleichzeitig (via "write multiple", FC 16) auf die Werte `0, 5947, 0` gesetzt werden. +Das kann zB. mit der [Modbus CLI](https://github.com/favalex/modbus-cli) gemacht werden: `modbus [...] H@1100=0 H@1101=5947 H@1102=0`. +Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modus, d.h. dieser kann nicht anderweitig genutzt werden. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx new file mode 100644 index 0000000000..f8b4211411 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx @@ -0,0 +1,150 @@ +--- +title: Growatt TL-X(H) Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Growatt TL-X(H) Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx new file mode 100644 index 0000000000..c992f77738 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx @@ -0,0 +1,90 @@ +--- +title: Homematic IP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homematic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Homematic IP + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx new file mode 100644 index 0000000000..187c382c7f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx @@ -0,0 +1,38 @@ +--- +title: HomeWizard kWh Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard-kwh.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HomeWizard kWh Meter + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx new file mode 100644 index 0000000000..e8ff6e6ce3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -0,0 +1,22 @@ +--- +title: HomeWizard Wi-Fi P1 Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# HomeWizard Wi-Fi P1 Meter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx new file mode 100644 index 0000000000..68fa9e9e09 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -0,0 +1,23 @@ +--- +title: Hoymiles HM & HMS Series (via AhoyDTU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-ahoydtu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hoymiles HM & HMS Series (via AhoyDTU) + + + + Inverter #[ID], optional`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx new file mode 100644 index 0000000000..55f5fa2e6a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -0,0 +1,22 @@ +--- +title: Hoymiles HM & HMS Series (via OpenDTU) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-opendtu.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hoymiles HM & HMS Series (via OpenDTU) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx new file mode 100644 index 0000000000..afcb6cc18b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx @@ -0,0 +1,74 @@ +--- +title: Huawei EMMA +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-emma.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei EMMA + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx new file mode 100644 index 0000000000..a32874a53b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx @@ -0,0 +1,104 @@ +--- +title: Huawei SmartLogger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-smartlogger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SmartLogger + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx new file mode 100644 index 0000000000..798459305d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -0,0 +1,32 @@ +--- +title: Huawei SUN2000 (SDongle) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-dongle.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SUN2000 (SDongle) + + + +Erfordert "Modbus/TCP". Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. +Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx new file mode 100644 index 0000000000..408b6a32de --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx @@ -0,0 +1,189 @@ +--- +title: Huawei SUN2000 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-sun2000.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SUN2000 + + + +Grid und Batterie erfordern den PowerSensor. +"Modbus/TCP" erfordert Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. +Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx new file mode 100644 index 0000000000..cf6acab8cc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx @@ -0,0 +1,52 @@ +--- +title: IAMMETER WEM3080 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IAMMETER WEM3080 + + + +Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). +Siehe https://www.iammeter.com/newsshow/net-energy-metering + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx new file mode 100644 index 0000000000..a7cff11808 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx @@ -0,0 +1,52 @@ +--- +title: IAMMETER WEM3080T/WEM3046T/WEM3050T +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IAMMETER WEM3080T/WEM3046T/WEM3050T + + + +Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). +Siehe https://www.iammeter.com/newsshow/net-energy-metering + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx new file mode 100644 index 0000000000..a69485b9e0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx @@ -0,0 +1,24 @@ +--- +title: IGEN Tech Solarman Logger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarman.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IGEN Tech Solarman Logger + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx new file mode 100644 index 0000000000..4fc892bea9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx @@ -0,0 +1,1626 @@ +--- +title: Meters +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Meters + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx new file mode 100644 index 0000000000..e840f09dcb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx @@ -0,0 +1,62 @@ +--- +title: inepro PRO380-MOD +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/inepro.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# inepro PRO380-MOD + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx new file mode 100644 index 0000000000..85f9888f1e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx @@ -0,0 +1,22 @@ +--- +title: IOmeter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iometer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IOmeter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx new file mode 100644 index 0000000000..9f18c74b02 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx @@ -0,0 +1,74 @@ +--- +title: Janitza B series, UMG series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Janitza B series, UMG series + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx new file mode 100644 index 0000000000..95a5cde714 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx @@ -0,0 +1,27 @@ +--- +title: KEBA KeContact E10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/keba-kecontact.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact E10 + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx new file mode 100644 index 0000000000..364ceb991e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -0,0 +1,74 @@ +--- +title: Kostal Energy Meter C (KEM-C) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Energy Meter C (KEM-C) + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx new file mode 100644 index 0000000000..5e3eaec0e7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -0,0 +1,62 @@ +--- +title: Kostal Energy Meter P (KEM-P) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Energy Meter P (KEM-P) + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx new file mode 100644 index 0000000000..73fc1da83d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx @@ -0,0 +1,54 @@ +--- +title: Kostal Piko Hybrid +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko Hybrid + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx new file mode 100644 index 0000000000..8998deab6e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx @@ -0,0 +1,24 @@ +--- +title: Kostal Piko (legacy) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-legacy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko (legacy) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx new file mode 100644 index 0000000000..690832a957 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx @@ -0,0 +1,22 @@ +--- +title: Kostal Piko MP Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko MP Plus + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx new file mode 100644 index 0000000000..ec4a1eae3e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx @@ -0,0 +1,38 @@ +--- +title: Kostal Piko, Piko BA +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko, Piko BA + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx new file mode 100644 index 0000000000..2f0d2b0510 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -0,0 +1,80 @@ +--- +title: Kostal Plenticore Hybrid, inkl. Netzladung der Hausbatterie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore-gen2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Plenticore Hybrid, inkl. Netzladung der Hausbatterie + + + +Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. **_Ist grundsätzlich anwendbar für verschiedene Wechselrichter Generationen (G1/G2/G3)._** +**Das Netzladen der Batterie steht mit dieser Vorlage zur Verfügung, ist aktuell jedoch inkompatibel mit wenigen älteren Wechselrichtern - _sorgfältig testen_!** +_siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx new file mode 100644 index 0000000000..0e6e2ecf1b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -0,0 +1,82 @@ +--- +title: Kostal Plenticore Hybrid +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Plenticore Hybrid + + + +Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. +**Das Netzladen der Batterie steht nicht zur Verfügung!** _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx new file mode 100644 index 0000000000..d5c5a801ae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -0,0 +1,30 @@ +--- +title: Kostal Smart Energy Meter (über den Wechselrichter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Smart Energy Meter (über den Wechselrichter) + + + +Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorposition 1 (Haushaltsverbrauch) wird nicht unterstützt. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx new file mode 100644 index 0000000000..ef381a7bf3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx @@ -0,0 +1,27 @@ +--- +title: Kostal Smart Energy Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Smart Energy Meter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx new file mode 100644 index 0000000000..b8046a8c8b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx @@ -0,0 +1,79 @@ +--- +title: LG ESS Home 15 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-15.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LG ESS Home 15 + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx new file mode 100644 index 0000000000..cea57e9171 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx @@ -0,0 +1,82 @@ +--- +title: LG ESS Home 8/10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LG ESS Home 8/10 + + + +Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich 10.05.7433 / R2155 benötigt + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx new file mode 100644 index 0000000000..b4fd95746a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx @@ -0,0 +1,74 @@ +--- +title: Loxone Miniserver +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/loxone.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Loxone Miniserver + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx new file mode 100644 index 0000000000..c2f4545bf4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -0,0 +1,84 @@ +--- +title: M-TEC Energy Butler GEN2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# M-TEC Energy Butler GEN2 + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx new file mode 100644 index 0000000000..f037642050 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -0,0 +1,126 @@ +--- +title: M-TEC Energy Butler GEN3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# M-TEC Energy Butler GEN3 + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx new file mode 100644 index 0000000000..e0b1ca7ebb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx @@ -0,0 +1,57 @@ +--- +title: Marstek Venus Battery Storage +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/marstek-venus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Marstek Venus Battery Storage + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx new file mode 100644 index 0000000000..d07d2f0749 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx @@ -0,0 +1,28 @@ +--- +title: mhendriks P1 dongle +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# mhendriks P1 dongle + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx new file mode 100644 index 0000000000..3f702aa5a6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -0,0 +1,22 @@ +--- +title: my-PV AC ELWA 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC ELWA 2 + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx new file mode 100644 index 0000000000..f21341c735 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -0,0 +1,22 @@ +--- +title: my-PV AC ELWA-E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-e.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC ELWA-E + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx new file mode 100644 index 0000000000..531a511c52 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx @@ -0,0 +1,22 @@ +--- +title: my-PV AC•THOR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx new file mode 100644 index 0000000000..50b9dea362 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx @@ -0,0 +1,27 @@ +--- +title: my-PV WiFi Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mypv-wifi-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV WiFi Meter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx new file mode 100644 index 0000000000..c5b5623342 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx @@ -0,0 +1,38 @@ +--- +title: myStrom Switch +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mystrom.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# myStrom Switch + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx new file mode 100644 index 0000000000..6a46df9297 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx @@ -0,0 +1,73 @@ +--- +title: OpenEMS +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OpenEMS + + + +Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx new file mode 100644 index 0000000000..cd30c1d512 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx @@ -0,0 +1,62 @@ +--- +title: Orno OR-WE-516, OR-WE-517 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Orno OR-WE-516, OR-WE-517 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx new file mode 100644 index 0000000000..a73fb7f77b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx @@ -0,0 +1,22 @@ +--- +title: P1Monitor P1 Monitor +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# P1Monitor P1 Monitor + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx new file mode 100644 index 0000000000..3b2413c086 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx @@ -0,0 +1,77 @@ +--- +title: Plexlog +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/plexlog.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Plexlog + + + +Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `interval` nicht kleiner als 30 Sekunden gewählt werden. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx new file mode 100644 index 0000000000..382ffb6127 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx @@ -0,0 +1,48 @@ +--- +title: Powerdog +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerdog.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Powerdog + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx new file mode 100644 index 0000000000..bebe0d5074 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx @@ -0,0 +1,54 @@ +--- +title: Powerfox Poweropti +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerfox-poweropti.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Powerfox Poweropti + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx new file mode 100644 index 0000000000..87fd5561c9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -0,0 +1,63 @@ +--- +title: QCells Hybrid-Wechselrichter (Cloud) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/qcells-hybrid-cloud.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# QCells Hybrid-Wechselrichter (Cloud) + + + +Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. + +**Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx new file mode 100644 index 0000000000..0ef1ded469 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx @@ -0,0 +1,183 @@ +--- +title: Qcells Q.HOME ESS HYB-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME ESS HYB-G3 + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx new file mode 100644 index 0000000000..6f0f3c6da4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx @@ -0,0 +1,77 @@ +--- +title: RCT Power +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/rct-power.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# RCT Power + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx new file mode 100644 index 0000000000..99661015ef --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx @@ -0,0 +1,62 @@ +--- +title: Saia-Burgess Controls ALE3, AWD3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Saia-Burgess Controls ALE3, AWD3 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx new file mode 100644 index 0000000000..c5c45b2afb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -0,0 +1,78 @@ +--- +title: SAJ H1 Series Hybrid Solar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAJ H1 Series Hybrid Solar Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx new file mode 100644 index 0000000000..16b50ef9db --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: SAJ H2 Series Hybrid Solar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAJ H2 Series Hybrid Solar Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx new file mode 100644 index 0000000000..be836300ca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -0,0 +1,34 @@ +--- +title: SAJ R5 Series Solar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-r5.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAJ R5 Series Solar Inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx new file mode 100644 index 0000000000..4bc53dd146 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx @@ -0,0 +1,48 @@ +--- +title: SAX Homespeicher +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SAX Homespeicher + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx new file mode 100644 index 0000000000..437f552eae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -0,0 +1,62 @@ +--- +title: Schneider Electric iEM3xxx Modbus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/schneider-iem3000.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Schneider Electric iEM3xxx Modbus + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx new file mode 100644 index 0000000000..303f104b4f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx @@ -0,0 +1,58 @@ +--- +title: SENEC .Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senec-home.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SENEC .Home + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx new file mode 100644 index 0000000000..d26588fdbf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx @@ -0,0 +1,27 @@ +--- +title: Senergy SE 4/5/6KTL-S1/G2 Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Senergy SE 4/5/6KTL-S1/G2 Inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx new file mode 100644 index 0000000000..6f108dfc18 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx @@ -0,0 +1,57 @@ +--- +title: Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx new file mode 100644 index 0000000000..7d50fa1040 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx @@ -0,0 +1,69 @@ +--- +title: Shelly 3EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-3em.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 3EM + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx new file mode 100644 index 0000000000..4a78238e50 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx @@ -0,0 +1,54 @@ +--- +title: Shelly Pro 3 EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-pro-3em.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 3 EM + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx new file mode 100644 index 0000000000..40405f5fa0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx @@ -0,0 +1,74 @@ +--- +title: Siemens 7KT1665 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-7kt1665.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens 7KT1665 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx new file mode 100644 index 0000000000..81498bd6d3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -0,0 +1,77 @@ +--- +title: Siemens Junelight Smart Battery +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-junelight.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens Junelight Smart Battery + + + +Die Batterie muss mit dem Installer Zugang auf Loxone gestellt werden. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx new file mode 100644 index 0000000000..71a4971d6d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx @@ -0,0 +1,74 @@ +--- +title: Siemens PAC 2200 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-pac2200.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Siemens PAC 2200 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx new file mode 100644 index 0000000000..d93f9e25db --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx @@ -0,0 +1,65 @@ +--- +title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC + + + +Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen App aktivieren bevor diese Konfiguration funktional ist. Diese Option ist in der mySigen App für Kunden nicht verfügbar. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx new file mode 100644 index 0000000000..5da329a43c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx @@ -0,0 +1,77 @@ +--- +title: SMA Data Manager +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-data-manager.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Data Manager + + + +In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikation" der Schalter "Modbus Server aktivieren" eingeschaltet sein. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx new file mode 100644 index 0000000000..ff473752d3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx @@ -0,0 +1,50 @@ +--- +title: SMA Energy Meter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-energy-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Energy Meter + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx new file mode 100644 index 0000000000..d173dd90be --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx @@ -0,0 +1,47 @@ +--- +title: SMA Wechselrichter (Speedwire) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-speedwire.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Wechselrichter (Speedwire) + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx new file mode 100644 index 0000000000..c132041f4f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -0,0 +1,72 @@ +--- +title: SMA Smart Energy Hybrid-Wechselrichter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Smart Energy Hybrid-Wechselrichter + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx new file mode 100644 index 0000000000..f0c3c21c5a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx @@ -0,0 +1,40 @@ +--- +title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx new file mode 100644 index 0000000000..fa094bea4d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx @@ -0,0 +1,40 @@ +--- +title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx new file mode 100644 index 0000000000..87b810e76a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx @@ -0,0 +1,28 @@ +--- +title: SMA Sunny Home Manager 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Home Manager 2.0 + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx new file mode 100644 index 0000000000..0c5030c1dd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx @@ -0,0 +1,40 @@ +--- +title: SMA Sunny Island (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-si-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Island (Modbus) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx new file mode 100644 index 0000000000..f10b8ce114 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx @@ -0,0 +1,27 @@ +--- +title: SMA WebBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-webbox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA WebBox + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx new file mode 100644 index 0000000000..ab7199b1f5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -0,0 +1,27 @@ +--- +title: SMA Wechselrichter (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-modbus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Wechselrichter (Modbus) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx new file mode 100644 index 0000000000..6794312191 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx @@ -0,0 +1,51 @@ +--- +title: Smartfox Box, Reg, Reg extended +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Box, Reg, Reg extended + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx new file mode 100644 index 0000000000..fca340eac2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx @@ -0,0 +1,69 @@ +--- +title: Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx new file mode 100644 index 0000000000..b5712f315e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar HYD 3…6K-EP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 3…6K-EP + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx new file mode 100644 index 0000000000..ca0c1e2dc4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar HYD 5…20K-3PH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 5…20K-3PH + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx new file mode 100644 index 0000000000..65d48290d6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: SofarSolar Inverter, Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar Inverter, Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx new file mode 100644 index 0000000000..45a3e6f954 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar SOFAR 5…24KTL-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 5…24KTL-G3 + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx new file mode 100644 index 0000000000..b1bf44d201 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx @@ -0,0 +1,180 @@ +--- +title: SofarSolar SOFAR 80…136KTL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 80…136KTL + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx new file mode 100644 index 0000000000..4bf54bb1b6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx @@ -0,0 +1,64 @@ +--- +title: Solaranzeige Solaranzeige +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solaranzeige Solaranzeige + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx new file mode 100644 index 0000000000..c926501a36 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -0,0 +1,186 @@ +--- +title: SolarEdge Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarEdge Hybrid Inverter + + + +Nur ein System kann und darf zeitgleich eine Modbus TCP-Verbindung zum Wechselrichter haben! +Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "Remote" stehen. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx new file mode 100644 index 0000000000..860a5e8b12 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx @@ -0,0 +1,79 @@ +--- +title: SolarEdge Wechselrichter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarEdge Wechselrichter + + + +Nur ein System kann und darf auf den Wechselrichter zugreifen! + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx new file mode 100644 index 0000000000..a180ba1f0f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx @@ -0,0 +1,44 @@ +--- +title: Solarlog +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarlog.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarlog + + + +Wir empfehlen dieses Gerät für den Netzbezug/Einspeisewerte nur zu verwenden, wenn kein anderes Gerät diese Daten liefert. +Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall für die erwähnten Werte verwendet werden! + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx new file mode 100644 index 0000000000..e4d8cb4d73 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx @@ -0,0 +1,101 @@ +--- +title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax MAX.STORAGE / MAX.STORAGE Ultimate + + + +Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx new file mode 100644 index 0000000000..5b22bd5fb9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx @@ -0,0 +1,27 @@ +--- +title: SolarMax SolarMax SMT +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-smt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax SolarMax SMT + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx new file mode 100644 index 0000000000..bf77b4110b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -0,0 +1,27 @@ +--- +title: SolarMax SP Series Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax SP Series Inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx new file mode 100644 index 0000000000..01c8912c14 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx @@ -0,0 +1,54 @@ +--- +title: Solarwatt EnergyManager, EnergyManager Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt EnergyManager, EnergyManager Pro + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx new file mode 100644 index 0000000000..f9a2a4844d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx @@ -0,0 +1,57 @@ +--- +title: Solarwatt Manager flex +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-flex.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt Manager flex + + + +Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx new file mode 100644 index 0000000000..c54cb6fe69 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -0,0 +1,58 @@ +--- +title: Solarwatt MyReserve Matrix (LAN oder PowerGateway) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-myreserve-matrix.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt MyReserve Matrix (LAN oder PowerGateway) + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx new file mode 100644 index 0000000000..97ecf2a87b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx @@ -0,0 +1,54 @@ +--- +title: Solarwatt MyReserve +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt MyReserve + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx new file mode 100644 index 0000000000..65ec328cde --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -0,0 +1,63 @@ +--- +title: Solax Hybrid-Wechselrichter (Cloud) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-hybrid-cloud.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax Hybrid-Wechselrichter (Cloud) + + + +Der Solax Hybrid-Wechselrichter muss in der SolaxCloud angemeldet sein. + +**Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. + + + + + + Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von \`tokenID\` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen`} /> + + + + + Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von \`tokenID\` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen`} /> + + + + + Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von \`tokenID\` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen`} advanced={`meters: + - name: my_battery + type: template + template: solax-hybrid-cloud + usage: battery + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von \`tokenID\` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + capacity: 50 # Akkukapazität (kWh), optional`} /> + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx new file mode 100644 index 0000000000..82b743b6a6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx @@ -0,0 +1,183 @@ +--- +title: Solax Hybrid X1/X3 G3/G4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax Hybrid X1/X3 G3/G4 + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx new file mode 100644 index 0000000000..77896cf6d9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx @@ -0,0 +1,28 @@ +--- +title: Solax PV-Wechselrichter (Cloud) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-inverter-cloud.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax PV-Wechselrichter (Cloud) + + + +Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. + +**Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. + + + Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von \`tokenID\` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx new file mode 100644 index 0000000000..fcdc8fd750 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx @@ -0,0 +1,139 @@ +--- +title: Solinteng +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solinteng + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx new file mode 100644 index 0000000000..6e3436ba14 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx @@ -0,0 +1,74 @@ +--- +title: Sonnen comfort, eco 5, eco 6, oem 6.5 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen comfort, eco 5, eco 6, oem 6.5 + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx new file mode 100644 index 0000000000..1f1454befc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -0,0 +1,67 @@ +--- +title: Sonnen sonnenBatterie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen sonnenBatterie + + + +Für die aktive Batteriesteuerung muss über das Webinterface der sonnenBatterie (unter Software-Integration) das "JSON Write API" aktiviert und das dort generierte API-Token in der Batteriekonfiguration unter `token` eingetragen werden. +Als Betriebsart der sonnenBatterie werden die beiden Modi "Eigenverbrauch" (Standard) und "Time-of-use" unterstützt. Der Modus kann über den Parameter `defaultmode` an die Konfiguration der sonnenBatterie angepasst werden. +Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBatterie über den Parameter `maxchargepower` angepasst werden. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx new file mode 100644 index 0000000000..e8434ed24c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx @@ -0,0 +1,139 @@ +--- +title: St-ems +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# St-ems + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx new file mode 100644 index 0000000000..5f2ad9ba3c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx @@ -0,0 +1,22 @@ +--- +title: Steca coolcept fleX +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Steca coolcept fleX + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx new file mode 100644 index 0000000000..b0fe41ad46 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -0,0 +1,74 @@ +--- +title: Sungrow SG Series Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow SG Series Inverter + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx new file mode 100644 index 0000000000..e47aa97360 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -0,0 +1,159 @@ +--- +title: Sungrow SH Series Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow SH Series Hybrid Inverter + + + +Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktueller Firmware. Ältere Versionen liefern nicht alle benötigten Daten (Leistung, Ladestand). + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx new file mode 100644 index 0000000000..2131e8b38d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx @@ -0,0 +1,65 @@ +--- +title: SunSpec Batterie (Model 124) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter-control.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Batterie (Model 124) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx new file mode 100644 index 0000000000..3708ffc938 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx @@ -0,0 +1,66 @@ +--- +title: SunSpec Batterie (Model 802) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-battery-control.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Batterie (Model 802) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx new file mode 100644 index 0000000000..facaac4383 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -0,0 +1,150 @@ +--- +title: SunSpec Hybridwechselrichter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-hybrid.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Hybridwechselrichter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx new file mode 100644 index 0000000000..7fd09bc67f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: SunSpec Wechselrichter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Wechselrichter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx new file mode 100644 index 0000000000..03f3917388 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx @@ -0,0 +1,48 @@ +--- +title: SunSpec Zähler +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SunSpec Zähler + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx new file mode 100644 index 0000000000..5cc53ba7d8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -0,0 +1,179 @@ +--- +title: Sunsynk 3p hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk 3p hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx new file mode 100644 index 0000000000..218bfe23ac --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -0,0 +1,185 @@ +--- +title: Sunsynk hp3 hybrid inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk hp3 hybrid inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx new file mode 100644 index 0000000000..dde97fc54c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Sunsynk Micro inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk Micro inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx new file mode 100644 index 0000000000..cafe274f8e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: Sunsynk Storage (hybrid) inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk Storage (hybrid) inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx new file mode 100644 index 0000000000..ed155ffd63 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx @@ -0,0 +1,40 @@ +--- +title: Sunsynk String inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunsynk String inverter + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx new file mode 100644 index 0000000000..f36a39bc06 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx @@ -0,0 +1,139 @@ +--- +title: Sunway +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sunway + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx new file mode 100644 index 0000000000..d9898bfb62 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx @@ -0,0 +1,91 @@ +--- +title: Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi + + + +Um die Werte des Smartmeters für evcc korrekt auslesen zu können, muss das Lesekopf-Script so geändert werden, dass folgende JSON-Tags erzeugt werden: +- **SML** als Gruppenname der ausgelesenen Parameter +- **Total_in** für den Gesamtverbrauch in KWh (4 Nachkommastellen) +- **Total_out** für den Gesamteinspeisung in KWh mit (4 Nachkommastellen) +- **Power_curr** für den aktuellen Verbrauch bzw. die aktuelle Einspeisung (0 Nachkommastellen) + +Ein entsprechendes Lesekopf-Script sieht wie folgt aus: +``` +>D +>B +=>sensor53 r +>M 1 +// highlight-next-line ++1,3,s,16,9600,SML +// highlight-next-line +1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 +// highlight-next-line +1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 +// highlight-next-line +1,77070100100700ff@1,Verbrauch,W,Power_curr,0 +1,77070100600100ff@#,Zählernummer,,Meter_Id,0 +# +``` + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx new file mode 100644 index 0000000000..7b088d254f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx @@ -0,0 +1,70 @@ +--- +title: Tasmota Tasmota (1 Phase + SML Meter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota Tasmota (1 Phase + SML Meter) + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx new file mode 100644 index 0000000000..f065aee823 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx @@ -0,0 +1,69 @@ +--- +title: Tasmota dreiphasig +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-3p.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota dreiphasig + + + +Kanäle 1,2,3 müssen verwendet werden. + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx new file mode 100644 index 0000000000..cf620e755f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx @@ -0,0 +1,95 @@ +--- +title: Tesla Powerwall +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tesla-powerwall.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla Powerwall + + + +Um die optionale Entladesteuerung der Battery zu nutzen wird ein `refresh` Token für die Kommunikation mit der Tesla API benötigt. + +Folgende Apps ermöglichen das Erstellen des Tokens: +- [Auth app for Tesla (iOS)](https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613#?platform=iphone) +- [Tesla Tokens (Android)](https://play.google.com/store/apps/details?id=net.leveugle.teslatokens) +- [Tesla Auth (macOS, Linux)](https://github.com/adriankumpf/tesla_auth) + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx new file mode 100644 index 0000000000..774b3942f6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx @@ -0,0 +1,23 @@ +--- +title: Tibber Pulse +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tibber-pulse.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tibber Pulse + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx new file mode 100644 index 0000000000..d20a6eae89 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,22 @@ +--- +title: TP-Link H-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tplink.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link H-Series Smart Plug + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx new file mode 100644 index 0000000000..a91e2b8476 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,24 @@ +--- +title: TP-Link Tapo P-Series Smart Plug +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tapo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TP-Link Tapo P-Series Smart Plug + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx new file mode 100644 index 0000000000..b5e62d115a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx @@ -0,0 +1,24 @@ +--- +title: TQ Energy Manager EM2xx/EM3xx +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TQ Energy Manager EM2xx/EM3xx + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx new file mode 100644 index 0000000000..4e93f55530 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx @@ -0,0 +1,25 @@ +--- +title: TQ Energy Manager EM420 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em420.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TQ Energy Manager EM420 + + + + Datenendpunkt (optional) + token: ey... # Accesstoken, Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel)`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx new file mode 100644 index 0000000000..d0f77af2e2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx @@ -0,0 +1,61 @@ +--- +title: VARTA pulse, pulse neo, element +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA pulse, pulse neo, element + + + +PV nur verfügbar mit PV-Sensor + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx new file mode 100644 index 0000000000..042805c7fa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx @@ -0,0 +1,65 @@ +--- +title: Victron EM24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM24 + + + +EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx new file mode 100644 index 0000000000..282944c248 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx @@ -0,0 +1,52 @@ +--- +title: Victron EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM24_E1 + + + +EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. +Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx new file mode 100644 index 0000000000..9925778553 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx @@ -0,0 +1,74 @@ +--- +title: Victron EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM530/EM540 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx new file mode 100644 index 0000000000..af1ac6abff --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx @@ -0,0 +1,82 @@ +--- +title: Victron Energy +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/victron-energy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron Energy + + + +Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt werden soll. + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx new file mode 100644 index 0000000000..84e7a9a10d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx @@ -0,0 +1,74 @@ +--- +title: Victron ET340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron ET340 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx new file mode 100644 index 0000000000..64b046306d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -0,0 +1,24 @@ +--- +title: Volkszähler HTTP API, Import & Export +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-importexport.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkszähler HTTP API, Import & Export + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx new file mode 100644 index 0000000000..0cd45c7f81 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx @@ -0,0 +1,23 @@ +--- +title: Volkszähler HTTP API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-http.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkszähler HTTP API + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx new file mode 100644 index 0000000000..4211ea8be5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx @@ -0,0 +1,24 @@ +--- +title: Volkszähler WebSocket API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-ws.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkszähler WebSocket API + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx new file mode 100644 index 0000000000..5217bbacea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx @@ -0,0 +1,42 @@ +--- +title: vzlogger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/vzlogger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# vzlogger + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx new file mode 100644 index 0000000000..3d07cd7c87 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx @@ -0,0 +1,62 @@ +--- +title: Wago 879-30xx +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wago-879-30xx.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wago 879-30xx + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx new file mode 100644 index 0000000000..6c38588e47 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx @@ -0,0 +1,139 @@ +--- +title: Wattsonic +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wattsonic + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx new file mode 100644 index 0000000000..d61d11c12a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM110-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM110-RTU-2P + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx new file mode 100644 index 0000000000..98f2b79f3d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM111-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM111-RTU-2P + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx new file mode 100644 index 0000000000..8b70536e33 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM120-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM120-RTU-2P + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx new file mode 100644 index 0000000000..fb072ac6d6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -0,0 +1,62 @@ +--- +title: Weidmüller EM122-RTU-2P +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Weidmüller EM122-RTU-2P + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx new file mode 100644 index 0000000000..afec18634c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx @@ -0,0 +1,41 @@ +--- +title: Youless Energy Monitor +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/youless.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Youless Energy Monitor + + + +Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszähler benötigt. + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx new file mode 100644 index 0000000000..e9842c465b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx @@ -0,0 +1,126 @@ +--- +title: ZCS Azzurro Inverter, Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZCS Azzurro Inverter, Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx new file mode 100644 index 0000000000..6a9bdd72b2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx @@ -0,0 +1,53 @@ +--- +title: Zendure Hyper 2000 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/zendure.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zendure Hyper 2000 + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx new file mode 100644 index 0000000000..1253494f87 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx @@ -0,0 +1,25 @@ +--- +title: Zuidwijk SlimmeLezer(+) in Luxembourg +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) in Luxembourg + + + +Slimmelezer-Geräte in Luxemburg verwenden für verschiedene Sensoren andere Namen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx new file mode 100644 index 0000000000..3283aa9029 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx @@ -0,0 +1,25 @@ +--- +title: Zuidwijk SlimmeLezer(+) V2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) V2 + + + +Neuere Slimmelezer-Geräte verwenden eine andere Konfiguration. Probieren Sie diese Vorlage aus, wenn die andere fehlschlägt. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx new file mode 100644 index 0000000000..4853ca8019 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx @@ -0,0 +1,28 @@ +--- +title: Zuidwijk SlimmeLezer(+) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx new file mode 100644 index 0000000000..7e88f4df11 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx @@ -0,0 +1,32 @@ +--- +title: Amber Electric +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/amber.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amber Electric + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx new file mode 100644 index 0000000000..7b4a539415 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx @@ -0,0 +1,28 @@ +--- +title: Awattar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/awattar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Awattar + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx new file mode 100644 index 0000000000..27bdb1ac24 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -0,0 +1,26 @@ +--- +title: Electricity Maps Commercial API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Electricity Maps Commercial API + + + +CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx new file mode 100644 index 0000000000..b2d534c2f3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx @@ -0,0 +1,25 @@ +--- +title: Electricity Maps Free API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps-free.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Electricity Maps Free API + + + +CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx new file mode 100644 index 0000000000..4a4549035f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx @@ -0,0 +1,28 @@ +--- +title: Energinet +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energinet.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Energinet + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx new file mode 100644 index 0000000000..792500844f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx @@ -0,0 +1,31 @@ +--- +title: Enever +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/enever.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Enever + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx new file mode 100644 index 0000000000..f4ea380c15 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx @@ -0,0 +1,34 @@ +--- +title: ENTSO-E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/entsoe.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ENTSO-E + + + +Day-ahead-Preise für den europäischen Strommarkt. Siehe https://transparency.entsoe.eu für weitere Informationen. +Basis für viele dynamische Tarife. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx new file mode 100644 index 0000000000..17cbf205ee --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx @@ -0,0 +1,39 @@ +--- +title: Forecast.Solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Forecast.Solar + + + +[forecast.solar](https://forecast.solar) kann kostenlos verwendet werden. Kostenpflichtige Pläne können ebenfalls verwendet werden, indem ein API-Key angegeben wird. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx new file mode 100644 index 0000000000..7110afd6d0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx @@ -0,0 +1,31 @@ +--- +title: Fraunhofer ISE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energy-charts-api.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fraunhofer ISE + + + +Day-ahead Energiepreise (je kWh) an der Börse. Kann ohne vorherige Anmeldung auf https://api.energy-charts.info/ abgerufen werden. Nutzbar u.a. für dynamische Stromtarife, wo der Anbieter bis dato auf der Kundenschnittstelle noch kein Preis-Vorhersagen anbietet. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx new file mode 100644 index 0000000000..990de751dc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx @@ -0,0 +1,25 @@ +--- +title: Green Grid Compass +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/green-grid-compass.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Green Grid Compass + + + +Europäische CO₂-Intensitätsdaten von [greengrid-compass.eu](https://www.greengrid-compass.eu). Liefert Vorhersagen der nächsten Stunden und ist nach Registrierung kostenlos nutzbar. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx new file mode 100644 index 0000000000..1dc0ce5f31 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -0,0 +1,26 @@ +--- +title: Groupe E Vario Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/groupe-e.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Groupe E Vario Plus + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx new file mode 100644 index 0000000000..ec18edccca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx @@ -0,0 +1,25 @@ +--- +title: Grünstromindex +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/grünstromindex.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Grünstromindex + + + +Regionale Emissionsdaten von https://gruenstromindex.de + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx new file mode 100644 index 0000000000..6afb0ee71a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx @@ -0,0 +1,202 @@ +--- +title: Tariffs +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Tariffs + +
+ + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx new file mode 100644 index 0000000000..e06231d792 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx @@ -0,0 +1,22 @@ +--- +title: National Grid ESO +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ngeso.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# National Grid ESO + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx new file mode 100644 index 0000000000..2f06490646 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx @@ -0,0 +1,33 @@ +--- +title: Nordpool spot prices +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/nordpool.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nordpool spot prices + + + +Nordpool Spot Preise im Day-Ahead-Markt für alle Märkte in der Nordpool-Region. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx new file mode 100644 index 0000000000..0afe2b0f9e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx @@ -0,0 +1,25 @@ +--- +title: Octopus Energy API +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-api.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Octopus Energy API + + + +Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx new file mode 100644 index 0000000000..79b9cbd31e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx @@ -0,0 +1,23 @@ +--- +title: Octopus Energy Product Code +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-productcode.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Octopus Energy Product Code + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx new file mode 100644 index 0000000000..dc78dcb7b6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx @@ -0,0 +1,43 @@ +--- +title: Open-Meteo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/open-meteo.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Open-Meteo + + + +Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Open-Source-Wetter-API und bietet kostenlosen Zugriff für nicht-kommerzielle Nutzung. Kein API-Schlüssel erforderlich. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx new file mode 100644 index 0000000000..f7119fd630 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx @@ -0,0 +1,26 @@ +--- +title: Ostrom +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ostrom.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ostrom + + + +Erzeuge einen 'Production Client' im Ostrom-Entwicklerportal: https://developer.ostrom-api.io/ + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx new file mode 100644 index 0000000000..1b8bb51c4c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx @@ -0,0 +1,29 @@ +--- +title: PUN Orario +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/pun.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# PUN Orario + + + +Preisdaten von https://www.mercatoelettrico.org/it/. Wird oft zur Einspeisung ins Netz verwendet. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx new file mode 100644 index 0000000000..8823e718c7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -0,0 +1,26 @@ +--- +title: SmartEnergy smartCONTROL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/smartenergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SmartEnergy smartCONTROL + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx new file mode 100644 index 0000000000..93949ecbd9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx @@ -0,0 +1,33 @@ +--- +title: Solcast +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/solcast.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solcast + + + +Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting)-Account. Der kostenlose "Home User" Tarif ist für private Anwendungen oft ausreichend. Dieser Plan hat ein API-Limit von 10 Anfragen pro Tag. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx new file mode 100644 index 0000000000..3d52452ae9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx @@ -0,0 +1,30 @@ +--- +title: Spotty Energie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/spottyenergy.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Spotty Energie + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx new file mode 100644 index 0000000000..54c739edc7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx @@ -0,0 +1,33 @@ +--- +title: Tibber +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/tibber.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tibber + + + +Hol dir deinen API-Token aus dem Tibber-Entwicklerportal: https://developer.tibber.com/ + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx new file mode 100644 index 0000000000..de5c656730 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -0,0 +1,31 @@ +--- +title: Victron VRM Solar Forecast +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/victron.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron VRM Solar Forecast + + + +[vrm.victronenergy.com](https://vrm.victronenergy.com) abrufen der 2-Tage-Prognose einer Installation im VRM-Portal. Es wird ein kostenloses User Access Token benoetigt. + + +Integrationen`} advanced={`tariffs: + solar: + - type: template + template: victron + idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt + token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen + interval: 1h # optional`} /> + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx new file mode 100644 index 0000000000..320fc0b208 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx @@ -0,0 +1,39 @@ +--- +title: Aiways +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/aiways.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Aiways + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx new file mode 100644 index 0000000000..6237540664 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx @@ -0,0 +1,39 @@ +--- +title: Audi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/audi.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx new file mode 100644 index 0000000000..d6323455b9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx @@ -0,0 +1,47 @@ +--- +title: BMW +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/bmw.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# BMW + +Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx new file mode 100644 index 0000000000..5764bf8694 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx @@ -0,0 +1,44 @@ +--- +title: Citroën +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/citroen.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Citroën + +Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx new file mode 100644 index 0000000000..c7f265ebdc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx @@ -0,0 +1,41 @@ +--- +title: Dacia +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/dacia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Dacia + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx new file mode 100644 index 0000000000..f2571aff6f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx @@ -0,0 +1,44 @@ +--- +title: DS +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ds.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# DS + +Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx new file mode 100644 index 0000000000..73daebe9c0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx @@ -0,0 +1,36 @@ +--- +title: evNotify +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/evnotify.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# evNotify + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx new file mode 100644 index 0000000000..f81147c5db --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx @@ -0,0 +1,43 @@ +--- +title: Fiat +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fiat + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx new file mode 100644 index 0000000000..f3bcae5d4a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx @@ -0,0 +1,43 @@ +--- +title: Ford +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ford-connect.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ford + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx new file mode 100644 index 0000000000..a0ad8557fd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -0,0 +1,32 @@ +--- +title: Generisches Fahrzeug (ohne API) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/offline.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Generisches Fahrzeug (ohne API) + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx new file mode 100644 index 0000000000..6ac00d56e8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx @@ -0,0 +1,44 @@ +--- +title: Hyundai Bluelink +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/hyundai.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hyundai Bluelink + +Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx new file mode 100644 index 0000000000..a5c71d6392 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx @@ -0,0 +1,378 @@ +--- +title: Vehicles +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# Vehicles + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx new file mode 100644 index 0000000000..6a60b4d11b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx @@ -0,0 +1,42 @@ +--- +title: ioBroker.bmw +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ioBroker.bmw.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ioBroker.bmw + +ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx new file mode 100644 index 0000000000..bb8d6d44e4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx @@ -0,0 +1,38 @@ +--- +title: ISO15118 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/iso15118.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ISO15118 + +Nur unterstützt wenn das Fahrzeug den Ladestand (Soc) an die verbundene Wallbox übermitteln kann. +Bei Verwendung von ISO15118 mit bestimmten VW Konzernfahrzeugen, z.B. Porsche Taycan, ist zusätzliche Konfiguration +im Fahrzeug erforderlich. Dafür muss ein aktives Ortsbezogenes Ladeprofil mit der niedrigsten Minimalladung (25%) +angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht in den Schalfmodus übergeben. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx new file mode 100644 index 0000000000..2352d89ce4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx @@ -0,0 +1,43 @@ +--- +title: Jeep +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Jeep + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx new file mode 100644 index 0000000000..7a2a9f3ed1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx @@ -0,0 +1,44 @@ +--- +title: Kia Bluelink +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/kia.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kia Bluelink + +Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx new file mode 100644 index 0000000000..c70fdd75d6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx @@ -0,0 +1,46 @@ +--- +title: Mercedes-Benz +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mercedes.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mercedes-Benz + +Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https://tinyurl.com/mbapi2020helptoken. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx new file mode 100644 index 0000000000..b7b591d670 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx @@ -0,0 +1,40 @@ +--- +title: MG +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# MG + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx new file mode 100644 index 0000000000..c165dbb0c3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx @@ -0,0 +1,41 @@ +--- +title: mg2mqtt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg2mqtt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# mg2mqtt + +Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway oder https://github.com/SAIC-iSmart-API/saic-java-client) + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx new file mode 100644 index 0000000000..8342922c50 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx @@ -0,0 +1,47 @@ +--- +title: Mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mini.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mini + +Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx new file mode 100644 index 0000000000..6eb62f3832 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx @@ -0,0 +1,38 @@ +--- +title: mz2mqtt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mz2mqtt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# mz2mqtt + +myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mqtt Installation https://github.com/C64Axel/mz2mqtt. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx new file mode 100644 index 0000000000..cfacc95a13 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx @@ -0,0 +1,39 @@ +--- +title: Nissan Ariya +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan-ariya.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nissan Ariya + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx new file mode 100644 index 0000000000..f27a797239 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -0,0 +1,39 @@ +--- +title: Nissan Leaf (pre 2019) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/carwings.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nissan Leaf (pre 2019) + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx new file mode 100644 index 0000000000..f3909de688 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx @@ -0,0 +1,39 @@ +--- +title: Nissan Leaf +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nissan Leaf + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx new file mode 100644 index 0000000000..00c3367ac2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx @@ -0,0 +1,24 @@ +--- +title: NIU E-Scooter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/niu-e-scooter.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# NIU E-Scooter + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx new file mode 100644 index 0000000000..d25c710d6e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx @@ -0,0 +1,44 @@ +--- +title: Opel +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/opel.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Opel + +Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx new file mode 100644 index 0000000000..8ecc11fce8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -0,0 +1,43 @@ +--- +title: Open Vehicle Monitoring System +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ovms.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Open Vehicle Monitoring System + +Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei [Open Vehicle Monitoring System](http://api.openvehicles.com/). + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx new file mode 100644 index 0000000000..2bb8f8d990 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx @@ -0,0 +1,44 @@ +--- +title: Peugeot +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/peugeot.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peugeot + +Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx new file mode 100644 index 0000000000..03fdf17495 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx @@ -0,0 +1,39 @@ +--- +title: Polestar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/polestar.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Polestar + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx new file mode 100644 index 0000000000..9afd3a6d29 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx @@ -0,0 +1,40 @@ +--- +title: PSA Car Controller +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/flobz.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# PSA Car Controller + +Remote Control of PSA car https://github.com/flobz/psa_car_controller + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx new file mode 100644 index 0000000000..382165f4a6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx @@ -0,0 +1,40 @@ +--- +title: Renault +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/renault.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Renault + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx new file mode 100644 index 0000000000..530ca99abd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -0,0 +1,39 @@ +--- +title: Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/seat.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx new file mode 100644 index 0000000000..b5ebe28cda --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -0,0 +1,41 @@ +--- +title: Seat CupraConnect Gen4 (Born, Formentor, Tavascan) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/cupra.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Seat CupraConnect Gen4 (Born, Formentor, Tavascan) + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx new file mode 100644 index 0000000000..eab2157926 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx @@ -0,0 +1,41 @@ +--- +title: Skoda Enyaq +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/enyaq.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda Enyaq + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx new file mode 100644 index 0000000000..7675572fe4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx @@ -0,0 +1,46 @@ +--- +title: Smart EQ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smart EQ + +Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx new file mode 100644 index 0000000000..2c7e3bf190 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx @@ -0,0 +1,41 @@ +--- +title: Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smart + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx new file mode 100644 index 0000000000..d25b9d96b3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx @@ -0,0 +1,41 @@ +--- +title: Tesla BLE +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla-ble.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla BLE + +Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx new file mode 100644 index 0000000000..1044ef66d7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx @@ -0,0 +1,59 @@ +--- +title: Tesla +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla + +Tesla bietet eine offizielle, aber kostenpflichtige Fahrzeug-API an. +Für private Nutzung kannst du dir einen [Tesla Developer Account](https://developer.tesla.com/) erstellen und erhältst ein monatliches API-Guthaben von 10 €. +Das ist für die gängigen evcc-Anwendungsfälle in der Regel ausreichend. + +Die Anleitung von [myteslamate.com](https://www.myteslamate.com/tesla-api-application-registration/) erklärt den Prozess und generiert dir kostenfrei die für evcc benötigten Access- und Refresh-Token. +Mit diesem Tokenpaar und deiner im Tesla Developer Account erstellten Client ID kann evcc direkt mit der Tesla API kommunizieren. +Dein verbrauchtes Guthaben kannst du im Tesla Developer Dashboard einsehen. + +Für die Nutzung des Tesla Wall Connectors benötigst du einen öffentlichen Command-Proxy-Server. +[myteslamate.com](https://app.myteslamate.com/) stellt diesen Dienst kostenpflichtig (nutzungsbasiert) zur Verfügung. +Konfiguriere dafür bei myteslamate.com die Command-Berechtigungen und trage das Proxy-Token hier ein. +Start-, Stopp- und Stromstärken-Kommandos werden über diesen Proxy an Tesla geschickt. + +Weitere Informationen und Alternativen findest du in [unserem Blogbeitrag](https://docs.evcc.io/blog/2025/01/20/tesla-api-update). + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx new file mode 100644 index 0000000000..a5671cb553 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx @@ -0,0 +1,41 @@ +--- +title: TeslaLogger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslalogger.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TeslaLogger + +Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx new file mode 100644 index 0000000000..e427fa69d1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx @@ -0,0 +1,37 @@ +--- +title: TeslaMate +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslamate.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TeslaMate + +Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Voraussetzung ist konfigurierter MQTT Broker. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx new file mode 100644 index 0000000000..b244bde94f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx @@ -0,0 +1,39 @@ +--- +title: Tessie +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tessie.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tessie + +Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug niemals aufwecken; das Polling kann auf „always“ und interval „1M“ eingestellt werden. Wenn das Fahrzeug wach ist, sind die Daten normalerweise weniger als 15 Sekunden alt. Wenn das Fahrzeug schläft, stammen die Daten aus dem Zeitpunkt, zu dem es eingeschlafen ist. Holen Sie sich Ihr Token unter https://dash.tessie.com/settings/api + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx new file mode 100644 index 0000000000..db02a1ec73 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx @@ -0,0 +1,42 @@ +--- +title: Toyota +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/toyota.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Toyota + +Benötigt Toyota Connected Services Account. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx new file mode 100644 index 0000000000..88585fef63 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx @@ -0,0 +1,41 @@ +--- +title: Tronity +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tronity.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tronity + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx new file mode 100644 index 0000000000..79fd1d7abb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -0,0 +1,44 @@ +--- +title: Volkswagen We Connect ID +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/vw.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volkswagen We Connect ID + +e-Golf, e-Up, ID Familie + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx new file mode 100644 index 0000000000..f033629235 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx @@ -0,0 +1,52 @@ +--- +title: Volvo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo-connected.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Volvo + +Für die Nutzung mit EVCC benötigst du einen Volvo Account und einen Volvo Connected Car API Key. +Erstelle dazu auf der [Account Seite](https://developer.volvocars.com/account/) eine neue Applikation und speichere den primären VCC API Key ab. +Veröffentliche nun deine Applikation und wähle unter "Scopes" die Berechtigungen "Connected Vehicle API -> conve:vehicle-relation" und "Energy API -> (alles)" aus. +Als Redirect URL musst du die URL deiner EVCC Instanz eintragen, zb "http://evcc.local:7070/oauth/callback". +Sobald die Applikation erstellt ist, wird sie als "Publication under Review" angezeigt. Das ist nicht weiter schlimm, es funktioniert trotzdem. +Beim Anlegen des Fahrzeugs über die UI wird ein Fehler angezeigt. +Schaue im Log nach der Meldung "registering oauth provider at /oauth/login?..." und öffne den Link "http://evcc.local:7070/oauth/login?..." in einem neuen Tab. +Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Ist die Autorisierung erfolgreich, kann das Fahrzeug hinzugefügt werden. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx new file mode 100644 index 0000000000..4aa05cd54b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx @@ -0,0 +1,39 @@ +--- +title: volvo2mqtt +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo2mqtt.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# volvo2mqtt + +Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqtt-Installation https://github.com/Dielee/volvo2mqtt. + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx new file mode 100644 index 0000000000..e39ad06e4a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx @@ -0,0 +1,39 @@ +--- +title: Zero Motorcycles +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/zero.yaml +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zero Motorcycles + + + diff --git a/package-lock.json b/package-lock.json index 9ef53cc198..857e7a0ac8 100644 --- a/package-lock.json +++ b/package-lock.json @@ -23,12 +23,18 @@ "mdx-mermaid": "^2.0.0", "prism-react-renderer": "^2.3.1", "raw-loader": "^4.0.2", + "slugify": "^1.6.6", "swagger-ui-react": "^5.18.3", "url-loader": "^4.1.1" }, "devDependencies": { + "@types/js-yaml": "^4.0.9", + "@types/lodash": "^4.14.202", + "@types/node": "^20.10.0", "prettier": "^3.1.1", - "trim": ">=0.0.3" + "trim": ">=0.0.3", + "tsx": "^4.6.0", + "typescript": "^5.3.0" } }, "node_modules/@algolia/autocomplete-core": { @@ -4090,6 +4096,431 @@ "node": ">=18.0" } }, + "node_modules/@esbuild/aix-ppc64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/aix-ppc64/-/aix-ppc64-0.25.5.tgz", + "integrity": "sha512-9o3TMmpmftaCMepOdA5k/yDw8SfInyzWWTjYTFCX3kPSDJMROQTb8jg+h9Cnwnmm1vOzvxN7gIfB5V2ewpjtGA==", + "cpu": [ + "ppc64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "aix" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/android-arm": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.25.5.tgz", + "integrity": "sha512-AdJKSPeEHgi7/ZhuIPtcQKr5RQdo6OO2IL87JkianiMYMPbCtot9fxPbrMiBADOWWm3T2si9stAiVsGbTQFkbA==", + "cpu": [ + "arm" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "android" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/android-arm64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/android-arm64/-/android-arm64-0.25.5.tgz", + "integrity": "sha512-VGzGhj4lJO+TVGV1v8ntCZWJktV7SGCs3Pn1GRWI1SBFtRALoomm8k5E9Pmwg3HOAal2VDc2F9+PM/rEY6oIDg==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "android" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/android-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/android-x64/-/android-x64-0.25.5.tgz", + "integrity": "sha512-D2GyJT1kjvO//drbRT3Hib9XPwQeWd9vZoBJn+bu/lVsOZ13cqNdDeqIF/xQ5/VmWvMduP6AmXvylO/PIc2isw==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "android" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/darwin-arm64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/darwin-arm64/-/darwin-arm64-0.25.5.tgz", + "integrity": "sha512-GtaBgammVvdF7aPIgH2jxMDdivezgFu6iKpmT+48+F8Hhg5J/sfnDieg0aeG/jfSvkYQU2/pceFPDKlqZzwnfQ==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "darwin" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/darwin-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/darwin-x64/-/darwin-x64-0.25.5.tgz", + "integrity": "sha512-1iT4FVL0dJ76/q1wd7XDsXrSW+oLoquptvh4CLR4kITDtqi2e/xwXwdCVH8hVHU43wgJdsq7Gxuzcs6Iq/7bxQ==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "darwin" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/freebsd-arm64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/freebsd-arm64/-/freebsd-arm64-0.25.5.tgz", + "integrity": "sha512-nk4tGP3JThz4La38Uy/gzyXtpkPW8zSAmoUhK9xKKXdBCzKODMc2adkB2+8om9BDYugz+uGV7sLmpTYzvmz6Sw==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "freebsd" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/freebsd-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/freebsd-x64/-/freebsd-x64-0.25.5.tgz", + "integrity": "sha512-PrikaNjiXdR2laW6OIjlbeuCPrPaAl0IwPIaRv+SMV8CiM8i2LqVUHFC1+8eORgWyY7yhQY+2U2fA55mBzReaw==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "freebsd" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-arm": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-arm/-/linux-arm-0.25.5.tgz", + "integrity": "sha512-cPzojwW2okgh7ZlRpcBEtsX7WBuqbLrNXqLU89GxWbNt6uIg78ET82qifUy3W6OVww6ZWobWub5oqZOVtwolfw==", + "cpu": [ + "arm" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-arm64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-arm64/-/linux-arm64-0.25.5.tgz", + "integrity": "sha512-Z9kfb1v6ZlGbWj8EJk9T6czVEjjq2ntSYLY2cw6pAZl4oKtfgQuS4HOq41M/BcoLPzrUbNd+R4BXFyH//nHxVg==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-ia32": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-ia32/-/linux-ia32-0.25.5.tgz", + "integrity": "sha512-sQ7l00M8bSv36GLV95BVAdhJ2QsIbCuCjh/uYrWiMQSUuV+LpXwIqhgJDcvMTj+VsQmqAHL2yYaasENvJ7CDKA==", + "cpu": [ + "ia32" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-loong64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-loong64/-/linux-loong64-0.25.5.tgz", + "integrity": "sha512-0ur7ae16hDUC4OL5iEnDb0tZHDxYmuQyhKhsPBV8f99f6Z9KQM02g33f93rNH5A30agMS46u2HP6qTdEt6Q1kg==", + "cpu": [ + "loong64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-mips64el": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-mips64el/-/linux-mips64el-0.25.5.tgz", + "integrity": "sha512-kB/66P1OsHO5zLz0i6X0RxlQ+3cu0mkxS3TKFvkb5lin6uwZ/ttOkP3Z8lfR9mJOBk14ZwZ9182SIIWFGNmqmg==", + "cpu": [ + "mips64el" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-ppc64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-ppc64/-/linux-ppc64-0.25.5.tgz", + "integrity": "sha512-UZCmJ7r9X2fe2D6jBmkLBMQetXPXIsZjQJCjgwpVDz+YMcS6oFR27alkgGv3Oqkv07bxdvw7fyB71/olceJhkQ==", + "cpu": [ + "ppc64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-riscv64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-riscv64/-/linux-riscv64-0.25.5.tgz", + "integrity": "sha512-kTxwu4mLyeOlsVIFPfQo+fQJAV9mh24xL+y+Bm6ej067sYANjyEw1dNHmvoqxJUCMnkBdKpvOn0Ahql6+4VyeA==", + "cpu": [ + "riscv64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-s390x": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-s390x/-/linux-s390x-0.25.5.tgz", + "integrity": "sha512-K2dSKTKfmdh78uJ3NcWFiqyRrimfdinS5ErLSn3vluHNeHVnBAFWC8a4X5N+7FgVE1EjXS1QDZbpqZBjfrqMTQ==", + "cpu": [ + "s390x" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/linux-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.25.5.tgz", + "integrity": "sha512-uhj8N2obKTE6pSZ+aMUbqq+1nXxNjZIIjCjGLfsWvVpy7gKCOL6rsY1MhRh9zLtUtAI7vpgLMK6DxjO8Qm9lJw==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/netbsd-arm64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/netbsd-arm64/-/netbsd-arm64-0.25.5.tgz", + "integrity": "sha512-pwHtMP9viAy1oHPvgxtOv+OkduK5ugofNTVDilIzBLpoWAM16r7b/mxBvfpuQDpRQFMfuVr5aLcn4yveGvBZvw==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "netbsd" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/netbsd-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/netbsd-x64/-/netbsd-x64-0.25.5.tgz", + "integrity": "sha512-WOb5fKrvVTRMfWFNCroYWWklbnXH0Q5rZppjq0vQIdlsQKuw6mdSihwSo4RV/YdQ5UCKKvBy7/0ZZYLBZKIbwQ==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "netbsd" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/openbsd-arm64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/openbsd-arm64/-/openbsd-arm64-0.25.5.tgz", + "integrity": "sha512-7A208+uQKgTxHd0G0uqZO8UjK2R0DDb4fDmERtARjSHWxqMTye4Erz4zZafx7Di9Cv+lNHYuncAkiGFySoD+Mw==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "openbsd" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/openbsd-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/openbsd-x64/-/openbsd-x64-0.25.5.tgz", + "integrity": "sha512-G4hE405ErTWraiZ8UiSoesH8DaCsMm0Cay4fsFWOOUcz8b8rC6uCvnagr+gnioEjWn0wC+o1/TAHt+It+MpIMg==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "openbsd" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/sunos-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/sunos-x64/-/sunos-x64-0.25.5.tgz", + "integrity": "sha512-l+azKShMy7FxzY0Rj4RCt5VD/q8mG/e+mDivgspo+yL8zW7qEwctQ6YqKX34DTEleFAvCIUviCFX1SDZRSyMQA==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "sunos" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/win32-arm64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/win32-arm64/-/win32-arm64-0.25.5.tgz", + "integrity": "sha512-O2S7SNZzdcFG7eFKgvwUEZ2VG9D/sn/eIiz8XRZ1Q/DO5a3s76Xv0mdBzVM5j5R639lXQmPmSo0iRpHqUUrsxw==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "win32" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/win32-ia32": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/win32-ia32/-/win32-ia32-0.25.5.tgz", + "integrity": "sha512-onOJ02pqs9h1iMJ1PQphR+VZv8qBMQ77Klcsqv9CNW2w6yLqoURLcgERAIurY6QE63bbLuqgP9ATqajFLK5AMQ==", + "cpu": [ + "ia32" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "win32" + ], + "engines": { + "node": ">=18" + } + }, + "node_modules/@esbuild/win32-x64": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.25.5.tgz", + "integrity": "sha512-TXv6YnJ8ZMVdX+SXWVBo/0p8LTcrUYngpWjvm91TMjjBQii7Oz11Lw5lbDV5Y0TzuhSJHwiH4hEtC1I42mMS0g==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "win32" + ], + "engines": { + "node": ">=18" + } + }, "node_modules/@hapi/hoek": { "version": "9.3.0", "resolved": "https://registry.npmjs.org/@hapi/hoek/-/hoek-9.3.0.tgz", @@ -6457,12 +6888,26 @@ "@types/istanbul-lib-report": "*" } }, + "node_modules/@types/js-yaml": { + "version": "4.0.9", + "resolved": "https://registry.npmjs.org/@types/js-yaml/-/js-yaml-4.0.9.tgz", + "integrity": "sha512-k4MGaQl5TGo/iipqb2UDG2UwjXziSWkh0uysQelTlJpX1qGlpUZYm8PnO4DxG1qBomtJUdYJ6qR6xdIah10JLg==", + "dev": true, + "license": "MIT" + }, "node_modules/@types/json-schema": { "version": "7.0.15", "resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.15.tgz", "integrity": "sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==", "license": "MIT" }, + "node_modules/@types/lodash": { + "version": "4.17.17", + "resolved": "https://registry.npmjs.org/@types/lodash/-/lodash-4.17.17.tgz", + "integrity": "sha512-RRVJ+J3J+WmyOTqnz3PiBLA501eKwXl2noseKOrNo/6+XEHjTAxO4xHvxQB6QuNm+s4WRbn6rSiap8+EA+ykFQ==", + "dev": true, + "license": "MIT" + }, "node_modules/@types/mdast": { "version": "4.0.4", "resolved": "https://registry.npmjs.org/@types/mdast/-/mdast-4.0.4.tgz", @@ -6491,12 +6936,12 @@ "license": "MIT" }, "node_modules/@types/node": { - "version": "22.13.1", - "resolved": "https://registry.npmjs.org/@types/node/-/node-22.13.1.tgz", - "integrity": "sha512-jK8uzQlrvXqEU91UxiK5J7pKHyzgnI1Qnl0QDHIgVGuolJhRb9EEl28Cj9b3rGR8B2lhFCtvIm5os8lFnO/1Ew==", + "version": "20.17.57", + "resolved": "https://registry.npmjs.org/@types/node/-/node-20.17.57.tgz", + "integrity": "sha512-f3T4y6VU4fVQDKVqJV4Uppy8c1p/sVvS3peyqxyWnzkqXFJLRU7Y1Bl7rMS1Qe9z0v4M6McY0Fp9yBsgHJUsWQ==", "license": "MIT", "dependencies": { - "undici-types": "~6.20.0" + "undici-types": "~6.19.2" } }, "node_modules/@types/node-forge": { @@ -10364,6 +10809,47 @@ "url": "https://opencollective.com/unified" } }, + "node_modules/esbuild": { + "version": "0.25.5", + "resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.25.5.tgz", + "integrity": "sha512-P8OtKZRv/5J5hhz0cUAdu/cLuPIKXpQl1R9pZtvmHWQvrAUVd0UNIPT4IB4W3rNOqVO0rlqHmCIbSwxh/c9yUQ==", + "dev": true, + "hasInstallScript": true, + "license": "MIT", + "bin": { + "esbuild": "bin/esbuild" + }, + "engines": { + "node": ">=18" + }, + "optionalDependencies": { + "@esbuild/aix-ppc64": "0.25.5", + "@esbuild/android-arm": "0.25.5", + "@esbuild/android-arm64": "0.25.5", + "@esbuild/android-x64": "0.25.5", + "@esbuild/darwin-arm64": "0.25.5", + "@esbuild/darwin-x64": "0.25.5", + "@esbuild/freebsd-arm64": "0.25.5", + "@esbuild/freebsd-x64": "0.25.5", + "@esbuild/linux-arm": "0.25.5", + "@esbuild/linux-arm64": "0.25.5", + "@esbuild/linux-ia32": "0.25.5", + "@esbuild/linux-loong64": "0.25.5", + "@esbuild/linux-mips64el": "0.25.5", + "@esbuild/linux-ppc64": "0.25.5", + "@esbuild/linux-riscv64": "0.25.5", + "@esbuild/linux-s390x": "0.25.5", + "@esbuild/linux-x64": "0.25.5", + "@esbuild/netbsd-arm64": "0.25.5", + "@esbuild/netbsd-x64": "0.25.5", + "@esbuild/openbsd-arm64": "0.25.5", + "@esbuild/openbsd-x64": "0.25.5", + "@esbuild/sunos-x64": "0.25.5", + "@esbuild/win32-arm64": "0.25.5", + "@esbuild/win32-ia32": "0.25.5", + "@esbuild/win32-x64": "0.25.5" + } + }, "node_modules/escalade": { "version": "3.2.0", "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.2.0.tgz", @@ -11461,6 +11947,19 @@ "url": "https://github.com/sponsors/sindresorhus" } }, + "node_modules/get-tsconfig": { + "version": "4.10.1", + "resolved": "https://registry.npmjs.org/get-tsconfig/-/get-tsconfig-4.10.1.tgz", + "integrity": "sha512-auHyJ4AgMz7vgS8Hp3N6HXSmlMdUyhSUrfBF16w153rxtLIEOE+HGqaBppczZvnHLqQJfiHotCYpNhl0lUROFQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "resolve-pkg-maps": "^1.0.0" + }, + "funding": { + "url": "https://github.com/privatenumber/get-tsconfig?sponsor=1" + } + }, "node_modules/get-uri": { "version": "6.0.4", "resolved": "https://registry.npmjs.org/get-uri/-/get-uri-6.0.4.tgz", @@ -22501,6 +23000,16 @@ "integrity": "sha512-C7rARubxI8bXFNB/hqcp/4iUeIXJhJZvFPFPiSPRnhU5UPxzMFIl+2E6yY6c4k9giDJAhtV+enfA+G89N6Csng==", "license": "MIT" }, + "node_modules/resolve-pkg-maps": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/resolve-pkg-maps/-/resolve-pkg-maps-1.0.0.tgz", + "integrity": "sha512-seS2Tj26TBVOC2NIc2rOe2y2ZO7efxITtLZcGSOnHHNOQ7CkiUBfw0Iw2ck6xkIhPwLhKNLS8BO+hEpngQlqzw==", + "dev": true, + "license": "MIT", + "funding": { + "url": "https://github.com/privatenumber/resolve-pkg-maps?sponsor=1" + } + }, "node_modules/responselike": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/responselike/-/responselike-3.0.0.tgz", @@ -23233,6 +23742,15 @@ "node": ">=8" } }, + "node_modules/slugify": { + "version": "1.6.6", + "resolved": "https://registry.npmjs.org/slugify/-/slugify-1.6.6.tgz", + "integrity": "sha512-h+z7HKHYXj6wJU+AnS/+IH8Uh9fdcX1Lrhg1/VMdf9PwoBQXFcXiAdsy2tSK0P6gKwJLXp02r90ahUCqHk9rrw==", + "license": "MIT", + "engines": { + "node": ">=8.0.0" + } + }, "node_modules/smart-buffer": { "version": "4.2.0", "resolved": "https://registry.npmjs.org/smart-buffer/-/smart-buffer-4.2.0.tgz", @@ -24050,6 +24568,26 @@ "integrity": "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==", "license": "0BSD" }, + "node_modules/tsx": { + "version": "4.19.4", + "resolved": "https://registry.npmjs.org/tsx/-/tsx-4.19.4.tgz", + "integrity": "sha512-gK5GVzDkJK1SI1zwHf32Mqxf2tSJkNx+eYcNly5+nHvWqXUJYUkWBQtKauoESz3ymezAI++ZwT855x5p5eop+Q==", + "dev": true, + "license": "MIT", + "dependencies": { + "esbuild": "~0.25.0", + "get-tsconfig": "^4.7.5" + }, + "bin": { + "tsx": "dist/cli.mjs" + }, + "engines": { + "node": ">=18.0.0" + }, + "optionalDependencies": { + "fsevents": "~2.3.3" + } + }, "node_modules/type-fest": { "version": "2.19.0", "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-2.19.0.tgz", @@ -24119,7 +24657,6 @@ "resolved": "https://registry.npmjs.org/typescript/-/typescript-5.7.3.tgz", "integrity": "sha512-84MVSjMEHP+FQRPy3pX9sTVV/INIex71s9TL2Gm5FG/WG1SqXeKyZ0k7/blY/4FdOzI12CBy1vGc4og/eus0fw==", "license": "Apache-2.0", - "peer": true, "bin": { "tsc": "bin/tsc", "tsserver": "bin/tsserver" @@ -24153,9 +24690,9 @@ } }, "node_modules/undici-types": { - "version": "6.20.0", - "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-6.20.0.tgz", - "integrity": "sha512-Ny6QZ2Nju20vw1SRHe3d9jVu6gJ+4e3+MMpqu7pqE5HT6WsTSlce++GQmK5UXS8mzV8DSYHrQH+Xrf2jVcuKNg==", + "version": "6.19.8", + "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-6.19.8.tgz", + "integrity": "sha512-ve2KP6f/JnbPBFyobGHuerC9g1FYGn/F8n1LWTwNxCEzd6IfqTwUQcNXgEtmmQ6DlRrC1hrSrBnCZPokRrDHjw==", "license": "MIT" }, "node_modules/unicode-canonical-property-names-ecmascript": { diff --git a/package.json b/package.json index c7a60cb7e5..c60f20737c 100644 --- a/package.json +++ b/package.json @@ -4,11 +4,13 @@ "private": true, "scripts": { "generate": "node src/generateFromTemplate.js && node src/copySwaggerStyles.js", + "generate:next": "npx tsx src/generateDevicesNext.ts", + "generate:all": "npm run generate && npm run generate:next", "docusaurus": "docusaurus", "start": "npm run generate && docusaurus start", "restart": "npm run clear && npm run start", "start:en": "npm run start -- --locale en", - "build": "npm run generate && docusaurus build", + "build": "npm run generate:all && docusaurus build", "swizzle": "docusaurus swizzle", "deploy": "docusaurus deploy", "clear": "docusaurus clear", @@ -34,6 +36,7 @@ "mdx-mermaid": "^2.0.0", "prism-react-renderer": "^2.3.1", "raw-loader": "^4.0.2", + "slugify": "^1.6.6", "swagger-ui-react": "^5.18.3", "url-loader": "^4.1.1" }, @@ -50,7 +53,12 @@ ] }, "devDependencies": { + "@types/js-yaml": "^4.0.9", + "@types/lodash": "^4.14.202", + "@types/node": "^20.10.0", "prettier": "^3.1.1", - "trim": ">=0.0.3" + "trim": ">=0.0.3", + "tsx": "^4.6.0", + "typescript": "^5.3.0" } } diff --git a/sidebars.js b/sidebars.js index 9df9b834e2..bb40178b77 100644 --- a/sidebars.js +++ b/sidebars.js @@ -12,15 +12,4 @@ module.exports = { // By default, Docusaurus generates a sidebar from the docs folder structure tutorialSidebar: [{ type: "autogenerated", dirName: "." }], - - // But you can create a sidebar manually - /* - tutorialSidebar: [ - { - type: 'category', - label: 'Tutorial', - items: ['hello'], - }, - ], - */ }; diff --git a/src/components/DeviceCard.module.css b/src/components/DeviceCard.module.css new file mode 100644 index 0000000000..91df80ef21 --- /dev/null +++ b/src/components/DeviceCard.module.css @@ -0,0 +1,130 @@ +.deviceCard { + background: var(--ifm-card-background-color); + border: 1px solid var(--ifm-color-emphasis-200); + border-radius: 12px; + transition: all 0.2s ease-in-out; + cursor: pointer; + overflow: hidden; + height: 100%; + display: flex; + flex-direction: column; + box-shadow: 0 2px 8px rgba(0, 0, 0, 0.1); +} + +.deviceCard:hover { + transform: translateY(-4px); + box-shadow: 0 8px 25px rgba(0, 0, 0, 0.15); + border-color: var(--ifm-color-primary); +} + +.deviceCard:focus-visible { + outline: 2px solid var(--ifm-color-primary); + outline-offset: 2px; +} + +.thumbnailContainer { + position: relative; + height: 200px; + background: var(--ifm-color-emphasis-100); + display: flex; + align-items: center; + justify-content: center; + overflow: hidden; +} + +.thumbnail { + width: 100%; + height: 100%; + object-fit: cover; + transition: transform 0.2s ease-in-out; +} + +.deviceCard:hover .thumbnail { + transform: scale(1.05); +} + +.content { + padding: 16px; + flex: 1; + display: flex; + flex-direction: column; + gap: 8px; +} + +.title { + font-size: 1.1rem; + font-weight: 500; + color: var(--ifm-color-emphasis-800); + line-height: 1.3; +} + +.capabilities { + display: flex; + flex-wrap: wrap; + gap: 6px; + margin-top: auto; +} + +.capabilityTag { + background: var(--ifm-color-emphasis-200); + color: var(--ifm-color-emphasis-700); + padding: 2px 8px; + border-radius: 12px; + font-size: 0.75rem; + font-weight: 500; +} + +.moreCapabilities { + color: var(--ifm-color-emphasis-600); + font-size: 0.75rem; + font-weight: 500; + font-style: italic; +} + +.footer { + padding: 0 16px 16px 16px; + margin-top: auto; +} + +.viewDetails { + display: inline-flex; + align-items: center; + gap: 4px; + color: var(--ifm-color-primary); + text-decoration: none; + font-weight: 500; + font-size: 0.875rem; + transition: color 0.2s ease-in-out; +} + +.viewDetails:hover { + color: var(--ifm-color-primary-dark); + text-decoration: none; +} + +/* Global device grid styles */ +:global(.device-grid) { + display: grid; + grid-template-columns: repeat(auto-fill, minmax(300px, 1fr)); + gap: 24px; + margin: 32px 0; +} + +@media (max-width: 768px) { + :global(.device-grid) { + grid-template-columns: 1fr; + gap: 16px; + } + + .thumbnailContainer { + height: 160px; + } + + .content { + padding: 12px; + } + + .footer { + padding: 0 12px 12px 12px; + } +} diff --git a/src/components/DeviceCard.tsx b/src/components/DeviceCard.tsx new file mode 100644 index 0000000000..4d6fbbc933 --- /dev/null +++ b/src/components/DeviceCard.tsx @@ -0,0 +1,94 @@ +import React from "react"; +import Link from "@docusaurus/Link"; +import styles from "./DeviceCard.module.css"; + +interface DeviceCardProps { + brand: string; + description: string; + thumbnail: string; + capabilities?: string[]; + requirements?: string[]; + href: string; +} + +const DeviceCard: React.FC = ({ + brand, + description, + thumbnail, + capabilities = [], + requirements = [], + href, +}) => { + const handleKeyDown = (event: React.KeyboardEvent) => { + if (event.key === "Enter" || event.key === " ") { + event.preventDefault(); + // The Link component will handle the navigation + (event.currentTarget as HTMLAnchorElement).click(); + } + }; + + // Use only capabilities since all features are now in capabilities + const allFeatures = capabilities; + + // Simple string mapping for feature translations + const featureTranslations: Record = { + "1p3p": "1P3P", + rfid: "RFID", + mA: "mA Regelung", + iso151182: "ISO 15118", + sponsorfree: "ohne Sponsoring", + sponsorship: "Sponsorship", + "battery-control": "aktive Batteriesteuerung", + eebus: "EEBUS", + skiptest: "Skip Test", + }; + + return ( + +
+ {`${brand} { + // Fallback to a placeholder image + (e.target as HTMLImageElement).src = "/img/devices/placeholder.svg"; + }} + /> +
+ +
+ {brand &&
{brand}
} + {description &&
{description}
} + + {allFeatures.length > 0 && ( +
+ {allFeatures.slice(0, 3).map((feature, index) => ( + + {featureTranslations[feature] || feature} + + ))} + {allFeatures.length > 3 && ( + + +{allFeatures.length - 3} more + + )} +
+ )} +
+ +
+ View Details → +
+ + ); +}; + +export default DeviceCard; diff --git a/src/generateDevicesNext.ts b/src/generateDevicesNext.ts new file mode 100644 index 0000000000..b7b84c8d14 --- /dev/null +++ b/src/generateDevicesNext.ts @@ -0,0 +1,467 @@ +import * as fs from "fs"; +import * as path from "path"; +import * as yaml from "js-yaml"; +import * as countries from "i18n-iso-countries"; +import slugify from "slugify"; + +// Register locale data +countries.registerLocale(require("i18n-iso-countries/langs/en.json")); +countries.registerLocale(require("i18n-iso-countries/langs/de.json")); + +interface ProductData { + product: { + brand: string; + description?: string; + group?: string; + }; + capabilities?: string[]; + requirements?: string[]; + countries?: string[]; + description?: string; + render: Array<{ + usage?: string; + default: string; + advanced?: string; + }>; +} + +interface DeviceCard { + id: string; + brand: string; + description: string; + thumbnail: string; + capabilities: string[]; + requirements: string[]; + countries: string[]; + slug: string; +} + +const DEVICE_TYPES = ["vehicle", "charger", "meter", "tariff"] as const; +const LANGUAGES = ["en", "de"] as const; + +const TARIFF_GROUPS: Record = { + "Dynamic electricity price": "price", + "Dynamischer Strompreis": "price", + "CO₂ Vorhersage": "co2", + "CO₂ forecast": "co2", + "PV Vorhersage": "solar", + "PV forecast": "solar", +}; + +const CODE_PREAMBLES: Record = { + vehicle: "vehicles:\n - name: my_car", + charger: "chargers:\n - name: my_charger", + meter: "meters:\n - name: my_meter", + grid: "meters:\n - name: my_grid", + pv: "meters:\n - name: my_pv", + battery: "meters:\n - name: my_battery", + charge: "meters:\n - name: my_charger", + aux: "meters:\n - name: my_aux", + price: "tariffs:\n grid:", + co2: "tariffs:\n co2:", + solar: "tariffs:\n solar:", +}; + +const TRANSLATIONS_DE: Record = { + "tab.grid": "Netz", + "tab.pv": "PV", + "tab.battery": "Batterie", + "tab.charge": "Wallbox", + "tab.aux": "AUX", + global: "Global", +}; + +const TRANSLATIONS_EN: Record = { + "tab.grid": "Grid", + "tab.pv": "PV", + "tab.battery": "Battery", + "tab.charge": "Wallbox", + "tab.aux": "AUX", + global: "Global", +}; + +interface TemplateWithFilename extends ProductData { + _filename: string; +} + +const makeTranslate = + (language: string) => + (key: string): string => { + const translations = language === "de" ? TRANSLATIONS_DE : TRANSLATIONS_EN; + + if (translations[key]) { + return translations[key]; + } + + const countryName = countries.getName(key, language); + if (countryName) { + return countryName; + } + + return key; + }; + +const readTemplates = (templatePath: string): TemplateWithFilename[] => { + if (!fs.existsSync(templatePath)) { + return []; + } + + const files = fs.readdirSync(templatePath); + return files + .filter((file) => file.endsWith(".yaml")) + .map((file) => { + const template = yaml.load( + fs.readFileSync(path.join(templatePath, file), "utf8"), + ) as ProductData; + return { + ...template, + _filename: file, + }; + }); +}; + +const extractTemplateNameFromFilename = (filename: string): string => { + // Extract template name from filename like "tesla_0.yaml" -> "tesla" + return filename.replace(/_\d+\.yaml$/, "").replace(/\.yaml$/, ""); +}; + +const normalizeForComparison = (text: string): string => { + return text + .toLowerCase() + .normalize("NFD") // Decompose accented characters + .replace(/[\u0300-\u036f]/g, "") // Remove diacritics + .replace(/[^a-z0-9]/g, ""); // Remove all non-alphanumeric characters +}; + +const createSlug = ( + brand: string, + description: string, + templateName: string, +): string => { + const parts: string[] = []; + + // Add brand if it exists and is not empty + if (brand && brand.trim()) { + parts.push(brand); + } + + // Add description if it exists AND is different from brand (normalized comparison) + if (description && description.trim()) { + const normalizedBrand = normalizeForComparison(brand); + const normalizedDescription = normalizeForComparison(description); + + if (normalizedDescription !== normalizedBrand) { + parts.push(description); + } + } + + // If no parts, we have a problem - skip this template + if (parts.length === 0) { + console.warn( + `No brand or description found for template: ${templateName} - skipping`, + ); + return ""; + } + + return slugify(parts.join(" "), { + lower: true, + strict: true, + remove: /[*+~.()'"!:@]/g, + }); +}; + +const getEnglishDescription = ( + template: TemplateWithFilename, + deviceType: string, +): string => { + // Try to find the corresponding English template + const englishTemplatePath = `./templates/release/en/${deviceType}`; + try { + const englishTemplates = readTemplates(englishTemplatePath); + const matchingTemplate = englishTemplates.find( + (t) => t._filename === template._filename, + ); + + if (matchingTemplate && matchingTemplate.product.description) { + return matchingTemplate.product.description; + } + } catch (e) { + // If we can't find English template, fall back to current description + } + + return template.product.description || ""; +}; + +const indentCode = (code: string, list = false): string => { + let result = code.replace(/`/g, "\\`"); + + if (list) { + result = result.replace(/^/, " - "); + return result.replace(/\n/gm, "\n "); + } else { + result = result.replace(/^/gm, " "); + } + + return result; +}; + +const generateDeviceCard = ( + data: TemplateWithFilename, + deviceType: string, + language: string, +): DeviceCard | null => { + const brand = data.product.brand || ""; + // Always use English description for slug consistency + const englishDescription = getEnglishDescription(data, deviceType); + const description = data.product.description || ""; + const templateName = extractTemplateNameFromFilename(data._filename); + const slug = createSlug(brand, englishDescription, templateName); + + // Skip if no valid slug could be created + if (!slug) { + return null; + } + + return { + id: `${brand}-${description}`.replace(/\s+/g, "-").toLowerCase(), + brand, + description, + thumbnail: `/img/devices/${deviceType}/${slug}.jpg`, + capabilities: data.capabilities || [], + requirements: data.requirements || [], + countries: data.countries || [], + slug, + }; +}; + +const generateOverviewPage = ( + cards: DeviceCard[], + deviceType: string, + language: string, +): string => { + const title = deviceType.charAt(0).toUpperCase() + deviceType.slice(1) + "s"; + + return `--- +title: ${title} +--- + +import DeviceCard from '@site/src/components/DeviceCard'; + +# ${title} + +
+${cards + .sort((a, b) => + `${a.brand} ${a.description}`.localeCompare(`${b.brand} ${b.description}`), + ) + .map((card) => { + const allCapabilities = [...card.capabilities]; + const allRequirements = [...card.requirements]; + + // Combine all features like in the existing implementation + const features = [...allCapabilities, ...allRequirements].filter( + (f) => f !== "skiptest", + ); + + // Apply same logic as existing implementation for chargers + if (deviceType === "charger") { + const sponsorshipIndex = features.indexOf("sponsorship"); + if (sponsorshipIndex > -1) { + features.splice(sponsorshipIndex, 1); + } else { + features.push("sponsorfree"); + } + } + + // Remove eebus like in existing implementation + const eebusIndex = features.indexOf("eebus"); + if (eebusIndex > -1) { + features.splice(eebusIndex, 1); + } + + return ` `"${f}"`).join(", ")}]} + requirements={[]} + href="/docs/devices-next/${deviceType}s/${card.slug}" + />`; + }) + .join("\n")} +
+`; +}; + +const generateDetailPage = ( + data: TemplateWithFilename, + deviceType: string, + language: string, +): string => { + const translate = makeTranslate(language); + const brand = data.product.brand || ""; + const description = data.product.description || ""; + const longDescription = data.description || ""; + + const codeBlocks = data.render.map((render) => { + let preamble = render.usage || deviceType; + let list = false; + + if (deviceType === "tariff") { + preamble = TARIFF_GROUPS[data.product.group || ""] || deviceType; + if (preamble === "solar") { + list = true; + } + } + + const code = `${CODE_PREAMBLES[preamble] || CODE_PREAMBLES[deviceType]}\n${indentCode(render.default, list).trimEnd()}`; + const advanced = + render.advanced && render.advanced !== render.default + ? `${CODE_PREAMBLES[preamble] || CODE_PREAMBLES[deviceType]}\n${indentCode(render.advanced, list).trimEnd()}` + : null; + + return { + usage: render.usage, + code: ``, + }; + }); + + let codeSection = ""; + if (codeBlocks.length === 1) { + codeSection = codeBlocks[0].code; + } else { + codeSection = ` +${codeBlocks + .map( + ( + block, + i, + ) => ` + +${block.code} + +`, + ) + .join("\n")} +`; + } + + const features = [ + ...(data.capabilities || []), + ...(data.requirements || []), + // Only add countries/regions for tariffs + ...(deviceType === "tariff" + ? (data.countries || ["global"]).map(translate) + : []), + ].filter((f) => f !== "skiptest"); + + const deviceFeatures = ["charger", "meter", "tariff"].includes(deviceType) + ? `\n\n` + : ""; + + const sponsor = data.requirements?.includes("sponsorship") + ? `\n\n` + : ""; + + // Create title from available parts + const titleParts = [brand, description].filter((part) => part.trim()); + const title = titleParts.join(" ") || "Device"; + + // Generate custom edit URL pointing to the original template + const cleanFilename = data._filename.replace(/_\d+\.yaml$/, ".yaml"); + const editUrl = `https://github.com/evcc-io/evcc/blob/master/templates/definition/${deviceType}/${cleanFilename}`; + + return `--- +title: ${title} +custom_edit_url: ${editUrl} +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ${title} + +${deviceFeatures}${longDescription ? longDescription + "\n\n" : ""}${codeSection} + +${sponsor}`; +}; + +const cleanDeviceFolders = () => { + const foldersToClean = [ + "./docs/devices-next", + "./i18n/de/docusaurus-plugin-content-docs/current/devices-next", + ]; + + foldersToClean.forEach((folder) => { + if (fs.existsSync(folder)) { + fs.rmSync(folder, { recursive: true, force: true }); + console.log(`Cleaned ${folder}`); + } + }); +}; + +const generateDevicePages = () => { + // Clean existing device folders first + cleanDeviceFolders(); + + DEVICE_TYPES.forEach((deviceType) => { + LANGUAGES.forEach((language) => { + console.log(`Generating ${deviceType} pages for ${language}...`); + + // Read templates + const templatePath = `./templates/release/${language}/${deviceType}`; + const templates = readTemplates(templatePath); + + if (templates.length === 0) { + console.log(`No templates found for ${deviceType} in ${language}`); + return; + } + + // Generate device cards, filtering out null values + const cards = templates + .map((template) => generateDeviceCard(template, deviceType, language)) + .filter((card): card is DeviceCard => card !== null); + + // Create output directories + const baseDir = + language === "en" + ? "./docs/devices-next" + : `./i18n/${language}/docusaurus-plugin-content-docs/current/devices-next`; + + const deviceDir = path.join(baseDir, `${deviceType}s`); + + fs.mkdirSync(deviceDir, { recursive: true }); + + // Generate overview page as index.mdx inside the device folder + const overviewContent = generateOverviewPage(cards, deviceType, language); + fs.writeFileSync(path.join(deviceDir, "index.mdx"), overviewContent); + + // Generate detail pages in the same folder as the overview + templates.forEach((template) => { + const card = generateDeviceCard(template, deviceType, language); + if (card) { + // Only generate if card is valid + const detailContent = generateDetailPage( + template, + deviceType, + language, + ); + fs.writeFileSync( + path.join(deviceDir, `${card.slug}.mdx`), + detailContent, + ); + } + }); + + console.log( + `Generated ${cards.length} ${deviceType} pages for ${language}`, + ); + }); + }); +}; + +// Run the generator +generateDevicePages(); diff --git a/static/img/devices/placeholder.svg b/static/img/devices/placeholder.svg new file mode 100644 index 0000000000..8684120d01 --- /dev/null +++ b/static/img/devices/placeholder.svg @@ -0,0 +1,6 @@ + + + + + + \ No newline at end of file diff --git a/tsconfig.json b/tsconfig.json new file mode 100644 index 0000000000..a80f247a1a --- /dev/null +++ b/tsconfig.json @@ -0,0 +1,19 @@ +{ + "compilerOptions": { + "target": "ES2020", + "lib": ["ES2020", "DOM"], + "allowJs": true, + "skipLibCheck": true, + "esModuleInterop": true, + "allowSyntheticDefaultImports": true, + "strict": true, + "forceConsistentCasingInFileNames": true, + "moduleResolution": "node", + "resolveJsonModule": true, + "isolatedModules": true, + "noEmit": true, + "jsx": "react-jsx" + }, + "include": ["src/**/*"], + "exclude": ["node_modules"] +} From 9a86ecbe782a51525850efb367216be6d3d3af86 Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Wed, 4 Jun 2025 16:50:50 +0200 Subject: [PATCH 02/10] add client search; card layout; @evcc/icons --- docs/devices-next/chargers/index.mdx | 737 +++++++++++++++++- docs/devices-next/meters/index.mdx | 611 ++++++++++++++- docs/devices-next/tariffs/index.mdx | 77 +- docs/devices-next/vehicles/index.mdx | 143 +++- .../current/devices-next/chargers/index.mdx | 737 +++++++++++++++++- .../current/devices-next/meters/index.mdx | 611 ++++++++++++++- .../current/devices-next/tariffs/index.mdx | 77 +- .../current/devices-next/vehicles/index.mdx | 143 +++- package-lock.json | 7 + package.json | 1 + src/components/DeviceCard.module.css | 84 +- src/components/DeviceCard.tsx | 20 +- src/components/DeviceGrid.tsx | 147 ++++ src/components/DeviceSearch.module.css | 95 +++ src/components/DeviceSearch.tsx | 90 +++ src/generateDevicesNext.ts | 10 +- 16 files changed, 3533 insertions(+), 57 deletions(-) create mode 100644 src/components/DeviceGrid.tsx create mode 100644 src/components/DeviceSearch.module.css create mode 100644 src/components/DeviceSearch.tsx diff --git a/docs/devices-next/chargers/index.mdx b/docs/devices-next/chargers/index.mdx index 2ea8ff4f7c..ffe0033fde 100644 --- a/docs/devices-next/chargers/index.mdx +++ b/docs/devices-next/chargers/index.mdx @@ -3,10 +3,11 @@ title: Chargers --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Chargers -
+ -
+ diff --git a/docs/devices-next/meters/index.mdx b/docs/devices-next/meters/index.mdx index 16c41c852f..d8eac3696a 100644 --- a/docs/devices-next/meters/index.mdx +++ b/docs/devices-next/meters/index.mdx @@ -3,10 +3,11 @@ title: Meters --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Meters -
+ -
+ diff --git a/docs/devices-next/tariffs/index.mdx b/docs/devices-next/tariffs/index.mdx index 6afb0ee71a..485d6de13d 100644 --- a/docs/devices-next/tariffs/index.mdx +++ b/docs/devices-next/tariffs/index.mdx @@ -3,10 +3,11 @@ title: Tariffs --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Tariffs -
+ -
+ diff --git a/docs/devices-next/vehicles/index.mdx b/docs/devices-next/vehicles/index.mdx index 71ec18fc58..5642bab0d0 100644 --- a/docs/devices-next/vehicles/index.mdx +++ b/docs/devices-next/vehicles/index.mdx @@ -3,10 +3,11 @@ title: Vehicles --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Vehicles -
+ -
+ diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx index 3ac91cf6fa..7c05c6512d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx @@ -3,10 +3,11 @@ title: Chargers --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Chargers -
+ -
+ diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx index 4fc892bea9..40ab9e5433 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx @@ -3,10 +3,11 @@ title: Meters --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Meters -
+ -
+ diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx index 6afb0ee71a..515db3c939 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx @@ -3,10 +3,11 @@ title: Tariffs --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Tariffs -
+ -
+ diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx index a5c71d6392..195786e3ce 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx @@ -3,10 +3,11 @@ title: Vehicles --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # Vehicles -
+ -
+ diff --git a/package-lock.json b/package-lock.json index 857e7a0ac8..3433dcf3ae 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,6 +13,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", + "@evcc/icons": "^0.5.2", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -4521,6 +4522,12 @@ "node": ">=18" } }, + "node_modules/@evcc/icons": { + "version": "0.5.2", + "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.2.tgz", + "integrity": "sha512-NoqABZzACEwEKmIGIitfeaRpwTeO31vOQvWnImdsuzsrOAYlINmJnDl5MTb7bPiiM44637/9L9cmc31GAWSj8A==", + "license": "CC-BY-NC-SA-4.0" + }, "node_modules/@hapi/hoek": { "version": "9.3.0", "resolved": "https://registry.npmjs.org/@hapi/hoek/-/hoek-9.3.0.tgz", diff --git a/package.json b/package.json index c60f20737c..65246f1dbc 100644 --- a/package.json +++ b/package.json @@ -26,6 +26,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", + "@evcc/icons": "^0.5.2", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", diff --git a/src/components/DeviceCard.module.css b/src/components/DeviceCard.module.css index 91df80ef21..da38fc2e36 100644 --- a/src/components/DeviceCard.module.css +++ b/src/components/DeviceCard.module.css @@ -1,31 +1,29 @@ .deviceCard { background: var(--ifm-card-background-color); - border: 1px solid var(--ifm-color-emphasis-200); + border: 2px solid var(--ifm-color-emphasis-300); border-radius: 12px; - transition: all 0.2s ease-in-out; cursor: pointer; overflow: hidden; height: 100%; display: flex; flex-direction: column; - box-shadow: 0 2px 8px rgba(0, 0, 0, 0.1); } .deviceCard:hover { - transform: translateY(-4px); - box-shadow: 0 8px 25px rgba(0, 0, 0, 0.15); - border-color: var(--ifm-color-primary); + border-color: #22c55e; } .deviceCard:focus-visible { - outline: 2px solid var(--ifm-color-primary); + outline: 2px solid #22c55e; outline-offset: 2px; } .thumbnailContainer { position: relative; - height: 200px; - background: var(--ifm-color-emphasis-100); + width: 100%; + aspect-ratio: 1; + background: #ffffff; + border-bottom: 1px solid var(--ifm-color-emphasis-300); display: flex; align-items: center; justify-content: center; @@ -35,12 +33,7 @@ .thumbnail { width: 100%; height: 100%; - object-fit: cover; - transition: transform 0.2s ease-in-out; -} - -.deviceCard:hover .thumbnail { - transform: scale(1.05); + object-fit: contain; } .content { @@ -48,37 +41,38 @@ flex: 1; display: flex; flex-direction: column; - gap: 8px; + gap: 4px; } .title { font-size: 1.1rem; - font-weight: 500; - color: var(--ifm-color-emphasis-800); - line-height: 1.3; + font-weight: 400; + color: var(--ifm-color-emphasis-900); + line-height: 1.4; } .capabilities { display: flex; flex-wrap: wrap; gap: 6px; - margin-top: auto; + margin-top: 16px; } .capabilityTag { - background: var(--ifm-color-emphasis-200); - color: var(--ifm-color-emphasis-700); - padding: 2px 8px; - border-radius: 12px; + background: #dcfce7; + color: #166534; + border: 1px solid #bbf7d0; + padding: 4px 8px; + border-radius: 6px; font-size: 0.75rem; font-weight: 500; + text-decoration: none; } .moreCapabilities { color: var(--ifm-color-emphasis-600); font-size: 0.75rem; font-weight: 500; - font-style: italic; } .footer { @@ -92,9 +86,8 @@ gap: 4px; color: var(--ifm-color-primary); text-decoration: none; - font-weight: 500; + font-weight: 400; font-size: 0.875rem; - transition: color 0.2s ease-in-out; } .viewDetails:hover { @@ -105,19 +98,48 @@ /* Global device grid styles */ :global(.device-grid) { display: grid; - grid-template-columns: repeat(auto-fill, minmax(300px, 1fr)); + grid-template-columns: repeat(4, 1fr); gap: 24px; margin: 32px 0; } +/* Large screens - maintain 4 columns */ +@media (min-width: 1400px) { + :global(.device-grid) { + grid-template-columns: repeat(4, 1fr); + gap: 24px; + } +} + +/* Medium screens - 3 columns */ +@media (max-width: 1200px) { + :global(.device-grid) { + grid-template-columns: repeat(3, 1fr); + gap: 20px; + } +} + +/* Small screens - 2 columns */ @media (max-width: 768px) { :global(.device-grid) { - grid-template-columns: 1fr; + grid-template-columns: repeat(2, 1fr); gap: 16px; } - .thumbnailContainer { - height: 160px; + .content { + padding: 12px; + } + + .footer { + padding: 0 12px 12px 12px; + } +} + +/* Very small screens - 1 column */ +@media (max-width: 480px) { + :global(.device-grid) { + grid-template-columns: 1fr; + gap: 16px; } .content { diff --git a/src/components/DeviceCard.tsx b/src/components/DeviceCard.tsx index 4d6fbbc933..932e9d4973 100644 --- a/src/components/DeviceCard.tsx +++ b/src/components/DeviceCard.tsx @@ -1,4 +1,5 @@ import React from "react"; +import "@evcc/icons"; import Link from "@docusaurus/Link"; import styles from "./DeviceCard.module.css"; @@ -9,6 +10,9 @@ interface DeviceCardProps { capabilities?: string[]; requirements?: string[]; href: string; + group?: string; + type: string; + name: string; } const DeviceCard: React.FC = ({ @@ -18,6 +22,9 @@ const DeviceCard: React.FC = ({ capabilities = [], requirements = [], href, + group, + type, + name, }) => { const handleKeyDown = (event: React.KeyboardEvent) => { if (event.key === "Enter" || event.key === " ") { @@ -53,15 +60,12 @@ const DeviceCard: React.FC = ({ aria-label={`View details for ${brand} ${description}`} >
- {`${brand} { - // Fallback to a placeholder image - (e.target as HTMLImageElement).src = "/img/devices/placeholder.svg"; - }} - /> + >
diff --git a/src/components/DeviceGrid.tsx b/src/components/DeviceGrid.tsx new file mode 100644 index 0000000000..814d865bcc --- /dev/null +++ b/src/components/DeviceGrid.tsx @@ -0,0 +1,147 @@ +import React, { useState, useMemo } from "react"; +import DeviceSearch from "./DeviceSearch"; + +interface DeviceGridProps { + children: React.ReactElement[]; + searchPlaceholder?: string; +} + +interface DeviceCardProps { + brand: string; + description: string; + group?: string; + [key: string]: any; +} + +const DeviceGrid: React.FC = ({ + children, + searchPlaceholder = "Search devices...", +}) => { + const [searchTerm, setSearchTerm] = useState(""); + + const normalizeText = (text: string): string => { + return text + .toLowerCase() + .normalize("NFD") + .replace(/[\u0300-\u036f]/g, "") + .trim(); + }; + + const getGroupDisplayName = ( + group: string | undefined, + deviceType: string, + ): string => { + if (!group) { + // Determine device type from URL or default naming + const typeMap: Record = { + vehicle: "Unterstützte Fahrzeuge", + charger: "Unterstützte Ladegeräte", + meter: "Unterstützte Zähler", + tariff: "Unterstützte Tarife", + }; + return typeMap[deviceType] || "Unterstützte Geräte"; + } + return group; + }; + + const filteredAndGroupedDevices = useMemo(() => { + // First filter by search term + const filtered = searchTerm.trim() + ? children.filter((child) => { + const props = child.props as DeviceCardProps; + const brand = normalizeText(props.brand || ""); + const description = normalizeText(props.description || ""); + const normalizedSearch = normalizeText(searchTerm); + + return ( + brand.includes(normalizedSearch) || + description.includes(normalizedSearch) + ); + }) + : children; + + // Then group by group field + const groups = new Map(); + + filtered.forEach((child) => { + const props = child.props as DeviceCardProps; + const groupKey = props.group || ""; + + if (!groups.has(groupKey)) { + groups.set(groupKey, []); + } + groups.get(groupKey)!.push(child); + }); + + // Sort devices within each group by display name (Brand + Description) + groups.forEach((devices, groupKey) => { + devices.sort((a, b) => { + const aProps = a.props as DeviceCardProps; + const bProps = b.props as DeviceCardProps; + const aDisplayName = + `${aProps.brand || ""} ${aProps.description || ""}`.trim(); + const bDisplayName = + `${bProps.brand || ""} ${bProps.description || ""}`.trim(); + return aDisplayName.localeCompare(bDisplayName); + }); + }); + + // Sort groups: empty group first, then alphabetically + const sortedGroups = Array.from(groups.entries()).sort(([a], [b]) => { + if (a === "" && b !== "") return -1; + if (a !== "" && b === "") return 1; + return a.localeCompare(b); + }); + + return sortedGroups; + }, [children, searchTerm]); + + const handleSearchChange = (newSearchTerm: string) => { + setSearchTerm(newSearchTerm); + }; + + // Determine device type from the current URL or context + const deviceType = + typeof window !== "undefined" + ? window.location.pathname.split("/").slice(-2, -1)[0]?.slice(0, -1) || + "device" + : "device"; + + const totalDevices = filteredAndGroupedDevices.reduce( + (sum, [, devices]) => sum + devices.length, + 0, + ); + + return ( + <> + + + {totalDevices === 0 && searchTerm.trim() ? ( +
+ No devices found matching "{searchTerm}" +
+ ) : ( + <> + {filteredAndGroupedDevices.map(([groupKey, devices]) => ( +
+

{getGroupDisplayName(groupKey, deviceType)}

+
{devices}
+
+ ))} + + )} + + ); +}; + +export default DeviceGrid; diff --git a/src/components/DeviceSearch.module.css b/src/components/DeviceSearch.module.css new file mode 100644 index 0000000000..143734da35 --- /dev/null +++ b/src/components/DeviceSearch.module.css @@ -0,0 +1,95 @@ +.searchContainer { + margin-bottom: 32px; +} + +.searchInputWrapper { + position: relative; + max-width: 400px; + margin: 0 auto; +} + +.searchInput { + width: 100%; + padding: 12px 16px 12px 48px; + border: 2px solid var(--ifm-color-emphasis-300); + border-radius: 12px; + font-size: 1rem; + background: var(--ifm-background-color); + color: var(--ifm-color-emphasis-900); + transition: all 0.2s ease-in-out; + outline: none; +} + +.searchInput:focus { + border-color: #22c55e; + box-shadow: 0 0 0 3px rgba(34, 197, 94, 0.1); +} + +.searchInput::placeholder { + color: var(--ifm-color-emphasis-500); +} + +.searchIcon { + position: absolute; + left: 16px; + top: 50%; + transform: translateY(-50%); + width: 20px; + height: 20px; + color: var(--ifm-color-emphasis-500); + pointer-events: none; +} + +.clearButton { + position: absolute; + right: 12px; + top: 50%; + transform: translateY(-50%); + width: 24px; + height: 24px; + border: none; + background: none; + color: var(--ifm-color-emphasis-500); + cursor: pointer; + border-radius: 4px; + display: flex; + align-items: center; + justify-content: center; + transition: all 0.2s ease-in-out; +} + +.clearButton:hover { + color: var(--ifm-color-emphasis-700); + background: var(--ifm-color-emphasis-200); +} + +.clearButton:focus-visible { + outline: 2px solid #22c55e; + outline-offset: 2px; +} + +.clearButton svg { + width: 16px; + height: 16px; +} + +@media (max-width: 768px) { + .searchContainer { + margin-bottom: 24px; + } + + .searchInputWrapper { + max-width: none; + } + + .searchInput { + padding: 10px 14px 10px 44px; + font-size: 16px; /* Prevent zoom on iOS */ + } + + .searchIcon { + left: 14px; + width: 18px; + height: 18px; + } +} diff --git a/src/components/DeviceSearch.tsx b/src/components/DeviceSearch.tsx new file mode 100644 index 0000000000..198a247214 --- /dev/null +++ b/src/components/DeviceSearch.tsx @@ -0,0 +1,90 @@ +import React, { useState, useRef } from "react"; +import styles from "./DeviceSearch.module.css"; + +interface DeviceSearchProps { + onSearchChange: (searchTerm: string) => void; + placeholder?: string; +} + +const DeviceSearch: React.FC = ({ + onSearchChange, + placeholder = "Search devices...", +}) => { + const [searchTerm, setSearchTerm] = useState(""); + const inputRef = useRef(null); + + const handleInputChange = (event: React.ChangeEvent) => { + const value = event.target.value; + setSearchTerm(value); + onSearchChange(value); + }; + + const handleClear = () => { + setSearchTerm(""); + onSearchChange(""); + inputRef.current?.focus(); + }; + + const handleKeyDown = (event: React.KeyboardEvent) => { + if (event.key === "Escape") { + handleClear(); + } + }; + + return ( +
+
+ + + {searchTerm && ( + + )} +
+
+ ); +}; + +export default DeviceSearch; diff --git a/src/generateDevicesNext.ts b/src/generateDevicesNext.ts index b7b84c8d14..4c6944bf0c 100644 --- a/src/generateDevicesNext.ts +++ b/src/generateDevicesNext.ts @@ -34,6 +34,7 @@ interface DeviceCard { requirements: string[]; countries: string[]; slug: string; + group?: string; } const DEVICE_TYPES = ["vehicle", "charger", "meter", "tariff"] as const; @@ -231,6 +232,7 @@ const generateDeviceCard = ( requirements: data.requirements || [], countries: data.countries || [], slug, + group: data.product.group, }; }; @@ -246,10 +248,11 @@ title: ${title} --- import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; # ${title} -
+ ${cards .sort((a, b) => `${a.brand} ${a.description}`.localeCompare(`${b.brand} ${b.description}`), @@ -286,10 +289,13 @@ ${cards capabilities={[${features.map((f) => `"${f}"`).join(", ")}]} requirements={[]} href="/docs/devices-next/${deviceType}s/${card.slug}" + group="${card.group || ""}" + type="${deviceType}" + name="${card.slug}" />`; }) .join("\n")} -
+ `; }; From 8beb39d332ddf98913a2094bc0268df9f15cc8af Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Wed, 4 Jun 2025 17:33:42 +0200 Subject: [PATCH 03/10] fix ssr --- package-lock.json | 8 ++++---- package.json | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package-lock.json b/package-lock.json index 3433dcf3ae..80ff2c4045 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,7 +13,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.2", + "@evcc/icons": "^0.5.4", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -4523,9 +4523,9 @@ } }, "node_modules/@evcc/icons": { - "version": "0.5.2", - "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.2.tgz", - "integrity": "sha512-NoqABZzACEwEKmIGIitfeaRpwTeO31vOQvWnImdsuzsrOAYlINmJnDl5MTb7bPiiM44637/9L9cmc31GAWSj8A==", + "version": "0.5.4", + "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.4.tgz", + "integrity": "sha512-PFiJkitXbCglCIxY1DbOhuhiP18ue7+5QR/grB2QZcgbXlQx9skAhcIHGlUEksuWk5GyxeVfJYLmue/nZHj+Fw==", "license": "CC-BY-NC-SA-4.0" }, "node_modules/@hapi/hoek": { diff --git a/package.json b/package.json index 65246f1dbc..4abe4c2571 100644 --- a/package.json +++ b/package.json @@ -26,7 +26,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.2", + "@evcc/icons": "^0.5.4", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", From ed4d3aca0718a29ebcfd3cd05b9731dcaa4d1cf3 Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Fri, 6 Jun 2025 00:31:10 +0200 Subject: [PATCH 04/10] new icons; wider layout --- docs/devices-next/chargers/index.mdx | 1 + docs/devices-next/meters/index.mdx | 1 + docs/devices-next/tariffs/index.mdx | 1 + docs/devices-next/vehicles/index.mdx | 1 + .../current/devices-next/chargers/index.mdx | 1 + .../current/devices-next/meters/index.mdx | 1 + .../current/devices-next/tariffs/index.mdx | 1 + .../current/devices-next/vehicles/index.mdx | 1 + package-lock.json | 8 ++++---- package.json | 2 +- src/components/DeviceCard.module.css | 7 ++----- src/generateDevicesNext.ts | 1 + 12 files changed, 16 insertions(+), 10 deletions(-) diff --git a/docs/devices-next/chargers/index.mdx b/docs/devices-next/chargers/index.mdx index ffe0033fde..4d80e03a30 100644 --- a/docs/devices-next/chargers/index.mdx +++ b/docs/devices-next/chargers/index.mdx @@ -1,5 +1,6 @@ --- title: Chargers +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/docs/devices-next/meters/index.mdx b/docs/devices-next/meters/index.mdx index d8eac3696a..5675b0f119 100644 --- a/docs/devices-next/meters/index.mdx +++ b/docs/devices-next/meters/index.mdx @@ -1,5 +1,6 @@ --- title: Meters +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/docs/devices-next/tariffs/index.mdx b/docs/devices-next/tariffs/index.mdx index 485d6de13d..7892c964e1 100644 --- a/docs/devices-next/tariffs/index.mdx +++ b/docs/devices-next/tariffs/index.mdx @@ -1,5 +1,6 @@ --- title: Tariffs +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/docs/devices-next/vehicles/index.mdx b/docs/devices-next/vehicles/index.mdx index 5642bab0d0..9229186377 100644 --- a/docs/devices-next/vehicles/index.mdx +++ b/docs/devices-next/vehicles/index.mdx @@ -1,5 +1,6 @@ --- title: Vehicles +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx index 7c05c6512d..9b332ad7a1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx @@ -1,5 +1,6 @@ --- title: Chargers +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx index 40ab9e5433..df9953760e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx @@ -1,5 +1,6 @@ --- title: Meters +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx index 515db3c939..144d49f855 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx @@ -1,5 +1,6 @@ --- title: Tariffs +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx index 195786e3ce..14d17d1a2f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx @@ -1,5 +1,6 @@ --- title: Vehicles +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/package-lock.json b/package-lock.json index 80ff2c4045..d5b1f2bc79 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,7 +13,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.4", + "@evcc/icons": "^0.5.5", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -4523,9 +4523,9 @@ } }, "node_modules/@evcc/icons": { - "version": "0.5.4", - "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.4.tgz", - "integrity": "sha512-PFiJkitXbCglCIxY1DbOhuhiP18ue7+5QR/grB2QZcgbXlQx9skAhcIHGlUEksuWk5GyxeVfJYLmue/nZHj+Fw==", + "version": "0.5.5", + "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.5.tgz", + "integrity": "sha512-BDsFpI5FxDkL5L34f14qEeuXaFjILHhJqj1wR/DiJo+19wCEcJa5ML6Y7MRinfRPZ57OlhNDGpcKuLA+46Wjvg==", "license": "CC-BY-NC-SA-4.0" }, "node_modules/@hapi/hoek": { diff --git a/package.json b/package.json index 4abe4c2571..c7ba75ff39 100644 --- a/package.json +++ b/package.json @@ -26,7 +26,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.4", + "@evcc/icons": "^0.5.5", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", diff --git a/src/components/DeviceCard.module.css b/src/components/DeviceCard.module.css index da38fc2e36..c12ee7ee22 100644 --- a/src/components/DeviceCard.module.css +++ b/src/components/DeviceCard.module.css @@ -98,15 +98,14 @@ /* Global device grid styles */ :global(.device-grid) { display: grid; - grid-template-columns: repeat(4, 1fr); + grid-template-columns: repeat(auto-fit, minmax(200px, 1fr)); gap: 24px; margin: 32px 0; } -/* Large screens - maintain 4 columns */ +/* Large screens - more columns with auto-fit */ @media (min-width: 1400px) { :global(.device-grid) { - grid-template-columns: repeat(4, 1fr); gap: 24px; } } @@ -114,7 +113,6 @@ /* Medium screens - 3 columns */ @media (max-width: 1200px) { :global(.device-grid) { - grid-template-columns: repeat(3, 1fr); gap: 20px; } } @@ -122,7 +120,6 @@ /* Small screens - 2 columns */ @media (max-width: 768px) { :global(.device-grid) { - grid-template-columns: repeat(2, 1fr); gap: 16px; } diff --git a/src/generateDevicesNext.ts b/src/generateDevicesNext.ts index 4c6944bf0c..3b47cf5086 100644 --- a/src/generateDevicesNext.ts +++ b/src/generateDevicesNext.ts @@ -245,6 +245,7 @@ const generateOverviewPage = ( return `--- title: ${title} +hide_table_of_contents: true --- import DeviceCard from '@site/src/components/DeviceCard'; From a5460b760d424e7c21ce70bc74cb4763b5eae0c8 Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Sat, 7 Jun 2025 14:57:34 +0200 Subject: [PATCH 05/10] more icons --- package-lock.json | 22 +++++++++++++++++----- package.json | 2 +- 2 files changed, 18 insertions(+), 6 deletions(-) diff --git a/package-lock.json b/package-lock.json index d5b1f2bc79..c69e7ea740 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,7 +13,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.5", + "@evcc/icons": "^0.5.6", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -4523,10 +4523,13 @@ } }, "node_modules/@evcc/icons": { - "version": "0.5.5", - "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.5.tgz", - "integrity": "sha512-BDsFpI5FxDkL5L34f14qEeuXaFjILHhJqj1wR/DiJo+19wCEcJa5ML6Y7MRinfRPZ57OlhNDGpcKuLA+46Wjvg==", - "license": "CC-BY-NC-SA-4.0" + "version": "0.5.6", + "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.6.tgz", + "integrity": "sha512-qYXKSkJlSTQm7OW4FdzMKBHf600YUr/CZKcNJTXsuyiMAKuOHmu5xKJWgP1K9jI2WJrMrhbVJpTcKggIi3DZJA==", + "license": "CC-BY-NC-SA-4.0", + "dependencies": { + "fuse.js": "^7.1.0" + } }, "node_modules/@hapi/hoek": { "version": "9.3.0", @@ -11876,6 +11879,15 @@ "url": "https://github.com/sponsors/ljharb" } }, + "node_modules/fuse.js": { + "version": "7.1.0", + "resolved": "https://registry.npmjs.org/fuse.js/-/fuse.js-7.1.0.tgz", + "integrity": "sha512-trLf4SzuuUxfusZADLINj+dE8clK1frKdmqiJNb1Es75fmI5oY6X2mxLVUciLLjxqw/xr72Dhy+lER6dGd02FQ==", + "license": "Apache-2.0", + "engines": { + "node": ">=10" + } + }, "node_modules/gensync": { "version": "1.0.0-beta.2", "resolved": "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz", diff --git a/package.json b/package.json index c7ba75ff39..8ea5451507 100644 --- a/package.json +++ b/package.json @@ -26,7 +26,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.5", + "@evcc/icons": "^0.5.6", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", From 05e50ac61e02a54c507bcbf7f5b153d5ab434a50 Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Wed, 11 Jun 2025 17:55:03 +0200 Subject: [PATCH 06/10] deps --- package-lock.json | 8 ++++---- package.json | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package-lock.json b/package-lock.json index c69e7ea740..d941dd488c 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,7 +13,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.6", + "@evcc/icons": "^0.5.8", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -4523,9 +4523,9 @@ } }, "node_modules/@evcc/icons": { - "version": "0.5.6", - "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.6.tgz", - "integrity": "sha512-qYXKSkJlSTQm7OW4FdzMKBHf600YUr/CZKcNJTXsuyiMAKuOHmu5xKJWgP1K9jI2WJrMrhbVJpTcKggIi3DZJA==", + "version": "0.5.8", + "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.8.tgz", + "integrity": "sha512-RbnX/4HEOgNzdiEs4Du11usuoD7KtzBtTxL57GObELc8SFg1RoE9rlR1RbnNbj8bAnCcrnr7+4CgJmUXkF+Scg==", "license": "CC-BY-NC-SA-4.0", "dependencies": { "fuse.js": "^7.1.0" diff --git a/package.json b/package.json index 8ea5451507..cd5763db85 100644 --- a/package.json +++ b/package.json @@ -26,7 +26,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.6", + "@evcc/icons": "^0.5.8", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", From f35b533345aa9fa3d99f41e83d128e0c836bf51b Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Wed, 11 Jun 2025 19:07:36 +0200 Subject: [PATCH 07/10] use identifier instead of slug; add params table to detail --- .../chargers/abb-terra-ac-ocpp.mdx | 49 + docs/devices-next/chargers/abb-terra-ac.mdx | 45 +- docs/devices-next/chargers/abl-em4-sbcx.mdx | 38 - .../chargers/abl-em4-single-ocpp.mdx | 46 + .../chargers/abl-em4-single-sbcx.mdx | 46 + .../chargers/abl-em4-twin-ocpp.mdx | 46 + .../chargers/abl-em4-twin-sbcx.mdx | 46 + docs/devices-next/chargers/abl-emh1.mdx | 8 + docs/devices-next/chargers/abl-emh2-ocpp.mdx | 46 + docs/devices-next/chargers/abl-emh2.mdx | 8 + docs/devices-next/chargers/abl-emh3-ocpp.mdx | 46 + .../devices-next/chargers/abl-sursum-emh2.mdx | 33 - .../devices-next/chargers/abl-sursum-emh3.mdx | 33 - .../devices-next/chargers/abl-sursum-emh4.mdx | 33 - docs/devices-next/chargers/alfen-eve-ocpp.mdx | 46 + docs/devices-next/chargers/alfen-eve.mdx | 33 +- docs/devices-next/chargers/alpha-innotec.mdx | 50 + .../chargers/alphatec-ladesaule-twin.mdx | 7 + .../chargers/alphatec-wallbox-mini-power.mdx | 38 - .../chargers/alphatec-wallbox-mini.mdx | 45 + .../chargers/alphatec-wallbox-power.mdx | 45 + .../amperfied-wallbox-connect-business.mdx | 35 + .../amperfied-wallbox-connect-home.mdx | 35 + .../amperfied-wallbox-connect-solar.mdx | 35 + .../amperfied-wallbox-connectbusiness.mdx | 28 - .../amperfied-wallbox-connecthome.mdx | 28 - .../amperfied-wallbox-connectsolar.mdx | 28 - .../amperfied-wallbox-energy-control.mdx | 7 + docs/devices-next/chargers/ampure-live.mdx | 31 - docs/devices-next/chargers/ampure-next.mdx | 8 + docs/devices-next/chargers/ampure-unite.mdx | 7 + .../chargers/audi-audi-wallbox-pro.mdx | 29 - .../chargers/audi-wallbox-plus.mdx | 8 + .../chargers/audi-wallbox-pro.mdx | 37 + .../chargers/autel-ac-compact.mdx | 13 + .../chargers/autel-ac-maxicharger.mdx | 13 + .../chargers/autoaid-business-wallbox.mdx | 13 + .../chargers/autoaid-intelligent-wallbox.mdx | 13 + docs/devices-next/chargers/avm-fritzdect.mdx | 14 + docs/devices-next/chargers/bender-cc612.mdx | 7 + docs/devices-next/chargers/bender-cc613.mdx | 7 + docs/devices-next/chargers/bender-icc1314.mdx | 7 + docs/devices-next/chargers/bender-icc1324.mdx | 7 + docs/devices-next/chargers/bmw-i-wallbox.mdx | 8 + docs/devices-next/chargers/bosch-sg-ready.mdx | 10 + docs/devices-next/chargers/bosch-x-change.mdx | 9 + .../chargers/buderus-logamatic-hmc-20-z.mdx | 50 + .../chargers/buderus-logamatic-hmc-20.mdx | 50 + .../chargers/buderus-sg-ready.mdx | 10 + .../chargers/cfos-power-brain-solar.mdx | 7 + .../chargers/cfos-power-brain.mdx | 7 + .../chargers/charge-amps-halo.mdx | 13 + docs/devices-next/chargers/compleo-ebox.mdx | 7 + .../chargers/cta-all-in-one-aeroplus.mdx | 50 + .../devices-next/chargers/cubos-c11e-c22e.mdx | 31 - docs/devices-next/chargers/cubos-c11e.mdx | 38 + docs/devices-next/chargers/cubos-c22e.mdx | 38 + .../chargers/cupra-charger-connect-2.mdx | 8 + .../chargers/cupra-charger-connect.mdx | 8 + .../chargers/cupra-charger-pro-2.mdx | 8 + .../cupra-charger-pro-eichrecht-2.mdx | 8 + .../chargers/cupra-charger-pro.mdx | 8 + .../chargers/dadapower-premium-wallbox.mdx | 7 + .../chargers/daheimladen-wallbox.mdx | 8 + .../chargers/daikin-homehub-sg-ready.mdx | 8 + .../chargers/delta-ac-max-basic.mdx | 8 + .../chargers/delta-ac-max-smart.mdx | 8 + .../chargers/delta-slim-charger.mdx | 8 + .../chargers/delta-ultra-fast-charger.mdx | 8 + docs/devices-next/chargers/demo-charger.mdx | 11 + .../devices-next/chargers/e-on-drive-ebox.mdx | 35 + .../devices-next/chargers/e-on-drive-vbox.mdx | 38 + .../chargers/e3-dc-easy-connect.mdx | 38 + .../chargers/e3dc-easy-connect.mdx | 31 - .../chargers/easee-charge-core.mdx | 11 + .../chargers/easee-charge-lite.mdx | 11 + docs/devices-next/chargers/easee-charge.mdx | 11 + docs/devices-next/chargers/easee-home.mdx | 11 + docs/devices-next/chargers/ebee-wallbox.mdx | 7 + docs/devices-next/chargers/echarge-cph1.mdx | 8 + .../chargers/echarge-cph2-cpm2.mdx | 23 - docs/devices-next/chargers/echarge-cph2.mdx | 30 + docs/devices-next/chargers/echarge-cpm2.mdx | 30 + .../chargers/ecoharmony-evse-epc-2-0-plus.mdx | 46 + .../chargers/ecoharmony-evse-epc-20-plus.mdx | 39 - .../chargers/edgetech-smart-evse.mdx | 7 + .../chargers/eebus-compatible.mdx | 8 + docs/devices-next/chargers/elco.mdx | 50 + docs/devices-next/chargers/elecq-biz.mdx | 13 + docs/devices-next/chargers/elecq-home.mdx | 13 + docs/devices-next/chargers/elecq-station.mdx | 13 + docs/devices-next/chargers/eledio-go.mdx | 13 + .../chargers/elli-charger-connect-2.mdx | 8 + .../chargers/elli-charger-connect.mdx | 8 + .../chargers/elli-charger-pro-2.mdx | 8 + .../chargers/elli-charger-pro-eichrecht-2.mdx | 8 + .../chargers/elli-charger-pro.mdx | 8 + docs/devices-next/chargers/em2go-home.mdx | 7 + .../chargers/em2go-pro-power-ocpp-onc.mdx | 36 + .../chargers/em2go-pro-power-ocpponc.mdx | 29 - .../chargers/en-ac-ev-charger.mdx | 33 - docs/devices-next/chargers/enercab-smart.mdx | 13 + .../chargers/enplus-ac-ev-charger.mdx | 46 + .../chargers/ensto-chago-wallbox.mdx | 7 + .../chargers/entratek-power-dot-fix.mdx | 13 + .../chargers/entratek-power-dot-pro-2.mdx | 13 + docs/devices-next/chargers/eon-drive-ebox.mdx | 28 - docs/devices-next/chargers/eon-drive-vbox.mdx | 31 - .../devices-next/chargers/esl-walli-light.mdx | 7 + .../chargers/esystems-ghostone.mdx | 8 + docs/devices-next/chargers/etrel-inch-duo.mdx | 9 + docs/devices-next/chargers/etrel-inch.mdx | 8 + docs/devices-next/chargers/evbox-elvi.mdx | 13 + docs/devices-next/chargers/evbox-livo.mdx | 8 + docs/devices-next/chargers/evse-din.mdx | 7 + docs/devices-next/chargers/evse-wifi.mdx | 7 + .../chargers/free2move-eprowallbox-move.mdx | 42 + .../chargers/free2move-eprowallbox.mdx | 7 + .../free2move-esolutions-eprowallbox.mdx | 13 + .../chargers/fronius-wattpilot-ocpp.mdx | 46 + .../chargers/fronius-wattpilot.mdx | 33 - .../chargers/garo-glb-glb-ls4-ls4-compact.mdx | 31 - docs/devices-next/chargers/garo-glb.mdx | 38 + docs/devices-next/chargers/garo-glbplus.mdx | 38 + .../chargers/garo-ls4-compact.mdx | 38 + docs/devices-next/chargers/garo-ls4.mdx | 38 + .../chargers/go-e-charger-gemini-ocpp.mdx | 46 + .../chargers/go-e-charger-gemini.mdx | 30 +- .../chargers/go-e-charger-home.mdx | 28 - .../chargers/go-e-charger-homefix.mdx | 7 + .../chargers/go-e-charger-homeplus.mdx | 35 + .../chargers/go-e-charger-pro-ocpp.mdx | 46 + .../chargers/go-e-charger-pro.mdx | 28 +- .../chargers/go-e-charger-v3-ocpp.mdx | 46 + .../devices-next/chargers/go-e-charger-v3.mdx | 30 +- .../chargers/hardy-barth-cph1.mdx | 39 + .../chargers/hardy-barth-cph2.mdx | 30 + .../chargers/hardy-barth-cpm2.mdx | 30 + .../devices-next/chargers/hardybarth-cph1.mdx | 31 - .../chargers/hardybarth-cph2-cpm2.mdx | 23 - .../chargers/heidelberg-energy-control.mdx | 7 + docs/devices-next/chargers/hesotec-ebox.mdx | 35 + .../chargers/hesotec-esat-ebox.mdx | 28 - docs/devices-next/chargers/hesotec-esat.mdx | 35 + .../chargers/home-assistant-switch.mdx | 14 + .../chargers/homecharge-homecharger.mdx | 13 + docs/devices-next/chargers/homematic-ip.mdx | 18 + docs/devices-next/chargers/homewizard.mdx | 11 + .../chargers/huawei-scharger-22kt-s0.mdx | 46 + .../huawei-scharger-7ks-s0-22kt-s0.mdx | 33 - .../chargers/huawei-scharger-7ks-s0.mdx | 46 + docs/devices-next/chargers/idm.mdx | 8 + docs/devices-next/chargers/index.mdx | 880 +++-- docs/devices-next/chargers/innogy-ebox.mdx | 7 + docs/devices-next/chargers/inro-pantabox.mdx | 7 + .../chargers/juice-charger-me.mdx | 7 + .../chargers/junkers-sg-ready.mdx | 10 + ...-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx | 31 - .../chargers/kathrein-kwb-ac20.mdx | 38 + .../chargers/kathrein-kwb-ac35.mdx | 38 + .../chargers/kathrein-kwb-ac40-e.mdx | 38 + .../chargers/kathrein-kwb-ac40.mdx | 38 + .../chargers/kathrein-kwb-ac60-e.mdx | 38 + .../chargers/kathrein-kwb-ac60.mdx | 38 + .../keba-kecontact-p20-p30-cx-series.mdx | 41 - .../chargers/keba-kecontact-p20.mdx | 49 + .../chargers/keba-kecontact-p30-c-series.mdx | 49 + .../chargers/keba-kecontact-p30-x-series.mdx | 49 + .../chargers/keba-kecontact-p40-p40-pro.mdx | 41 - .../chargers/keba-kecontact-p40-pro.mdx | 49 + .../chargers/keba-kecontact-p40.mdx | 49 + .../chargers/kermi-x-center-pro.mdx | 9 + .../chargers/kontron-solar-charger.mdx | 8 + docs/devices-next/chargers/kostal-enector.mdx | 7 + docs/devices-next/chargers/kse-wbx16.mdx | 7 + .../chargers/ladefoxx-evload-mikro-20.mdx | 36 - .../devices-next/chargers/ladefoxx-evload.mdx | 44 + .../chargers/ladefoxx-mikro-2-0.mdx | 44 + .../chargers/lambda-eu-l-series.mdx | 9 + .../chargers/lrt-home-essential.mdx | 38 - .../chargers/lrt-home-essentialplus.mdx | 45 + .../chargers/mennekes-amedio-professional.mdx | 7 + .../mennekes-amtron-4business-700.mdx | 7 + .../chargers/mennekes-amtron-4you-300.mdx | 7 + .../chargers/mennekes-amtron-4you-500.mdx | 7 + .../mennekes-amtron-chargecontrol.mdx | 7 + .../chargers/mennekes-amtron-compact-2-0s.mdx | 47 + .../chargers/mennekes-amtron-compact-20s.mdx | 40 - .../chargers/mennekes-amtron-premium.mdx | 7 + .../chargers/mennekes-amtron-professional.mdx | 7 + .../chargers/mennekes-amtron-xtra.mdx | 7 + .../mennekes-emobility-gateway-acu.mdx | 13 + .../chargers/mennekes-smart-acu.mdx | 13 + .../chargers/mennekes-smart-t-acu.mdx | 13 + .../devices-next/chargers/my-pv-ac-elwa-2.mdx | 8 + .../chargers/my-pv-ac-thor-9s.mdx | 39 + .../chargers/my-pv-ac-thor-ac-thor-9s.mdx | 30 - docs/devices-next/chargers/my-pv-ac-thor.mdx | 39 + docs/devices-next/chargers/mystrom-switch.mdx | 11 + docs/devices-next/chargers/nibe-ap-aw10.mdx | 50 + .../devices-next/chargers/novelan-wpr-net.mdx | 50 + .../devices-next/chargers/nrgkick-connect.mdx | 13 +- docs/devices-next/chargers/nrgkick-gen2.mdx | 12 +- .../chargers/obo-bettermann-ion.mdx | 7 + .../ocpp-1-6j-compatible-smart-charging.mdx | 67 + .../ocpp-16j-compatible-smart-charging.mdx | 54 - docs/devices-next/chargers/openevse.mdx | 9 + docs/devices-next/chargers/openwb-pro.mdx | 7 + docs/devices-next/chargers/openwb-series2.mdx | 9 + .../chargers/openwb-software-2-x.mdx | 53 + .../chargers/openwb-software-2x.mdx | 44 - .../chargers/optec-mobility-one.mdx | 7 + docs/devices-next/chargers/orbis-viaris.mdx | 13 + .../chargers/pc-electric-garo.mdx | 8 + .../devices-next/chargers/peblar-business.mdx | 38 + .../peblar-home-home-plus-business.mdx | 31 - .../chargers/peblar-home-plus.mdx | 38 + docs/devices-next/chargers/peblar-home.mdx | 38 + .../chargers/phoenix-contact-charx.mdx | 8 + .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 7 + ...ix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 7 + ...oenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 7 + ...nix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 7 + ...hoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 7 + .../chargers/phoenix-contact-ev-ser.mdx | 7 + docs/devices-next/chargers/plugchoice.mdx | 9 + .../porsche-mobile-charger-connect.mdx | 8 + .../chargers/porsche-mobile-charger-plus.mdx | 8 + .../devices-next/chargers/porsche-wallbox.mdx | 8 + .../devices-next/chargers/pracht-alpha-xt.mdx | 9 + docs/devices-next/chargers/pracht-mono-xt.mdx | 9 + docs/devices-next/chargers/pracht-pni.mdx | 9 + docs/devices-next/chargers/pracht-xt.mdx | 66 - docs/devices-next/chargers/pracht-xtplus.mdx | 75 + .../chargers/pulsares-simplebox.mdx | 7 + docs/devices-next/chargers/pulsatrix.mdx | 7 + .../chargers/qcells-q-home-edrive-a.mdx | 45 + .../chargers/qcells-qhome-edrive-a.mdx | 38 - .../devices-next/chargers/roth-thermoaura.mdx | 50 + .../chargers/roth-thermoterra.mdx | 50 + .../chargers/schneider-evlink-pro.mdx | 7 + .../chargers/schrack-i-charge-cion.mdx | 7 + .../chargers/senec-wallbox-pro-s.mdx | 7 + .../chargers/senec-wallbox-pro.mdx | 8 + docs/devices-next/chargers/shelly-1.mdx | 50 + docs/devices-next/chargers/shelly-plug-s.mdx | 50 + docs/devices-next/chargers/shelly-plus-1.mdx | 50 + docs/devices-next/chargers/shelly-pro-1.mdx | 50 + docs/devices-next/chargers/shelly.mdx | 36 - .../chargers/siemens-versicharge-gen3.mdx | 7 + .../chargers/skoda-charger-connect.mdx | 8 + .../chargers/skoda-charger-pro-eichrecht.mdx | 8 + .../chargers/skoda-charger-pro.mdx | 8 + .../chargers/skoda-iv-charger-connect.mdx | 20 +- .../chargers/skoda-iv-charger-connectplus.mdx | 37 + docs/devices-next/chargers/sma-echarger.mdx | 37 + .../chargers/sma-ev-charger-echarger.mdx | 28 - docs/devices-next/chargers/sma-ev-charger.mdx | 37 + .../chargers/smartfox-pro-charger.mdx | 7 + docs/devices-next/chargers/smartwb.mdx | 7 + .../chargers/solaredge-home-ev-charger.mdx | 8 + docs/devices-next/chargers/solax-x3-evc.mdx | 7 + .../chargers/sonnen-sonnencharger.mdx | 8 + .../chargers/spelsberg-wallbox-smart-pro.mdx | 7 + .../chargers/stark-in-strom-easy.mdx | 7 + .../stiebel-eltron-lwa-lwz-sg-ready.mdx | 35 + .../stiebel-eltron-lwalwz-sg-ready.mdx | 27 - .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 8 + .../chargers/sungrow-ac011e-01.mdx | 7 + docs/devices-next/chargers/sungrow-ac011e.mdx | 13 + .../chargers/sungrow-ac22e-01.mdx | 48 + .../chargers/tasmota-single-phase.mdx | 14 + .../chargers/tecalor-thz-sg-ready.mdx | 8 + .../chargers/technisat-technivolt.mdx | 7 + docs/devices-next/chargers/tesla-twc3.mdx | 24 - .../chargers/tesla-wall-connector-gen-3.mdx | 31 + docs/devices-next/chargers/tessie.mdx | 9 + .../chargers/tigo-go-ev-charger.mdx | 7 + .../chargers/tinkerforge-warp-charger-pro.mdx | 13 + .../tinkerforge-warp-charger-smart.mdx | 13 + .../tinkerforge-warp3-charger-pro.mdx | 12 + .../tinkerforge-warp3-charger-smart.mdx | 12 + .../chargers/tp-link-h-series-smart-plug.mdx | 11 + .../tp-link-tapo-p-series-smart-plug.mdx | 13 + .../chargers/ubitricity-heinz.mdx | 7 + docs/devices-next/chargers/v2c-trydan.mdx | 7 + .../chargers/vaillant-sensonet-sg-ready.mdx | 11 + .../chargers/vestel-connect-plus.mdx | 38 + .../vestel-evc04-home-smart-connect-plus.mdx | 31 - .../chargers/vestel-evc04-home-smart.mdx | 38 + .../victron-ev-charging-station-via-gx.mdx | 7 + .../chargers/victron-ev-charging-station.mdx | 7 + .../chargers/viessmann-heatpump-sg-ready.mdx | 15 +- .../viridian-ev-evse-epc-2-0-plus.mdx | 46 + .../chargers/viridian-ev-evse-epc-20-plus.mdx | 39 - .../chargers/volkswagen-charger-connect-2.mdx | 8 + .../chargers/volkswagen-charger-pro-2.mdx | 8 + .../volkswagen-charger-pro-eichrecht-2.mdx | 8 + .../volkswagen-id-charger-connect.mdx | 8 + .../chargers/volkswagen-id-charger-pro.mdx | 8 + docs/devices-next/chargers/volt-time-one.mdx | 8 + .../chargers/volt-time-source-2.mdx | 8 + .../chargers/volt-time-source-2s.mdx | 8 + .../chargers/volt-time-source.mdx | 8 + .../chargers/wallbe-eco-2-0-s.mdx | 38 + docs/devices-next/chargers/wallbe-eco-20s.mdx | 31 - docs/devices-next/chargers/wallbe-eco.mdx | 7 + docs/devices-next/chargers/wallbe-pro.mdx | 7 + .../chargers/wallbox-commander-2-fw-5-x.mdx | 55 + .../chargers/wallbox-commander-2-fw-5x.mdx | 42 - .../chargers/wallbox-commander-2.mdx | 13 + .../chargers/wallbox-copper-sb-fw-5-x.mdx | 55 + .../chargers/wallbox-copper-sb-fw-5x.mdx | 42 - .../chargers/wallbox-copper-sb.mdx | 13 + .../chargers/wallbox-pulsar-max-fw-5-x.mdx | 55 + .../chargers/wallbox-pulsar-max-fw-5x.mdx | 42 - .../chargers/wallbox-pulsar-max.mdx | 13 + .../chargers/wallbox-pulsar-plus-fw-5-x.mdx | 55 + .../chargers/wallbox-pulsar-plus-fw-5x.mdx | 42 - .../chargers/wallbox-pulsar-plus.mdx | 13 + .../chargers/walther-werke-basic-evo-pro.mdx | 7 + docs/devices-next/chargers/webasto-live.mdx | 7 + docs/devices-next/chargers/webasto-next.mdx | 8 + docs/devices-next/chargers/webasto-unite.mdx | 7 + .../chargers/weidmuller-ac-smart.mdx | 7 + docs/devices-next/chargers/wolf-bwl.mdx | 50 + docs/devices-next/chargers/wolf-bws.mdx | 50 + docs/devices-next/chargers/zaptec-go-2.mdx | 9 + docs/devices-next/chargers/zaptec-go-ocpp.mdx | 51 + docs/devices-next/chargers/zaptec-go.mdx | 9 + docs/devices-next/chargers/zaptec-pro.mdx | 9 + .../chargers/zewotherm-eu-l-series.mdx | 9 + .../chargers/zj-beny-bcp-ev-charger.mdx | 13 + docs/devices-next/meters/a-tronix.mdx | 9 + .../meters/abb-a43-a44-b23-b24.mdx | 62 - docs/devices-next/meters/abb-a43.mdx | 69 + docs/devices-next/meters/abb-a44.mdx | 69 + docs/devices-next/meters/abb-b23.mdx | 69 + docs/devices-next/meters/abb-b24.mdx | 69 + .../acrel-adw300-wireless-metering-meter.mdx | 102 - docs/devices-next/meters/acrel-adw300.mdx | 109 + docs/devices-next/meters/ads-tec-storaxe.mdx | 8 + .../meters/alpha-ess-storion-smile.mdx | 11 + .../meters/ampere-ampere-storagepro.mdx | 190 ++ .../meters/ampere-amperestoragepro.mdx | 179 - .../meters/anker-micro-inverter.mdx | 7 + docs/devices-next/meters/apsystems-ez1.mdx | 7 + docs/devices-next/meters/avm-fritzdect.mdx | 10 + .../meters/axitec-axihycon-12-15h.mdx | 9 + .../meters/bernecker-engineering-mpm3pm.mdx | 7 + docs/devices-next/meters/bgetech-ds100.mdx | 7 + docs/devices-next/meters/bgetech-ws100.mdx | 7 + .../meters/bosch-bpt-s-5-hybrid.mdx | 8 + .../meters/bosswerk-micro-inverter.mdx | 7 + .../meters/carlo-gavazzi-em110-111-112.mdx | 69 + .../meters/carlo-gavazzi-em110111112.mdx | 62 - .../meters/carlo-gavazzi-em24.mdx | 7 + .../meters/carlo-gavazzi-em24_e1.mdx | 59 + .../meters/carlo-gavazzi-em24e1.mdx | 52 - .../meters/carlo-gavazzi-em330-em340.mdx | 81 + .../meters/carlo-gavazzi-em330em340.mdx | 74 - .../meters/carlo-gavazzi-em530-em540.mdx | 81 + .../meters/carlo-gavazzi-em530em540.mdx | 74 - .../meters/carlo-gavazzi-et112.mdx | 7 + .../meters/carlo-gavazzi-et330-et340.mdx | 81 + .../meters/carlo-gavazzi-et330et340.mdx | 74 - .../meters/cfos-powerbrain-meter.mdx | 7 + docs/devices-next/meters/demo-battery.mdx | 13 + docs/devices-next/meters/demo-meter.mdx | 11 + .../meters/deye-3p-hybrid-inverter.mdx | 11 + .../meters/deye-hp3-hybrid-inverter.mdx | 13 + .../meters/deye-micro-inverter.mdx | 7 + .../meters/deye-storage-hybrid-inverter.mdx | 8 + .../meters/deye-string-inverter.mdx | 7 + docs/devices-next/meters/discovergy.mdx | 9 + docs/devices-next/meters/dsmr.mdx | 9 + docs/devices-next/meters/dzg-dvh4013.mdx | 7 + docs/devices-next/meters/e3-dc.mdx | 111 + docs/devices-next/meters/e3dc.mdx | 97 - .../meters/eastron-sdm120-modbus.mdx | 7 + .../meters/eastron-sdm220-230.mdx | 69 + .../devices-next/meters/eastron-sdm220230.mdx | 62 - .../meters/eastron-sdm630-modbus.mdx | 7 + docs/devices-next/meters/eastron-sdm72d-m.mdx | 7 + .../meters/eastron-sdm72dm-v2.mdx | 7 + docs/devices-next/meters/enphase-iq-envoy.mdx | 10 + .../meters/esphome-dlms-meter-austria.mdx | 8 + docs/devices-next/meters/esphome-dsmr.mdx | 8 + docs/devices-next/meters/fenecon.mdx | 12 + .../foxess-h1-series-hybrid-inverter.mdx | 7 + .../foxess-h3-series-hybrid-inverter.mdx | 11 + ...foxess-h3-smart-series-hybrid-inverter.mdx | 11 + docs/devices-next/meters/fronius-ohmpilot.mdx | 8 + .../meters/fronius-primo-gen24-plus.mdx | 12 + .../fronius-smartmeter-via-inverter.mdx | 7 + .../meters/fronius-solar-api-v1.mdx | 36 +- .../meters/fronius-symo-gen24-plus.mdx | 12 + ...nlong-solis-hybrid-inverter-rhi-series.mdx | 9 + ...ginlong-solis-hybrid-inverter-s-series.mdx | 9 + .../meters/ginlong-solis-inverter.mdx | 7 + docs/devices-next/meters/go-e-controller.mdx | 7 + .../goodwe-et-eh-bh-bt-hybrid-inverter.mdx | 165 + .../goodwe-etehbhbt-hybrid-inverter.mdx | 155 - .../meters/goodwe-goodwe-over-wifi.mdx | 7 + .../meters/goodwe-sdt-dt-inverter.mdx | 47 + .../meters/goodwe-sdtdt-inverter.mdx | 40 - .../meters/growatt-hybrid-inverter.mdx | 9 + .../meters/growatt-tl-x-h-hybrid-inverter.mdx | 159 + .../meters/growatt-tl-xh-hybrid-inverter.mdx | 150 - docs/devices-next/meters/homematic-ip.mdx | 12 + .../meters/homewizard-kwh-meter.mdx | 7 + .../meters/homewizard-wi-fi-p1-meter.mdx | 7 + ...hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 8 + ...hoymiles-hm-and-hms-series-via-opendtu.mdx | 7 + docs/devices-next/meters/huawei-emma.mdx | 8 + .../meters/huawei-smartlogger.mdx | 11 + .../meters/huawei-sun2000-sdongle.mdx | 8 + docs/devices-next/meters/huawei-sun2000.mdx | 13 + docs/devices-next/meters/iammeter-wem3080.mdx | 7 + .../iammeter-wem3080t-wem3046t-wem3050t.mdx | 59 + .../iammeter-wem3080twem3046twem3050t.mdx | 52 - .../meters/igen-tech-solarman-logger.mdx | 9 + docs/devices-next/meters/index.mdx | 656 +++- .../devices-next/meters/inepro-pro380-mod.mdx | 7 + docs/devices-next/meters/iometer.mdx | 7 + .../meters/janitza-b-series-umg-series.mdx | 74 - docs/devices-next/meters/janitza-b-series.mdx | 81 + .../meters/janitza-umg-series.mdx | 81 + .../meters/keba-kecontact-e10.mdx | 7 + .../meters/kostal-energy-meter-c-kem-c.mdx | 7 + .../meters/kostal-energy-meter-p-kem-p.mdx | 7 + docs/devices-next/meters/kostal-piko-ba.mdx | 45 + .../meters/kostal-piko-hybrid.mdx | 8 + .../meters/kostal-piko-legacy.mdx | 9 + .../meters/kostal-piko-mp-plus.mdx | 7 + .../meters/kostal-piko-piko-ba.mdx | 38 - docs/devices-next/meters/kostal-piko.mdx | 45 + ...ncl-grid-charging-of-the-house-battery.mdx | 12 + .../meters/kostal-plenticore-hybrid.mdx | 13 + ...kostal-smart-energy-meter-via-inverter.mdx | 7 + .../meters/kostal-smart-energy-meter.mdx | 7 + docs/devices-next/meters/lg-ess-home-15.mdx | 12 + docs/devices-next/meters/lg-ess-home-8-10.mdx | 94 + docs/devices-next/meters/lg-ess-home-810.mdx | 82 - .../devices-next/meters/loxone-miniserver.mdx | 11 + .../meters/m-tec-energy-butler-gen2.mdx | 7 + .../meters/m-tec-energy-butler-gen3.mdx | 8 + .../meters/marstek-venus-battery-storage.mdx | 12 + .../meters/mhendriks-p1-dongle.mdx | 8 + docs/devices-next/meters/my-pv-ac-elwa-2.mdx | 7 + docs/devices-next/meters/my-pv-ac-elwa-e.mdx | 7 + docs/devices-next/meters/my-pv-ac-thor.mdx | 29 + docs/devices-next/meters/my-pv-acthor.mdx | 22 - docs/devices-next/meters/my-pv-wifi-meter.mdx | 7 + docs/devices-next/meters/mystrom-switch.mdx | 7 + docs/devices-next/meters/openems.mdx | 12 + .../meters/orno-or-we-516-or-we-517.mdx | 62 - docs/devices-next/meters/orno-or-we-516.mdx | 69 + docs/devices-next/meters/orno-or-we-517.mdx | 69 + .../meters/p1monitor-p1-monitor.mdx | 29 + docs/devices-next/meters/p1monitor.mdx | 22 - docs/devices-next/meters/plexlog.mdx | 8 + docs/devices-next/meters/powerdog.mdx | 7 + .../meters/powerfox-poweropti.mdx | 9 + .../meters/qcells-hybrid-inverter-cloud.mdx | 23 +- .../meters/qcells-q-home-ess-hyb-g3.mdx | 195 ++ .../meters/qcells-qhome-ess-hyb-g3.mdx | 183 - docs/devices-next/meters/rct-power.mdx | 13 + .../saia-burgess-controls-ale3-awd3.mdx | 62 - .../meters/saia-burgess-controls-sbc-ale3.mdx | 69 + .../meters/saia-burgess-controls-sbc-awd3.mdx | 69 + .../saj-h1-series-hybrid-solar-inverter.mdx | 9 + .../saj-h2-series-hybrid-solar-inverter.mdx | 11 + .../meters/saj-r5-series-solar-inverter.mdx | 7 + docs/devices-next/meters/sax-homespeicher.mdx | 7 + .../schneider-electric-iem3xxx-modbus.mdx | 7 + docs/devices-next/meters/senec-home.mdx | 9 + .../senergy-se-4-5-6ktl-s1-g2-inverter.mdx | 34 + .../senergy-se-456ktl-s1g2-inverter.mdx | 27 - ...pm-em-plug-s-pro-3em-in-monophase-mode.mdx | 57 - docs/devices-next/meters/shelly-1pm-mini.mdx | 67 + docs/devices-next/meters/shelly-1pm.mdx | 67 + docs/devices-next/meters/shelly-3em.mdx | 9 + docs/devices-next/meters/shelly-em.mdx | 67 + docs/devices-next/meters/shelly-plug-s.mdx | 67 + docs/devices-next/meters/shelly-pm-mini.mdx | 67 + docs/devices-next/meters/shelly-pro-1pm.mdx | 67 + docs/devices-next/meters/shelly-pro-3-em.mdx | 9 + .../meters/shelly-pro-3em-monophase-mode.mdx | 67 + docs/devices-next/meters/shelly-pro-em.mdx | 67 + docs/devices-next/meters/siemens-7kt1665.mdx | 7 + .../siemens-junelight-smart-battery.mdx | 8 + docs/devices-next/meters/siemens-pac-2200.mdx | 7 + ...igen-hybrid-sigen-pv-max-sigenstore-ec.mdx | 75 + ...-sigen-hybridsigen-pv-maxsigenstore-ec.mdx | 65 - docs/devices-next/meters/sma-data-manager.mdx | 8 + docs/devices-next/meters/sma-energy-meter.mdx | 8 + .../meters/sma-inverter-speedwire.mdx | 9 + .../sma-smart-energy-hybrid-inverter.mdx | 11 + ...a-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx | 50 + .../sma-sunny-boy-storage-152025-modbus.mdx | 40 - ...a-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx | 50 + .../sma-sunny-boy-storage-375060-modbus.mdx | 40 - .../meters/sma-sunny-home-manager-2-0.mdx | 36 + .../meters/sma-sunny-home-manager-20.mdx | 28 - .../meters/sma-sunny-island-modbus.mdx | 10 + docs/devices-next/meters/sma-webbox.mdx | 7 + .../meters/sma-wechselrichter-modbus.mdx | 7 + .../meters/smartfox-box-reg-reg-extended.mdx | 51 - docs/devices-next/meters/smartfox-box.mdx | 58 + .../meters/smartfox-light-em2-firmware.mdx | 77 + docs/devices-next/meters/smartfox-pro-2.mdx | 77 + .../meters/smartfox-pro-light-2.mdx | 77 + .../meters/smartfox-pro-light.mdx | 77 + ...o-light-pro-light-2-light-em2-firmware.mdx | 69 - docs/devices-next/meters/smartfox-pro.mdx | 77 + .../meters/smartfox-reg-extended.mdx | 58 + docs/devices-next/meters/smartfox-reg.mdx | 58 + .../meters/sofarsolar-hybrid-inverter.mdx | 134 + .../meters/sofarsolar-hyd-3-6k-ep.mdx | 191 ++ .../meters/sofarsolar-hyd-36k-ep.mdx | 180 - .../meters/sofarsolar-hyd-5-20k-3ph.mdx | 191 ++ .../meters/sofarsolar-hyd-520k-3ph.mdx | 180 - .../sofarsolar-inverter-hybrid-inverter.mdx | 126 - .../meters/sofarsolar-inverter.mdx | 134 + .../meters/sofarsolar-sofar-5-24ktl-g3.mdx | 191 ++ .../meters/sofarsolar-sofar-524ktl-g3.mdx | 180 - .../meters/sofarsolar-sofar-80-136ktl.mdx | 191 ++ .../meters/sofarsolar-sofar-80136ktl.mdx | 180 - .../meters/solaranzeige-solaranzeige.mdx | 76 + docs/devices-next/meters/solaranzeige.mdx | 64 - .../meters/solaredge-hybrid-inverter.mdx | 11 + .../meters/solaredge-inverter.mdx | 8 + docs/devices-next/meters/solarlog.mdx | 8 + ...armax-max-storage-max-storage-ultimate.mdx | 111 + ...olarmax-maxstorage-maxstorage-ultimate.mdx | 101 - .../meters/solarmax-solarmax-smt.mdx | 7 + .../meters/solarmax-sp-series-inverter.mdx | 7 + ...arwatt-energymanager-energymanager-pro.mdx | 54 - .../meters/solarwatt-energymanager-pro.mdx | 62 + .../meters/solarwatt-energymanager.mdx | 62 + .../meters/solarwatt-manager-flex.mdx | 8 + ...myreserve-matrix-lan-oder-powergateway.mdx | 9 + .../meters/solarwatt-myreserve.mdx | 8 + .../meters/solax-hybrid-inverter-cloud.mdx | 9 + .../meters/solax-hybrid-x1-x3-g3-g4.mdx | 195 ++ .../meters/solax-hybrid-x1x3-g3g4.mdx | 183 - .../meters/solax-inverter-cloud.mdx | 8 + docs/devices-next/meters/solinteng.mdx | 9 + .../sonnen-comfort-eco-5-eco-6-oem-65.mdx | 74 - docs/devices-next/meters/sonnen-comfort.mdx | 85 + docs/devices-next/meters/sonnen-eco-5.mdx | 85 + docs/devices-next/meters/sonnen-eco-6.mdx | 85 + docs/devices-next/meters/sonnen-oem-6-5.mdx | 85 + .../meters/sonnen-sonnenbatterie.mdx | 12 + docs/devices-next/meters/st-ems.mdx | 9 + .../meters/steca-coolcept-flex.mdx | 7 + .../meters/sungrow-sg-series-inverter.mdx | 7 + .../sungrow-sh-series-hybrid-inverter.mdx | 11 + .../meters/sunspec-battery-model-124.mdx | 9 + .../meters/sunspec-battery-model-802.mdx | 10 + .../meters/sunspec-hybrid-inverter.mdx | 9 + docs/devices-next/meters/sunspec-inverter.mdx | 8 + docs/devices-next/meters/sunspec-meter.mdx | 7 + .../meters/sunsynk-3p-hybrid-inverter.mdx | 11 + .../meters/sunsynk-hp3-hybrid-inverter.mdx | 13 + .../meters/sunsynk-micro-inverter.mdx | 7 + .../sunsynk-storage-hybrid-inverter.mdx | 8 + .../meters/sunsynk-string-inverter.mdx | 7 + docs/devices-next/meters/sunway.mdx | 9 + ...ml-ir-reader-for-smartmeters-e-g-hichi.mdx | 100 + ...sml-ir-reader-for-smartmeters-eg-hichi.mdx | 91 - ...tasmota-tasmota-1-phase-plus-sml-meter.mdx | 80 + .../tasmota-tasmota-1-phase-sml-meter.mdx | 70 - .../meters/tasmota-three-phase.mdx | 9 + docs/devices-next/meters/tesla-powerwall.mdx | 12 + docs/devices-next/meters/tibber-pulse.mdx | 8 + .../meters/tp-link-h-series-smart-plug.mdx | 7 + .../tp-link-tapo-p-series-smart-plug.mdx | 9 + .../meters/tq-energy-manager-em2xx-em3xx.mdx | 33 + .../meters/tq-energy-manager-em2xxem3xx.mdx | 24 - .../meters/tq-energy-manager-em420.mdx | 10 + docs/devices-next/meters/varta-element.mdx | 70 + docs/devices-next/meters/varta-pulse-neo.mdx | 70 + .../meters/varta-pulse-pulse-neo-element.mdx | 61 - docs/devices-next/meters/varta-pulse.mdx | 70 + docs/devices-next/meters/victron-em24.mdx | 7 + docs/devices-next/meters/victron-em24_e1.mdx | 59 + docs/devices-next/meters/victron-em24e1.mdx | 52 - .../meters/victron-em530-em540.mdx | 81 + .../meters/victron-em530em540.mdx | 74 - docs/devices-next/meters/victron-energy.mdx | 13 + docs/devices-next/meters/victron-et340.mdx | 7 + ...volkszahler-http-api-import-and-export.mdx | 9 + .../meters/volkszahler-http-api.mdx | 8 + .../meters/volkszahler-websocket-api.mdx | 9 + docs/devices-next/meters/vzlogger.mdx | 20 + docs/devices-next/meters/wago-879-30xx.mdx | 7 + docs/devices-next/meters/wattsonic.mdx | 9 + .../meters/weidmuller-em110-rtu-2p.mdx | 7 + .../meters/weidmuller-em111-rtu-2p.mdx | 7 + .../meters/weidmuller-em120-rtu-2p.mdx | 7 + .../meters/weidmuller-em122-rtu-2p.mdx | 7 + .../meters/youless-energy-monitor.mdx | 7 + .../meters/zcs-azzurro-hybrid-inverter.mdx | 134 + .../zcs-azzurro-inverter-hybrid-inverter.mdx | 126 - .../meters/zcs-azzurro-inverter.mdx | 134 + .../meters/zendure-hyper-2000.mdx | 11 + .../zuidwijk-slimmelezer-in-luxembourg.mdx | 25 - ...uidwijk-slimmelezer-plus-in-luxembourg.mdx | 32 + .../meters/zuidwijk-slimmelezer-plus-v2.mdx | 32 + .../meters/zuidwijk-slimmelezer-plus.mdx | 36 + .../meters/zuidwijk-slimmelezer-v2.mdx | 25 - .../meters/zuidwijk-slimmelezer.mdx | 28 - docs/devices-next/tariffs/amber-electric.mdx | 12 + docs/devices-next/tariffs/awattar.mdx | 10 + .../electricity-maps-commercial-api.mdx | 9 + .../tariffs/electricity-maps-free-api.mdx | 8 + docs/devices-next/tariffs/energinet.mdx | 10 + docs/devices-next/tariffs/enever.mdx | 12 + docs/devices-next/tariffs/entso-e.mdx | 11 + docs/devices-next/tariffs/forecast-solar.mdx | 53 + docs/devices-next/tariffs/forecastsolar.mdx | 39 - docs/devices-next/tariffs/fraunhofer-ise.mdx | 10 + .../tariffs/green-grid-compass.mdx | 8 + .../tariffs/groupe-e-vario-plus.mdx | 9 + docs/devices-next/tariffs/grunstromindex.mdx | 8 + docs/devices-next/tariffs/index.mdx | 6 +- .../tariffs/national-grid-eso.mdx | 8 + .../tariffs/nordpool-spot-prices.mdx | 11 + .../tariffs/octopus-energy-api.mdx | 8 + .../tariffs/octopus-energy-product-code.mdx | 9 + docs/devices-next/tariffs/open-meteo.mdx | 18 + docs/devices-next/tariffs/ostrom.mdx | 9 + docs/devices-next/tariffs/pun-orario.mdx | 9 + .../tariffs/smartenergy-smartcontrol.mdx | 9 + docs/devices-next/tariffs/solcast.mdx | 11 + docs/devices-next/tariffs/spotty-energie.mdx | 11 + docs/devices-next/tariffs/tibber.mdx | 11 + .../tariffs/victron-vrm-solar-forecast.mdx | 9 + docs/devices-next/vehicles/aiways.mdx | 19 + docs/devices-next/vehicles/audi.mdx | 19 + docs/devices-next/vehicles/bmw.mdx | 25 +- docs/devices-next/vehicles/citroen.mdx | 20 + docs/devices-next/vehicles/dacia.mdx | 23 +- docs/devices-next/vehicles/ds.mdx | 20 + docs/devices-next/vehicles/evnotify.mdx | 17 + docs/devices-next/vehicles/fiat.mdx | 24 +- docs/devices-next/vehicles/ford.mdx | 21 + .../vehicles/generic-vehicle-without-api.mdx | 15 + .../vehicles/hyundai-bluelink.mdx | 20 + docs/devices-next/vehicles/index.mdx | 12 +- docs/devices-next/vehicles/iobroker-bmw.mdx | 62 + docs/devices-next/vehicles/iobrokerbmw.mdx | 42 - docs/devices-next/vehicles/iso15118.mdx | 15 + docs/devices-next/vehicles/jeep.mdx | 24 +- docs/devices-next/vehicles/kia-bluelink.mdx | 20 + docs/devices-next/vehicles/mercedes-benz.mdx | 21 + docs/devices-next/vehicles/mg.mdx | 20 + docs/devices-next/vehicles/mg2mqtt.mdx | 18 + docs/devices-next/vehicles/mini.mdx | 25 +- docs/devices-next/vehicles/mz2mqtt.mdx | 17 + docs/devices-next/vehicles/nissan-ariya.mdx | 19 + .../vehicles/nissan-leaf-pre-2019.mdx | 19 + docs/devices-next/vehicles/nissan-leaf.mdx | 19 + docs/devices-next/vehicles/niu-e-scooter.mdx | 12 + docs/devices-next/vehicles/opel.mdx | 20 + .../open-vehicle-monitoring-system.mdx | 20 + docs/devices-next/vehicles/peugeot.mdx | 20 + docs/devices-next/vehicles/polestar.mdx | 19 + .../vehicles/psa-car-controller.mdx | 18 + docs/devices-next/vehicles/renault.mdx | 20 + ...nect-gen3-ateca-leon-formentor-tarraco.mdx | 19 + ...raconnect-gen4-born-formentor-tavascan.mdx | 23 +- docs/devices-next/vehicles/skoda-enyaq.mdx | 20 + docs/devices-next/vehicles/smart-1.mdx | 62 + docs/devices-next/vehicles/smart-eq.mdx | 21 + docs/devices-next/vehicles/smart.mdx | 41 - docs/devices-next/vehicles/tesla-ble.mdx | 18 + docs/devices-next/vehicles/tesla.mdx | 22 + docs/devices-next/vehicles/teslalogger.mdx | 18 + docs/devices-next/vehicles/teslamate.mdx | 16 + docs/devices-next/vehicles/tessie.mdx | 17 + docs/devices-next/vehicles/toyota.mdx | 19 + docs/devices-next/vehicles/tronity.mdx | 19 + .../vehicles/volkswagen-we-connect-id.mdx | 26 +- docs/devices-next/vehicles/volvo.mdx | 20 + docs/devices-next/vehicles/volvo2mqtt.mdx | 17 + .../vehicles/zero-motorcycles.mdx | 19 + docs/devices/chargers.mdx | 348 +- docs/devices/meters.mdx | 3014 +++++++++++++---- docs/devices/smartswitches.mdx | 85 +- docs/devices/vehicles.mdx | 28 +- .../chargers/abb-terra-ac-ocpp.mdx | 49 + .../devices-next/chargers/abb-terra-ac.mdx | 45 +- .../devices-next/chargers/abl-em4-sbcx.mdx | 38 - .../chargers/abl-em4-single-ocpp.mdx | 46 + .../chargers/abl-em4-single-sbcx.mdx | 46 + .../chargers/abl-em4-twin-ocpp.mdx | 46 + .../chargers/abl-em4-twin-sbcx.mdx | 46 + .../devices-next/chargers/abl-emh1.mdx | 8 + .../devices-next/chargers/abl-emh2-ocpp.mdx | 46 + .../devices-next/chargers/abl-emh2.mdx | 8 + .../devices-next/chargers/abl-emh3-ocpp.mdx | 46 + .../devices-next/chargers/abl-sursum-emh2.mdx | 33 - .../devices-next/chargers/abl-sursum-emh3.mdx | 33 - .../devices-next/chargers/abl-sursum-emh4.mdx | 33 - .../devices-next/chargers/alfen-eve-ocpp.mdx | 46 + .../devices-next/chargers/alfen-eve.mdx | 33 +- .../devices-next/chargers/alpha-innotec.mdx | 50 + .../chargers/alphatec-ladesaule-twin.mdx | 7 + .../chargers/alphatec-wallbox-mini-power.mdx | 38 - .../chargers/alphatec-wallbox-mini.mdx | 45 + .../chargers/alphatec-wallbox-power.mdx | 45 + .../amperfied-wallbox-connect-business.mdx | 35 + .../amperfied-wallbox-connect-home.mdx | 35 + .../amperfied-wallbox-connect-solar.mdx | 35 + .../amperfied-wallbox-connectbusiness.mdx | 28 - .../amperfied-wallbox-connecthome.mdx | 28 - .../amperfied-wallbox-connectsolar.mdx | 28 - .../amperfied-wallbox-energy-control.mdx | 7 + .../devices-next/chargers/ampure-live.mdx | 31 - .../devices-next/chargers/ampure-next.mdx | 8 + .../devices-next/chargers/ampure-unite.mdx | 7 + .../chargers/audi-audi-wallbox-pro.mdx | 29 - .../chargers/audi-wallbox-plus.mdx | 8 + .../chargers/audi-wallbox-pro.mdx | 37 + .../chargers/autel-ac-compact.mdx | 13 + .../chargers/autel-ac-maxicharger.mdx | 13 + .../chargers/autoaid-business-wallbox.mdx | 13 + .../chargers/autoaid-intelligent-wallbox.mdx | 13 + .../devices-next/chargers/avm-fritzdect.mdx | 14 + .../devices-next/chargers/bender-cc612.mdx | 7 + .../devices-next/chargers/bender-cc613.mdx | 7 + .../devices-next/chargers/bender-icc1314.mdx | 7 + .../devices-next/chargers/bender-icc1324.mdx | 7 + .../devices-next/chargers/bmw-i-wallbox.mdx | 8 + .../devices-next/chargers/bosch-sg-ready.mdx | 10 + .../devices-next/chargers/bosch-x-change.mdx | 9 + .../chargers/buderus-logamatic-hmc-20-z.mdx | 50 + .../chargers/buderus-logamatic-hmc-20.mdx | 50 + .../chargers/buderus-sg-ready.mdx | 10 + .../chargers/cfos-power-brain-solar.mdx | 7 + .../chargers/cfos-power-brain.mdx | 7 + .../chargers/charge-amps-halo.mdx | 13 + .../devices-next/chargers/compleo-ebox.mdx | 7 + .../chargers/cta-all-in-one-aeroplus.mdx | 50 + .../devices-next/chargers/cubos-c11e-c22e.mdx | 31 - .../devices-next/chargers/cubos-c11e.mdx | 38 + .../devices-next/chargers/cubos-c22e.mdx | 38 + .../chargers/cupra-charger-connect-2.mdx | 8 + .../chargers/cupra-charger-connect.mdx | 8 + .../chargers/cupra-charger-pro-2.mdx | 8 + .../cupra-charger-pro-eichrecht-2.mdx | 8 + .../chargers/cupra-charger-pro.mdx | 8 + .../chargers/dadapower-premium-wallbox.mdx | 7 + .../chargers/daheimladen-wallbox.mdx | 8 + .../chargers/daikin-homehub-sg-ready.mdx | 8 + .../chargers/delta-ac-max-basic.mdx | 8 + .../chargers/delta-ac-max-smart.mdx | 8 + .../chargers/delta-slim-charger.mdx | 8 + .../chargers/delta-ultra-fast-charger.mdx | 8 + .../devices-next/chargers/demo-charger.mdx | 11 + .../devices-next/chargers/e-on-drive-ebox.mdx | 35 + .../devices-next/chargers/e-on-drive-vbox.mdx | 38 + .../chargers/e3-dc-easy-connect.mdx | 38 + .../chargers/e3dc-easy-connect.mdx | 31 - .../chargers/easee-charge-core.mdx | 11 + .../chargers/easee-charge-lite.mdx | 11 + .../devices-next/chargers/easee-charge.mdx | 11 + .../devices-next/chargers/easee-home.mdx | 11 + .../devices-next/chargers/ebee-wallbox.mdx | 7 + .../devices-next/chargers/echarge-cph1.mdx | 8 + .../chargers/echarge-cph2-cpm2.mdx | 23 - .../devices-next/chargers/echarge-cph2.mdx | 30 + .../devices-next/chargers/echarge-cpm2.mdx | 30 + .../chargers/ecoharmony-evse-epc-2-0-plus.mdx | 46 + .../chargers/ecoharmony-evse-epc-20-plus.mdx | 39 - .../chargers/edgetech-smart-evse.mdx | 7 + .../chargers/eebus-compatible.mdx | 8 + .../current/devices-next/chargers/elco.mdx | 50 + .../devices-next/chargers/elecq-biz.mdx | 13 + .../devices-next/chargers/elecq-home.mdx | 13 + .../devices-next/chargers/elecq-station.mdx | 13 + .../devices-next/chargers/eledio-go.mdx | 13 + .../chargers/elli-charger-connect-2.mdx | 8 + .../chargers/elli-charger-connect.mdx | 8 + .../chargers/elli-charger-pro-2.mdx | 8 + .../chargers/elli-charger-pro-eichrecht-2.mdx | 8 + .../chargers/elli-charger-pro.mdx | 8 + .../devices-next/chargers/em2go-home.mdx | 7 + .../chargers/em2go-pro-power-ocpp-onc.mdx | 36 + .../chargers/em2go-pro-power-ocpponc.mdx | 29 - .../chargers/en-ac-ev-charger.mdx | 33 - .../devices-next/chargers/enercab-smart.mdx | 13 + .../chargers/enplus-ac-ev-charger.mdx | 46 + .../chargers/ensto-chago-wallbox.mdx | 7 + .../chargers/entratek-power-dot-fix.mdx | 13 + .../chargers/entratek-power-dot-pro-2.mdx | 13 + .../devices-next/chargers/eon-drive-ebox.mdx | 28 - .../devices-next/chargers/eon-drive-vbox.mdx | 31 - .../devices-next/chargers/esl-walli-light.mdx | 7 + .../chargers/esystems-ghostone.mdx | 8 + .../devices-next/chargers/etrel-inch-duo.mdx | 9 + .../devices-next/chargers/etrel-inch.mdx | 8 + .../devices-next/chargers/evbox-elvi.mdx | 13 + .../devices-next/chargers/evbox-livo.mdx | 8 + .../devices-next/chargers/evse-din.mdx | 7 + .../devices-next/chargers/evse-wifi.mdx | 7 + .../chargers/free2move-eprowallbox-move.mdx | 42 + .../chargers/free2move-eprowallbox.mdx | 7 + .../free2move-esolutions-eprowallbox.mdx | 13 + .../chargers/fronius-wattpilot-ocpp.mdx | 46 + .../chargers/fronius-wattpilot.mdx | 33 - .../chargers/garo-glb-glb-ls4-ls4-compact.mdx | 31 - .../devices-next/chargers/garo-glb.mdx | 38 + .../devices-next/chargers/garo-glbplus.mdx | 38 + .../chargers/garo-ls4-compact.mdx | 38 + .../devices-next/chargers/garo-ls4.mdx | 38 + .../chargers/go-e-charger-gemini-ocpp.mdx | 46 + .../chargers/go-e-charger-gemini.mdx | 30 +- .../chargers/go-e-charger-home.mdx | 28 - .../chargers/go-e-charger-homefix.mdx | 7 + .../chargers/go-e-charger-homeplus.mdx | 35 + .../chargers/go-e-charger-pro-ocpp.mdx | 46 + .../chargers/go-e-charger-pro.mdx | 28 +- .../chargers/go-e-charger-v3-ocpp.mdx | 46 + .../devices-next/chargers/go-e-charger-v3.mdx | 30 +- .../chargers/hardy-barth-cph1.mdx | 39 + .../chargers/hardy-barth-cph2.mdx | 30 + .../chargers/hardy-barth-cpm2.mdx | 30 + .../devices-next/chargers/hardybarth-cph1.mdx | 31 - .../chargers/hardybarth-cph2-cpm2.mdx | 23 - .../chargers/heidelberg-energy-control.mdx | 7 + .../devices-next/chargers/hesotec-ebox.mdx | 35 + .../chargers/hesotec-esat-ebox.mdx | 28 - .../devices-next/chargers/hesotec-esat.mdx | 35 + .../chargers/home-assistant-switch.mdx | 14 + .../chargers/homecharge-homecharger.mdx | 13 + .../devices-next/chargers/homematic-ip.mdx | 18 + .../devices-next/chargers/homewizard.mdx | 11 + .../chargers/huawei-scharger-22kt-s0.mdx | 46 + .../huawei-scharger-7ks-s0-22kt-s0.mdx | 33 - .../chargers/huawei-scharger-7ks-s0.mdx | 46 + .../current/devices-next/chargers/idm.mdx | 8 + .../current/devices-next/chargers/index.mdx | 880 +++-- .../devices-next/chargers/innogy-ebox.mdx | 7 + .../devices-next/chargers/inro-pantabox.mdx | 7 + .../chargers/juice-charger-me.mdx | 7 + .../chargers/junkers-sg-ready.mdx | 10 + ...-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx | 31 - .../chargers/kathrein-kwb-ac20.mdx | 38 + .../chargers/kathrein-kwb-ac35.mdx | 38 + .../chargers/kathrein-kwb-ac40-e.mdx | 38 + .../chargers/kathrein-kwb-ac40.mdx | 38 + .../chargers/kathrein-kwb-ac60-e.mdx | 38 + .../chargers/kathrein-kwb-ac60.mdx | 38 + .../keba-kecontact-p20-p30-cx-series.mdx | 41 - .../chargers/keba-kecontact-p20.mdx | 49 + .../chargers/keba-kecontact-p30-c-series.mdx | 49 + .../chargers/keba-kecontact-p30-x-series.mdx | 49 + .../chargers/keba-kecontact-p40-p40-pro.mdx | 41 - .../chargers/keba-kecontact-p40-pro.mdx | 49 + .../chargers/keba-kecontact-p40.mdx | 49 + .../chargers/kermi-x-center-pro.mdx | 9 + .../chargers/kontron-solar-charger.mdx | 8 + .../devices-next/chargers/kostal-enector.mdx | 7 + .../devices-next/chargers/kse-wbx16.mdx | 7 + .../chargers/ladefoxx-evload-mikro-20.mdx | 36 - .../devices-next/chargers/ladefoxx-evload.mdx | 44 + .../chargers/ladefoxx-mikro-2-0.mdx | 44 + .../chargers/lambda-eu-l-series.mdx | 9 + .../chargers/lrt-home-essential.mdx | 38 - .../chargers/lrt-home-essentialplus.mdx | 45 + .../chargers/mennekes-amedio-professional.mdx | 7 + .../mennekes-amtron-4business-700.mdx | 7 + .../chargers/mennekes-amtron-4you-300.mdx | 7 + .../chargers/mennekes-amtron-4you-500.mdx | 7 + .../mennekes-amtron-chargecontrol.mdx | 7 + .../chargers/mennekes-amtron-compact-2-0s.mdx | 47 + .../chargers/mennekes-amtron-compact-20s.mdx | 40 - .../chargers/mennekes-amtron-premium.mdx | 7 + .../chargers/mennekes-amtron-professional.mdx | 7 + .../chargers/mennekes-amtron-xtra.mdx | 7 + .../mennekes-emobility-gateway-acu.mdx | 13 + .../chargers/mennekes-smart-acu.mdx | 13 + .../chargers/mennekes-smart-t-acu.mdx | 13 + .../devices-next/chargers/my-pv-ac-elwa-2.mdx | 8 + .../chargers/my-pv-ac-thor-9s.mdx | 39 + .../chargers/my-pv-ac-thor-ac-thor-9s.mdx | 30 - .../devices-next/chargers/my-pv-ac-thor.mdx | 39 + .../devices-next/chargers/mystrom-switch.mdx | 11 + .../devices-next/chargers/nibe-ap-aw10.mdx | 50 + .../devices-next/chargers/novelan-wpr-net.mdx | 50 + .../devices-next/chargers/nrgkick-connect.mdx | 13 +- .../devices-next/chargers/nrgkick-gen2.mdx | 12 +- .../chargers/obo-bettermann-ion.mdx | 7 + .../ocpp-1-6j-compatible-smart-charging.mdx | 67 + .../ocpp-16j-compatible-smart-charging.mdx | 54 - .../devices-next/chargers/openevse.mdx | 9 + .../devices-next/chargers/openwb-pro.mdx | 7 + .../devices-next/chargers/openwb-series2.mdx | 9 + .../chargers/openwb-software-2-x.mdx | 53 + .../chargers/openwb-software-2x.mdx | 44 - .../chargers/optec-mobility-one.mdx | 7 + .../devices-next/chargers/orbis-viaris.mdx | 13 + .../chargers/pc-electric-garo.mdx | 8 + .../devices-next/chargers/peblar-business.mdx | 38 + .../peblar-home-home-plus-business.mdx | 31 - .../chargers/peblar-home-plus.mdx | 38 + .../devices-next/chargers/peblar-home.mdx | 38 + .../chargers/phoenix-contact-charx.mdx | 8 + .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 7 + ...ix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 7 + ...oenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 7 + ...nix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 7 + ...hoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 7 + .../chargers/phoenix-contact-ev-ser.mdx | 7 + .../devices-next/chargers/plugchoice.mdx | 9 + .../porsche-mobile-charger-connect.mdx | 8 + .../chargers/porsche-mobile-charger-plus.mdx | 8 + .../devices-next/chargers/porsche-wallbox.mdx | 8 + .../devices-next/chargers/pracht-alpha-xt.mdx | 9 + .../devices-next/chargers/pracht-mono-xt.mdx | 9 + .../devices-next/chargers/pracht-pni.mdx | 9 + .../devices-next/chargers/pracht-xt.mdx | 66 - .../devices-next/chargers/pracht-xtplus.mdx | 75 + .../chargers/pulsares-simplebox.mdx | 7 + .../devices-next/chargers/pulsatrix.mdx | 7 + .../chargers/qcells-q-home-edrive-a.mdx | 45 + .../chargers/qcells-qhome-edrive-a.mdx | 38 - .../devices-next/chargers/roth-thermoaura.mdx | 50 + .../chargers/roth-thermoterra.mdx | 50 + .../chargers/schneider-evlink-pro.mdx | 7 + .../chargers/schrack-i-charge-cion.mdx | 7 + .../chargers/senec-wallbox-pro-s.mdx | 7 + .../chargers/senec-wallbox-pro.mdx | 8 + .../devices-next/chargers/shelly-1.mdx | 50 + .../devices-next/chargers/shelly-plug-s.mdx | 50 + .../devices-next/chargers/shelly-plus-1.mdx | 50 + .../devices-next/chargers/shelly-pro-1.mdx | 50 + .../current/devices-next/chargers/shelly.mdx | 36 - .../chargers/siemens-versicharge-gen3.mdx | 7 + .../chargers/skoda-charger-connect.mdx | 8 + .../chargers/skoda-charger-pro-eichrecht.mdx | 8 + .../chargers/skoda-charger-pro.mdx | 8 + .../chargers/skoda-iv-charger-connect.mdx | 18 +- .../chargers/skoda-iv-charger-connectplus.mdx | 37 + .../devices-next/chargers/sma-echarger.mdx | 37 + .../chargers/sma-ev-charger-echarger.mdx | 28 - .../devices-next/chargers/sma-ev-charger.mdx | 37 + .../chargers/smartfox-pro-charger.mdx | 7 + .../current/devices-next/chargers/smartwb.mdx | 7 + .../chargers/solaredge-home-ev-charger.mdx | 8 + .../devices-next/chargers/solax-x3-evc.mdx | 7 + .../chargers/sonnen-sonnencharger.mdx | 8 + .../chargers/spelsberg-wallbox-smart-pro.mdx | 7 + .../chargers/stark-in-strom-easy.mdx | 7 + .../stiebel-eltron-lwa-lwz-sg-ready.mdx | 35 + .../stiebel-eltron-lwalwz-sg-ready.mdx | 27 - .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 8 + .../chargers/sungrow-ac011e-01.mdx | 7 + .../devices-next/chargers/sungrow-ac011e.mdx | 13 + .../chargers/sungrow-ac22e-01.mdx | 48 + .../chargers/tasmota-single-phase.mdx | 14 + .../chargers/tecalor-thz-sg-ready.mdx | 8 + .../chargers/technisat-technivolt.mdx | 7 + .../devices-next/chargers/tesla-twc3.mdx | 24 - .../chargers/tesla-wall-connector-gen-3.mdx | 31 + .../current/devices-next/chargers/tessie.mdx | 9 + .../chargers/tigo-go-ev-charger.mdx | 7 + .../chargers/tinkerforge-warp-charger-pro.mdx | 13 + .../tinkerforge-warp-charger-smart.mdx | 13 + .../tinkerforge-warp3-charger-pro.mdx | 12 + .../tinkerforge-warp3-charger-smart.mdx | 12 + .../chargers/tp-link-h-series-smart-plug.mdx | 11 + .../tp-link-tapo-p-series-smart-plug.mdx | 13 + .../chargers/ubitricity-heinz.mdx | 7 + .../devices-next/chargers/v2c-trydan.mdx | 7 + .../chargers/vaillant-sensonet-sg-ready.mdx | 11 + .../chargers/vestel-connect-plus.mdx | 38 + .../vestel-evc04-home-smart-connect-plus.mdx | 31 - .../chargers/vestel-evc04-home-smart.mdx | 38 + .../victron-ev-charging-station-via-gx.mdx | 7 + .../chargers/victron-ev-charging-station.mdx | 7 + .../chargers/viessmann-heatpump-sg-ready.mdx | 15 +- .../viridian-ev-evse-epc-2-0-plus.mdx | 46 + .../chargers/viridian-ev-evse-epc-20-plus.mdx | 39 - .../chargers/volkswagen-charger-connect-2.mdx | 8 + .../chargers/volkswagen-charger-pro-2.mdx | 8 + .../volkswagen-charger-pro-eichrecht-2.mdx | 8 + .../volkswagen-id-charger-connect.mdx | 8 + .../chargers/volkswagen-id-charger-pro.mdx | 8 + .../devices-next/chargers/volt-time-one.mdx | 8 + .../chargers/volt-time-source-2.mdx | 8 + .../chargers/volt-time-source-2s.mdx | 8 + .../chargers/volt-time-source.mdx | 8 + .../chargers/wallbe-eco-2-0-s.mdx | 38 + .../devices-next/chargers/wallbe-eco-20s.mdx | 31 - .../devices-next/chargers/wallbe-eco.mdx | 7 + .../devices-next/chargers/wallbe-pro.mdx | 7 + .../chargers/wallbox-commander-2-fw-5-x.mdx | 55 + .../chargers/wallbox-commander-2-fw-5x.mdx | 42 - .../chargers/wallbox-commander-2.mdx | 13 + .../chargers/wallbox-copper-sb-fw-5-x.mdx | 55 + .../chargers/wallbox-copper-sb-fw-5x.mdx | 42 - .../chargers/wallbox-copper-sb.mdx | 13 + .../chargers/wallbox-pulsar-max-fw-5-x.mdx | 55 + .../chargers/wallbox-pulsar-max-fw-5x.mdx | 42 - .../chargers/wallbox-pulsar-max.mdx | 13 + .../chargers/wallbox-pulsar-plus-fw-5-x.mdx | 55 + .../chargers/wallbox-pulsar-plus-fw-5x.mdx | 42 - .../chargers/wallbox-pulsar-plus.mdx | 13 + .../chargers/walther-werke-basic-evo-pro.mdx | 7 + .../devices-next/chargers/webasto-live.mdx | 7 + .../devices-next/chargers/webasto-next.mdx | 8 + .../devices-next/chargers/webasto-unite.mdx | 7 + .../chargers/weidmuller-ac-smart.mdx | 7 + .../devices-next/chargers/wolf-bwl.mdx | 50 + .../devices-next/chargers/wolf-bws.mdx | 50 + .../devices-next/chargers/zaptec-go-2.mdx | 9 + .../devices-next/chargers/zaptec-go-ocpp.mdx | 51 + .../devices-next/chargers/zaptec-go.mdx | 9 + .../devices-next/chargers/zaptec-pro.mdx | 9 + .../chargers/zewotherm-eu-l-series.mdx | 9 + .../chargers/zj-beny-bcp-ev-charger.mdx | 13 + .../current/devices-next/meters/a-tronix.mdx | 9 + .../meters/abb-a43-a44-b23-b24.mdx | 62 - .../current/devices-next/meters/abb-a43.mdx | 69 + .../current/devices-next/meters/abb-a44.mdx | 69 + .../current/devices-next/meters/abb-b23.mdx | 69 + .../current/devices-next/meters/abb-b24.mdx | 69 + .../acrel-adw300-wireless-metering-meter.mdx | 102 - .../devices-next/meters/acrel-adw300.mdx | 109 + .../devices-next/meters/ads-tec-storaxe.mdx | 8 + .../meters/alpha-ess-storion-smile.mdx | 11 + .../meters/ampere-ampere-storagepro.mdx | 190 ++ .../meters/ampere-amperestoragepro.mdx | 179 - .../meters/anker-micro-inverter.mdx | 7 + .../devices-next/meters/apsystems-ez1.mdx | 7 + .../devices-next/meters/avm-fritzdect.mdx | 10 + .../meters/axitec-axihycon-12-15h.mdx | 9 + .../meters/bernecker-engineering-mpm3pm.mdx | 7 + .../devices-next/meters/bgetech-ds100.mdx | 7 + .../devices-next/meters/bgetech-ws100.mdx | 7 + .../meters/bosch-bpt-s-5-hybrid.mdx | 8 + .../meters/bosswerk-micro-inverter.mdx | 7 + .../meters/carlo-gavazzi-em110-111-112.mdx | 69 + .../meters/carlo-gavazzi-em110111112.mdx | 62 - .../meters/carlo-gavazzi-em24.mdx | 7 + .../meters/carlo-gavazzi-em24_e1.mdx | 59 + .../meters/carlo-gavazzi-em24e1.mdx | 52 - .../meters/carlo-gavazzi-em330-em340.mdx | 81 + .../meters/carlo-gavazzi-em330em340.mdx | 74 - .../meters/carlo-gavazzi-em530-em540.mdx | 81 + .../meters/carlo-gavazzi-em530em540.mdx | 74 - .../meters/carlo-gavazzi-et112.mdx | 7 + .../meters/carlo-gavazzi-et330-et340.mdx | 81 + .../meters/carlo-gavazzi-et330et340.mdx | 74 - .../meters/cfos-powerbrain-meter.mdx | 7 + .../devices-next/meters/demo-battery.mdx | 13 + .../devices-next/meters/demo-meter.mdx | 11 + .../meters/deye-3p-hybrid-inverter.mdx | 11 + .../meters/deye-hp3-hybrid-inverter.mdx | 13 + .../meters/deye-micro-inverter.mdx | 7 + .../meters/deye-storage-hybrid-inverter.mdx | 8 + .../meters/deye-string-inverter.mdx | 7 + .../devices-next/meters/discovergy.mdx | 9 + .../current/devices-next/meters/dsmr.mdx | 9 + .../devices-next/meters/dzg-dvh4013.mdx | 7 + .../current/devices-next/meters/e3-dc.mdx | 111 + .../current/devices-next/meters/e3dc.mdx | 97 - .../meters/eastron-sdm120-modbus.mdx | 7 + .../meters/eastron-sdm220-230.mdx | 69 + .../devices-next/meters/eastron-sdm220230.mdx | 62 - .../meters/eastron-sdm630-modbus.mdx | 7 + .../devices-next/meters/eastron-sdm72d-m.mdx | 7 + .../meters/eastron-sdm72dm-v2.mdx | 7 + .../devices-next/meters/enphase-iq-envoy.mdx | 10 + .../meters/esphome-dlms-meter-austria.mdx | 8 + .../devices-next/meters/esphome-dsmr.mdx | 8 + .../current/devices-next/meters/fenecon.mdx | 12 + .../foxess-h1-series-hybrid-inverter.mdx | 7 + .../foxess-h3-series-hybrid-inverter.mdx | 11 + ...foxess-h3-smart-series-hybrid-inverter.mdx | 11 + .../devices-next/meters/fronius-ohmpilot.mdx | 8 + .../meters/fronius-primo-gen24-plus.mdx | 12 + .../fronius-smartmeter-via-inverter.mdx | 7 + .../meters/fronius-solar-api-v1.mdx | 36 +- .../meters/fronius-symo-gen24-plus.mdx | 12 + ...nlong-solis-hybrid-inverter-rhi-series.mdx | 9 + ...ginlong-solis-hybrid-inverter-s-series.mdx | 9 + .../meters/ginlong-solis-inverter.mdx | 7 + .../devices-next/meters/go-e-controller.mdx | 7 + .../goodwe-et-eh-bh-bt-hybrid-inverter.mdx | 165 + .../goodwe-etehbhbt-hybrid-inverter.mdx | 155 - .../meters/goodwe-goodwe-over-wifi.mdx | 7 + .../meters/goodwe-sdt-dt-inverter.mdx | 47 + .../meters/goodwe-sdtdt-inverter.mdx | 40 - .../meters/growatt-hybrid-inverter.mdx | 9 + .../meters/growatt-tl-x-h-hybrid-inverter.mdx | 159 + .../meters/growatt-tl-xh-hybrid-inverter.mdx | 150 - .../devices-next/meters/homematic-ip.mdx | 12 + .../meters/homewizard-kwh-meter.mdx | 7 + .../meters/homewizard-wi-fi-p1-meter.mdx | 7 + ...hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 8 + ...hoymiles-hm-and-hms-series-via-opendtu.mdx | 7 + .../devices-next/meters/huawei-emma.mdx | 8 + .../meters/huawei-smartlogger.mdx | 11 + .../meters/huawei-sun2000-sdongle.mdx | 8 + .../devices-next/meters/huawei-sun2000.mdx | 13 + .../devices-next/meters/iammeter-wem3080.mdx | 7 + .../iammeter-wem3080t-wem3046t-wem3050t.mdx | 59 + .../iammeter-wem3080twem3046twem3050t.mdx | 52 - .../meters/igen-tech-solarman-logger.mdx | 9 + .../current/devices-next/meters/index.mdx | 656 +++- .../devices-next/meters/inepro-pro380-mod.mdx | 7 + .../current/devices-next/meters/iometer.mdx | 7 + .../meters/janitza-b-series-umg-series.mdx | 74 - .../devices-next/meters/janitza-b-series.mdx | 81 + .../meters/janitza-umg-series.mdx | 81 + .../meters/keba-kecontact-e10.mdx | 7 + .../meters/kostal-energy-meter-c-kem-c.mdx | 7 + .../meters/kostal-energy-meter-p-kem-p.mdx | 7 + .../devices-next/meters/kostal-piko-ba.mdx | 45 + .../meters/kostal-piko-hybrid.mdx | 8 + .../meters/kostal-piko-legacy.mdx | 9 + .../meters/kostal-piko-mp-plus.mdx | 7 + .../meters/kostal-piko-piko-ba.mdx | 38 - .../devices-next/meters/kostal-piko.mdx | 45 + ...ncl-grid-charging-of-the-house-battery.mdx | 12 + .../meters/kostal-plenticore-hybrid.mdx | 13 + ...kostal-smart-energy-meter-via-inverter.mdx | 7 + .../meters/kostal-smart-energy-meter.mdx | 7 + .../devices-next/meters/lg-ess-home-15.mdx | 12 + .../devices-next/meters/lg-ess-home-8-10.mdx | 94 + .../devices-next/meters/lg-ess-home-810.mdx | 82 - .../devices-next/meters/loxone-miniserver.mdx | 11 + .../meters/m-tec-energy-butler-gen2.mdx | 7 + .../meters/m-tec-energy-butler-gen3.mdx | 8 + .../meters/marstek-venus-battery-storage.mdx | 12 + .../meters/mhendriks-p1-dongle.mdx | 8 + .../devices-next/meters/my-pv-ac-elwa-2.mdx | 7 + .../devices-next/meters/my-pv-ac-elwa-e.mdx | 7 + .../devices-next/meters/my-pv-ac-thor.mdx | 29 + .../devices-next/meters/my-pv-acthor.mdx | 22 - .../devices-next/meters/my-pv-wifi-meter.mdx | 7 + .../devices-next/meters/mystrom-switch.mdx | 7 + .../current/devices-next/meters/openems.mdx | 12 + .../meters/orno-or-we-516-or-we-517.mdx | 62 - .../devices-next/meters/orno-or-we-516.mdx | 69 + .../devices-next/meters/orno-or-we-517.mdx | 69 + .../meters/p1monitor-p1-monitor.mdx | 29 + .../current/devices-next/meters/p1monitor.mdx | 22 - .../current/devices-next/meters/plexlog.mdx | 8 + .../current/devices-next/meters/powerdog.mdx | 7 + .../meters/powerfox-poweropti.mdx | 9 + .../meters/qcells-hybrid-inverter-cloud.mdx | 23 +- .../meters/qcells-q-home-ess-hyb-g3.mdx | 195 ++ .../meters/qcells-qhome-ess-hyb-g3.mdx | 183 - .../current/devices-next/meters/rct-power.mdx | 13 + .../saia-burgess-controls-ale3-awd3.mdx | 62 - .../meters/saia-burgess-controls-sbc-ale3.mdx | 69 + .../meters/saia-burgess-controls-sbc-awd3.mdx | 69 + .../saj-h1-series-hybrid-solar-inverter.mdx | 9 + .../saj-h2-series-hybrid-solar-inverter.mdx | 11 + .../meters/saj-r5-series-solar-inverter.mdx | 7 + .../devices-next/meters/sax-homespeicher.mdx | 7 + .../schneider-electric-iem3xxx-modbus.mdx | 7 + .../devices-next/meters/senec-home.mdx | 9 + .../senergy-se-4-5-6ktl-s1-g2-inverter.mdx | 34 + .../senergy-se-456ktl-s1g2-inverter.mdx | 27 - ...pm-em-plug-s-pro-3em-in-monophase-mode.mdx | 57 - .../devices-next/meters/shelly-1pm-mini.mdx | 67 + .../devices-next/meters/shelly-1pm.mdx | 67 + .../devices-next/meters/shelly-3em.mdx | 9 + .../current/devices-next/meters/shelly-em.mdx | 67 + .../devices-next/meters/shelly-plug-s.mdx | 67 + .../devices-next/meters/shelly-pm-mini.mdx | 67 + .../devices-next/meters/shelly-pro-1pm.mdx | 67 + .../devices-next/meters/shelly-pro-3-em.mdx | 9 + .../meters/shelly-pro-3em-monophase-mode.mdx | 67 + .../devices-next/meters/shelly-pro-em.mdx | 67 + .../devices-next/meters/siemens-7kt1665.mdx | 7 + .../siemens-junelight-smart-battery.mdx | 8 + .../devices-next/meters/siemens-pac-2200.mdx | 7 + ...igen-hybrid-sigen-pv-max-sigenstore-ec.mdx | 75 + ...-sigen-hybridsigen-pv-maxsigenstore-ec.mdx | 65 - .../devices-next/meters/sma-data-manager.mdx | 8 + .../devices-next/meters/sma-energy-meter.mdx | 8 + .../meters/sma-inverter-speedwire.mdx | 9 + .../sma-smart-energy-hybrid-inverter.mdx | 11 + ...a-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx | 50 + .../sma-sunny-boy-storage-152025-modbus.mdx | 40 - ...a-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx | 50 + .../sma-sunny-boy-storage-375060-modbus.mdx | 40 - .../meters/sma-sunny-home-manager-2-0.mdx | 36 + .../meters/sma-sunny-home-manager-20.mdx | 28 - .../meters/sma-sunny-island-modbus.mdx | 10 + .../devices-next/meters/sma-webbox.mdx | 7 + .../meters/sma-wechselrichter-modbus.mdx | 7 + .../meters/smartfox-box-reg-reg-extended.mdx | 51 - .../devices-next/meters/smartfox-box.mdx | 58 + .../meters/smartfox-light-em2-firmware.mdx | 77 + .../devices-next/meters/smartfox-pro-2.mdx | 77 + .../meters/smartfox-pro-light-2.mdx | 77 + .../meters/smartfox-pro-light.mdx | 77 + ...o-light-pro-light-2-light-em2-firmware.mdx | 69 - .../devices-next/meters/smartfox-pro.mdx | 77 + .../meters/smartfox-reg-extended.mdx | 58 + .../devices-next/meters/smartfox-reg.mdx | 58 + .../meters/sofarsolar-hybrid-inverter.mdx | 134 + .../meters/sofarsolar-hyd-3-6k-ep.mdx | 191 ++ .../meters/sofarsolar-hyd-36k-ep.mdx | 180 - .../meters/sofarsolar-hyd-5-20k-3ph.mdx | 191 ++ .../meters/sofarsolar-hyd-520k-3ph.mdx | 180 - .../sofarsolar-inverter-hybrid-inverter.mdx | 126 - .../meters/sofarsolar-inverter.mdx | 134 + .../meters/sofarsolar-sofar-5-24ktl-g3.mdx | 191 ++ .../meters/sofarsolar-sofar-524ktl-g3.mdx | 180 - .../meters/sofarsolar-sofar-80-136ktl.mdx | 191 ++ .../meters/sofarsolar-sofar-80136ktl.mdx | 180 - .../meters/solaranzeige-solaranzeige.mdx | 76 + .../devices-next/meters/solaranzeige.mdx | 64 - .../meters/solaredge-hybrid-inverter.mdx | 11 + .../meters/solaredge-inverter.mdx | 8 + .../current/devices-next/meters/solarlog.mdx | 8 + ...armax-max-storage-max-storage-ultimate.mdx | 111 + ...olarmax-maxstorage-maxstorage-ultimate.mdx | 101 - .../meters/solarmax-solarmax-smt.mdx | 7 + .../meters/solarmax-sp-series-inverter.mdx | 7 + ...arwatt-energymanager-energymanager-pro.mdx | 54 - .../meters/solarwatt-energymanager-pro.mdx | 62 + .../meters/solarwatt-energymanager.mdx | 62 + .../meters/solarwatt-manager-flex.mdx | 8 + ...myreserve-matrix-lan-oder-powergateway.mdx | 9 + .../meters/solarwatt-myreserve.mdx | 8 + .../meters/solax-hybrid-inverter-cloud.mdx | 9 + .../meters/solax-hybrid-x1-x3-g3-g4.mdx | 195 ++ .../meters/solax-hybrid-x1x3-g3g4.mdx | 183 - .../meters/solax-inverter-cloud.mdx | 8 + .../current/devices-next/meters/solinteng.mdx | 9 + .../sonnen-comfort-eco-5-eco-6-oem-65.mdx | 74 - .../devices-next/meters/sonnen-comfort.mdx | 85 + .../devices-next/meters/sonnen-eco-5.mdx | 85 + .../devices-next/meters/sonnen-eco-6.mdx | 85 + .../devices-next/meters/sonnen-oem-6-5.mdx | 85 + .../meters/sonnen-sonnenbatterie.mdx | 12 + .../current/devices-next/meters/st-ems.mdx | 9 + .../meters/steca-coolcept-flex.mdx | 7 + .../meters/sungrow-sg-series-inverter.mdx | 7 + .../sungrow-sh-series-hybrid-inverter.mdx | 11 + .../meters/sunspec-battery-model-124.mdx | 9 + .../meters/sunspec-battery-model-802.mdx | 10 + .../meters/sunspec-hybrid-inverter.mdx | 9 + .../devices-next/meters/sunspec-inverter.mdx | 8 + .../devices-next/meters/sunspec-meter.mdx | 7 + .../meters/sunsynk-3p-hybrid-inverter.mdx | 11 + .../meters/sunsynk-hp3-hybrid-inverter.mdx | 13 + .../meters/sunsynk-micro-inverter.mdx | 7 + .../sunsynk-storage-hybrid-inverter.mdx | 8 + .../meters/sunsynk-string-inverter.mdx | 7 + .../current/devices-next/meters/sunway.mdx | 9 + ...ml-ir-reader-for-smartmeters-e-g-hichi.mdx | 100 + ...sml-ir-reader-for-smartmeters-eg-hichi.mdx | 91 - ...tasmota-tasmota-1-phase-plus-sml-meter.mdx | 80 + .../tasmota-tasmota-1-phase-sml-meter.mdx | 70 - .../meters/tasmota-three-phase.mdx | 9 + .../devices-next/meters/tesla-powerwall.mdx | 12 + .../devices-next/meters/tibber-pulse.mdx | 8 + .../meters/tp-link-h-series-smart-plug.mdx | 7 + .../tp-link-tapo-p-series-smart-plug.mdx | 9 + .../meters/tq-energy-manager-em2xx-em3xx.mdx | 33 + .../meters/tq-energy-manager-em2xxem3xx.mdx | 24 - .../meters/tq-energy-manager-em420.mdx | 10 + .../devices-next/meters/varta-element.mdx | 70 + .../devices-next/meters/varta-pulse-neo.mdx | 70 + .../meters/varta-pulse-pulse-neo-element.mdx | 61 - .../devices-next/meters/varta-pulse.mdx | 70 + .../devices-next/meters/victron-em24.mdx | 7 + .../devices-next/meters/victron-em24_e1.mdx | 59 + .../devices-next/meters/victron-em24e1.mdx | 52 - .../meters/victron-em530-em540.mdx | 81 + .../meters/victron-em530em540.mdx | 74 - .../devices-next/meters/victron-energy.mdx | 13 + .../devices-next/meters/victron-et340.mdx | 7 + ...volkszahler-http-api-import-and-export.mdx | 9 + .../meters/volkszahler-http-api.mdx | 8 + .../meters/volkszahler-websocket-api.mdx | 9 + .../current/devices-next/meters/vzlogger.mdx | 20 + .../devices-next/meters/wago-879-30xx.mdx | 7 + .../current/devices-next/meters/wattsonic.mdx | 9 + .../meters/weidmuller-em110-rtu-2p.mdx | 7 + .../meters/weidmuller-em111-rtu-2p.mdx | 7 + .../meters/weidmuller-em120-rtu-2p.mdx | 7 + .../meters/weidmuller-em122-rtu-2p.mdx | 7 + .../meters/youless-energy-monitor.mdx | 7 + .../meters/zcs-azzurro-hybrid-inverter.mdx | 134 + .../zcs-azzurro-inverter-hybrid-inverter.mdx | 126 - .../meters/zcs-azzurro-inverter.mdx | 134 + .../meters/zendure-hyper-2000.mdx | 11 + .../zuidwijk-slimmelezer-in-luxembourg.mdx | 25 - ...uidwijk-slimmelezer-plus-in-luxembourg.mdx | 32 + .../meters/zuidwijk-slimmelezer-plus-v2.mdx | 32 + .../meters/zuidwijk-slimmelezer-plus.mdx | 36 + .../meters/zuidwijk-slimmelezer-v2.mdx | 25 - .../meters/zuidwijk-slimmelezer.mdx | 28 - .../devices-next/tariffs/amber-electric.mdx | 12 + .../current/devices-next/tariffs/awattar.mdx | 10 + .../electricity-maps-commercial-api.mdx | 9 + .../tariffs/electricity-maps-free-api.mdx | 8 + .../devices-next/tariffs/energinet.mdx | 10 + .../current/devices-next/tariffs/enever.mdx | 12 + .../current/devices-next/tariffs/entso-e.mdx | 11 + .../devices-next/tariffs/forecast-solar.mdx | 53 + .../devices-next/tariffs/forecastsolar.mdx | 39 - .../devices-next/tariffs/fraunhofer-ise.mdx | 10 + .../tariffs/green-grid-compass.mdx | 8 + .../tariffs/groupe-e-vario-plus.mdx | 9 + .../devices-next/tariffs/grunstromindex.mdx | 8 + .../current/devices-next/tariffs/index.mdx | 6 +- .../tariffs/national-grid-eso.mdx | 8 + .../tariffs/nordpool-spot-prices.mdx | 11 + .../tariffs/octopus-energy-api.mdx | 8 + .../tariffs/octopus-energy-product-code.mdx | 9 + .../devices-next/tariffs/open-meteo.mdx | 18 + .../current/devices-next/tariffs/ostrom.mdx | 9 + .../devices-next/tariffs/pun-orario.mdx | 9 + .../tariffs/smartenergy-smartcontrol.mdx | 9 + .../current/devices-next/tariffs/solcast.mdx | 11 + .../devices-next/tariffs/spotty-energie.mdx | 11 + .../current/devices-next/tariffs/tibber.mdx | 11 + .../tariffs/victron-vrm-solar-forecast.mdx | 9 + .../current/devices-next/vehicles/aiways.mdx | 19 + .../current/devices-next/vehicles/audi.mdx | 19 + .../current/devices-next/vehicles/bmw.mdx | 25 +- .../current/devices-next/vehicles/citroen.mdx | 20 + .../current/devices-next/vehicles/dacia.mdx | 23 +- .../current/devices-next/vehicles/ds.mdx | 20 + .../devices-next/vehicles/evnotify.mdx | 17 + .../current/devices-next/vehicles/fiat.mdx | 24 +- .../current/devices-next/vehicles/ford.mdx | 21 + .../vehicles/generic-vehicle-without-api.mdx | 15 + .../vehicles/hyundai-bluelink.mdx | 20 + .../current/devices-next/vehicles/index.mdx | 12 +- .../devices-next/vehicles/iobroker-bmw.mdx | 62 + .../devices-next/vehicles/iobrokerbmw.mdx | 42 - .../devices-next/vehicles/iso15118.mdx | 15 + .../current/devices-next/vehicles/jeep.mdx | 24 +- .../devices-next/vehicles/kia-bluelink.mdx | 20 + .../devices-next/vehicles/mercedes-benz.mdx | 21 + .../current/devices-next/vehicles/mg.mdx | 20 + .../current/devices-next/vehicles/mg2mqtt.mdx | 18 + .../current/devices-next/vehicles/mini.mdx | 25 +- .../current/devices-next/vehicles/mz2mqtt.mdx | 17 + .../devices-next/vehicles/nissan-ariya.mdx | 19 + .../vehicles/nissan-leaf-pre-2019.mdx | 19 + .../devices-next/vehicles/nissan-leaf.mdx | 19 + .../devices-next/vehicles/niu-e-scooter.mdx | 12 + .../current/devices-next/vehicles/opel.mdx | 20 + .../open-vehicle-monitoring-system.mdx | 20 + .../current/devices-next/vehicles/peugeot.mdx | 20 + .../devices-next/vehicles/polestar.mdx | 19 + .../vehicles/psa-car-controller.mdx | 18 + .../current/devices-next/vehicles/renault.mdx | 20 + ...nect-gen3-ateca-leon-formentor-tarraco.mdx | 19 + ...raconnect-gen4-born-formentor-tavascan.mdx | 23 +- .../devices-next/vehicles/skoda-enyaq.mdx | 20 + .../current/devices-next/vehicles/smart-1.mdx | 62 + .../devices-next/vehicles/smart-eq.mdx | 21 + .../current/devices-next/vehicles/smart.mdx | 41 - .../devices-next/vehicles/tesla-ble.mdx | 18 + .../current/devices-next/vehicles/tesla.mdx | 22 + .../devices-next/vehicles/teslalogger.mdx | 18 + .../devices-next/vehicles/teslamate.mdx | 16 + .../current/devices-next/vehicles/tessie.mdx | 17 + .../current/devices-next/vehicles/toyota.mdx | 19 + .../current/devices-next/vehicles/tronity.mdx | 19 + .../vehicles/volkswagen-we-connect-id.mdx | 26 +- .../current/devices-next/vehicles/volvo.mdx | 20 + .../devices-next/vehicles/volvo2mqtt.mdx | 17 + .../vehicles/zero-motorcycles.mdx | 19 + .../current/devices/chargers.mdx | 348 +- .../current/devices/meters.mdx | 3014 +++++++++++++---- .../current/devices/smartswitches.mdx | 85 +- .../current/devices/vehicles.mdx | 28 +- src/css/custom.css | 13 + src/generateDevicesNext.ts | 242 +- templates/release/de/charger/Kathrein_0.yaml | 17 - templates/release/de/charger/Kathrein_1.yaml | 17 - templates/release/de/charger/Kathrein_2.yaml | 17 - templates/release/de/charger/Kathrein_3.yaml | 17 - templates/release/de/charger/Kathrein_4.yaml | 17 - templates/release/de/charger/Kathrein_5.yaml | 17 - .../release/de/charger/abb-terra-ac-ocpp.yaml | 88 + .../release/de/charger/abb-terra-ac.yaml | 52 + templates/release/de/charger/abb_0.yaml | 30 - .../de/charger/abl-em4-single-ocpp.yaml | 86 + .../de/charger/abl-em4-single-sbcx.yaml | 52 + .../release/de/charger/abl-em4-twin-ocpp.yaml | 86 + .../release/de/charger/abl-em4-twin-sbcx.yaml | 52 + templates/release/de/charger/abl-em4_0.yaml | 25 - templates/release/de/charger/abl-emh1.yaml | 53 + .../release/de/charger/abl-emh2-ocpp.yaml | 86 + templates/release/de/charger/abl-emh2.yaml | 53 + .../release/de/charger/abl-emh3-ocpp.yaml | 86 + templates/release/de/charger/abl_0.yaml | 23 - templates/release/de/charger/abl_1.yaml | 23 - templates/release/de/charger/abl_2.yaml | 23 - templates/release/de/charger/ac-elwa-2_0.yaml | 16 - templates/release/de/charger/ac-thor_0.yaml | 17 - templates/release/de/charger/ac-thor_1.yaml | 17 - .../release/de/charger/alfen-eve-ocpp.yaml | 86 + templates/release/de/charger/alfen-eve.yaml | 35 + templates/release/de/charger/alfen_0.yaml | 17 - .../release/de/charger/alpha-innotec.yaml | 63 + .../de/charger/alphatec-ladesaule-twin.yaml | 44 + .../de/charger/alphatec-wallbox-mini.yaml | 44 + .../de/charger/alphatec-wallbox-power.yaml | 44 + templates/release/de/charger/alphatec_0.yaml | 23 - templates/release/de/charger/alphatec_1.yaml | 23 - templates/release/de/charger/alphatec_2.yaml | 23 - templates/release/de/charger/alphatec_3.yaml | 23 - .../release/de/charger/amperfied-solar_0.yaml | 15 - .../amperfied-wallbox-connect-business.yaml | 33 + .../amperfied-wallbox-connect-home.yaml | 33 + .../amperfied-wallbox-connect-solar.yaml | 33 + .../amperfied-wallbox-energy-control.yaml | 45 + templates/release/de/charger/amperfied_0.yaml | 15 - templates/release/de/charger/amperfied_1.yaml | 15 - templates/release/de/charger/ampure-next.yaml | 34 + .../release/de/charger/ampure-unite.yaml | 35 + .../release/de/charger/audi-wallbox-plus.yaml | 41 + .../release/de/charger/audi-wallbox-pro.yaml | 39 + .../release/de/charger/autel-ac-compact.yaml | 94 + .../de/charger/autel-ac-maxicharger.yaml | 94 + .../de/charger/autoaid-business-wallbox.yaml | 86 + .../charger/autoaid-intelligent-wallbox.yaml | 86 + .../release/de/charger/avm-fritzdect.yaml | 99 + .../release/de/charger/bender-cc612.yaml | 35 + .../release/de/charger/bender-cc613.yaml | 35 + templates/release/de/charger/bender-cc_0.yaml | 17 - templates/release/de/charger/bender-cc_1.yaml | 17 - .../release/de/charger/bender-cc_10.yaml | 17 - .../release/de/charger/bender-cc_11.yaml | 17 - .../release/de/charger/bender-cc_12.yaml | 17 - .../release/de/charger/bender-cc_13.yaml | 17 - .../release/de/charger/bender-cc_14.yaml | 17 - .../release/de/charger/bender-cc_15.yaml | 17 - templates/release/de/charger/bender-cc_2.yaml | 17 - templates/release/de/charger/bender-cc_3.yaml | 17 - templates/release/de/charger/bender-cc_4.yaml | 17 - templates/release/de/charger/bender-cc_5.yaml | 17 - templates/release/de/charger/bender-cc_6.yaml | 17 - templates/release/de/charger/bender-cc_7.yaml | 17 - templates/release/de/charger/bender-cc_8.yaml | 17 - templates/release/de/charger/bender-cc_9.yaml | 17 - .../release/de/charger/bender-icc1314.yaml | 35 + .../release/de/charger/bender-icc1324.yaml | 35 + .../release/de/charger/bender-icc_0.yaml | 17 - .../release/de/charger/bender-icc_1.yaml | 17 - .../release/de/charger/bender-icc_2.yaml | 17 - .../release/de/charger/bender-icc_3.yaml | 17 - .../release/de/charger/bmw-i-wallbox.yaml | 54 + .../release/de/charger/bosch-sg-ready.yaml | 53 + .../release/de/charger/bosch-x-change.yaml | 46 + .../charger/buderus-logamatic-hmc-20-z.yaml | 64 + .../de/charger/buderus-logamatic-hmc-20.yaml | 64 + .../release/de/charger/buderus-sg-ready.yaml | 53 + .../de/charger/cfos-power-brain-solar.yaml | 28 + .../release/de/charger/cfos-power-brain.yaml | 28 + templates/release/de/charger/cfos_0.yaml | 16 - templates/release/de/charger/cfos_1.yaml | 16 - .../release/de/charger/charge-amps-halo.yaml | 86 + .../release/de/charger/compleo-ebox.yaml | 33 + .../de/charger/cta-all-in-one-aeroplus.yaml | 64 + templates/release/de/charger/cubos-c11e.yaml | 35 + templates/release/de/charger/cubos-c22e.yaml | 35 + .../de/charger/cupra-charger-connect-2.yaml | 39 + .../de/charger/cupra-charger-connect.yaml | 41 + .../de/charger/cupra-charger-pro-2.yaml | 39 + .../cupra-charger-pro-eichrecht-2.yaml | 39 + .../release/de/charger/cupra-charger-pro.yaml | 39 + .../de/charger/dadapower-premium-wallbox.yaml | 33 + templates/release/de/charger/dadapower_0.yaml | 15 - .../release/de/charger/daheimladen-mb_0.yaml | 11 - .../de/charger/daheimladen-wallbox.yaml | 32 + .../de/charger/daikin-homehub-sg-ready.yaml | 42 + .../release/de/charger/daikin-homehub_0.yaml | 15 - .../de/charger/delta-ac-max-basic.yaml | 82 + .../de/charger/delta-ac-max-smart.yaml | 82 + .../de/charger/delta-slim-charger.yaml | 82 + .../de/charger/delta-ultra-fast-charger.yaml | 82 + templates/release/de/charger/delta_0.yaml | 51 - templates/release/de/charger/delta_1.yaml | 51 - templates/release/de/charger/delta_2.yaml | 51 - templates/release/de/charger/delta_3.yaml | 51 - .../release/de/charger/demo-charger.yaml | 68 + .../release/de/charger/demo-charger_0.yaml | 20 - .../release/de/charger/e-on-drive-ebox.yaml | 33 + .../release/de/charger/e-on-drive-vbox.yaml | 35 + .../de/charger/e3-dc-easy-connect.yaml | 35 + .../release/de/charger/easee-charge-core.yaml | 62 + .../release/de/charger/easee-charge-lite.yaml | 62 + .../release/de/charger/easee-charge.yaml | 62 + templates/release/de/charger/easee-home.yaml | 62 + templates/release/de/charger/easee_0.yaml | 14 - templates/release/de/charger/easee_1.yaml | 14 - templates/release/de/charger/easee_2.yaml | 14 - templates/release/de/charger/easee_3.yaml | 14 - .../release/de/charger/ebee-wallbox.yaml | 35 + .../release/de/charger/echarge-cph1.yaml | 37 + .../release/de/charger/echarge-cph2.yaml | 21 + .../release/de/charger/echarge-cpm2.yaml | 21 + .../charger/ecoharmony-evse-epc-2-0-plus.yaml | 48 + .../de/charger/edgetech-smart-evse.yaml | 42 + .../release/de/charger/eebus-compatible.yaml | 32 + templates/release/de/charger/eebus_0.yaml | 11 - templates/release/de/charger/elco.yaml | 63 + templates/release/de/charger/elecq-biz.yaml | 85 + templates/release/de/charger/elecq-home.yaml | 85 + .../release/de/charger/elecq-station.yaml | 85 + templates/release/de/charger/eledio-go.yaml | 89 + templates/release/de/charger/elli-2_0.yaml | 18 - templates/release/de/charger/elli-2_1.yaml | 18 - templates/release/de/charger/elli-2_10.yaml | 18 - templates/release/de/charger/elli-2_11.yaml | 18 - templates/release/de/charger/elli-2_2.yaml | 18 - templates/release/de/charger/elli-2_3.yaml | 18 - templates/release/de/charger/elli-2_4.yaml | 18 - templates/release/de/charger/elli-2_5.yaml | 18 - templates/release/de/charger/elli-2_6.yaml | 18 - templates/release/de/charger/elli-2_7.yaml | 18 - templates/release/de/charger/elli-2_8.yaml | 18 - templates/release/de/charger/elli-2_9.yaml | 18 - .../de/charger/elli-charger-connect-2.yaml | 39 + .../de/charger/elli-charger-connect.yaml | 41 + .../de/charger/elli-charger-pro-2.yaml | 39 + .../charger/elli-charger-pro-eichrecht-2.yaml | 39 + .../release/de/charger/elli-charger-pro.yaml | 39 + .../release/de/charger/elliconnect_0.yaml | 20 - .../release/de/charger/elliconnect_1.yaml | 20 - .../release/de/charger/elliconnect_2.yaml | 20 - .../release/de/charger/elliconnect_3.yaml | 20 - .../release/de/charger/elliconnect_4.yaml | 20 - templates/release/de/charger/ellipro_0.yaml | 18 - templates/release/de/charger/ellipro_1.yaml | 18 - templates/release/de/charger/ellipro_2.yaml | 18 - templates/release/de/charger/ellipro_3.yaml | 18 - templates/release/de/charger/ellipro_4.yaml | 18 - templates/release/de/charger/em2go-home.yaml | 23 + .../release/de/charger/em2go-home_0.yaml | 11 - .../de/charger/em2go-pro-power-ocpp-onc.yaml | 34 + templates/release/de/charger/em2go_0.yaml | 16 - templates/release/de/charger/emsesp_0.yaml | 14 - templates/release/de/charger/emsesp_1.yaml | 14 - templates/release/de/charger/emsesp_2.yaml | 14 - .../release/de/charger/enercab-smart.yaml | 89 + .../de/charger/enplus-ac-ev-charger.yaml | 86 + .../de/charger/ensto-chago-wallbox.yaml | 35 + .../de/charger/entratek-power-dot-fix.yaml | 86 + .../de/charger/entratek-power-dot-pro-2.yaml | 86 + .../release/de/charger/eprowallbox_0.yaml | 22 - .../release/de/charger/esl-walli-light.yaml | 35 + .../release/de/charger/esystems-ghostone.yaml | 39 + templates/release/de/charger/etrel-duo_0.yaml | 19 - .../release/de/charger/etrel-inch-duo.yaml | 49 + templates/release/de/charger/etrel-inch.yaml | 34 + templates/release/de/charger/etrel_0.yaml | 13 - templates/release/de/charger/etrel_1.yaml | 13 - templates/release/de/charger/evbox-elvi.yaml | 86 + templates/release/de/charger/evbox-livo.yaml | 33 + templates/release/de/charger/evse-din.yaml | 40 + templates/release/de/charger/evse-din_0.yaml | 20 - templates/release/de/charger/evse-din_1.yaml | 19 - templates/release/de/charger/evse-wifi.yaml | 19 + templates/release/de/charger/evsewifi_0.yaml | 7 - .../charger/free2move-eprowallbox-move.yaml | 43 + .../de/charger/free2move-eprowallbox.yaml | 43 + .../free2move-esolutions-eprowallbox.yaml | 86 + templates/release/de/charger/fritzdect_0.yaml | 24 - .../de/charger/fronius-wattpilot-ocpp.yaml | 86 + templates/release/de/charger/garo-glb.yaml | 35 + .../release/de/charger/garo-glbplus.yaml | 35 + .../release/de/charger/garo-ls4-compact.yaml | 35 + templates/release/de/charger/garo-ls4.yaml | 35 + templates/release/de/charger/ghost_0.yaml | 18 - templates/release/de/charger/ghost_1.yaml | 18 - .../de/charger/go-e-charger-gemini-ocpp.yaml | 86 + .../de/charger/go-e-charger-gemini.yaml | 27 + .../de/charger/go-e-charger-homefix.yaml | 24 + .../de/charger/go-e-charger-homeplus.yaml | 27 + .../de/charger/go-e-charger-pro-ocpp.yaml | 86 + .../release/de/charger/go-e-charger-pro.yaml | 24 + .../de/charger/go-e-charger-v3-ocpp.yaml | 86 + .../release/de/charger/go-e-charger-v3.yaml | 27 + templates/release/de/charger/go-e-v3_0.yaml | 15 - templates/release/de/charger/go-e-v3_1.yaml | 15 - templates/release/de/charger/go-e-v3_2.yaml | 15 - templates/release/de/charger/go-e_0.yaml | 12 - templates/release/de/charger/go-e_1.yaml | 12 - .../release/de/charger/hardy-barth-cph1.yaml | 37 + .../release/de/charger/hardy-barth-cph2.yaml | 21 + .../release/de/charger/hardy-barth-cpm2.yaml | 21 + .../release/de/charger/hardybarth-ecb1_0.yaml | 16 - .../release/de/charger/hardybarth-ecb1_1.yaml | 16 - .../de/charger/hardybarth-salia_0.yaml | 9 - .../de/charger/hardybarth-salia_1.yaml | 9 - .../de/charger/hardybarth-salia_2.yaml | 9 - .../de/charger/hardybarth-salia_3.yaml | 9 - .../de/charger/heidelberg-energy-control.yaml | 45 + .../release/de/charger/heidelberg_0.yaml | 24 - .../release/de/charger/heidelberg_1.yaml | 24 - .../release/de/charger/heidelberg_2.yaml | 24 - .../release/de/charger/heidelberg_3.yaml | 24 - .../release/de/charger/hesotec-ebox.yaml | 32 + .../release/de/charger/hesotec-esat.yaml | 32 + templates/release/de/charger/hesotec_0.yaml | 14 - templates/release/de/charger/hesotec_1.yaml | 14 - .../de/charger/home-assistant-switch.yaml | 100 + .../de/charger/homeassistant-switch_0.yaml | 25 - .../de/charger/homecharge-homecharger.yaml | 90 + .../release/de/charger/homematic-ip.yaml | 139 + templates/release/de/charger/homematic_0.yaml | 28 - templates/release/de/charger/homewizard.yaml | 65 + .../release/de/charger/homewizard_0.yaml | 17 - .../de/charger/huawei-scharger-22kt-s0.yaml | 85 + .../de/charger/huawei-scharger-7ks-s0.yaml | 85 + .../release/de/charger/ichargecion_0.yaml | 20 - .../release/de/charger/ichargecion_1.yaml | 20 - templates/release/de/charger/idm.yaml | 41 + templates/release/de/charger/idm_0.yaml | 14 - templates/release/de/charger/innogy-ebox.yaml | 33 + .../release/de/charger/innogy-ebox_0.yaml | 15 - .../release/de/charger/innogy-ebox_1.yaml | 15 - .../release/de/charger/innogy-ebox_2.yaml | 15 - .../release/de/charger/inro-pantabox.yaml | 20 + .../release/de/charger/juice-charger-me.yaml | 35 + .../release/de/charger/junkers-sg-ready.yaml | 53 + .../release/de/charger/kathrein-kwb-ac20.yaml | 35 + .../release/de/charger/kathrein-kwb-ac35.yaml | 35 + .../de/charger/kathrein-kwb-ac40-e.yaml | 35 + .../release/de/charger/kathrein-kwb-ac40.yaml | 35 + .../de/charger/kathrein-kwb-ac60-e.yaml | 35 + .../release/de/charger/kathrein-kwb-ac60.yaml | 35 + .../de/charger/keba-kecontact-p20.yaml | 54 + .../charger/keba-kecontact-p30-c-series.yaml | 54 + .../charger/keba-kecontact-p30-x-series.yaml | 54 + .../de/charger/keba-kecontact-p40-pro.yaml | 54 + .../de/charger/keba-kecontact-p40.yaml | 54 + .../release/de/charger/keba-modbus_0.yaml | 27 - .../release/de/charger/keba-modbus_1.yaml | 27 - .../release/de/charger/keba-modbus_2.yaml | 27 - .../release/de/charger/keba-modbus_3.yaml | 27 - .../release/de/charger/keba-modbus_4.yaml | 27 - .../release/de/charger/keba-modbus_5.yaml | 27 - .../release/de/charger/keba-modbus_6.yaml | 27 - .../de/charger/kermi-x-center-pro.yaml | 46 + templates/release/de/charger/kermi_0.yaml | 16 - templates/release/de/charger/kermi_1.yaml | 16 - .../de/charger/kontron-solar-charger.yaml | 39 + .../release/de/charger/kostal-enector.yaml | 48 + templates/release/de/charger/kse-wbx16.yaml | 43 + templates/release/de/charger/kse_0.yaml | 22 - .../release/de/charger/ladefoxx-evload.yaml | 50 + .../de/charger/ladefoxx-mikro-2-0.yaml | 50 + .../de/charger/lambda-eu-l-series.yaml | 52 + .../de/charger/lambda-zewotherm_0.yaml | 22 - .../de/charger/lambda-zewotherm_1.yaml | 22 - templates/release/de/charger/livo_0.yaml | 12 - .../de/charger/lrt-home-essentialplus.yaml | 44 + templates/release/de/charger/luxtronik_0.yaml | 28 - templates/release/de/charger/luxtronik_1.yaml | 28 - .../release/de/charger/luxtronik_10.yaml | 28 - templates/release/de/charger/luxtronik_2.yaml | 27 - templates/release/de/charger/luxtronik_3.yaml | 28 - templates/release/de/charger/luxtronik_4.yaml | 27 - templates/release/de/charger/luxtronik_5.yaml | 28 - templates/release/de/charger/luxtronik_6.yaml | 28 - templates/release/de/charger/luxtronik_7.yaml | 28 - templates/release/de/charger/luxtronik_8.yaml | 28 - templates/release/de/charger/luxtronik_9.yaml | 28 - .../charger/mennekes-amedio-professional.yaml | 35 + .../mennekes-amtron-4business-700.yaml | 35 + .../de/charger/mennekes-amtron-4you-300.yaml | 48 + .../de/charger/mennekes-amtron-4you-500.yaml | 35 + .../mennekes-amtron-chargecontrol.yaml | 35 + .../charger/mennekes-amtron-compact-2-0s.yaml | 48 + .../de/charger/mennekes-amtron-premium.yaml | 32 + .../charger/mennekes-amtron-professional.yaml | 35 + .../de/charger/mennekes-amtron-xtra.yaml | 32 + .../de/charger/mennekes-compact_0.yaml | 27 - .../de/charger/mennekes-compact_1.yaml | 27 - .../de/charger/mennekes-compact_2.yaml | 27 - .../mennekes-emobility-gateway-acu.yaml | 91 + .../release/de/charger/mennekes-hcc3_0.yaml | 14 - .../release/de/charger/mennekes-hcc3_1.yaml | 14 - .../de/charger/mennekes-smart-acu.yaml | 91 + .../de/charger/mennekes-smart-t-acu.yaml | 91 + .../release/de/charger/my-pv-ac-elwa-2.yaml | 43 + .../release/de/charger/my-pv-ac-thor-9s.yaml | 53 + .../release/de/charger/my-pv-ac-thor.yaml | 53 + .../release/de/charger/mystrom-switch.yaml | 66 + templates/release/de/charger/mystrom_0.yaml | 18 - .../release/de/charger/nibe-ap-aw10.yaml | 64 + .../release/de/charger/novelan-wpr-net.yaml | 64 + templates/release/de/charger/nrggen2_0.yaml | 25 - .../release/de/charger/nrgkick-connect.yaml | 42 + .../release/de/charger/nrgkick-connect_0.yaml | 12 - .../release/de/charger/nrgkick-gen2.yaml | 52 + .../de/charger/obo-bettermann-ion.yaml | 48 + templates/release/de/charger/obo_0.yaml | 26 - templates/release/de/charger/obo_1.yaml | 26 - templates/release/de/charger/obo_2.yaml | 26 - .../ocpp-1-6j-compatible-smart-charging.yaml | 107 + .../release/de/charger/ocpp-abb-tac_0.yaml | 22 - templates/release/de/charger/ocpp-abl_0.yaml | 20 - templates/release/de/charger/ocpp-abl_1.yaml | 20 - templates/release/de/charger/ocpp-abl_2.yaml | 20 - .../release/de/charger/ocpp-alfen_0.yaml | 20 - .../release/de/charger/ocpp-autel_0.yaml | 28 - .../release/de/charger/ocpp-autel_1.yaml | 28 - .../release/de/charger/ocpp-autoaid_0.yaml | 20 - .../release/de/charger/ocpp-autoaid_1.yaml | 20 - templates/release/de/charger/ocpp-beny_0.yaml | 20 - .../release/de/charger/ocpp-chargeamps_0.yaml | 20 - .../release/de/charger/ocpp-elecq_0.yaml | 19 - .../release/de/charger/ocpp-elecq_1.yaml | 19 - .../release/de/charger/ocpp-elecq_2.yaml | 19 - .../release/de/charger/ocpp-enercab_0.yaml | 23 - .../release/de/charger/ocpp-enercab_1.yaml | 23 - .../release/de/charger/ocpp-enplus_0.yaml | 20 - .../release/de/charger/ocpp-entratek_0.yaml | 20 - .../release/de/charger/ocpp-entratek_1.yaml | 20 - .../release/de/charger/ocpp-esolutions_0.yaml | 20 - .../release/de/charger/ocpp-evbox-elvi_0.yaml | 20 - templates/release/de/charger/ocpp-goe_0.yaml | 20 - templates/release/de/charger/ocpp-goe_1.yaml | 20 - templates/release/de/charger/ocpp-goe_2.yaml | 20 - templates/release/de/charger/ocpp-goe_3.yaml | 20 - .../release/de/charger/ocpp-homecharge_0.yaml | 24 - .../release/de/charger/ocpp-huawei_0.yaml | 19 - .../release/de/charger/ocpp-huawei_1.yaml | 19 - .../de/charger/ocpp-mennekes-acu_0.yaml | 25 - .../de/charger/ocpp-mennekes-acu_1.yaml | 25 - .../de/charger/ocpp-mennekes-acu_2.yaml | 25 - .../release/de/charger/ocpp-orbis_0.yaml | 19 - .../release/de/charger/ocpp-sungrow_0.yaml | 20 - .../release/de/charger/ocpp-wallbox_0.yaml | 28 - .../release/de/charger/ocpp-wallbox_1.yaml | 28 - .../release/de/charger/ocpp-wallbox_2.yaml | 28 - .../release/de/charger/ocpp-wallbox_3.yaml | 28 - .../release/de/charger/ocpp-zaptec_0.yaml | 25 - templates/release/de/charger/ocpp_0.yaml | 41 - templates/release/de/charger/openevse.yaml | 41 + templates/release/de/charger/openevse_0.yaml | 11 - .../release/de/charger/openwb-2.0_0.yaml | 32 - templates/release/de/charger/openwb-pro.yaml | 21 + .../release/de/charger/openwb-pro_0.yaml | 9 - .../release/de/charger/openwb-series2.yaml | 46 + .../de/charger/openwb-software-2-x.yaml | 68 + templates/release/de/charger/openwb_0.yaml | 16 - .../de/charger/optec-mobility-one.yaml | 35 + .../release/de/charger/orbis-viaris.yaml | 85 + templates/release/de/charger/pantabox_0.yaml | 8 - .../release/de/charger/pc-electric-garo.yaml | 33 + .../release/de/charger/pcelectric-garo_0.yaml | 12 - .../release/de/charger/peblar-business.yaml | 35 + .../release/de/charger/peblar-home-plus.yaml | 35 + templates/release/de/charger/peblar-home.yaml | 35 + templates/release/de/charger/peblar_0.yaml | 17 - templates/release/de/charger/peblar_1.yaml | 17 - templates/release/de/charger/peblar_2.yaml | 17 - .../release/de/charger/phoenix-charx_0.yaml | 23 - .../release/de/charger/phoenix-charx_1.yaml | 23 - .../release/de/charger/phoenix-charx_2.yaml | 23 - .../de/charger/phoenix-contact-charx.yaml | 50 + .../charger/phoenix-contact-em-cp-pp-eth.yaml | 31 + ...x-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml | 35 + ...enix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml | 35 + ...ix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml | 35 + ...oenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml | 35 + .../de/charger/phoenix-contact-ev-ser.yaml | 41 + .../release/de/charger/phoenix-em-eth_0.yaml | 13 - .../release/de/charger/phoenix-ev-eth_0.yaml | 17 - .../release/de/charger/phoenix-ev-eth_1.yaml | 17 - .../release/de/charger/phoenix-ev-eth_2.yaml | 17 - .../release/de/charger/phoenix-ev-eth_3.yaml | 17 - .../release/de/charger/phoenix-ev-eth_4.yaml | 17 - .../release/de/charger/phoenix-ev-eth_5.yaml | 17 - .../release/de/charger/phoenix-ev-eth_6.yaml | 17 - .../release/de/charger/phoenix-ev-eth_7.yaml | 17 - .../release/de/charger/phoenix-ev-eth_8.yaml | 17 - .../release/de/charger/phoenix-ev-ser_0.yaml | 20 - templates/release/de/charger/plugchoice.yaml | 56 + .../release/de/charger/plugchoice_0.yaml | 26 - templates/release/de/charger/pmcc_0.yaml | 11 - templates/release/de/charger/pmcp_0.yaml | 10 - .../porsche-mobile-charger-connect.yaml | 32 + .../charger/porsche-mobile-charger-plus.yaml | 31 + .../release/de/charger/porsche-wallbox.yaml | 39 + .../release/de/charger/porsche-wallbox_0.yaml | 18 - .../release/de/charger/pracht-alpha-xt.yaml | 92 + .../release/de/charger/pracht-alpha_0.yaml | 52 - .../release/de/charger/pracht-alpha_1.yaml | 52 - .../release/de/charger/pracht-alpha_2.yaml | 52 - .../release/de/charger/pracht-alpha_3.yaml | 52 - .../release/de/charger/pracht-mono-xt.yaml | 92 + templates/release/de/charger/pracht-pni.yaml | 92 + .../release/de/charger/pracht-xtplus.yaml | 92 + .../de/charger/pulsares-simplebox.yaml | 41 + templates/release/de/charger/pulsares_0.yaml | 20 - templates/release/de/charger/pulsatrix.yaml | 20 + templates/release/de/charger/pulsatrix_0.yaml | 8 - .../de/charger/qcells-q-home-edrive-a.yaml | 45 + .../release/de/charger/roth-thermoaura.yaml | 64 + .../release/de/charger/roth-thermoterra.yaml | 64 + .../de/charger/schneider-evlink-pro.yaml | 32 + .../de/charger/schneider-evlink-v3_0.yaml | 14 - .../de/charger/schrack-i-charge-cion.yaml | 41 + .../de/charger/senec-wallbox-pro-s.yaml | 45 + .../release/de/charger/senec-wallbox-pro.yaml | 53 + templates/release/de/charger/shelly-1.yaml | 99 + .../release/de/charger/shelly-plug-s.yaml | 99 + .../release/de/charger/shelly-plus-1.yaml | 99 + .../release/de/charger/shelly-pro-1.yaml | 99 + templates/release/de/charger/shelly_0.yaml | 23 - .../de/charger/siemens-versicharge-gen3.yaml | 34 + .../de/charger/skoda-charger-connect.yaml | 39 + .../charger/skoda-charger-pro-eichrecht.yaml | 39 + .../release/de/charger/skoda-charger-pro.yaml | 39 + .../de/charger/skoda-iv-charger-connect.yaml | 41 + .../charger/skoda-iv-charger-connectplus.yaml | 39 + .../release/de/charger/sma-echarger.yaml | 44 + .../release/de/charger/sma-ev-charger.yaml | 44 + .../release/de/charger/smaevcharger_0.yaml | 14 - .../release/de/charger/smaevcharger_1.yaml | 14 - templates/release/de/charger/smartevse_0.yaml | 21 - .../de/charger/smartfox-pro-charger.yaml | 41 + templates/release/de/charger/smartwb.yaml | 19 + templates/release/de/charger/smartwb_0.yaml | 7 - .../de/charger/solaredge-home-ev-charger.yaml | 54 + .../release/de/charger/solax-x3-evc.yaml | 45 + templates/release/de/charger/solax_0.yaml | 24 - templates/release/de/charger/solax_1.yaml | 24 - templates/release/de/charger/solax_2.yaml | 24 - .../de/charger/sonnen-sonnencharger.yaml | 34 + .../charger/spelsberg-wallbox-smart-pro.yaml | 35 + .../de/charger/stark-in-strom-easy.yaml | 41 + .../stiebel-eltron-lwa-lwz-sg-ready.yaml | 42 + .../charger/stiebel-eltron-wpm-sg-ready.yaml | 42 + .../release/de/charger/stiebel-lwa_0.yaml | 15 - .../release/de/charger/stiebel-lwa_1.yaml | 15 - .../release/de/charger/stiebel-wpm_0.yaml | 15 - .../release/de/charger/sungrow-ac011e-01.yaml | 50 + .../release/de/charger/sungrow-ac011e.yaml | 86 + .../release/de/charger/sungrow-ac22e-01.yaml | 50 + templates/release/de/charger/sungrow_0.yaml | 28 - templates/release/de/charger/sungrow_1.yaml | 28 - templates/release/de/charger/tapo_0.yaml | 22 - .../de/charger/tasmota-single-phase.yaml | 99 + templates/release/de/charger/tasmota_0.yaml | 24 - .../de/charger/tecalor-thz-sg-ready.yaml | 42 + .../de/charger/technisat-technivolt.yaml | 35 + .../charger/tesla-wall-connector-gen-3.yaml | 22 + templates/release/de/charger/tessie.yaml | 41 + templates/release/de/charger/tessie_0.yaml | 11 - .../de/charger/tigo-go-ev-charger.yaml | 45 + .../charger/tinkerforge-warp-charger-pro.yaml | 92 + .../tinkerforge-warp-charger-smart.yaml | 92 + .../tinkerforge-warp3-charger-pro.yaml | 81 + .../tinkerforge-warp3-charger-smart.yaml | 79 + .../de/charger/tinkerforge-warp3-smart_0.yaml | 22 - .../de/charger/tinkerforge-warp3_0.yaml | 24 - .../de/charger/tinkerforge-warp_0.yaml | 26 - .../de/charger/tinkerforge-warp_1.yaml | 26 - .../charger/tp-link-h-series-smart-plug.yaml | 66 + .../tp-link-tapo-p-series-smart-plug.yaml | 88 + templates/release/de/charger/tplink_0.yaml | 18 - templates/release/de/charger/trydan_0.yaml | 8 - templates/release/de/charger/twc3_0.yaml | 10 - .../release/de/charger/ubitricity-heinz.yaml | 35 + templates/release/de/charger/v2c-trydan.yaml | 20 + .../charger/vaillant-sensonet-sg-ready.yaml | 63 + templates/release/de/charger/vaillant_0.yaml | 15 - .../release/de/charger/versicharge_0.yaml | 16 - .../de/charger/vestel-connect-plus.yaml | 35 + .../de/charger/vestel-evc04-home-smart.yaml | 35 + templates/release/de/charger/vestel_0.yaml | 17 - templates/release/de/charger/vestel_1.yaml | 17 - templates/release/de/charger/vestel_2.yaml | 17 - templates/release/de/charger/vestel_3.yaml | 17 - templates/release/de/charger/vestel_4.yaml | 17 - .../victron-ev-charging-station-via-gx.yaml | 33 + .../charger/victron-ev-charging-station.yaml | 33 + .../release/de/charger/victron-evcs_0.yaml | 15 - templates/release/de/charger/victron_0.yaml | 15 - .../charger/viessmann-heatpump-sg-ready.yaml | 85 + templates/release/de/charger/viessmann_0.yaml | 19 - .../viridian-ev-evse-epc-2-0-plus.yaml | 48 + .../charger/volkswagen-charger-connect-2.yaml | 39 + .../de/charger/volkswagen-charger-pro-2.yaml | 39 + .../volkswagen-charger-pro-eichrecht-2.yaml | 39 + .../volkswagen-id-charger-connect.yaml | 41 + .../de/charger/volkswagen-id-charger-pro.yaml | 39 + .../release/de/charger/volt-time-one.yaml | 31 + .../de/charger/volt-time-source-2.yaml | 31 + .../de/charger/volt-time-source-2s.yaml | 31 + .../release/de/charger/volt-time-source.yaml | 31 + templates/release/de/charger/volttime_0.yaml | 10 - templates/release/de/charger/volttime_1.yaml | 10 - templates/release/de/charger/volttime_2.yaml | 10 - templates/release/de/charger/volttime_3.yaml | 10 - .../release/de/charger/wallbe-eco-2-0-s.yaml | 35 + templates/release/de/charger/wallbe-eco.yaml | 35 + templates/release/de/charger/wallbe-pro.yaml | 35 + .../charger/wallbox-commander-2-fw-5-x.yaml | 94 + .../de/charger/wallbox-commander-2.yaml | 94 + .../de/charger/wallbox-copper-sb-fw-5-x.yaml | 94 + .../release/de/charger/wallbox-copper-sb.yaml | 94 + .../release/de/charger/wallbox-fw5_0.yaml | 28 - .../release/de/charger/wallbox-fw5_1.yaml | 28 - .../release/de/charger/wallbox-fw5_2.yaml | 28 - .../release/de/charger/wallbox-fw5_3.yaml | 28 - .../de/charger/wallbox-pulsar-max-fw-5-x.yaml | 94 + .../de/charger/wallbox-pulsar-max.yaml | 94 + .../charger/wallbox-pulsar-plus-fw-5-x.yaml | 94 + .../de/charger/wallbox-pulsar-plus.yaml | 94 + .../charger/walther-werke-basic-evo-pro.yaml | 45 + .../release/de/charger/webasto-live.yaml | 35 + .../release/de/charger/webasto-next.yaml | 34 + .../release/de/charger/webasto-next_0.yaml | 13 - .../release/de/charger/webasto-next_1.yaml | 13 - .../release/de/charger/webasto-unite.yaml | 35 + .../de/charger/weidmuller-ac-smart.yaml | 22 + .../de/charger/weidm\303\274ller_0.yaml" | 10 - templates/release/de/charger/wolf-bwl.yaml | 64 + templates/release/de/charger/wolf-bws.yaml | 64 + templates/release/de/charger/zaptec-go-2.yaml | 42 + .../release/de/charger/zaptec-go-ocpp.yaml | 91 + templates/release/de/charger/zaptec-go.yaml | 42 + templates/release/de/charger/zaptec-pro.yaml | 42 + templates/release/de/charger/zaptec_0.yaml | 12 - templates/release/de/charger/zaptec_1.yaml | 12 - templates/release/de/charger/zaptec_2.yaml | 12 - .../de/charger/zewotherm-eu-l-series.yaml | 52 + .../de/charger/zj-beny-bcp-ev-charger.yaml | 86 + templates/release/de/meter/a-tronix.yaml | 151 + templates/release/de/meter/abb-a43.yaml | 61 + templates/release/de/meter/abb-a44.yaml | 61 + templates/release/de/meter/abb-ab_0.yaml | 40 - templates/release/de/meter/abb-b23.yaml | 61 + templates/release/de/meter/abb-b24.yaml | 61 + templates/release/de/meter/ac-elwa-2_0.yaml | 10 - templates/release/de/meter/ac-elwa-e_0.yaml | 10 - templates/release/de/meter/acrel-adw300.yaml | 98 + .../release/de/meter/acrel-adw300_0.yaml | 76 - .../release/de/meter/ads-tec-storaxe.yaml | 53 + .../release/de/meter/alpha-ess-smile_0.yaml | 157 - .../de/meter/alpha-ess-storion-smile.yaml | 215 ++ .../de/meter/ampere-ampere-storagepro.yaml | 211 ++ .../de/meter/anker-micro-inverter.yaml | 73 + templates/release/de/meter/apsystems-ez1.yaml | 22 + .../release/de/meter/apsystems-ez1_0.yaml | 10 - templates/release/de/meter/avm-fritzdect.yaml | 62 + .../de/meter/axitec-axihycon-12-15h.yaml | 150 + .../meter/bernecker-engineering-mpm3pm.yaml | 61 + .../release/de/meter/bge_tech_ds100_0.yaml | 100 - .../release/de/meter/bge_tech_ws100_0.yaml | 100 - templates/release/de/meter/bgetech-ds100.yaml | 122 + templates/release/de/meter/bgetech-ws100.yaml | 122 + .../de/meter/bosch-bpt-s-5-hybrid.yaml | 60 + templates/release/de/meter/bosch-bpt_0.yaml | 39 - .../de/meter/bosswerk-micro-inverter.yaml | 73 + .../de/meter/carlo-gavazzi-em110-111-112.yaml | 61 + .../release/de/meter/carlo-gavazzi-em24.yaml | 64 + .../de/meter/carlo-gavazzi-em24_e1.yaml | 48 + .../de/meter/carlo-gavazzi-em330-em340.yaml | 74 + .../de/meter/carlo-gavazzi-em530-em540.yaml | 74 + .../release/de/meter/carlo-gavazzi-et112.yaml | 61 + .../de/meter/carlo-gavazzi-et330-et340.yaml | 74 + .../de/meter/cfos-powerbrain-meter.yaml | 34 + templates/release/de/meter/cfos_0.yaml | 16 - templates/release/de/meter/cg-em24_0.yaml | 43 - templates/release/de/meter/cg-em24_1.yaml | 43 - templates/release/de/meter/cg-em24_e1_0.yaml | 30 - templates/release/de/meter/cg-em24_e1_1.yaml | 30 - templates/release/de/meter/cg-emt1xx_0.yaml | 40 - templates/release/de/meter/cg-emt1xx_1.yaml | 40 - templates/release/de/meter/cg-emt3xx_0.yaml | 52 - templates/release/de/meter/cg-emt3xx_1.yaml | 52 - templates/release/de/meter/cg-emt3xx_2.yaml | 52 - templates/release/de/meter/cg-emt3xx_3.yaml | 52 - templates/release/de/meter/cg-emt3xx_4.yaml | 52 - templates/release/de/meter/cg-emt3xx_5.yaml | 52 - templates/release/de/meter/demo-battery.yaml | 91 + .../release/de/meter/demo-battery_0.yaml | 25 - templates/release/de/meter/demo-meter.yaml | 114 + templates/release/de/meter/demo-meter_0.yaml | 66 - .../de/meter/deye-3p-hybrid-inverter.yaml | 212 ++ .../de/meter/deye-hp3-hybrid-inverter.yaml | 236 ++ .../release/de/meter/deye-hybrid-3p_0.yaml | 154 - .../release/de/meter/deye-hybrid-3p_1.yaml | 154 - .../release/de/meter/deye-hybrid-hp3_0.yaml | 160 - .../release/de/meter/deye-hybrid-hp3_1.yaml | 160 - templates/release/de/meter/deye-mi_0.yaml | 51 - templates/release/de/meter/deye-mi_1.yaml | 51 - templates/release/de/meter/deye-mi_2.yaml | 51 - templates/release/de/meter/deye-mi_3.yaml | 51 - .../release/de/meter/deye-micro-inverter.yaml | 73 + .../meter/deye-storage-hybrid-inverter.yaml | 177 + .../release/de/meter/deye-storage_0.yaml | 146 - .../release/de/meter/deye-storage_1.yaml | 146 - .../de/meter/deye-string-inverter.yaml | 50 + templates/release/de/meter/deye-string_0.yaml | 28 - templates/release/de/meter/deye-string_1.yaml | 28 - templates/release/de/meter/discovergy.yaml | 49 + templates/release/de/meter/discovergy_0.yaml | 19 - templates/release/de/meter/dsmr.yaml | 47 + templates/release/de/meter/dsmr_0.yaml | 17 - templates/release/de/meter/dzg-dvh4013.yaml | 43 + templates/release/de/meter/dzg_0.yaml | 22 - templates/release/de/meter/e3-dc.yaml | 146 + templates/release/de/meter/e3dc-rscp_0.yaml | 71 - .../de/meter/eastron-sdm120-modbus.yaml | 79 + .../release/de/meter/eastron-sdm120_0.yaml | 58 - .../release/de/meter/eastron-sdm220-230.yaml | 61 + .../de/meter/eastron-sdm220_230_0.yaml | 40 - .../de/meter/eastron-sdm220_230_1.yaml | 40 - .../de/meter/eastron-sdm220_230_2.yaml | 40 - .../de/meter/eastron-sdm630-modbus.yaml | 61 + .../release/de/meter/eastron-sdm72_0.yaml | 40 - .../release/de/meter/eastron-sdm72d-m.yaml | 61 + .../release/de/meter/eastron-sdm72dm-v2.yaml | 61 + templates/release/de/meter/eastron_0.yaml | 40 - templates/release/de/meter/eastron_1.yaml | 40 - templates/release/de/meter/eastron_2.yaml | 40 - templates/release/de/meter/eastron_3.yaml | 40 - templates/release/de/meter/eastron_4.yaml | 40 - .../release/de/meter/enphase-iq-envoy.yaml | 88 + templates/release/de/meter/enphase_0.yaml | 49 - .../de/meter/esphome-dlms-austria_0.yaml | 20 - .../de/meter/esphome-dlms-meter-austria.yaml | 41 + templates/release/de/meter/esphome-dsmr.yaml | 37 + templates/release/de/meter/fenecon.yaml | 104 + templates/release/de/meter/fox-ess-h1_0.yaml | 52 - .../release/de/meter/fox-ess-h3-smart_0.yaml | 154 - templates/release/de/meter/fox-ess-h3_0.yaml | 154 - .../foxess-h1-series-hybrid-inverter.yaml | 74 + .../foxess-h3-series-hybrid-inverter.yaml | 212 ++ ...oxess-h3-smart-series-hybrid-inverter.yaml | 212 ++ templates/release/de/meter/fritzdect_0.yaml | 23 - .../release/de/meter/fronius-gen24_0.yaml | 48 - .../release/de/meter/fronius-gen24_1.yaml | 48 - .../release/de/meter/fronius-ohmpilot.yaml | 37 + .../release/de/meter/fronius-ohmpilot_0.yaml | 16 - .../de/meter/fronius-primo-gen24-plus.yaml | 105 + .../fronius-smartmeter-via-inverter.yaml | 44 + .../de/meter/fronius-solar-api-v1.yaml | 109 + .../de/meter/fronius-solarapi-v1_0.yaml | 58 - .../de/meter/fronius-symo-gen24-plus.yaml | 105 + ...long-solis-hybrid-inverter-rhi-series.yaml | 150 + ...inlong-solis-hybrid-inverter-s-series.yaml | 150 + .../de/meter/ginlong-solis-inverter.yaml | 61 + .../release/de/meter/go-e-controller.yaml | 28 + .../release/de/meter/go-e-controller_0.yaml | 16 - templates/release/de/meter/goodwe-dt_0.yaml | 28 - .../goodwe-et-eh-bh-bt-hybrid-inverter.yaml | 204 ++ .../de/meter/goodwe-goodwe-over-wifi.yaml | 35 + .../release/de/meter/goodwe-hybrid_0.yaml | 154 - .../de/meter/goodwe-sdt-dt-inverter.yaml | 50 + templates/release/de/meter/goodwe-wifi_0.yaml | 23 - .../de/meter/growatt-hybrid-inverter.yaml | 194 ++ .../de/meter/growatt-hybrid-tlxh_0.yaml | 148 - .../release/de/meter/growatt-hybrid_0.yaml | 154 - .../meter/growatt-tl-x-h-hybrid-inverter.yaml | 188 + templates/release/de/meter/homematic-ip.yaml | 121 + templates/release/de/meter/homematic_0.yaml | 64 - .../de/meter/homewizard-kwh-meter.yaml | 28 + .../release/de/meter/homewizard-kwh_0.yaml | 16 - .../de/meter/homewizard-wi-fi-p1-meter.yaml | 22 + templates/release/de/meter/homewizard_0.yaml | 10 - .../release/de/meter/hoymiles-ahoydtu_0.yaml | 11 - ...oymiles-hm-and-hms-series-via-ahoydtu.yaml | 32 + ...oymiles-hm-and-hms-series-via-opendtu.yaml | 22 + .../release/de/meter/hoymiles-opendtu_0.yaml | 10 - .../release/de/meter/huawei-dongle_0.yaml | 20 - templates/release/de/meter/huawei-emma.yaml | 95 + templates/release/de/meter/huawei-emma_0.yaml | 68 - .../release/de/meter/huawei-smartlogger.yaml | 133 + .../de/meter/huawei-smartlogger_0.yaml | 79 - .../de/meter/huawei-sun2000-sdongle.yaml | 47 + .../release/de/meter/huawei-sun2000.yaml | 240 ++ .../release/de/meter/huawei-sun2000_0.yaml | 164 - .../release/de/meter/iammeter-wem3080.yaml | 38 + .../iammeter-wem3080t-wem3046t-wem3050t.yaml | 38 + templates/release/de/meter/iammeter_0.yaml | 26 - templates/release/de/meter/iammeter_1.yaml | 26 - .../de/meter/igen-tech-solarman-logger.yaml | 42 + .../release/de/meter/inepro-pro380-mod.yaml | 61 + templates/release/de/meter/inepro_0.yaml | 40 - templates/release/de/meter/iometer.yaml | 21 + templates/release/de/meter/iometer_0.yaml | 9 - .../release/de/meter/janitza-b-series.yaml | 74 + .../release/de/meter/janitza-umg-series.yaml | 74 + templates/release/de/meter/janitza_0.yaml | 52 - .../release/de/meter/keba-kecontact-e10.yaml | 33 + .../release/de/meter/keba-kecontact_0.yaml | 15 - .../de/meter/kostal-energy-meter-c-kem-c.yaml | 74 + .../de/meter/kostal-energy-meter-p-kem-p.yaml | 61 + .../de/meter/kostal-ksem-inverter_0.yaml | 17 - templates/release/de/meter/kostal-ksem_0.yaml | 15 - .../release/de/meter/kostal-piko-ba.yaml | 28 + .../release/de/meter/kostal-piko-hybrid.yaml | 59 + .../de/meter/kostal-piko-hybrid_0.yaml | 38 - .../release/de/meter/kostal-piko-legacy.yaml | 42 + .../de/meter/kostal-piko-legacy_0.yaml | 12 - .../release/de/meter/kostal-piko-mp-plus.yaml | 22 + .../de/meter/kostal-piko-mp-plus_0.yaml | 10 - .../de/meter/kostal-piko-mp-plus_1.yaml | 10 - .../release/de/meter/kostal-piko-pv_0.yaml | 16 - templates/release/de/meter/kostal-piko.yaml | 28 + .../de/meter/kostal-plenticore-gen2_0.yaml | 59 - ...cl-grid-charging-of-the-house-battery.yaml | 122 + .../de/meter/kostal-plenticore-hybrid.yaml | 133 + .../release/de/meter/kostal-plenticore_0.yaml | 61 - ...ostal-smart-energy-meter-via-inverter.yaml | 35 + .../de/meter/kostal-smart-energy-meter.yaml | 33 + .../release/de/meter/lg-ess-home-15.yaml | 111 + .../release/de/meter/lg-ess-home-15_0.yaml | 54 - .../release/de/meter/lg-ess-home-8-10.yaml | 114 + .../release/de/meter/lg-ess-home-8-10_0.yaml | 57 - .../release/de/meter/loxone-miniserver.yaml | 92 + templates/release/de/meter/loxone_0.yaml | 44 - .../de/meter/m-tec-energy-butler-gen2.yaml | 79 + .../de/meter/m-tec-energy-butler-gen3.yaml | 178 + .../meter/marstek-venus-battery-storage.yaml | 112 + .../release/de/meter/marstek-venus_0.yaml | 46 - .../release/de/meter/mhendriks-p1-dongle.yaml | 37 + templates/release/de/meter/mpm3pm_0.yaml | 40 - .../release/de/meter/mtec-eb-gen2_0.yaml | 58 - .../release/de/meter/mtec-eb-gen3_0.yaml | 147 - .../release/de/meter/my-pv-ac-elwa-2.yaml | 22 + .../release/de/meter/my-pv-ac-elwa-e.yaml | 22 + templates/release/de/meter/my-pv-ac-thor.yaml | 22 + .../release/de/meter/my-pv-wifi-meter.yaml | 33 + .../release/de/meter/mypv-wifi-meter_0.yaml | 15 - .../release/de/meter/mystrom-switch.yaml | 29 + templates/release/de/meter/mystrom_0.yaml | 17 - templates/release/de/meter/openems.yaml | 104 + templates/release/de/meter/openems_0.yaml | 47 - templates/release/de/meter/openems_1.yaml | 47 - .../release/de/meter/orno-or-we-516.yaml | 61 + .../release/de/meter/orno-or-we-517.yaml | 61 + templates/release/de/meter/orno_0.yaml | 40 - .../de/meter/p1monitor-p1-monitor.yaml | 22 + templates/release/de/meter/p1monitor_0.yaml | 10 - templates/release/de/meter/plexlog.yaml | 97 + templates/release/de/meter/plexlog_0.yaml | 70 - templates/release/de/meter/powerdog.yaml | 43 + templates/release/de/meter/powerdog_0.yaml | 25 - .../release/de/meter/powerfox-poweropti.yaml | 62 + .../de/meter/powerfox-poweropti_0.yaml | 32 - .../de/meter/qcells-hybrid-cloud_0.yaml | 49 - .../meter/qcells-hybrid-inverter-cloud.yaml | 79 + .../de/meter/qcells-q-home-ess-hyb-g3.yaml | 225 ++ templates/release/de/meter/rct-power.yaml | 118 + templates/release/de/meter/rct-power_0.yaml | 52 - .../meter/saia-burgess-controls-sbc-ale3.yaml | 61 + .../meter/saia-burgess-controls-sbc-awd3.yaml | 61 + .../saj-h1-series-hybrid-solar-inverter.yaml | 110 + templates/release/de/meter/saj-h1_0.yaml | 74 - .../saj-h2-series-hybrid-solar-inverter.yaml | 211 ++ templates/release/de/meter/saj-h2_0.yaml | 153 - templates/release/de/meter/saj-h2_1.yaml | 153 - .../meter/saj-r5-series-solar-inverter.yaml | 43 + templates/release/de/meter/saj-r5_0.yaml | 22 - .../release/de/meter/sax-homespeicher.yaml | 44 + templates/release/de/meter/sax_0.yaml | 26 - templates/release/de/meter/sbc-axx3_0.yaml | 40 - .../schneider-electric-iem3xxx-modbus.yaml | 61 + .../release/de/meter/schneider-iem3000_0.yaml | 40 - templates/release/de/meter/senec-home.yaml | 75 + templates/release/de/meter/senec-home_0.yaml | 45 - .../senergy-se-4-5-6ktl-s1-g2-inverter.yaml | 33 + templates/release/de/meter/senergy_0.yaml | 15 - templates/release/de/meter/senergy_1.yaml | 15 - .../release/de/meter/shelly-1pm-mini.yaml | 71 + templates/release/de/meter/shelly-1pm.yaml | 71 + templates/release/de/meter/shelly-1pm_0.yaml | 32 - templates/release/de/meter/shelly-3em.yaml | 73 + templates/release/de/meter/shelly-3em_0.yaml | 43 - templates/release/de/meter/shelly-em.yaml | 71 + templates/release/de/meter/shelly-plug-s.yaml | 71 + .../release/de/meter/shelly-pm-mini.yaml | 71 + .../release/de/meter/shelly-pro-1pm.yaml | 71 + .../release/de/meter/shelly-pro-3-em.yaml | 58 + .../meter/shelly-pro-3em-monophase-mode.yaml | 71 + .../release/de/meter/shelly-pro-3em_0.yaml | 28 - templates/release/de/meter/shelly-pro-em.yaml | 71 + .../release/de/meter/siemens-7kt1665.yaml | 74 + .../release/de/meter/siemens-7kt1665_0.yaml | 52 - .../siemens-junelight-smart-battery.yaml | 98 + .../release/de/meter/siemens-junelight_0.yaml | 71 - .../release/de/meter/siemens-pac-2200.yaml | 74 + .../release/de/meter/siemens-pac2200_0.yaml | 52 - ...gen-hybrid-sigen-pv-max-sigenstore-ec.yaml | 91 + templates/release/de/meter/sigenergy_0.yaml | 52 - .../release/de/meter/slimmelezer-V2_0.yaml | 12 - .../de/meter/slimmelezer-luxembourg_0.yaml | 12 - templates/release/de/meter/slimmelezer_0.yaml | 16 - templates/release/de/meter/slimmelezer_1.yaml | 16 - templates/release/de/meter/slimmelezer_2.yaml | 16 - .../release/de/meter/sma-data-manager.yaml | 97 + .../release/de/meter/sma-data-manager_0.yaml | 70 - .../release/de/meter/sma-energy-meter.yaml | 49 + .../release/de/meter/sma-energy-meter_0.yaml | 28 - .../release/de/meter/sma-home-manager_0.yaml | 18 - templates/release/de/meter/sma-hybrid_0.yaml | 51 - .../de/meter/sma-inverter-modbus_0.yaml | 15 - .../de/meter/sma-inverter-speedwire.yaml | 62 + .../de/meter/sma-inverter-speedwire_0.yaml | 32 - .../de/meter/sma-sbs-15-25-modbus_0.yaml | 29 - .../release/de/meter/sma-sbs-modbus_0.yaml | 29 - .../release/de/meter/sma-si-modbus_0.yaml | 29 - .../sma-smart-energy-hybrid-inverter.yaml | 105 + ...-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml | 74 + ...-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml | 74 + .../de/meter/sma-sunny-home-manager-2-0.yaml | 39 + .../de/meter/sma-sunny-island-modbus.yaml | 74 + templates/release/de/meter/sma-webbox.yaml | 33 + templates/release/de/meter/sma-webbox_0.yaml | 15 - .../de/meter/sma-wechselrichter-modbus.yaml | 33 + templates/release/de/meter/smartfox-box.yaml | 37 + .../release/de/meter/smartfox-em2_0.yaml | 43 - .../de/meter/smartfox-light-em2-firmware.yaml | 64 + .../release/de/meter/smartfox-pro-2.yaml | 64 + .../de/meter/smartfox-pro-light-2.yaml | 64 + .../release/de/meter/smartfox-pro-light.yaml | 64 + templates/release/de/meter/smartfox-pro.yaml | 64 + .../de/meter/smartfox-reg-extended.yaml | 37 + templates/release/de/meter/smartfox-reg.yaml | 37 + templates/release/de/meter/smartfox_0.yaml | 25 - .../release/de/meter/sofarsolar-g3_0.yaml | 154 - .../release/de/meter/sofarsolar-g3_1.yaml | 154 - .../release/de/meter/sofarsolar-g3_2.yaml | 154 - .../release/de/meter/sofarsolar-g3_3.yaml | 154 - .../de/meter/sofarsolar-hybrid-inverter.yaml | 177 + .../de/meter/sofarsolar-hyd-3-6k-ep.yaml | 212 ++ .../de/meter/sofarsolar-hyd-5-20k-3ph.yaml | 212 ++ .../release/de/meter/sofarsolar-inverter.yaml | 177 + .../de/meter/sofarsolar-sofar-5-24ktl-g3.yaml | 212 ++ .../de/meter/sofarsolar-sofar-80-136ktl.yaml | 212 ++ templates/release/de/meter/sofarsolar_0.yaml | 146 - templates/release/de/meter/sofarsolar_1.yaml | 146 - .../de/meter/solaranzeige-solaranzeige.yaml | 100 + .../release/de/meter/solaranzeige_0.yaml | 43 - .../de/meter/solaredge-hybrid-inverter.yaml | 219 ++ .../release/de/meter/solaredge-hybrid_0.yaml | 161 - .../release/de/meter/solaredge-inverter.yaml | 87 + .../de/meter/solaredge-inverter_0.yaml | 56 - templates/release/de/meter/solarlog.yaml | 42 + templates/release/de/meter/solarlog_0.yaml | 21 - templates/release/de/meter/solarman_0.yaml | 12 - ...rmax-max-storage-max-storage-ultimate.yaml | 120 + .../de/meter/solarmax-maxstorage_0.yaml | 75 - .../release/de/meter/solarmax-smt_0.yaml | 15 - .../de/meter/solarmax-solarmax-smt.yaml | 33 + .../de/meter/solarmax-sp-series-inverter.yaml | 33 + .../de/meter/solarwatt-energymanager-pro.yaml | 59 + .../de/meter/solarwatt-energymanager.yaml | 59 + .../release/de/meter/solarwatt-flex_0.yaml | 41 - .../de/meter/solarwatt-manager-flex.yaml | 62 + ...yreserve-matrix-lan-oder-powergateway.yaml | 74 + .../meter/solarwatt-myreserve-matrix_0.yaml | 44 - .../release/de/meter/solarwatt-myreserve.yaml | 59 + templates/release/de/meter/solarwatt_0.yaml | 38 - templates/release/de/meter/solarwatt_1.yaml | 38 - .../de/meter/solax-hybrid-cloud_0.yaml | 49 - .../de/meter/solax-hybrid-inverter-cloud.yaml | 79 + .../de/meter/solax-hybrid-x1-x3-g3-g4.yaml | 225 ++ .../de/meter/solax-inverter-cloud.yaml | 37 + .../de/meter/solax-inverter-cloud_0.yaml | 16 - templates/release/de/meter/solax_0.yaml | 158 - templates/release/de/meter/solax_1.yaml | 158 - templates/release/de/meter/solinteng.yaml | 151 + .../release/de/meter/solis-hybrid-s_0.yaml | 111 - .../release/de/meter/solis-hybrid-s_1.yaml | 111 - .../release/de/meter/solis-hybrid_0.yaml | 111 - templates/release/de/meter/solis_0.yaml | 40 - .../release/de/meter/sonnen-comfort.yaml | 96 + templates/release/de/meter/sonnen-eco-5.yaml | 96 + templates/release/de/meter/sonnen-eco-6.yaml | 96 + .../release/de/meter/sonnen-oem-6-5.yaml | 96 + .../de/meter/sonnen-sonnenbatterie.yaml | 111 + .../de/meter/sonnenbatterie-eco56_0.yaml | 48 - .../release/de/meter/sonnenbatterie_0.yaml | 54 - templates/release/de/meter/st-ems.yaml | 151 + .../release/de/meter/steca-coolcept-flex.yaml | 22 + templates/release/de/meter/storaxe_0.yaml | 26 - .../release/de/meter/sungrow-hybrid_0.yaml | 157 - .../release/de/meter/sungrow-inverter_0.yaml | 52 - .../de/meter/sungrow-sg-series-inverter.yaml | 74 + .../sungrow-sh-series-hybrid-inverter.yaml | 215 ++ .../de/meter/sunspec-battery-control_0.yaml | 55 - .../de/meter/sunspec-battery-model-124.yaml | 94 + .../de/meter/sunspec-battery-model-802.yaml | 104 + .../de/meter/sunspec-hybrid-inverter.yaml | 187 + .../release/de/meter/sunspec-hybrid_0.yaml | 147 - .../de/meter/sunspec-inverter-control_0.yaml | 54 - .../release/de/meter/sunspec-inverter.yaml | 177 + .../release/de/meter/sunspec-inverter_0.yaml | 146 - templates/release/de/meter/sunspec-meter.yaml | 43 + .../release/de/meter/sunspec-meter_0.yaml | 25 - .../release/de/meter/sunspec-meter_1.yaml | 26 - .../de/meter/sunsynk-3p-hybrid-inverter.yaml | 212 ++ .../de/meter/sunsynk-hp3-hybrid-inverter.yaml | 236 ++ .../de/meter/sunsynk-micro-inverter.yaml | 73 + .../sunsynk-storage-hybrid-inverter.yaml | 177 + .../de/meter/sunsynk-string-inverter.yaml | 50 + templates/release/de/meter/sunway.yaml | 151 + templates/release/de/meter/tapo_0.yaml | 13 - templates/release/de/meter/tasmota-3p_0.yaml | 39 - ...l-ir-reader-for-smartmeters-e-g-hichi.yaml | 91 + templates/release/de/meter/tasmota-sml_0.yaml | 61 - ...asmota-tasmota-1-phase-plus-sml-meter.yaml | 80 + .../release/de/meter/tasmota-three-phase.yaml | 69 + templates/release/de/meter/tasmota_0.yaml | 41 - .../release/de/meter/tesla-powerwall.yaml | 127 + .../release/de/meter/tesla-powerwall_0.yaml | 70 - templates/release/de/meter/thor_0.yaml | 10 - templates/release/de/meter/tibber-pulse.yaml | 33 + .../release/de/meter/tibber-pulse_0.yaml | 12 - .../de/meter/tp-link-h-series-smart-plug.yaml | 23 + .../tp-link-tapo-p-series-smart-plug.yaml | 43 + templates/release/de/meter/tplink_0.yaml | 11 - templates/release/de/meter/tq-em420_0.yaml | 13 - templates/release/de/meter/tq-em_0.yaml | 12 - .../meter/tq-energy-manager-em2xx-em3xx.yaml | 42 + .../de/meter/tq-energy-manager-em420.yaml | 52 + templates/release/de/meter/varta-element.yaml | 76 + .../release/de/meter/varta-pulse-neo.yaml | 76 + templates/release/de/meter/varta-pulse.yaml | 76 + templates/release/de/meter/varta_0.yaml | 46 - templates/release/de/meter/victron-em24.yaml | 64 + .../release/de/meter/victron-em24_e1.yaml | 48 + .../release/de/meter/victron-em530-em540.yaml | 74 + .../release/de/meter/victron-energy.yaml | 122 + .../release/de/meter/victron-energy_0.yaml | 56 - templates/release/de/meter/victron-et340.yaml | 74 + .../release/de/meter/volkszaehler-http_0.yaml | 12 - .../de/meter/volkszaehler-importexport_0.yaml | 13 - .../release/de/meter/volkszaehler-ws_0.yaml | 14 - ...olkszahler-http-api-import-and-export.yaml | 43 + .../de/meter/volkszahler-http-api.yaml | 33 + .../de/meter/volkszahler-websocket-api.yaml | 44 + templates/release/de/meter/vzlogger.yaml | 159 + templates/release/de/meter/vzlogger_0.yaml | 30 - templates/release/de/meter/wago-879-30xx.yaml | 61 + .../release/de/meter/wago-879-30xx_0.yaml | 40 - templates/release/de/meter/wattsonic.yaml | 151 + templates/release/de/meter/wattsonic_0.yaml | 112 - templates/release/de/meter/wattsonic_1.yaml | 112 - templates/release/de/meter/wattsonic_2.yaml | 112 - templates/release/de/meter/wattsonic_3.yaml | 112 - templates/release/de/meter/wattsonic_4.yaml | 112 - .../de/meter/weidmuller-em110-rtu-2p.yaml | 61 + .../de/meter/weidmuller-em111-rtu-2p.yaml | 61 + .../de/meter/weidmuller-em120-rtu-2p.yaml | 61 + .../de/meter/weidmuller-em122-rtu-2p.yaml | 61 + .../de/meter/youless-energy-monitor.yaml | 31 + templates/release/de/meter/youless_0.yaml | 19 - .../de/meter/zcs-azzurro-hybrid-inverter.yaml | 177 + .../de/meter/zcs-azzurro-inverter.yaml | 177 + .../release/de/meter/zendure-hyper-2000.yaml | 88 + templates/release/de/meter/zendure_0.yaml | 40 - ...idwijk-slimmelezer-plus-in-luxembourg.yaml | 24 + .../meter/zuidwijk-slimmelezer-plus-v2.yaml | 24 + .../de/meter/zuidwijk-slimmelezer-plus.yaml | 37 + .../release/de/tariff/amber-electric.yaml | 77 + templates/release/de/tariff/amber_0.yaml | 20 - templates/release/de/tariff/awattar.yaml | 55 + templates/release/de/tariff/awattar_0.yaml | 16 - .../electricity-maps-commercial-api.yaml | 44 + .../de/tariff/electricity-maps-free-api.yaml | 34 + .../de/tariff/electricitymaps-free_0.yaml | 13 - .../release/de/tariff/electricitymaps_0.yaml | 14 - templates/release/de/tariff/energinet.yaml | 56 + templates/release/de/tariff/energinet_0.yaml | 17 - .../de/tariff/energy-charts-api_0.yaml | 19 - templates/release/de/tariff/enever.yaml | 77 + templates/release/de/tariff/enever_0.yaml | 20 - templates/release/de/tariff/entso-e.yaml | 70 + templates/release/de/tariff/entsoe_0.yaml | 22 - .../release/de/tariff/forecast-solar.yaml | 101 + .../release/de/tariff/forecast-solar_0.yaml | 26 - .../release/de/tariff/fraunhofer-ise.yaml | 58 + .../release/de/tariff/green-grid-compass.yaml | 34 + .../de/tariff/green-grid-compass_0.yaml | 13 - .../de/tariff/groupe-e-vario-plus.yaml | 46 + templates/release/de/tariff/groupe-e_0.yaml | 16 - .../release/de/tariff/grunstromindex.yaml | 34 + .../de/tariff/gr\303\274nstromindex_0.yaml" | 13 - .../release/de/tariff/national-grid-eso.yaml | 31 + templates/release/de/tariff/ngeso_0.yaml | 10 - .../de/tariff/nordpool-spot-prices.yaml | 69 + templates/release/de/tariff/nordpool_0.yaml | 21 - .../release/de/tariff/octopus-api_0.yaml | 13 - .../release/de/tariff/octopus-energy-api.yaml | 34 + .../tariff/octopus-energy-product-code.yaml | 42 + .../de/tariff/octopus-productcode_0.yaml | 12 - templates/release/de/tariff/open-meteo.yaml | 141 + templates/release/de/tariff/open-meteo_0.yaml | 30 - templates/release/de/tariff/ostrom.yaml | 44 + templates/release/de/tariff/ostrom_0.yaml | 14 - templates/release/de/tariff/pun-orario.yaml | 47 + templates/release/de/tariff/pun_0.yaml | 17 - .../de/tariff/smartenergy-smartcontrol.yaml | 45 + .../release/de/tariff/smartenergy_0.yaml | 15 - templates/release/de/tariff/solcast.yaml | 68 + templates/release/de/tariff/solcast_0.yaml | 20 - .../release/de/tariff/spotty-energie.yaml | 67 + .../release/de/tariff/spottyenergy_0.yaml | 19 - templates/release/de/tariff/tibber.yaml | 69 + templates/release/de/tariff/tibber_0.yaml | 21 - .../de/tariff/victron-vrm-solar-forecast.yaml | 49 + templates/release/de/tariff/victron_0.yaml | 19 - templates/release/de/vehicle/aiways.yaml | 147 + templates/release/de/vehicle/aiways_0.yaml | 27 - templates/release/de/vehicle/audi.yaml | 147 + templates/release/de/vehicle/audi_0.yaml | 27 - templates/release/de/vehicle/bmw.yaml | 191 ++ templates/release/de/vehicle/bmw_0.yaml | 35 - templates/release/de/vehicle/carwings_0.yaml | 28 - templates/release/de/vehicle/citroen.yaml | 161 + templates/release/de/vehicle/citroen_0.yaml | 32 - templates/release/de/vehicle/cupra_0.yaml | 30 - templates/release/de/vehicle/dacia.yaml | 167 + templates/release/de/vehicle/dacia_0.yaml | 29 - templates/release/de/vehicle/ds.yaml | 161 + templates/release/de/vehicle/ds_0.yaml | 32 - templates/release/de/vehicle/enyaq_0.yaml | 30 - templates/release/de/vehicle/evnotify.yaml | 127 + templates/release/de/vehicle/evnotify_0.yaml | 25 - templates/release/de/vehicle/fiat.yaml | 178 + templates/release/de/vehicle/fiat_0.yaml | 31 - templates/release/de/vehicle/fiat_1.yaml | 31 - templates/release/de/vehicle/flobz_0.yaml | 28 - .../release/de/vehicle/ford-connect_0.yaml | 31 - templates/release/de/vehicle/ford.yaml | 169 + .../vehicle/generic-vehicle-without-api.yaml | 105 + .../release/de/vehicle/hyundai-bluelink.yaml | 161 + templates/release/de/vehicle/hyundai_0.yaml | 32 - .../release/de/vehicle/ioBroker.bmw_0.yaml | 30 - .../release/de/vehicle/iobroker-bmw.yaml | 159 + templates/release/de/vehicle/iso15118.yaml | 112 + templates/release/de/vehicle/iso15118_0.yaml | 28 - templates/release/de/vehicle/jeep.yaml | 178 + .../release/de/vehicle/kia-bluelink.yaml | 161 + templates/release/de/vehicle/kia_0.yaml | 32 - .../release/de/vehicle/mercedes-benz.yaml | 172 + templates/release/de/vehicle/mercedes_0.yaml | 34 - templates/release/de/vehicle/mg.yaml | 157 + templates/release/de/vehicle/mg2mqtt.yaml | 140 + templates/release/de/vehicle/mg2mqtt_0.yaml | 29 - templates/release/de/vehicle/mg_0.yaml | 28 - templates/release/de/vehicle/mini.yaml | 191 ++ templates/release/de/vehicle/mini_0.yaml | 35 - templates/release/de/vehicle/mz2mqtt.yaml | 128 + templates/release/de/vehicle/mz2mqtt_0.yaml | 26 - .../release/de/vehicle/nissan-ariya.yaml | 148 + .../release/de/vehicle/nissan-ariya_0.yaml | 28 - .../de/vehicle/nissan-leaf-pre-2019.yaml | 148 + templates/release/de/vehicle/nissan-leaf.yaml | 148 + templates/release/de/vehicle/nissan_0.yaml | 28 - .../release/de/vehicle/niu-e-scooter.yaml | 71 + .../release/de/vehicle/niu-e-scooter_0.yaml | 14 - templates/release/de/vehicle/offline_0.yaml | 21 - templates/release/de/vehicle/opel.yaml | 161 + templates/release/de/vehicle/opel_0.yaml | 32 - .../open-vehicle-monitoring-system.yaml | 160 + templates/release/de/vehicle/ovms_0.yaml | 31 - templates/release/de/vehicle/peugeot.yaml | 161 + templates/release/de/vehicle/peugeot_0.yaml | 32 - templates/release/de/vehicle/polestar.yaml | 148 + templates/release/de/vehicle/polestar_0.yaml | 28 - .../de/vehicle/psa-car-controller.yaml | 139 + templates/release/de/vehicle/renault.yaml | 157 + templates/release/de/vehicle/renault_0.yaml | 28 - ...ect-gen3-ateca-leon-formentor-tarraco.yaml | 148 + ...aconnect-gen4-born-formentor-tavascan.yaml | 168 + templates/release/de/vehicle/seat_0.yaml | 28 - templates/release/de/vehicle/skoda-enyaq.yaml | 159 + templates/release/de/vehicle/smart-1.yaml | 168 + templates/release/de/vehicle/smart-eq.yaml | 173 + .../release/de/vehicle/smart-hello_0.yaml | 30 - templates/release/de/vehicle/smart_0.yaml | 35 - templates/release/de/vehicle/tesla-ble.yaml | 140 + templates/release/de/vehicle/tesla-ble_0.yaml | 29 - templates/release/de/vehicle/tesla.yaml | 195 ++ templates/release/de/vehicle/tesla_0.yaml | 48 - templates/release/de/vehicle/teslalogger.yaml | 140 + .../release/de/vehicle/teslalogger_0.yaml | 29 - templates/release/de/vehicle/teslamate.yaml | 118 + templates/release/de/vehicle/teslamate_0.yaml | 25 - templates/release/de/vehicle/tessie.yaml | 129 + templates/release/de/vehicle/tessie_0.yaml | 27 - templates/release/de/vehicle/toyota.yaml | 150 + templates/release/de/vehicle/toyota_0.yaml | 30 - templates/release/de/vehicle/tronity.yaml | 149 + templates/release/de/vehicle/tronity_0.yaml | 29 - .../de/vehicle/volkswagen-we-connect-id.yaml | 181 + .../release/de/vehicle/volvo-connected_0.yaml | 40 - templates/release/de/vehicle/volvo.yaml | 169 + templates/release/de/vehicle/volvo2mqtt.yaml | 129 + .../release/de/vehicle/volvo2mqtt_0.yaml | 27 - templates/release/de/vehicle/vw_0.yaml | 34 - .../release/de/vehicle/zero-motorcycles.yaml | 147 + templates/release/de/vehicle/zero_0.yaml | 27 - templates/release/en/charger/Kathrein_0.yaml | 17 - templates/release/en/charger/Kathrein_1.yaml | 17 - templates/release/en/charger/Kathrein_2.yaml | 17 - templates/release/en/charger/Kathrein_3.yaml | 17 - templates/release/en/charger/Kathrein_4.yaml | 17 - templates/release/en/charger/Kathrein_5.yaml | 17 - .../release/en/charger/abb-terra-ac-ocpp.yaml | 88 + .../release/en/charger/abb-terra-ac.yaml | 52 + templates/release/en/charger/abb_0.yaml | 30 - .../en/charger/abl-em4-single-ocpp.yaml | 86 + .../en/charger/abl-em4-single-sbcx.yaml | 52 + .../release/en/charger/abl-em4-twin-ocpp.yaml | 86 + .../release/en/charger/abl-em4-twin-sbcx.yaml | 52 + templates/release/en/charger/abl-em4_0.yaml | 25 - templates/release/en/charger/abl-emh1.yaml | 53 + .../release/en/charger/abl-emh2-ocpp.yaml | 86 + templates/release/en/charger/abl-emh2.yaml | 53 + .../release/en/charger/abl-emh3-ocpp.yaml | 86 + templates/release/en/charger/abl_0.yaml | 23 - templates/release/en/charger/abl_1.yaml | 23 - templates/release/en/charger/abl_2.yaml | 23 - templates/release/en/charger/ac-elwa-2_0.yaml | 16 - templates/release/en/charger/ac-thor_0.yaml | 17 - templates/release/en/charger/ac-thor_1.yaml | 17 - .../release/en/charger/alfen-eve-ocpp.yaml | 86 + templates/release/en/charger/alfen-eve.yaml | 35 + templates/release/en/charger/alfen_0.yaml | 17 - .../release/en/charger/alpha-innotec.yaml | 63 + .../en/charger/alphatec-ladesaule-twin.yaml | 44 + .../en/charger/alphatec-wallbox-mini.yaml | 44 + .../en/charger/alphatec-wallbox-power.yaml | 44 + templates/release/en/charger/alphatec_0.yaml | 23 - templates/release/en/charger/alphatec_1.yaml | 23 - templates/release/en/charger/alphatec_2.yaml | 23 - templates/release/en/charger/alphatec_3.yaml | 23 - .../release/en/charger/amperfied-solar_0.yaml | 15 - .../amperfied-wallbox-connect-business.yaml | 33 + .../amperfied-wallbox-connect-home.yaml | 33 + .../amperfied-wallbox-connect-solar.yaml | 33 + .../amperfied-wallbox-energy-control.yaml | 45 + templates/release/en/charger/amperfied_0.yaml | 15 - templates/release/en/charger/amperfied_1.yaml | 15 - templates/release/en/charger/ampure-next.yaml | 34 + .../release/en/charger/ampure-unite.yaml | 35 + .../release/en/charger/audi-wallbox-plus.yaml | 41 + .../release/en/charger/audi-wallbox-pro.yaml | 39 + .../release/en/charger/autel-ac-compact.yaml | 94 + .../en/charger/autel-ac-maxicharger.yaml | 94 + .../en/charger/autoaid-business-wallbox.yaml | 86 + .../charger/autoaid-intelligent-wallbox.yaml | 86 + .../release/en/charger/avm-fritzdect.yaml | 99 + .../release/en/charger/bender-cc612.yaml | 35 + .../release/en/charger/bender-cc613.yaml | 35 + templates/release/en/charger/bender-cc_0.yaml | 17 - templates/release/en/charger/bender-cc_1.yaml | 17 - .../release/en/charger/bender-cc_10.yaml | 17 - .../release/en/charger/bender-cc_11.yaml | 17 - .../release/en/charger/bender-cc_12.yaml | 17 - .../release/en/charger/bender-cc_13.yaml | 17 - .../release/en/charger/bender-cc_14.yaml | 17 - .../release/en/charger/bender-cc_15.yaml | 17 - templates/release/en/charger/bender-cc_2.yaml | 17 - templates/release/en/charger/bender-cc_3.yaml | 17 - templates/release/en/charger/bender-cc_4.yaml | 17 - templates/release/en/charger/bender-cc_5.yaml | 17 - templates/release/en/charger/bender-cc_6.yaml | 17 - templates/release/en/charger/bender-cc_7.yaml | 17 - templates/release/en/charger/bender-cc_8.yaml | 17 - templates/release/en/charger/bender-cc_9.yaml | 17 - .../release/en/charger/bender-icc1314.yaml | 35 + .../release/en/charger/bender-icc1324.yaml | 35 + .../release/en/charger/bender-icc_0.yaml | 17 - .../release/en/charger/bender-icc_1.yaml | 17 - .../release/en/charger/bender-icc_2.yaml | 17 - .../release/en/charger/bender-icc_3.yaml | 17 - .../release/en/charger/bmw-i-wallbox.yaml | 54 + .../release/en/charger/bosch-sg-ready.yaml | 53 + .../release/en/charger/bosch-x-change.yaml | 46 + .../charger/buderus-logamatic-hmc-20-z.yaml | 64 + .../en/charger/buderus-logamatic-hmc-20.yaml | 64 + .../release/en/charger/buderus-sg-ready.yaml | 53 + .../en/charger/cfos-power-brain-solar.yaml | 28 + .../release/en/charger/cfos-power-brain.yaml | 28 + templates/release/en/charger/cfos_0.yaml | 16 - templates/release/en/charger/cfos_1.yaml | 16 - .../release/en/charger/charge-amps-halo.yaml | 86 + .../release/en/charger/compleo-ebox.yaml | 33 + .../en/charger/cta-all-in-one-aeroplus.yaml | 64 + templates/release/en/charger/cubos-c11e.yaml | 35 + templates/release/en/charger/cubos-c22e.yaml | 35 + .../en/charger/cupra-charger-connect-2.yaml | 39 + .../en/charger/cupra-charger-connect.yaml | 41 + .../en/charger/cupra-charger-pro-2.yaml | 39 + .../cupra-charger-pro-eichrecht-2.yaml | 39 + .../release/en/charger/cupra-charger-pro.yaml | 39 + .../en/charger/dadapower-premium-wallbox.yaml | 33 + templates/release/en/charger/dadapower_0.yaml | 15 - .../release/en/charger/daheimladen-mb_0.yaml | 11 - .../en/charger/daheimladen-wallbox.yaml | 32 + .../en/charger/daikin-homehub-sg-ready.yaml | 42 + .../release/en/charger/daikin-homehub_0.yaml | 15 - .../en/charger/delta-ac-max-basic.yaml | 82 + .../en/charger/delta-ac-max-smart.yaml | 82 + .../en/charger/delta-slim-charger.yaml | 82 + .../en/charger/delta-ultra-fast-charger.yaml | 82 + templates/release/en/charger/delta_0.yaml | 51 - templates/release/en/charger/delta_1.yaml | 51 - templates/release/en/charger/delta_2.yaml | 51 - templates/release/en/charger/delta_3.yaml | 51 - .../release/en/charger/demo-charger.yaml | 68 + .../release/en/charger/demo-charger_0.yaml | 20 - .../release/en/charger/e-on-drive-ebox.yaml | 33 + .../release/en/charger/e-on-drive-vbox.yaml | 35 + .../en/charger/e3-dc-easy-connect.yaml | 35 + .../release/en/charger/easee-charge-core.yaml | 62 + .../release/en/charger/easee-charge-lite.yaml | 62 + .../release/en/charger/easee-charge.yaml | 62 + templates/release/en/charger/easee-home.yaml | 62 + templates/release/en/charger/easee_0.yaml | 14 - templates/release/en/charger/easee_1.yaml | 14 - templates/release/en/charger/easee_2.yaml | 14 - templates/release/en/charger/easee_3.yaml | 14 - .../release/en/charger/ebee-wallbox.yaml | 35 + .../release/en/charger/echarge-cph1.yaml | 37 + .../release/en/charger/echarge-cph2.yaml | 21 + .../release/en/charger/echarge-cpm2.yaml | 21 + .../charger/ecoharmony-evse-epc-2-0-plus.yaml | 48 + .../en/charger/edgetech-smart-evse.yaml | 42 + .../release/en/charger/eebus-compatible.yaml | 32 + templates/release/en/charger/eebus_0.yaml | 11 - templates/release/en/charger/elco.yaml | 63 + templates/release/en/charger/elecq-biz.yaml | 85 + templates/release/en/charger/elecq-home.yaml | 85 + .../release/en/charger/elecq-station.yaml | 85 + templates/release/en/charger/eledio-go.yaml | 89 + templates/release/en/charger/elli-2_0.yaml | 18 - templates/release/en/charger/elli-2_1.yaml | 18 - templates/release/en/charger/elli-2_10.yaml | 18 - templates/release/en/charger/elli-2_11.yaml | 18 - templates/release/en/charger/elli-2_2.yaml | 18 - templates/release/en/charger/elli-2_3.yaml | 18 - templates/release/en/charger/elli-2_4.yaml | 18 - templates/release/en/charger/elli-2_5.yaml | 18 - templates/release/en/charger/elli-2_6.yaml | 18 - templates/release/en/charger/elli-2_7.yaml | 18 - templates/release/en/charger/elli-2_8.yaml | 18 - templates/release/en/charger/elli-2_9.yaml | 18 - .../en/charger/elli-charger-connect-2.yaml | 39 + .../en/charger/elli-charger-connect.yaml | 41 + .../en/charger/elli-charger-pro-2.yaml | 39 + .../charger/elli-charger-pro-eichrecht-2.yaml | 39 + .../release/en/charger/elli-charger-pro.yaml | 39 + .../release/en/charger/elliconnect_0.yaml | 20 - .../release/en/charger/elliconnect_1.yaml | 20 - .../release/en/charger/elliconnect_2.yaml | 20 - .../release/en/charger/elliconnect_3.yaml | 20 - .../release/en/charger/elliconnect_4.yaml | 20 - templates/release/en/charger/ellipro_0.yaml | 18 - templates/release/en/charger/ellipro_1.yaml | 18 - templates/release/en/charger/ellipro_2.yaml | 18 - templates/release/en/charger/ellipro_3.yaml | 18 - templates/release/en/charger/ellipro_4.yaml | 18 - templates/release/en/charger/em2go-home.yaml | 23 + .../release/en/charger/em2go-home_0.yaml | 11 - .../en/charger/em2go-pro-power-ocpp-onc.yaml | 34 + templates/release/en/charger/em2go_0.yaml | 16 - templates/release/en/charger/emsesp_0.yaml | 14 - templates/release/en/charger/emsesp_1.yaml | 14 - templates/release/en/charger/emsesp_2.yaml | 14 - .../release/en/charger/enercab-smart.yaml | 89 + .../en/charger/enplus-ac-ev-charger.yaml | 86 + .../en/charger/ensto-chago-wallbox.yaml | 35 + .../en/charger/entratek-power-dot-fix.yaml | 86 + .../en/charger/entratek-power-dot-pro-2.yaml | 86 + .../release/en/charger/eprowallbox_0.yaml | 22 - .../release/en/charger/esl-walli-light.yaml | 35 + .../release/en/charger/esystems-ghostone.yaml | 39 + templates/release/en/charger/etrel-duo_0.yaml | 19 - .../release/en/charger/etrel-inch-duo.yaml | 49 + templates/release/en/charger/etrel-inch.yaml | 34 + templates/release/en/charger/etrel_0.yaml | 13 - templates/release/en/charger/etrel_1.yaml | 13 - templates/release/en/charger/evbox-elvi.yaml | 86 + templates/release/en/charger/evbox-livo.yaml | 33 + templates/release/en/charger/evse-din.yaml | 40 + templates/release/en/charger/evse-din_0.yaml | 20 - templates/release/en/charger/evse-din_1.yaml | 19 - templates/release/en/charger/evse-wifi.yaml | 19 + templates/release/en/charger/evsewifi_0.yaml | 7 - .../charger/free2move-eprowallbox-move.yaml | 43 + .../en/charger/free2move-eprowallbox.yaml | 43 + .../free2move-esolutions-eprowallbox.yaml | 86 + templates/release/en/charger/fritzdect_0.yaml | 24 - .../en/charger/fronius-wattpilot-ocpp.yaml | 86 + templates/release/en/charger/garo-glb.yaml | 35 + .../release/en/charger/garo-glbplus.yaml | 35 + .../release/en/charger/garo-ls4-compact.yaml | 35 + templates/release/en/charger/garo-ls4.yaml | 35 + templates/release/en/charger/ghost_0.yaml | 18 - templates/release/en/charger/ghost_1.yaml | 18 - .../en/charger/go-e-charger-gemini-ocpp.yaml | 86 + .../en/charger/go-e-charger-gemini.yaml | 27 + .../en/charger/go-e-charger-homefix.yaml | 24 + .../en/charger/go-e-charger-homeplus.yaml | 27 + .../en/charger/go-e-charger-pro-ocpp.yaml | 86 + .../release/en/charger/go-e-charger-pro.yaml | 24 + .../en/charger/go-e-charger-v3-ocpp.yaml | 86 + .../release/en/charger/go-e-charger-v3.yaml | 27 + templates/release/en/charger/go-e-v3_0.yaml | 15 - templates/release/en/charger/go-e-v3_1.yaml | 15 - templates/release/en/charger/go-e-v3_2.yaml | 15 - templates/release/en/charger/go-e_0.yaml | 12 - templates/release/en/charger/go-e_1.yaml | 12 - .../release/en/charger/hardy-barth-cph1.yaml | 37 + .../release/en/charger/hardy-barth-cph2.yaml | 21 + .../release/en/charger/hardy-barth-cpm2.yaml | 21 + .../release/en/charger/hardybarth-ecb1_0.yaml | 16 - .../release/en/charger/hardybarth-ecb1_1.yaml | 16 - .../en/charger/hardybarth-salia_0.yaml | 9 - .../en/charger/hardybarth-salia_1.yaml | 9 - .../en/charger/hardybarth-salia_2.yaml | 9 - .../en/charger/hardybarth-salia_3.yaml | 9 - .../en/charger/heidelberg-energy-control.yaml | 45 + .../release/en/charger/heidelberg_0.yaml | 24 - .../release/en/charger/heidelberg_1.yaml | 24 - .../release/en/charger/heidelberg_2.yaml | 24 - .../release/en/charger/heidelberg_3.yaml | 24 - .../release/en/charger/hesotec-ebox.yaml | 32 + .../release/en/charger/hesotec-esat.yaml | 32 + templates/release/en/charger/hesotec_0.yaml | 14 - templates/release/en/charger/hesotec_1.yaml | 14 - .../en/charger/home-assistant-switch.yaml | 100 + .../en/charger/homeassistant-switch_0.yaml | 25 - .../en/charger/homecharge-homecharger.yaml | 90 + .../release/en/charger/homematic-ip.yaml | 139 + templates/release/en/charger/homematic_0.yaml | 28 - templates/release/en/charger/homewizard.yaml | 65 + .../release/en/charger/homewizard_0.yaml | 17 - .../en/charger/huawei-scharger-22kt-s0.yaml | 85 + .../en/charger/huawei-scharger-7ks-s0.yaml | 85 + .../release/en/charger/ichargecion_0.yaml | 20 - .../release/en/charger/ichargecion_1.yaml | 20 - templates/release/en/charger/idm.yaml | 41 + templates/release/en/charger/idm_0.yaml | 14 - templates/release/en/charger/innogy-ebox.yaml | 33 + .../release/en/charger/innogy-ebox_0.yaml | 15 - .../release/en/charger/innogy-ebox_1.yaml | 15 - .../release/en/charger/innogy-ebox_2.yaml | 15 - .../release/en/charger/inro-pantabox.yaml | 20 + .../release/en/charger/juice-charger-me.yaml | 35 + .../release/en/charger/junkers-sg-ready.yaml | 53 + .../release/en/charger/kathrein-kwb-ac20.yaml | 35 + .../release/en/charger/kathrein-kwb-ac35.yaml | 35 + .../en/charger/kathrein-kwb-ac40-e.yaml | 35 + .../release/en/charger/kathrein-kwb-ac40.yaml | 35 + .../en/charger/kathrein-kwb-ac60-e.yaml | 35 + .../release/en/charger/kathrein-kwb-ac60.yaml | 35 + .../en/charger/keba-kecontact-p20.yaml | 54 + .../charger/keba-kecontact-p30-c-series.yaml | 54 + .../charger/keba-kecontact-p30-x-series.yaml | 54 + .../en/charger/keba-kecontact-p40-pro.yaml | 54 + .../en/charger/keba-kecontact-p40.yaml | 54 + .../release/en/charger/keba-modbus_0.yaml | 27 - .../release/en/charger/keba-modbus_1.yaml | 27 - .../release/en/charger/keba-modbus_2.yaml | 27 - .../release/en/charger/keba-modbus_3.yaml | 27 - .../release/en/charger/keba-modbus_4.yaml | 27 - .../release/en/charger/keba-modbus_5.yaml | 27 - .../release/en/charger/keba-modbus_6.yaml | 27 - .../en/charger/kermi-x-center-pro.yaml | 46 + templates/release/en/charger/kermi_0.yaml | 16 - templates/release/en/charger/kermi_1.yaml | 16 - .../en/charger/kontron-solar-charger.yaml | 39 + .../release/en/charger/kostal-enector.yaml | 48 + templates/release/en/charger/kse-wbx16.yaml | 43 + templates/release/en/charger/kse_0.yaml | 22 - .../release/en/charger/ladefoxx-evload.yaml | 50 + .../en/charger/ladefoxx-mikro-2-0.yaml | 50 + .../en/charger/lambda-eu-l-series.yaml | 52 + .../en/charger/lambda-zewotherm_0.yaml | 22 - .../en/charger/lambda-zewotherm_1.yaml | 22 - templates/release/en/charger/livo_0.yaml | 12 - .../en/charger/lrt-home-essentialplus.yaml | 44 + templates/release/en/charger/luxtronik_0.yaml | 28 - templates/release/en/charger/luxtronik_1.yaml | 28 - .../release/en/charger/luxtronik_10.yaml | 28 - templates/release/en/charger/luxtronik_2.yaml | 27 - templates/release/en/charger/luxtronik_3.yaml | 28 - templates/release/en/charger/luxtronik_4.yaml | 27 - templates/release/en/charger/luxtronik_5.yaml | 28 - templates/release/en/charger/luxtronik_6.yaml | 28 - templates/release/en/charger/luxtronik_7.yaml | 28 - templates/release/en/charger/luxtronik_8.yaml | 28 - templates/release/en/charger/luxtronik_9.yaml | 28 - .../charger/mennekes-amedio-professional.yaml | 35 + .../mennekes-amtron-4business-700.yaml | 35 + .../en/charger/mennekes-amtron-4you-300.yaml | 48 + .../en/charger/mennekes-amtron-4you-500.yaml | 35 + .../mennekes-amtron-chargecontrol.yaml | 35 + .../charger/mennekes-amtron-compact-2-0s.yaml | 48 + .../en/charger/mennekes-amtron-premium.yaml | 32 + .../charger/mennekes-amtron-professional.yaml | 35 + .../en/charger/mennekes-amtron-xtra.yaml | 32 + .../en/charger/mennekes-compact_0.yaml | 27 - .../en/charger/mennekes-compact_1.yaml | 27 - .../en/charger/mennekes-compact_2.yaml | 27 - .../mennekes-emobility-gateway-acu.yaml | 91 + .../release/en/charger/mennekes-hcc3_0.yaml | 14 - .../release/en/charger/mennekes-hcc3_1.yaml | 14 - .../en/charger/mennekes-smart-acu.yaml | 91 + .../en/charger/mennekes-smart-t-acu.yaml | 91 + .../release/en/charger/my-pv-ac-elwa-2.yaml | 43 + .../release/en/charger/my-pv-ac-thor-9s.yaml | 53 + .../release/en/charger/my-pv-ac-thor.yaml | 53 + .../release/en/charger/mystrom-switch.yaml | 66 + templates/release/en/charger/mystrom_0.yaml | 18 - .../release/en/charger/nibe-ap-aw10.yaml | 64 + .../release/en/charger/novelan-wpr-net.yaml | 64 + templates/release/en/charger/nrggen2_0.yaml | 25 - .../release/en/charger/nrgkick-connect.yaml | 42 + .../release/en/charger/nrgkick-connect_0.yaml | 12 - .../release/en/charger/nrgkick-gen2.yaml | 52 + .../en/charger/obo-bettermann-ion.yaml | 48 + templates/release/en/charger/obo_0.yaml | 26 - templates/release/en/charger/obo_1.yaml | 26 - templates/release/en/charger/obo_2.yaml | 26 - .../ocpp-1-6j-compatible-smart-charging.yaml | 107 + .../release/en/charger/ocpp-abb-tac_0.yaml | 22 - templates/release/en/charger/ocpp-abl_0.yaml | 20 - templates/release/en/charger/ocpp-abl_1.yaml | 20 - templates/release/en/charger/ocpp-abl_2.yaml | 20 - .../release/en/charger/ocpp-alfen_0.yaml | 20 - .../release/en/charger/ocpp-autel_0.yaml | 28 - .../release/en/charger/ocpp-autel_1.yaml | 28 - .../release/en/charger/ocpp-autoaid_0.yaml | 20 - .../release/en/charger/ocpp-autoaid_1.yaml | 20 - templates/release/en/charger/ocpp-beny_0.yaml | 20 - .../release/en/charger/ocpp-chargeamps_0.yaml | 20 - .../release/en/charger/ocpp-elecq_0.yaml | 19 - .../release/en/charger/ocpp-elecq_1.yaml | 19 - .../release/en/charger/ocpp-elecq_2.yaml | 19 - .../release/en/charger/ocpp-enercab_0.yaml | 23 - .../release/en/charger/ocpp-enercab_1.yaml | 23 - .../release/en/charger/ocpp-enplus_0.yaml | 20 - .../release/en/charger/ocpp-entratek_0.yaml | 20 - .../release/en/charger/ocpp-entratek_1.yaml | 20 - .../release/en/charger/ocpp-esolutions_0.yaml | 20 - .../release/en/charger/ocpp-evbox-elvi_0.yaml | 20 - templates/release/en/charger/ocpp-goe_0.yaml | 20 - templates/release/en/charger/ocpp-goe_1.yaml | 20 - templates/release/en/charger/ocpp-goe_2.yaml | 20 - templates/release/en/charger/ocpp-goe_3.yaml | 20 - .../release/en/charger/ocpp-homecharge_0.yaml | 24 - .../release/en/charger/ocpp-huawei_0.yaml | 19 - .../release/en/charger/ocpp-huawei_1.yaml | 19 - .../en/charger/ocpp-mennekes-acu_0.yaml | 25 - .../en/charger/ocpp-mennekes-acu_1.yaml | 25 - .../en/charger/ocpp-mennekes-acu_2.yaml | 25 - .../release/en/charger/ocpp-orbis_0.yaml | 19 - .../release/en/charger/ocpp-sungrow_0.yaml | 20 - .../release/en/charger/ocpp-wallbox_0.yaml | 28 - .../release/en/charger/ocpp-wallbox_1.yaml | 28 - .../release/en/charger/ocpp-wallbox_2.yaml | 28 - .../release/en/charger/ocpp-wallbox_3.yaml | 28 - .../release/en/charger/ocpp-zaptec_0.yaml | 25 - templates/release/en/charger/ocpp_0.yaml | 41 - templates/release/en/charger/openevse.yaml | 41 + templates/release/en/charger/openevse_0.yaml | 11 - .../release/en/charger/openwb-2.0_0.yaml | 32 - templates/release/en/charger/openwb-pro.yaml | 21 + .../release/en/charger/openwb-pro_0.yaml | 9 - .../release/en/charger/openwb-series2.yaml | 46 + .../en/charger/openwb-software-2-x.yaml | 68 + templates/release/en/charger/openwb_0.yaml | 16 - .../en/charger/optec-mobility-one.yaml | 35 + .../release/en/charger/orbis-viaris.yaml | 85 + templates/release/en/charger/pantabox_0.yaml | 8 - .../release/en/charger/pc-electric-garo.yaml | 33 + .../release/en/charger/pcelectric-garo_0.yaml | 12 - .../release/en/charger/peblar-business.yaml | 35 + .../release/en/charger/peblar-home-plus.yaml | 35 + templates/release/en/charger/peblar-home.yaml | 35 + templates/release/en/charger/peblar_0.yaml | 17 - templates/release/en/charger/peblar_1.yaml | 17 - templates/release/en/charger/peblar_2.yaml | 17 - .../release/en/charger/phoenix-charx_0.yaml | 23 - .../release/en/charger/phoenix-charx_1.yaml | 23 - .../release/en/charger/phoenix-charx_2.yaml | 23 - .../en/charger/phoenix-contact-charx.yaml | 50 + .../charger/phoenix-contact-em-cp-pp-eth.yaml | 31 + ...x-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml | 35 + ...enix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml | 35 + ...ix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml | 35 + ...oenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml | 35 + .../en/charger/phoenix-contact-ev-ser.yaml | 41 + .../release/en/charger/phoenix-em-eth_0.yaml | 13 - .../release/en/charger/phoenix-ev-eth_0.yaml | 17 - .../release/en/charger/phoenix-ev-eth_1.yaml | 17 - .../release/en/charger/phoenix-ev-eth_2.yaml | 17 - .../release/en/charger/phoenix-ev-eth_3.yaml | 17 - .../release/en/charger/phoenix-ev-eth_4.yaml | 17 - .../release/en/charger/phoenix-ev-eth_5.yaml | 17 - .../release/en/charger/phoenix-ev-eth_6.yaml | 17 - .../release/en/charger/phoenix-ev-eth_7.yaml | 17 - .../release/en/charger/phoenix-ev-eth_8.yaml | 17 - .../release/en/charger/phoenix-ev-ser_0.yaml | 20 - templates/release/en/charger/plugchoice.yaml | 56 + .../release/en/charger/plugchoice_0.yaml | 26 - templates/release/en/charger/pmcc_0.yaml | 11 - templates/release/en/charger/pmcp_0.yaml | 10 - .../porsche-mobile-charger-connect.yaml | 32 + .../charger/porsche-mobile-charger-plus.yaml | 31 + .../release/en/charger/porsche-wallbox.yaml | 39 + .../release/en/charger/porsche-wallbox_0.yaml | 18 - .../release/en/charger/pracht-alpha-xt.yaml | 92 + .../release/en/charger/pracht-alpha_0.yaml | 52 - .../release/en/charger/pracht-alpha_1.yaml | 52 - .../release/en/charger/pracht-alpha_2.yaml | 52 - .../release/en/charger/pracht-alpha_3.yaml | 52 - .../release/en/charger/pracht-mono-xt.yaml | 92 + templates/release/en/charger/pracht-pni.yaml | 92 + .../release/en/charger/pracht-xtplus.yaml | 92 + .../en/charger/pulsares-simplebox.yaml | 41 + templates/release/en/charger/pulsares_0.yaml | 20 - templates/release/en/charger/pulsatrix.yaml | 20 + templates/release/en/charger/pulsatrix_0.yaml | 8 - .../en/charger/qcells-q-home-edrive-a.yaml | 45 + .../release/en/charger/roth-thermoaura.yaml | 64 + .../release/en/charger/roth-thermoterra.yaml | 64 + .../en/charger/schneider-evlink-pro.yaml | 32 + .../en/charger/schneider-evlink-v3_0.yaml | 14 - .../en/charger/schrack-i-charge-cion.yaml | 41 + .../en/charger/senec-wallbox-pro-s.yaml | 45 + .../release/en/charger/senec-wallbox-pro.yaml | 53 + templates/release/en/charger/shelly-1.yaml | 99 + .../release/en/charger/shelly-plug-s.yaml | 99 + .../release/en/charger/shelly-plus-1.yaml | 99 + .../release/en/charger/shelly-pro-1.yaml | 99 + templates/release/en/charger/shelly_0.yaml | 23 - .../en/charger/siemens-versicharge-gen3.yaml | 34 + .../en/charger/skoda-charger-connect.yaml | 39 + .../charger/skoda-charger-pro-eichrecht.yaml | 39 + .../release/en/charger/skoda-charger-pro.yaml | 39 + .../en/charger/skoda-iv-charger-connect.yaml | 41 + .../charger/skoda-iv-charger-connectplus.yaml | 39 + .../release/en/charger/sma-echarger.yaml | 44 + .../release/en/charger/sma-ev-charger.yaml | 44 + .../release/en/charger/smaevcharger_0.yaml | 14 - .../release/en/charger/smaevcharger_1.yaml | 14 - templates/release/en/charger/smartevse_0.yaml | 21 - .../en/charger/smartfox-pro-charger.yaml | 41 + templates/release/en/charger/smartwb.yaml | 19 + templates/release/en/charger/smartwb_0.yaml | 7 - .../en/charger/solaredge-home-ev-charger.yaml | 54 + .../release/en/charger/solax-x3-evc.yaml | 45 + templates/release/en/charger/solax_0.yaml | 24 - templates/release/en/charger/solax_1.yaml | 24 - templates/release/en/charger/solax_2.yaml | 24 - .../en/charger/sonnen-sonnencharger.yaml | 34 + .../charger/spelsberg-wallbox-smart-pro.yaml | 35 + .../en/charger/stark-in-strom-easy.yaml | 41 + .../stiebel-eltron-lwa-lwz-sg-ready.yaml | 42 + .../charger/stiebel-eltron-wpm-sg-ready.yaml | 42 + .../release/en/charger/stiebel-lwa_0.yaml | 15 - .../release/en/charger/stiebel-lwa_1.yaml | 15 - .../release/en/charger/stiebel-wpm_0.yaml | 15 - .../release/en/charger/sungrow-ac011e-01.yaml | 50 + .../release/en/charger/sungrow-ac011e.yaml | 86 + .../release/en/charger/sungrow-ac22e-01.yaml | 50 + templates/release/en/charger/sungrow_0.yaml | 28 - templates/release/en/charger/sungrow_1.yaml | 28 - templates/release/en/charger/tapo_0.yaml | 22 - .../en/charger/tasmota-single-phase.yaml | 99 + templates/release/en/charger/tasmota_0.yaml | 24 - .../en/charger/tecalor-thz-sg-ready.yaml | 42 + .../en/charger/technisat-technivolt.yaml | 35 + .../charger/tesla-wall-connector-gen-3.yaml | 22 + templates/release/en/charger/tessie.yaml | 41 + templates/release/en/charger/tessie_0.yaml | 11 - .../en/charger/tigo-go-ev-charger.yaml | 45 + .../charger/tinkerforge-warp-charger-pro.yaml | 92 + .../tinkerforge-warp-charger-smart.yaml | 92 + .../tinkerforge-warp3-charger-pro.yaml | 81 + .../tinkerforge-warp3-charger-smart.yaml | 79 + .../en/charger/tinkerforge-warp3-smart_0.yaml | 22 - .../en/charger/tinkerforge-warp3_0.yaml | 24 - .../en/charger/tinkerforge-warp_0.yaml | 26 - .../en/charger/tinkerforge-warp_1.yaml | 26 - .../charger/tp-link-h-series-smart-plug.yaml | 66 + .../tp-link-tapo-p-series-smart-plug.yaml | 88 + templates/release/en/charger/tplink_0.yaml | 18 - templates/release/en/charger/trydan_0.yaml | 10 - templates/release/en/charger/twc3_0.yaml | 10 - .../release/en/charger/ubitricity-heinz.yaml | 35 + templates/release/en/charger/v2c-trydan.yaml | 22 + .../charger/vaillant-sensonet-sg-ready.yaml | 63 + templates/release/en/charger/vaillant_0.yaml | 15 - .../release/en/charger/versicharge_0.yaml | 16 - .../en/charger/vestel-connect-plus.yaml | 35 + .../en/charger/vestel-evc04-home-smart.yaml | 35 + templates/release/en/charger/vestel_0.yaml | 17 - templates/release/en/charger/vestel_1.yaml | 17 - templates/release/en/charger/vestel_2.yaml | 17 - templates/release/en/charger/vestel_3.yaml | 17 - templates/release/en/charger/vestel_4.yaml | 17 - .../victron-ev-charging-station-via-gx.yaml | 33 + .../charger/victron-ev-charging-station.yaml | 33 + .../release/en/charger/victron-evcs_0.yaml | 15 - templates/release/en/charger/victron_0.yaml | 15 - .../charger/viessmann-heatpump-sg-ready.yaml | 85 + templates/release/en/charger/viessmann_0.yaml | 19 - .../viridian-ev-evse-epc-2-0-plus.yaml | 48 + .../charger/volkswagen-charger-connect-2.yaml | 39 + .../en/charger/volkswagen-charger-pro-2.yaml | 39 + .../volkswagen-charger-pro-eichrecht-2.yaml | 39 + .../volkswagen-id-charger-connect.yaml | 41 + .../en/charger/volkswagen-id-charger-pro.yaml | 39 + .../release/en/charger/volt-time-one.yaml | 31 + .../en/charger/volt-time-source-2.yaml | 31 + .../en/charger/volt-time-source-2s.yaml | 31 + .../release/en/charger/volt-time-source.yaml | 31 + templates/release/en/charger/volttime_0.yaml | 10 - templates/release/en/charger/volttime_1.yaml | 10 - templates/release/en/charger/volttime_2.yaml | 10 - templates/release/en/charger/volttime_3.yaml | 10 - .../release/en/charger/wallbe-eco-2-0-s.yaml | 35 + templates/release/en/charger/wallbe-eco.yaml | 35 + templates/release/en/charger/wallbe-pro.yaml | 35 + .../charger/wallbox-commander-2-fw-5-x.yaml | 94 + .../en/charger/wallbox-commander-2.yaml | 94 + .../en/charger/wallbox-copper-sb-fw-5-x.yaml | 94 + .../release/en/charger/wallbox-copper-sb.yaml | 94 + .../release/en/charger/wallbox-fw5_0.yaml | 28 - .../release/en/charger/wallbox-fw5_1.yaml | 28 - .../release/en/charger/wallbox-fw5_2.yaml | 28 - .../release/en/charger/wallbox-fw5_3.yaml | 28 - .../en/charger/wallbox-pulsar-max-fw-5-x.yaml | 94 + .../en/charger/wallbox-pulsar-max.yaml | 94 + .../charger/wallbox-pulsar-plus-fw-5-x.yaml | 94 + .../en/charger/wallbox-pulsar-plus.yaml | 94 + .../charger/walther-werke-basic-evo-pro.yaml | 45 + .../release/en/charger/webasto-live.yaml | 35 + .../release/en/charger/webasto-next.yaml | 34 + .../release/en/charger/webasto-next_0.yaml | 13 - .../release/en/charger/webasto-next_1.yaml | 13 - .../release/en/charger/webasto-unite.yaml | 35 + .../en/charger/weidmuller-ac-smart.yaml | 22 + .../en/charger/weidm\303\274ller_0.yaml" | 10 - templates/release/en/charger/wolf-bwl.yaml | 64 + templates/release/en/charger/wolf-bws.yaml | 64 + templates/release/en/charger/zaptec-go-2.yaml | 42 + .../release/en/charger/zaptec-go-ocpp.yaml | 91 + templates/release/en/charger/zaptec-go.yaml | 42 + templates/release/en/charger/zaptec-pro.yaml | 42 + templates/release/en/charger/zaptec_0.yaml | 12 - templates/release/en/charger/zaptec_1.yaml | 12 - templates/release/en/charger/zaptec_2.yaml | 12 - .../en/charger/zewotherm-eu-l-series.yaml | 52 + .../en/charger/zj-beny-bcp-ev-charger.yaml | 86 + templates/release/en/meter/a-tronix.yaml | 151 + templates/release/en/meter/abb-a43.yaml | 61 + templates/release/en/meter/abb-a44.yaml | 61 + templates/release/en/meter/abb-ab_0.yaml | 40 - templates/release/en/meter/abb-b23.yaml | 61 + templates/release/en/meter/abb-b24.yaml | 61 + templates/release/en/meter/ac-elwa-2_0.yaml | 10 - templates/release/en/meter/ac-elwa-e_0.yaml | 10 - templates/release/en/meter/acrel-adw300.yaml | 98 + .../release/en/meter/acrel-adw300_0.yaml | 76 - .../release/en/meter/ads-tec-storaxe.yaml | 53 + .../release/en/meter/alpha-ess-smile_0.yaml | 157 - .../en/meter/alpha-ess-storion-smile.yaml | 215 ++ .../en/meter/ampere-ampere-storagepro.yaml | 211 ++ .../en/meter/anker-micro-inverter.yaml | 73 + templates/release/en/meter/apsystems-ez1.yaml | 22 + .../release/en/meter/apsystems-ez1_0.yaml | 10 - templates/release/en/meter/avm-fritzdect.yaml | 62 + .../en/meter/axitec-axihycon-12-15h.yaml | 150 + .../meter/bernecker-engineering-mpm3pm.yaml | 61 + .../release/en/meter/bge_tech_ds100_0.yaml | 100 - .../release/en/meter/bge_tech_ws100_0.yaml | 100 - templates/release/en/meter/bgetech-ds100.yaml | 122 + templates/release/en/meter/bgetech-ws100.yaml | 122 + .../en/meter/bosch-bpt-s-5-hybrid.yaml | 60 + templates/release/en/meter/bosch-bpt_0.yaml | 39 - .../en/meter/bosswerk-micro-inverter.yaml | 73 + .../en/meter/carlo-gavazzi-em110-111-112.yaml | 61 + .../release/en/meter/carlo-gavazzi-em24.yaml | 64 + .../en/meter/carlo-gavazzi-em24_e1.yaml | 48 + .../en/meter/carlo-gavazzi-em330-em340.yaml | 74 + .../en/meter/carlo-gavazzi-em530-em540.yaml | 74 + .../release/en/meter/carlo-gavazzi-et112.yaml | 61 + .../en/meter/carlo-gavazzi-et330-et340.yaml | 74 + .../en/meter/cfos-powerbrain-meter.yaml | 34 + templates/release/en/meter/cfos_0.yaml | 16 - templates/release/en/meter/cg-em24_0.yaml | 43 - templates/release/en/meter/cg-em24_1.yaml | 43 - templates/release/en/meter/cg-em24_e1_0.yaml | 30 - templates/release/en/meter/cg-em24_e1_1.yaml | 30 - templates/release/en/meter/cg-emt1xx_0.yaml | 40 - templates/release/en/meter/cg-emt1xx_1.yaml | 40 - templates/release/en/meter/cg-emt3xx_0.yaml | 52 - templates/release/en/meter/cg-emt3xx_1.yaml | 52 - templates/release/en/meter/cg-emt3xx_2.yaml | 52 - templates/release/en/meter/cg-emt3xx_3.yaml | 52 - templates/release/en/meter/cg-emt3xx_4.yaml | 52 - templates/release/en/meter/cg-emt3xx_5.yaml | 52 - templates/release/en/meter/demo-battery.yaml | 91 + .../release/en/meter/demo-battery_0.yaml | 25 - templates/release/en/meter/demo-meter.yaml | 114 + templates/release/en/meter/demo-meter_0.yaml | 66 - .../en/meter/deye-3p-hybrid-inverter.yaml | 212 ++ .../en/meter/deye-hp3-hybrid-inverter.yaml | 236 ++ .../release/en/meter/deye-hybrid-3p_0.yaml | 154 - .../release/en/meter/deye-hybrid-3p_1.yaml | 154 - .../release/en/meter/deye-hybrid-hp3_0.yaml | 160 - .../release/en/meter/deye-hybrid-hp3_1.yaml | 160 - templates/release/en/meter/deye-mi_0.yaml | 51 - templates/release/en/meter/deye-mi_1.yaml | 51 - templates/release/en/meter/deye-mi_2.yaml | 51 - templates/release/en/meter/deye-mi_3.yaml | 51 - .../release/en/meter/deye-micro-inverter.yaml | 73 + .../meter/deye-storage-hybrid-inverter.yaml | 177 + .../release/en/meter/deye-storage_0.yaml | 146 - .../release/en/meter/deye-storage_1.yaml | 146 - .../en/meter/deye-string-inverter.yaml | 50 + templates/release/en/meter/deye-string_0.yaml | 28 - templates/release/en/meter/deye-string_1.yaml | 28 - templates/release/en/meter/discovergy.yaml | 49 + templates/release/en/meter/discovergy_0.yaml | 19 - templates/release/en/meter/dsmr.yaml | 47 + templates/release/en/meter/dsmr_0.yaml | 17 - templates/release/en/meter/dzg-dvh4013.yaml | 43 + templates/release/en/meter/dzg_0.yaml | 22 - templates/release/en/meter/e3-dc.yaml | 146 + templates/release/en/meter/e3dc-rscp_0.yaml | 71 - .../en/meter/eastron-sdm120-modbus.yaml | 79 + .../release/en/meter/eastron-sdm120_0.yaml | 58 - .../release/en/meter/eastron-sdm220-230.yaml | 61 + .../en/meter/eastron-sdm220_230_0.yaml | 40 - .../en/meter/eastron-sdm220_230_1.yaml | 40 - .../en/meter/eastron-sdm220_230_2.yaml | 40 - .../en/meter/eastron-sdm630-modbus.yaml | 61 + .../release/en/meter/eastron-sdm72_0.yaml | 40 - .../release/en/meter/eastron-sdm72d-m.yaml | 61 + .../release/en/meter/eastron-sdm72dm-v2.yaml | 61 + templates/release/en/meter/eastron_0.yaml | 40 - templates/release/en/meter/eastron_1.yaml | 40 - templates/release/en/meter/eastron_2.yaml | 40 - templates/release/en/meter/eastron_3.yaml | 40 - templates/release/en/meter/eastron_4.yaml | 40 - .../release/en/meter/enphase-iq-envoy.yaml | 88 + templates/release/en/meter/enphase_0.yaml | 49 - .../en/meter/esphome-dlms-austria_0.yaml | 20 - .../en/meter/esphome-dlms-meter-austria.yaml | 41 + templates/release/en/meter/esphome-dsmr.yaml | 37 + templates/release/en/meter/fenecon.yaml | 104 + templates/release/en/meter/fox-ess-h1_0.yaml | 52 - .../release/en/meter/fox-ess-h3-smart_0.yaml | 154 - templates/release/en/meter/fox-ess-h3_0.yaml | 154 - .../foxess-h1-series-hybrid-inverter.yaml | 74 + .../foxess-h3-series-hybrid-inverter.yaml | 212 ++ ...oxess-h3-smart-series-hybrid-inverter.yaml | 212 ++ templates/release/en/meter/fritzdect_0.yaml | 23 - .../release/en/meter/fronius-gen24_0.yaml | 48 - .../release/en/meter/fronius-gen24_1.yaml | 48 - .../release/en/meter/fronius-ohmpilot.yaml | 37 + .../release/en/meter/fronius-ohmpilot_0.yaml | 16 - .../en/meter/fronius-primo-gen24-plus.yaml | 105 + .../fronius-smartmeter-via-inverter.yaml | 44 + .../en/meter/fronius-solar-api-v1.yaml | 109 + .../en/meter/fronius-solarapi-v1_0.yaml | 58 - .../en/meter/fronius-symo-gen24-plus.yaml | 105 + ...long-solis-hybrid-inverter-rhi-series.yaml | 150 + ...inlong-solis-hybrid-inverter-s-series.yaml | 150 + .../en/meter/ginlong-solis-inverter.yaml | 61 + .../release/en/meter/go-e-controller.yaml | 28 + .../release/en/meter/go-e-controller_0.yaml | 16 - templates/release/en/meter/goodwe-dt_0.yaml | 28 - .../goodwe-et-eh-bh-bt-hybrid-inverter.yaml | 204 ++ .../en/meter/goodwe-goodwe-over-wifi.yaml | 35 + .../release/en/meter/goodwe-hybrid_0.yaml | 154 - .../en/meter/goodwe-sdt-dt-inverter.yaml | 50 + templates/release/en/meter/goodwe-wifi_0.yaml | 23 - .../en/meter/growatt-hybrid-inverter.yaml | 194 ++ .../en/meter/growatt-hybrid-tlxh_0.yaml | 148 - .../release/en/meter/growatt-hybrid_0.yaml | 154 - .../meter/growatt-tl-x-h-hybrid-inverter.yaml | 188 + templates/release/en/meter/homematic-ip.yaml | 121 + templates/release/en/meter/homematic_0.yaml | 64 - .../en/meter/homewizard-kwh-meter.yaml | 28 + .../release/en/meter/homewizard-kwh_0.yaml | 16 - .../en/meter/homewizard-wi-fi-p1-meter.yaml | 22 + templates/release/en/meter/homewizard_0.yaml | 10 - .../release/en/meter/hoymiles-ahoydtu_0.yaml | 11 - ...oymiles-hm-and-hms-series-via-ahoydtu.yaml | 32 + ...oymiles-hm-and-hms-series-via-opendtu.yaml | 22 + .../release/en/meter/hoymiles-opendtu_0.yaml | 10 - .../release/en/meter/huawei-dongle_0.yaml | 20 - templates/release/en/meter/huawei-emma.yaml | 95 + templates/release/en/meter/huawei-emma_0.yaml | 68 - .../release/en/meter/huawei-smartlogger.yaml | 133 + .../en/meter/huawei-smartlogger_0.yaml | 79 - .../en/meter/huawei-sun2000-sdongle.yaml | 47 + .../release/en/meter/huawei-sun2000.yaml | 240 ++ .../release/en/meter/huawei-sun2000_0.yaml | 164 - .../release/en/meter/iammeter-wem3080.yaml | 38 + .../iammeter-wem3080t-wem3046t-wem3050t.yaml | 38 + templates/release/en/meter/iammeter_0.yaml | 26 - templates/release/en/meter/iammeter_1.yaml | 26 - .../en/meter/igen-tech-solarman-logger.yaml | 42 + .../release/en/meter/inepro-pro380-mod.yaml | 61 + templates/release/en/meter/inepro_0.yaml | 40 - templates/release/en/meter/iometer.yaml | 21 + templates/release/en/meter/iometer_0.yaml | 9 - .../release/en/meter/janitza-b-series.yaml | 74 + .../release/en/meter/janitza-umg-series.yaml | 74 + templates/release/en/meter/janitza_0.yaml | 52 - .../release/en/meter/keba-kecontact-e10.yaml | 33 + .../release/en/meter/keba-kecontact_0.yaml | 15 - .../en/meter/kostal-energy-meter-c-kem-c.yaml | 74 + .../en/meter/kostal-energy-meter-p-kem-p.yaml | 61 + .../en/meter/kostal-ksem-inverter_0.yaml | 17 - templates/release/en/meter/kostal-ksem_0.yaml | 15 - .../release/en/meter/kostal-piko-ba.yaml | 28 + .../release/en/meter/kostal-piko-hybrid.yaml | 59 + .../en/meter/kostal-piko-hybrid_0.yaml | 38 - .../release/en/meter/kostal-piko-legacy.yaml | 42 + .../en/meter/kostal-piko-legacy_0.yaml | 12 - .../release/en/meter/kostal-piko-mp-plus.yaml | 22 + .../en/meter/kostal-piko-mp-plus_0.yaml | 10 - .../en/meter/kostal-piko-mp-plus_1.yaml | 10 - .../release/en/meter/kostal-piko-pv_0.yaml | 16 - templates/release/en/meter/kostal-piko.yaml | 28 + .../en/meter/kostal-plenticore-gen2_0.yaml | 59 - ...cl-grid-charging-of-the-house-battery.yaml | 122 + .../en/meter/kostal-plenticore-hybrid.yaml | 133 + .../release/en/meter/kostal-plenticore_0.yaml | 61 - ...ostal-smart-energy-meter-via-inverter.yaml | 35 + .../en/meter/kostal-smart-energy-meter.yaml | 33 + .../release/en/meter/lg-ess-home-15.yaml | 111 + .../release/en/meter/lg-ess-home-15_0.yaml | 54 - .../release/en/meter/lg-ess-home-8-10.yaml | 114 + .../release/en/meter/lg-ess-home-8-10_0.yaml | 57 - .../release/en/meter/loxone-miniserver.yaml | 92 + templates/release/en/meter/loxone_0.yaml | 44 - .../en/meter/m-tec-energy-butler-gen2.yaml | 79 + .../en/meter/m-tec-energy-butler-gen3.yaml | 178 + .../meter/marstek-venus-battery-storage.yaml | 112 + .../release/en/meter/marstek-venus_0.yaml | 46 - .../release/en/meter/mhendriks-p1-dongle.yaml | 37 + templates/release/en/meter/mpm3pm_0.yaml | 40 - .../release/en/meter/mtec-eb-gen2_0.yaml | 58 - .../release/en/meter/mtec-eb-gen3_0.yaml | 147 - .../release/en/meter/my-pv-ac-elwa-2.yaml | 22 + .../release/en/meter/my-pv-ac-elwa-e.yaml | 22 + templates/release/en/meter/my-pv-ac-thor.yaml | 22 + .../release/en/meter/my-pv-wifi-meter.yaml | 33 + .../release/en/meter/mypv-wifi-meter_0.yaml | 15 - .../release/en/meter/mystrom-switch.yaml | 29 + templates/release/en/meter/mystrom_0.yaml | 17 - templates/release/en/meter/openems.yaml | 104 + templates/release/en/meter/openems_0.yaml | 47 - templates/release/en/meter/openems_1.yaml | 47 - .../release/en/meter/orno-or-we-516.yaml | 61 + .../release/en/meter/orno-or-we-517.yaml | 61 + templates/release/en/meter/orno_0.yaml | 40 - .../en/meter/p1monitor-p1-monitor.yaml | 22 + templates/release/en/meter/p1monitor_0.yaml | 10 - templates/release/en/meter/plexlog.yaml | 97 + templates/release/en/meter/plexlog_0.yaml | 70 - templates/release/en/meter/powerdog.yaml | 43 + templates/release/en/meter/powerdog_0.yaml | 25 - .../release/en/meter/powerfox-poweropti.yaml | 62 + .../en/meter/powerfox-poweropti_0.yaml | 32 - .../en/meter/qcells-hybrid-cloud_0.yaml | 49 - .../meter/qcells-hybrid-inverter-cloud.yaml | 79 + .../en/meter/qcells-q-home-ess-hyb-g3.yaml | 225 ++ templates/release/en/meter/rct-power.yaml | 118 + templates/release/en/meter/rct-power_0.yaml | 52 - .../meter/saia-burgess-controls-sbc-ale3.yaml | 61 + .../meter/saia-burgess-controls-sbc-awd3.yaml | 61 + .../saj-h1-series-hybrid-solar-inverter.yaml | 110 + templates/release/en/meter/saj-h1_0.yaml | 74 - .../saj-h2-series-hybrid-solar-inverter.yaml | 211 ++ templates/release/en/meter/saj-h2_0.yaml | 153 - templates/release/en/meter/saj-h2_1.yaml | 153 - .../meter/saj-r5-series-solar-inverter.yaml | 43 + templates/release/en/meter/saj-r5_0.yaml | 22 - .../release/en/meter/sax-homespeicher.yaml | 44 + templates/release/en/meter/sax_0.yaml | 26 - templates/release/en/meter/sbc-axx3_0.yaml | 40 - .../schneider-electric-iem3xxx-modbus.yaml | 61 + .../release/en/meter/schneider-iem3000_0.yaml | 40 - templates/release/en/meter/senec-home.yaml | 75 + templates/release/en/meter/senec-home_0.yaml | 45 - .../senergy-se-4-5-6ktl-s1-g2-inverter.yaml | 33 + templates/release/en/meter/senergy_0.yaml | 15 - templates/release/en/meter/senergy_1.yaml | 15 - .../release/en/meter/shelly-1pm-mini.yaml | 71 + templates/release/en/meter/shelly-1pm.yaml | 71 + templates/release/en/meter/shelly-1pm_0.yaml | 32 - templates/release/en/meter/shelly-3em.yaml | 73 + templates/release/en/meter/shelly-3em_0.yaml | 43 - templates/release/en/meter/shelly-em.yaml | 71 + templates/release/en/meter/shelly-plug-s.yaml | 71 + .../release/en/meter/shelly-pm-mini.yaml | 71 + .../release/en/meter/shelly-pro-1pm.yaml | 71 + .../release/en/meter/shelly-pro-3-em.yaml | 58 + .../meter/shelly-pro-3em-monophase-mode.yaml | 71 + .../release/en/meter/shelly-pro-3em_0.yaml | 28 - templates/release/en/meter/shelly-pro-em.yaml | 71 + .../release/en/meter/siemens-7kt1665.yaml | 74 + .../release/en/meter/siemens-7kt1665_0.yaml | 52 - .../siemens-junelight-smart-battery.yaml | 98 + .../release/en/meter/siemens-junelight_0.yaml | 71 - .../release/en/meter/siemens-pac-2200.yaml | 74 + .../release/en/meter/siemens-pac2200_0.yaml | 52 - ...gen-hybrid-sigen-pv-max-sigenstore-ec.yaml | 91 + templates/release/en/meter/sigenergy_0.yaml | 52 - .../release/en/meter/slimmelezer-V2_0.yaml | 12 - .../en/meter/slimmelezer-luxembourg_0.yaml | 12 - templates/release/en/meter/slimmelezer_0.yaml | 16 - templates/release/en/meter/slimmelezer_1.yaml | 16 - templates/release/en/meter/slimmelezer_2.yaml | 16 - .../release/en/meter/sma-data-manager.yaml | 97 + .../release/en/meter/sma-data-manager_0.yaml | 70 - .../release/en/meter/sma-energy-meter.yaml | 49 + .../release/en/meter/sma-energy-meter_0.yaml | 28 - .../release/en/meter/sma-home-manager_0.yaml | 18 - templates/release/en/meter/sma-hybrid_0.yaml | 51 - .../en/meter/sma-inverter-modbus_0.yaml | 15 - .../en/meter/sma-inverter-speedwire.yaml | 62 + .../en/meter/sma-inverter-speedwire_0.yaml | 32 - .../en/meter/sma-sbs-15-25-modbus_0.yaml | 29 - .../release/en/meter/sma-sbs-modbus_0.yaml | 29 - .../release/en/meter/sma-si-modbus_0.yaml | 29 - .../sma-smart-energy-hybrid-inverter.yaml | 105 + ...-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml | 74 + ...-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml | 74 + .../en/meter/sma-sunny-home-manager-2-0.yaml | 39 + .../en/meter/sma-sunny-island-modbus.yaml | 74 + templates/release/en/meter/sma-webbox.yaml | 33 + templates/release/en/meter/sma-webbox_0.yaml | 15 - .../en/meter/sma-wechselrichter-modbus.yaml | 33 + templates/release/en/meter/smartfox-box.yaml | 37 + .../release/en/meter/smartfox-em2_0.yaml | 43 - .../en/meter/smartfox-light-em2-firmware.yaml | 64 + .../release/en/meter/smartfox-pro-2.yaml | 64 + .../en/meter/smartfox-pro-light-2.yaml | 64 + .../release/en/meter/smartfox-pro-light.yaml | 64 + templates/release/en/meter/smartfox-pro.yaml | 64 + .../en/meter/smartfox-reg-extended.yaml | 37 + templates/release/en/meter/smartfox-reg.yaml | 37 + templates/release/en/meter/smartfox_0.yaml | 25 - .../release/en/meter/sofarsolar-g3_0.yaml | 154 - .../release/en/meter/sofarsolar-g3_1.yaml | 154 - .../release/en/meter/sofarsolar-g3_2.yaml | 154 - .../release/en/meter/sofarsolar-g3_3.yaml | 154 - .../en/meter/sofarsolar-hybrid-inverter.yaml | 177 + .../en/meter/sofarsolar-hyd-3-6k-ep.yaml | 212 ++ .../en/meter/sofarsolar-hyd-5-20k-3ph.yaml | 212 ++ .../release/en/meter/sofarsolar-inverter.yaml | 177 + .../en/meter/sofarsolar-sofar-5-24ktl-g3.yaml | 212 ++ .../en/meter/sofarsolar-sofar-80-136ktl.yaml | 212 ++ templates/release/en/meter/sofarsolar_0.yaml | 146 - templates/release/en/meter/sofarsolar_1.yaml | 146 - .../en/meter/solaranzeige-solaranzeige.yaml | 100 + .../release/en/meter/solaranzeige_0.yaml | 43 - .../en/meter/solaredge-hybrid-inverter.yaml | 219 ++ .../release/en/meter/solaredge-hybrid_0.yaml | 161 - .../release/en/meter/solaredge-inverter.yaml | 87 + .../en/meter/solaredge-inverter_0.yaml | 56 - templates/release/en/meter/solarlog.yaml | 42 + templates/release/en/meter/solarlog_0.yaml | 21 - templates/release/en/meter/solarman_0.yaml | 12 - ...rmax-max-storage-max-storage-ultimate.yaml | 120 + .../en/meter/solarmax-maxstorage_0.yaml | 75 - .../release/en/meter/solarmax-smt_0.yaml | 15 - .../en/meter/solarmax-solarmax-smt.yaml | 33 + .../en/meter/solarmax-sp-series-inverter.yaml | 33 + .../en/meter/solarwatt-energymanager-pro.yaml | 59 + .../en/meter/solarwatt-energymanager.yaml | 59 + .../release/en/meter/solarwatt-flex_0.yaml | 41 - .../en/meter/solarwatt-manager-flex.yaml | 62 + ...yreserve-matrix-lan-oder-powergateway.yaml | 74 + .../meter/solarwatt-myreserve-matrix_0.yaml | 44 - .../release/en/meter/solarwatt-myreserve.yaml | 59 + templates/release/en/meter/solarwatt_0.yaml | 38 - templates/release/en/meter/solarwatt_1.yaml | 38 - .../en/meter/solax-hybrid-cloud_0.yaml | 49 - .../en/meter/solax-hybrid-inverter-cloud.yaml | 79 + .../en/meter/solax-hybrid-x1-x3-g3-g4.yaml | 225 ++ .../en/meter/solax-inverter-cloud.yaml | 37 + .../en/meter/solax-inverter-cloud_0.yaml | 16 - templates/release/en/meter/solax_0.yaml | 158 - templates/release/en/meter/solax_1.yaml | 158 - templates/release/en/meter/solinteng.yaml | 151 + .../release/en/meter/solis-hybrid-s_0.yaml | 111 - .../release/en/meter/solis-hybrid-s_1.yaml | 111 - .../release/en/meter/solis-hybrid_0.yaml | 111 - templates/release/en/meter/solis_0.yaml | 40 - .../release/en/meter/sonnen-comfort.yaml | 96 + templates/release/en/meter/sonnen-eco-5.yaml | 96 + templates/release/en/meter/sonnen-eco-6.yaml | 96 + .../release/en/meter/sonnen-oem-6-5.yaml | 96 + .../en/meter/sonnen-sonnenbatterie.yaml | 111 + .../en/meter/sonnenbatterie-eco56_0.yaml | 48 - .../release/en/meter/sonnenbatterie_0.yaml | 54 - templates/release/en/meter/st-ems.yaml | 151 + .../release/en/meter/steca-coolcept-flex.yaml | 22 + templates/release/en/meter/storaxe_0.yaml | 26 - .../release/en/meter/sungrow-hybrid_0.yaml | 157 - .../release/en/meter/sungrow-inverter_0.yaml | 52 - .../en/meter/sungrow-sg-series-inverter.yaml | 74 + .../sungrow-sh-series-hybrid-inverter.yaml | 215 ++ .../en/meter/sunspec-battery-control_0.yaml | 55 - .../en/meter/sunspec-battery-model-124.yaml | 94 + .../en/meter/sunspec-battery-model-802.yaml | 104 + .../en/meter/sunspec-hybrid-inverter.yaml | 187 + .../release/en/meter/sunspec-hybrid_0.yaml | 147 - .../en/meter/sunspec-inverter-control_0.yaml | 54 - .../release/en/meter/sunspec-inverter.yaml | 177 + .../release/en/meter/sunspec-inverter_0.yaml | 146 - templates/release/en/meter/sunspec-meter.yaml | 43 + .../release/en/meter/sunspec-meter_0.yaml | 25 - .../release/en/meter/sunspec-meter_1.yaml | 26 - .../en/meter/sunsynk-3p-hybrid-inverter.yaml | 212 ++ .../en/meter/sunsynk-hp3-hybrid-inverter.yaml | 236 ++ .../en/meter/sunsynk-micro-inverter.yaml | 73 + .../sunsynk-storage-hybrid-inverter.yaml | 177 + .../en/meter/sunsynk-string-inverter.yaml | 50 + templates/release/en/meter/sunway.yaml | 151 + templates/release/en/meter/tapo_0.yaml | 13 - templates/release/en/meter/tasmota-3p_0.yaml | 39 - ...l-ir-reader-for-smartmeters-e-g-hichi.yaml | 91 + templates/release/en/meter/tasmota-sml_0.yaml | 61 - ...asmota-tasmota-1-phase-plus-sml-meter.yaml | 80 + .../release/en/meter/tasmota-three-phase.yaml | 69 + templates/release/en/meter/tasmota_0.yaml | 41 - .../release/en/meter/tesla-powerwall.yaml | 127 + .../release/en/meter/tesla-powerwall_0.yaml | 70 - templates/release/en/meter/thor_0.yaml | 10 - templates/release/en/meter/tibber-pulse.yaml | 33 + .../release/en/meter/tibber-pulse_0.yaml | 12 - .../en/meter/tp-link-h-series-smart-plug.yaml | 23 + .../tp-link-tapo-p-series-smart-plug.yaml | 43 + templates/release/en/meter/tplink_0.yaml | 11 - templates/release/en/meter/tq-em420_0.yaml | 13 - templates/release/en/meter/tq-em_0.yaml | 12 - .../meter/tq-energy-manager-em2xx-em3xx.yaml | 42 + .../en/meter/tq-energy-manager-em420.yaml | 52 + templates/release/en/meter/varta-element.yaml | 76 + .../release/en/meter/varta-pulse-neo.yaml | 76 + templates/release/en/meter/varta-pulse.yaml | 76 + templates/release/en/meter/varta_0.yaml | 46 - templates/release/en/meter/victron-em24.yaml | 64 + .../release/en/meter/victron-em24_e1.yaml | 48 + .../release/en/meter/victron-em530-em540.yaml | 74 + .../release/en/meter/victron-energy.yaml | 122 + .../release/en/meter/victron-energy_0.yaml | 56 - templates/release/en/meter/victron-et340.yaml | 74 + .../release/en/meter/volkszaehler-http_0.yaml | 12 - .../en/meter/volkszaehler-importexport_0.yaml | 13 - .../release/en/meter/volkszaehler-ws_0.yaml | 14 - ...olkszahler-http-api-import-and-export.yaml | 43 + .../en/meter/volkszahler-http-api.yaml | 33 + .../en/meter/volkszahler-websocket-api.yaml | 44 + templates/release/en/meter/vzlogger.yaml | 159 + templates/release/en/meter/vzlogger_0.yaml | 30 - templates/release/en/meter/wago-879-30xx.yaml | 61 + .../release/en/meter/wago-879-30xx_0.yaml | 40 - templates/release/en/meter/wattsonic.yaml | 151 + templates/release/en/meter/wattsonic_0.yaml | 112 - templates/release/en/meter/wattsonic_1.yaml | 112 - templates/release/en/meter/wattsonic_2.yaml | 112 - templates/release/en/meter/wattsonic_3.yaml | 112 - templates/release/en/meter/wattsonic_4.yaml | 112 - .../en/meter/weidmuller-em110-rtu-2p.yaml | 61 + .../en/meter/weidmuller-em111-rtu-2p.yaml | 61 + .../en/meter/weidmuller-em120-rtu-2p.yaml | 61 + .../en/meter/weidmuller-em122-rtu-2p.yaml | 61 + .../en/meter/youless-energy-monitor.yaml | 31 + templates/release/en/meter/youless_0.yaml | 19 - .../en/meter/zcs-azzurro-hybrid-inverter.yaml | 177 + .../en/meter/zcs-azzurro-inverter.yaml | 177 + .../release/en/meter/zendure-hyper-2000.yaml | 88 + templates/release/en/meter/zendure_0.yaml | 40 - ...idwijk-slimmelezer-plus-in-luxembourg.yaml | 24 + .../meter/zuidwijk-slimmelezer-plus-v2.yaml | 24 + .../en/meter/zuidwijk-slimmelezer-plus.yaml | 37 + .../release/en/tariff/amber-electric.yaml | 77 + templates/release/en/tariff/amber_0.yaml | 20 - templates/release/en/tariff/awattar.yaml | 55 + templates/release/en/tariff/awattar_0.yaml | 16 - .../electricity-maps-commercial-api.yaml | 44 + .../en/tariff/electricity-maps-free-api.yaml | 34 + .../en/tariff/electricitymaps-free_0.yaml | 13 - .../release/en/tariff/electricitymaps_0.yaml | 14 - templates/release/en/tariff/energinet.yaml | 56 + templates/release/en/tariff/energinet_0.yaml | 17 - .../en/tariff/energy-charts-api_0.yaml | 19 - templates/release/en/tariff/enever.yaml | 77 + templates/release/en/tariff/enever_0.yaml | 20 - templates/release/en/tariff/entso-e.yaml | 70 + templates/release/en/tariff/entsoe_0.yaml | 22 - .../release/en/tariff/forecast-solar.yaml | 101 + .../release/en/tariff/forecast-solar_0.yaml | 26 - .../release/en/tariff/fraunhofer-ise.yaml | 58 + .../release/en/tariff/green-grid-compass.yaml | 34 + .../en/tariff/green-grid-compass_0.yaml | 13 - .../en/tariff/groupe-e-vario-plus.yaml | 46 + templates/release/en/tariff/groupe-e_0.yaml | 16 - .../release/en/tariff/grunstromindex.yaml | 34 + .../en/tariff/gr\303\274nstromindex_0.yaml" | 13 - .../release/en/tariff/national-grid-eso.yaml | 31 + templates/release/en/tariff/ngeso_0.yaml | 10 - .../en/tariff/nordpool-spot-prices.yaml | 69 + templates/release/en/tariff/nordpool_0.yaml | 21 - .../release/en/tariff/octopus-api_0.yaml | 13 - .../release/en/tariff/octopus-energy-api.yaml | 34 + .../tariff/octopus-energy-product-code.yaml | 42 + .../en/tariff/octopus-productcode_0.yaml | 12 - templates/release/en/tariff/open-meteo.yaml | 141 + templates/release/en/tariff/open-meteo_0.yaml | 30 - templates/release/en/tariff/ostrom.yaml | 44 + templates/release/en/tariff/ostrom_0.yaml | 14 - templates/release/en/tariff/pun-orario.yaml | 47 + templates/release/en/tariff/pun_0.yaml | 17 - .../en/tariff/smartenergy-smartcontrol.yaml | 45 + .../release/en/tariff/smartenergy_0.yaml | 15 - templates/release/en/tariff/solcast.yaml | 68 + templates/release/en/tariff/solcast_0.yaml | 20 - .../release/en/tariff/spotty-energie.yaml | 67 + .../release/en/tariff/spottyenergy_0.yaml | 19 - templates/release/en/tariff/tibber.yaml | 69 + templates/release/en/tariff/tibber_0.yaml | 21 - .../en/tariff/victron-vrm-solar-forecast.yaml | 49 + templates/release/en/tariff/victron_0.yaml | 19 - templates/release/en/vehicle/aiways.yaml | 147 + templates/release/en/vehicle/aiways_0.yaml | 27 - templates/release/en/vehicle/audi.yaml | 147 + templates/release/en/vehicle/audi_0.yaml | 27 - templates/release/en/vehicle/bmw.yaml | 191 ++ templates/release/en/vehicle/bmw_0.yaml | 35 - templates/release/en/vehicle/carwings_0.yaml | 28 - templates/release/en/vehicle/citroen.yaml | 161 + templates/release/en/vehicle/citroen_0.yaml | 32 - templates/release/en/vehicle/cupra_0.yaml | 30 - templates/release/en/vehicle/dacia.yaml | 167 + templates/release/en/vehicle/dacia_0.yaml | 29 - templates/release/en/vehicle/ds.yaml | 161 + templates/release/en/vehicle/ds_0.yaml | 32 - templates/release/en/vehicle/enyaq_0.yaml | 30 - templates/release/en/vehicle/evnotify.yaml | 127 + templates/release/en/vehicle/evnotify_0.yaml | 25 - templates/release/en/vehicle/fiat.yaml | 178 + templates/release/en/vehicle/fiat_0.yaml | 31 - templates/release/en/vehicle/fiat_1.yaml | 31 - templates/release/en/vehicle/flobz_0.yaml | 28 - .../release/en/vehicle/ford-connect_0.yaml | 31 - templates/release/en/vehicle/ford.yaml | 169 + .../vehicle/generic-vehicle-without-api.yaml | 105 + .../release/en/vehicle/hyundai-bluelink.yaml | 161 + templates/release/en/vehicle/hyundai_0.yaml | 32 - .../release/en/vehicle/ioBroker.bmw_0.yaml | 30 - .../release/en/vehicle/iobroker-bmw.yaml | 159 + templates/release/en/vehicle/iso15118.yaml | 112 + templates/release/en/vehicle/iso15118_0.yaml | 28 - templates/release/en/vehicle/jeep.yaml | 178 + .../release/en/vehicle/kia-bluelink.yaml | 161 + templates/release/en/vehicle/kia_0.yaml | 32 - .../release/en/vehicle/mercedes-benz.yaml | 172 + templates/release/en/vehicle/mercedes_0.yaml | 34 - templates/release/en/vehicle/mg.yaml | 157 + templates/release/en/vehicle/mg2mqtt.yaml | 140 + templates/release/en/vehicle/mg2mqtt_0.yaml | 29 - templates/release/en/vehicle/mg_0.yaml | 28 - templates/release/en/vehicle/mini.yaml | 191 ++ templates/release/en/vehicle/mini_0.yaml | 35 - templates/release/en/vehicle/mz2mqtt.yaml | 128 + templates/release/en/vehicle/mz2mqtt_0.yaml | 26 - .../release/en/vehicle/nissan-ariya.yaml | 148 + .../release/en/vehicle/nissan-ariya_0.yaml | 28 - .../en/vehicle/nissan-leaf-pre-2019.yaml | 148 + templates/release/en/vehicle/nissan-leaf.yaml | 148 + templates/release/en/vehicle/nissan_0.yaml | 28 - .../release/en/vehicle/niu-e-scooter.yaml | 71 + .../release/en/vehicle/niu-e-scooter_0.yaml | 14 - templates/release/en/vehicle/offline_0.yaml | 21 - templates/release/en/vehicle/opel.yaml | 161 + templates/release/en/vehicle/opel_0.yaml | 32 - .../open-vehicle-monitoring-system.yaml | 160 + templates/release/en/vehicle/ovms_0.yaml | 31 - templates/release/en/vehicle/peugeot.yaml | 161 + templates/release/en/vehicle/peugeot_0.yaml | 32 - templates/release/en/vehicle/polestar.yaml | 148 + templates/release/en/vehicle/polestar_0.yaml | 28 - .../en/vehicle/psa-car-controller.yaml | 139 + templates/release/en/vehicle/renault.yaml | 157 + templates/release/en/vehicle/renault_0.yaml | 28 - ...ect-gen3-ateca-leon-formentor-tarraco.yaml | 148 + ...aconnect-gen4-born-formentor-tavascan.yaml | 168 + templates/release/en/vehicle/seat_0.yaml | 28 - templates/release/en/vehicle/skoda-enyaq.yaml | 159 + templates/release/en/vehicle/smart-1.yaml | 168 + templates/release/en/vehicle/smart-eq.yaml | 173 + .../release/en/vehicle/smart-hello_0.yaml | 30 - templates/release/en/vehicle/smart_0.yaml | 35 - templates/release/en/vehicle/tesla-ble.yaml | 140 + templates/release/en/vehicle/tesla-ble_0.yaml | 29 - templates/release/en/vehicle/tesla.yaml | 195 ++ templates/release/en/vehicle/tesla_0.yaml | 48 - templates/release/en/vehicle/teslalogger.yaml | 140 + .../release/en/vehicle/teslalogger_0.yaml | 29 - templates/release/en/vehicle/teslamate.yaml | 118 + templates/release/en/vehicle/teslamate_0.yaml | 25 - templates/release/en/vehicle/tessie.yaml | 129 + templates/release/en/vehicle/tessie_0.yaml | 27 - templates/release/en/vehicle/toyota.yaml | 150 + templates/release/en/vehicle/toyota_0.yaml | 30 - templates/release/en/vehicle/tronity.yaml | 149 + templates/release/en/vehicle/tronity_0.yaml | 29 - .../en/vehicle/volkswagen-we-connect-id.yaml | 181 + .../release/en/vehicle/volvo-connected_0.yaml | 40 - templates/release/en/vehicle/volvo.yaml | 169 + templates/release/en/vehicle/volvo2mqtt.yaml | 129 + .../release/en/vehicle/volvo2mqtt_0.yaml | 27 - templates/release/en/vehicle/vw_0.yaml | 34 - .../release/en/vehicle/zero-motorcycles.yaml | 147 + templates/release/en/vehicle/zero_0.yaml | 27 - 3650 files changed, 124351 insertions(+), 51196 deletions(-) create mode 100644 docs/devices-next/chargers/abb-terra-ac-ocpp.mdx delete mode 100644 docs/devices-next/chargers/abl-em4-sbcx.mdx create mode 100644 docs/devices-next/chargers/abl-em4-single-ocpp.mdx create mode 100644 docs/devices-next/chargers/abl-em4-single-sbcx.mdx create mode 100644 docs/devices-next/chargers/abl-em4-twin-ocpp.mdx create mode 100644 docs/devices-next/chargers/abl-em4-twin-sbcx.mdx create mode 100644 docs/devices-next/chargers/abl-emh2-ocpp.mdx create mode 100644 docs/devices-next/chargers/abl-emh3-ocpp.mdx delete mode 100644 docs/devices-next/chargers/abl-sursum-emh2.mdx delete mode 100644 docs/devices-next/chargers/abl-sursum-emh3.mdx delete mode 100644 docs/devices-next/chargers/abl-sursum-emh4.mdx create mode 100644 docs/devices-next/chargers/alfen-eve-ocpp.mdx create mode 100644 docs/devices-next/chargers/alpha-innotec.mdx delete mode 100644 docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx create mode 100644 docs/devices-next/chargers/alphatec-wallbox-mini.mdx create mode 100644 docs/devices-next/chargers/alphatec-wallbox-power.mdx create mode 100644 docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx create mode 100644 docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx create mode 100644 docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx delete mode 100644 docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx delete mode 100644 docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx delete mode 100644 docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx delete mode 100644 docs/devices-next/chargers/ampure-live.mdx delete mode 100644 docs/devices-next/chargers/audi-audi-wallbox-pro.mdx create mode 100644 docs/devices-next/chargers/audi-wallbox-pro.mdx create mode 100644 docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx create mode 100644 docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx create mode 100644 docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx delete mode 100644 docs/devices-next/chargers/cubos-c11e-c22e.mdx create mode 100644 docs/devices-next/chargers/cubos-c11e.mdx create mode 100644 docs/devices-next/chargers/cubos-c22e.mdx create mode 100644 docs/devices-next/chargers/e-on-drive-ebox.mdx create mode 100644 docs/devices-next/chargers/e-on-drive-vbox.mdx create mode 100644 docs/devices-next/chargers/e3-dc-easy-connect.mdx delete mode 100644 docs/devices-next/chargers/e3dc-easy-connect.mdx delete mode 100644 docs/devices-next/chargers/echarge-cph2-cpm2.mdx create mode 100644 docs/devices-next/chargers/echarge-cph2.mdx create mode 100644 docs/devices-next/chargers/echarge-cpm2.mdx create mode 100644 docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx delete mode 100644 docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx create mode 100644 docs/devices-next/chargers/elco.mdx create mode 100644 docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx delete mode 100644 docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx delete mode 100644 docs/devices-next/chargers/en-ac-ev-charger.mdx create mode 100644 docs/devices-next/chargers/enplus-ac-ev-charger.mdx delete mode 100644 docs/devices-next/chargers/eon-drive-ebox.mdx delete mode 100644 docs/devices-next/chargers/eon-drive-vbox.mdx create mode 100644 docs/devices-next/chargers/free2move-eprowallbox-move.mdx create mode 100644 docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx delete mode 100644 docs/devices-next/chargers/fronius-wattpilot.mdx delete mode 100644 docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx create mode 100644 docs/devices-next/chargers/garo-glb.mdx create mode 100644 docs/devices-next/chargers/garo-glbplus.mdx create mode 100644 docs/devices-next/chargers/garo-ls4-compact.mdx create mode 100644 docs/devices-next/chargers/garo-ls4.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx delete mode 100644 docs/devices-next/chargers/go-e-charger-home.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-homeplus.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx create mode 100644 docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx create mode 100644 docs/devices-next/chargers/hardy-barth-cph1.mdx create mode 100644 docs/devices-next/chargers/hardy-barth-cph2.mdx create mode 100644 docs/devices-next/chargers/hardy-barth-cpm2.mdx delete mode 100644 docs/devices-next/chargers/hardybarth-cph1.mdx delete mode 100644 docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx create mode 100644 docs/devices-next/chargers/hesotec-ebox.mdx delete mode 100644 docs/devices-next/chargers/hesotec-esat-ebox.mdx create mode 100644 docs/devices-next/chargers/hesotec-esat.mdx create mode 100644 docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx delete mode 100644 docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx create mode 100644 docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx delete mode 100644 docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx create mode 100644 docs/devices-next/chargers/kathrein-kwb-ac20.mdx create mode 100644 docs/devices-next/chargers/kathrein-kwb-ac35.mdx create mode 100644 docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx create mode 100644 docs/devices-next/chargers/kathrein-kwb-ac40.mdx create mode 100644 docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx create mode 100644 docs/devices-next/chargers/kathrein-kwb-ac60.mdx delete mode 100644 docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx create mode 100644 docs/devices-next/chargers/keba-kecontact-p20.mdx create mode 100644 docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx create mode 100644 docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx delete mode 100644 docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx create mode 100644 docs/devices-next/chargers/keba-kecontact-p40-pro.mdx create mode 100644 docs/devices-next/chargers/keba-kecontact-p40.mdx delete mode 100644 docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx create mode 100644 docs/devices-next/chargers/ladefoxx-evload.mdx create mode 100644 docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx delete mode 100644 docs/devices-next/chargers/lrt-home-essential.mdx create mode 100644 docs/devices-next/chargers/lrt-home-essentialplus.mdx create mode 100644 docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx delete mode 100644 docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx create mode 100644 docs/devices-next/chargers/my-pv-ac-thor-9s.mdx delete mode 100644 docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx create mode 100644 docs/devices-next/chargers/my-pv-ac-thor.mdx create mode 100644 docs/devices-next/chargers/nibe-ap-aw10.mdx create mode 100644 docs/devices-next/chargers/novelan-wpr-net.mdx create mode 100644 docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx delete mode 100644 docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx create mode 100644 docs/devices-next/chargers/openwb-software-2-x.mdx delete mode 100644 docs/devices-next/chargers/openwb-software-2x.mdx create mode 100644 docs/devices-next/chargers/peblar-business.mdx delete mode 100644 docs/devices-next/chargers/peblar-home-home-plus-business.mdx create mode 100644 docs/devices-next/chargers/peblar-home-plus.mdx create mode 100644 docs/devices-next/chargers/peblar-home.mdx delete mode 100644 docs/devices-next/chargers/pracht-xt.mdx create mode 100644 docs/devices-next/chargers/pracht-xtplus.mdx create mode 100644 docs/devices-next/chargers/qcells-q-home-edrive-a.mdx delete mode 100644 docs/devices-next/chargers/qcells-qhome-edrive-a.mdx create mode 100644 docs/devices-next/chargers/roth-thermoaura.mdx create mode 100644 docs/devices-next/chargers/roth-thermoterra.mdx create mode 100644 docs/devices-next/chargers/shelly-1.mdx create mode 100644 docs/devices-next/chargers/shelly-plug-s.mdx create mode 100644 docs/devices-next/chargers/shelly-plus-1.mdx create mode 100644 docs/devices-next/chargers/shelly-pro-1.mdx delete mode 100644 docs/devices-next/chargers/shelly.mdx create mode 100644 docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx create mode 100644 docs/devices-next/chargers/sma-echarger.mdx delete mode 100644 docs/devices-next/chargers/sma-ev-charger-echarger.mdx create mode 100644 docs/devices-next/chargers/sma-ev-charger.mdx create mode 100644 docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx delete mode 100644 docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx create mode 100644 docs/devices-next/chargers/sungrow-ac22e-01.mdx delete mode 100644 docs/devices-next/chargers/tesla-twc3.mdx create mode 100644 docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx create mode 100644 docs/devices-next/chargers/vestel-connect-plus.mdx delete mode 100644 docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx create mode 100644 docs/devices-next/chargers/vestel-evc04-home-smart.mdx create mode 100644 docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx delete mode 100644 docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx create mode 100644 docs/devices-next/chargers/wallbe-eco-2-0-s.mdx delete mode 100644 docs/devices-next/chargers/wallbe-eco-20s.mdx create mode 100644 docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx delete mode 100644 docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx delete mode 100644 docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx delete mode 100644 docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx delete mode 100644 docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx create mode 100644 docs/devices-next/chargers/wolf-bwl.mdx create mode 100644 docs/devices-next/chargers/wolf-bws.mdx create mode 100644 docs/devices-next/chargers/zaptec-go-ocpp.mdx delete mode 100644 docs/devices-next/meters/abb-a43-a44-b23-b24.mdx create mode 100644 docs/devices-next/meters/abb-a43.mdx create mode 100644 docs/devices-next/meters/abb-a44.mdx create mode 100644 docs/devices-next/meters/abb-b23.mdx create mode 100644 docs/devices-next/meters/abb-b24.mdx delete mode 100644 docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx create mode 100644 docs/devices-next/meters/acrel-adw300.mdx create mode 100644 docs/devices-next/meters/ampere-ampere-storagepro.mdx delete mode 100644 docs/devices-next/meters/ampere-amperestoragepro.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx delete mode 100644 docs/devices-next/meters/carlo-gavazzi-em110111112.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx delete mode 100644 docs/devices-next/meters/carlo-gavazzi-em24e1.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx delete mode 100644 docs/devices-next/meters/carlo-gavazzi-em330em340.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx delete mode 100644 docs/devices-next/meters/carlo-gavazzi-em530em540.mdx create mode 100644 docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx delete mode 100644 docs/devices-next/meters/carlo-gavazzi-et330et340.mdx create mode 100644 docs/devices-next/meters/e3-dc.mdx delete mode 100644 docs/devices-next/meters/e3dc.mdx create mode 100644 docs/devices-next/meters/eastron-sdm220-230.mdx delete mode 100644 docs/devices-next/meters/eastron-sdm220230.mdx create mode 100644 docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx delete mode 100644 docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx delete mode 100644 docs/devices-next/meters/goodwe-sdtdt-inverter.mdx create mode 100644 docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx delete mode 100644 docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx delete mode 100644 docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx delete mode 100644 docs/devices-next/meters/janitza-b-series-umg-series.mdx create mode 100644 docs/devices-next/meters/janitza-b-series.mdx create mode 100644 docs/devices-next/meters/janitza-umg-series.mdx create mode 100644 docs/devices-next/meters/kostal-piko-ba.mdx delete mode 100644 docs/devices-next/meters/kostal-piko-piko-ba.mdx create mode 100644 docs/devices-next/meters/kostal-piko.mdx create mode 100644 docs/devices-next/meters/lg-ess-home-8-10.mdx delete mode 100644 docs/devices-next/meters/lg-ess-home-810.mdx create mode 100644 docs/devices-next/meters/my-pv-ac-thor.mdx delete mode 100644 docs/devices-next/meters/my-pv-acthor.mdx delete mode 100644 docs/devices-next/meters/orno-or-we-516-or-we-517.mdx create mode 100644 docs/devices-next/meters/orno-or-we-516.mdx create mode 100644 docs/devices-next/meters/orno-or-we-517.mdx create mode 100644 docs/devices-next/meters/p1monitor-p1-monitor.mdx delete mode 100644 docs/devices-next/meters/p1monitor.mdx create mode 100644 docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx delete mode 100644 docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx delete mode 100644 docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx create mode 100644 docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx create mode 100644 docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx create mode 100644 docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx delete mode 100644 docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx delete mode 100644 docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx create mode 100644 docs/devices-next/meters/shelly-1pm-mini.mdx create mode 100644 docs/devices-next/meters/shelly-1pm.mdx create mode 100644 docs/devices-next/meters/shelly-em.mdx create mode 100644 docs/devices-next/meters/shelly-plug-s.mdx create mode 100644 docs/devices-next/meters/shelly-pm-mini.mdx create mode 100644 docs/devices-next/meters/shelly-pro-1pm.mdx create mode 100644 docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx create mode 100644 docs/devices-next/meters/shelly-pro-em.mdx create mode 100644 docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx delete mode 100644 docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx create mode 100644 docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx delete mode 100644 docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx create mode 100644 docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx delete mode 100644 docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx create mode 100644 docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx delete mode 100644 docs/devices-next/meters/sma-sunny-home-manager-20.mdx delete mode 100644 docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx create mode 100644 docs/devices-next/meters/smartfox-box.mdx create mode 100644 docs/devices-next/meters/smartfox-light-em2-firmware.mdx create mode 100644 docs/devices-next/meters/smartfox-pro-2.mdx create mode 100644 docs/devices-next/meters/smartfox-pro-light-2.mdx create mode 100644 docs/devices-next/meters/smartfox-pro-light.mdx delete mode 100644 docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx create mode 100644 docs/devices-next/meters/smartfox-pro.mdx create mode 100644 docs/devices-next/meters/smartfox-reg-extended.mdx create mode 100644 docs/devices-next/meters/smartfox-reg.mdx create mode 100644 docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx delete mode 100644 docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx create mode 100644 docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx delete mode 100644 docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx delete mode 100644 docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/sofarsolar-inverter.mdx create mode 100644 docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx delete mode 100644 docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx create mode 100644 docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx delete mode 100644 docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx create mode 100644 docs/devices-next/meters/solaranzeige-solaranzeige.mdx delete mode 100644 docs/devices-next/meters/solaranzeige.mdx create mode 100644 docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx delete mode 100644 docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx delete mode 100644 docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx create mode 100644 docs/devices-next/meters/solarwatt-energymanager-pro.mdx create mode 100644 docs/devices-next/meters/solarwatt-energymanager.mdx create mode 100644 docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx delete mode 100644 docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx delete mode 100644 docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx create mode 100644 docs/devices-next/meters/sonnen-comfort.mdx create mode 100644 docs/devices-next/meters/sonnen-eco-5.mdx create mode 100644 docs/devices-next/meters/sonnen-eco-6.mdx create mode 100644 docs/devices-next/meters/sonnen-oem-6-5.mdx create mode 100644 docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx delete mode 100644 docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx create mode 100644 docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx delete mode 100644 docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx create mode 100644 docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx delete mode 100644 docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx create mode 100644 docs/devices-next/meters/varta-element.mdx create mode 100644 docs/devices-next/meters/varta-pulse-neo.mdx delete mode 100644 docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx create mode 100644 docs/devices-next/meters/varta-pulse.mdx create mode 100644 docs/devices-next/meters/victron-em24_e1.mdx delete mode 100644 docs/devices-next/meters/victron-em24e1.mdx create mode 100644 docs/devices-next/meters/victron-em530-em540.mdx delete mode 100644 docs/devices-next/meters/victron-em530em540.mdx create mode 100644 docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx delete mode 100644 docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx create mode 100644 docs/devices-next/meters/zcs-azzurro-inverter.mdx delete mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx create mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx create mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx create mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx delete mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx delete mode 100644 docs/devices-next/meters/zuidwijk-slimmelezer.mdx create mode 100644 docs/devices-next/tariffs/forecast-solar.mdx delete mode 100644 docs/devices-next/tariffs/forecastsolar.mdx create mode 100644 docs/devices-next/vehicles/iobroker-bmw.mdx delete mode 100644 docs/devices-next/vehicles/iobrokerbmw.mdx create mode 100644 docs/devices-next/vehicles/smart-1.mdx delete mode 100644 docs/devices-next/vehicles/smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx delete mode 100644 templates/release/de/charger/Kathrein_0.yaml delete mode 100644 templates/release/de/charger/Kathrein_1.yaml delete mode 100644 templates/release/de/charger/Kathrein_2.yaml delete mode 100644 templates/release/de/charger/Kathrein_3.yaml delete mode 100644 templates/release/de/charger/Kathrein_4.yaml delete mode 100644 templates/release/de/charger/Kathrein_5.yaml create mode 100644 templates/release/de/charger/abb-terra-ac-ocpp.yaml create mode 100644 templates/release/de/charger/abb-terra-ac.yaml delete mode 100644 templates/release/de/charger/abb_0.yaml create mode 100644 templates/release/de/charger/abl-em4-single-ocpp.yaml create mode 100644 templates/release/de/charger/abl-em4-single-sbcx.yaml create mode 100644 templates/release/de/charger/abl-em4-twin-ocpp.yaml create mode 100644 templates/release/de/charger/abl-em4-twin-sbcx.yaml delete mode 100644 templates/release/de/charger/abl-em4_0.yaml create mode 100644 templates/release/de/charger/abl-emh1.yaml create mode 100644 templates/release/de/charger/abl-emh2-ocpp.yaml create mode 100644 templates/release/de/charger/abl-emh2.yaml create mode 100644 templates/release/de/charger/abl-emh3-ocpp.yaml delete mode 100644 templates/release/de/charger/abl_0.yaml delete mode 100644 templates/release/de/charger/abl_1.yaml delete mode 100644 templates/release/de/charger/abl_2.yaml delete mode 100644 templates/release/de/charger/ac-elwa-2_0.yaml delete mode 100644 templates/release/de/charger/ac-thor_0.yaml delete mode 100644 templates/release/de/charger/ac-thor_1.yaml create mode 100644 templates/release/de/charger/alfen-eve-ocpp.yaml create mode 100644 templates/release/de/charger/alfen-eve.yaml delete mode 100644 templates/release/de/charger/alfen_0.yaml create mode 100644 templates/release/de/charger/alpha-innotec.yaml create mode 100644 templates/release/de/charger/alphatec-ladesaule-twin.yaml create mode 100644 templates/release/de/charger/alphatec-wallbox-mini.yaml create mode 100644 templates/release/de/charger/alphatec-wallbox-power.yaml delete mode 100644 templates/release/de/charger/alphatec_0.yaml delete mode 100644 templates/release/de/charger/alphatec_1.yaml delete mode 100644 templates/release/de/charger/alphatec_2.yaml delete mode 100644 templates/release/de/charger/alphatec_3.yaml delete mode 100644 templates/release/de/charger/amperfied-solar_0.yaml create mode 100644 templates/release/de/charger/amperfied-wallbox-connect-business.yaml create mode 100644 templates/release/de/charger/amperfied-wallbox-connect-home.yaml create mode 100644 templates/release/de/charger/amperfied-wallbox-connect-solar.yaml create mode 100644 templates/release/de/charger/amperfied-wallbox-energy-control.yaml delete mode 100644 templates/release/de/charger/amperfied_0.yaml delete mode 100644 templates/release/de/charger/amperfied_1.yaml create mode 100644 templates/release/de/charger/ampure-next.yaml create mode 100644 templates/release/de/charger/ampure-unite.yaml create mode 100644 templates/release/de/charger/audi-wallbox-plus.yaml create mode 100644 templates/release/de/charger/audi-wallbox-pro.yaml create mode 100644 templates/release/de/charger/autel-ac-compact.yaml create mode 100644 templates/release/de/charger/autel-ac-maxicharger.yaml create mode 100644 templates/release/de/charger/autoaid-business-wallbox.yaml create mode 100644 templates/release/de/charger/autoaid-intelligent-wallbox.yaml create mode 100644 templates/release/de/charger/avm-fritzdect.yaml create mode 100644 templates/release/de/charger/bender-cc612.yaml create mode 100644 templates/release/de/charger/bender-cc613.yaml delete mode 100644 templates/release/de/charger/bender-cc_0.yaml delete mode 100644 templates/release/de/charger/bender-cc_1.yaml delete mode 100644 templates/release/de/charger/bender-cc_10.yaml delete mode 100644 templates/release/de/charger/bender-cc_11.yaml delete mode 100644 templates/release/de/charger/bender-cc_12.yaml delete mode 100644 templates/release/de/charger/bender-cc_13.yaml delete mode 100644 templates/release/de/charger/bender-cc_14.yaml delete mode 100644 templates/release/de/charger/bender-cc_15.yaml delete mode 100644 templates/release/de/charger/bender-cc_2.yaml delete mode 100644 templates/release/de/charger/bender-cc_3.yaml delete mode 100644 templates/release/de/charger/bender-cc_4.yaml delete mode 100644 templates/release/de/charger/bender-cc_5.yaml delete mode 100644 templates/release/de/charger/bender-cc_6.yaml delete mode 100644 templates/release/de/charger/bender-cc_7.yaml delete mode 100644 templates/release/de/charger/bender-cc_8.yaml delete mode 100644 templates/release/de/charger/bender-cc_9.yaml create mode 100644 templates/release/de/charger/bender-icc1314.yaml create mode 100644 templates/release/de/charger/bender-icc1324.yaml delete mode 100644 templates/release/de/charger/bender-icc_0.yaml delete mode 100644 templates/release/de/charger/bender-icc_1.yaml delete mode 100644 templates/release/de/charger/bender-icc_2.yaml delete mode 100644 templates/release/de/charger/bender-icc_3.yaml create mode 100644 templates/release/de/charger/bmw-i-wallbox.yaml create mode 100644 templates/release/de/charger/bosch-sg-ready.yaml create mode 100644 templates/release/de/charger/bosch-x-change.yaml create mode 100644 templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml create mode 100644 templates/release/de/charger/buderus-logamatic-hmc-20.yaml create mode 100644 templates/release/de/charger/buderus-sg-ready.yaml create mode 100644 templates/release/de/charger/cfos-power-brain-solar.yaml create mode 100644 templates/release/de/charger/cfos-power-brain.yaml delete mode 100644 templates/release/de/charger/cfos_0.yaml delete mode 100644 templates/release/de/charger/cfos_1.yaml create mode 100644 templates/release/de/charger/charge-amps-halo.yaml create mode 100644 templates/release/de/charger/compleo-ebox.yaml create mode 100644 templates/release/de/charger/cta-all-in-one-aeroplus.yaml create mode 100644 templates/release/de/charger/cubos-c11e.yaml create mode 100644 templates/release/de/charger/cubos-c22e.yaml create mode 100644 templates/release/de/charger/cupra-charger-connect-2.yaml create mode 100644 templates/release/de/charger/cupra-charger-connect.yaml create mode 100644 templates/release/de/charger/cupra-charger-pro-2.yaml create mode 100644 templates/release/de/charger/cupra-charger-pro-eichrecht-2.yaml create mode 100644 templates/release/de/charger/cupra-charger-pro.yaml create mode 100644 templates/release/de/charger/dadapower-premium-wallbox.yaml delete mode 100644 templates/release/de/charger/dadapower_0.yaml delete mode 100644 templates/release/de/charger/daheimladen-mb_0.yaml create mode 100644 templates/release/de/charger/daheimladen-wallbox.yaml create mode 100644 templates/release/de/charger/daikin-homehub-sg-ready.yaml delete mode 100644 templates/release/de/charger/daikin-homehub_0.yaml create mode 100644 templates/release/de/charger/delta-ac-max-basic.yaml create mode 100644 templates/release/de/charger/delta-ac-max-smart.yaml create mode 100644 templates/release/de/charger/delta-slim-charger.yaml create mode 100644 templates/release/de/charger/delta-ultra-fast-charger.yaml delete mode 100644 templates/release/de/charger/delta_0.yaml delete mode 100644 templates/release/de/charger/delta_1.yaml delete mode 100644 templates/release/de/charger/delta_2.yaml delete mode 100644 templates/release/de/charger/delta_3.yaml create mode 100644 templates/release/de/charger/demo-charger.yaml delete mode 100644 templates/release/de/charger/demo-charger_0.yaml create mode 100644 templates/release/de/charger/e-on-drive-ebox.yaml create mode 100644 templates/release/de/charger/e-on-drive-vbox.yaml create mode 100644 templates/release/de/charger/e3-dc-easy-connect.yaml create mode 100644 templates/release/de/charger/easee-charge-core.yaml create mode 100644 templates/release/de/charger/easee-charge-lite.yaml create mode 100644 templates/release/de/charger/easee-charge.yaml create mode 100644 templates/release/de/charger/easee-home.yaml delete mode 100644 templates/release/de/charger/easee_0.yaml delete mode 100644 templates/release/de/charger/easee_1.yaml delete mode 100644 templates/release/de/charger/easee_2.yaml delete mode 100644 templates/release/de/charger/easee_3.yaml create mode 100644 templates/release/de/charger/ebee-wallbox.yaml create mode 100644 templates/release/de/charger/echarge-cph1.yaml create mode 100644 templates/release/de/charger/echarge-cph2.yaml create mode 100644 templates/release/de/charger/echarge-cpm2.yaml create mode 100644 templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml create mode 100644 templates/release/de/charger/edgetech-smart-evse.yaml create mode 100644 templates/release/de/charger/eebus-compatible.yaml delete mode 100644 templates/release/de/charger/eebus_0.yaml create mode 100644 templates/release/de/charger/elco.yaml create mode 100644 templates/release/de/charger/elecq-biz.yaml create mode 100644 templates/release/de/charger/elecq-home.yaml create mode 100644 templates/release/de/charger/elecq-station.yaml create mode 100644 templates/release/de/charger/eledio-go.yaml delete mode 100644 templates/release/de/charger/elli-2_0.yaml delete mode 100644 templates/release/de/charger/elli-2_1.yaml delete mode 100644 templates/release/de/charger/elli-2_10.yaml delete mode 100644 templates/release/de/charger/elli-2_11.yaml delete mode 100644 templates/release/de/charger/elli-2_2.yaml delete mode 100644 templates/release/de/charger/elli-2_3.yaml delete mode 100644 templates/release/de/charger/elli-2_4.yaml delete mode 100644 templates/release/de/charger/elli-2_5.yaml delete mode 100644 templates/release/de/charger/elli-2_6.yaml delete mode 100644 templates/release/de/charger/elli-2_7.yaml delete mode 100644 templates/release/de/charger/elli-2_8.yaml delete mode 100644 templates/release/de/charger/elli-2_9.yaml create mode 100644 templates/release/de/charger/elli-charger-connect-2.yaml create mode 100644 templates/release/de/charger/elli-charger-connect.yaml create mode 100644 templates/release/de/charger/elli-charger-pro-2.yaml create mode 100644 templates/release/de/charger/elli-charger-pro-eichrecht-2.yaml create mode 100644 templates/release/de/charger/elli-charger-pro.yaml delete mode 100644 templates/release/de/charger/elliconnect_0.yaml delete mode 100644 templates/release/de/charger/elliconnect_1.yaml delete mode 100644 templates/release/de/charger/elliconnect_2.yaml delete mode 100644 templates/release/de/charger/elliconnect_3.yaml delete mode 100644 templates/release/de/charger/elliconnect_4.yaml delete mode 100644 templates/release/de/charger/ellipro_0.yaml delete mode 100644 templates/release/de/charger/ellipro_1.yaml delete mode 100644 templates/release/de/charger/ellipro_2.yaml delete mode 100644 templates/release/de/charger/ellipro_3.yaml delete mode 100644 templates/release/de/charger/ellipro_4.yaml create mode 100644 templates/release/de/charger/em2go-home.yaml delete mode 100644 templates/release/de/charger/em2go-home_0.yaml create mode 100644 templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml delete mode 100644 templates/release/de/charger/em2go_0.yaml delete mode 100644 templates/release/de/charger/emsesp_0.yaml delete mode 100644 templates/release/de/charger/emsesp_1.yaml delete mode 100644 templates/release/de/charger/emsesp_2.yaml create mode 100644 templates/release/de/charger/enercab-smart.yaml create mode 100644 templates/release/de/charger/enplus-ac-ev-charger.yaml create mode 100644 templates/release/de/charger/ensto-chago-wallbox.yaml create mode 100644 templates/release/de/charger/entratek-power-dot-fix.yaml create mode 100644 templates/release/de/charger/entratek-power-dot-pro-2.yaml delete mode 100644 templates/release/de/charger/eprowallbox_0.yaml create mode 100644 templates/release/de/charger/esl-walli-light.yaml create mode 100644 templates/release/de/charger/esystems-ghostone.yaml delete mode 100644 templates/release/de/charger/etrel-duo_0.yaml create mode 100644 templates/release/de/charger/etrel-inch-duo.yaml create mode 100644 templates/release/de/charger/etrel-inch.yaml delete mode 100644 templates/release/de/charger/etrel_0.yaml delete mode 100644 templates/release/de/charger/etrel_1.yaml create mode 100644 templates/release/de/charger/evbox-elvi.yaml create mode 100644 templates/release/de/charger/evbox-livo.yaml create mode 100644 templates/release/de/charger/evse-din.yaml delete mode 100644 templates/release/de/charger/evse-din_0.yaml delete mode 100644 templates/release/de/charger/evse-din_1.yaml create mode 100644 templates/release/de/charger/evse-wifi.yaml delete mode 100644 templates/release/de/charger/evsewifi_0.yaml create mode 100644 templates/release/de/charger/free2move-eprowallbox-move.yaml create mode 100644 templates/release/de/charger/free2move-eprowallbox.yaml create mode 100644 templates/release/de/charger/free2move-esolutions-eprowallbox.yaml delete mode 100644 templates/release/de/charger/fritzdect_0.yaml create mode 100644 templates/release/de/charger/fronius-wattpilot-ocpp.yaml create mode 100644 templates/release/de/charger/garo-glb.yaml create mode 100644 templates/release/de/charger/garo-glbplus.yaml create mode 100644 templates/release/de/charger/garo-ls4-compact.yaml create mode 100644 templates/release/de/charger/garo-ls4.yaml delete mode 100644 templates/release/de/charger/ghost_0.yaml delete mode 100644 templates/release/de/charger/ghost_1.yaml create mode 100644 templates/release/de/charger/go-e-charger-gemini-ocpp.yaml create mode 100644 templates/release/de/charger/go-e-charger-gemini.yaml create mode 100644 templates/release/de/charger/go-e-charger-homefix.yaml create mode 100644 templates/release/de/charger/go-e-charger-homeplus.yaml create mode 100644 templates/release/de/charger/go-e-charger-pro-ocpp.yaml create mode 100644 templates/release/de/charger/go-e-charger-pro.yaml create mode 100644 templates/release/de/charger/go-e-charger-v3-ocpp.yaml create mode 100644 templates/release/de/charger/go-e-charger-v3.yaml delete mode 100644 templates/release/de/charger/go-e-v3_0.yaml delete mode 100644 templates/release/de/charger/go-e-v3_1.yaml delete mode 100644 templates/release/de/charger/go-e-v3_2.yaml delete mode 100644 templates/release/de/charger/go-e_0.yaml delete mode 100644 templates/release/de/charger/go-e_1.yaml create mode 100644 templates/release/de/charger/hardy-barth-cph1.yaml create mode 100644 templates/release/de/charger/hardy-barth-cph2.yaml create mode 100644 templates/release/de/charger/hardy-barth-cpm2.yaml delete mode 100644 templates/release/de/charger/hardybarth-ecb1_0.yaml delete mode 100644 templates/release/de/charger/hardybarth-ecb1_1.yaml delete mode 100644 templates/release/de/charger/hardybarth-salia_0.yaml delete mode 100644 templates/release/de/charger/hardybarth-salia_1.yaml delete mode 100644 templates/release/de/charger/hardybarth-salia_2.yaml delete mode 100644 templates/release/de/charger/hardybarth-salia_3.yaml create mode 100644 templates/release/de/charger/heidelberg-energy-control.yaml delete mode 100644 templates/release/de/charger/heidelberg_0.yaml delete mode 100644 templates/release/de/charger/heidelberg_1.yaml delete mode 100644 templates/release/de/charger/heidelberg_2.yaml delete mode 100644 templates/release/de/charger/heidelberg_3.yaml create mode 100644 templates/release/de/charger/hesotec-ebox.yaml create mode 100644 templates/release/de/charger/hesotec-esat.yaml delete mode 100644 templates/release/de/charger/hesotec_0.yaml delete mode 100644 templates/release/de/charger/hesotec_1.yaml create mode 100644 templates/release/de/charger/home-assistant-switch.yaml delete mode 100644 templates/release/de/charger/homeassistant-switch_0.yaml create mode 100644 templates/release/de/charger/homecharge-homecharger.yaml create mode 100644 templates/release/de/charger/homematic-ip.yaml delete mode 100644 templates/release/de/charger/homematic_0.yaml create mode 100644 templates/release/de/charger/homewizard.yaml delete mode 100644 templates/release/de/charger/homewizard_0.yaml create mode 100644 templates/release/de/charger/huawei-scharger-22kt-s0.yaml create mode 100644 templates/release/de/charger/huawei-scharger-7ks-s0.yaml delete mode 100644 templates/release/de/charger/ichargecion_0.yaml delete mode 100644 templates/release/de/charger/ichargecion_1.yaml create mode 100644 templates/release/de/charger/idm.yaml delete mode 100644 templates/release/de/charger/idm_0.yaml create mode 100644 templates/release/de/charger/innogy-ebox.yaml delete mode 100644 templates/release/de/charger/innogy-ebox_0.yaml delete mode 100644 templates/release/de/charger/innogy-ebox_1.yaml delete mode 100644 templates/release/de/charger/innogy-ebox_2.yaml create mode 100644 templates/release/de/charger/inro-pantabox.yaml create mode 100644 templates/release/de/charger/juice-charger-me.yaml create mode 100644 templates/release/de/charger/junkers-sg-ready.yaml create mode 100644 templates/release/de/charger/kathrein-kwb-ac20.yaml create mode 100644 templates/release/de/charger/kathrein-kwb-ac35.yaml create mode 100644 templates/release/de/charger/kathrein-kwb-ac40-e.yaml create mode 100644 templates/release/de/charger/kathrein-kwb-ac40.yaml create mode 100644 templates/release/de/charger/kathrein-kwb-ac60-e.yaml create mode 100644 templates/release/de/charger/kathrein-kwb-ac60.yaml create mode 100644 templates/release/de/charger/keba-kecontact-p20.yaml create mode 100644 templates/release/de/charger/keba-kecontact-p30-c-series.yaml create mode 100644 templates/release/de/charger/keba-kecontact-p30-x-series.yaml create mode 100644 templates/release/de/charger/keba-kecontact-p40-pro.yaml create mode 100644 templates/release/de/charger/keba-kecontact-p40.yaml delete mode 100644 templates/release/de/charger/keba-modbus_0.yaml delete mode 100644 templates/release/de/charger/keba-modbus_1.yaml delete mode 100644 templates/release/de/charger/keba-modbus_2.yaml delete mode 100644 templates/release/de/charger/keba-modbus_3.yaml delete mode 100644 templates/release/de/charger/keba-modbus_4.yaml delete mode 100644 templates/release/de/charger/keba-modbus_5.yaml delete mode 100644 templates/release/de/charger/keba-modbus_6.yaml create mode 100644 templates/release/de/charger/kermi-x-center-pro.yaml delete mode 100644 templates/release/de/charger/kermi_0.yaml delete mode 100644 templates/release/de/charger/kermi_1.yaml create mode 100644 templates/release/de/charger/kontron-solar-charger.yaml create mode 100644 templates/release/de/charger/kostal-enector.yaml create mode 100644 templates/release/de/charger/kse-wbx16.yaml delete mode 100644 templates/release/de/charger/kse_0.yaml create mode 100644 templates/release/de/charger/ladefoxx-evload.yaml create mode 100644 templates/release/de/charger/ladefoxx-mikro-2-0.yaml create mode 100644 templates/release/de/charger/lambda-eu-l-series.yaml delete mode 100644 templates/release/de/charger/lambda-zewotherm_0.yaml delete mode 100644 templates/release/de/charger/lambda-zewotherm_1.yaml delete mode 100644 templates/release/de/charger/livo_0.yaml create mode 100644 templates/release/de/charger/lrt-home-essentialplus.yaml delete mode 100644 templates/release/de/charger/luxtronik_0.yaml delete mode 100644 templates/release/de/charger/luxtronik_1.yaml delete mode 100644 templates/release/de/charger/luxtronik_10.yaml delete mode 100644 templates/release/de/charger/luxtronik_2.yaml delete mode 100644 templates/release/de/charger/luxtronik_3.yaml delete mode 100644 templates/release/de/charger/luxtronik_4.yaml delete mode 100644 templates/release/de/charger/luxtronik_5.yaml delete mode 100644 templates/release/de/charger/luxtronik_6.yaml delete mode 100644 templates/release/de/charger/luxtronik_7.yaml delete mode 100644 templates/release/de/charger/luxtronik_8.yaml delete mode 100644 templates/release/de/charger/luxtronik_9.yaml create mode 100644 templates/release/de/charger/mennekes-amedio-professional.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-4business-700.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-4you-300.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-4you-500.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-chargecontrol.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-premium.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-professional.yaml create mode 100644 templates/release/de/charger/mennekes-amtron-xtra.yaml delete mode 100644 templates/release/de/charger/mennekes-compact_0.yaml delete mode 100644 templates/release/de/charger/mennekes-compact_1.yaml delete mode 100644 templates/release/de/charger/mennekes-compact_2.yaml create mode 100644 templates/release/de/charger/mennekes-emobility-gateway-acu.yaml delete mode 100644 templates/release/de/charger/mennekes-hcc3_0.yaml delete mode 100644 templates/release/de/charger/mennekes-hcc3_1.yaml create mode 100644 templates/release/de/charger/mennekes-smart-acu.yaml create mode 100644 templates/release/de/charger/mennekes-smart-t-acu.yaml create mode 100644 templates/release/de/charger/my-pv-ac-elwa-2.yaml create mode 100644 templates/release/de/charger/my-pv-ac-thor-9s.yaml create mode 100644 templates/release/de/charger/my-pv-ac-thor.yaml create mode 100644 templates/release/de/charger/mystrom-switch.yaml delete mode 100644 templates/release/de/charger/mystrom_0.yaml create mode 100644 templates/release/de/charger/nibe-ap-aw10.yaml create mode 100644 templates/release/de/charger/novelan-wpr-net.yaml delete mode 100644 templates/release/de/charger/nrggen2_0.yaml create mode 100644 templates/release/de/charger/nrgkick-connect.yaml delete mode 100644 templates/release/de/charger/nrgkick-connect_0.yaml create mode 100644 templates/release/de/charger/nrgkick-gen2.yaml create mode 100644 templates/release/de/charger/obo-bettermann-ion.yaml delete mode 100644 templates/release/de/charger/obo_0.yaml delete mode 100644 templates/release/de/charger/obo_1.yaml delete mode 100644 templates/release/de/charger/obo_2.yaml create mode 100644 templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml delete mode 100644 templates/release/de/charger/ocpp-abb-tac_0.yaml delete mode 100644 templates/release/de/charger/ocpp-abl_0.yaml delete mode 100644 templates/release/de/charger/ocpp-abl_1.yaml delete mode 100644 templates/release/de/charger/ocpp-abl_2.yaml delete mode 100644 templates/release/de/charger/ocpp-alfen_0.yaml delete mode 100644 templates/release/de/charger/ocpp-autel_0.yaml delete mode 100644 templates/release/de/charger/ocpp-autel_1.yaml delete mode 100644 templates/release/de/charger/ocpp-autoaid_0.yaml delete mode 100644 templates/release/de/charger/ocpp-autoaid_1.yaml delete mode 100644 templates/release/de/charger/ocpp-beny_0.yaml delete mode 100644 templates/release/de/charger/ocpp-chargeamps_0.yaml delete mode 100644 templates/release/de/charger/ocpp-elecq_0.yaml delete mode 100644 templates/release/de/charger/ocpp-elecq_1.yaml delete mode 100644 templates/release/de/charger/ocpp-elecq_2.yaml delete mode 100644 templates/release/de/charger/ocpp-enercab_0.yaml delete mode 100644 templates/release/de/charger/ocpp-enercab_1.yaml delete mode 100644 templates/release/de/charger/ocpp-enplus_0.yaml delete mode 100644 templates/release/de/charger/ocpp-entratek_0.yaml delete mode 100644 templates/release/de/charger/ocpp-entratek_1.yaml delete mode 100644 templates/release/de/charger/ocpp-esolutions_0.yaml delete mode 100644 templates/release/de/charger/ocpp-evbox-elvi_0.yaml delete mode 100644 templates/release/de/charger/ocpp-goe_0.yaml delete mode 100644 templates/release/de/charger/ocpp-goe_1.yaml delete mode 100644 templates/release/de/charger/ocpp-goe_2.yaml delete mode 100644 templates/release/de/charger/ocpp-goe_3.yaml delete mode 100644 templates/release/de/charger/ocpp-homecharge_0.yaml delete mode 100644 templates/release/de/charger/ocpp-huawei_0.yaml delete mode 100644 templates/release/de/charger/ocpp-huawei_1.yaml delete mode 100644 templates/release/de/charger/ocpp-mennekes-acu_0.yaml delete mode 100644 templates/release/de/charger/ocpp-mennekes-acu_1.yaml delete mode 100644 templates/release/de/charger/ocpp-mennekes-acu_2.yaml delete mode 100644 templates/release/de/charger/ocpp-orbis_0.yaml delete mode 100644 templates/release/de/charger/ocpp-sungrow_0.yaml delete mode 100644 templates/release/de/charger/ocpp-wallbox_0.yaml delete mode 100644 templates/release/de/charger/ocpp-wallbox_1.yaml delete mode 100644 templates/release/de/charger/ocpp-wallbox_2.yaml delete mode 100644 templates/release/de/charger/ocpp-wallbox_3.yaml delete mode 100644 templates/release/de/charger/ocpp-zaptec_0.yaml delete mode 100644 templates/release/de/charger/ocpp_0.yaml create mode 100644 templates/release/de/charger/openevse.yaml delete mode 100644 templates/release/de/charger/openevse_0.yaml delete mode 100644 templates/release/de/charger/openwb-2.0_0.yaml create mode 100644 templates/release/de/charger/openwb-pro.yaml delete mode 100644 templates/release/de/charger/openwb-pro_0.yaml create mode 100644 templates/release/de/charger/openwb-series2.yaml create mode 100644 templates/release/de/charger/openwb-software-2-x.yaml delete mode 100644 templates/release/de/charger/openwb_0.yaml create mode 100644 templates/release/de/charger/optec-mobility-one.yaml create mode 100644 templates/release/de/charger/orbis-viaris.yaml delete mode 100644 templates/release/de/charger/pantabox_0.yaml create mode 100644 templates/release/de/charger/pc-electric-garo.yaml delete mode 100644 templates/release/de/charger/pcelectric-garo_0.yaml create mode 100644 templates/release/de/charger/peblar-business.yaml create mode 100644 templates/release/de/charger/peblar-home-plus.yaml create mode 100644 templates/release/de/charger/peblar-home.yaml delete mode 100644 templates/release/de/charger/peblar_0.yaml delete mode 100644 templates/release/de/charger/peblar_1.yaml delete mode 100644 templates/release/de/charger/peblar_2.yaml delete mode 100644 templates/release/de/charger/phoenix-charx_0.yaml delete mode 100644 templates/release/de/charger/phoenix-charx_1.yaml delete mode 100644 templates/release/de/charger/phoenix-charx_2.yaml create mode 100644 templates/release/de/charger/phoenix-contact-charx.yaml create mode 100644 templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml create mode 100644 templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml create mode 100644 templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml create mode 100644 templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml create mode 100644 templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml create mode 100644 templates/release/de/charger/phoenix-contact-ev-ser.yaml delete mode 100644 templates/release/de/charger/phoenix-em-eth_0.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_0.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_1.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_2.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_3.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_4.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_5.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_6.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_7.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-eth_8.yaml delete mode 100644 templates/release/de/charger/phoenix-ev-ser_0.yaml create mode 100644 templates/release/de/charger/plugchoice.yaml delete mode 100644 templates/release/de/charger/plugchoice_0.yaml delete mode 100644 templates/release/de/charger/pmcc_0.yaml delete mode 100644 templates/release/de/charger/pmcp_0.yaml create mode 100644 templates/release/de/charger/porsche-mobile-charger-connect.yaml create mode 100644 templates/release/de/charger/porsche-mobile-charger-plus.yaml create mode 100644 templates/release/de/charger/porsche-wallbox.yaml delete mode 100644 templates/release/de/charger/porsche-wallbox_0.yaml create mode 100644 templates/release/de/charger/pracht-alpha-xt.yaml delete mode 100644 templates/release/de/charger/pracht-alpha_0.yaml delete mode 100644 templates/release/de/charger/pracht-alpha_1.yaml delete mode 100644 templates/release/de/charger/pracht-alpha_2.yaml delete mode 100644 templates/release/de/charger/pracht-alpha_3.yaml create mode 100644 templates/release/de/charger/pracht-mono-xt.yaml create mode 100644 templates/release/de/charger/pracht-pni.yaml create mode 100644 templates/release/de/charger/pracht-xtplus.yaml create mode 100644 templates/release/de/charger/pulsares-simplebox.yaml delete mode 100644 templates/release/de/charger/pulsares_0.yaml create mode 100644 templates/release/de/charger/pulsatrix.yaml delete mode 100644 templates/release/de/charger/pulsatrix_0.yaml create mode 100644 templates/release/de/charger/qcells-q-home-edrive-a.yaml create mode 100644 templates/release/de/charger/roth-thermoaura.yaml create mode 100644 templates/release/de/charger/roth-thermoterra.yaml create mode 100644 templates/release/de/charger/schneider-evlink-pro.yaml delete mode 100644 templates/release/de/charger/schneider-evlink-v3_0.yaml create mode 100644 templates/release/de/charger/schrack-i-charge-cion.yaml create mode 100644 templates/release/de/charger/senec-wallbox-pro-s.yaml create mode 100644 templates/release/de/charger/senec-wallbox-pro.yaml create mode 100644 templates/release/de/charger/shelly-1.yaml create mode 100644 templates/release/de/charger/shelly-plug-s.yaml create mode 100644 templates/release/de/charger/shelly-plus-1.yaml create mode 100644 templates/release/de/charger/shelly-pro-1.yaml delete mode 100644 templates/release/de/charger/shelly_0.yaml create mode 100644 templates/release/de/charger/siemens-versicharge-gen3.yaml create mode 100644 templates/release/de/charger/skoda-charger-connect.yaml create mode 100644 templates/release/de/charger/skoda-charger-pro-eichrecht.yaml create mode 100644 templates/release/de/charger/skoda-charger-pro.yaml create mode 100644 templates/release/de/charger/skoda-iv-charger-connect.yaml create mode 100644 templates/release/de/charger/skoda-iv-charger-connectplus.yaml create mode 100644 templates/release/de/charger/sma-echarger.yaml create mode 100644 templates/release/de/charger/sma-ev-charger.yaml delete mode 100644 templates/release/de/charger/smaevcharger_0.yaml delete mode 100644 templates/release/de/charger/smaevcharger_1.yaml delete mode 100644 templates/release/de/charger/smartevse_0.yaml create mode 100644 templates/release/de/charger/smartfox-pro-charger.yaml create mode 100644 templates/release/de/charger/smartwb.yaml delete mode 100644 templates/release/de/charger/smartwb_0.yaml create mode 100644 templates/release/de/charger/solaredge-home-ev-charger.yaml create mode 100644 templates/release/de/charger/solax-x3-evc.yaml delete mode 100644 templates/release/de/charger/solax_0.yaml delete mode 100644 templates/release/de/charger/solax_1.yaml delete mode 100644 templates/release/de/charger/solax_2.yaml create mode 100644 templates/release/de/charger/sonnen-sonnencharger.yaml create mode 100644 templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml create mode 100644 templates/release/de/charger/stark-in-strom-easy.yaml create mode 100644 templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml create mode 100644 templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml delete mode 100644 templates/release/de/charger/stiebel-lwa_0.yaml delete mode 100644 templates/release/de/charger/stiebel-lwa_1.yaml delete mode 100644 templates/release/de/charger/stiebel-wpm_0.yaml create mode 100644 templates/release/de/charger/sungrow-ac011e-01.yaml create mode 100644 templates/release/de/charger/sungrow-ac011e.yaml create mode 100644 templates/release/de/charger/sungrow-ac22e-01.yaml delete mode 100644 templates/release/de/charger/sungrow_0.yaml delete mode 100644 templates/release/de/charger/sungrow_1.yaml delete mode 100644 templates/release/de/charger/tapo_0.yaml create mode 100644 templates/release/de/charger/tasmota-single-phase.yaml delete mode 100644 templates/release/de/charger/tasmota_0.yaml create mode 100644 templates/release/de/charger/tecalor-thz-sg-ready.yaml create mode 100644 templates/release/de/charger/technisat-technivolt.yaml create mode 100644 templates/release/de/charger/tesla-wall-connector-gen-3.yaml create mode 100644 templates/release/de/charger/tessie.yaml delete mode 100644 templates/release/de/charger/tessie_0.yaml create mode 100644 templates/release/de/charger/tigo-go-ev-charger.yaml create mode 100644 templates/release/de/charger/tinkerforge-warp-charger-pro.yaml create mode 100644 templates/release/de/charger/tinkerforge-warp-charger-smart.yaml create mode 100644 templates/release/de/charger/tinkerforge-warp3-charger-pro.yaml create mode 100644 templates/release/de/charger/tinkerforge-warp3-charger-smart.yaml delete mode 100644 templates/release/de/charger/tinkerforge-warp3-smart_0.yaml delete mode 100644 templates/release/de/charger/tinkerforge-warp3_0.yaml delete mode 100644 templates/release/de/charger/tinkerforge-warp_0.yaml delete mode 100644 templates/release/de/charger/tinkerforge-warp_1.yaml create mode 100644 templates/release/de/charger/tp-link-h-series-smart-plug.yaml create mode 100644 templates/release/de/charger/tp-link-tapo-p-series-smart-plug.yaml delete mode 100644 templates/release/de/charger/tplink_0.yaml delete mode 100644 templates/release/de/charger/trydan_0.yaml delete mode 100644 templates/release/de/charger/twc3_0.yaml create mode 100644 templates/release/de/charger/ubitricity-heinz.yaml create mode 100644 templates/release/de/charger/v2c-trydan.yaml create mode 100644 templates/release/de/charger/vaillant-sensonet-sg-ready.yaml delete mode 100644 templates/release/de/charger/vaillant_0.yaml delete mode 100644 templates/release/de/charger/versicharge_0.yaml create mode 100644 templates/release/de/charger/vestel-connect-plus.yaml create mode 100644 templates/release/de/charger/vestel-evc04-home-smart.yaml delete mode 100644 templates/release/de/charger/vestel_0.yaml delete mode 100644 templates/release/de/charger/vestel_1.yaml delete mode 100644 templates/release/de/charger/vestel_2.yaml delete mode 100644 templates/release/de/charger/vestel_3.yaml delete mode 100644 templates/release/de/charger/vestel_4.yaml create mode 100644 templates/release/de/charger/victron-ev-charging-station-via-gx.yaml create mode 100644 templates/release/de/charger/victron-ev-charging-station.yaml delete mode 100644 templates/release/de/charger/victron-evcs_0.yaml delete mode 100644 templates/release/de/charger/victron_0.yaml create mode 100644 templates/release/de/charger/viessmann-heatpump-sg-ready.yaml delete mode 100644 templates/release/de/charger/viessmann_0.yaml create mode 100644 templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml create mode 100644 templates/release/de/charger/volkswagen-charger-connect-2.yaml create mode 100644 templates/release/de/charger/volkswagen-charger-pro-2.yaml create mode 100644 templates/release/de/charger/volkswagen-charger-pro-eichrecht-2.yaml create mode 100644 templates/release/de/charger/volkswagen-id-charger-connect.yaml create mode 100644 templates/release/de/charger/volkswagen-id-charger-pro.yaml create mode 100644 templates/release/de/charger/volt-time-one.yaml create mode 100644 templates/release/de/charger/volt-time-source-2.yaml create mode 100644 templates/release/de/charger/volt-time-source-2s.yaml create mode 100644 templates/release/de/charger/volt-time-source.yaml delete mode 100644 templates/release/de/charger/volttime_0.yaml delete mode 100644 templates/release/de/charger/volttime_1.yaml delete mode 100644 templates/release/de/charger/volttime_2.yaml delete mode 100644 templates/release/de/charger/volttime_3.yaml create mode 100644 templates/release/de/charger/wallbe-eco-2-0-s.yaml create mode 100644 templates/release/de/charger/wallbe-eco.yaml create mode 100644 templates/release/de/charger/wallbe-pro.yaml create mode 100644 templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml create mode 100644 templates/release/de/charger/wallbox-commander-2.yaml create mode 100644 templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml create mode 100644 templates/release/de/charger/wallbox-copper-sb.yaml delete mode 100644 templates/release/de/charger/wallbox-fw5_0.yaml delete mode 100644 templates/release/de/charger/wallbox-fw5_1.yaml delete mode 100644 templates/release/de/charger/wallbox-fw5_2.yaml delete mode 100644 templates/release/de/charger/wallbox-fw5_3.yaml create mode 100644 templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml create mode 100644 templates/release/de/charger/wallbox-pulsar-max.yaml create mode 100644 templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml create mode 100644 templates/release/de/charger/wallbox-pulsar-plus.yaml create mode 100644 templates/release/de/charger/walther-werke-basic-evo-pro.yaml create mode 100644 templates/release/de/charger/webasto-live.yaml create mode 100644 templates/release/de/charger/webasto-next.yaml delete mode 100644 templates/release/de/charger/webasto-next_0.yaml delete mode 100644 templates/release/de/charger/webasto-next_1.yaml create mode 100644 templates/release/de/charger/webasto-unite.yaml create mode 100644 templates/release/de/charger/weidmuller-ac-smart.yaml delete mode 100644 "templates/release/de/charger/weidm\303\274ller_0.yaml" create mode 100644 templates/release/de/charger/wolf-bwl.yaml create mode 100644 templates/release/de/charger/wolf-bws.yaml create mode 100644 templates/release/de/charger/zaptec-go-2.yaml create mode 100644 templates/release/de/charger/zaptec-go-ocpp.yaml create mode 100644 templates/release/de/charger/zaptec-go.yaml create mode 100644 templates/release/de/charger/zaptec-pro.yaml delete mode 100644 templates/release/de/charger/zaptec_0.yaml delete mode 100644 templates/release/de/charger/zaptec_1.yaml delete mode 100644 templates/release/de/charger/zaptec_2.yaml create mode 100644 templates/release/de/charger/zewotherm-eu-l-series.yaml create mode 100644 templates/release/de/charger/zj-beny-bcp-ev-charger.yaml create mode 100644 templates/release/de/meter/a-tronix.yaml create mode 100644 templates/release/de/meter/abb-a43.yaml create mode 100644 templates/release/de/meter/abb-a44.yaml delete mode 100644 templates/release/de/meter/abb-ab_0.yaml create mode 100644 templates/release/de/meter/abb-b23.yaml create mode 100644 templates/release/de/meter/abb-b24.yaml delete mode 100644 templates/release/de/meter/ac-elwa-2_0.yaml delete mode 100644 templates/release/de/meter/ac-elwa-e_0.yaml create mode 100644 templates/release/de/meter/acrel-adw300.yaml delete mode 100644 templates/release/de/meter/acrel-adw300_0.yaml create mode 100644 templates/release/de/meter/ads-tec-storaxe.yaml delete mode 100644 templates/release/de/meter/alpha-ess-smile_0.yaml create mode 100644 templates/release/de/meter/alpha-ess-storion-smile.yaml create mode 100644 templates/release/de/meter/ampere-ampere-storagepro.yaml create mode 100644 templates/release/de/meter/anker-micro-inverter.yaml create mode 100644 templates/release/de/meter/apsystems-ez1.yaml delete mode 100644 templates/release/de/meter/apsystems-ez1_0.yaml create mode 100644 templates/release/de/meter/avm-fritzdect.yaml create mode 100644 templates/release/de/meter/axitec-axihycon-12-15h.yaml create mode 100644 templates/release/de/meter/bernecker-engineering-mpm3pm.yaml delete mode 100644 templates/release/de/meter/bge_tech_ds100_0.yaml delete mode 100644 templates/release/de/meter/bge_tech_ws100_0.yaml create mode 100644 templates/release/de/meter/bgetech-ds100.yaml create mode 100644 templates/release/de/meter/bgetech-ws100.yaml create mode 100644 templates/release/de/meter/bosch-bpt-s-5-hybrid.yaml delete mode 100644 templates/release/de/meter/bosch-bpt_0.yaml create mode 100644 templates/release/de/meter/bosswerk-micro-inverter.yaml create mode 100644 templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml create mode 100644 templates/release/de/meter/carlo-gavazzi-em24.yaml create mode 100644 templates/release/de/meter/carlo-gavazzi-em24_e1.yaml create mode 100644 templates/release/de/meter/carlo-gavazzi-em330-em340.yaml create mode 100644 templates/release/de/meter/carlo-gavazzi-em530-em540.yaml create mode 100644 templates/release/de/meter/carlo-gavazzi-et112.yaml create mode 100644 templates/release/de/meter/carlo-gavazzi-et330-et340.yaml create mode 100644 templates/release/de/meter/cfos-powerbrain-meter.yaml delete mode 100644 templates/release/de/meter/cfos_0.yaml delete mode 100644 templates/release/de/meter/cg-em24_0.yaml delete mode 100644 templates/release/de/meter/cg-em24_1.yaml delete mode 100644 templates/release/de/meter/cg-em24_e1_0.yaml delete mode 100644 templates/release/de/meter/cg-em24_e1_1.yaml delete mode 100644 templates/release/de/meter/cg-emt1xx_0.yaml delete mode 100644 templates/release/de/meter/cg-emt1xx_1.yaml delete mode 100644 templates/release/de/meter/cg-emt3xx_0.yaml delete mode 100644 templates/release/de/meter/cg-emt3xx_1.yaml delete mode 100644 templates/release/de/meter/cg-emt3xx_2.yaml delete mode 100644 templates/release/de/meter/cg-emt3xx_3.yaml delete mode 100644 templates/release/de/meter/cg-emt3xx_4.yaml delete mode 100644 templates/release/de/meter/cg-emt3xx_5.yaml create mode 100644 templates/release/de/meter/demo-battery.yaml delete mode 100644 templates/release/de/meter/demo-battery_0.yaml create mode 100644 templates/release/de/meter/demo-meter.yaml delete mode 100644 templates/release/de/meter/demo-meter_0.yaml create mode 100644 templates/release/de/meter/deye-3p-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/deye-hp3-hybrid-inverter.yaml delete mode 100644 templates/release/de/meter/deye-hybrid-3p_0.yaml delete mode 100644 templates/release/de/meter/deye-hybrid-3p_1.yaml delete mode 100644 templates/release/de/meter/deye-hybrid-hp3_0.yaml delete mode 100644 templates/release/de/meter/deye-hybrid-hp3_1.yaml delete mode 100644 templates/release/de/meter/deye-mi_0.yaml delete mode 100644 templates/release/de/meter/deye-mi_1.yaml delete mode 100644 templates/release/de/meter/deye-mi_2.yaml delete mode 100644 templates/release/de/meter/deye-mi_3.yaml create mode 100644 templates/release/de/meter/deye-micro-inverter.yaml create mode 100644 templates/release/de/meter/deye-storage-hybrid-inverter.yaml delete mode 100644 templates/release/de/meter/deye-storage_0.yaml delete mode 100644 templates/release/de/meter/deye-storage_1.yaml create mode 100644 templates/release/de/meter/deye-string-inverter.yaml delete mode 100644 templates/release/de/meter/deye-string_0.yaml delete mode 100644 templates/release/de/meter/deye-string_1.yaml create mode 100644 templates/release/de/meter/discovergy.yaml delete mode 100644 templates/release/de/meter/discovergy_0.yaml create mode 100644 templates/release/de/meter/dsmr.yaml delete mode 100644 templates/release/de/meter/dsmr_0.yaml create mode 100644 templates/release/de/meter/dzg-dvh4013.yaml delete mode 100644 templates/release/de/meter/dzg_0.yaml create mode 100644 templates/release/de/meter/e3-dc.yaml delete mode 100644 templates/release/de/meter/e3dc-rscp_0.yaml create mode 100644 templates/release/de/meter/eastron-sdm120-modbus.yaml delete mode 100644 templates/release/de/meter/eastron-sdm120_0.yaml create mode 100644 templates/release/de/meter/eastron-sdm220-230.yaml delete mode 100644 templates/release/de/meter/eastron-sdm220_230_0.yaml delete mode 100644 templates/release/de/meter/eastron-sdm220_230_1.yaml delete mode 100644 templates/release/de/meter/eastron-sdm220_230_2.yaml create mode 100644 templates/release/de/meter/eastron-sdm630-modbus.yaml delete mode 100644 templates/release/de/meter/eastron-sdm72_0.yaml create mode 100644 templates/release/de/meter/eastron-sdm72d-m.yaml create mode 100644 templates/release/de/meter/eastron-sdm72dm-v2.yaml delete mode 100644 templates/release/de/meter/eastron_0.yaml delete mode 100644 templates/release/de/meter/eastron_1.yaml delete mode 100644 templates/release/de/meter/eastron_2.yaml delete mode 100644 templates/release/de/meter/eastron_3.yaml delete mode 100644 templates/release/de/meter/eastron_4.yaml create mode 100644 templates/release/de/meter/enphase-iq-envoy.yaml delete mode 100644 templates/release/de/meter/enphase_0.yaml delete mode 100644 templates/release/de/meter/esphome-dlms-austria_0.yaml create mode 100644 templates/release/de/meter/esphome-dlms-meter-austria.yaml create mode 100644 templates/release/de/meter/esphome-dsmr.yaml create mode 100644 templates/release/de/meter/fenecon.yaml delete mode 100644 templates/release/de/meter/fox-ess-h1_0.yaml delete mode 100644 templates/release/de/meter/fox-ess-h3-smart_0.yaml delete mode 100644 templates/release/de/meter/fox-ess-h3_0.yaml create mode 100644 templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml delete mode 100644 templates/release/de/meter/fritzdect_0.yaml delete mode 100644 templates/release/de/meter/fronius-gen24_0.yaml delete mode 100644 templates/release/de/meter/fronius-gen24_1.yaml create mode 100644 templates/release/de/meter/fronius-ohmpilot.yaml delete mode 100644 templates/release/de/meter/fronius-ohmpilot_0.yaml create mode 100644 templates/release/de/meter/fronius-primo-gen24-plus.yaml create mode 100644 templates/release/de/meter/fronius-smartmeter-via-inverter.yaml create mode 100644 templates/release/de/meter/fronius-solar-api-v1.yaml delete mode 100644 templates/release/de/meter/fronius-solarapi-v1_0.yaml create mode 100644 templates/release/de/meter/fronius-symo-gen24-plus.yaml create mode 100644 templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml create mode 100644 templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml create mode 100644 templates/release/de/meter/ginlong-solis-inverter.yaml create mode 100644 templates/release/de/meter/go-e-controller.yaml delete mode 100644 templates/release/de/meter/go-e-controller_0.yaml delete mode 100644 templates/release/de/meter/goodwe-dt_0.yaml create mode 100644 templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/goodwe-goodwe-over-wifi.yaml delete mode 100644 templates/release/de/meter/goodwe-hybrid_0.yaml create mode 100644 templates/release/de/meter/goodwe-sdt-dt-inverter.yaml delete mode 100644 templates/release/de/meter/goodwe-wifi_0.yaml create mode 100644 templates/release/de/meter/growatt-hybrid-inverter.yaml delete mode 100644 templates/release/de/meter/growatt-hybrid-tlxh_0.yaml delete mode 100644 templates/release/de/meter/growatt-hybrid_0.yaml create mode 100644 templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/homematic-ip.yaml delete mode 100644 templates/release/de/meter/homematic_0.yaml create mode 100644 templates/release/de/meter/homewizard-kwh-meter.yaml delete mode 100644 templates/release/de/meter/homewizard-kwh_0.yaml create mode 100644 templates/release/de/meter/homewizard-wi-fi-p1-meter.yaml delete mode 100644 templates/release/de/meter/homewizard_0.yaml delete mode 100644 templates/release/de/meter/hoymiles-ahoydtu_0.yaml create mode 100644 templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml create mode 100644 templates/release/de/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml delete mode 100644 templates/release/de/meter/hoymiles-opendtu_0.yaml delete mode 100644 templates/release/de/meter/huawei-dongle_0.yaml create mode 100644 templates/release/de/meter/huawei-emma.yaml delete mode 100644 templates/release/de/meter/huawei-emma_0.yaml create mode 100644 templates/release/de/meter/huawei-smartlogger.yaml delete mode 100644 templates/release/de/meter/huawei-smartlogger_0.yaml create mode 100644 templates/release/de/meter/huawei-sun2000-sdongle.yaml create mode 100644 templates/release/de/meter/huawei-sun2000.yaml delete mode 100644 templates/release/de/meter/huawei-sun2000_0.yaml create mode 100644 templates/release/de/meter/iammeter-wem3080.yaml create mode 100644 templates/release/de/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml delete mode 100644 templates/release/de/meter/iammeter_0.yaml delete mode 100644 templates/release/de/meter/iammeter_1.yaml create mode 100644 templates/release/de/meter/igen-tech-solarman-logger.yaml create mode 100644 templates/release/de/meter/inepro-pro380-mod.yaml delete mode 100644 templates/release/de/meter/inepro_0.yaml create mode 100644 templates/release/de/meter/iometer.yaml delete mode 100644 templates/release/de/meter/iometer_0.yaml create mode 100644 templates/release/de/meter/janitza-b-series.yaml create mode 100644 templates/release/de/meter/janitza-umg-series.yaml delete mode 100644 templates/release/de/meter/janitza_0.yaml create mode 100644 templates/release/de/meter/keba-kecontact-e10.yaml delete mode 100644 templates/release/de/meter/keba-kecontact_0.yaml create mode 100644 templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml create mode 100644 templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml delete mode 100644 templates/release/de/meter/kostal-ksem-inverter_0.yaml delete mode 100644 templates/release/de/meter/kostal-ksem_0.yaml create mode 100644 templates/release/de/meter/kostal-piko-ba.yaml create mode 100644 templates/release/de/meter/kostal-piko-hybrid.yaml delete mode 100644 templates/release/de/meter/kostal-piko-hybrid_0.yaml create mode 100644 templates/release/de/meter/kostal-piko-legacy.yaml delete mode 100644 templates/release/de/meter/kostal-piko-legacy_0.yaml create mode 100644 templates/release/de/meter/kostal-piko-mp-plus.yaml delete mode 100644 templates/release/de/meter/kostal-piko-mp-plus_0.yaml delete mode 100644 templates/release/de/meter/kostal-piko-mp-plus_1.yaml delete mode 100644 templates/release/de/meter/kostal-piko-pv_0.yaml create mode 100644 templates/release/de/meter/kostal-piko.yaml delete mode 100644 templates/release/de/meter/kostal-plenticore-gen2_0.yaml create mode 100644 templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml create mode 100644 templates/release/de/meter/kostal-plenticore-hybrid.yaml delete mode 100644 templates/release/de/meter/kostal-plenticore_0.yaml create mode 100644 templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml create mode 100644 templates/release/de/meter/kostal-smart-energy-meter.yaml create mode 100644 templates/release/de/meter/lg-ess-home-15.yaml delete mode 100644 templates/release/de/meter/lg-ess-home-15_0.yaml create mode 100644 templates/release/de/meter/lg-ess-home-8-10.yaml delete mode 100644 templates/release/de/meter/lg-ess-home-8-10_0.yaml create mode 100644 templates/release/de/meter/loxone-miniserver.yaml delete mode 100644 templates/release/de/meter/loxone_0.yaml create mode 100644 templates/release/de/meter/m-tec-energy-butler-gen2.yaml create mode 100644 templates/release/de/meter/m-tec-energy-butler-gen3.yaml create mode 100644 templates/release/de/meter/marstek-venus-battery-storage.yaml delete mode 100644 templates/release/de/meter/marstek-venus_0.yaml create mode 100644 templates/release/de/meter/mhendriks-p1-dongle.yaml delete mode 100644 templates/release/de/meter/mpm3pm_0.yaml delete mode 100644 templates/release/de/meter/mtec-eb-gen2_0.yaml delete mode 100644 templates/release/de/meter/mtec-eb-gen3_0.yaml create mode 100644 templates/release/de/meter/my-pv-ac-elwa-2.yaml create mode 100644 templates/release/de/meter/my-pv-ac-elwa-e.yaml create mode 100644 templates/release/de/meter/my-pv-ac-thor.yaml create mode 100644 templates/release/de/meter/my-pv-wifi-meter.yaml delete mode 100644 templates/release/de/meter/mypv-wifi-meter_0.yaml create mode 100644 templates/release/de/meter/mystrom-switch.yaml delete mode 100644 templates/release/de/meter/mystrom_0.yaml create mode 100644 templates/release/de/meter/openems.yaml delete mode 100644 templates/release/de/meter/openems_0.yaml delete mode 100644 templates/release/de/meter/openems_1.yaml create mode 100644 templates/release/de/meter/orno-or-we-516.yaml create mode 100644 templates/release/de/meter/orno-or-we-517.yaml delete mode 100644 templates/release/de/meter/orno_0.yaml create mode 100644 templates/release/de/meter/p1monitor-p1-monitor.yaml delete mode 100644 templates/release/de/meter/p1monitor_0.yaml create mode 100644 templates/release/de/meter/plexlog.yaml delete mode 100644 templates/release/de/meter/plexlog_0.yaml create mode 100644 templates/release/de/meter/powerdog.yaml delete mode 100644 templates/release/de/meter/powerdog_0.yaml create mode 100644 templates/release/de/meter/powerfox-poweropti.yaml delete mode 100644 templates/release/de/meter/powerfox-poweropti_0.yaml delete mode 100644 templates/release/de/meter/qcells-hybrid-cloud_0.yaml create mode 100644 templates/release/de/meter/qcells-hybrid-inverter-cloud.yaml create mode 100644 templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml create mode 100644 templates/release/de/meter/rct-power.yaml delete mode 100644 templates/release/de/meter/rct-power_0.yaml create mode 100644 templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml create mode 100644 templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml create mode 100644 templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml delete mode 100644 templates/release/de/meter/saj-h1_0.yaml create mode 100644 templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml delete mode 100644 templates/release/de/meter/saj-h2_0.yaml delete mode 100644 templates/release/de/meter/saj-h2_1.yaml create mode 100644 templates/release/de/meter/saj-r5-series-solar-inverter.yaml delete mode 100644 templates/release/de/meter/saj-r5_0.yaml create mode 100644 templates/release/de/meter/sax-homespeicher.yaml delete mode 100644 templates/release/de/meter/sax_0.yaml delete mode 100644 templates/release/de/meter/sbc-axx3_0.yaml create mode 100644 templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml delete mode 100644 templates/release/de/meter/schneider-iem3000_0.yaml create mode 100644 templates/release/de/meter/senec-home.yaml delete mode 100644 templates/release/de/meter/senec-home_0.yaml create mode 100644 templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml delete mode 100644 templates/release/de/meter/senergy_0.yaml delete mode 100644 templates/release/de/meter/senergy_1.yaml create mode 100644 templates/release/de/meter/shelly-1pm-mini.yaml create mode 100644 templates/release/de/meter/shelly-1pm.yaml delete mode 100644 templates/release/de/meter/shelly-1pm_0.yaml create mode 100644 templates/release/de/meter/shelly-3em.yaml delete mode 100644 templates/release/de/meter/shelly-3em_0.yaml create mode 100644 templates/release/de/meter/shelly-em.yaml create mode 100644 templates/release/de/meter/shelly-plug-s.yaml create mode 100644 templates/release/de/meter/shelly-pm-mini.yaml create mode 100644 templates/release/de/meter/shelly-pro-1pm.yaml create mode 100644 templates/release/de/meter/shelly-pro-3-em.yaml create mode 100644 templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml delete mode 100644 templates/release/de/meter/shelly-pro-3em_0.yaml create mode 100644 templates/release/de/meter/shelly-pro-em.yaml create mode 100644 templates/release/de/meter/siemens-7kt1665.yaml delete mode 100644 templates/release/de/meter/siemens-7kt1665_0.yaml create mode 100644 templates/release/de/meter/siemens-junelight-smart-battery.yaml delete mode 100644 templates/release/de/meter/siemens-junelight_0.yaml create mode 100644 templates/release/de/meter/siemens-pac-2200.yaml delete mode 100644 templates/release/de/meter/siemens-pac2200_0.yaml create mode 100644 templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml delete mode 100644 templates/release/de/meter/sigenergy_0.yaml delete mode 100644 templates/release/de/meter/slimmelezer-V2_0.yaml delete mode 100644 templates/release/de/meter/slimmelezer-luxembourg_0.yaml delete mode 100644 templates/release/de/meter/slimmelezer_0.yaml delete mode 100644 templates/release/de/meter/slimmelezer_1.yaml delete mode 100644 templates/release/de/meter/slimmelezer_2.yaml create mode 100644 templates/release/de/meter/sma-data-manager.yaml delete mode 100644 templates/release/de/meter/sma-data-manager_0.yaml create mode 100644 templates/release/de/meter/sma-energy-meter.yaml delete mode 100644 templates/release/de/meter/sma-energy-meter_0.yaml delete mode 100644 templates/release/de/meter/sma-home-manager_0.yaml delete mode 100644 templates/release/de/meter/sma-hybrid_0.yaml delete mode 100644 templates/release/de/meter/sma-inverter-modbus_0.yaml create mode 100644 templates/release/de/meter/sma-inverter-speedwire.yaml delete mode 100644 templates/release/de/meter/sma-inverter-speedwire_0.yaml delete mode 100644 templates/release/de/meter/sma-sbs-15-25-modbus_0.yaml delete mode 100644 templates/release/de/meter/sma-sbs-modbus_0.yaml delete mode 100644 templates/release/de/meter/sma-si-modbus_0.yaml create mode 100644 templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml create mode 100644 templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml create mode 100644 templates/release/de/meter/sma-sunny-home-manager-2-0.yaml create mode 100644 templates/release/de/meter/sma-sunny-island-modbus.yaml create mode 100644 templates/release/de/meter/sma-webbox.yaml delete mode 100644 templates/release/de/meter/sma-webbox_0.yaml create mode 100644 templates/release/de/meter/sma-wechselrichter-modbus.yaml create mode 100644 templates/release/de/meter/smartfox-box.yaml delete mode 100644 templates/release/de/meter/smartfox-em2_0.yaml create mode 100644 templates/release/de/meter/smartfox-light-em2-firmware.yaml create mode 100644 templates/release/de/meter/smartfox-pro-2.yaml create mode 100644 templates/release/de/meter/smartfox-pro-light-2.yaml create mode 100644 templates/release/de/meter/smartfox-pro-light.yaml create mode 100644 templates/release/de/meter/smartfox-pro.yaml create mode 100644 templates/release/de/meter/smartfox-reg-extended.yaml create mode 100644 templates/release/de/meter/smartfox-reg.yaml delete mode 100644 templates/release/de/meter/smartfox_0.yaml delete mode 100644 templates/release/de/meter/sofarsolar-g3_0.yaml delete mode 100644 templates/release/de/meter/sofarsolar-g3_1.yaml delete mode 100644 templates/release/de/meter/sofarsolar-g3_2.yaml delete mode 100644 templates/release/de/meter/sofarsolar-g3_3.yaml create mode 100644 templates/release/de/meter/sofarsolar-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml create mode 100644 templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml create mode 100644 templates/release/de/meter/sofarsolar-inverter.yaml create mode 100644 templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml create mode 100644 templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml delete mode 100644 templates/release/de/meter/sofarsolar_0.yaml delete mode 100644 templates/release/de/meter/sofarsolar_1.yaml create mode 100644 templates/release/de/meter/solaranzeige-solaranzeige.yaml delete mode 100644 templates/release/de/meter/solaranzeige_0.yaml create mode 100644 templates/release/de/meter/solaredge-hybrid-inverter.yaml delete mode 100644 templates/release/de/meter/solaredge-hybrid_0.yaml create mode 100644 templates/release/de/meter/solaredge-inverter.yaml delete mode 100644 templates/release/de/meter/solaredge-inverter_0.yaml create mode 100644 templates/release/de/meter/solarlog.yaml delete mode 100644 templates/release/de/meter/solarlog_0.yaml delete mode 100644 templates/release/de/meter/solarman_0.yaml create mode 100644 templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml delete mode 100644 templates/release/de/meter/solarmax-maxstorage_0.yaml delete mode 100644 templates/release/de/meter/solarmax-smt_0.yaml create mode 100644 templates/release/de/meter/solarmax-solarmax-smt.yaml create mode 100644 templates/release/de/meter/solarmax-sp-series-inverter.yaml create mode 100644 templates/release/de/meter/solarwatt-energymanager-pro.yaml create mode 100644 templates/release/de/meter/solarwatt-energymanager.yaml delete mode 100644 templates/release/de/meter/solarwatt-flex_0.yaml create mode 100644 templates/release/de/meter/solarwatt-manager-flex.yaml create mode 100644 templates/release/de/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml delete mode 100644 templates/release/de/meter/solarwatt-myreserve-matrix_0.yaml create mode 100644 templates/release/de/meter/solarwatt-myreserve.yaml delete mode 100644 templates/release/de/meter/solarwatt_0.yaml delete mode 100644 templates/release/de/meter/solarwatt_1.yaml delete mode 100644 templates/release/de/meter/solax-hybrid-cloud_0.yaml create mode 100644 templates/release/de/meter/solax-hybrid-inverter-cloud.yaml create mode 100644 templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml create mode 100644 templates/release/de/meter/solax-inverter-cloud.yaml delete mode 100644 templates/release/de/meter/solax-inverter-cloud_0.yaml delete mode 100644 templates/release/de/meter/solax_0.yaml delete mode 100644 templates/release/de/meter/solax_1.yaml create mode 100644 templates/release/de/meter/solinteng.yaml delete mode 100644 templates/release/de/meter/solis-hybrid-s_0.yaml delete mode 100644 templates/release/de/meter/solis-hybrid-s_1.yaml delete mode 100644 templates/release/de/meter/solis-hybrid_0.yaml delete mode 100644 templates/release/de/meter/solis_0.yaml create mode 100644 templates/release/de/meter/sonnen-comfort.yaml create mode 100644 templates/release/de/meter/sonnen-eco-5.yaml create mode 100644 templates/release/de/meter/sonnen-eco-6.yaml create mode 100644 templates/release/de/meter/sonnen-oem-6-5.yaml create mode 100644 templates/release/de/meter/sonnen-sonnenbatterie.yaml delete mode 100644 templates/release/de/meter/sonnenbatterie-eco56_0.yaml delete mode 100644 templates/release/de/meter/sonnenbatterie_0.yaml create mode 100644 templates/release/de/meter/st-ems.yaml create mode 100644 templates/release/de/meter/steca-coolcept-flex.yaml delete mode 100644 templates/release/de/meter/storaxe_0.yaml delete mode 100644 templates/release/de/meter/sungrow-hybrid_0.yaml delete mode 100644 templates/release/de/meter/sungrow-inverter_0.yaml create mode 100644 templates/release/de/meter/sungrow-sg-series-inverter.yaml create mode 100644 templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml delete mode 100644 templates/release/de/meter/sunspec-battery-control_0.yaml create mode 100644 templates/release/de/meter/sunspec-battery-model-124.yaml create mode 100644 templates/release/de/meter/sunspec-battery-model-802.yaml create mode 100644 templates/release/de/meter/sunspec-hybrid-inverter.yaml delete mode 100644 templates/release/de/meter/sunspec-hybrid_0.yaml delete mode 100644 templates/release/de/meter/sunspec-inverter-control_0.yaml create mode 100644 templates/release/de/meter/sunspec-inverter.yaml delete mode 100644 templates/release/de/meter/sunspec-inverter_0.yaml create mode 100644 templates/release/de/meter/sunspec-meter.yaml delete mode 100644 templates/release/de/meter/sunspec-meter_0.yaml delete mode 100644 templates/release/de/meter/sunspec-meter_1.yaml create mode 100644 templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/sunsynk-micro-inverter.yaml create mode 100644 templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/sunsynk-string-inverter.yaml create mode 100644 templates/release/de/meter/sunway.yaml delete mode 100644 templates/release/de/meter/tapo_0.yaml delete mode 100644 templates/release/de/meter/tasmota-3p_0.yaml create mode 100644 templates/release/de/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml delete mode 100644 templates/release/de/meter/tasmota-sml_0.yaml create mode 100644 templates/release/de/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml create mode 100644 templates/release/de/meter/tasmota-three-phase.yaml delete mode 100644 templates/release/de/meter/tasmota_0.yaml create mode 100644 templates/release/de/meter/tesla-powerwall.yaml delete mode 100644 templates/release/de/meter/tesla-powerwall_0.yaml delete mode 100644 templates/release/de/meter/thor_0.yaml create mode 100644 templates/release/de/meter/tibber-pulse.yaml delete mode 100644 templates/release/de/meter/tibber-pulse_0.yaml create mode 100644 templates/release/de/meter/tp-link-h-series-smart-plug.yaml create mode 100644 templates/release/de/meter/tp-link-tapo-p-series-smart-plug.yaml delete mode 100644 templates/release/de/meter/tplink_0.yaml delete mode 100644 templates/release/de/meter/tq-em420_0.yaml delete mode 100644 templates/release/de/meter/tq-em_0.yaml create mode 100644 templates/release/de/meter/tq-energy-manager-em2xx-em3xx.yaml create mode 100644 templates/release/de/meter/tq-energy-manager-em420.yaml create mode 100644 templates/release/de/meter/varta-element.yaml create mode 100644 templates/release/de/meter/varta-pulse-neo.yaml create mode 100644 templates/release/de/meter/varta-pulse.yaml delete mode 100644 templates/release/de/meter/varta_0.yaml create mode 100644 templates/release/de/meter/victron-em24.yaml create mode 100644 templates/release/de/meter/victron-em24_e1.yaml create mode 100644 templates/release/de/meter/victron-em530-em540.yaml create mode 100644 templates/release/de/meter/victron-energy.yaml delete mode 100644 templates/release/de/meter/victron-energy_0.yaml create mode 100644 templates/release/de/meter/victron-et340.yaml delete mode 100644 templates/release/de/meter/volkszaehler-http_0.yaml delete mode 100644 templates/release/de/meter/volkszaehler-importexport_0.yaml delete mode 100644 templates/release/de/meter/volkszaehler-ws_0.yaml create mode 100644 templates/release/de/meter/volkszahler-http-api-import-and-export.yaml create mode 100644 templates/release/de/meter/volkszahler-http-api.yaml create mode 100644 templates/release/de/meter/volkszahler-websocket-api.yaml create mode 100644 templates/release/de/meter/vzlogger.yaml delete mode 100644 templates/release/de/meter/vzlogger_0.yaml create mode 100644 templates/release/de/meter/wago-879-30xx.yaml delete mode 100644 templates/release/de/meter/wago-879-30xx_0.yaml create mode 100644 templates/release/de/meter/wattsonic.yaml delete mode 100644 templates/release/de/meter/wattsonic_0.yaml delete mode 100644 templates/release/de/meter/wattsonic_1.yaml delete mode 100644 templates/release/de/meter/wattsonic_2.yaml delete mode 100644 templates/release/de/meter/wattsonic_3.yaml delete mode 100644 templates/release/de/meter/wattsonic_4.yaml create mode 100644 templates/release/de/meter/weidmuller-em110-rtu-2p.yaml create mode 100644 templates/release/de/meter/weidmuller-em111-rtu-2p.yaml create mode 100644 templates/release/de/meter/weidmuller-em120-rtu-2p.yaml create mode 100644 templates/release/de/meter/weidmuller-em122-rtu-2p.yaml create mode 100644 templates/release/de/meter/youless-energy-monitor.yaml delete mode 100644 templates/release/de/meter/youless_0.yaml create mode 100644 templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml create mode 100644 templates/release/de/meter/zcs-azzurro-inverter.yaml create mode 100644 templates/release/de/meter/zendure-hyper-2000.yaml delete mode 100644 templates/release/de/meter/zendure_0.yaml create mode 100644 templates/release/de/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml create mode 100644 templates/release/de/meter/zuidwijk-slimmelezer-plus-v2.yaml create mode 100644 templates/release/de/meter/zuidwijk-slimmelezer-plus.yaml create mode 100644 templates/release/de/tariff/amber-electric.yaml delete mode 100644 templates/release/de/tariff/amber_0.yaml create mode 100644 templates/release/de/tariff/awattar.yaml delete mode 100644 templates/release/de/tariff/awattar_0.yaml create mode 100644 templates/release/de/tariff/electricity-maps-commercial-api.yaml create mode 100644 templates/release/de/tariff/electricity-maps-free-api.yaml delete mode 100644 templates/release/de/tariff/electricitymaps-free_0.yaml delete mode 100644 templates/release/de/tariff/electricitymaps_0.yaml create mode 100644 templates/release/de/tariff/energinet.yaml delete mode 100644 templates/release/de/tariff/energinet_0.yaml delete mode 100644 templates/release/de/tariff/energy-charts-api_0.yaml create mode 100644 templates/release/de/tariff/enever.yaml delete mode 100644 templates/release/de/tariff/enever_0.yaml create mode 100644 templates/release/de/tariff/entso-e.yaml delete mode 100644 templates/release/de/tariff/entsoe_0.yaml create mode 100644 templates/release/de/tariff/forecast-solar.yaml delete mode 100644 templates/release/de/tariff/forecast-solar_0.yaml create mode 100644 templates/release/de/tariff/fraunhofer-ise.yaml create mode 100644 templates/release/de/tariff/green-grid-compass.yaml delete mode 100644 templates/release/de/tariff/green-grid-compass_0.yaml create mode 100644 templates/release/de/tariff/groupe-e-vario-plus.yaml delete mode 100644 templates/release/de/tariff/groupe-e_0.yaml create mode 100644 templates/release/de/tariff/grunstromindex.yaml delete mode 100644 "templates/release/de/tariff/gr\303\274nstromindex_0.yaml" create mode 100644 templates/release/de/tariff/national-grid-eso.yaml delete mode 100644 templates/release/de/tariff/ngeso_0.yaml create mode 100644 templates/release/de/tariff/nordpool-spot-prices.yaml delete mode 100644 templates/release/de/tariff/nordpool_0.yaml delete mode 100644 templates/release/de/tariff/octopus-api_0.yaml create mode 100644 templates/release/de/tariff/octopus-energy-api.yaml create mode 100644 templates/release/de/tariff/octopus-energy-product-code.yaml delete mode 100644 templates/release/de/tariff/octopus-productcode_0.yaml create mode 100644 templates/release/de/tariff/open-meteo.yaml delete mode 100644 templates/release/de/tariff/open-meteo_0.yaml create mode 100644 templates/release/de/tariff/ostrom.yaml delete mode 100644 templates/release/de/tariff/ostrom_0.yaml create mode 100644 templates/release/de/tariff/pun-orario.yaml delete mode 100644 templates/release/de/tariff/pun_0.yaml create mode 100644 templates/release/de/tariff/smartenergy-smartcontrol.yaml delete mode 100644 templates/release/de/tariff/smartenergy_0.yaml create mode 100644 templates/release/de/tariff/solcast.yaml delete mode 100644 templates/release/de/tariff/solcast_0.yaml create mode 100644 templates/release/de/tariff/spotty-energie.yaml delete mode 100644 templates/release/de/tariff/spottyenergy_0.yaml create mode 100644 templates/release/de/tariff/tibber.yaml delete mode 100644 templates/release/de/tariff/tibber_0.yaml create mode 100644 templates/release/de/tariff/victron-vrm-solar-forecast.yaml delete mode 100644 templates/release/de/tariff/victron_0.yaml create mode 100644 templates/release/de/vehicle/aiways.yaml delete mode 100644 templates/release/de/vehicle/aiways_0.yaml create mode 100644 templates/release/de/vehicle/audi.yaml delete mode 100644 templates/release/de/vehicle/audi_0.yaml create mode 100644 templates/release/de/vehicle/bmw.yaml delete mode 100644 templates/release/de/vehicle/bmw_0.yaml delete mode 100644 templates/release/de/vehicle/carwings_0.yaml create mode 100644 templates/release/de/vehicle/citroen.yaml delete mode 100644 templates/release/de/vehicle/citroen_0.yaml delete mode 100644 templates/release/de/vehicle/cupra_0.yaml create mode 100644 templates/release/de/vehicle/dacia.yaml delete mode 100644 templates/release/de/vehicle/dacia_0.yaml create mode 100644 templates/release/de/vehicle/ds.yaml delete mode 100644 templates/release/de/vehicle/ds_0.yaml delete mode 100644 templates/release/de/vehicle/enyaq_0.yaml create mode 100644 templates/release/de/vehicle/evnotify.yaml delete mode 100644 templates/release/de/vehicle/evnotify_0.yaml create mode 100644 templates/release/de/vehicle/fiat.yaml delete mode 100644 templates/release/de/vehicle/fiat_0.yaml delete mode 100644 templates/release/de/vehicle/fiat_1.yaml delete mode 100644 templates/release/de/vehicle/flobz_0.yaml delete mode 100644 templates/release/de/vehicle/ford-connect_0.yaml create mode 100644 templates/release/de/vehicle/ford.yaml create mode 100644 templates/release/de/vehicle/generic-vehicle-without-api.yaml create mode 100644 templates/release/de/vehicle/hyundai-bluelink.yaml delete mode 100644 templates/release/de/vehicle/hyundai_0.yaml delete mode 100644 templates/release/de/vehicle/ioBroker.bmw_0.yaml create mode 100644 templates/release/de/vehicle/iobroker-bmw.yaml create mode 100644 templates/release/de/vehicle/iso15118.yaml delete mode 100644 templates/release/de/vehicle/iso15118_0.yaml create mode 100644 templates/release/de/vehicle/jeep.yaml create mode 100644 templates/release/de/vehicle/kia-bluelink.yaml delete mode 100644 templates/release/de/vehicle/kia_0.yaml create mode 100644 templates/release/de/vehicle/mercedes-benz.yaml delete mode 100644 templates/release/de/vehicle/mercedes_0.yaml create mode 100644 templates/release/de/vehicle/mg.yaml create mode 100644 templates/release/de/vehicle/mg2mqtt.yaml delete mode 100644 templates/release/de/vehicle/mg2mqtt_0.yaml delete mode 100644 templates/release/de/vehicle/mg_0.yaml create mode 100644 templates/release/de/vehicle/mini.yaml delete mode 100644 templates/release/de/vehicle/mini_0.yaml create mode 100644 templates/release/de/vehicle/mz2mqtt.yaml delete mode 100644 templates/release/de/vehicle/mz2mqtt_0.yaml create mode 100644 templates/release/de/vehicle/nissan-ariya.yaml delete mode 100644 templates/release/de/vehicle/nissan-ariya_0.yaml create mode 100644 templates/release/de/vehicle/nissan-leaf-pre-2019.yaml create mode 100644 templates/release/de/vehicle/nissan-leaf.yaml delete mode 100644 templates/release/de/vehicle/nissan_0.yaml create mode 100644 templates/release/de/vehicle/niu-e-scooter.yaml delete mode 100644 templates/release/de/vehicle/niu-e-scooter_0.yaml delete mode 100644 templates/release/de/vehicle/offline_0.yaml create mode 100644 templates/release/de/vehicle/opel.yaml delete mode 100644 templates/release/de/vehicle/opel_0.yaml create mode 100644 templates/release/de/vehicle/open-vehicle-monitoring-system.yaml delete mode 100644 templates/release/de/vehicle/ovms_0.yaml create mode 100644 templates/release/de/vehicle/peugeot.yaml delete mode 100644 templates/release/de/vehicle/peugeot_0.yaml create mode 100644 templates/release/de/vehicle/polestar.yaml delete mode 100644 templates/release/de/vehicle/polestar_0.yaml create mode 100644 templates/release/de/vehicle/psa-car-controller.yaml create mode 100644 templates/release/de/vehicle/renault.yaml delete mode 100644 templates/release/de/vehicle/renault_0.yaml create mode 100644 templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml create mode 100644 templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml delete mode 100644 templates/release/de/vehicle/seat_0.yaml create mode 100644 templates/release/de/vehicle/skoda-enyaq.yaml create mode 100644 templates/release/de/vehicle/smart-1.yaml create mode 100644 templates/release/de/vehicle/smart-eq.yaml delete mode 100644 templates/release/de/vehicle/smart-hello_0.yaml delete mode 100644 templates/release/de/vehicle/smart_0.yaml create mode 100644 templates/release/de/vehicle/tesla-ble.yaml delete mode 100644 templates/release/de/vehicle/tesla-ble_0.yaml create mode 100644 templates/release/de/vehicle/tesla.yaml delete mode 100644 templates/release/de/vehicle/tesla_0.yaml create mode 100644 templates/release/de/vehicle/teslalogger.yaml delete mode 100644 templates/release/de/vehicle/teslalogger_0.yaml create mode 100644 templates/release/de/vehicle/teslamate.yaml delete mode 100644 templates/release/de/vehicle/teslamate_0.yaml create mode 100644 templates/release/de/vehicle/tessie.yaml delete mode 100644 templates/release/de/vehicle/tessie_0.yaml create mode 100644 templates/release/de/vehicle/toyota.yaml delete mode 100644 templates/release/de/vehicle/toyota_0.yaml create mode 100644 templates/release/de/vehicle/tronity.yaml delete mode 100644 templates/release/de/vehicle/tronity_0.yaml create mode 100644 templates/release/de/vehicle/volkswagen-we-connect-id.yaml delete mode 100644 templates/release/de/vehicle/volvo-connected_0.yaml create mode 100644 templates/release/de/vehicle/volvo.yaml create mode 100644 templates/release/de/vehicle/volvo2mqtt.yaml delete mode 100644 templates/release/de/vehicle/volvo2mqtt_0.yaml delete mode 100644 templates/release/de/vehicle/vw_0.yaml create mode 100644 templates/release/de/vehicle/zero-motorcycles.yaml delete mode 100644 templates/release/de/vehicle/zero_0.yaml delete mode 100644 templates/release/en/charger/Kathrein_0.yaml delete mode 100644 templates/release/en/charger/Kathrein_1.yaml delete mode 100644 templates/release/en/charger/Kathrein_2.yaml delete mode 100644 templates/release/en/charger/Kathrein_3.yaml delete mode 100644 templates/release/en/charger/Kathrein_4.yaml delete mode 100644 templates/release/en/charger/Kathrein_5.yaml create mode 100644 templates/release/en/charger/abb-terra-ac-ocpp.yaml create mode 100644 templates/release/en/charger/abb-terra-ac.yaml delete mode 100644 templates/release/en/charger/abb_0.yaml create mode 100644 templates/release/en/charger/abl-em4-single-ocpp.yaml create mode 100644 templates/release/en/charger/abl-em4-single-sbcx.yaml create mode 100644 templates/release/en/charger/abl-em4-twin-ocpp.yaml create mode 100644 templates/release/en/charger/abl-em4-twin-sbcx.yaml delete mode 100644 templates/release/en/charger/abl-em4_0.yaml create mode 100644 templates/release/en/charger/abl-emh1.yaml create mode 100644 templates/release/en/charger/abl-emh2-ocpp.yaml create mode 100644 templates/release/en/charger/abl-emh2.yaml create mode 100644 templates/release/en/charger/abl-emh3-ocpp.yaml delete mode 100644 templates/release/en/charger/abl_0.yaml delete mode 100644 templates/release/en/charger/abl_1.yaml delete mode 100644 templates/release/en/charger/abl_2.yaml delete mode 100644 templates/release/en/charger/ac-elwa-2_0.yaml delete mode 100644 templates/release/en/charger/ac-thor_0.yaml delete mode 100644 templates/release/en/charger/ac-thor_1.yaml create mode 100644 templates/release/en/charger/alfen-eve-ocpp.yaml create mode 100644 templates/release/en/charger/alfen-eve.yaml delete mode 100644 templates/release/en/charger/alfen_0.yaml create mode 100644 templates/release/en/charger/alpha-innotec.yaml create mode 100644 templates/release/en/charger/alphatec-ladesaule-twin.yaml create mode 100644 templates/release/en/charger/alphatec-wallbox-mini.yaml create mode 100644 templates/release/en/charger/alphatec-wallbox-power.yaml delete mode 100644 templates/release/en/charger/alphatec_0.yaml delete mode 100644 templates/release/en/charger/alphatec_1.yaml delete mode 100644 templates/release/en/charger/alphatec_2.yaml delete mode 100644 templates/release/en/charger/alphatec_3.yaml delete mode 100644 templates/release/en/charger/amperfied-solar_0.yaml create mode 100644 templates/release/en/charger/amperfied-wallbox-connect-business.yaml create mode 100644 templates/release/en/charger/amperfied-wallbox-connect-home.yaml create mode 100644 templates/release/en/charger/amperfied-wallbox-connect-solar.yaml create mode 100644 templates/release/en/charger/amperfied-wallbox-energy-control.yaml delete mode 100644 templates/release/en/charger/amperfied_0.yaml delete mode 100644 templates/release/en/charger/amperfied_1.yaml create mode 100644 templates/release/en/charger/ampure-next.yaml create mode 100644 templates/release/en/charger/ampure-unite.yaml create mode 100644 templates/release/en/charger/audi-wallbox-plus.yaml create mode 100644 templates/release/en/charger/audi-wallbox-pro.yaml create mode 100644 templates/release/en/charger/autel-ac-compact.yaml create mode 100644 templates/release/en/charger/autel-ac-maxicharger.yaml create mode 100644 templates/release/en/charger/autoaid-business-wallbox.yaml create mode 100644 templates/release/en/charger/autoaid-intelligent-wallbox.yaml create mode 100644 templates/release/en/charger/avm-fritzdect.yaml create mode 100644 templates/release/en/charger/bender-cc612.yaml create mode 100644 templates/release/en/charger/bender-cc613.yaml delete mode 100644 templates/release/en/charger/bender-cc_0.yaml delete mode 100644 templates/release/en/charger/bender-cc_1.yaml delete mode 100644 templates/release/en/charger/bender-cc_10.yaml delete mode 100644 templates/release/en/charger/bender-cc_11.yaml delete mode 100644 templates/release/en/charger/bender-cc_12.yaml delete mode 100644 templates/release/en/charger/bender-cc_13.yaml delete mode 100644 templates/release/en/charger/bender-cc_14.yaml delete mode 100644 templates/release/en/charger/bender-cc_15.yaml delete mode 100644 templates/release/en/charger/bender-cc_2.yaml delete mode 100644 templates/release/en/charger/bender-cc_3.yaml delete mode 100644 templates/release/en/charger/bender-cc_4.yaml delete mode 100644 templates/release/en/charger/bender-cc_5.yaml delete mode 100644 templates/release/en/charger/bender-cc_6.yaml delete mode 100644 templates/release/en/charger/bender-cc_7.yaml delete mode 100644 templates/release/en/charger/bender-cc_8.yaml delete mode 100644 templates/release/en/charger/bender-cc_9.yaml create mode 100644 templates/release/en/charger/bender-icc1314.yaml create mode 100644 templates/release/en/charger/bender-icc1324.yaml delete mode 100644 templates/release/en/charger/bender-icc_0.yaml delete mode 100644 templates/release/en/charger/bender-icc_1.yaml delete mode 100644 templates/release/en/charger/bender-icc_2.yaml delete mode 100644 templates/release/en/charger/bender-icc_3.yaml create mode 100644 templates/release/en/charger/bmw-i-wallbox.yaml create mode 100644 templates/release/en/charger/bosch-sg-ready.yaml create mode 100644 templates/release/en/charger/bosch-x-change.yaml create mode 100644 templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml create mode 100644 templates/release/en/charger/buderus-logamatic-hmc-20.yaml create mode 100644 templates/release/en/charger/buderus-sg-ready.yaml create mode 100644 templates/release/en/charger/cfos-power-brain-solar.yaml create mode 100644 templates/release/en/charger/cfos-power-brain.yaml delete mode 100644 templates/release/en/charger/cfos_0.yaml delete mode 100644 templates/release/en/charger/cfos_1.yaml create mode 100644 templates/release/en/charger/charge-amps-halo.yaml create mode 100644 templates/release/en/charger/compleo-ebox.yaml create mode 100644 templates/release/en/charger/cta-all-in-one-aeroplus.yaml create mode 100644 templates/release/en/charger/cubos-c11e.yaml create mode 100644 templates/release/en/charger/cubos-c22e.yaml create mode 100644 templates/release/en/charger/cupra-charger-connect-2.yaml create mode 100644 templates/release/en/charger/cupra-charger-connect.yaml create mode 100644 templates/release/en/charger/cupra-charger-pro-2.yaml create mode 100644 templates/release/en/charger/cupra-charger-pro-eichrecht-2.yaml create mode 100644 templates/release/en/charger/cupra-charger-pro.yaml create mode 100644 templates/release/en/charger/dadapower-premium-wallbox.yaml delete mode 100644 templates/release/en/charger/dadapower_0.yaml delete mode 100644 templates/release/en/charger/daheimladen-mb_0.yaml create mode 100644 templates/release/en/charger/daheimladen-wallbox.yaml create mode 100644 templates/release/en/charger/daikin-homehub-sg-ready.yaml delete mode 100644 templates/release/en/charger/daikin-homehub_0.yaml create mode 100644 templates/release/en/charger/delta-ac-max-basic.yaml create mode 100644 templates/release/en/charger/delta-ac-max-smart.yaml create mode 100644 templates/release/en/charger/delta-slim-charger.yaml create mode 100644 templates/release/en/charger/delta-ultra-fast-charger.yaml delete mode 100644 templates/release/en/charger/delta_0.yaml delete mode 100644 templates/release/en/charger/delta_1.yaml delete mode 100644 templates/release/en/charger/delta_2.yaml delete mode 100644 templates/release/en/charger/delta_3.yaml create mode 100644 templates/release/en/charger/demo-charger.yaml delete mode 100644 templates/release/en/charger/demo-charger_0.yaml create mode 100644 templates/release/en/charger/e-on-drive-ebox.yaml create mode 100644 templates/release/en/charger/e-on-drive-vbox.yaml create mode 100644 templates/release/en/charger/e3-dc-easy-connect.yaml create mode 100644 templates/release/en/charger/easee-charge-core.yaml create mode 100644 templates/release/en/charger/easee-charge-lite.yaml create mode 100644 templates/release/en/charger/easee-charge.yaml create mode 100644 templates/release/en/charger/easee-home.yaml delete mode 100644 templates/release/en/charger/easee_0.yaml delete mode 100644 templates/release/en/charger/easee_1.yaml delete mode 100644 templates/release/en/charger/easee_2.yaml delete mode 100644 templates/release/en/charger/easee_3.yaml create mode 100644 templates/release/en/charger/ebee-wallbox.yaml create mode 100644 templates/release/en/charger/echarge-cph1.yaml create mode 100644 templates/release/en/charger/echarge-cph2.yaml create mode 100644 templates/release/en/charger/echarge-cpm2.yaml create mode 100644 templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml create mode 100644 templates/release/en/charger/edgetech-smart-evse.yaml create mode 100644 templates/release/en/charger/eebus-compatible.yaml delete mode 100644 templates/release/en/charger/eebus_0.yaml create mode 100644 templates/release/en/charger/elco.yaml create mode 100644 templates/release/en/charger/elecq-biz.yaml create mode 100644 templates/release/en/charger/elecq-home.yaml create mode 100644 templates/release/en/charger/elecq-station.yaml create mode 100644 templates/release/en/charger/eledio-go.yaml delete mode 100644 templates/release/en/charger/elli-2_0.yaml delete mode 100644 templates/release/en/charger/elli-2_1.yaml delete mode 100644 templates/release/en/charger/elli-2_10.yaml delete mode 100644 templates/release/en/charger/elli-2_11.yaml delete mode 100644 templates/release/en/charger/elli-2_2.yaml delete mode 100644 templates/release/en/charger/elli-2_3.yaml delete mode 100644 templates/release/en/charger/elli-2_4.yaml delete mode 100644 templates/release/en/charger/elli-2_5.yaml delete mode 100644 templates/release/en/charger/elli-2_6.yaml delete mode 100644 templates/release/en/charger/elli-2_7.yaml delete mode 100644 templates/release/en/charger/elli-2_8.yaml delete mode 100644 templates/release/en/charger/elli-2_9.yaml create mode 100644 templates/release/en/charger/elli-charger-connect-2.yaml create mode 100644 templates/release/en/charger/elli-charger-connect.yaml create mode 100644 templates/release/en/charger/elli-charger-pro-2.yaml create mode 100644 templates/release/en/charger/elli-charger-pro-eichrecht-2.yaml create mode 100644 templates/release/en/charger/elli-charger-pro.yaml delete mode 100644 templates/release/en/charger/elliconnect_0.yaml delete mode 100644 templates/release/en/charger/elliconnect_1.yaml delete mode 100644 templates/release/en/charger/elliconnect_2.yaml delete mode 100644 templates/release/en/charger/elliconnect_3.yaml delete mode 100644 templates/release/en/charger/elliconnect_4.yaml delete mode 100644 templates/release/en/charger/ellipro_0.yaml delete mode 100644 templates/release/en/charger/ellipro_1.yaml delete mode 100644 templates/release/en/charger/ellipro_2.yaml delete mode 100644 templates/release/en/charger/ellipro_3.yaml delete mode 100644 templates/release/en/charger/ellipro_4.yaml create mode 100644 templates/release/en/charger/em2go-home.yaml delete mode 100644 templates/release/en/charger/em2go-home_0.yaml create mode 100644 templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml delete mode 100644 templates/release/en/charger/em2go_0.yaml delete mode 100644 templates/release/en/charger/emsesp_0.yaml delete mode 100644 templates/release/en/charger/emsesp_1.yaml delete mode 100644 templates/release/en/charger/emsesp_2.yaml create mode 100644 templates/release/en/charger/enercab-smart.yaml create mode 100644 templates/release/en/charger/enplus-ac-ev-charger.yaml create mode 100644 templates/release/en/charger/ensto-chago-wallbox.yaml create mode 100644 templates/release/en/charger/entratek-power-dot-fix.yaml create mode 100644 templates/release/en/charger/entratek-power-dot-pro-2.yaml delete mode 100644 templates/release/en/charger/eprowallbox_0.yaml create mode 100644 templates/release/en/charger/esl-walli-light.yaml create mode 100644 templates/release/en/charger/esystems-ghostone.yaml delete mode 100644 templates/release/en/charger/etrel-duo_0.yaml create mode 100644 templates/release/en/charger/etrel-inch-duo.yaml create mode 100644 templates/release/en/charger/etrel-inch.yaml delete mode 100644 templates/release/en/charger/etrel_0.yaml delete mode 100644 templates/release/en/charger/etrel_1.yaml create mode 100644 templates/release/en/charger/evbox-elvi.yaml create mode 100644 templates/release/en/charger/evbox-livo.yaml create mode 100644 templates/release/en/charger/evse-din.yaml delete mode 100644 templates/release/en/charger/evse-din_0.yaml delete mode 100644 templates/release/en/charger/evse-din_1.yaml create mode 100644 templates/release/en/charger/evse-wifi.yaml delete mode 100644 templates/release/en/charger/evsewifi_0.yaml create mode 100644 templates/release/en/charger/free2move-eprowallbox-move.yaml create mode 100644 templates/release/en/charger/free2move-eprowallbox.yaml create mode 100644 templates/release/en/charger/free2move-esolutions-eprowallbox.yaml delete mode 100644 templates/release/en/charger/fritzdect_0.yaml create mode 100644 templates/release/en/charger/fronius-wattpilot-ocpp.yaml create mode 100644 templates/release/en/charger/garo-glb.yaml create mode 100644 templates/release/en/charger/garo-glbplus.yaml create mode 100644 templates/release/en/charger/garo-ls4-compact.yaml create mode 100644 templates/release/en/charger/garo-ls4.yaml delete mode 100644 templates/release/en/charger/ghost_0.yaml delete mode 100644 templates/release/en/charger/ghost_1.yaml create mode 100644 templates/release/en/charger/go-e-charger-gemini-ocpp.yaml create mode 100644 templates/release/en/charger/go-e-charger-gemini.yaml create mode 100644 templates/release/en/charger/go-e-charger-homefix.yaml create mode 100644 templates/release/en/charger/go-e-charger-homeplus.yaml create mode 100644 templates/release/en/charger/go-e-charger-pro-ocpp.yaml create mode 100644 templates/release/en/charger/go-e-charger-pro.yaml create mode 100644 templates/release/en/charger/go-e-charger-v3-ocpp.yaml create mode 100644 templates/release/en/charger/go-e-charger-v3.yaml delete mode 100644 templates/release/en/charger/go-e-v3_0.yaml delete mode 100644 templates/release/en/charger/go-e-v3_1.yaml delete mode 100644 templates/release/en/charger/go-e-v3_2.yaml delete mode 100644 templates/release/en/charger/go-e_0.yaml delete mode 100644 templates/release/en/charger/go-e_1.yaml create mode 100644 templates/release/en/charger/hardy-barth-cph1.yaml create mode 100644 templates/release/en/charger/hardy-barth-cph2.yaml create mode 100644 templates/release/en/charger/hardy-barth-cpm2.yaml delete mode 100644 templates/release/en/charger/hardybarth-ecb1_0.yaml delete mode 100644 templates/release/en/charger/hardybarth-ecb1_1.yaml delete mode 100644 templates/release/en/charger/hardybarth-salia_0.yaml delete mode 100644 templates/release/en/charger/hardybarth-salia_1.yaml delete mode 100644 templates/release/en/charger/hardybarth-salia_2.yaml delete mode 100644 templates/release/en/charger/hardybarth-salia_3.yaml create mode 100644 templates/release/en/charger/heidelberg-energy-control.yaml delete mode 100644 templates/release/en/charger/heidelberg_0.yaml delete mode 100644 templates/release/en/charger/heidelberg_1.yaml delete mode 100644 templates/release/en/charger/heidelberg_2.yaml delete mode 100644 templates/release/en/charger/heidelberg_3.yaml create mode 100644 templates/release/en/charger/hesotec-ebox.yaml create mode 100644 templates/release/en/charger/hesotec-esat.yaml delete mode 100644 templates/release/en/charger/hesotec_0.yaml delete mode 100644 templates/release/en/charger/hesotec_1.yaml create mode 100644 templates/release/en/charger/home-assistant-switch.yaml delete mode 100644 templates/release/en/charger/homeassistant-switch_0.yaml create mode 100644 templates/release/en/charger/homecharge-homecharger.yaml create mode 100644 templates/release/en/charger/homematic-ip.yaml delete mode 100644 templates/release/en/charger/homematic_0.yaml create mode 100644 templates/release/en/charger/homewizard.yaml delete mode 100644 templates/release/en/charger/homewizard_0.yaml create mode 100644 templates/release/en/charger/huawei-scharger-22kt-s0.yaml create mode 100644 templates/release/en/charger/huawei-scharger-7ks-s0.yaml delete mode 100644 templates/release/en/charger/ichargecion_0.yaml delete mode 100644 templates/release/en/charger/ichargecion_1.yaml create mode 100644 templates/release/en/charger/idm.yaml delete mode 100644 templates/release/en/charger/idm_0.yaml create mode 100644 templates/release/en/charger/innogy-ebox.yaml delete mode 100644 templates/release/en/charger/innogy-ebox_0.yaml delete mode 100644 templates/release/en/charger/innogy-ebox_1.yaml delete mode 100644 templates/release/en/charger/innogy-ebox_2.yaml create mode 100644 templates/release/en/charger/inro-pantabox.yaml create mode 100644 templates/release/en/charger/juice-charger-me.yaml create mode 100644 templates/release/en/charger/junkers-sg-ready.yaml create mode 100644 templates/release/en/charger/kathrein-kwb-ac20.yaml create mode 100644 templates/release/en/charger/kathrein-kwb-ac35.yaml create mode 100644 templates/release/en/charger/kathrein-kwb-ac40-e.yaml create mode 100644 templates/release/en/charger/kathrein-kwb-ac40.yaml create mode 100644 templates/release/en/charger/kathrein-kwb-ac60-e.yaml create mode 100644 templates/release/en/charger/kathrein-kwb-ac60.yaml create mode 100644 templates/release/en/charger/keba-kecontact-p20.yaml create mode 100644 templates/release/en/charger/keba-kecontact-p30-c-series.yaml create mode 100644 templates/release/en/charger/keba-kecontact-p30-x-series.yaml create mode 100644 templates/release/en/charger/keba-kecontact-p40-pro.yaml create mode 100644 templates/release/en/charger/keba-kecontact-p40.yaml delete mode 100644 templates/release/en/charger/keba-modbus_0.yaml delete mode 100644 templates/release/en/charger/keba-modbus_1.yaml delete mode 100644 templates/release/en/charger/keba-modbus_2.yaml delete mode 100644 templates/release/en/charger/keba-modbus_3.yaml delete mode 100644 templates/release/en/charger/keba-modbus_4.yaml delete mode 100644 templates/release/en/charger/keba-modbus_5.yaml delete mode 100644 templates/release/en/charger/keba-modbus_6.yaml create mode 100644 templates/release/en/charger/kermi-x-center-pro.yaml delete mode 100644 templates/release/en/charger/kermi_0.yaml delete mode 100644 templates/release/en/charger/kermi_1.yaml create mode 100644 templates/release/en/charger/kontron-solar-charger.yaml create mode 100644 templates/release/en/charger/kostal-enector.yaml create mode 100644 templates/release/en/charger/kse-wbx16.yaml delete mode 100644 templates/release/en/charger/kse_0.yaml create mode 100644 templates/release/en/charger/ladefoxx-evload.yaml create mode 100644 templates/release/en/charger/ladefoxx-mikro-2-0.yaml create mode 100644 templates/release/en/charger/lambda-eu-l-series.yaml delete mode 100644 templates/release/en/charger/lambda-zewotherm_0.yaml delete mode 100644 templates/release/en/charger/lambda-zewotherm_1.yaml delete mode 100644 templates/release/en/charger/livo_0.yaml create mode 100644 templates/release/en/charger/lrt-home-essentialplus.yaml delete mode 100644 templates/release/en/charger/luxtronik_0.yaml delete mode 100644 templates/release/en/charger/luxtronik_1.yaml delete mode 100644 templates/release/en/charger/luxtronik_10.yaml delete mode 100644 templates/release/en/charger/luxtronik_2.yaml delete mode 100644 templates/release/en/charger/luxtronik_3.yaml delete mode 100644 templates/release/en/charger/luxtronik_4.yaml delete mode 100644 templates/release/en/charger/luxtronik_5.yaml delete mode 100644 templates/release/en/charger/luxtronik_6.yaml delete mode 100644 templates/release/en/charger/luxtronik_7.yaml delete mode 100644 templates/release/en/charger/luxtronik_8.yaml delete mode 100644 templates/release/en/charger/luxtronik_9.yaml create mode 100644 templates/release/en/charger/mennekes-amedio-professional.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-4business-700.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-4you-300.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-4you-500.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-chargecontrol.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-premium.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-professional.yaml create mode 100644 templates/release/en/charger/mennekes-amtron-xtra.yaml delete mode 100644 templates/release/en/charger/mennekes-compact_0.yaml delete mode 100644 templates/release/en/charger/mennekes-compact_1.yaml delete mode 100644 templates/release/en/charger/mennekes-compact_2.yaml create mode 100644 templates/release/en/charger/mennekes-emobility-gateway-acu.yaml delete mode 100644 templates/release/en/charger/mennekes-hcc3_0.yaml delete mode 100644 templates/release/en/charger/mennekes-hcc3_1.yaml create mode 100644 templates/release/en/charger/mennekes-smart-acu.yaml create mode 100644 templates/release/en/charger/mennekes-smart-t-acu.yaml create mode 100644 templates/release/en/charger/my-pv-ac-elwa-2.yaml create mode 100644 templates/release/en/charger/my-pv-ac-thor-9s.yaml create mode 100644 templates/release/en/charger/my-pv-ac-thor.yaml create mode 100644 templates/release/en/charger/mystrom-switch.yaml delete mode 100644 templates/release/en/charger/mystrom_0.yaml create mode 100644 templates/release/en/charger/nibe-ap-aw10.yaml create mode 100644 templates/release/en/charger/novelan-wpr-net.yaml delete mode 100644 templates/release/en/charger/nrggen2_0.yaml create mode 100644 templates/release/en/charger/nrgkick-connect.yaml delete mode 100644 templates/release/en/charger/nrgkick-connect_0.yaml create mode 100644 templates/release/en/charger/nrgkick-gen2.yaml create mode 100644 templates/release/en/charger/obo-bettermann-ion.yaml delete mode 100644 templates/release/en/charger/obo_0.yaml delete mode 100644 templates/release/en/charger/obo_1.yaml delete mode 100644 templates/release/en/charger/obo_2.yaml create mode 100644 templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml delete mode 100644 templates/release/en/charger/ocpp-abb-tac_0.yaml delete mode 100644 templates/release/en/charger/ocpp-abl_0.yaml delete mode 100644 templates/release/en/charger/ocpp-abl_1.yaml delete mode 100644 templates/release/en/charger/ocpp-abl_2.yaml delete mode 100644 templates/release/en/charger/ocpp-alfen_0.yaml delete mode 100644 templates/release/en/charger/ocpp-autel_0.yaml delete mode 100644 templates/release/en/charger/ocpp-autel_1.yaml delete mode 100644 templates/release/en/charger/ocpp-autoaid_0.yaml delete mode 100644 templates/release/en/charger/ocpp-autoaid_1.yaml delete mode 100644 templates/release/en/charger/ocpp-beny_0.yaml delete mode 100644 templates/release/en/charger/ocpp-chargeamps_0.yaml delete mode 100644 templates/release/en/charger/ocpp-elecq_0.yaml delete mode 100644 templates/release/en/charger/ocpp-elecq_1.yaml delete mode 100644 templates/release/en/charger/ocpp-elecq_2.yaml delete mode 100644 templates/release/en/charger/ocpp-enercab_0.yaml delete mode 100644 templates/release/en/charger/ocpp-enercab_1.yaml delete mode 100644 templates/release/en/charger/ocpp-enplus_0.yaml delete mode 100644 templates/release/en/charger/ocpp-entratek_0.yaml delete mode 100644 templates/release/en/charger/ocpp-entratek_1.yaml delete mode 100644 templates/release/en/charger/ocpp-esolutions_0.yaml delete mode 100644 templates/release/en/charger/ocpp-evbox-elvi_0.yaml delete mode 100644 templates/release/en/charger/ocpp-goe_0.yaml delete mode 100644 templates/release/en/charger/ocpp-goe_1.yaml delete mode 100644 templates/release/en/charger/ocpp-goe_2.yaml delete mode 100644 templates/release/en/charger/ocpp-goe_3.yaml delete mode 100644 templates/release/en/charger/ocpp-homecharge_0.yaml delete mode 100644 templates/release/en/charger/ocpp-huawei_0.yaml delete mode 100644 templates/release/en/charger/ocpp-huawei_1.yaml delete mode 100644 templates/release/en/charger/ocpp-mennekes-acu_0.yaml delete mode 100644 templates/release/en/charger/ocpp-mennekes-acu_1.yaml delete mode 100644 templates/release/en/charger/ocpp-mennekes-acu_2.yaml delete mode 100644 templates/release/en/charger/ocpp-orbis_0.yaml delete mode 100644 templates/release/en/charger/ocpp-sungrow_0.yaml delete mode 100644 templates/release/en/charger/ocpp-wallbox_0.yaml delete mode 100644 templates/release/en/charger/ocpp-wallbox_1.yaml delete mode 100644 templates/release/en/charger/ocpp-wallbox_2.yaml delete mode 100644 templates/release/en/charger/ocpp-wallbox_3.yaml delete mode 100644 templates/release/en/charger/ocpp-zaptec_0.yaml delete mode 100644 templates/release/en/charger/ocpp_0.yaml create mode 100644 templates/release/en/charger/openevse.yaml delete mode 100644 templates/release/en/charger/openevse_0.yaml delete mode 100644 templates/release/en/charger/openwb-2.0_0.yaml create mode 100644 templates/release/en/charger/openwb-pro.yaml delete mode 100644 templates/release/en/charger/openwb-pro_0.yaml create mode 100644 templates/release/en/charger/openwb-series2.yaml create mode 100644 templates/release/en/charger/openwb-software-2-x.yaml delete mode 100644 templates/release/en/charger/openwb_0.yaml create mode 100644 templates/release/en/charger/optec-mobility-one.yaml create mode 100644 templates/release/en/charger/orbis-viaris.yaml delete mode 100644 templates/release/en/charger/pantabox_0.yaml create mode 100644 templates/release/en/charger/pc-electric-garo.yaml delete mode 100644 templates/release/en/charger/pcelectric-garo_0.yaml create mode 100644 templates/release/en/charger/peblar-business.yaml create mode 100644 templates/release/en/charger/peblar-home-plus.yaml create mode 100644 templates/release/en/charger/peblar-home.yaml delete mode 100644 templates/release/en/charger/peblar_0.yaml delete mode 100644 templates/release/en/charger/peblar_1.yaml delete mode 100644 templates/release/en/charger/peblar_2.yaml delete mode 100644 templates/release/en/charger/phoenix-charx_0.yaml delete mode 100644 templates/release/en/charger/phoenix-charx_1.yaml delete mode 100644 templates/release/en/charger/phoenix-charx_2.yaml create mode 100644 templates/release/en/charger/phoenix-contact-charx.yaml create mode 100644 templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml create mode 100644 templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml create mode 100644 templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml create mode 100644 templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml create mode 100644 templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml create mode 100644 templates/release/en/charger/phoenix-contact-ev-ser.yaml delete mode 100644 templates/release/en/charger/phoenix-em-eth_0.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_0.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_1.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_2.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_3.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_4.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_5.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_6.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_7.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-eth_8.yaml delete mode 100644 templates/release/en/charger/phoenix-ev-ser_0.yaml create mode 100644 templates/release/en/charger/plugchoice.yaml delete mode 100644 templates/release/en/charger/plugchoice_0.yaml delete mode 100644 templates/release/en/charger/pmcc_0.yaml delete mode 100644 templates/release/en/charger/pmcp_0.yaml create mode 100644 templates/release/en/charger/porsche-mobile-charger-connect.yaml create mode 100644 templates/release/en/charger/porsche-mobile-charger-plus.yaml create mode 100644 templates/release/en/charger/porsche-wallbox.yaml delete mode 100644 templates/release/en/charger/porsche-wallbox_0.yaml create mode 100644 templates/release/en/charger/pracht-alpha-xt.yaml delete mode 100644 templates/release/en/charger/pracht-alpha_0.yaml delete mode 100644 templates/release/en/charger/pracht-alpha_1.yaml delete mode 100644 templates/release/en/charger/pracht-alpha_2.yaml delete mode 100644 templates/release/en/charger/pracht-alpha_3.yaml create mode 100644 templates/release/en/charger/pracht-mono-xt.yaml create mode 100644 templates/release/en/charger/pracht-pni.yaml create mode 100644 templates/release/en/charger/pracht-xtplus.yaml create mode 100644 templates/release/en/charger/pulsares-simplebox.yaml delete mode 100644 templates/release/en/charger/pulsares_0.yaml create mode 100644 templates/release/en/charger/pulsatrix.yaml delete mode 100644 templates/release/en/charger/pulsatrix_0.yaml create mode 100644 templates/release/en/charger/qcells-q-home-edrive-a.yaml create mode 100644 templates/release/en/charger/roth-thermoaura.yaml create mode 100644 templates/release/en/charger/roth-thermoterra.yaml create mode 100644 templates/release/en/charger/schneider-evlink-pro.yaml delete mode 100644 templates/release/en/charger/schneider-evlink-v3_0.yaml create mode 100644 templates/release/en/charger/schrack-i-charge-cion.yaml create mode 100644 templates/release/en/charger/senec-wallbox-pro-s.yaml create mode 100644 templates/release/en/charger/senec-wallbox-pro.yaml create mode 100644 templates/release/en/charger/shelly-1.yaml create mode 100644 templates/release/en/charger/shelly-plug-s.yaml create mode 100644 templates/release/en/charger/shelly-plus-1.yaml create mode 100644 templates/release/en/charger/shelly-pro-1.yaml delete mode 100644 templates/release/en/charger/shelly_0.yaml create mode 100644 templates/release/en/charger/siemens-versicharge-gen3.yaml create mode 100644 templates/release/en/charger/skoda-charger-connect.yaml create mode 100644 templates/release/en/charger/skoda-charger-pro-eichrecht.yaml create mode 100644 templates/release/en/charger/skoda-charger-pro.yaml create mode 100644 templates/release/en/charger/skoda-iv-charger-connect.yaml create mode 100644 templates/release/en/charger/skoda-iv-charger-connectplus.yaml create mode 100644 templates/release/en/charger/sma-echarger.yaml create mode 100644 templates/release/en/charger/sma-ev-charger.yaml delete mode 100644 templates/release/en/charger/smaevcharger_0.yaml delete mode 100644 templates/release/en/charger/smaevcharger_1.yaml delete mode 100644 templates/release/en/charger/smartevse_0.yaml create mode 100644 templates/release/en/charger/smartfox-pro-charger.yaml create mode 100644 templates/release/en/charger/smartwb.yaml delete mode 100644 templates/release/en/charger/smartwb_0.yaml create mode 100644 templates/release/en/charger/solaredge-home-ev-charger.yaml create mode 100644 templates/release/en/charger/solax-x3-evc.yaml delete mode 100644 templates/release/en/charger/solax_0.yaml delete mode 100644 templates/release/en/charger/solax_1.yaml delete mode 100644 templates/release/en/charger/solax_2.yaml create mode 100644 templates/release/en/charger/sonnen-sonnencharger.yaml create mode 100644 templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml create mode 100644 templates/release/en/charger/stark-in-strom-easy.yaml create mode 100644 templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml create mode 100644 templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml delete mode 100644 templates/release/en/charger/stiebel-lwa_0.yaml delete mode 100644 templates/release/en/charger/stiebel-lwa_1.yaml delete mode 100644 templates/release/en/charger/stiebel-wpm_0.yaml create mode 100644 templates/release/en/charger/sungrow-ac011e-01.yaml create mode 100644 templates/release/en/charger/sungrow-ac011e.yaml create mode 100644 templates/release/en/charger/sungrow-ac22e-01.yaml delete mode 100644 templates/release/en/charger/sungrow_0.yaml delete mode 100644 templates/release/en/charger/sungrow_1.yaml delete mode 100644 templates/release/en/charger/tapo_0.yaml create mode 100644 templates/release/en/charger/tasmota-single-phase.yaml delete mode 100644 templates/release/en/charger/tasmota_0.yaml create mode 100644 templates/release/en/charger/tecalor-thz-sg-ready.yaml create mode 100644 templates/release/en/charger/technisat-technivolt.yaml create mode 100644 templates/release/en/charger/tesla-wall-connector-gen-3.yaml create mode 100644 templates/release/en/charger/tessie.yaml delete mode 100644 templates/release/en/charger/tessie_0.yaml create mode 100644 templates/release/en/charger/tigo-go-ev-charger.yaml create mode 100644 templates/release/en/charger/tinkerforge-warp-charger-pro.yaml create mode 100644 templates/release/en/charger/tinkerforge-warp-charger-smart.yaml create mode 100644 templates/release/en/charger/tinkerforge-warp3-charger-pro.yaml create mode 100644 templates/release/en/charger/tinkerforge-warp3-charger-smart.yaml delete mode 100644 templates/release/en/charger/tinkerforge-warp3-smart_0.yaml delete mode 100644 templates/release/en/charger/tinkerforge-warp3_0.yaml delete mode 100644 templates/release/en/charger/tinkerforge-warp_0.yaml delete mode 100644 templates/release/en/charger/tinkerforge-warp_1.yaml create mode 100644 templates/release/en/charger/tp-link-h-series-smart-plug.yaml create mode 100644 templates/release/en/charger/tp-link-tapo-p-series-smart-plug.yaml delete mode 100644 templates/release/en/charger/tplink_0.yaml delete mode 100644 templates/release/en/charger/trydan_0.yaml delete mode 100644 templates/release/en/charger/twc3_0.yaml create mode 100644 templates/release/en/charger/ubitricity-heinz.yaml create mode 100644 templates/release/en/charger/v2c-trydan.yaml create mode 100644 templates/release/en/charger/vaillant-sensonet-sg-ready.yaml delete mode 100644 templates/release/en/charger/vaillant_0.yaml delete mode 100644 templates/release/en/charger/versicharge_0.yaml create mode 100644 templates/release/en/charger/vestel-connect-plus.yaml create mode 100644 templates/release/en/charger/vestel-evc04-home-smart.yaml delete mode 100644 templates/release/en/charger/vestel_0.yaml delete mode 100644 templates/release/en/charger/vestel_1.yaml delete mode 100644 templates/release/en/charger/vestel_2.yaml delete mode 100644 templates/release/en/charger/vestel_3.yaml delete mode 100644 templates/release/en/charger/vestel_4.yaml create mode 100644 templates/release/en/charger/victron-ev-charging-station-via-gx.yaml create mode 100644 templates/release/en/charger/victron-ev-charging-station.yaml delete mode 100644 templates/release/en/charger/victron-evcs_0.yaml delete mode 100644 templates/release/en/charger/victron_0.yaml create mode 100644 templates/release/en/charger/viessmann-heatpump-sg-ready.yaml delete mode 100644 templates/release/en/charger/viessmann_0.yaml create mode 100644 templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml create mode 100644 templates/release/en/charger/volkswagen-charger-connect-2.yaml create mode 100644 templates/release/en/charger/volkswagen-charger-pro-2.yaml create mode 100644 templates/release/en/charger/volkswagen-charger-pro-eichrecht-2.yaml create mode 100644 templates/release/en/charger/volkswagen-id-charger-connect.yaml create mode 100644 templates/release/en/charger/volkswagen-id-charger-pro.yaml create mode 100644 templates/release/en/charger/volt-time-one.yaml create mode 100644 templates/release/en/charger/volt-time-source-2.yaml create mode 100644 templates/release/en/charger/volt-time-source-2s.yaml create mode 100644 templates/release/en/charger/volt-time-source.yaml delete mode 100644 templates/release/en/charger/volttime_0.yaml delete mode 100644 templates/release/en/charger/volttime_1.yaml delete mode 100644 templates/release/en/charger/volttime_2.yaml delete mode 100644 templates/release/en/charger/volttime_3.yaml create mode 100644 templates/release/en/charger/wallbe-eco-2-0-s.yaml create mode 100644 templates/release/en/charger/wallbe-eco.yaml create mode 100644 templates/release/en/charger/wallbe-pro.yaml create mode 100644 templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml create mode 100644 templates/release/en/charger/wallbox-commander-2.yaml create mode 100644 templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml create mode 100644 templates/release/en/charger/wallbox-copper-sb.yaml delete mode 100644 templates/release/en/charger/wallbox-fw5_0.yaml delete mode 100644 templates/release/en/charger/wallbox-fw5_1.yaml delete mode 100644 templates/release/en/charger/wallbox-fw5_2.yaml delete mode 100644 templates/release/en/charger/wallbox-fw5_3.yaml create mode 100644 templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml create mode 100644 templates/release/en/charger/wallbox-pulsar-max.yaml create mode 100644 templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml create mode 100644 templates/release/en/charger/wallbox-pulsar-plus.yaml create mode 100644 templates/release/en/charger/walther-werke-basic-evo-pro.yaml create mode 100644 templates/release/en/charger/webasto-live.yaml create mode 100644 templates/release/en/charger/webasto-next.yaml delete mode 100644 templates/release/en/charger/webasto-next_0.yaml delete mode 100644 templates/release/en/charger/webasto-next_1.yaml create mode 100644 templates/release/en/charger/webasto-unite.yaml create mode 100644 templates/release/en/charger/weidmuller-ac-smart.yaml delete mode 100644 "templates/release/en/charger/weidm\303\274ller_0.yaml" create mode 100644 templates/release/en/charger/wolf-bwl.yaml create mode 100644 templates/release/en/charger/wolf-bws.yaml create mode 100644 templates/release/en/charger/zaptec-go-2.yaml create mode 100644 templates/release/en/charger/zaptec-go-ocpp.yaml create mode 100644 templates/release/en/charger/zaptec-go.yaml create mode 100644 templates/release/en/charger/zaptec-pro.yaml delete mode 100644 templates/release/en/charger/zaptec_0.yaml delete mode 100644 templates/release/en/charger/zaptec_1.yaml delete mode 100644 templates/release/en/charger/zaptec_2.yaml create mode 100644 templates/release/en/charger/zewotherm-eu-l-series.yaml create mode 100644 templates/release/en/charger/zj-beny-bcp-ev-charger.yaml create mode 100644 templates/release/en/meter/a-tronix.yaml create mode 100644 templates/release/en/meter/abb-a43.yaml create mode 100644 templates/release/en/meter/abb-a44.yaml delete mode 100644 templates/release/en/meter/abb-ab_0.yaml create mode 100644 templates/release/en/meter/abb-b23.yaml create mode 100644 templates/release/en/meter/abb-b24.yaml delete mode 100644 templates/release/en/meter/ac-elwa-2_0.yaml delete mode 100644 templates/release/en/meter/ac-elwa-e_0.yaml create mode 100644 templates/release/en/meter/acrel-adw300.yaml delete mode 100644 templates/release/en/meter/acrel-adw300_0.yaml create mode 100644 templates/release/en/meter/ads-tec-storaxe.yaml delete mode 100644 templates/release/en/meter/alpha-ess-smile_0.yaml create mode 100644 templates/release/en/meter/alpha-ess-storion-smile.yaml create mode 100644 templates/release/en/meter/ampere-ampere-storagepro.yaml create mode 100644 templates/release/en/meter/anker-micro-inverter.yaml create mode 100644 templates/release/en/meter/apsystems-ez1.yaml delete mode 100644 templates/release/en/meter/apsystems-ez1_0.yaml create mode 100644 templates/release/en/meter/avm-fritzdect.yaml create mode 100644 templates/release/en/meter/axitec-axihycon-12-15h.yaml create mode 100644 templates/release/en/meter/bernecker-engineering-mpm3pm.yaml delete mode 100644 templates/release/en/meter/bge_tech_ds100_0.yaml delete mode 100644 templates/release/en/meter/bge_tech_ws100_0.yaml create mode 100644 templates/release/en/meter/bgetech-ds100.yaml create mode 100644 templates/release/en/meter/bgetech-ws100.yaml create mode 100644 templates/release/en/meter/bosch-bpt-s-5-hybrid.yaml delete mode 100644 templates/release/en/meter/bosch-bpt_0.yaml create mode 100644 templates/release/en/meter/bosswerk-micro-inverter.yaml create mode 100644 templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml create mode 100644 templates/release/en/meter/carlo-gavazzi-em24.yaml create mode 100644 templates/release/en/meter/carlo-gavazzi-em24_e1.yaml create mode 100644 templates/release/en/meter/carlo-gavazzi-em330-em340.yaml create mode 100644 templates/release/en/meter/carlo-gavazzi-em530-em540.yaml create mode 100644 templates/release/en/meter/carlo-gavazzi-et112.yaml create mode 100644 templates/release/en/meter/carlo-gavazzi-et330-et340.yaml create mode 100644 templates/release/en/meter/cfos-powerbrain-meter.yaml delete mode 100644 templates/release/en/meter/cfos_0.yaml delete mode 100644 templates/release/en/meter/cg-em24_0.yaml delete mode 100644 templates/release/en/meter/cg-em24_1.yaml delete mode 100644 templates/release/en/meter/cg-em24_e1_0.yaml delete mode 100644 templates/release/en/meter/cg-em24_e1_1.yaml delete mode 100644 templates/release/en/meter/cg-emt1xx_0.yaml delete mode 100644 templates/release/en/meter/cg-emt1xx_1.yaml delete mode 100644 templates/release/en/meter/cg-emt3xx_0.yaml delete mode 100644 templates/release/en/meter/cg-emt3xx_1.yaml delete mode 100644 templates/release/en/meter/cg-emt3xx_2.yaml delete mode 100644 templates/release/en/meter/cg-emt3xx_3.yaml delete mode 100644 templates/release/en/meter/cg-emt3xx_4.yaml delete mode 100644 templates/release/en/meter/cg-emt3xx_5.yaml create mode 100644 templates/release/en/meter/demo-battery.yaml delete mode 100644 templates/release/en/meter/demo-battery_0.yaml create mode 100644 templates/release/en/meter/demo-meter.yaml delete mode 100644 templates/release/en/meter/demo-meter_0.yaml create mode 100644 templates/release/en/meter/deye-3p-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/deye-hp3-hybrid-inverter.yaml delete mode 100644 templates/release/en/meter/deye-hybrid-3p_0.yaml delete mode 100644 templates/release/en/meter/deye-hybrid-3p_1.yaml delete mode 100644 templates/release/en/meter/deye-hybrid-hp3_0.yaml delete mode 100644 templates/release/en/meter/deye-hybrid-hp3_1.yaml delete mode 100644 templates/release/en/meter/deye-mi_0.yaml delete mode 100644 templates/release/en/meter/deye-mi_1.yaml delete mode 100644 templates/release/en/meter/deye-mi_2.yaml delete mode 100644 templates/release/en/meter/deye-mi_3.yaml create mode 100644 templates/release/en/meter/deye-micro-inverter.yaml create mode 100644 templates/release/en/meter/deye-storage-hybrid-inverter.yaml delete mode 100644 templates/release/en/meter/deye-storage_0.yaml delete mode 100644 templates/release/en/meter/deye-storage_1.yaml create mode 100644 templates/release/en/meter/deye-string-inverter.yaml delete mode 100644 templates/release/en/meter/deye-string_0.yaml delete mode 100644 templates/release/en/meter/deye-string_1.yaml create mode 100644 templates/release/en/meter/discovergy.yaml delete mode 100644 templates/release/en/meter/discovergy_0.yaml create mode 100644 templates/release/en/meter/dsmr.yaml delete mode 100644 templates/release/en/meter/dsmr_0.yaml create mode 100644 templates/release/en/meter/dzg-dvh4013.yaml delete mode 100644 templates/release/en/meter/dzg_0.yaml create mode 100644 templates/release/en/meter/e3-dc.yaml delete mode 100644 templates/release/en/meter/e3dc-rscp_0.yaml create mode 100644 templates/release/en/meter/eastron-sdm120-modbus.yaml delete mode 100644 templates/release/en/meter/eastron-sdm120_0.yaml create mode 100644 templates/release/en/meter/eastron-sdm220-230.yaml delete mode 100644 templates/release/en/meter/eastron-sdm220_230_0.yaml delete mode 100644 templates/release/en/meter/eastron-sdm220_230_1.yaml delete mode 100644 templates/release/en/meter/eastron-sdm220_230_2.yaml create mode 100644 templates/release/en/meter/eastron-sdm630-modbus.yaml delete mode 100644 templates/release/en/meter/eastron-sdm72_0.yaml create mode 100644 templates/release/en/meter/eastron-sdm72d-m.yaml create mode 100644 templates/release/en/meter/eastron-sdm72dm-v2.yaml delete mode 100644 templates/release/en/meter/eastron_0.yaml delete mode 100644 templates/release/en/meter/eastron_1.yaml delete mode 100644 templates/release/en/meter/eastron_2.yaml delete mode 100644 templates/release/en/meter/eastron_3.yaml delete mode 100644 templates/release/en/meter/eastron_4.yaml create mode 100644 templates/release/en/meter/enphase-iq-envoy.yaml delete mode 100644 templates/release/en/meter/enphase_0.yaml delete mode 100644 templates/release/en/meter/esphome-dlms-austria_0.yaml create mode 100644 templates/release/en/meter/esphome-dlms-meter-austria.yaml create mode 100644 templates/release/en/meter/esphome-dsmr.yaml create mode 100644 templates/release/en/meter/fenecon.yaml delete mode 100644 templates/release/en/meter/fox-ess-h1_0.yaml delete mode 100644 templates/release/en/meter/fox-ess-h3-smart_0.yaml delete mode 100644 templates/release/en/meter/fox-ess-h3_0.yaml create mode 100644 templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml delete mode 100644 templates/release/en/meter/fritzdect_0.yaml delete mode 100644 templates/release/en/meter/fronius-gen24_0.yaml delete mode 100644 templates/release/en/meter/fronius-gen24_1.yaml create mode 100644 templates/release/en/meter/fronius-ohmpilot.yaml delete mode 100644 templates/release/en/meter/fronius-ohmpilot_0.yaml create mode 100644 templates/release/en/meter/fronius-primo-gen24-plus.yaml create mode 100644 templates/release/en/meter/fronius-smartmeter-via-inverter.yaml create mode 100644 templates/release/en/meter/fronius-solar-api-v1.yaml delete mode 100644 templates/release/en/meter/fronius-solarapi-v1_0.yaml create mode 100644 templates/release/en/meter/fronius-symo-gen24-plus.yaml create mode 100644 templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml create mode 100644 templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml create mode 100644 templates/release/en/meter/ginlong-solis-inverter.yaml create mode 100644 templates/release/en/meter/go-e-controller.yaml delete mode 100644 templates/release/en/meter/go-e-controller_0.yaml delete mode 100644 templates/release/en/meter/goodwe-dt_0.yaml create mode 100644 templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/goodwe-goodwe-over-wifi.yaml delete mode 100644 templates/release/en/meter/goodwe-hybrid_0.yaml create mode 100644 templates/release/en/meter/goodwe-sdt-dt-inverter.yaml delete mode 100644 templates/release/en/meter/goodwe-wifi_0.yaml create mode 100644 templates/release/en/meter/growatt-hybrid-inverter.yaml delete mode 100644 templates/release/en/meter/growatt-hybrid-tlxh_0.yaml delete mode 100644 templates/release/en/meter/growatt-hybrid_0.yaml create mode 100644 templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/homematic-ip.yaml delete mode 100644 templates/release/en/meter/homematic_0.yaml create mode 100644 templates/release/en/meter/homewizard-kwh-meter.yaml delete mode 100644 templates/release/en/meter/homewizard-kwh_0.yaml create mode 100644 templates/release/en/meter/homewizard-wi-fi-p1-meter.yaml delete mode 100644 templates/release/en/meter/homewizard_0.yaml delete mode 100644 templates/release/en/meter/hoymiles-ahoydtu_0.yaml create mode 100644 templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml create mode 100644 templates/release/en/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml delete mode 100644 templates/release/en/meter/hoymiles-opendtu_0.yaml delete mode 100644 templates/release/en/meter/huawei-dongle_0.yaml create mode 100644 templates/release/en/meter/huawei-emma.yaml delete mode 100644 templates/release/en/meter/huawei-emma_0.yaml create mode 100644 templates/release/en/meter/huawei-smartlogger.yaml delete mode 100644 templates/release/en/meter/huawei-smartlogger_0.yaml create mode 100644 templates/release/en/meter/huawei-sun2000-sdongle.yaml create mode 100644 templates/release/en/meter/huawei-sun2000.yaml delete mode 100644 templates/release/en/meter/huawei-sun2000_0.yaml create mode 100644 templates/release/en/meter/iammeter-wem3080.yaml create mode 100644 templates/release/en/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml delete mode 100644 templates/release/en/meter/iammeter_0.yaml delete mode 100644 templates/release/en/meter/iammeter_1.yaml create mode 100644 templates/release/en/meter/igen-tech-solarman-logger.yaml create mode 100644 templates/release/en/meter/inepro-pro380-mod.yaml delete mode 100644 templates/release/en/meter/inepro_0.yaml create mode 100644 templates/release/en/meter/iometer.yaml delete mode 100644 templates/release/en/meter/iometer_0.yaml create mode 100644 templates/release/en/meter/janitza-b-series.yaml create mode 100644 templates/release/en/meter/janitza-umg-series.yaml delete mode 100644 templates/release/en/meter/janitza_0.yaml create mode 100644 templates/release/en/meter/keba-kecontact-e10.yaml delete mode 100644 templates/release/en/meter/keba-kecontact_0.yaml create mode 100644 templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml create mode 100644 templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml delete mode 100644 templates/release/en/meter/kostal-ksem-inverter_0.yaml delete mode 100644 templates/release/en/meter/kostal-ksem_0.yaml create mode 100644 templates/release/en/meter/kostal-piko-ba.yaml create mode 100644 templates/release/en/meter/kostal-piko-hybrid.yaml delete mode 100644 templates/release/en/meter/kostal-piko-hybrid_0.yaml create mode 100644 templates/release/en/meter/kostal-piko-legacy.yaml delete mode 100644 templates/release/en/meter/kostal-piko-legacy_0.yaml create mode 100644 templates/release/en/meter/kostal-piko-mp-plus.yaml delete mode 100644 templates/release/en/meter/kostal-piko-mp-plus_0.yaml delete mode 100644 templates/release/en/meter/kostal-piko-mp-plus_1.yaml delete mode 100644 templates/release/en/meter/kostal-piko-pv_0.yaml create mode 100644 templates/release/en/meter/kostal-piko.yaml delete mode 100644 templates/release/en/meter/kostal-plenticore-gen2_0.yaml create mode 100644 templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml create mode 100644 templates/release/en/meter/kostal-plenticore-hybrid.yaml delete mode 100644 templates/release/en/meter/kostal-plenticore_0.yaml create mode 100644 templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml create mode 100644 templates/release/en/meter/kostal-smart-energy-meter.yaml create mode 100644 templates/release/en/meter/lg-ess-home-15.yaml delete mode 100644 templates/release/en/meter/lg-ess-home-15_0.yaml create mode 100644 templates/release/en/meter/lg-ess-home-8-10.yaml delete mode 100644 templates/release/en/meter/lg-ess-home-8-10_0.yaml create mode 100644 templates/release/en/meter/loxone-miniserver.yaml delete mode 100644 templates/release/en/meter/loxone_0.yaml create mode 100644 templates/release/en/meter/m-tec-energy-butler-gen2.yaml create mode 100644 templates/release/en/meter/m-tec-energy-butler-gen3.yaml create mode 100644 templates/release/en/meter/marstek-venus-battery-storage.yaml delete mode 100644 templates/release/en/meter/marstek-venus_0.yaml create mode 100644 templates/release/en/meter/mhendriks-p1-dongle.yaml delete mode 100644 templates/release/en/meter/mpm3pm_0.yaml delete mode 100644 templates/release/en/meter/mtec-eb-gen2_0.yaml delete mode 100644 templates/release/en/meter/mtec-eb-gen3_0.yaml create mode 100644 templates/release/en/meter/my-pv-ac-elwa-2.yaml create mode 100644 templates/release/en/meter/my-pv-ac-elwa-e.yaml create mode 100644 templates/release/en/meter/my-pv-ac-thor.yaml create mode 100644 templates/release/en/meter/my-pv-wifi-meter.yaml delete mode 100644 templates/release/en/meter/mypv-wifi-meter_0.yaml create mode 100644 templates/release/en/meter/mystrom-switch.yaml delete mode 100644 templates/release/en/meter/mystrom_0.yaml create mode 100644 templates/release/en/meter/openems.yaml delete mode 100644 templates/release/en/meter/openems_0.yaml delete mode 100644 templates/release/en/meter/openems_1.yaml create mode 100644 templates/release/en/meter/orno-or-we-516.yaml create mode 100644 templates/release/en/meter/orno-or-we-517.yaml delete mode 100644 templates/release/en/meter/orno_0.yaml create mode 100644 templates/release/en/meter/p1monitor-p1-monitor.yaml delete mode 100644 templates/release/en/meter/p1monitor_0.yaml create mode 100644 templates/release/en/meter/plexlog.yaml delete mode 100644 templates/release/en/meter/plexlog_0.yaml create mode 100644 templates/release/en/meter/powerdog.yaml delete mode 100644 templates/release/en/meter/powerdog_0.yaml create mode 100644 templates/release/en/meter/powerfox-poweropti.yaml delete mode 100644 templates/release/en/meter/powerfox-poweropti_0.yaml delete mode 100644 templates/release/en/meter/qcells-hybrid-cloud_0.yaml create mode 100644 templates/release/en/meter/qcells-hybrid-inverter-cloud.yaml create mode 100644 templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml create mode 100644 templates/release/en/meter/rct-power.yaml delete mode 100644 templates/release/en/meter/rct-power_0.yaml create mode 100644 templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml create mode 100644 templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml create mode 100644 templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml delete mode 100644 templates/release/en/meter/saj-h1_0.yaml create mode 100644 templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml delete mode 100644 templates/release/en/meter/saj-h2_0.yaml delete mode 100644 templates/release/en/meter/saj-h2_1.yaml create mode 100644 templates/release/en/meter/saj-r5-series-solar-inverter.yaml delete mode 100644 templates/release/en/meter/saj-r5_0.yaml create mode 100644 templates/release/en/meter/sax-homespeicher.yaml delete mode 100644 templates/release/en/meter/sax_0.yaml delete mode 100644 templates/release/en/meter/sbc-axx3_0.yaml create mode 100644 templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml delete mode 100644 templates/release/en/meter/schneider-iem3000_0.yaml create mode 100644 templates/release/en/meter/senec-home.yaml delete mode 100644 templates/release/en/meter/senec-home_0.yaml create mode 100644 templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml delete mode 100644 templates/release/en/meter/senergy_0.yaml delete mode 100644 templates/release/en/meter/senergy_1.yaml create mode 100644 templates/release/en/meter/shelly-1pm-mini.yaml create mode 100644 templates/release/en/meter/shelly-1pm.yaml delete mode 100644 templates/release/en/meter/shelly-1pm_0.yaml create mode 100644 templates/release/en/meter/shelly-3em.yaml delete mode 100644 templates/release/en/meter/shelly-3em_0.yaml create mode 100644 templates/release/en/meter/shelly-em.yaml create mode 100644 templates/release/en/meter/shelly-plug-s.yaml create mode 100644 templates/release/en/meter/shelly-pm-mini.yaml create mode 100644 templates/release/en/meter/shelly-pro-1pm.yaml create mode 100644 templates/release/en/meter/shelly-pro-3-em.yaml create mode 100644 templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml delete mode 100644 templates/release/en/meter/shelly-pro-3em_0.yaml create mode 100644 templates/release/en/meter/shelly-pro-em.yaml create mode 100644 templates/release/en/meter/siemens-7kt1665.yaml delete mode 100644 templates/release/en/meter/siemens-7kt1665_0.yaml create mode 100644 templates/release/en/meter/siemens-junelight-smart-battery.yaml delete mode 100644 templates/release/en/meter/siemens-junelight_0.yaml create mode 100644 templates/release/en/meter/siemens-pac-2200.yaml delete mode 100644 templates/release/en/meter/siemens-pac2200_0.yaml create mode 100644 templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml delete mode 100644 templates/release/en/meter/sigenergy_0.yaml delete mode 100644 templates/release/en/meter/slimmelezer-V2_0.yaml delete mode 100644 templates/release/en/meter/slimmelezer-luxembourg_0.yaml delete mode 100644 templates/release/en/meter/slimmelezer_0.yaml delete mode 100644 templates/release/en/meter/slimmelezer_1.yaml delete mode 100644 templates/release/en/meter/slimmelezer_2.yaml create mode 100644 templates/release/en/meter/sma-data-manager.yaml delete mode 100644 templates/release/en/meter/sma-data-manager_0.yaml create mode 100644 templates/release/en/meter/sma-energy-meter.yaml delete mode 100644 templates/release/en/meter/sma-energy-meter_0.yaml delete mode 100644 templates/release/en/meter/sma-home-manager_0.yaml delete mode 100644 templates/release/en/meter/sma-hybrid_0.yaml delete mode 100644 templates/release/en/meter/sma-inverter-modbus_0.yaml create mode 100644 templates/release/en/meter/sma-inverter-speedwire.yaml delete mode 100644 templates/release/en/meter/sma-inverter-speedwire_0.yaml delete mode 100644 templates/release/en/meter/sma-sbs-15-25-modbus_0.yaml delete mode 100644 templates/release/en/meter/sma-sbs-modbus_0.yaml delete mode 100644 templates/release/en/meter/sma-si-modbus_0.yaml create mode 100644 templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml create mode 100644 templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml create mode 100644 templates/release/en/meter/sma-sunny-home-manager-2-0.yaml create mode 100644 templates/release/en/meter/sma-sunny-island-modbus.yaml create mode 100644 templates/release/en/meter/sma-webbox.yaml delete mode 100644 templates/release/en/meter/sma-webbox_0.yaml create mode 100644 templates/release/en/meter/sma-wechselrichter-modbus.yaml create mode 100644 templates/release/en/meter/smartfox-box.yaml delete mode 100644 templates/release/en/meter/smartfox-em2_0.yaml create mode 100644 templates/release/en/meter/smartfox-light-em2-firmware.yaml create mode 100644 templates/release/en/meter/smartfox-pro-2.yaml create mode 100644 templates/release/en/meter/smartfox-pro-light-2.yaml create mode 100644 templates/release/en/meter/smartfox-pro-light.yaml create mode 100644 templates/release/en/meter/smartfox-pro.yaml create mode 100644 templates/release/en/meter/smartfox-reg-extended.yaml create mode 100644 templates/release/en/meter/smartfox-reg.yaml delete mode 100644 templates/release/en/meter/smartfox_0.yaml delete mode 100644 templates/release/en/meter/sofarsolar-g3_0.yaml delete mode 100644 templates/release/en/meter/sofarsolar-g3_1.yaml delete mode 100644 templates/release/en/meter/sofarsolar-g3_2.yaml delete mode 100644 templates/release/en/meter/sofarsolar-g3_3.yaml create mode 100644 templates/release/en/meter/sofarsolar-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml create mode 100644 templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml create mode 100644 templates/release/en/meter/sofarsolar-inverter.yaml create mode 100644 templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml create mode 100644 templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml delete mode 100644 templates/release/en/meter/sofarsolar_0.yaml delete mode 100644 templates/release/en/meter/sofarsolar_1.yaml create mode 100644 templates/release/en/meter/solaranzeige-solaranzeige.yaml delete mode 100644 templates/release/en/meter/solaranzeige_0.yaml create mode 100644 templates/release/en/meter/solaredge-hybrid-inverter.yaml delete mode 100644 templates/release/en/meter/solaredge-hybrid_0.yaml create mode 100644 templates/release/en/meter/solaredge-inverter.yaml delete mode 100644 templates/release/en/meter/solaredge-inverter_0.yaml create mode 100644 templates/release/en/meter/solarlog.yaml delete mode 100644 templates/release/en/meter/solarlog_0.yaml delete mode 100644 templates/release/en/meter/solarman_0.yaml create mode 100644 templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml delete mode 100644 templates/release/en/meter/solarmax-maxstorage_0.yaml delete mode 100644 templates/release/en/meter/solarmax-smt_0.yaml create mode 100644 templates/release/en/meter/solarmax-solarmax-smt.yaml create mode 100644 templates/release/en/meter/solarmax-sp-series-inverter.yaml create mode 100644 templates/release/en/meter/solarwatt-energymanager-pro.yaml create mode 100644 templates/release/en/meter/solarwatt-energymanager.yaml delete mode 100644 templates/release/en/meter/solarwatt-flex_0.yaml create mode 100644 templates/release/en/meter/solarwatt-manager-flex.yaml create mode 100644 templates/release/en/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml delete mode 100644 templates/release/en/meter/solarwatt-myreserve-matrix_0.yaml create mode 100644 templates/release/en/meter/solarwatt-myreserve.yaml delete mode 100644 templates/release/en/meter/solarwatt_0.yaml delete mode 100644 templates/release/en/meter/solarwatt_1.yaml delete mode 100644 templates/release/en/meter/solax-hybrid-cloud_0.yaml create mode 100644 templates/release/en/meter/solax-hybrid-inverter-cloud.yaml create mode 100644 templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml create mode 100644 templates/release/en/meter/solax-inverter-cloud.yaml delete mode 100644 templates/release/en/meter/solax-inverter-cloud_0.yaml delete mode 100644 templates/release/en/meter/solax_0.yaml delete mode 100644 templates/release/en/meter/solax_1.yaml create mode 100644 templates/release/en/meter/solinteng.yaml delete mode 100644 templates/release/en/meter/solis-hybrid-s_0.yaml delete mode 100644 templates/release/en/meter/solis-hybrid-s_1.yaml delete mode 100644 templates/release/en/meter/solis-hybrid_0.yaml delete mode 100644 templates/release/en/meter/solis_0.yaml create mode 100644 templates/release/en/meter/sonnen-comfort.yaml create mode 100644 templates/release/en/meter/sonnen-eco-5.yaml create mode 100644 templates/release/en/meter/sonnen-eco-6.yaml create mode 100644 templates/release/en/meter/sonnen-oem-6-5.yaml create mode 100644 templates/release/en/meter/sonnen-sonnenbatterie.yaml delete mode 100644 templates/release/en/meter/sonnenbatterie-eco56_0.yaml delete mode 100644 templates/release/en/meter/sonnenbatterie_0.yaml create mode 100644 templates/release/en/meter/st-ems.yaml create mode 100644 templates/release/en/meter/steca-coolcept-flex.yaml delete mode 100644 templates/release/en/meter/storaxe_0.yaml delete mode 100644 templates/release/en/meter/sungrow-hybrid_0.yaml delete mode 100644 templates/release/en/meter/sungrow-inverter_0.yaml create mode 100644 templates/release/en/meter/sungrow-sg-series-inverter.yaml create mode 100644 templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml delete mode 100644 templates/release/en/meter/sunspec-battery-control_0.yaml create mode 100644 templates/release/en/meter/sunspec-battery-model-124.yaml create mode 100644 templates/release/en/meter/sunspec-battery-model-802.yaml create mode 100644 templates/release/en/meter/sunspec-hybrid-inverter.yaml delete mode 100644 templates/release/en/meter/sunspec-hybrid_0.yaml delete mode 100644 templates/release/en/meter/sunspec-inverter-control_0.yaml create mode 100644 templates/release/en/meter/sunspec-inverter.yaml delete mode 100644 templates/release/en/meter/sunspec-inverter_0.yaml create mode 100644 templates/release/en/meter/sunspec-meter.yaml delete mode 100644 templates/release/en/meter/sunspec-meter_0.yaml delete mode 100644 templates/release/en/meter/sunspec-meter_1.yaml create mode 100644 templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/sunsynk-micro-inverter.yaml create mode 100644 templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/sunsynk-string-inverter.yaml create mode 100644 templates/release/en/meter/sunway.yaml delete mode 100644 templates/release/en/meter/tapo_0.yaml delete mode 100644 templates/release/en/meter/tasmota-3p_0.yaml create mode 100644 templates/release/en/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml delete mode 100644 templates/release/en/meter/tasmota-sml_0.yaml create mode 100644 templates/release/en/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml create mode 100644 templates/release/en/meter/tasmota-three-phase.yaml delete mode 100644 templates/release/en/meter/tasmota_0.yaml create mode 100644 templates/release/en/meter/tesla-powerwall.yaml delete mode 100644 templates/release/en/meter/tesla-powerwall_0.yaml delete mode 100644 templates/release/en/meter/thor_0.yaml create mode 100644 templates/release/en/meter/tibber-pulse.yaml delete mode 100644 templates/release/en/meter/tibber-pulse_0.yaml create mode 100644 templates/release/en/meter/tp-link-h-series-smart-plug.yaml create mode 100644 templates/release/en/meter/tp-link-tapo-p-series-smart-plug.yaml delete mode 100644 templates/release/en/meter/tplink_0.yaml delete mode 100644 templates/release/en/meter/tq-em420_0.yaml delete mode 100644 templates/release/en/meter/tq-em_0.yaml create mode 100644 templates/release/en/meter/tq-energy-manager-em2xx-em3xx.yaml create mode 100644 templates/release/en/meter/tq-energy-manager-em420.yaml create mode 100644 templates/release/en/meter/varta-element.yaml create mode 100644 templates/release/en/meter/varta-pulse-neo.yaml create mode 100644 templates/release/en/meter/varta-pulse.yaml delete mode 100644 templates/release/en/meter/varta_0.yaml create mode 100644 templates/release/en/meter/victron-em24.yaml create mode 100644 templates/release/en/meter/victron-em24_e1.yaml create mode 100644 templates/release/en/meter/victron-em530-em540.yaml create mode 100644 templates/release/en/meter/victron-energy.yaml delete mode 100644 templates/release/en/meter/victron-energy_0.yaml create mode 100644 templates/release/en/meter/victron-et340.yaml delete mode 100644 templates/release/en/meter/volkszaehler-http_0.yaml delete mode 100644 templates/release/en/meter/volkszaehler-importexport_0.yaml delete mode 100644 templates/release/en/meter/volkszaehler-ws_0.yaml create mode 100644 templates/release/en/meter/volkszahler-http-api-import-and-export.yaml create mode 100644 templates/release/en/meter/volkszahler-http-api.yaml create mode 100644 templates/release/en/meter/volkszahler-websocket-api.yaml create mode 100644 templates/release/en/meter/vzlogger.yaml delete mode 100644 templates/release/en/meter/vzlogger_0.yaml create mode 100644 templates/release/en/meter/wago-879-30xx.yaml delete mode 100644 templates/release/en/meter/wago-879-30xx_0.yaml create mode 100644 templates/release/en/meter/wattsonic.yaml delete mode 100644 templates/release/en/meter/wattsonic_0.yaml delete mode 100644 templates/release/en/meter/wattsonic_1.yaml delete mode 100644 templates/release/en/meter/wattsonic_2.yaml delete mode 100644 templates/release/en/meter/wattsonic_3.yaml delete mode 100644 templates/release/en/meter/wattsonic_4.yaml create mode 100644 templates/release/en/meter/weidmuller-em110-rtu-2p.yaml create mode 100644 templates/release/en/meter/weidmuller-em111-rtu-2p.yaml create mode 100644 templates/release/en/meter/weidmuller-em120-rtu-2p.yaml create mode 100644 templates/release/en/meter/weidmuller-em122-rtu-2p.yaml create mode 100644 templates/release/en/meter/youless-energy-monitor.yaml delete mode 100644 templates/release/en/meter/youless_0.yaml create mode 100644 templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml create mode 100644 templates/release/en/meter/zcs-azzurro-inverter.yaml create mode 100644 templates/release/en/meter/zendure-hyper-2000.yaml delete mode 100644 templates/release/en/meter/zendure_0.yaml create mode 100644 templates/release/en/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml create mode 100644 templates/release/en/meter/zuidwijk-slimmelezer-plus-v2.yaml create mode 100644 templates/release/en/meter/zuidwijk-slimmelezer-plus.yaml create mode 100644 templates/release/en/tariff/amber-electric.yaml delete mode 100644 templates/release/en/tariff/amber_0.yaml create mode 100644 templates/release/en/tariff/awattar.yaml delete mode 100644 templates/release/en/tariff/awattar_0.yaml create mode 100644 templates/release/en/tariff/electricity-maps-commercial-api.yaml create mode 100644 templates/release/en/tariff/electricity-maps-free-api.yaml delete mode 100644 templates/release/en/tariff/electricitymaps-free_0.yaml delete mode 100644 templates/release/en/tariff/electricitymaps_0.yaml create mode 100644 templates/release/en/tariff/energinet.yaml delete mode 100644 templates/release/en/tariff/energinet_0.yaml delete mode 100644 templates/release/en/tariff/energy-charts-api_0.yaml create mode 100644 templates/release/en/tariff/enever.yaml delete mode 100644 templates/release/en/tariff/enever_0.yaml create mode 100644 templates/release/en/tariff/entso-e.yaml delete mode 100644 templates/release/en/tariff/entsoe_0.yaml create mode 100644 templates/release/en/tariff/forecast-solar.yaml delete mode 100644 templates/release/en/tariff/forecast-solar_0.yaml create mode 100644 templates/release/en/tariff/fraunhofer-ise.yaml create mode 100644 templates/release/en/tariff/green-grid-compass.yaml delete mode 100644 templates/release/en/tariff/green-grid-compass_0.yaml create mode 100644 templates/release/en/tariff/groupe-e-vario-plus.yaml delete mode 100644 templates/release/en/tariff/groupe-e_0.yaml create mode 100644 templates/release/en/tariff/grunstromindex.yaml delete mode 100644 "templates/release/en/tariff/gr\303\274nstromindex_0.yaml" create mode 100644 templates/release/en/tariff/national-grid-eso.yaml delete mode 100644 templates/release/en/tariff/ngeso_0.yaml create mode 100644 templates/release/en/tariff/nordpool-spot-prices.yaml delete mode 100644 templates/release/en/tariff/nordpool_0.yaml delete mode 100644 templates/release/en/tariff/octopus-api_0.yaml create mode 100644 templates/release/en/tariff/octopus-energy-api.yaml create mode 100644 templates/release/en/tariff/octopus-energy-product-code.yaml delete mode 100644 templates/release/en/tariff/octopus-productcode_0.yaml create mode 100644 templates/release/en/tariff/open-meteo.yaml delete mode 100644 templates/release/en/tariff/open-meteo_0.yaml create mode 100644 templates/release/en/tariff/ostrom.yaml delete mode 100644 templates/release/en/tariff/ostrom_0.yaml create mode 100644 templates/release/en/tariff/pun-orario.yaml delete mode 100644 templates/release/en/tariff/pun_0.yaml create mode 100644 templates/release/en/tariff/smartenergy-smartcontrol.yaml delete mode 100644 templates/release/en/tariff/smartenergy_0.yaml create mode 100644 templates/release/en/tariff/solcast.yaml delete mode 100644 templates/release/en/tariff/solcast_0.yaml create mode 100644 templates/release/en/tariff/spotty-energie.yaml delete mode 100644 templates/release/en/tariff/spottyenergy_0.yaml create mode 100644 templates/release/en/tariff/tibber.yaml delete mode 100644 templates/release/en/tariff/tibber_0.yaml create mode 100644 templates/release/en/tariff/victron-vrm-solar-forecast.yaml delete mode 100644 templates/release/en/tariff/victron_0.yaml create mode 100644 templates/release/en/vehicle/aiways.yaml delete mode 100644 templates/release/en/vehicle/aiways_0.yaml create mode 100644 templates/release/en/vehicle/audi.yaml delete mode 100644 templates/release/en/vehicle/audi_0.yaml create mode 100644 templates/release/en/vehicle/bmw.yaml delete mode 100644 templates/release/en/vehicle/bmw_0.yaml delete mode 100644 templates/release/en/vehicle/carwings_0.yaml create mode 100644 templates/release/en/vehicle/citroen.yaml delete mode 100644 templates/release/en/vehicle/citroen_0.yaml delete mode 100644 templates/release/en/vehicle/cupra_0.yaml create mode 100644 templates/release/en/vehicle/dacia.yaml delete mode 100644 templates/release/en/vehicle/dacia_0.yaml create mode 100644 templates/release/en/vehicle/ds.yaml delete mode 100644 templates/release/en/vehicle/ds_0.yaml delete mode 100644 templates/release/en/vehicle/enyaq_0.yaml create mode 100644 templates/release/en/vehicle/evnotify.yaml delete mode 100644 templates/release/en/vehicle/evnotify_0.yaml create mode 100644 templates/release/en/vehicle/fiat.yaml delete mode 100644 templates/release/en/vehicle/fiat_0.yaml delete mode 100644 templates/release/en/vehicle/fiat_1.yaml delete mode 100644 templates/release/en/vehicle/flobz_0.yaml delete mode 100644 templates/release/en/vehicle/ford-connect_0.yaml create mode 100644 templates/release/en/vehicle/ford.yaml create mode 100644 templates/release/en/vehicle/generic-vehicle-without-api.yaml create mode 100644 templates/release/en/vehicle/hyundai-bluelink.yaml delete mode 100644 templates/release/en/vehicle/hyundai_0.yaml delete mode 100644 templates/release/en/vehicle/ioBroker.bmw_0.yaml create mode 100644 templates/release/en/vehicle/iobroker-bmw.yaml create mode 100644 templates/release/en/vehicle/iso15118.yaml delete mode 100644 templates/release/en/vehicle/iso15118_0.yaml create mode 100644 templates/release/en/vehicle/jeep.yaml create mode 100644 templates/release/en/vehicle/kia-bluelink.yaml delete mode 100644 templates/release/en/vehicle/kia_0.yaml create mode 100644 templates/release/en/vehicle/mercedes-benz.yaml delete mode 100644 templates/release/en/vehicle/mercedes_0.yaml create mode 100644 templates/release/en/vehicle/mg.yaml create mode 100644 templates/release/en/vehicle/mg2mqtt.yaml delete mode 100644 templates/release/en/vehicle/mg2mqtt_0.yaml delete mode 100644 templates/release/en/vehicle/mg_0.yaml create mode 100644 templates/release/en/vehicle/mini.yaml delete mode 100644 templates/release/en/vehicle/mini_0.yaml create mode 100644 templates/release/en/vehicle/mz2mqtt.yaml delete mode 100644 templates/release/en/vehicle/mz2mqtt_0.yaml create mode 100644 templates/release/en/vehicle/nissan-ariya.yaml delete mode 100644 templates/release/en/vehicle/nissan-ariya_0.yaml create mode 100644 templates/release/en/vehicle/nissan-leaf-pre-2019.yaml create mode 100644 templates/release/en/vehicle/nissan-leaf.yaml delete mode 100644 templates/release/en/vehicle/nissan_0.yaml create mode 100644 templates/release/en/vehicle/niu-e-scooter.yaml delete mode 100644 templates/release/en/vehicle/niu-e-scooter_0.yaml delete mode 100644 templates/release/en/vehicle/offline_0.yaml create mode 100644 templates/release/en/vehicle/opel.yaml delete mode 100644 templates/release/en/vehicle/opel_0.yaml create mode 100644 templates/release/en/vehicle/open-vehicle-monitoring-system.yaml delete mode 100644 templates/release/en/vehicle/ovms_0.yaml create mode 100644 templates/release/en/vehicle/peugeot.yaml delete mode 100644 templates/release/en/vehicle/peugeot_0.yaml create mode 100644 templates/release/en/vehicle/polestar.yaml delete mode 100644 templates/release/en/vehicle/polestar_0.yaml create mode 100644 templates/release/en/vehicle/psa-car-controller.yaml create mode 100644 templates/release/en/vehicle/renault.yaml delete mode 100644 templates/release/en/vehicle/renault_0.yaml create mode 100644 templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml create mode 100644 templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml delete mode 100644 templates/release/en/vehicle/seat_0.yaml create mode 100644 templates/release/en/vehicle/skoda-enyaq.yaml create mode 100644 templates/release/en/vehicle/smart-1.yaml create mode 100644 templates/release/en/vehicle/smart-eq.yaml delete mode 100644 templates/release/en/vehicle/smart-hello_0.yaml delete mode 100644 templates/release/en/vehicle/smart_0.yaml create mode 100644 templates/release/en/vehicle/tesla-ble.yaml delete mode 100644 templates/release/en/vehicle/tesla-ble_0.yaml create mode 100644 templates/release/en/vehicle/tesla.yaml delete mode 100644 templates/release/en/vehicle/tesla_0.yaml create mode 100644 templates/release/en/vehicle/teslalogger.yaml delete mode 100644 templates/release/en/vehicle/teslalogger_0.yaml create mode 100644 templates/release/en/vehicle/teslamate.yaml delete mode 100644 templates/release/en/vehicle/teslamate_0.yaml create mode 100644 templates/release/en/vehicle/tessie.yaml delete mode 100644 templates/release/en/vehicle/tessie_0.yaml create mode 100644 templates/release/en/vehicle/toyota.yaml delete mode 100644 templates/release/en/vehicle/toyota_0.yaml create mode 100644 templates/release/en/vehicle/tronity.yaml delete mode 100644 templates/release/en/vehicle/tronity_0.yaml create mode 100644 templates/release/en/vehicle/volkswagen-we-connect-id.yaml delete mode 100644 templates/release/en/vehicle/volvo-connected_0.yaml create mode 100644 templates/release/en/vehicle/volvo.yaml create mode 100644 templates/release/en/vehicle/volvo2mqtt.yaml delete mode 100644 templates/release/en/vehicle/volvo2mqtt_0.yaml delete mode 100644 templates/release/en/vehicle/vw_0.yaml create mode 100644 templates/release/en/vehicle/zero-motorcycles.yaml delete mode 100644 templates/release/en/vehicle/zero_0.yaml diff --git a/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx b/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx new file mode 100644 index 0000000000..b35690c829 --- /dev/null +++ b/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -0,0 +1,49 @@ +--- +title: ABB Terra AC (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB Terra AC (OCPP) + + + +https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-abb-tac` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/abb-terra-ac.mdx b/docs/devices-next/chargers/abb-terra-ac.mdx index 610d44db70..fa04914cfa 100644 --- a/docs/devices-next/chargers/abb-terra-ac.mdx +++ b/docs/devices-next/chargers/abb-terra-ac.mdx @@ -1,6 +1,7 @@ --- title: ABB Terra AC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,26 +12,40 @@ import TabItem from '@theme/TabItem'; # ABB Terra AC - + -https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf +Requires firmware >= 1.6.5 :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + template: abb + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> + +## Template Parameter `abb` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/chargers/abl-em4-sbcx.mdx b/docs/devices-next/chargers/abl-em4-sbcx.mdx deleted file mode 100644 index 927c8ff2bf..0000000000 --- a/docs/devices-next/chargers/abl-em4-sbcx.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: ABL eM4 (SBCx) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL eM4 (SBCx) - - - -1 loadpoint), optional`} /> - - - diff --git a/docs/devices-next/chargers/abl-em4-single-ocpp.mdx b/docs/devices-next/chargers/abl-em4-single-ocpp.mdx new file mode 100644 index 0000000000..7d79eff172 --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Single (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Single (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-abl` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/abl-em4-single-sbcx.mdx b/docs/devices-next/chargers/abl-em4-single-sbcx.mdx new file mode 100644 index 0000000000..6cf17fea0e --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Single (SBCx) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Single (SBCx) + + + +1 loadpoint), optional`} /> + +## Template Parameter `abl-em4` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + + + diff --git a/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx b/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx new file mode 100644 index 0000000000..fe43ca44ae --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Twin (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Twin (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-abl` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx b/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx new file mode 100644 index 0000000000..46639454d3 --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Twin (SBCx) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Twin (SBCx) + + + +1 loadpoint), optional`} /> + +## Template Parameter `abl-em4` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + + + diff --git a/docs/devices-next/chargers/abl-emh1.mdx b/docs/devices-next/chargers/abl-emh1.mdx index d31bf40a9e..0500bd3e2e 100644 --- a/docs/devices-next/chargers/abl-emh1.mdx +++ b/docs/devices-next/chargers/abl-emh1.mdx @@ -1,6 +1,7 @@ --- title: ABL eMH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port timeout: 10s # Timeout, optional`} /> +## Template Parameter `abl` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | + diff --git a/docs/devices-next/chargers/abl-emh2-ocpp.mdx b/docs/devices-next/chargers/abl-emh2-ocpp.mdx new file mode 100644 index 0000000000..ed23abcbf5 --- /dev/null +++ b/docs/devices-next/chargers/abl-emh2-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eMH2 (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH2 (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-abl` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/abl-emh2.mdx b/docs/devices-next/chargers/abl-emh2.mdx index 69c6d982e8..8489de2b8b 100644 --- a/docs/devices-next/chargers/abl-emh2.mdx +++ b/docs/devices-next/chargers/abl-emh2.mdx @@ -1,6 +1,7 @@ --- title: ABL eMH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port timeout: 10s # Timeout, optional`} /> +## Template Parameter `abl` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | + diff --git a/docs/devices-next/chargers/abl-emh3-ocpp.mdx b/docs/devices-next/chargers/abl-emh3-ocpp.mdx new file mode 100644 index 0000000000..5e719ba995 --- /dev/null +++ b/docs/devices-next/chargers/abl-emh3-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eMH3 (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH3 (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-abl` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/abl-sursum-emh2.mdx b/docs/devices-next/chargers/abl-sursum-emh2.mdx deleted file mode 100644 index 78016cb9be..0000000000 --- a/docs/devices-next/chargers/abl-sursum-emh2.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: ABL Sursum eMH2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL Sursum eMH2 - - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/abl-sursum-emh3.mdx b/docs/devices-next/chargers/abl-sursum-emh3.mdx deleted file mode 100644 index 4fae7d9112..0000000000 --- a/docs/devices-next/chargers/abl-sursum-emh3.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: ABL Sursum eMH3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL Sursum eMH3 - - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/abl-sursum-emh4.mdx b/docs/devices-next/chargers/abl-sursum-emh4.mdx deleted file mode 100644 index 99997e002f..0000000000 --- a/docs/devices-next/chargers/abl-sursum-emh4.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: ABL Sursum eMH4 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL Sursum eMH4 - - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/alfen-eve-ocpp.mdx b/docs/devices-next/chargers/alfen-eve-ocpp.mdx new file mode 100644 index 0000000000..b34f71d60d --- /dev/null +++ b/docs/devices-next/chargers/alfen-eve-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: Alfen Eve (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alfen Eve (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-alfen` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/alfen-eve.mdx b/docs/devices-next/chargers/alfen-eve.mdx index 2e921d2a97..0811abd225 100644 --- a/docs/devices-next/chargers/alfen-eve.mdx +++ b/docs/devices-next/chargers/alfen-eve.mdx @@ -1,6 +1,7 @@ --- title: Alfen Eve -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alfen.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,27 @@ import TabItem from '@theme/TabItem'; # Alfen Eve - + + +The "Active load balancing" license is required for external Modbus control of the charger. Enable "Active Load Balancing" and select "Energy Management System" as Data Source in the configuration. It is recommended to set "ValidityTime" ("TCP/IP EMS" menu) to 300s. When using "Double" charger both loadpoints need to be added. The the first port (or single) is accessable on ID 1, second port on ID 2. + :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + template: alfen + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> + +## Template Parameter `alfen` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/alpha-innotec.mdx b/docs/devices-next/chargers/alpha-innotec.mdx new file mode 100644 index 0000000000..ddc78e0987 --- /dev/null +++ b/docs/devices-next/chargers/alpha-innotec.mdx @@ -0,0 +1,50 @@ +--- +title: alpha innotec +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# alpha innotec + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx index 6c4d67a324..427488a061 100644 --- a/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx +++ b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -1,6 +1,7 @@ --- title: Alphatec Ladesäule Twin custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ The motherboard requires current firmware. You can recognize a current software host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx b/docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx deleted file mode 100644 index 7e9e4b416e..0000000000 --- a/docs/devices-next/chargers/alphatec-wallbox-mini-power.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Alphatec Wallbox Mini, Power -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Alphatec Wallbox Mini, Power - - - -The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. - - - - - - diff --git a/docs/devices-next/chargers/alphatec-wallbox-mini.mdx b/docs/devices-next/chargers/alphatec-wallbox-mini.mdx new file mode 100644 index 0000000000..cbf1a14ed0 --- /dev/null +++ b/docs/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -0,0 +1,45 @@ +--- +title: Alphatec Wallbox Mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Wallbox Mini + + + +The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. + + + + +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/alphatec-wallbox-power.mdx b/docs/devices-next/chargers/alphatec-wallbox-power.mdx new file mode 100644 index 0000000000..e2e7832918 --- /dev/null +++ b/docs/devices-next/chargers/alphatec-wallbox-power.mdx @@ -0,0 +1,45 @@ +--- +title: Alphatec Wallbox Power +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Wallbox Power + + + +The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. + + + + +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx new file mode 100644 index 0000000000..0f1f33d25d --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -0,0 +1,35 @@ +--- +title: Amperfied Wallbox connect.business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.business + + + + + +## Template Parameter `amperfied` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx new file mode 100644 index 0000000000..439e8c3df0 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -0,0 +1,35 @@ +--- +title: Amperfied Wallbox connect.home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.home + + + + + +## Template Parameter `amperfied` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx new file mode 100644 index 0000000000..653eba1989 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -0,0 +1,35 @@ +--- +title: Amperfied Wallbox connect.solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.solar + + + + + +## Template Parameter `amperfied-solar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx b/docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx deleted file mode 100644 index 6a4d20c236..0000000000 --- a/docs/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Amperfied Wallbox connect.business -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Amperfied Wallbox connect.business - - - - - - - diff --git a/docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx b/docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx deleted file mode 100644 index a0db0963ae..0000000000 --- a/docs/devices-next/chargers/amperfied-wallbox-connecthome.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Amperfied Wallbox connect.home -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Amperfied Wallbox connect.home - - - - - - - diff --git a/docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx b/docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx deleted file mode 100644 index 257e44333f..0000000000 --- a/docs/devices-next/chargers/amperfied-wallbox-connectsolar.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Amperfied Wallbox connect.solar -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Amperfied Wallbox connect.solar - - - - - - - diff --git a/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx index d619a95a86..4e31ead08d 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -1,6 +1,7 @@ --- title: Amperfied Wallbox Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Please read the wiring and configuration manual carefully. All boxes must be con host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/ampure-live.mdx b/docs/devices-next/chargers/ampure-live.mdx deleted file mode 100644 index b08adcbcbd..0000000000 --- a/docs/devices-next/chargers/ampure-live.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Ampure Live -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Ampure Live - - - -The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. - - - - - - diff --git a/docs/devices-next/chargers/ampure-next.mdx b/docs/devices-next/chargers/ampure-next.mdx index 13ec4a7ed7..4a84b413e6 100644 --- a/docs/devices-next/chargers/ampure-next.mdx +++ b/docs/devices-next/chargers/ampure-next.mdx @@ -1,6 +1,7 @@ --- title: Ampure NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +## Template Parameter `webasto-next` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | + diff --git a/docs/devices-next/chargers/ampure-unite.mdx b/docs/devices-next/chargers/ampure-unite.mdx index 6213c1998a..0f66de22f1 100644 --- a/docs/devices-next/chargers/ampure-unite.mdx +++ b/docs/devices-next/chargers/ampure-unite.mdx @@ -1,6 +1,7 @@ --- title: Ampure Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/audi-audi-wallbox-pro.mdx b/docs/devices-next/chargers/audi-audi-wallbox-pro.mdx deleted file mode 100644 index 4794b9c8f4..0000000000 --- a/docs/devices-next/chargers/audi-audi-wallbox-pro.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Audi Audi Wallbox pro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Audi Audi Wallbox pro - - - -The device has to have a fix IP address (manuall or via DHCP). - -The identification of a vehicle using the RFID card is not possible. - -Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - - - - diff --git a/docs/devices-next/chargers/audi-wallbox-plus.mdx b/docs/devices-next/chargers/audi-wallbox-plus.mdx index f7ad4d001f..accc30cdf2 100644 --- a/docs/devices-next/chargers/audi-wallbox-plus.mdx +++ b/docs/devices-next/chargers/audi-wallbox-plus.mdx @@ -1,6 +1,7 @@ --- title: Audi Wallbox plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elliconnect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/audi-wallbox-pro.mdx b/docs/devices-next/chargers/audi-wallbox-pro.mdx new file mode 100644 index 0000000000..88d827a43b --- /dev/null +++ b/docs/devices-next/chargers/audi-wallbox-pro.mdx @@ -0,0 +1,37 @@ +--- +title: Audi Wallbox pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi Wallbox pro + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + + + +## Template Parameter `ellipro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/autel-ac-compact.mdx b/docs/devices-next/chargers/autel-ac-compact.mdx index c2b7b6a680..090090bcc5 100644 --- a/docs/devices-next/chargers/autel-ac-compact.mdx +++ b/docs/devices-next/chargers/autel-ac-compact.mdx @@ -1,6 +1,7 @@ --- title: AUTEL AC Compact custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,17 @@ Setup Guide: meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-autel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/autel-ac-maxicharger.mdx b/docs/devices-next/chargers/autel-ac-maxicharger.mdx index ed565a398b..414f40550c 100644 --- a/docs/devices-next/chargers/autel-ac-maxicharger.mdx +++ b/docs/devices-next/chargers/autel-ac-maxicharger.mdx @@ -1,6 +1,7 @@ --- title: AUTEL AC MaxiCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,17 @@ Setup Guide: meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-autel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/autoaid-business-wallbox.mdx b/docs/devices-next/chargers/autoaid-business-wallbox.mdx index f3ebdcd934..8f9b16101c 100644 --- a/docs/devices-next/chargers/autoaid-business-wallbox.mdx +++ b/docs/devices-next/chargers/autoaid-business-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Autoaid Business Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-autoaid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx index f1197df4e4..510f59ba37 100644 --- a/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx +++ b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Autoaid Intelligent Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-autoaid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/avm-fritzdect.mdx b/docs/devices-next/chargers/avm-fritzdect.mdx index 512b4eaa37..17d4e655ed 100644 --- a/docs/devices-next/chargers/avm-fritzdect.mdx +++ b/docs/devices-next/chargers/avm-fritzdect.mdx @@ -1,6 +1,7 @@ --- title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/fritzdect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,16 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `fritzdect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| URI
`uri` | HTTP(S) address | Standard: `https://fritz.box` | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Actor Identification Number (AIN)
`ain` | Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. | Beispiel: `307788992233` | yes | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/bender-cc612.mdx b/docs/devices-next/chargers/bender-cc612.mdx index 6508279477..8ff16ed234 100644 --- a/docs/devices-next/chargers/bender-cc612.mdx +++ b/docs/devices-next/chargers/bender-cc612.mdx @@ -1,6 +1,7 @@ --- title: Bender CC612 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/bender-cc613.mdx b/docs/devices-next/chargers/bender-cc613.mdx index 3ee32ed758..9ddd98231c 100644 --- a/docs/devices-next/chargers/bender-cc613.mdx +++ b/docs/devices-next/chargers/bender-cc613.mdx @@ -1,6 +1,7 @@ --- title: Bender CC613 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/bender-icc1314.mdx b/docs/devices-next/chargers/bender-icc1314.mdx index 4f6fc17647..ea2127342d 100644 --- a/docs/devices-next/chargers/bender-icc1314.mdx +++ b/docs/devices-next/chargers/bender-icc1314.mdx @@ -1,6 +1,7 @@ --- title: Bender ICC1314 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The configuration option 'External Energy Management' must be enabled. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/bender-icc1324.mdx b/docs/devices-next/chargers/bender-icc1324.mdx index 1b77bdbae2..5c2f893e16 100644 --- a/docs/devices-next/chargers/bender-icc1324.mdx +++ b/docs/devices-next/chargers/bender-icc1324.mdx @@ -1,6 +1,7 @@ --- title: Bender ICC1324 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The configuration option 'External Energy Management' must be enabled. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/bmw-i-wallbox.mdx b/docs/devices-next/chargers/bmw-i-wallbox.mdx index b07c221f63..23ff9f06bc 100644 --- a/docs/devices-next/chargers/bmw-i-wallbox.mdx +++ b/docs/devices-next/chargers/bmw-i-wallbox.mdx @@ -1,6 +1,7 @@ --- title: BMW i Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,12 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/chargers/bosch-sg-ready.mdx b/docs/devices-next/chargers/bosch-sg-ready.mdx index 0377aaafd1..fc879fdda7 100644 --- a/docs/devices-next/chargers/bosch-sg-ready.mdx +++ b/docs/devices-next/chargers/bosch-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Bosch SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,12 @@ Integrated via [EMSESP](https://emsesp.org/) powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> +## Template Parameter `emsesp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| `token` | | | no | +| Power source
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater` | no | + diff --git a/docs/devices-next/chargers/bosch-x-change.mdx b/docs/devices-next/chargers/bosch-x-change.mdx index 11131a1911..439f0107e5 100644 --- a/docs/devices-next/chargers/bosch-x-change.mdx +++ b/docs/devices-next/chargers/bosch-x-change.mdx @@ -1,6 +1,7 @@ --- title: Bösch x-change custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,11 @@ import TabItem from '@theme/TabItem'; tempsource: # Temperature source, [warmwater, buffer] (optional) watchdog: 60s # optional`} /> +## Template Parameter `kermi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx b/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx new file mode 100644 index 0000000000..07eb74689d --- /dev/null +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -0,0 +1,50 @@ +--- +title: Buderus Logamatic HMC 20 Z +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Buderus Logamatic HMC 20 Z + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx b/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx new file mode 100644 index 0000000000..c5928d9af3 --- /dev/null +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -0,0 +1,50 @@ +--- +title: Buderus Logamatic HMC 20 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Buderus Logamatic HMC 20 + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/buderus-sg-ready.mdx b/docs/devices-next/chargers/buderus-sg-ready.mdx index f9585b1b71..3857db3e59 100644 --- a/docs/devices-next/chargers/buderus-sg-ready.mdx +++ b/docs/devices-next/chargers/buderus-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Buderus SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,12 @@ Integrated via [EMSESP](https://emsesp.org/) powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> +## Template Parameter `emsesp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| `token` | | | no | +| Power source
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater` | no | + diff --git a/docs/devices-next/chargers/cfos-power-brain-solar.mdx b/docs/devices-next/chargers/cfos-power-brain-solar.mdx index 4942eb8304..422895b2ee 100644 --- a/docs/devices-next/chargers/cfos-power-brain-solar.mdx +++ b/docs/devices-next/chargers/cfos-power-brain-solar.mdx @@ -1,6 +1,7 @@ --- title: cFos Power Brain Solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,11 @@ Phase switching is only available with the Solar variant and must be enabled by template: cfos host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `cfos` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/cfos-power-brain.mdx b/docs/devices-next/chargers/cfos-power-brain.mdx index 7102e5d0bd..a5c27d90b7 100644 --- a/docs/devices-next/chargers/cfos-power-brain.mdx +++ b/docs/devices-next/chargers/cfos-power-brain.mdx @@ -1,6 +1,7 @@ --- title: cFos Power Brain custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,11 @@ Phase switching is only available with the Solar variant and must be enabled by template: cfos host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `cfos` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/charge-amps-halo.mdx b/docs/devices-next/chargers/charge-amps-halo.mdx index 82cfbb5cbb..29cadaeba2 100644 --- a/docs/devices-next/chargers/charge-amps-halo.mdx +++ b/docs/devices-next/chargers/charge-amps-halo.mdx @@ -1,6 +1,7 @@ --- title: Charge Amps Halo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-chargeamps.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-chargeamps` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/compleo-ebox.mdx b/docs/devices-next/chargers/compleo-ebox.mdx index c09694e8f9..96f6108c76 100644 --- a/docs/devices-next/chargers/compleo-ebox.mdx +++ b/docs/devices-next/chargers/compleo-ebox.mdx @@ -1,6 +1,7 @@ --- title: Compleo eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `innogy-ebox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx b/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx new file mode 100644 index 0000000000..1186ec7683 --- /dev/null +++ b/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -0,0 +1,50 @@ +--- +title: CTA All-In-One Aeroplus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CTA All-In-One Aeroplus + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/cubos-c11e-c22e.mdx b/docs/devices-next/chargers/cubos-c11e-c22e.mdx deleted file mode 100644 index 08907f488c..0000000000 --- a/docs/devices-next/chargers/cubos-c11e-c22e.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: CUBOS C11E, C22E -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# CUBOS C11E, C22E - - - -The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. - - - - - - diff --git a/docs/devices-next/chargers/cubos-c11e.mdx b/docs/devices-next/chargers/cubos-c11e.mdx new file mode 100644 index 0000000000..5ab9876748 --- /dev/null +++ b/docs/devices-next/chargers/cubos-c11e.mdx @@ -0,0 +1,38 @@ +--- +title: CUBOS C11E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CUBOS C11E + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/cubos-c22e.mdx b/docs/devices-next/chargers/cubos-c22e.mdx new file mode 100644 index 0000000000..55db0558a2 --- /dev/null +++ b/docs/devices-next/chargers/cubos-c22e.mdx @@ -0,0 +1,38 @@ +--- +title: CUBOS C22E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CUBOS C22E + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/cupra-charger-connect-2.mdx b/docs/devices-next/chargers/cupra-charger-connect-2.mdx index 687e757119..572adf7bef 100644 --- a/docs/devices-next/chargers/cupra-charger-connect-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-connect-2.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/cupra-charger-connect.mdx b/docs/devices-next/chargers/cupra-charger-connect.mdx index 1feebf1fc3..98b1ac4341 100644 --- a/docs/devices-next/chargers/cupra-charger-connect.mdx +++ b/docs/devices-next/chargers/cupra-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elliconnect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/cupra-charger-pro-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-2.mdx index 1160e8afe6..92ffc58fa7 100644 --- a/docs/devices-next/chargers/cupra-charger-pro-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro-2.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx index dd497ad9e8..b4d96cfa7c 100644 --- a/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/cupra-charger-pro.mdx b/docs/devices-next/chargers/cupra-charger-pro.mdx index 71975f01ef..b66843cede 100644 --- a/docs/devices-next/chargers/cupra-charger-pro.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Important: A mostly flawless functionality can only be provided with an external ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `ellipro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/dadapower-premium-wallbox.mdx b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx index 0d871b2d82..17771a0b7c 100644 --- a/docs/devices-next/chargers/dadapower-premium-wallbox.mdx +++ b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Dadapower Premium Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/dadapower.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `dadapower` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/daheimladen-wallbox.mdx b/docs/devices-next/chargers/daheimladen-wallbox.mdx index 94b16f8c4e..435bc29154 100644 --- a/docs/devices-next/chargers/daheimladen-wallbox.mdx +++ b/docs/devices-next/chargers/daheimladen-wallbox.mdx @@ -1,6 +1,7 @@ --- title: DaheimLaden Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daheimladen-mb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ Wallbox must be operated with a recent firmware including Modbus support. Furthe host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +## Template Parameter `daheimladen-mb` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | + diff --git a/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx index dc34312833..ee1de3fa59 100644 --- a/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx +++ b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Daikin HomeHub (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daikin-homehub.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperature source, [warmwater, buffer] (optional)`} /> +## Template Parameter `daikin-homehub` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | + diff --git a/docs/devices-next/chargers/delta-ac-max-basic.mdx b/docs/devices-next/chargers/delta-ac-max-basic.mdx index 0899099e7a..65244b2a07 100644 --- a/docs/devices-next/chargers/delta-ac-max-basic.mdx +++ b/docs/devices-next/chargers/delta-ac-max-basic.mdx @@ -1,6 +1,7 @@ --- title: Delta AC Max Basic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `delta` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/delta-ac-max-smart.mdx b/docs/devices-next/chargers/delta-ac-max-smart.mdx index e35400f760..3a191f8e4a 100644 --- a/docs/devices-next/chargers/delta-ac-max-smart.mdx +++ b/docs/devices-next/chargers/delta-ac-max-smart.mdx @@ -1,6 +1,7 @@ --- title: Delta AC MAX Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `delta` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/delta-slim-charger.mdx b/docs/devices-next/chargers/delta-slim-charger.mdx index d1af7483e7..db555fbd40 100644 --- a/docs/devices-next/chargers/delta-slim-charger.mdx +++ b/docs/devices-next/chargers/delta-slim-charger.mdx @@ -1,6 +1,7 @@ --- title: Delta SLIM Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `delta` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/delta-ultra-fast-charger.mdx b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx index e8e290aaac..b184805abf 100644 --- a/docs/devices-next/chargers/delta-ultra-fast-charger.mdx +++ b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -1,6 +1,7 @@ --- title: Delta Ultra Fast Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `delta` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/demo-charger.mdx b/docs/devices-next/chargers/demo-charger.mdx index 19a91fd024..d7794b883b 100644 --- a/docs/devices-next/chargers/demo-charger.mdx +++ b/docs/devices-next/chargers/demo-charger.mdx @@ -1,6 +1,7 @@ --- title: Demo charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/demo-charger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,13 @@ For demonstration purposes. Charger with a fixed set of values. maxcurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) phases1p3p: false # Phase switching, optional`} /> +## Template Parameter `demo-charger` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Charge status
`status` | | Standard: `A`
Auswahl: `A`, `B`, `C` | yes | +| Power
`power` | | | no | +| Enabled
`enabled` | | Standard: `true` | no | +| Maximum amperage
`maxcurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Phase switching
`phases1p3p` | | | no | + diff --git a/docs/devices-next/chargers/e-on-drive-ebox.mdx b/docs/devices-next/chargers/e-on-drive-ebox.mdx new file mode 100644 index 0000000000..de7f7118da --- /dev/null +++ b/docs/devices-next/chargers/e-on-drive-ebox.mdx @@ -0,0 +1,35 @@ +--- +title: E.ON Drive eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive eBox + + + + + +## Template Parameter `innogy-ebox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/e-on-drive-vbox.mdx b/docs/devices-next/chargers/e-on-drive-vbox.mdx new file mode 100644 index 0000000000..fefc4bf2f2 --- /dev/null +++ b/docs/devices-next/chargers/e-on-drive-vbox.mdx @@ -0,0 +1,38 @@ +--- +title: E.ON Drive vBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive vBox + + + +1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. + + + + +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/e3-dc-easy-connect.mdx b/docs/devices-next/chargers/e3-dc-easy-connect.mdx new file mode 100644 index 0000000000..bc1e76f3e3 --- /dev/null +++ b/docs/devices-next/chargers/e3-dc-easy-connect.mdx @@ -0,0 +1,38 @@ +--- +title: E3/DC Easy Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC Easy Connect + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/e3dc-easy-connect.mdx b/docs/devices-next/chargers/e3dc-easy-connect.mdx deleted file mode 100644 index 5d17d6537a..0000000000 --- a/docs/devices-next/chargers/e3dc-easy-connect.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: E3/DC Easy Connect -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E3/DC Easy Connect - - - -DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. - - - - - - diff --git a/docs/devices-next/chargers/easee-charge-core.mdx b/docs/devices-next/chargers/easee-charge-core.mdx index 948df12c5a..0ffdfd7195 100644 --- a/docs/devices-next/chargers/easee-charge-core.mdx +++ b/docs/devices-next/chargers/easee-charge-core.mdx @@ -1,6 +1,7 @@ --- title: Easee Charge Core custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +## Template Parameter `easee` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | Email address | | yes | +| Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | +| `charger` | | Beispiel: `EH______` | yes | +| Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | +| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | + diff --git a/docs/devices-next/chargers/easee-charge-lite.mdx b/docs/devices-next/chargers/easee-charge-lite.mdx index aa3e7ef412..888376913f 100644 --- a/docs/devices-next/chargers/easee-charge-lite.mdx +++ b/docs/devices-next/chargers/easee-charge-lite.mdx @@ -1,6 +1,7 @@ --- title: Easee Charge Lite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +## Template Parameter `easee` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | Email address | | yes | +| Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | +| `charger` | | Beispiel: `EH______` | yes | +| Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | +| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | + diff --git a/docs/devices-next/chargers/easee-charge.mdx b/docs/devices-next/chargers/easee-charge.mdx index fee1d7ee64..efb812e7d7 100644 --- a/docs/devices-next/chargers/easee-charge.mdx +++ b/docs/devices-next/chargers/easee-charge.mdx @@ -1,6 +1,7 @@ --- title: Easee Charge custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +## Template Parameter `easee` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | Email address | | yes | +| Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | +| `charger` | | Beispiel: `EH______` | yes | +| Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | +| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | + diff --git a/docs/devices-next/chargers/easee-home.mdx b/docs/devices-next/chargers/easee-home.mdx index 69326be221..dd532e264f 100644 --- a/docs/devices-next/chargers/easee-home.mdx +++ b/docs/devices-next/chargers/easee-home.mdx @@ -1,6 +1,7 @@ --- title: Easee Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +## Template Parameter `easee` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | Email address | | yes | +| Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | +| `charger` | | Beispiel: `EH______` | yes | +| Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | +| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | + diff --git a/docs/devices-next/chargers/ebee-wallbox.mdx b/docs/devices-next/chargers/ebee-wallbox.mdx index 36e31cb966..4f610a8900 100644 --- a/docs/devices-next/chargers/ebee-wallbox.mdx +++ b/docs/devices-next/chargers/ebee-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Ebee Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/echarge-cph1.mdx b/docs/devices-next/chargers/echarge-cph1.mdx index 6931953a1a..c3d0ac772f 100644 --- a/docs/devices-next/chargers/echarge-cph1.mdx +++ b/docs/devices-next/chargers/echarge-cph1.mdx @@ -1,6 +1,7 @@ --- title: echarge cPH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,12 @@ Charge mode must be configured as `manual` host: 192.0.2.2 # IP address or hostname connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `hardybarth-ecb1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/echarge-cph2-cpm2.mdx b/docs/devices-next/chargers/echarge-cph2-cpm2.mdx deleted file mode 100644 index 32d6f23561..0000000000 --- a/docs/devices-next/chargers/echarge-cph2-cpm2.mdx +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: echarge cPH2, cPμ2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# echarge cPH2, cPμ2 - - - - - - - diff --git a/docs/devices-next/chargers/echarge-cph2.mdx b/docs/devices-next/chargers/echarge-cph2.mdx new file mode 100644 index 0000000000..47e8fe531d --- /dev/null +++ b/docs/devices-next/chargers/echarge-cph2.mdx @@ -0,0 +1,30 @@ +--- +title: echarge cPH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPH2 + + + + + +## Template Parameter `hardybarth-salia` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + + + diff --git a/docs/devices-next/chargers/echarge-cpm2.mdx b/docs/devices-next/chargers/echarge-cpm2.mdx new file mode 100644 index 0000000000..5886040db5 --- /dev/null +++ b/docs/devices-next/chargers/echarge-cpm2.mdx @@ -0,0 +1,30 @@ +--- +title: echarge cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPμ2 + + + + + +## Template Parameter `hardybarth-salia` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + + + diff --git a/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx b/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx new file mode 100644 index 0000000000..ee9ef213f7 --- /dev/null +++ b/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -0,0 +1,46 @@ +--- +title: EcoHarmony EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EcoHarmony EVSE EPC 2.0 Plus + + + + + +## Template Parameter `obo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx b/docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx deleted file mode 100644 index 2b99761d93..0000000000 --- a/docs/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: EcoHarmony EVSE EPC 2.0 Plus -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# EcoHarmony EVSE EPC 2.0 Plus - - - - - diff --git a/docs/devices-next/chargers/edgetech-smart-evse.mdx b/docs/devices-next/chargers/edgetech-smart-evse.mdx index d9f3b3f146..11eafc16b1 100644 --- a/docs/devices-next/chargers/edgetech-smart-evse.mdx +++ b/docs/devices-next/chargers/edgetech-smart-evse.mdx @@ -1,6 +1,7 @@ --- title: Edgetech Smart EVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartevse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `smartevse` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/eebus-compatible.mdx b/docs/devices-next/chargers/eebus-compatible.mdx index 13ee920779..7e22859905 100644 --- a/docs/devices-next/chargers/eebus-compatible.mdx +++ b/docs/devices-next/chargers/eebus-compatible.mdx @@ -1,6 +1,7 @@ --- title: EEBUS compatible custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eebus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,10 @@ import TabItem from '@theme/TabItem'; ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `eebus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/elco.mdx b/docs/devices-next/chargers/elco.mdx new file mode 100644 index 0000000000..a9df553694 --- /dev/null +++ b/docs/devices-next/chargers/elco.mdx @@ -0,0 +1,50 @@ +--- +title: Elco +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elco + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/elecq-biz.mdx b/docs/devices-next/chargers/elecq-biz.mdx index afc8e3e56a..fe63e627c6 100644 --- a/docs/devices-next/chargers/elecq-biz.mdx +++ b/docs/devices-next/chargers/elecq-biz.mdx @@ -1,6 +1,7 @@ --- title: Elecq Biz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-elecq` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/elecq-home.mdx b/docs/devices-next/chargers/elecq-home.mdx index ab4b3618b7..9cef59bc11 100644 --- a/docs/devices-next/chargers/elecq-home.mdx +++ b/docs/devices-next/chargers/elecq-home.mdx @@ -1,6 +1,7 @@ --- title: Elecq Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-elecq` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/elecq-station.mdx b/docs/devices-next/chargers/elecq-station.mdx index c11adaef5c..43fea337f2 100644 --- a/docs/devices-next/chargers/elecq-station.mdx +++ b/docs/devices-next/chargers/elecq-station.mdx @@ -1,6 +1,7 @@ --- title: Elecq Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-elecq` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/eledio-go.mdx b/docs/devices-next/chargers/eledio-go.mdx index f5b4da2250..ad2ae603d4 100644 --- a/docs/devices-next/chargers/eledio-go.mdx +++ b/docs/devices-next/chargers/eledio-go.mdx @@ -1,6 +1,7 @@ --- title: eledio go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-enercab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/elli-charger-connect-2.mdx b/docs/devices-next/chargers/elli-charger-connect-2.mdx index 7b1040423f..539097c62f 100644 --- a/docs/devices-next/chargers/elli-charger-connect-2.mdx +++ b/docs/devices-next/chargers/elli-charger-connect-2.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/elli-charger-connect.mdx b/docs/devices-next/chargers/elli-charger-connect.mdx index fcdae5d8ca..ae92f9d6fb 100644 --- a/docs/devices-next/chargers/elli-charger-connect.mdx +++ b/docs/devices-next/chargers/elli-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elliconnect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/elli-charger-pro-2.mdx b/docs/devices-next/chargers/elli-charger-pro-2.mdx index 08027242a5..3f4b3c3147 100644 --- a/docs/devices-next/chargers/elli-charger-pro-2.mdx +++ b/docs/devices-next/chargers/elli-charger-pro-2.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx index 7130dfa9bc..3f220a92df 100644 --- a/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/elli-charger-pro.mdx b/docs/devices-next/chargers/elli-charger-pro.mdx index f02937069c..d78895d99e 100644 --- a/docs/devices-next/chargers/elli-charger-pro.mdx +++ b/docs/devices-next/chargers/elli-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Important: A mostly flawless functionality can only be provided with an external ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `ellipro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/em2go-home.mdx b/docs/devices-next/chargers/em2go-home.mdx index 533ae90c11..30638a0f05 100644 --- a/docs/devices-next/chargers/em2go-home.mdx +++ b/docs/devices-next/chargers/em2go-home.mdx @@ -1,6 +1,7 @@ --- title: EM2GO Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go-home.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,9 @@ Requires FW Version >= E3C_V1.1. mA regulation requires FW version >= E3C_V1.3. template: em2go-home host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `em2go-home` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx b/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx new file mode 100644 index 0000000000..3c680ba50f --- /dev/null +++ b/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -0,0 +1,36 @@ +--- +title: EM2GO Pro Power (OCPP/ONC) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EM2GO Pro Power (OCPP/ONC) + + + +Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15) + + + + +## Template Parameter `em2go` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx b/docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx deleted file mode 100644 index 95ac09a448..0000000000 --- a/docs/devices-next/chargers/em2go-pro-power-ocpponc.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: EM2GO Pro Power, OCPP/ONC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# EM2GO Pro Power, OCPP/ONC - - - -Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15) - - - - diff --git a/docs/devices-next/chargers/en-ac-ev-charger.mdx b/docs/devices-next/chargers/en-ac-ev-charger.mdx deleted file mode 100644 index f4e3854946..0000000000 --- a/docs/devices-next/chargers/en-ac-ev-charger.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: EN+ AC EV Charger -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# EN+ AC EV Charger - - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/enercab-smart.mdx b/docs/devices-next/chargers/enercab-smart.mdx index 0729ea0aa3..c95899f200 100644 --- a/docs/devices-next/chargers/enercab-smart.mdx +++ b/docs/devices-next/chargers/enercab-smart.mdx @@ -1,6 +1,7 @@ --- title: enercab smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-enercab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/enplus-ac-ev-charger.mdx b/docs/devices-next/chargers/enplus-ac-ev-charger.mdx new file mode 100644 index 0000000000..c2a9414cd4 --- /dev/null +++ b/docs/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -0,0 +1,46 @@ +--- +title: EN+ AC EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EN+ AC EV Charger + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-enplus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/ensto-chago-wallbox.mdx b/docs/devices-next/chargers/ensto-chago-wallbox.mdx index c59d4ed91f..07310463bd 100644 --- a/docs/devices-next/chargers/ensto-chago-wallbox.mdx +++ b/docs/devices-next/chargers/ensto-chago-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Ensto Chago Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/entratek-power-dot-fix.mdx b/docs/devices-next/chargers/entratek-power-dot-fix.mdx index b6913b5778..af035b2296 100644 --- a/docs/devices-next/chargers/entratek-power-dot-fix.mdx +++ b/docs/devices-next/chargers/entratek-power-dot-fix.mdx @@ -1,6 +1,7 @@ --- title: EntraTek Power Dot Fix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-entratek` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx index fae5d66726..100efd0d5c 100644 --- a/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx +++ b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -1,6 +1,7 @@ --- title: EntraTek Power Dot Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-entratek` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/eon-drive-ebox.mdx b/docs/devices-next/chargers/eon-drive-ebox.mdx deleted file mode 100644 index 9fa1d98fbf..0000000000 --- a/docs/devices-next/chargers/eon-drive-ebox.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: E.ON Drive eBox -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E.ON Drive eBox - - - - - - - diff --git a/docs/devices-next/chargers/eon-drive-vbox.mdx b/docs/devices-next/chargers/eon-drive-vbox.mdx deleted file mode 100644 index 63221599d7..0000000000 --- a/docs/devices-next/chargers/eon-drive-vbox.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: E.ON Drive vBox -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E.ON Drive vBox - - - -1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. - - - - - - diff --git a/docs/devices-next/chargers/esl-walli-light.mdx b/docs/devices-next/chargers/esl-walli-light.mdx index 270671e5df..4ce5b517d5 100644 --- a/docs/devices-next/chargers/esl-walli-light.mdx +++ b/docs/devices-next/chargers/esl-walli-light.mdx @@ -1,6 +1,7 @@ --- title: ESL Walli LIGHT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/esystems-ghostone.mdx b/docs/devices-next/chargers/esystems-ghostone.mdx index 778d9f08a5..a5eef6e95e 100644 --- a/docs/devices-next/chargers/esystems-ghostone.mdx +++ b/docs/devices-next/chargers/esystems-ghostone.mdx @@ -1,6 +1,7 @@ --- title: eSystems ghostONE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `ghost` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/etrel-inch-duo.mdx b/docs/devices-next/chargers/etrel-inch-duo.mdx index 2c26c9cf8d..e88c19ed09 100644 --- a/docs/devices-next/chargers/etrel-inch-duo.mdx +++ b/docs/devices-next/chargers/etrel-inch-duo.mdx @@ -1,6 +1,7 @@ --- title: Etrel INCH Duo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel-duo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,13 @@ The charger must be switched to "Power" charging mode. port: 502 # Port, optional connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `etrel-duo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/etrel-inch.mdx b/docs/devices-next/chargers/etrel-inch.mdx index 5b58e5c7b1..9cbe001883 100644 --- a/docs/devices-next/chargers/etrel-inch.mdx +++ b/docs/devices-next/chargers/etrel-inch.mdx @@ -1,6 +1,7 @@ --- title: Etrel INCH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ The charger must be switched to "Power" charging mode. host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +## Template Parameter `etrel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | + diff --git a/docs/devices-next/chargers/evbox-elvi.mdx b/docs/devices-next/chargers/evbox-elvi.mdx index dcf125e4e9..61ac8c831a 100644 --- a/docs/devices-next/chargers/evbox-elvi.mdx +++ b/docs/devices-next/chargers/evbox-elvi.mdx @@ -1,6 +1,7 @@ --- title: EVBox Elvi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-evbox-elvi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,5 +31,17 @@ import TabItem from '@theme/TabItem'; connecttimeout: 5m # Timeout for the registration of the charging point, optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-evbox-elvi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| `meter` | | Standard: `true` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/evbox-livo.mdx b/docs/devices-next/chargers/evbox-livo.mdx index f4c0b4f6e3..6ed0e2801b 100644 --- a/docs/devices-next/chargers/evbox-livo.mdx +++ b/docs/devices-next/chargers/evbox-livo.mdx @@ -1,6 +1,7 @@ --- title: EVBox Livo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/livo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `livo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/evse-din.mdx b/docs/devices-next/chargers/evse-din.mdx index 66343afe2a..72b1f73f50 100644 --- a/docs/devices-next/chargers/evse-din.mdx +++ b/docs/devices-next/chargers/evse-din.mdx @@ -1,6 +1,7 @@ --- title: EVSE DIN custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `evse-din` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/evse-wifi.mdx b/docs/devices-next/chargers/evse-wifi.mdx index d661e95728..5c1b2a05b9 100644 --- a/docs/devices-next/chargers/evse-wifi.mdx +++ b/docs/devices-next/chargers/evse-wifi.mdx @@ -1,6 +1,7 @@ --- title: EVSE-WiFi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evsewifi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: evsewifi host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `evsewifi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/free2move-eprowallbox-move.mdx b/docs/devices-next/chargers/free2move-eprowallbox-move.mdx new file mode 100644 index 0000000000..06f6421e12 --- /dev/null +++ b/docs/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -0,0 +1,42 @@ +--- +title: Free2Move eProWallbox Move +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Free2Move eProWallbox Move + + + + + +## Template Parameter `eprowallbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/free2move-eprowallbox.mdx b/docs/devices-next/chargers/free2move-eprowallbox.mdx index fa1915c2c6..32f6154e4d 100644 --- a/docs/devices-next/chargers/free2move-eprowallbox.mdx +++ b/docs/devices-next/chargers/free2move-eprowallbox.mdx @@ -1,6 +1,7 @@ --- title: Free2Move eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,5 +32,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `eprowallbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx index 8c593c8999..aca2bad025 100644 --- a/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx +++ b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -1,6 +1,7 @@ --- title: Free2move eSolutions eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-esolutions.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-esolutions` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx b/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx new file mode 100644 index 0000000000..52ec2ada0b --- /dev/null +++ b/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: Fronius Wattpilot (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Wattpilot (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-goe` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/fronius-wattpilot.mdx b/docs/devices-next/chargers/fronius-wattpilot.mdx deleted file mode 100644 index 0e46a80065..0000000000 --- a/docs/devices-next/chargers/fronius-wattpilot.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Fronius Wattpilot -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Fronius Wattpilot - - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx b/docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx deleted file mode 100644 index 3f640dca66..0000000000 --- a/docs/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Garo GLB, GLB+, LS4, LS4 compact -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Garo GLB, GLB+, LS4, LS4 compact - - - -The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. - - - - - - diff --git a/docs/devices-next/chargers/garo-glb.mdx b/docs/devices-next/chargers/garo-glb.mdx new file mode 100644 index 0000000000..54280af247 --- /dev/null +++ b/docs/devices-next/chargers/garo-glb.mdx @@ -0,0 +1,38 @@ +--- +title: Garo GLB +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo GLB + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/garo-glbplus.mdx b/docs/devices-next/chargers/garo-glbplus.mdx new file mode 100644 index 0000000000..e0ad8c835b --- /dev/null +++ b/docs/devices-next/chargers/garo-glbplus.mdx @@ -0,0 +1,38 @@ +--- +title: Garo GLB+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo GLB+ + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/garo-ls4-compact.mdx b/docs/devices-next/chargers/garo-ls4-compact.mdx new file mode 100644 index 0000000000..e43f0f09a2 --- /dev/null +++ b/docs/devices-next/chargers/garo-ls4-compact.mdx @@ -0,0 +1,38 @@ +--- +title: Garo LS4 compact +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo LS4 compact + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/garo-ls4.mdx b/docs/devices-next/chargers/garo-ls4.mdx new file mode 100644 index 0000000000..d42012e3f5 --- /dev/null +++ b/docs/devices-next/chargers/garo-ls4.mdx @@ -0,0 +1,38 @@ +--- +title: Garo LS4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo LS4 + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx new file mode 100644 index 0000000000..5b43422d0b --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: go-e Charger Gemini (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger Gemini (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-goe` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/go-e-charger-gemini.mdx b/docs/devices-next/chargers/go-e-charger-gemini.mdx index 6576568234..d77cb936aa 100644 --- a/docs/devices-next/chargers/go-e-charger-gemini.mdx +++ b/docs/devices-next/chargers/go-e-charger-gemini.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger Gemini -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,24 @@ import TabItem from '@theme/TabItem'; # go-e Charger Gemini - + + +Requires firmware 052.1 or later. +Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. +The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). + :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + template: go-e-v3 + host: 192.0.2.2 # IP address or hostname`} /> + +## Template Parameter `go-e-v3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | diff --git a/docs/devices-next/chargers/go-e-charger-home.mdx b/docs/devices-next/chargers/go-e-charger-home.mdx deleted file mode 100644 index f8d50f6d24..0000000000 --- a/docs/devices-next/chargers/go-e-charger-home.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: go-e Charger HOME+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# go-e Charger HOME+ - - - -Requires firmware 052.1 or later. -Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. -The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). - - - - - - diff --git a/docs/devices-next/chargers/go-e-charger-homefix.mdx b/docs/devices-next/chargers/go-e-charger-homefix.mdx index f50e131f9d..f60e1107a6 100644 --- a/docs/devices-next/chargers/go-e-charger-homefix.mdx +++ b/docs/devices-next/chargers/go-e-charger-homefix.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger HOMEfix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,5 +23,11 @@ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. template: go-e host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `go-e` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/go-e-charger-homeplus.mdx b/docs/devices-next/chargers/go-e-charger-homeplus.mdx new file mode 100644 index 0000000000..e1781976e9 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-homeplus.mdx @@ -0,0 +1,35 @@ +--- +title: go-e Charger HOME+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger HOME+ + + + +Requires firmware 052.1 or later. +Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. +The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). + + + + +## Template Parameter `go-e-v3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + + + diff --git a/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx new file mode 100644 index 0000000000..48638d700d --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: go-e Charger PRO (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger PRO (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-goe` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/go-e-charger-pro.mdx b/docs/devices-next/chargers/go-e-charger-pro.mdx index 4494d18b1a..eb32e864bd 100644 --- a/docs/devices-next/chargers/go-e-charger-pro.mdx +++ b/docs/devices-next/chargers/go-e-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger PRO -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,22 @@ import TabItem from '@theme/TabItem'; # go-e Charger PRO - + + +Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. + :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + template: go-e + host: 192.0.2.2 # IP address or hostname`} /> + +## Template Parameter `go-e` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | diff --git a/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx new file mode 100644 index 0000000000..4dab005bef --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: go-e Charger V3 (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger V3 (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-goe` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/go-e-charger-v3.mdx b/docs/devices-next/chargers/go-e-charger-v3.mdx index f999ca3c9a..7878ab3fe3 100644 --- a/docs/devices-next/chargers/go-e-charger-v3.mdx +++ b/docs/devices-next/chargers/go-e-charger-v3.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger V3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,24 @@ import TabItem from '@theme/TabItem'; # go-e Charger V3 - + + +Requires firmware 052.1 or later. +Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. +The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). + :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + template: go-e-v3 + host: 192.0.2.2 # IP address or hostname`} /> + +## Template Parameter `go-e-v3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | diff --git a/docs/devices-next/chargers/hardy-barth-cph1.mdx b/docs/devices-next/chargers/hardy-barth-cph1.mdx new file mode 100644 index 0000000000..bdda6656a4 --- /dev/null +++ b/docs/devices-next/chargers/hardy-barth-cph1.mdx @@ -0,0 +1,39 @@ +--- +title: Hardy Barth cPH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hardy Barth cPH1 + + + +Charge mode must be configured as `manual` + + +1 loadpoint), optional`} /> + +## Template Parameter `hardybarth-ecb1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + + + diff --git a/docs/devices-next/chargers/hardy-barth-cph2.mdx b/docs/devices-next/chargers/hardy-barth-cph2.mdx new file mode 100644 index 0000000000..907b33b0da --- /dev/null +++ b/docs/devices-next/chargers/hardy-barth-cph2.mdx @@ -0,0 +1,30 @@ +--- +title: Hardy Barth cPH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hardy Barth cPH2 + + + + + +## Template Parameter `hardybarth-salia` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + + + diff --git a/docs/devices-next/chargers/hardy-barth-cpm2.mdx b/docs/devices-next/chargers/hardy-barth-cpm2.mdx new file mode 100644 index 0000000000..3e7b6a2cd5 --- /dev/null +++ b/docs/devices-next/chargers/hardy-barth-cpm2.mdx @@ -0,0 +1,30 @@ +--- +title: Hardy Barth cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hardy Barth cPμ2 + + + + + +## Template Parameter `hardybarth-salia` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + + + diff --git a/docs/devices-next/chargers/hardybarth-cph1.mdx b/docs/devices-next/chargers/hardybarth-cph1.mdx deleted file mode 100644 index 5b0ae4d8e8..0000000000 --- a/docs/devices-next/chargers/hardybarth-cph1.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: HardyBarth cPH1 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# HardyBarth cPH1 - - - -Charge mode must be configured as `manual` - - -1 loadpoint), optional`} /> - - - diff --git a/docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx b/docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx deleted file mode 100644 index f22698bc11..0000000000 --- a/docs/devices-next/chargers/hardybarth-cph2-cpm2.mdx +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: HardyBarth cPH2, cPμ2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# HardyBarth cPH2, cPμ2 - - - - - - - diff --git a/docs/devices-next/chargers/heidelberg-energy-control.mdx b/docs/devices-next/chargers/heidelberg-energy-control.mdx index 9446adc0c3..7784efbc87 100644 --- a/docs/devices-next/chargers/heidelberg-energy-control.mdx +++ b/docs/devices-next/chargers/heidelberg-energy-control.mdx @@ -1,6 +1,7 @@ --- title: Heidelberg Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Please read the wiring and configuration manual carefully. All boxes must be con host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/hesotec-ebox.mdx b/docs/devices-next/chargers/hesotec-ebox.mdx new file mode 100644 index 0000000000..c48477cdb7 --- /dev/null +++ b/docs/devices-next/chargers/hesotec-ebox.mdx @@ -0,0 +1,35 @@ +--- +title: Hesotec eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hesotec eBox + + + + + +## Template Parameter `hesotec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/hesotec-esat-ebox.mdx b/docs/devices-next/chargers/hesotec-esat-ebox.mdx deleted file mode 100644 index 815f7bf64a..0000000000 --- a/docs/devices-next/chargers/hesotec-esat-ebox.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Hesotec eSat, eBox -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Hesotec eSat, eBox - - - - - - - diff --git a/docs/devices-next/chargers/hesotec-esat.mdx b/docs/devices-next/chargers/hesotec-esat.mdx new file mode 100644 index 0000000000..08e7a0037a --- /dev/null +++ b/docs/devices-next/chargers/hesotec-esat.mdx @@ -0,0 +1,35 @@ +--- +title: Hesotec eSat +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hesotec eSat + + + + + +## Template Parameter `hesotec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/home-assistant-switch.mdx b/docs/devices-next/chargers/home-assistant-switch.mdx index b925ff9f0f..ac62a24fd8 100644 --- a/docs/devices-next/chargers/home-assistant-switch.mdx +++ b/docs/devices-next/chargers/home-assistant-switch.mdx @@ -1,6 +1,7 @@ --- title: Home Assistant Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homeassistant-switch.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,16 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `homeassistant-switch` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Base URL of the Home Assistant instance
`baseurl` | | Beispiel: `http://homeassistant.local:8123` | yes | +| Long-Lived Access Token
`token` | from Home Assistant profile | | yes | +| Entity ID of the switch device
`switchentity` | | Beispiel: `switch.smartsocket` | yes | +| Entity ID for power measurement
`powerentity` | | Beispiel: `sensor.smartsocket_power` | no | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/homecharge-homecharger.mdx b/docs/devices-next/chargers/homecharge-homecharger.mdx index aeda593af8..836410def7 100644 --- a/docs/devices-next/chargers/homecharge-homecharger.mdx +++ b/docs/devices-next/chargers/homecharge-homecharger.mdx @@ -1,6 +1,7 @@ --- title: Homecharge Homecharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-homecharge.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ For login credentials, ask your dealer or the vendor EFR (www.efr.de). meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-homecharge` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/homematic-ip.mdx b/docs/devices-next/chargers/homematic-ip.mdx index ac56889015..5704dcdeec 100644 --- a/docs/devices-next/chargers/homematic-ip.mdx +++ b/docs/devices-next/chargers/homematic-ip.mdx @@ -1,6 +1,7 @@ --- title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homematic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `homematic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010)
`port` | | Standard: `2010` | no | +| Device address/Serial number
`device` | Homematic device id like shown in the CCU web user interface. | Beispiel: `0001EE89AAD848` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2)
`meterchannel` | Homematic meter channel number like shown in the CCU web user interface. | Standard: `6` | yes | +| Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1)
`switchchannel` | Homematic switch actor channel number like shown in the CCU web user interface. | Standard: `3` | yes | +| XML-RPC api cache duration - Default 1s. (valid units are s,m,h)
`cache` | In case of duty cycle problems try a cache setting of 30s. | Standard: `1s`
Beispiel: `5m` | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/homewizard.mdx b/docs/devices-next/chargers/homewizard.mdx index 9362080e33..51dd5e83db 100644 --- a/docs/devices-next/chargers/homewizard.mdx +++ b/docs/devices-next/chargers/homewizard.mdx @@ -1,6 +1,7 @@ --- title: HomeWizard custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homewizard.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `homewizard` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx b/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx new file mode 100644 index 0000000000..ef8af32765 --- /dev/null +++ b/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -0,0 +1,46 @@ +--- +title: Huawei SCharger-22KT-S0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SCharger-22KT-S0 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-huawei` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx b/docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx deleted file mode 100644 index f29a63101d..0000000000 --- a/docs/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Huawei SCharger-7KS-S0 / 22KT-S0 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Huawei SCharger-7KS-S0 / 22KT-S0 - - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx b/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx new file mode 100644 index 0000000000..0fea498495 --- /dev/null +++ b/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -0,0 +1,46 @@ +--- +title: Huawei SCharger-7KS-S0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SCharger-7KS-S0 + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-huawei` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/idm.mdx b/docs/devices-next/chargers/idm.mdx index 525683ef76..f7c53a6ecf 100644 --- a/docs/devices-next/chargers/idm.mdx +++ b/docs/devices-next/chargers/idm.mdx @@ -1,6 +1,7 @@ --- title: IDM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/idm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer] (optional)`} /> +## Template Parameter `idm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer` | no | + diff --git a/docs/devices-next/chargers/index.mdx b/docs/devices-next/chargers/index.mdx index 4d80e03a30..e0a7fe557e 100644 --- a/docs/devices-next/chargers/index.mdx +++ b/docs/devices-next/chargers/index.mdx @@ -56,13 +56,13 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; + + + - + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `innogy-ebox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/inro-pantabox.mdx b/docs/devices-next/chargers/inro-pantabox.mdx index d6d24e490a..968f06aaef 100644 --- a/docs/devices-next/chargers/inro-pantabox.mdx +++ b/docs/devices-next/chargers/inro-pantabox.mdx @@ -1,6 +1,7 @@ --- title: INRO Pantabox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pantabox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: pantabox host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `pantabox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/juice-charger-me.mdx b/docs/devices-next/chargers/juice-charger-me.mdx index 9aeafcdefb..6399c5772a 100644 --- a/docs/devices-next/chargers/juice-charger-me.mdx +++ b/docs/devices-next/chargers/juice-charger-me.mdx @@ -1,6 +1,7 @@ --- title: Juice Charger Me custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/junkers-sg-ready.mdx b/docs/devices-next/chargers/junkers-sg-ready.mdx index 2a17db6485..bc289f0749 100644 --- a/docs/devices-next/chargers/junkers-sg-ready.mdx +++ b/docs/devices-next/chargers/junkers-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Junkers SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,12 @@ Integrated via [EMSESP](https://emsesp.org/) powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> +## Template Parameter `emsesp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| `token` | | | no | +| Power source
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater` | no | + diff --git a/docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx deleted file mode 100644 index a4b83dd447..0000000000 --- a/docs/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E - - - -The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 - - - - - - diff --git a/docs/devices-next/chargers/kathrein-kwb-ac20.mdx b/docs/devices-next/chargers/kathrein-kwb-ac20.mdx new file mode 100644 index 0000000000..964f868df2 --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC20 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC20 + + + +The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 + + + + +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/kathrein-kwb-ac35.mdx b/docs/devices-next/chargers/kathrein-kwb-ac35.mdx new file mode 100644 index 0000000000..158d9933dc --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC35 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC35 + + + +The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 + + + + +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx new file mode 100644 index 0000000000..28f4b9376b --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC40 E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC40 E + + + +The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 + + + + +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/kathrein-kwb-ac40.mdx b/docs/devices-next/chargers/kathrein-kwb-ac40.mdx new file mode 100644 index 0000000000..a27c9858b7 --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC40 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC40 + + + +The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 + + + + +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx new file mode 100644 index 0000000000..280db3ed76 --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC60 E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC60 E + + + +The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 + + + + +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/kathrein-kwb-ac60.mdx b/docs/devices-next/chargers/kathrein-kwb-ac60.mdx new file mode 100644 index 0000000000..32ddd6d8c0 --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC60 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC60 + + + +The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 + + + + +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx b/docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx deleted file mode 100644 index f2c26147a0..0000000000 --- a/docs/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: KEBA KeContact P20, P30, C/X Series -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# KEBA KeContact P20, P30, C/X Series - - - -Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. - - - - - - diff --git a/docs/devices-next/chargers/keba-kecontact-p20.mdx b/docs/devices-next/chargers/keba-kecontact-p20.mdx new file mode 100644 index 0000000000..7301934382 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p20.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P20 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P20 + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + + + diff --git a/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx b/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx new file mode 100644 index 0000000000..6410bab519 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P30 C-Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P30 C-Series + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + + + diff --git a/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx b/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx new file mode 100644 index 0000000000..52d72e8e56 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P30 X-Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P30 X-Series + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + + + diff --git a/docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx b/docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx deleted file mode 100644 index 8e5be0fabf..0000000000 --- a/docs/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: KEBA KeContact P40, P40 Pro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# KEBA KeContact P40, P40 Pro - - - -Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. - - - - - - diff --git a/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx b/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx new file mode 100644 index 0000000000..d7ac2d398d --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P40 Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P40 Pro + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + + + diff --git a/docs/devices-next/chargers/keba-kecontact-p40.mdx b/docs/devices-next/chargers/keba-kecontact-p40.mdx new file mode 100644 index 0000000000..81c51f3c59 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p40.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P40 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P40 + + + +Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. + + + + +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + + + diff --git a/docs/devices-next/chargers/kermi-x-center-pro.mdx b/docs/devices-next/chargers/kermi-x-center-pro.mdx index d6d6d8f5d4..2834b37c66 100644 --- a/docs/devices-next/chargers/kermi-x-center-pro.mdx +++ b/docs/devices-next/chargers/kermi-x-center-pro.mdx @@ -1,6 +1,7 @@ --- title: Kermi x-center pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,11 @@ import TabItem from '@theme/TabItem'; tempsource: # Temperature source, [warmwater, buffer] (optional) watchdog: 60s # optional`} /> +## Template Parameter `kermi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/chargers/kontron-solar-charger.mdx b/docs/devices-next/chargers/kontron-solar-charger.mdx index bc62f59708..f4b6d66b2a 100644 --- a/docs/devices-next/chargers/kontron-solar-charger.mdx +++ b/docs/devices-next/chargers/kontron-solar-charger.mdx @@ -1,6 +1,7 @@ --- title: Kontron Solar Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `ghost` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/kostal-enector.mdx b/docs/devices-next/chargers/kostal-enector.mdx index 4142b5b186..dd1104969b 100644 --- a/docs/devices-next/chargers/kostal-enector.mdx +++ b/docs/devices-next/chargers/kostal-enector.mdx @@ -1,6 +1,7 @@ --- title: Kostal Enector custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,5 +37,11 @@ For Kostal systems with Smart Energy Meter (KSEM), the additional activation cod host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `mennekes-compact` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/kse-wbx16.mdx b/docs/devices-next/chargers/kse-wbx16.mdx index 0dfbe570c2..6615040b3f 100644 --- a/docs/devices-next/chargers/kse-wbx16.mdx +++ b/docs/devices-next/chargers/kse-wbx16.mdx @@ -1,6 +1,7 @@ --- title: KSE wBX16 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,5 +32,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `kse` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx b/docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx deleted file mode 100644 index eb53e26083..0000000000 --- a/docs/devices-next/chargers/ladefoxx-evload-mikro-20.mdx +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: LadeFoxx EvLoad, Mikro 2.0 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# LadeFoxx EvLoad, Mikro 2.0 - - - -1 loadpoint), optional`} /> - diff --git a/docs/devices-next/chargers/ladefoxx-evload.mdx b/docs/devices-next/chargers/ladefoxx-evload.mdx new file mode 100644 index 0000000000..77f94ad9c4 --- /dev/null +++ b/docs/devices-next/chargers/ladefoxx-evload.mdx @@ -0,0 +1,44 @@ +--- +title: LadeFoxx EvLoad +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LadeFoxx EvLoad + + + +1 loadpoint), optional`} /> + +## Template Parameter `phoenix-charx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx b/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx new file mode 100644 index 0000000000..022ec2ecf9 --- /dev/null +++ b/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -0,0 +1,44 @@ +--- +title: LadeFoxx Mikro 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LadeFoxx Mikro 2.0 + + + +1 loadpoint), optional`} /> + +## Template Parameter `phoenix-charx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/lambda-eu-l-series.mdx b/docs/devices-next/chargers/lambda-eu-l-series.mdx index 86745e765d..86d580ab45 100644 --- a/docs/devices-next/chargers/lambda-eu-l-series.mdx +++ b/docs/devices-next/chargers/lambda-eu-l-series.mdx @@ -1,6 +1,7 @@ --- title: Lambda EU-L Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,11 @@ Energy management settings of the device: tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) watchdog: 60s # optional`} /> +## Template Parameter `lambda-zewotherm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Temperature source
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/chargers/lrt-home-essential.mdx b/docs/devices-next/chargers/lrt-home-essential.mdx deleted file mode 100644 index 30e92389a7..0000000000 --- a/docs/devices-next/chargers/lrt-home-essential.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: LRT HOME Essential+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# LRT HOME Essential+ - - - -The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. - - - - - - diff --git a/docs/devices-next/chargers/lrt-home-essentialplus.mdx b/docs/devices-next/chargers/lrt-home-essentialplus.mdx new file mode 100644 index 0000000000..b7ff0a40a1 --- /dev/null +++ b/docs/devices-next/chargers/lrt-home-essentialplus.mdx @@ -0,0 +1,45 @@ +--- +title: LRT HOME Essential+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LRT HOME Essential+ + + + +The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. + + + + +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/mennekes-amedio-professional.mdx b/docs/devices-next/chargers/mennekes-amedio-professional.mdx index 620f5b0c5f..3c01c8cc61 100644 --- a/docs/devices-next/chargers/mennekes-amedio-professional.mdx +++ b/docs/devices-next/chargers/mennekes-amedio-professional.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMEDIO Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx index 7e6f2715b9..42bb1cd509 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON 4Business 700 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The configuration option 'External Energy Management' must be enabled. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx index 127b00ed4f..337b9b178a 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON 4You 300 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,5 +37,11 @@ For Kostal systems with Smart Energy Meter (KSEM), the additional activation cod host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `mennekes-compact` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx index 6f9cdefcb9..d579ab3404 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON 4You 500 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The configuration option 'External Energy Management' must be enabled. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx index 01bd814290..f0debd43d4 100644 --- a/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON ChargeControl custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx b/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx new file mode 100644 index 0000000000..7531ae7980 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -0,0 +1,47 @@ +--- +title: Mennekes AMTRON Compact 2.0s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Compact 2.0s + + + +The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). +No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. +For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. + + + + +## Template Parameter `mennekes-compact` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx b/docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx deleted file mode 100644 index 33832b5df9..0000000000 --- a/docs/devices-next/chargers/mennekes-amtron-compact-20s.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Mennekes AMTRON Compact 2.0s -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Mennekes AMTRON Compact 2.0s - - - -The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). -No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. -For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. - - - - - - diff --git a/docs/devices-next/chargers/mennekes-amtron-premium.mdx b/docs/devices-next/chargers/mennekes-amtron-premium.mdx index 96b0d859a3..3f27a943ff 100644 --- a/docs/devices-next/chargers/mennekes-amtron-premium.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-premium.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON Premium custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `mennekes-hcc3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/mennekes-amtron-professional.mdx b/docs/devices-next/chargers/mennekes-amtron-professional.mdx index 4ee7f9931a..93eea7fd21 100644 --- a/docs/devices-next/chargers/mennekes-amtron-professional.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-professional.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/mennekes-amtron-xtra.mdx b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx index 4aa744660a..2695c36cac 100644 --- a/docs/devices-next/chargers/mennekes-amtron-xtra.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON Xtra custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `mennekes-hcc3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx index 8f68d6b9e8..0fa4fc1472 100644 --- a/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx +++ b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -1,6 +1,7 @@ --- title: Mennekes eMobility Gateway (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-mennekes-acu` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/mennekes-smart-acu.mdx b/docs/devices-next/chargers/mennekes-smart-acu.mdx index 4178279094..5349be7c8b 100644 --- a/docs/devices-next/chargers/mennekes-smart-acu.mdx +++ b/docs/devices-next/chargers/mennekes-smart-acu.mdx @@ -1,6 +1,7 @@ --- title: Mennekes Smart (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-mennekes-acu` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/mennekes-smart-t-acu.mdx b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx index 0373b0eb1e..9553f2e51a 100644 --- a/docs/devices-next/chargers/mennekes-smart-t-acu.mdx +++ b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -1,6 +1,7 @@ --- title: Mennekes Smart T (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-mennekes-acu` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx index e8831dd3ce..20463e5162 100644 --- a/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx +++ b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -1,6 +1,7 @@ --- title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-elwa-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port scale: 1 # Scale factor for power limit, optional`} /> +## Template Parameter `ac-elwa-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Scale factor for power limit
`scale` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx b/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx new file mode 100644 index 0000000000..fda3b9d4cd --- /dev/null +++ b/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -0,0 +1,39 @@ +--- +title: my-PV AC•THOR 9s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR 9s + + + + + +## Template Parameter `ac-thor` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Temperature sensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | no | +| Scale factor for power limit
`scale` | | Standard: `1` | no | + + + diff --git a/docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx b/docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx deleted file mode 100644 index 0a0cca3b32..0000000000 --- a/docs/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: my-PV AC THOR, AC THOR 9s -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# my-PV AC THOR, AC THOR 9s - - - - - - - diff --git a/docs/devices-next/chargers/my-pv-ac-thor.mdx b/docs/devices-next/chargers/my-pv-ac-thor.mdx new file mode 100644 index 0000000000..ef1549b477 --- /dev/null +++ b/docs/devices-next/chargers/my-pv-ac-thor.mdx @@ -0,0 +1,39 @@ +--- +title: my-PV AC•THOR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR + + + + + +## Template Parameter `ac-thor` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Temperature sensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | no | +| Scale factor for power limit
`scale` | | Standard: `1` | no | + + + diff --git a/docs/devices-next/chargers/mystrom-switch.mdx b/docs/devices-next/chargers/mystrom-switch.mdx index bfdd79a7ea..0f359e1b0b 100644 --- a/docs/devices-next/chargers/mystrom-switch.mdx +++ b/docs/devices-next/chargers/mystrom-switch.mdx @@ -1,6 +1,7 @@ --- title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mystrom.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `mystrom` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/nibe-ap-aw10.mdx b/docs/devices-next/chargers/nibe-ap-aw10.mdx new file mode 100644 index 0000000000..58d7aa1bf9 --- /dev/null +++ b/docs/devices-next/chargers/nibe-ap-aw10.mdx @@ -0,0 +1,50 @@ +--- +title: Nibe AP-AW10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nibe AP-AW10 + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/novelan-wpr-net.mdx b/docs/devices-next/chargers/novelan-wpr-net.mdx new file mode 100644 index 0000000000..be343aa505 --- /dev/null +++ b/docs/devices-next/chargers/novelan-wpr-net.mdx @@ -0,0 +1,50 @@ +--- +title: Novelan WPR NET +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Novelan WPR NET + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/nrgkick-connect.mdx b/docs/devices-next/chargers/nrgkick-connect.mdx index 98f4383cf0..5c9e0bd02b 100644 --- a/docs/devices-next/chargers/nrgkick-connect.mdx +++ b/docs/devices-next/chargers/nrgkick-connect.mdx @@ -1,6 +1,7 @@ --- -title: NRGKick Connect +title: NRGkick Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrgkick-connect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,7 +10,7 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# NRGKick Connect +# NRGkick Connect @@ -24,3 +25,11 @@ NRGkick charging unit via HTTP (older than 2022/2023) mac: password: # Password, Use single quotes in case of leading zeros`} /> +## Template Parameter `nrgkick-connect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| `mac` | | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | + diff --git a/docs/devices-next/chargers/nrgkick-gen2.mdx b/docs/devices-next/chargers/nrgkick-gen2.mdx index 214ba5b881..a006a6f774 100644 --- a/docs/devices-next/chargers/nrgkick-gen2.mdx +++ b/docs/devices-next/chargers/nrgkick-gen2.mdx @@ -1,6 +1,7 @@ --- -title: NRGKick Gen2 +title: NRGkick Gen2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrggen2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,7 +10,7 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# NRGKick Gen2 +# NRGkick Gen2 @@ -34,5 +35,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port phases1p3p: false # Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. (optional)`} /> +## Template Parameter `nrggen2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `phases1p3p` | Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. | | no | + diff --git a/docs/devices-next/chargers/obo-bettermann-ion.mdx b/docs/devices-next/chargers/obo-bettermann-ion.mdx index 229ff8177a..94b4125a6e 100644 --- a/docs/devices-next/chargers/obo-bettermann-ion.mdx +++ b/docs/devices-next/chargers/obo-bettermann-ion.mdx @@ -1,6 +1,7 @@ --- title: OBO Bettermann Ion custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `obo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx b/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx new file mode 100644 index 0000000000..c1e2561f29 --- /dev/null +++ b/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -0,0 +1,67 @@ +--- +title: OCPP 1.6J compatible (Smart Charging) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OCPP 1.6J compatible (Smart Charging) + + + +With OCPP the connection will be established from charger (client) to evcc (server). +The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. +By default, the first incoming connection with any station identifier is used. +In order to be able to clearly assign several charging points, the respective station identifier (`stationid: `) and connector number (`connector: `) must be configured. +Many wallboxes automatically add the `station id` to the backend URL, some have to do this manually `ws://:8887/`. +If the charger supports sending metering values, try to adjust the interval to a short time span (< 10s) . +Use your RFID tags (this allows e.g. vehicle identification) or set your charger to "free charging" or "autostart" to generate the transaction required for charging release. + +If the charger does not offer any option to start transactions locally, the `remotestart` advanced option can be used to automatically start a transaction as soon as a vehicle is connected. +This should only be necessary in exceptional cases. + +Requirements: +* If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration +* Backend URL (Central System) in the charger configuration: `ws://[evcc-adresse]:8887/` (possibly add `stationid`) +* Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar +* No encryption, no authentication, no password +* Local network connection + +The specific configuration and the actual usable functionality depend on the charger model and its software. + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx b/docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx deleted file mode 100644 index c9afc5e3e2..0000000000 --- a/docs/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: OCPP 1.6J compatible (Smart Charging) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# OCPP 1.6J compatible (Smart Charging) - - - -With OCPP the connection will be established from charger (client) to evcc (server). -The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. -By default, the first incoming connection with any station identifier is used. -In order to be able to clearly assign several charging points, the respective station identifier (`stationid: `) and connector number (`connector: `) must be configured. -Many wallboxes automatically add the `station id` to the backend URL, some have to do this manually `ws://:8887/`. -If the charger supports sending metering values, try to adjust the interval to a short time span (< 10s) . -Use your RFID tags (this allows e.g. vehicle identification) or set your charger to "free charging" or "autostart" to generate the transaction required for charging release. - -If the charger does not offer any option to start transactions locally, the `remotestart` advanced option can be used to automatically start a transaction as soon as a vehicle is connected. -This should only be necessary in exceptional cases. - -Requirements: -* If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration -* Backend URL (Central System) in the charger configuration: `ws://[evcc-adresse]:8887/` (possibly add `stationid`) -* Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar -* No encryption, no authentication, no password -* Local network connection - -The specific configuration and the actual usable functionality depend on the charger model and its software. - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/openevse.mdx b/docs/devices-next/chargers/openevse.mdx index 64af434add..8cba61c922 100644 --- a/docs/devices-next/chargers/openevse.mdx +++ b/docs/devices-next/chargers/openevse.mdx @@ -1,6 +1,7 @@ --- title: OpenEVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openevse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ Requires firmware 7.0 or later. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `openevse` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/openwb-pro.mdx b/docs/devices-next/chargers/openwb-pro.mdx index cf77c4efb5..1633e1facc 100644 --- a/docs/devices-next/chargers/openwb-pro.mdx +++ b/docs/devices-next/chargers/openwb-pro.mdx @@ -1,6 +1,7 @@ --- title: openWB Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-pro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: openwb-pro host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `openwb-pro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/openwb-series2.mdx b/docs/devices-next/chargers/openwb-series2.mdx index 835974275d..4a401ef868 100644 --- a/docs/devices-next/chargers/openwb-series2.mdx +++ b/docs/devices-next/chargers/openwb-series2.mdx @@ -1,6 +1,7 @@ --- title: openWB series2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,11 @@ The wallbox has to be configured as loadpoint. connector: 1 # Loadpoint (if >1 loadpoint), optional phases1p3p: false # Charger is equipped with phase switching feature, optional`} /> +## Template Parameter `openwb` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Charger is equipped with phase switching feature
`phases1p3p` | | | no | + diff --git a/docs/devices-next/chargers/openwb-software-2-x.mdx b/docs/devices-next/chargers/openwb-software-2-x.mdx new file mode 100644 index 0000000000..96fc608fc6 --- /dev/null +++ b/docs/devices-next/chargers/openwb-software-2-x.mdx @@ -0,0 +1,53 @@ +--- +title: openWB Software 2.x +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB Software 2.x + + + +Requires [`Software 2.x`](https://github.com/openWB/core). +The following changes are necessary under the 'Einstellungen' tab: + +* Steuerungsmodus: `secondary` +* Steuerung über Modbus als secondary: `An` + + +1 loadpoint), optional + phases1p3p: true # Charger is equipped with phase switching feature, optional`} /> + +## Template Parameter `openwb-2.0` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Charger is equipped with phase switching feature
`phases1p3p` | | Standard: `true` | no | + diff --git a/docs/devices-next/chargers/openwb-software-2x.mdx b/docs/devices-next/chargers/openwb-software-2x.mdx deleted file mode 100644 index 3b51269df8..0000000000 --- a/docs/devices-next/chargers/openwb-software-2x.mdx +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: openWB Software 2.x -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# openWB Software 2.x - - - -Requires [`Software 2.x`](https://github.com/openWB/core). -The following changes are necessary under the 'Einstellungen' tab: - -* Steuerungsmodus: `secondary` -* Steuerung über Modbus als secondary: `An` - - -1 loadpoint), optional - phases1p3p: true # Charger is equipped with phase switching feature, optional`} /> - diff --git a/docs/devices-next/chargers/optec-mobility-one.mdx b/docs/devices-next/chargers/optec-mobility-one.mdx index 6b0bee3b72..e93b74cb48 100644 --- a/docs/devices-next/chargers/optec-mobility-one.mdx +++ b/docs/devices-next/chargers/optec-mobility-one.mdx @@ -1,6 +1,7 @@ --- title: Optec Mobility One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/orbis-viaris.mdx b/docs/devices-next/chargers/orbis-viaris.mdx index 6c17a188a0..ba234cff82 100644 --- a/docs/devices-next/chargers/orbis-viaris.mdx +++ b/docs/devices-next/chargers/orbis-viaris.mdx @@ -1,6 +1,7 @@ --- title: Orbis Viaris custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-orbis.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-orbis` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/pc-electric-garo.mdx b/docs/devices-next/chargers/pc-electric-garo.mdx index b4b633622c..ea51373233 100644 --- a/docs/devices-next/chargers/pc-electric-garo.mdx +++ b/docs/devices-next/chargers/pc-electric-garo.mdx @@ -1,6 +1,7 @@ --- title: PC Electric Garo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pcelectric-garo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Only devices configured as master can be used right now! host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional`} /> +## Template Parameter `pcelectric-garo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `8080` | no | + diff --git a/docs/devices-next/chargers/peblar-business.mdx b/docs/devices-next/chargers/peblar-business.mdx new file mode 100644 index 0000000000..b12a8b61f7 --- /dev/null +++ b/docs/devices-next/chargers/peblar-business.mdx @@ -0,0 +1,38 @@ +--- +title: Peblar Business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Business + + + +Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. + + + + +## Template Parameter `peblar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/peblar-home-home-plus-business.mdx b/docs/devices-next/chargers/peblar-home-home-plus-business.mdx deleted file mode 100644 index 8680cfccbc..0000000000 --- a/docs/devices-next/chargers/peblar-home-home-plus-business.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Peblar Home, Home Plus, Business -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Peblar Home, Home Plus, Business - - - -Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. - - - - - - diff --git a/docs/devices-next/chargers/peblar-home-plus.mdx b/docs/devices-next/chargers/peblar-home-plus.mdx new file mode 100644 index 0000000000..44a1deefdf --- /dev/null +++ b/docs/devices-next/chargers/peblar-home-plus.mdx @@ -0,0 +1,38 @@ +--- +title: Peblar Home Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Home Plus + + + +Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. + + + + +## Template Parameter `peblar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/peblar-home.mdx b/docs/devices-next/chargers/peblar-home.mdx new file mode 100644 index 0000000000..1f4c00fdac --- /dev/null +++ b/docs/devices-next/chargers/peblar-home.mdx @@ -0,0 +1,38 @@ +--- +title: Peblar Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Home + + + +Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. + + + + +## Template Parameter `peblar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/phoenix-contact-charx.mdx b/docs/devices-next/chargers/phoenix-contact-charx.mdx index c3dee86377..540bdbbfb5 100644 --- a/docs/devices-next/chargers/phoenix-contact-charx.mdx +++ b/docs/devices-next/chargers/phoenix-contact-charx.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact CHARX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `phoenix-charx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx index a22dc03947..c9b0136e3a 100644 --- a/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx +++ b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EM-CP-PP-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-em-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-em-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx index 1cb5960aab..fefd5bfe6b 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx index 7abb20dca7..c64e9450a1 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx index 4a3f15b160..e2415ae806 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx index 6182d82ef9..8e87a768c9 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx index 1dce994e0f..aa935bdc46 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-SER custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-ser.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-ser` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/plugchoice.mdx b/docs/devices-next/chargers/plugchoice.mdx index 9f42589588..78bdbe5c6e 100644 --- a/docs/devices-next/chargers/plugchoice.mdx +++ b/docs/devices-next/chargers/plugchoice.mdx @@ -1,6 +1,7 @@ --- title: Plugchoice custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/plugchoice.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,5 +37,13 @@ These adjustments enable more frequent and detailed reporting of charging data t identity: # Charger identity (e.g. AA123456) connector: 1 # Loadpoint (if >1 loadpoint), Connector ID (usually 1)`} /> +## Template Parameter `plugchoice` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | API Token | | yes | +| `identity` | Charger identity (e.g. AA123456) | | yes | +| Loadpoint (if >1 loadpoint)
`connector` | Connector ID (usually 1) | Standard: `1` | yes | + diff --git a/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx index b527a29b6b..874a1ac216 100644 --- a/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx +++ b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Porsche Mobile Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,10 @@ import TabItem from '@theme/TabItem'; ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `pmcc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx index a95fa8f605..e5eb32f4fb 100644 --- a/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx +++ b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -1,6 +1,7 @@ --- title: Porsche Mobile Charger Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,10 @@ import TabItem from '@theme/TabItem'; ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `pmcp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/porsche-wallbox.mdx b/docs/devices-next/chargers/porsche-wallbox.mdx index ee24b4fe1d..f396beb7e3 100644 --- a/docs/devices-next/chargers/porsche-wallbox.mdx +++ b/docs/devices-next/chargers/porsche-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Porsche Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/porsche-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `porsche-wallbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/pracht-alpha-xt.mdx b/docs/devices-next/chargers/pracht-alpha-xt.mdx index 7484f59800..6479adc4b9 100644 --- a/docs/devices-next/chargers/pracht-alpha-xt.mdx +++ b/docs/devices-next/chargers/pracht-alpha-xt.mdx @@ -1,6 +1,7 @@ --- title: Pracht Alpha XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -62,5 +63,13 @@ import TabItem from '@theme/TabItem'; timeout: 10s # Timeout, optional connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `pracht-alpha` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/pracht-mono-xt.mdx b/docs/devices-next/chargers/pracht-mono-xt.mdx index ab4dc66a68..72728fef30 100644 --- a/docs/devices-next/chargers/pracht-mono-xt.mdx +++ b/docs/devices-next/chargers/pracht-mono-xt.mdx @@ -1,6 +1,7 @@ --- title: Pracht Mono XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -62,5 +63,13 @@ import TabItem from '@theme/TabItem'; timeout: 10s # Timeout, optional connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `pracht-alpha` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/pracht-pni.mdx b/docs/devices-next/chargers/pracht-pni.mdx index d32088d39e..2703128f98 100644 --- a/docs/devices-next/chargers/pracht-pni.mdx +++ b/docs/devices-next/chargers/pracht-pni.mdx @@ -1,6 +1,7 @@ --- title: Pracht PNI custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -62,5 +63,13 @@ import TabItem from '@theme/TabItem'; timeout: 10s # Timeout, optional connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +## Template Parameter `pracht-alpha` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + diff --git a/docs/devices-next/chargers/pracht-xt.mdx b/docs/devices-next/chargers/pracht-xt.mdx deleted file mode 100644 index 2a637437e4..0000000000 --- a/docs/devices-next/chargers/pracht-xt.mdx +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Pracht XT+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Pracht XT+ - - - -1 loadpoint), optional`} /> - - - diff --git a/docs/devices-next/chargers/pracht-xtplus.mdx b/docs/devices-next/chargers/pracht-xtplus.mdx new file mode 100644 index 0000000000..956cface67 --- /dev/null +++ b/docs/devices-next/chargers/pracht-xtplus.mdx @@ -0,0 +1,75 @@ +--- +title: Pracht XT+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht XT+ + + + +1 loadpoint), optional`} /> + +## Template Parameter `pracht-alpha` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | + + + diff --git a/docs/devices-next/chargers/pulsares-simplebox.mdx b/docs/devices-next/chargers/pulsares-simplebox.mdx index 4b9dbce34f..c06824dfac 100644 --- a/docs/devices-next/chargers/pulsares-simplebox.mdx +++ b/docs/devices-next/chargers/pulsares-simplebox.mdx @@ -1,6 +1,7 @@ --- title: Pulsares SimpleBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsares.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `pulsares` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/pulsatrix.mdx b/docs/devices-next/chargers/pulsatrix.mdx index f2668a3a2a..752e2dbe98 100644 --- a/docs/devices-next/chargers/pulsatrix.mdx +++ b/docs/devices-next/chargers/pulsatrix.mdx @@ -1,6 +1,7 @@ --- title: Pulsatrix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsatrix.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,5 +20,11 @@ import TabItem from '@theme/TabItem'; template: pulsatrix host: 192.0.2.2 # IP address or hostname, Shown on 3rd page of SECC display`} /> +## Template Parameter `pulsatrix` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | Shown on 3rd page of SECC display | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx b/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx new file mode 100644 index 0000000000..6e407efb07 --- /dev/null +++ b/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -0,0 +1,45 @@ +--- +title: Qcells Q.HOME EDRIVE A +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME EDRIVE A + + + +The charger must be in “Fast” mode and decoupled from the inverter system. + + + + +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/qcells-qhome-edrive-a.mdx b/docs/devices-next/chargers/qcells-qhome-edrive-a.mdx deleted file mode 100644 index 158eec5f10..0000000000 --- a/docs/devices-next/chargers/qcells-qhome-edrive-a.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Qcells Q.HOME EDRIVE A -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Qcells Q.HOME EDRIVE A - - - -The charger must be in “Fast” mode and decoupled from the inverter system. - - - - - - diff --git a/docs/devices-next/chargers/roth-thermoaura.mdx b/docs/devices-next/chargers/roth-thermoaura.mdx new file mode 100644 index 0000000000..964f80de3d --- /dev/null +++ b/docs/devices-next/chargers/roth-thermoaura.mdx @@ -0,0 +1,50 @@ +--- +title: Roth ThermoAura +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Roth ThermoAura + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/roth-thermoterra.mdx b/docs/devices-next/chargers/roth-thermoterra.mdx new file mode 100644 index 0000000000..c7c060d312 --- /dev/null +++ b/docs/devices-next/chargers/roth-thermoterra.mdx @@ -0,0 +1,50 @@ +--- +title: Roth ThermoTerra +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Roth ThermoTerra + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/schneider-evlink-pro.mdx b/docs/devices-next/chargers/schneider-evlink-pro.mdx index 46e0ecba3f..86dcff93b8 100644 --- a/docs/devices-next/chargers/schneider-evlink-pro.mdx +++ b/docs/devices-next/chargers/schneider-evlink-pro.mdx @@ -1,6 +1,7 @@ --- title: Schneider EVlink Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/schneider-evlink-v3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `schneider-evlink-v3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/schrack-i-charge-cion.mdx b/docs/devices-next/chargers/schrack-i-charge-cion.mdx index 823e8052be..cbde9b5903 100644 --- a/docs/devices-next/chargers/schrack-i-charge-cion.mdx +++ b/docs/devices-next/chargers/schrack-i-charge-cion.mdx @@ -1,6 +1,7 @@ --- title: Schrack i-CHARGE CION custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `ichargecion` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/senec-wallbox-pro-s.mdx b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx index 3d5c3cd5fe..4b05c78413 100644 --- a/docs/devices-next/chargers/senec-wallbox-pro-s.mdx +++ b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -1,6 +1,7 @@ --- title: SENEC Wallbox pro s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Please read the wiring and configuration manual carefully. All boxes must be con host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/senec-wallbox-pro.mdx b/docs/devices-next/chargers/senec-wallbox-pro.mdx index 9c71e1864d..670a84ffef 100644 --- a/docs/devices-next/chargers/senec-wallbox-pro.mdx +++ b/docs/devices-next/chargers/senec-wallbox-pro.mdx @@ -1,6 +1,7 @@ --- title: SENEC Wallbox pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port timeout: 10s # Timeout, optional`} /> +## Template Parameter `abl` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | + diff --git a/docs/devices-next/chargers/shelly-1.mdx b/docs/devices-next/chargers/shelly-1.mdx new file mode 100644 index 0000000000..b8d8027117 --- /dev/null +++ b/docs/devices-next/chargers/shelly-1.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly 1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1 + + + + + +## Template Parameter `shelly` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/shelly-plug-s.mdx b/docs/devices-next/chargers/shelly-plug-s.mdx new file mode 100644 index 0000000000..4dbd9ac452 --- /dev/null +++ b/docs/devices-next/chargers/shelly-plug-s.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly Plug S +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Plug S + + + + + +## Template Parameter `shelly` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/shelly-plus-1.mdx b/docs/devices-next/chargers/shelly-plus-1.mdx new file mode 100644 index 0000000000..1dbbf6b80e --- /dev/null +++ b/docs/devices-next/chargers/shelly-plus-1.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly Plus 1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Plus 1 + + + + + +## Template Parameter `shelly` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/shelly-pro-1.mdx b/docs/devices-next/chargers/shelly-pro-1.mdx new file mode 100644 index 0000000000..36b39b7aa5 --- /dev/null +++ b/docs/devices-next/chargers/shelly-pro-1.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly Pro 1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 1 + + + + + +## Template Parameter `shelly` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/shelly.mdx b/docs/devices-next/chargers/shelly.mdx deleted file mode 100644 index dc26ad8ed6..0000000000 --- a/docs/devices-next/chargers/shelly.mdx +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Shelly -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Shelly - - - - - diff --git a/docs/devices-next/chargers/siemens-versicharge-gen3.mdx b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx index b740df3281..b7b16215ac 100644 --- a/docs/devices-next/chargers/siemens-versicharge-gen3.mdx +++ b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -1,6 +1,7 @@ --- title: Siemens Versicharge GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/versicharge.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Requires firmware >= 2.135 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `versicharge` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/skoda-charger-connect.mdx b/docs/devices-next/chargers/skoda-charger-connect.mdx index 0d74b6386b..4119e22ae4 100644 --- a/docs/devices-next/chargers/skoda-charger-connect.mdx +++ b/docs/devices-next/chargers/skoda-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Skoda Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx index 7e6f2eca75..bdf917be2b 100644 --- a/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx +++ b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -1,6 +1,7 @@ --- title: Skoda Charger Pro Eichrecht custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/skoda-charger-pro.mdx b/docs/devices-next/chargers/skoda-charger-pro.mdx index 9cdf03b1cb..ddae605919 100644 --- a/docs/devices-next/chargers/skoda-charger-pro.mdx +++ b/docs/devices-next/chargers/skoda-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Skoda Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/skoda-iv-charger-connect.mdx b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx index fe7ec34cee..18c2ab9e42 100644 --- a/docs/devices-next/chargers/skoda-iv-charger-connect.mdx +++ b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -1,6 +1,7 @@ --- -title: Skoda iV Charger Connect+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +title: Skoda iV Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,7 +10,7 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# Skoda iV Charger Connect+ +# Skoda iV Charger Connect @@ -17,13 +18,22 @@ The device has to have a fix IP address (manuall or via DHCP). The identification of a vehicle using the RFID card is not possible. -Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. +## Template Parameter `elliconnect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx b/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx new file mode 100644 index 0000000000..6af9218dc1 --- /dev/null +++ b/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -0,0 +1,37 @@ +--- +title: Skoda iV Charger Connect+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda iV Charger Connect+ + + + +The device has to have a fix IP address (manuall or via DHCP). + +The identification of a vehicle using the RFID card is not possible. + +Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + + + +## Template Parameter `ellipro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/sma-echarger.mdx b/docs/devices-next/chargers/sma-echarger.mdx new file mode 100644 index 0000000000..249e77a6ac --- /dev/null +++ b/docs/devices-next/chargers/sma-echarger.mdx @@ -0,0 +1,37 @@ +--- +title: SMA eCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA eCharger + + + +The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. + + + + +## Template Parameter `smaevcharger` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | + + + diff --git a/docs/devices-next/chargers/sma-ev-charger-echarger.mdx b/docs/devices-next/chargers/sma-ev-charger-echarger.mdx deleted file mode 100644 index 9a9ecbbb1e..0000000000 --- a/docs/devices-next/chargers/sma-ev-charger-echarger.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: SMA EV Charger, eCharger -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA EV Charger, eCharger - - - -The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. - - - - - - diff --git a/docs/devices-next/chargers/sma-ev-charger.mdx b/docs/devices-next/chargers/sma-ev-charger.mdx new file mode 100644 index 0000000000..7e73d7c81c --- /dev/null +++ b/docs/devices-next/chargers/sma-ev-charger.mdx @@ -0,0 +1,37 @@ +--- +title: SMA EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA EV Charger + + + +The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. + + + + +## Template Parameter `smaevcharger` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | + + + diff --git a/docs/devices-next/chargers/smartfox-pro-charger.mdx b/docs/devices-next/chargers/smartfox-pro-charger.mdx index 61f6c01afe..d2864b80aa 100644 --- a/docs/devices-next/chargers/smartfox-pro-charger.mdx +++ b/docs/devices-next/chargers/smartfox-pro-charger.mdx @@ -1,6 +1,7 @@ --- title: Smartfox Pro Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `ichargecion` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/smartwb.mdx b/docs/devices-next/chargers/smartwb.mdx index b7fc1c9b65..f051492112 100644 --- a/docs/devices-next/chargers/smartwb.mdx +++ b/docs/devices-next/chargers/smartwb.mdx @@ -1,6 +1,7 @@ --- title: smartWB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartwb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: smartwb host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `smartwb` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/solaredge-home-ev-charger.mdx b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx index 569ed4870e..82d20c8754 100644 --- a/docs/devices-next/chargers/solaredge-home-ev-charger.mdx +++ b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -1,6 +1,7 @@ --- title: SolarEdge Home EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,12 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/chargers/solax-x3-evc.mdx b/docs/devices-next/chargers/solax-x3-evc.mdx index 0b93d79a4f..ef85206983 100644 --- a/docs/devices-next/chargers/solax-x3-evc.mdx +++ b/docs/devices-next/chargers/solax-x3-evc.mdx @@ -1,6 +1,7 @@ --- title: Solax X3-EVC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ The charger must be in “Fast” mode and decoupled from the inverter system. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/sonnen-sonnencharger.mdx b/docs/devices-next/chargers/sonnen-sonnencharger.mdx index 521a9c68a5..a9038918fc 100644 --- a/docs/devices-next/chargers/sonnen-sonnencharger.mdx +++ b/docs/devices-next/chargers/sonnen-sonnencharger.mdx @@ -1,6 +1,7 @@ --- title: Sonnen sonnenCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ The charger must be switched to "Power" charging mode. host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +## Template Parameter `etrel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | + diff --git a/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx index 057ec3a6a0..13fe2decb9 100644 --- a/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx +++ b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -1,6 +1,7 @@ --- title: Spelsberg Wallbox Smart Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/stark-in-strom-easy.mdx b/docs/devices-next/chargers/stark-in-strom-easy.mdx index 17e1380699..6cd3e22a5d 100644 --- a/docs/devices-next/chargers/stark-in-strom-easy.mdx +++ b/docs/devices-next/chargers/stark-in-strom-easy.mdx @@ -1,6 +1,7 @@ --- title: Stark in Strom Easy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `evse-din` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx new file mode 100644 index 0000000000..8761319b97 --- /dev/null +++ b/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -0,0 +1,35 @@ +--- +title: Stiebel Eltron LWA/LWZ (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stiebel Eltron LWA/LWZ (SG Ready) + + + + + +## Template Parameter `stiebel-lwa` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater` | no | + diff --git a/docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx deleted file mode 100644 index 5981a905f5..0000000000 --- a/docs/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Stiebel Eltron LWA/LWZ (SG Ready) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Stiebel Eltron LWA/LWZ (SG Ready) - - - - - diff --git a/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx index e3f028ce05..0d8f5f661c 100644 --- a/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx +++ b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Stiebel Eltron WPM (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-wpm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperature source, [warmwater, buffer] (optional)`} /> +## Template Parameter `stiebel-wpm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | + diff --git a/docs/devices-next/chargers/sungrow-ac011e-01.mdx b/docs/devices-next/chargers/sungrow-ac011e-01.mdx index 3ee7b944e7..09b1864d0c 100644 --- a/docs/devices-next/chargers/sungrow-ac011e-01.mdx +++ b/docs/devices-next/chargers/sungrow-ac011e-01.mdx @@ -1,6 +1,7 @@ --- title: Sungrow AC011E-01 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `sungrow` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/chargers/sungrow-ac011e.mdx b/docs/devices-next/chargers/sungrow-ac011e.mdx index 0085ad67d8..c3e9313490 100644 --- a/docs/devices-next/chargers/sungrow-ac011e.mdx +++ b/docs/devices-next/chargers/sungrow-ac011e.mdx @@ -1,6 +1,7 @@ --- title: Sungrow AC011E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-sungrow.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-sungrow` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/sungrow-ac22e-01.mdx b/docs/devices-next/chargers/sungrow-ac22e-01.mdx new file mode 100644 index 0000000000..1887815f9f --- /dev/null +++ b/docs/devices-next/chargers/sungrow-ac22e-01.mdx @@ -0,0 +1,48 @@ +--- +title: Sungrow AC22E-01 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow AC22E-01 + + + + + +## Template Parameter `sungrow` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/tasmota-single-phase.mdx b/docs/devices-next/chargers/tasmota-single-phase.mdx index d354fb6e01..8728520c3d 100644 --- a/docs/devices-next/chargers/tasmota-single-phase.mdx +++ b/docs/devices-next/chargers/tasmota-single-phase.mdx @@ -1,6 +1,7 @@ --- title: Tasmota single phase custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tasmota.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,16 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `tasmota` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | admin is default | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| Relaychannel number
`channel` | Relaychannel number (1-8) | Standard: `1` | yes | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx index 958dc68017..e994a0ac5f 100644 --- a/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx +++ b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Tecalor THZ (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperature source, [warmwater] (optional)`} /> +## Template Parameter `stiebel-lwa` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Temperature source
`tempsource` | | Auswahl: `warmwater` | no | + diff --git a/docs/devices-next/chargers/technisat-technivolt.mdx b/docs/devices-next/chargers/technisat-technivolt.mdx index 4b18531e82..8d3c8b09a5 100644 --- a/docs/devices-next/chargers/technisat-technivolt.mdx +++ b/docs/devices-next/chargers/technisat-technivolt.mdx @@ -1,6 +1,7 @@ --- title: TechniSat Technivolt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/tesla-twc3.mdx b/docs/devices-next/chargers/tesla-twc3.mdx deleted file mode 100644 index 5d35924b92..0000000000 --- a/docs/devices-next/chargers/tesla-twc3.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Tesla TWC3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Tesla TWC3 - - - -The TWC wallbox cannot be controlled directly. Control is via the vehicle. The vehicle must be selected at the TWC3 loadpoint. At this time only [Tesla vehicles](https://docs.evcc.io/en/docs/devices/vehicles#tesla) are supported. - - - - diff --git a/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx b/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx new file mode 100644 index 0000000000..531694529f --- /dev/null +++ b/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -0,0 +1,31 @@ +--- +title: Tesla Wall Connector (Gen 3) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla Wall Connector (Gen 3) + + + +The TWC wallbox cannot be controlled directly. Control is via the vehicle. The vehicle must be selected at the TWC3 loadpoint. At this time only [Tesla vehicles](https://docs.evcc.io/en/docs/devices/vehicles#tesla) are supported. + + + + +## Template Parameter `twc3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/tessie.mdx b/docs/devices-next/chargers/tessie.mdx index ee8d2a75f1..bdb8c5361d 100644 --- a/docs/devices-next/chargers/tessie.mdx +++ b/docs/devices-next/chargers/tessie.mdx @@ -1,6 +1,7 @@ --- title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tessie.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ Charger connected via the Tessie API. Allows control of charging state and confi token: # Tessie API Token location: tessiehome # Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive)`} /> +## Template Parameter `tessie` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Tessie API Token
`token` | | | yes | +| Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive)
`location` | | Beispiel: `tessiehome` | yes | + diff --git a/docs/devices-next/chargers/tigo-go-ev-charger.mdx b/docs/devices-next/chargers/tigo-go-ev-charger.mdx index 0cd12013c9..9aa7e6bce4 100644 --- a/docs/devices-next/chargers/tigo-go-ev-charger.mdx +++ b/docs/devices-next/chargers/tigo-go-ev-charger.mdx @@ -1,6 +1,7 @@ --- title: Tigo GO EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ The charger must be in “Fast” mode and decoupled from the inverter system. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx index 5103b14ee3..b65a191774 100644 --- a/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,15 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `tinkerforge-warp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | IP address or hostname of the MQTT broker | Beispiel: `192.0.2.2` | yes | +| Port
`port` | MQTT broker port | Standard: `1883` | no | +| Topic
`topic` | Topic (omit leading /) | Standard: `warp` | no | +| Timeout
`timeout` | Don't accept values older than this value | Standard: `30s`
Beispiel: `10s` | no | +| `energymanager` | WEM Firmware v2 required. EnergyManager MQTT topic (if installed) | | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx index 38276ada0d..c3e6b6552b 100644 --- a/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,15 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `tinkerforge-warp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | IP address or hostname of the MQTT broker | Beispiel: `192.0.2.2` | yes | +| Port
`port` | MQTT broker port | Standard: `1883` | no | +| Topic
`topic` | Topic (omit leading /) | Standard: `warp` | no | +| Timeout
`timeout` | Don't accept values older than this value | Standard: `30s`
Beispiel: `10s` | no | +| `energymanager` | WEM Firmware v2 required. EnergyManager MQTT topic (if installed) | | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx index 03878b054d..66da08e436 100644 --- a/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP3 Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,14 @@ The automatic phase switching for 1p vehicles must be deactivated. Siehe https:/ user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `tinkerforge-warp3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | IP address or hostname of the MQTT broker | Beispiel: `192.0.2.2` | yes | +| Port
`port` | MQTT broker port | Standard: `1883` | no | +| Topic
`topic` | Topic (omit leading /) | Standard: `warp` | no | +| Timeout
`timeout` | Don't accept values older than this value | Standard: `30s`
Beispiel: `10s` | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx index 74187543d4..ef4beccc09 100644 --- a/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP3 Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3-smart.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,14 @@ import TabItem from '@theme/TabItem'; user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `tinkerforge-warp3-smart` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | IP address or hostname of the MQTT broker | Beispiel: `192.0.2.2` | yes | +| Port
`port` | MQTT broker port | Standard: `1883` | no | +| Topic
`topic` | Topic (omit leading /) | Standard: `warp` | no | +| Timeout
`timeout` | Don't accept values older than this value | Standard: `30s`
Beispiel: `10s` | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx index 4aea80806c..178a110e5c 100644 --- a/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx +++ b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tplink.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `tplink` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx index 4dc26af931..7c0990d4a6 100644 --- a/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx +++ b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tapo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,15 @@ import TabItem from '@theme/TabItem'; heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Template Parameter `tapo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | +| Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | +| Heating device
`heating` | Shows °C instead of % | | no | +| Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | + diff --git a/docs/devices-next/chargers/ubitricity-heinz.mdx b/docs/devices-next/chargers/ubitricity-heinz.mdx index 34251b42fa..c3c23230ab 100644 --- a/docs/devices-next/chargers/ubitricity-heinz.mdx +++ b/docs/devices-next/chargers/ubitricity-heinz.mdx @@ -1,6 +1,7 @@ --- title: Ubitricity Heinz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/v2c-trydan.mdx b/docs/devices-next/chargers/v2c-trydan.mdx index cfd7e27643..f0c842d0f5 100644 --- a/docs/devices-next/chargers/v2c-trydan.mdx +++ b/docs/devices-next/chargers/v2c-trydan.mdx @@ -1,6 +1,7 @@ --- title: V2C Trydan custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/trydan.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,5 +23,11 @@ V2C trydan template: trydan host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `trydan` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx index 6837d1e4c8..1b8ae11ed4 100644 --- a/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx +++ b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Vaillant SensoNET (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vaillant.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,13 @@ The boost function heats hot water or a boost zone. The boost zone is identified zone: # Boost zone id (optional) setpoint: # Boost temperature setpoint (optional)`} /> +## Template Parameter `vaillant` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `realm` | | Standard: `DE`
Auswahl: `DE`, `AT` | no | +| `zone` | Boost zone id | | no | +| `setpoint` | Boost temperature setpoint | | no | + diff --git a/docs/devices-next/chargers/vestel-connect-plus.mdx b/docs/devices-next/chargers/vestel-connect-plus.mdx new file mode 100644 index 0000000000..2f86afc11b --- /dev/null +++ b/docs/devices-next/chargers/vestel-connect-plus.mdx @@ -0,0 +1,38 @@ +--- +title: Vestel Connect Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vestel Connect Plus + + + +1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. + + + + +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx b/docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx deleted file mode 100644 index b4017e6146..0000000000 --- a/docs/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Vestel EVC04 Home Smart, Connect Plus -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Vestel EVC04 Home Smart, Connect Plus - - - -1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. - - - - - - diff --git a/docs/devices-next/chargers/vestel-evc04-home-smart.mdx b/docs/devices-next/chargers/vestel-evc04-home-smart.mdx new file mode 100644 index 0000000000..f7ca16c065 --- /dev/null +++ b/docs/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -0,0 +1,38 @@ +--- +title: Vestel EVC04 Home Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vestel EVC04 Home Smart + + + +1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. + + + + +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx index cfdf9be1f6..f86e595ea2 100644 --- a/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx +++ b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -1,6 +1,7 @@ --- title: Victron EV Charging Station (via GX) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,9 @@ Enter the host of the GX device (not the charger). The charger has to be in manu host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `victron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/victron-ev-charging-station.mdx b/docs/devices-next/chargers/victron-ev-charging-station.mdx index 279b15ac6f..9d31dc2db0 100644 --- a/docs/devices-next/chargers/victron-ev-charging-station.mdx +++ b/docs/devices-next/chargers/victron-ev-charging-station.mdx @@ -1,6 +1,7 @@ --- title: Victron EV Charging Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron-evcs.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,9 @@ Enter the host of the charger (not the GX device) and ensure that the charger is host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `victron-evcs` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx index 6be19915df..63988debb1 100644 --- a/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx +++ b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Viessmann Heatpump (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/viessmann.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,7 +25,19 @@ One-time hot water preparation to a configurable target temperature. The device password: # Password, For the configured Viessmann account. clientid: # Client ID, Configure at [app.developer.viessmann.com](https://app.developer.viessmann.com) gateway_serial: # Gateway Serial, VitoConnect serial number (VitoCare App -> Settings -> Communication module -> Serial number) - installation_id: # Installation ID, Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...
Prerequisites: curl, jq, and the following parameters: \`\`\` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= \`\`\` Then execute the following (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): \`\`\` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" \`\`\` + installation_id: # Installation ID, Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...
Prerequisites: curl, jq, and the following parameters: \`\`\` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= \`\`\` Then execute the following to get an oauth token (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): \`\`\` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\\?code=\\(.*\\).*/\\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) \`\`\` Finally, get the installation id: \`\`\` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' \`\`\` device_id: 0 # Device ID, typically \`0\` target_temperature: 45 # Target temperature for one-time charge (°C), max. 60°C`} /> +## Template Parameter `viessmann` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | Register at \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | yes | +| Password
`password` | For the configured Viessmann account. | | yes | +| Client ID
`clientid` | Configure at \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | yes | +| Gateway Serial
`gateway_serial` | VitoConnect serial number (VitoCare App -> Settings -> Communication module -> Serial number) | | yes | +| Installation ID
`installation_id` | Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...<br/> Prerequisites: curl, jq, and the following parameters: ``` VIESSMANN_USER=<your-user> VIESSMANN_PASS=<your-password> VIESSMANN_CLIENT_ID=<your-clientid> ``` Then execute the following to get an oauth token (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ \| grep "^location: " \ \| sed 's/.*\?code=\(.*\).*/\1/' \ \| tr -d '\[:space:\]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE \| jq --raw-output .access_token) ``` Finally, get the installation id: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ \| jq '.data\[\].id' ``` | | yes | +| Device ID
`device_id` | typically `0` | | yes | +| Target temperature for one-time charge
`target_temperature` | max. 60°C | Standard: `45`
Einheit: °C | yes | + diff --git a/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx b/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx new file mode 100644 index 0000000000..3048b90aeb --- /dev/null +++ b/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -0,0 +1,46 @@ +--- +title: Viridian EV EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Viridian EV EVSE EPC 2.0 Plus + + + + + +## Template Parameter `obo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx b/docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx deleted file mode 100644 index 3325e35d37..0000000000 --- a/docs/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Viridian EV EVSE EPC 2.0 Plus -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Viridian EV EVSE EPC 2.0 Plus - - - - - diff --git a/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx index 5fb962f0d1..949650ab4f 100644 --- a/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx index 855460ed3e..34e11df6a2 100644 --- a/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx index cfb145ecd7..b7f6f4d36a 100644 --- a/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ The identification of a vehicle using the RFID card is not possible. ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elli-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx index 638ea822f1..e51560f21d 100644 --- a/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx +++ b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen ID. Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `elliconnect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx index 8a01e16e67..4f8c142913 100644 --- a/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx +++ b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen ID. Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Important: A mostly flawless functionality can only be provided with an external ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +## Template Parameter `ellipro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Subject Key Identifier (SKI)
`ski` | Usually found on the web interface of the wallbox | | yes | +| IP address
`ip` | | Beispiel: `192.0.2.2` | no | + diff --git a/docs/devices-next/chargers/volt-time-one.mdx b/docs/devices-next/chargers/volt-time-one.mdx index f713f15255..c26ebac84f 100644 --- a/docs/devices-next/chargers/volt-time-one.mdx +++ b/docs/devices-next/chargers/volt-time-one.mdx @@ -1,6 +1,7 @@ --- title: Volt Time One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Serial number (e.g. 1008621)`} /> +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| `serial_number` | Serial number (e.g. 1008621) | | yes | + diff --git a/docs/devices-next/chargers/volt-time-source-2.mdx b/docs/devices-next/chargers/volt-time-source-2.mdx index 6d9361f8bb..a29ea2922a 100644 --- a/docs/devices-next/chargers/volt-time-source-2.mdx +++ b/docs/devices-next/chargers/volt-time-source-2.mdx @@ -1,6 +1,7 @@ --- title: Volt Time Source 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Serial number (e.g. 1008621)`} /> +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| `serial_number` | Serial number (e.g. 1008621) | | yes | + diff --git a/docs/devices-next/chargers/volt-time-source-2s.mdx b/docs/devices-next/chargers/volt-time-source-2s.mdx index 840306719f..82d2dc0b1b 100644 --- a/docs/devices-next/chargers/volt-time-source-2s.mdx +++ b/docs/devices-next/chargers/volt-time-source-2s.mdx @@ -1,6 +1,7 @@ --- title: Volt Time Source 2s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Serial number (e.g. 1008621)`} /> +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| `serial_number` | Serial number (e.g. 1008621) | | yes | + diff --git a/docs/devices-next/chargers/volt-time-source.mdx b/docs/devices-next/chargers/volt-time-source.mdx index da5906e2df..b83e1fa8f9 100644 --- a/docs/devices-next/chargers/volt-time-source.mdx +++ b/docs/devices-next/chargers/volt-time-source.mdx @@ -1,6 +1,7 @@ --- title: Volt Time Source custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Serial number (e.g. 1008621)`} /> +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| `serial_number` | Serial number (e.g. 1008621) | | yes | + diff --git a/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx b/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx new file mode 100644 index 0000000000..e3af349fd2 --- /dev/null +++ b/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -0,0 +1,38 @@ +--- +title: Wallbe Eco 2.0(s) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Eco 2.0(s) + + + +DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. + + + + +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/wallbe-eco-20s.mdx b/docs/devices-next/chargers/wallbe-eco-20s.mdx deleted file mode 100644 index 0eec5dca5b..0000000000 --- a/docs/devices-next/chargers/wallbe-eco-20s.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Wallbe Eco 2.0(s) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Wallbe Eco 2.0(s) - - - -DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. - - - - - - diff --git a/docs/devices-next/chargers/wallbe-eco.mdx b/docs/devices-next/chargers/wallbe-eco.mdx index b457fa53e3..795742e957 100644 --- a/docs/devices-next/chargers/wallbe-eco.mdx +++ b/docs/devices-next/chargers/wallbe-eco.mdx @@ -1,6 +1,7 @@ --- title: Wallbe Eco custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/wallbe-pro.mdx b/docs/devices-next/chargers/wallbe-pro.mdx index da4b49eeb1..cdddaeecb1 100644 --- a/docs/devices-next/chargers/wallbe-pro.mdx +++ b/docs/devices-next/chargers/wallbe-pro.mdx @@ -1,6 +1,7 @@ --- title: Wallbe Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx new file mode 100644 index 0000000000..6871f0cbf2 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Commander 2 (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Commander 2 (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `wallbox-fw5` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx b/docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx deleted file mode 100644 index e9f2041b67..0000000000 --- a/docs/devices-next/chargers/wallbox-commander-2-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Commander 2 (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Commander 2 (FW 5.x) - - - -Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) -* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (local network connection) -* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* -* Password: leave empty - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/wallbox-commander-2.mdx b/docs/devices-next/chargers/wallbox-commander-2.mdx index f257f43bd6..a451eafb73 100644 --- a/docs/devices-next/chargers/wallbox-commander-2.mdx +++ b/docs/devices-next/chargers/wallbox-commander-2.mdx @@ -1,6 +1,7 @@ --- title: wallbox Commander 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-wallbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx new file mode 100644 index 0000000000..3bc8561a26 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Copper SB (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Copper SB (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `wallbox-fw5` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx b/docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx deleted file mode 100644 index efd7140aa7..0000000000 --- a/docs/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Copper SB (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Copper SB (FW 5.x) - - - -Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) -* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (local network connection) -* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* -* Password: leave empty - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/wallbox-copper-sb.mdx b/docs/devices-next/chargers/wallbox-copper-sb.mdx index a6d59c6f73..954d6c3e53 100644 --- a/docs/devices-next/chargers/wallbox-copper-sb.mdx +++ b/docs/devices-next/chargers/wallbox-copper-sb.mdx @@ -1,6 +1,7 @@ --- title: wallbox Copper SB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-wallbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx new file mode 100644 index 0000000000..93ef670c26 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Pulsar Max (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Max (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `wallbox-fw5` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx deleted file mode 100644 index fd8fd6e574..0000000000 --- a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Pulsar Max (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Pulsar Max (FW 5.x) - - - -Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) -* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (local network connection) -* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* -* Password: leave empty - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/wallbox-pulsar-max.mdx b/docs/devices-next/chargers/wallbox-pulsar-max.mdx index b0c82f209c..bda2f8702d 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-max.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-max.mdx @@ -1,6 +1,7 @@ --- title: wallbox Pulsar Max custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-wallbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx new file mode 100644 index 0000000000..b7c291c594 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Pulsar Plus (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Plus (FW 5.x) + + + +Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) +* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (local network connection) +* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* +* Password: leave empty + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `wallbox-fw5` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx deleted file mode 100644 index f26625c4d7..0000000000 --- a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Pulsar Plus (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Pulsar Plus (FW 5.x) - - - -Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) -* Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (local network connection) -* Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* -* Password: leave empty - - -:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> - - - diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx index 80d3b1ba3b..19a6590ed2 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-plus.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -1,6 +1,7 @@ --- title: wallbox Pulsar Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-wallbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx index c30691684b..929711dff7 100644 --- a/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx +++ b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -1,6 +1,7 @@ --- title: Walther Werke Basic Evo Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Please read the wiring and configuration manual carefully. All boxes must be con host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/webasto-live.mdx b/docs/devices-next/chargers/webasto-live.mdx index b7fcbe8395..fb3f01b17b 100644 --- a/docs/devices-next/chargers/webasto-live.mdx +++ b/docs/devices-next/chargers/webasto-live.mdx @@ -1,6 +1,7 @@ --- title: Webasto Live custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/webasto-next.mdx b/docs/devices-next/chargers/webasto-next.mdx index da12321ff5..5f0a909143 100644 --- a/docs/devices-next/chargers/webasto-next.mdx +++ b/docs/devices-next/chargers/webasto-next.mdx @@ -1,6 +1,7 @@ --- title: Webasto NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +## Template Parameter `webasto-next` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | + diff --git a/docs/devices-next/chargers/webasto-unite.mdx b/docs/devices-next/chargers/webasto-unite.mdx index ec59f0020e..462bcd20cc 100644 --- a/docs/devices-next/chargers/webasto-unite.mdx +++ b/docs/devices-next/chargers/webasto-unite.mdx @@ -1,6 +1,7 @@ --- title: Webasto Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/weidmuller-ac-smart.mdx b/docs/devices-next/chargers/weidmuller-ac-smart.mdx index f70dc919fa..31e485a5f5 100644 --- a/docs/devices-next/chargers/weidmuller-ac-smart.mdx +++ b/docs/devices-next/chargers/weidmuller-ac-smart.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller AC Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/weidmüller.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,5 +20,11 @@ import TabItem from '@theme/TabItem'; template: weidmüller host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `weidmüller` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/chargers/wolf-bwl.mdx b/docs/devices-next/chargers/wolf-bwl.mdx new file mode 100644 index 0000000000..7f1cef4437 --- /dev/null +++ b/docs/devices-next/chargers/wolf-bwl.mdx @@ -0,0 +1,50 @@ +--- +title: Wolf BWL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wolf BWL + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/wolf-bws.mdx b/docs/devices-next/chargers/wolf-bws.mdx new file mode 100644 index 0000000000..8be88939fd --- /dev/null +++ b/docs/devices-next/chargers/wolf-bws.mdx @@ -0,0 +1,50 @@ +--- +title: Wolf BWS +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wolf BWS + + + +For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | + diff --git a/docs/devices-next/chargers/zaptec-go-2.mdx b/docs/devices-next/chargers/zaptec-go-2.mdx index cd0fc3a973..6c25f11749 100644 --- a/docs/devices-next/chargers/zaptec-go-2.mdx +++ b/docs/devices-next/chargers/zaptec-go-2.mdx @@ -1,6 +1,7 @@ --- title: Zaptec Go 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,5 +22,13 @@ import TabItem from '@theme/TabItem'; user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `zaptec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `id` | Charger ID | | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/zaptec-go-ocpp.mdx b/docs/devices-next/chargers/zaptec-go-ocpp.mdx new file mode 100644 index 0000000000..d2b5c818bc --- /dev/null +++ b/docs/devices-next/chargers/zaptec-go-ocpp.mdx @@ -0,0 +1,51 @@ +--- +title: Zaptec Go (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-zaptec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Go (OCPP) + + + +OCPP Native mode + +https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-zaptec + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + +## Template Parameter `ocpp-zaptec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + + + diff --git a/docs/devices-next/chargers/zaptec-go.mdx b/docs/devices-next/chargers/zaptec-go.mdx index 62d22e899b..c8b6798eac 100644 --- a/docs/devices-next/chargers/zaptec-go.mdx +++ b/docs/devices-next/chargers/zaptec-go.mdx @@ -1,6 +1,7 @@ --- title: Zaptec Go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,5 +22,13 @@ import TabItem from '@theme/TabItem'; user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `zaptec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `id` | Charger ID | | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/zaptec-pro.mdx b/docs/devices-next/chargers/zaptec-pro.mdx index b4ffb2db1e..7d0097e0b2 100644 --- a/docs/devices-next/chargers/zaptec-pro.mdx +++ b/docs/devices-next/chargers/zaptec-pro.mdx @@ -1,6 +1,7 @@ --- title: Zaptec Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,5 +22,13 @@ import TabItem from '@theme/TabItem'; user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `zaptec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `id` | Charger ID | | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/chargers/zewotherm-eu-l-series.mdx b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx index 7627e86901..68faeed8b7 100644 --- a/docs/devices-next/chargers/zewotherm-eu-l-series.mdx +++ b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -1,6 +1,7 @@ --- title: Zewotherm EU-L Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,11 @@ Energy management settings of the device: tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) watchdog: 60s # optional`} /> +## Template Parameter `lambda-zewotherm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Temperature source
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx index 796d04b3c5..e7dff3d3db 100644 --- a/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx +++ b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -1,6 +1,7 @@ --- title: ZJ Beny BCP EV charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-beny.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> +## Template Parameter `ocpp-beny` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | +| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | +| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | +| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | +| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | +| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | + diff --git a/docs/devices-next/meters/a-tronix.mdx b/docs/devices-next/meters/a-tronix.mdx index 575b8ae48f..5bd3f06eb6 100644 --- a/docs/devices-next/meters/a-tronix.mdx +++ b/docs/devices-next/meters/a-tronix.mdx @@ -1,6 +1,7 @@ --- title: A-Tronix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `delay` | | Standard: `100ms` | no | + diff --git a/docs/devices-next/meters/abb-a43-a44-b23-b24.mdx b/docs/devices-next/meters/abb-a43-a44-b23-b24.mdx deleted file mode 100644 index f77804a0a1..0000000000 --- a/docs/devices-next/meters/abb-a43-a44-b23-b24.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: ABB A43, A44, B23, B24 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABB A43, A44, B23, B24 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/abb-a43.mdx b/docs/devices-next/meters/abb-a43.mdx new file mode 100644 index 0000000000..8420702774 --- /dev/null +++ b/docs/devices-next/meters/abb-a43.mdx @@ -0,0 +1,69 @@ +--- +title: ABB A43 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB A43 + + + + + + + + + + + + + + + + +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/abb-a44.mdx b/docs/devices-next/meters/abb-a44.mdx new file mode 100644 index 0000000000..197c339009 --- /dev/null +++ b/docs/devices-next/meters/abb-a44.mdx @@ -0,0 +1,69 @@ +--- +title: ABB A44 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB A44 + + + + + + + + + + + + + + + + +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/abb-b23.mdx b/docs/devices-next/meters/abb-b23.mdx new file mode 100644 index 0000000000..9a91918c24 --- /dev/null +++ b/docs/devices-next/meters/abb-b23.mdx @@ -0,0 +1,69 @@ +--- +title: ABB B23 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB B23 + + + + + + + + + + + + + + + + +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/abb-b24.mdx b/docs/devices-next/meters/abb-b24.mdx new file mode 100644 index 0000000000..c770606b63 --- /dev/null +++ b/docs/devices-next/meters/abb-b24.mdx @@ -0,0 +1,69 @@ +--- +title: ABB B24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB B24 + + + + + + + + + + + + + + + + +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx b/docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx deleted file mode 100644 index 7f7abf5af1..0000000000 --- a/docs/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Acrel ADW300 Wireless Metering Meter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Acrel ADW300 Wireless Metering Meter - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/acrel-adw300.mdx b/docs/devices-next/meters/acrel-adw300.mdx new file mode 100644 index 0000000000..bfcde75a1f --- /dev/null +++ b/docs/devices-next/meters/acrel-adw300.mdx @@ -0,0 +1,109 @@ +--- +title: Acrel ADW300 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Acrel ADW300 + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `acrel-adw300` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/ads-tec-storaxe.mdx b/docs/devices-next/meters/ads-tec-storaxe.mdx index e4494d8611..0ef2c118ce 100644 --- a/docs/devices-next/meters/ads-tec-storaxe.mdx +++ b/docs/devices-next/meters/ads-tec-storaxe.mdx @@ -1,6 +1,7 @@ --- title: Ads-tec StoraXe custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/storaxe.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port capacity: 50 # Battery capacity (kWh), optional`} /> +## Template Parameter `storaxe` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/alpha-ess-storion-smile.mdx b/docs/devices-next/meters/alpha-ess-storion-smile.mdx index 917d1ea264..f41518246f 100644 --- a/docs/devices-next/meters/alpha-ess-storion-smile.mdx +++ b/docs/devices-next/meters/alpha-ess-storion-smile.mdx @@ -1,6 +1,7 @@ --- title: Alpha ESS Storion SMILE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/alpha-ess-smile.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -180,3 +181,13 @@ To use active battery control, times for grid charging must be defined once via +## Template Parameter `alpha-ess-smile` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/ampere-ampere-storagepro.mdx b/docs/devices-next/meters/ampere-ampere-storagepro.mdx new file mode 100644 index 0000000000..326fd880b5 --- /dev/null +++ b/docs/devices-next/meters/ampere-ampere-storagepro.mdx @@ -0,0 +1,190 @@ +--- +title: Ampere Ampere.StoragePro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampere Ampere.StoragePro + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `saj-h2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | Standard: `2` | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | + diff --git a/docs/devices-next/meters/ampere-amperestoragepro.mdx b/docs/devices-next/meters/ampere-amperestoragepro.mdx deleted file mode 100644 index 6961a948db..0000000000 --- a/docs/devices-next/meters/ampere-amperestoragepro.mdx +++ /dev/null @@ -1,179 +0,0 @@ ---- -title: Ampere Ampere.StoragePro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Ampere Ampere.StoragePro - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/anker-micro-inverter.mdx b/docs/devices-next/meters/anker-micro-inverter.mdx index 440d80e22e..7de7993c55 100644 --- a/docs/devices-next/meters/anker-micro-inverter.mdx +++ b/docs/devices-next/meters/anker-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Anker Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `deye-mi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/apsystems-ez1.mdx b/docs/devices-next/meters/apsystems-ez1.mdx index a0acbca3db..b3dca8fe7c 100644 --- a/docs/devices-next/meters/apsystems-ez1.mdx +++ b/docs/devices-next/meters/apsystems-ez1.mdx @@ -1,6 +1,7 @@ --- title: APsystems EZ1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/apsystems-ez1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `apsystems-ez1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/avm-fritzdect.mdx b/docs/devices-next/meters/avm-fritzdect.mdx index 56e8148c14..faea2b05ea 100644 --- a/docs/devices-next/meters/avm-fritzdect.mdx +++ b/docs/devices-next/meters/avm-fritzdect.mdx @@ -1,6 +1,7 @@ --- title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fritzdect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,12 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `fritzdect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| URI
`uri` | HTTP(S) address | Standard: `https://fritz.box` | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Actor Identification Number (AIN)
`ain` | Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. | Beispiel: `307788992233` | yes | + diff --git a/docs/devices-next/meters/axitec-axihycon-12-15h.mdx b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx index fd0ece0833..f5d06f9984 100644 --- a/docs/devices-next/meters/axitec-axihycon-12-15h.mdx +++ b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -1,6 +1,7 @@ --- title: Axitec AXIhycon 12-15H custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -118,3 +119,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `solis-hybrid-s` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx index 43fa4c33b7..bf3b04f4e7 100644 --- a/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx +++ b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -1,6 +1,7 @@ --- title: Bernecker Engineering MPM3PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mpm3pm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `mpm3pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/bgetech-ds100.mdx b/docs/devices-next/meters/bgetech-ds100.mdx index 70a31f4e26..915f965238 100644 --- a/docs/devices-next/meters/bgetech-ds100.mdx +++ b/docs/devices-next/meters/bgetech-ds100.mdx @@ -1,6 +1,7 @@ --- title: BGEtech DS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ds100.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -128,3 +129,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `bge_tech_ds100` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/bgetech-ws100.mdx b/docs/devices-next/meters/bgetech-ws100.mdx index 3565b4d584..c5b053f643 100644 --- a/docs/devices-next/meters/bgetech-ws100.mdx +++ b/docs/devices-next/meters/bgetech-ws100.mdx @@ -1,6 +1,7 @@ --- title: BGEtech WS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ws100.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -128,3 +129,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `bge_tech_ws100` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx index ee7c21405c..944191f7fa 100644 --- a/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx +++ b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -1,6 +1,7 @@ --- title: Bosch BPT-S 5 Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bosch-bpt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `bosch-bpt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| URI
`uri` | HTTP(S) address | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/bosswerk-micro-inverter.mdx b/docs/devices-next/meters/bosswerk-micro-inverter.mdx index 3e097c9564..ef2b169802 100644 --- a/docs/devices-next/meters/bosswerk-micro-inverter.mdx +++ b/docs/devices-next/meters/bosswerk-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Bosswerk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `deye-mi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx b/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx new file mode 100644 index 0000000000..7911e5c143 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -0,0 +1,69 @@ +--- +title: Carlo Gavazzi EM110/111/112 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM110/111/112 + + + + + + + + + + + + + + + + +## Template Parameter `cg-emt1xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-em110111112.mdx b/docs/devices-next/meters/carlo-gavazzi-em110111112.mdx deleted file mode 100644 index 2c0f809f50..0000000000 --- a/docs/devices-next/meters/carlo-gavazzi-em110111112.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Carlo Gavazzi EM110/111/112 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM110/111/112 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/carlo-gavazzi-em24.mdx b/docs/devices-next/meters/carlo-gavazzi-em24.mdx index 0261a2cfa8..8bf71aa3e8 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em24.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em24.mdx @@ -1,6 +1,7 @@ --- title: Carlo Gavazzi EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -63,3 +64,9 @@ EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Etherne +## Template Parameter `cg-em24` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx b/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx new file mode 100644 index 0000000000..db5f10d056 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -0,0 +1,59 @@ +--- +title: Carlo Gavazzi EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM24_E1 + + + +EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. +The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + +## Template Parameter `cg-em24_e1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-em24e1.mdx b/docs/devices-next/meters/carlo-gavazzi-em24e1.mdx deleted file mode 100644 index 9deaa48d4c..0000000000 --- a/docs/devices-next/meters/carlo-gavazzi-em24e1.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Carlo Gavazzi EM24_E1 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM24_E1 - - - -EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. -The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx b/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx new file mode 100644 index 0000000000..f6d870c5c7 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -0,0 +1,81 @@ +--- +title: Carlo Gavazzi EM330/EM340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM330/EM340 + + + + + + + + + + + + + + + + +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-em330em340.mdx b/docs/devices-next/meters/carlo-gavazzi-em330em340.mdx deleted file mode 100644 index 40f8f37575..0000000000 --- a/docs/devices-next/meters/carlo-gavazzi-em330em340.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Carlo Gavazzi EM330/EM340 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM330/EM340 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx b/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx new file mode 100644 index 0000000000..1a23f424be --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -0,0 +1,81 @@ +--- +title: Carlo Gavazzi EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM530/EM540 + + + + + + + + + + + + + + + + +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-em530em540.mdx b/docs/devices-next/meters/carlo-gavazzi-em530em540.mdx deleted file mode 100644 index 3138e7897f..0000000000 --- a/docs/devices-next/meters/carlo-gavazzi-em530em540.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Carlo Gavazzi EM530/EM540 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM530/EM540 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/carlo-gavazzi-et112.mdx b/docs/devices-next/meters/carlo-gavazzi-et112.mdx index 03e0ba9f5d..b8b8a8b4ec 100644 --- a/docs/devices-next/meters/carlo-gavazzi-et112.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-et112.mdx @@ -1,6 +1,7 @@ --- title: Carlo Gavazzi ET112 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `cg-emt1xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx b/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx new file mode 100644 index 0000000000..561e9670f0 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -0,0 +1,81 @@ +--- +title: Carlo Gavazzi ET330/ET340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi ET330/ET340 + + + + + + + + + + + + + + + + +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/carlo-gavazzi-et330et340.mdx b/docs/devices-next/meters/carlo-gavazzi-et330et340.mdx deleted file mode 100644 index 487039c3ed..0000000000 --- a/docs/devices-next/meters/carlo-gavazzi-et330et340.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Carlo Gavazzi ET330/ET340 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi ET330/ET340 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/cfos-powerbrain-meter.mdx b/docs/devices-next/meters/cfos-powerbrain-meter.mdx index 4f8f0459bd..217b040d59 100644 --- a/docs/devices-next/meters/cfos-powerbrain-meter.mdx +++ b/docs/devices-next/meters/cfos-powerbrain-meter.mdx @@ -1,6 +1,7 @@ --- title: cFos PowerBrain Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cfos.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 4702 # Port`} /> +## Template Parameter `cfos` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/demo-battery.mdx b/docs/devices-next/meters/demo-battery.mdx index b65fe9a5e6..fe3c8928b6 100644 --- a/docs/devices-next/meters/demo-battery.mdx +++ b/docs/devices-next/meters/demo-battery.mdx @@ -1,6 +1,7 @@ --- title: Demo battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-battery.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,15 @@ For demonstration purposes. Battery with a fixed set of values. currentL2: # L2 current (A), optional currentL3: # L3 current (A), optional`} /> +## Template Parameter `demo-battery` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Power
`power` | | Einheit: W | no | +| Charge
`soc` | | Einheit: % | no | +| Controllable
`controllable` | Supports active battery control | | no | +| Meter reading
`energy` | | Einheit: kWh | no | +| L1 current
`currentL1` | | Einheit: A | no | +| L2 current
`currentL2` | | Einheit: A | no | +| L3 current
`currentL3` | | Einheit: A | no | + diff --git a/docs/devices-next/meters/demo-meter.mdx b/docs/devices-next/meters/demo-meter.mdx index 4e4c525ecc..e1ab7b065c 100644 --- a/docs/devices-next/meters/demo-meter.mdx +++ b/docs/devices-next/meters/demo-meter.mdx @@ -1,6 +1,7 @@ --- title: Demo meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -95,3 +96,13 @@ For demonstration purposes. Meter with a fixed set of values. +## Template Parameter `demo-meter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Power
`power` | | Einheit: W | no | +| Meter reading
`energy` | | Einheit: kWh | no | +| L1 current
`currentL1` | | Einheit: A | no | +| L2 current
`currentL2` | | Einheit: A | no | +| L3 current
`currentL3` | | Einheit: A | no | + diff --git a/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx index a933df3bdd..1d1dcc05c6 100644 --- a/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `deye-hybrid-3p` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx index d28f600321..cd614552a9 100644 --- a/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -183,3 +184,15 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `deye-hybrid-hp3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| `storageunit` | | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Treat GEN port as solar input
`includegenport` | | | no | + diff --git a/docs/devices-next/meters/deye-micro-inverter.mdx b/docs/devices-next/meters/deye-micro-inverter.mdx index ecdbcc3b76..92c6da2bdc 100644 --- a/docs/devices-next/meters/deye-micro-inverter.mdx +++ b/docs/devices-next/meters/deye-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `deye-mi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx index 1e91b51b28..effd2280e3 100644 --- a/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `deye-storage` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/deye-string-inverter.mdx b/docs/devices-next/meters/deye-string-inverter.mdx index a2c6861fe6..1e7c364a27 100644 --- a/docs/devices-next/meters/deye-string-inverter.mdx +++ b/docs/devices-next/meters/deye-string-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `deye-string` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/discovergy.mdx b/docs/devices-next/meters/discovergy.mdx index 9465b60a25..bcd47cf323 100644 --- a/docs/devices-next/meters/discovergy.mdx +++ b/docs/devices-next/meters/discovergy.mdx @@ -1,6 +1,7 @@ --- title: Discovergy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/discovergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,3 +41,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `discovergy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| `meter` | | Beispiel: `1ESY1161229886` | yes | + diff --git a/docs/devices-next/meters/dsmr.mdx b/docs/devices-next/meters/dsmr.mdx index 626d791b0f..71d889bb34 100644 --- a/docs/devices-next/meters/dsmr.mdx +++ b/docs/devices-next/meters/dsmr.mdx @@ -1,6 +1,7 @@ --- title: DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dsmr.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,11 @@ import TabItem from '@theme/TabItem'; port: 1502 # Port, optional energy: # OBIS code for energy consumption, Typically 1-0:1.8.0 or 1-0:1.8.1/1-0:1.8.2 with multiple tariffs (optional)`} /> +## Template Parameter `dsmr` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `1502` | no | +| OBIS code for energy consumption
`energy` | Typically 1-0:1.8.0 or 1-0:1.8.1/1-0:1.8.2 with multiple tariffs | | no | + diff --git a/docs/devices-next/meters/dzg-dvh4013.mdx b/docs/devices-next/meters/dzg-dvh4013.mdx index 2aa2c5fae7..fd9eff1eb9 100644 --- a/docs/devices-next/meters/dzg-dvh4013.mdx +++ b/docs/devices-next/meters/dzg-dvh4013.mdx @@ -1,6 +1,7 @@ --- title: DZG DVH4013 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dzg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `dzg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/e3-dc.mdx b/docs/devices-next/meters/e3-dc.mdx new file mode 100644 index 0000000000..5ef572189b --- /dev/null +++ b/docs/devices-next/meters/e3-dc.mdx @@ -0,0 +1,111 @@ +--- +title: E3/DC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC + + + +Username and password are identical to Web Portal or My E3/DC App access. Key (=RSCP-Password) must be set in the E3/DC system at Personalize/User Profile. The IP adresses of evcc and E3/DC system must be in the same subnet. + +**Note**: Active battery control will override Smart-Power/Operating Range settings. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `e3dc-rscp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `5033` | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| `key` | | | yes | +| Discharge limit in W
`dischargelimit` | Limits discharge power in 'Hold' battery mode | | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/e3dc.mdx b/docs/devices-next/meters/e3dc.mdx deleted file mode 100644 index ab879e5e70..0000000000 --- a/docs/devices-next/meters/e3dc.mdx +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: E3/DC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E3/DC - - - -Username and password are identical to Web Portal or My E3/DC App access. Key (=RSCP-Password) must be set in the E3/DC system at Personalize/User Profile. The IP adresses of evcc and E3/DC system must be in the same subnet. - -**Note**: Active battery control will override Smart-Power/Operating Range settings. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/eastron-sdm120-modbus.mdx b/docs/devices-next/meters/eastron-sdm120-modbus.mdx index 89196e71b9..bf6c21cc9d 100644 --- a/docs/devices-next/meters/eastron-sdm120-modbus.mdx +++ b/docs/devices-next/meters/eastron-sdm120-modbus.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM120-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm120.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -82,3 +83,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron-sdm120` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/eastron-sdm220-230.mdx b/docs/devices-next/meters/eastron-sdm220-230.mdx new file mode 100644 index 0000000000..3ec38750b9 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm220-230.mdx @@ -0,0 +1,69 @@ +--- +title: Eastron SDM220/230 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM220/230 + + + + + + + + + + + + + + + + +## Template Parameter `eastron-sdm220_230` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/eastron-sdm220230.mdx b/docs/devices-next/meters/eastron-sdm220230.mdx deleted file mode 100644 index 01c6237991..0000000000 --- a/docs/devices-next/meters/eastron-sdm220230.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Eastron SDM220/230 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Eastron SDM220/230 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/eastron-sdm630-modbus.mdx b/docs/devices-next/meters/eastron-sdm630-modbus.mdx index c8c4de88e3..b86eab1fc8 100644 --- a/docs/devices-next/meters/eastron-sdm630-modbus.mdx +++ b/docs/devices-next/meters/eastron-sdm630-modbus.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM630-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/eastron-sdm72d-m.mdx b/docs/devices-next/meters/eastron-sdm72d-m.mdx index cd58bb9e71..8bea6fe9a3 100644 --- a/docs/devices-next/meters/eastron-sdm72d-m.mdx +++ b/docs/devices-next/meters/eastron-sdm72d-m.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM72D-M custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm72.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron-sdm72` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/eastron-sdm72dm-v2.mdx b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx index 6368042b3f..f197a07083 100644 --- a/docs/devices-next/meters/eastron-sdm72dm-v2.mdx +++ b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM72DM-V2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/enphase-iq-envoy.mdx b/docs/devices-next/meters/enphase-iq-envoy.mdx index 214fa28ccb..5be05d7273 100644 --- a/docs/devices-next/meters/enphase-iq-envoy.mdx +++ b/docs/devices-next/meters/enphase-iq-envoy.mdx @@ -1,6 +1,7 @@ --- title: Enphase IQ Envoy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/enphase.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -74,3 +75,12 @@ Only batteries of type "AC Battery" are currently supported by Enphase-API. +## Template Parameter `enphase` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| `token` | Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/esphome-dlms-meter-austria.mdx b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx index 903fac0bd9..acfa30d61b 100644 --- a/docs/devices-next/meters/esphome-dlms-meter-austria.mdx +++ b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -1,6 +1,7 @@ --- title: ESPHome DLMS Meter Austria custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/esphome-dlms-austria.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,10 @@ configured for Austrian DLMS meters. host: 192.0.2.2 # IP address or hostname timeout: 10s # Timeout, optional`} /> +## Template Parameter `esphome-dlms-austria` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Timeout
`timeout` | | Standard: `10s`
Beispiel: `10s` | no | + diff --git a/docs/devices-next/meters/esphome-dsmr.mdx b/docs/devices-next/meters/esphome-dsmr.mdx index 67a15d0e68..397c156ce4 100644 --- a/docs/devices-next/meters/esphome-dsmr.mdx +++ b/docs/devices-next/meters/esphome-dsmr.mdx @@ -1,6 +1,7 @@ --- title: ESPHome DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle`} /> +## Template Parameter `slimmelezer` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Scale factor
`scale` | Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle | Standard: `1000`
Beispiel: `1 \| 10 \| 100 \| 1000` | yes | + diff --git a/docs/devices-next/meters/fenecon.mdx b/docs/devices-next/meters/fenecon.mdx index 2b884218ac..b90cc9c79e 100644 --- a/docs/devices-next/meters/fenecon.mdx +++ b/docs/devices-next/meters/fenecon.mdx @@ -1,6 +1,7 @@ --- title: FENECON custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ A commercial license is required for FEMS FENECON systems for active battery con +## Template Parameter `openems` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Password
`password` | Use single quotes in case of leading zeros | Standard: `user` | no | +| `battery` | controllable battery component | Beispiel: `ess0` | no | +| `watchdog` | adjusted to the API timeout | Standard: `60s` | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx index 10ab1a56f7..81d88eccf2 100644 --- a/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: FoxESS H1 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `fox-ess-h1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx index cc9f33352e..807557c105 100644 --- a/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: FoxESS H3 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `fox-ess-h3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx index 1a1a3f17b2..ac8e5a156f 100644 --- a/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: FoxESS H3-Smart Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3-smart.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `fox-ess-h3-smart` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/fronius-ohmpilot.mdx b/docs/devices-next/meters/fronius-ohmpilot.mdx index c723d09994..ca7a992baf 100644 --- a/docs/devices-next/meters/fronius-ohmpilot.mdx +++ b/docs/devices-next/meters/fronius-ohmpilot.mdx @@ -1,6 +1,7 @@ --- title: Fronius Ohmpilot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-ohmpilot.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname key: 0 # ID of the Ohmpilot in SolarAPI, optional`} /> +## Template Parameter `fronius-ohmpilot` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| ID of the Ohmpilot in SolarAPI
`key` | | | no | + diff --git a/docs/devices-next/meters/fronius-primo-gen24-plus.mdx b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx index 06cbb41124..cf76c73bd7 100644 --- a/docs/devices-next/meters/fronius-primo-gen24-plus.mdx +++ b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -1,6 +1,7 @@ --- title: Fronius Primo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `fronius-gen24` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| `id` | Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). | Standard: `200` | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx index 2dd20b9c8d..987bc1734d 100644 --- a/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx +++ b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -1,6 +1,7 @@ --- title: Fronius Smartmeter (via Inverter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sunspec-meter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/fronius-solar-api-v1.mdx b/docs/devices-next/meters/fronius-solar-api-v1.mdx index 1968483c3e..d94426ebf8 100644 --- a/docs/devices-next/meters/fronius-solar-api-v1.mdx +++ b/docs/devices-next/meters/fronius-solar-api-v1.mdx @@ -1,6 +1,7 @@ --- title: Fronius Solar API V1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-solarapi-v1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -17,7 +18,7 @@ Solar API should only be used as fallback. Integration via Modbus is preferred. Username and password are only required for active battery control. -**Attention**: Active battery control should only be used if no other settings for time-dependent battery control were made in the inverter configuration under "Energy Management" - "Battery Management", as existing settings will be overwritten. +**Attention**: Active battery control should only be used if no other settings for time-dependent battery control were made in the inverter configuration under "Energy Management" - "Battery Management", as existing settings will be overwritten. Choose corresponding configuration URI! @@ -30,7 +31,15 @@ Username and password are only required for active battery control. usage: grid host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} /> + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} advanced={`meters: + - name: my_grid + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> @@ -42,7 +51,15 @@ Username and password are only required for active battery control. usage: pv host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} /> + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} advanced={`meters: + - name: my_pv + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> @@ -62,8 +79,19 @@ Username and password are only required for active battery control. host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - capacity: 50 # Battery capacity (kWh), optional`} /> + capacity: 50 # Battery capacity (kWh), optional + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> +## Template Parameter `fronius-solarapi-v1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username (for active battery control)
`user` | e.g. email address, user id, etc. | Standard: `customer` | no | +| Password (for active battery control)
`password` | Use single quotes in case of leading zeros | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Firmware starting with 1.36.5-1 require /api/config.
`batteryconfiguri` | | Standard: `/config`
Auswahl: `/config`, `/api/config` | no | + diff --git a/docs/devices-next/meters/fronius-symo-gen24-plus.mdx b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx index 8b2fee86e9..a83500687c 100644 --- a/docs/devices-next/meters/fronius-symo-gen24-plus.mdx +++ b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -1,6 +1,7 @@ --- title: Fronius Symo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `fronius-gen24` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| `id` | Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). | Standard: `200` | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx index 1cf1c61c77..9770d8e6d9 100644 --- a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -1,6 +1,7 @@ --- title: Ginlong Solis Hybrid Inverter (RHI series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -118,3 +119,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `solis-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx index e491558b99..c231f1dbfb 100644 --- a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -1,6 +1,7 @@ --- title: Ginlong Solis Hybrid Inverter (S Series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -118,3 +119,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `solis-hybrid-s` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/ginlong-solis-inverter.mdx b/docs/devices-next/meters/ginlong-solis-inverter.mdx index 2ea9f54b02..6d38692a2f 100644 --- a/docs/devices-next/meters/ginlong-solis-inverter.mdx +++ b/docs/devices-next/meters/ginlong-solis-inverter.mdx @@ -1,6 +1,7 @@ --- title: Ginlong Solis Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `solis` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/go-e-controller.mdx b/docs/devices-next/meters/go-e-controller.mdx index 7cb9c07265..abb32f8a4f 100644 --- a/docs/devices-next/meters/go-e-controller.mdx +++ b/docs/devices-next/meters/go-e-controller.mdx @@ -1,6 +1,7 @@ --- title: go-e Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/go-e-controller.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `go-e-controller` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx b/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx new file mode 100644 index 0000000000..aab18b6eae --- /dev/null +++ b/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -0,0 +1,165 @@ +--- +title: GoodWe ET/EH/BH/BT Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe ET/EH/BH/BT Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `goodwe-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip`, `udp` | no | +| `battery` | | Standard: `1`
Auswahl: `1`, `2` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx b/docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx deleted file mode 100644 index 71a3d1d055..0000000000 --- a/docs/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: GoodWe ET/EH/BH/BT Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# GoodWe ET/EH/BH/BT Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx index ea89fb96a6..347be75c10 100644 --- a/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx +++ b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -1,6 +1,7 @@ --- title: GoodWe GoodWe over Wifi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-wifi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `goodwe-wifi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`uri` | HTTP(S) address | | no | + diff --git a/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx b/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx new file mode 100644 index 0000000000..be940ae405 --- /dev/null +++ b/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -0,0 +1,47 @@ +--- +title: GoodWe SDT/DT Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe SDT/DT Inverter + + + + + +## Template Parameter `goodwe-dt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/goodwe-sdtdt-inverter.mdx b/docs/devices-next/meters/goodwe-sdtdt-inverter.mdx deleted file mode 100644 index 0809d0ea25..0000000000 --- a/docs/devices-next/meters/goodwe-sdtdt-inverter.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: GoodWe SDT/DT Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# GoodWe SDT/DT Inverter - - - - - diff --git a/docs/devices-next/meters/growatt-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-hybrid-inverter.mdx index 80c237c732..101e3c326b 100644 --- a/docs/devices-next/meters/growatt-hybrid-inverter.mdx +++ b/docs/devices-next/meters/growatt-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Growatt Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -154,3 +155,11 @@ The active battery control uses the first "Battery first" timeslot, so it cannot +## Template Parameter `growatt-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx new file mode 100644 index 0000000000..30246d9e41 --- /dev/null +++ b/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -0,0 +1,159 @@ +--- +title: Growatt TL-X(H) Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Growatt TL-X(H) Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `growatt-hybrid-tlxh` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx deleted file mode 100644 index bd80b22b42..0000000000 --- a/docs/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: Growatt TL-X(H) Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Growatt TL-X(H) Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/homematic-ip.mdx b/docs/devices-next/meters/homematic-ip.mdx index f7d4042c5a..c15d2d44fd 100644 --- a/docs/devices-next/meters/homematic-ip.mdx +++ b/docs/devices-next/meters/homematic-ip.mdx @@ -1,6 +1,7 @@ --- title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homematic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -88,3 +89,14 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `homematic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Device address/Serial number
`device` | Homematic device id like shown in the CCU web user interface. | Beispiel: `0001EE89AAD848` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1)
`meterchannel` | Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. | Standard: `6` | yes | +| XML-RPC api cache duration - Default 1s. (valid units are s,m,h)
`cache` | In case of duty cycle problems try a cache setting of 30s. | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/homewizard-kwh-meter.mdx b/docs/devices-next/meters/homewizard-kwh-meter.mdx index 5fa5226da4..87f8b6c3d7 100644 --- a/docs/devices-next/meters/homewizard-kwh-meter.mdx +++ b/docs/devices-next/meters/homewizard-kwh-meter.mdx @@ -1,6 +1,7 @@ --- title: HomeWizard kWh Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard-kwh.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `homewizard-kwh` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx index 3ccdd6bb8e..a6816f9ed4 100644 --- a/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx +++ b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -1,6 +1,7 @@ --- title: HomeWizard Wi-Fi P1 Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `homewizard` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx index fe4d31452e..b1f16136ed 100644 --- a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -1,6 +1,7 @@ --- title: Hoymiles HM & HMS Series (via AhoyDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-ahoydtu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname id: 0 # Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID], optional`} /> +## Template Parameter `hoymiles-ahoydtu` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #\[ID\]
`id` | | | no | + diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx index 002634479b..d406a1f428 100644 --- a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -1,6 +1,7 @@ --- title: Hoymiles HM & HMS Series (via OpenDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-opendtu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `hoymiles-opendtu` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/huawei-emma.mdx b/docs/devices-next/meters/huawei-emma.mdx index 32031c5d8d..3bfcc0d6c2 100644 --- a/docs/devices-next/meters/huawei-emma.mdx +++ b/docs/devices-next/meters/huawei-emma.mdx @@ -1,6 +1,7 @@ --- title: Huawei EMMA custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-emma.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `huawei-emma` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/huawei-smartlogger.mdx b/docs/devices-next/meters/huawei-smartlogger.mdx index c9ee4b2adb..68a56794ad 100644 --- a/docs/devices-next/meters/huawei-smartlogger.mdx +++ b/docs/devices-next/meters/huawei-smartlogger.mdx @@ -1,6 +1,7 @@ --- title: Huawei SmartLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-smartlogger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -102,3 +103,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `huawei-smartlogger` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | no | +| `storageunit` | | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/huawei-sun2000-sdongle.mdx b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx index 86b5ce911b..132329fbab 100644 --- a/docs/devices-next/meters/huawei-sun2000-sdongle.mdx +++ b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -1,6 +1,7 @@ --- title: Huawei SUN2000 (SDongle) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-dongle.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,10 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 port: 502 # Port timeout: 15s # Timeout, optional`} /> +## Template Parameter `huawei-dongle` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | no | + diff --git a/docs/devices-next/meters/huawei-sun2000.mdx b/docs/devices-next/meters/huawei-sun2000.mdx index f855498d80..1d14b6b223 100644 --- a/docs/devices-next/meters/huawei-sun2000.mdx +++ b/docs/devices-next/meters/huawei-sun2000.mdx @@ -1,6 +1,7 @@ --- title: Huawei SUN2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-sun2000.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -187,3 +188,15 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 +## Template Parameter `huawei-sun2000` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | no | +| `storageunit` | | Standard: `1` | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `10000`
Einheit: W | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Inverter cascade
`forceaccharging` | Keep AC charging active to charge the storage from other inverters via AC. Prevents stand-by. | | no | + diff --git a/docs/devices-next/meters/iammeter-wem3080.mdx b/docs/devices-next/meters/iammeter-wem3080.mdx index 6f46a62192..dfd5b5e65e 100644 --- a/docs/devices-next/meters/iammeter-wem3080.mdx +++ b/docs/devices-next/meters/iammeter-wem3080.mdx @@ -1,6 +1,7 @@ --- title: IAMMETER WEM3080 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -50,3 +51,9 @@ See https://www.iammeter.com/newsshow/net-energy-metering +## Template Parameter `iammeter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx b/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx new file mode 100644 index 0000000000..da56e4e3f3 --- /dev/null +++ b/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -0,0 +1,59 @@ +--- +title: IAMMETER WEM3080T/WEM3046T/WEM3050T +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IAMMETER WEM3080T/WEM3046T/WEM3050T + + + +3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. +See https://www.iammeter.com/newsshow/net-energy-metering + + + + + + + + + + + + + + + + + + + + +## Template Parameter `iammeter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx b/docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx deleted file mode 100644 index 12b5100e10..0000000000 --- a/docs/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: IAMMETER WEM3080T/WEM3046T/WEM3050T -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# IAMMETER WEM3080T/WEM3046T/WEM3050T - - - -3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. -See https://www.iammeter.com/newsshow/net-energy-metering - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/igen-tech-solarman-logger.mdx b/docs/devices-next/meters/igen-tech-solarman-logger.mdx index 8840cadc89..daa1532704 100644 --- a/docs/devices-next/meters/igen-tech-solarman-logger.mdx +++ b/docs/devices-next/meters/igen-tech-solarman-logger.mdx @@ -1,6 +1,7 @@ --- title: IGEN Tech Solarman Logger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarman.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; user: admin # Username, e.g. email address, user id, etc. (optional) password: admin # Password, Use single quotes in case of leading zeros (optional)`} /> +## Template Parameter `solarman` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | Standard: `admin` | no | +| Password
`password` | Use single quotes in case of leading zeros | Standard: `admin` | no | + diff --git a/docs/devices-next/meters/index.mdx b/docs/devices-next/meters/index.mdx index 5675b0f119..dae6e986c9 100644 --- a/docs/devices-next/meters/index.mdx +++ b/docs/devices-next/meters/index.mdx @@ -154,25 +154,58 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; /> + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/meters/inepro-pro380-mod.mdx b/docs/devices-next/meters/inepro-pro380-mod.mdx index ff07157d4a..8ea681d21a 100644 --- a/docs/devices-next/meters/inepro-pro380-mod.mdx +++ b/docs/devices-next/meters/inepro-pro380-mod.mdx @@ -1,6 +1,7 @@ --- title: inepro PRO380-MOD custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/inepro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `inepro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/iometer.mdx b/docs/devices-next/meters/iometer.mdx index dd0312178b..df733dad24 100644 --- a/docs/devices-next/meters/iometer.mdx +++ b/docs/devices-next/meters/iometer.mdx @@ -1,6 +1,7 @@ --- title: IOmeter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iometer.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP of your IOmeter`} /> +## Template Parameter `iometer` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP of your IOmeter
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/janitza-b-series-umg-series.mdx b/docs/devices-next/meters/janitza-b-series-umg-series.mdx deleted file mode 100644 index e997390c3c..0000000000 --- a/docs/devices-next/meters/janitza-b-series-umg-series.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Janitza B series, UMG series -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Janitza B series, UMG series - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/janitza-b-series.mdx b/docs/devices-next/meters/janitza-b-series.mdx new file mode 100644 index 0000000000..73c5706f3b --- /dev/null +++ b/docs/devices-next/meters/janitza-b-series.mdx @@ -0,0 +1,81 @@ +--- +title: Janitza B series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Janitza B series + + + + + + + + + + + + + + + + +## Template Parameter `janitza` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/janitza-umg-series.mdx b/docs/devices-next/meters/janitza-umg-series.mdx new file mode 100644 index 0000000000..1e931c79cd --- /dev/null +++ b/docs/devices-next/meters/janitza-umg-series.mdx @@ -0,0 +1,81 @@ +--- +title: Janitza UMG series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Janitza UMG series + + + + + + + + + + + + + + + + +## Template Parameter `janitza` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/keba-kecontact-e10.mdx b/docs/devices-next/meters/keba-kecontact-e10.mdx index 95a5cde714..fc357a1d76 100644 --- a/docs/devices-next/meters/keba-kecontact-e10.mdx +++ b/docs/devices-next/meters/keba-kecontact-e10.mdx @@ -1,6 +1,7 @@ --- title: KEBA KeContact E10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/keba-kecontact.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `keba-kecontact` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx index 175faa5299..e1a6dbbd6c 100644 --- a/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx +++ b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -1,6 +1,7 @@ --- title: Kostal Energy Meter C (KEM-C) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx index e41937076f..f95a1292c6 100644 --- a/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx +++ b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -1,6 +1,7 @@ --- title: Kostal Energy Meter P (KEM-P) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/kostal-piko-ba.mdx b/docs/devices-next/meters/kostal-piko-ba.mdx new file mode 100644 index 0000000000..3ee5dc67cf --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-ba.mdx @@ -0,0 +1,45 @@ +--- +title: Kostal Piko BA +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko BA + + + + + + + + + + + + + + + + +## Template Parameter `kostal-piko-pv` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/kostal-piko-hybrid.mdx b/docs/devices-next/meters/kostal-piko-hybrid.mdx index 54aeb380fd..7614400f55 100644 --- a/docs/devices-next/meters/kostal-piko-hybrid.mdx +++ b/docs/devices-next/meters/kostal-piko-hybrid.mdx @@ -1,6 +1,7 @@ --- title: Kostal Piko Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `kostal-piko-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/kostal-piko-legacy.mdx b/docs/devices-next/meters/kostal-piko-legacy.mdx index a828caff51..57179714a3 100644 --- a/docs/devices-next/meters/kostal-piko-legacy.mdx +++ b/docs/devices-next/meters/kostal-piko-legacy.mdx @@ -1,6 +1,7 @@ --- title: Kostal Piko (legacy) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-legacy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros`} /> +## Template Parameter `kostal-piko-legacy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | + diff --git a/docs/devices-next/meters/kostal-piko-mp-plus.mdx b/docs/devices-next/meters/kostal-piko-mp-plus.mdx index 5075b80f29..0975f5754d 100644 --- a/docs/devices-next/meters/kostal-piko-mp-plus.mdx +++ b/docs/devices-next/meters/kostal-piko-mp-plus.mdx @@ -1,6 +1,7 @@ --- title: Kostal Piko MP Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `kostal-piko-mp-plus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/kostal-piko-piko-ba.mdx b/docs/devices-next/meters/kostal-piko-piko-ba.mdx deleted file mode 100644 index 60d38e4df1..0000000000 --- a/docs/devices-next/meters/kostal-piko-piko-ba.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Kostal Piko, Piko BA -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Kostal Piko, Piko BA - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/kostal-piko.mdx b/docs/devices-next/meters/kostal-piko.mdx new file mode 100644 index 0000000000..69e0b21ede --- /dev/null +++ b/docs/devices-next/meters/kostal-piko.mdx @@ -0,0 +1,45 @@ +--- +title: Kostal Piko +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko + + + + + + + + + + + + + + + + +## Template Parameter `kostal-piko-pv` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx index eeb43849db..1d010b9c94 100644 --- a/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx +++ b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -1,6 +1,7 @@ --- title: Kostal Plenticore Hybrid, incl. grid charging of the house battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore-gen2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -78,3 +79,14 @@ _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ +## Template Parameter `kostal-plenticore-gen2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Endianness (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx index b677be849c..578b8f0d4e 100644 --- a/docs/devices-next/meters/kostal-plenticore-hybrid.mdx +++ b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -1,6 +1,7 @@ --- title: Kostal Plenticore Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -80,3 +81,15 @@ Only a single system may access the inverter! For active battery control the fun +## Template Parameter `kostal-plenticore` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Endianness (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx index a33a15612d..ad3250e277 100644 --- a/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx +++ b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -1,6 +1,7 @@ --- title: Kostal Smart Energy Meter (via inverter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,9 @@ The energy meter must be installed in sensor position 2 (grid connection). Senso host: 192.0.2.2 # Hostname port: 1502 # Port`} /> +## Template Parameter `kostal-ksem-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/kostal-smart-energy-meter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter.mdx index ef381a7bf3..d59b1fdd6c 100644 --- a/docs/devices-next/meters/kostal-smart-energy-meter.mdx +++ b/docs/devices-next/meters/kostal-smart-energy-meter.mdx @@ -1,6 +1,7 @@ --- title: Kostal Smart Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `kostal-ksem` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/lg-ess-home-15.mdx b/docs/devices-next/meters/lg-ess-home-15.mdx index 5a5c67f0be..605a7b6e1d 100644 --- a/docs/devices-next/meters/lg-ess-home-15.mdx +++ b/docs/devices-next/meters/lg-ess-home-15.mdx @@ -1,6 +1,7 @@ --- title: LG ESS Home 15 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-15.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -77,3 +78,14 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `lg-ess-home-15` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Password
`password` | User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. | | no | +| `registration` | Registration id of the LG ESS HOME inverter. | Beispiel: `DE200...` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | + diff --git a/docs/devices-next/meters/lg-ess-home-8-10.mdx b/docs/devices-next/meters/lg-ess-home-8-10.mdx new file mode 100644 index 0000000000..f3e9dec586 --- /dev/null +++ b/docs/devices-next/meters/lg-ess-home-8-10.mdx @@ -0,0 +1,94 @@ +--- +title: LG ESS Home 8/10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LG ESS Home 8/10 + + + +To use the battery control, a firmware version greater than or equal to 10.05.7433 / R2155 is required + + + + + + + + + + + + + + + + + + + + +## Template Parameter `lg-ess-home-8-10` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Password
`password` | User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. | | no | +| `registration` | Registration id of the LG ESS HOME inverter. | Beispiel: `DE200...` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | + diff --git a/docs/devices-next/meters/lg-ess-home-810.mdx b/docs/devices-next/meters/lg-ess-home-810.mdx deleted file mode 100644 index a1b72aeed6..0000000000 --- a/docs/devices-next/meters/lg-ess-home-810.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: LG ESS Home 8/10 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# LG ESS Home 8/10 - - - -To use the battery control, a firmware version greater than or equal to 10.05.7433 / R2155 is required - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/loxone-miniserver.mdx b/docs/devices-next/meters/loxone-miniserver.mdx index 61741fc010..05989cc6fd 100644 --- a/docs/devices-next/meters/loxone-miniserver.mdx +++ b/docs/devices-next/meters/loxone-miniserver.mdx @@ -1,6 +1,7 @@ --- title: Loxone Miniserver custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/loxone.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `loxone` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| Meter block
`meterblock` | Name from Loxone Config | | yes | +| Function block name for state of charge
`socblock` | Name from Loxone Config, only for battery | | no | + diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx index e80f29828c..c8cfbd5209 100644 --- a/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx +++ b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -1,6 +1,7 @@ --- title: M-TEC Energy Butler GEN2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -82,3 +83,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `mtec-eb-gen2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx index 38cf0bf105..7b2e369958 100644 --- a/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx +++ b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -1,6 +1,7 @@ --- title: M-TEC Energy Butler GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `mtec-eb-gen3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/marstek-venus-battery-storage.mdx b/docs/devices-next/meters/marstek-venus-battery-storage.mdx index 5e68739167..5ddde8b1c9 100644 --- a/docs/devices-next/meters/marstek-venus-battery-storage.mdx +++ b/docs/devices-next/meters/marstek-venus-battery-storage.mdx @@ -1,6 +1,7 @@ --- title: Marstek Venus Battery Storage custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/marstek-venus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -55,3 +56,14 @@ import TabItem from '@theme/TabItem'; maxchargepower: 2500 # Charge power in watts for Charge mode. 2500W is the maximum for Venus. (W), For forced charging of the battery. (optional) work_mode_normal: 1 # Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode., optional`} /> +## Template Parameter `marstek-venus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | Venus-E 5.12 kWh, Venus-C 2.56 kWh | Standard: `5.12`
Beispiel: `50`
Einheit: kWh | no | +| Venus can only be discharged down to 11%.
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `11`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `100`
Beispiel: `95`
Einheit: % | no | +| Charge power in watts for Charge mode. 2500W is the maximum for Venus.
`maxchargepower` | For forced charging of the battery. | Standard: `2500`
Einheit: W | no | +| Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode.
`work_mode_normal` | | Standard: `1` | no | + diff --git a/docs/devices-next/meters/mhendriks-p1-dongle.mdx b/docs/devices-next/meters/mhendriks-p1-dongle.mdx index 37377a34be..92918dd944 100644 --- a/docs/devices-next/meters/mhendriks-p1-dongle.mdx +++ b/docs/devices-next/meters/mhendriks-p1-dongle.mdx @@ -1,6 +1,7 @@ --- title: mhendriks P1 dongle custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle`} /> +## Template Parameter `slimmelezer` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Scale factor
`scale` | Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle | Standard: `1000`
Beispiel: `1 \| 10 \| 100 \| 1000` | yes | + diff --git a/docs/devices-next/meters/my-pv-ac-elwa-2.mdx b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx index 468cf368b4..f52c5ba6a9 100644 --- a/docs/devices-next/meters/my-pv-ac-elwa-2.mdx +++ b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -1,6 +1,7 @@ --- title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: aux host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `ac-elwa-2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/my-pv-ac-elwa-e.mdx b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx index acec8a304a..83a5a3d40b 100644 --- a/docs/devices-next/meters/my-pv-ac-elwa-e.mdx +++ b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -1,6 +1,7 @@ --- title: my-PV AC ELWA-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: aux host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `ac-elwa-e` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/my-pv-ac-thor.mdx b/docs/devices-next/meters/my-pv-ac-thor.mdx new file mode 100644 index 0000000000..c428ef23d3 --- /dev/null +++ b/docs/devices-next/meters/my-pv-ac-thor.mdx @@ -0,0 +1,29 @@ +--- +title: my-PV AC•THOR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR + + + + + +## Template Parameter `thor` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/my-pv-acthor.mdx b/docs/devices-next/meters/my-pv-acthor.mdx deleted file mode 100644 index 84c0712713..0000000000 --- a/docs/devices-next/meters/my-pv-acthor.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: my-PV AC•THOR -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# my-PV AC•THOR - - - - - diff --git a/docs/devices-next/meters/my-pv-wifi-meter.mdx b/docs/devices-next/meters/my-pv-wifi-meter.mdx index 50b9dea362..7c13006d33 100644 --- a/docs/devices-next/meters/my-pv-wifi-meter.mdx +++ b/docs/devices-next/meters/my-pv-wifi-meter.mdx @@ -1,6 +1,7 @@ --- title: my-PV WiFi Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mypv-wifi-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `mypv-wifi-meter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/mystrom-switch.mdx b/docs/devices-next/meters/mystrom-switch.mdx index af9907f637..5c992fb900 100644 --- a/docs/devices-next/meters/mystrom-switch.mdx +++ b/docs/devices-next/meters/mystrom-switch.mdx @@ -1,6 +1,7 @@ --- title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mystrom.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `mystrom` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/openems.mdx b/docs/devices-next/meters/openems.mdx index 41630a404f..7b91fc2297 100644 --- a/docs/devices-next/meters/openems.mdx +++ b/docs/devices-next/meters/openems.mdx @@ -1,6 +1,7 @@ --- title: OpenEMS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ A commercial license is required for FEMS FENECON systems for active battery con +## Template Parameter `openems` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Password
`password` | Use single quotes in case of leading zeros | Standard: `user` | no | +| `battery` | controllable battery component | Beispiel: `ess0` | no | +| `watchdog` | adjusted to the API timeout | Standard: `60s` | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/orno-or-we-516-or-we-517.mdx b/docs/devices-next/meters/orno-or-we-516-or-we-517.mdx deleted file mode 100644 index 2ff44ce2d6..0000000000 --- a/docs/devices-next/meters/orno-or-we-516-or-we-517.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Orno OR-WE-516, OR-WE-517 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Orno OR-WE-516, OR-WE-517 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/orno-or-we-516.mdx b/docs/devices-next/meters/orno-or-we-516.mdx new file mode 100644 index 0000000000..b65eedce7b --- /dev/null +++ b/docs/devices-next/meters/orno-or-we-516.mdx @@ -0,0 +1,69 @@ +--- +title: ORNO OR-WE-516 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ORNO OR-WE-516 + + + + + + + + + + + + + + + + +## Template Parameter `orno` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/orno-or-we-517.mdx b/docs/devices-next/meters/orno-or-we-517.mdx new file mode 100644 index 0000000000..d75a04e510 --- /dev/null +++ b/docs/devices-next/meters/orno-or-we-517.mdx @@ -0,0 +1,69 @@ +--- +title: ORNO OR-WE-517 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ORNO OR-WE-517 + + + + + + + + + + + + + + + + +## Template Parameter `orno` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/p1monitor-p1-monitor.mdx b/docs/devices-next/meters/p1monitor-p1-monitor.mdx new file mode 100644 index 0000000000..6fe2036cf0 --- /dev/null +++ b/docs/devices-next/meters/p1monitor-p1-monitor.mdx @@ -0,0 +1,29 @@ +--- +title: P1Monitor P1 Monitor +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# P1Monitor P1 Monitor + + + + + +## Template Parameter `p1monitor` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/p1monitor.mdx b/docs/devices-next/meters/p1monitor.mdx deleted file mode 100644 index d56dfbd294..0000000000 --- a/docs/devices-next/meters/p1monitor.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: P1Monitor P1 Monitor -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# P1Monitor P1 Monitor - - - - - diff --git a/docs/devices-next/meters/plexlog.mdx b/docs/devices-next/meters/plexlog.mdx index 269d0fd2b4..dd0f27e0e0 100644 --- a/docs/devices-next/meters/plexlog.mdx +++ b/docs/devices-next/meters/plexlog.mdx @@ -1,6 +1,7 @@ --- title: Plexlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/plexlog.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,10 @@ The values are updated approximately every 15 seconds, hence the evcc `interval` +## Template Parameter `plexlog` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/powerdog.mdx b/docs/devices-next/meters/powerdog.mdx index 9446f980b4..0c5967908c 100644 --- a/docs/devices-next/meters/powerdog.mdx +++ b/docs/devices-next/meters/powerdog.mdx @@ -1,6 +1,7 @@ --- title: Powerdog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerdog.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `powerdog` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/powerfox-poweropti.mdx b/docs/devices-next/meters/powerfox-poweropti.mdx index 1e0ac55700..cb7099f950 100644 --- a/docs/devices-next/meters/powerfox-poweropti.mdx +++ b/docs/devices-next/meters/powerfox-poweropti.mdx @@ -1,6 +1,7 @@ --- title: Powerfox Poweropti custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerfox-poweropti.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `powerfox-poweropti` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| `id` | Id in case of multiple PowerOpti | Standard: `main` | yes | + diff --git a/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx index 8e32f43c27..e25ecbda9a 100644 --- a/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx +++ b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -1,6 +1,7 @@ --- -title: QCells Hybrid-Inverter (Cloud) +title: Qcells Hybrid-Inverter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/qcells-hybrid-cloud.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,11 +10,11 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# QCells Hybrid-Inverter (Cloud) +# Qcells Hybrid-Inverter (Cloud) -The QCells hybrid inverter has to be registered in the QCellsCloud. +The Qcells hybrid inverter has to be registered in the QcellsCloud. **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. @@ -26,7 +27,7 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. type: template template: qcells-hybrid-cloud usage: grid - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number.`} /> @@ -37,7 +38,7 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. type: template template: qcells-hybrid-cloud usage: pv - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number.`} /> @@ -48,16 +49,24 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number.`} advanced={`meters: - name: my_battery type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. capacity: 50 # Battery capacity (kWh), optional`} /> +## Template Parameter `qcells-hybrid-cloud` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| QcellsCloud TokenID
`tokenid` | Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". | | yes | +| Serial number
`serial` | Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. | | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx b/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx new file mode 100644 index 0000000000..728e0c6b47 --- /dev/null +++ b/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -0,0 +1,195 @@ +--- +title: Qcells Q.HOME ESS HYB-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME ESS HYB-G3 + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| The inverter has a third PV input (MPPT3)
`mppt3` | | | no | +| `storageunit` | | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | | no | + diff --git a/docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx b/docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx deleted file mode 100644 index 8e9f578b3c..0000000000 --- a/docs/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Qcells Q.HOME ESS HYB-G3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Qcells Q.HOME ESS HYB-G3 - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/rct-power.mdx b/docs/devices-next/meters/rct-power.mdx index b93a9d1fa1..4261375a6c 100644 --- a/docs/devices-next/meters/rct-power.mdx +++ b/docs/devices-next/meters/rct-power.mdx @@ -1,6 +1,7 @@ --- title: RCT Power custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/rct-power.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,15 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `rct-power` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `7`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `97`
Beispiel: `95`
Einheit: % | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `30s`
Beispiel: `5m` | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Einheit: W | no | +| External power
`externalpower` | Query external power of all devices connected to S0 | | no | + diff --git a/docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx b/docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx deleted file mode 100644 index 77e3fec27f..0000000000 --- a/docs/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Saia-Burgess Controls ALE3, AWD3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Saia-Burgess Controls ALE3, AWD3 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx new file mode 100644 index 0000000000..5e32e8fb70 --- /dev/null +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -0,0 +1,69 @@ +--- +title: Saia-Burgess Controls (SBC) ALE3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Saia-Burgess Controls (SBC) ALE3 + + + + + + + + + + + + + + + + +## Template Parameter `sbc-axx3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx b/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx new file mode 100644 index 0000000000..e1e8adca06 --- /dev/null +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -0,0 +1,69 @@ +--- +title: Saia-Burgess Controls (SBC) AWD3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Saia-Burgess Controls (SBC) AWD3 + + + + + + + + + + + + + + + + +## Template Parameter `sbc-axx3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx index 99a8fdab21..c485d7dfa6 100644 --- a/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -1,6 +1,7 @@ --- title: SAJ H1 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -76,3 +77,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `saj-h1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Timeout
`timeout` | | Standard: `5s`
Beispiel: `10s` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx index c4bbd2fd41..bd7735ecea 100644 --- a/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -1,6 +1,7 @@ --- title: SAJ H2 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `saj-h2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | Standard: `2` | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | + diff --git a/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx index be836300ca..6968e5eb68 100644 --- a/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -1,6 +1,7 @@ --- title: SAJ R5 Series Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-r5.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `saj-r5` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/sax-homespeicher.mdx b/docs/devices-next/meters/sax-homespeicher.mdx index 8fde7219f6..8591ea5cd6 100644 --- a/docs/devices-next/meters/sax-homespeicher.mdx +++ b/docs/devices-next/meters/sax-homespeicher.mdx @@ -1,6 +1,7 @@ --- title: SAX Homespeicher custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sax.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx index 68e36d98ce..44a475f4e9 100644 --- a/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx +++ b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -1,6 +1,7 @@ --- title: Schneider Electric iEM3xxx Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/schneider-iem3000.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `schneider-iem3000` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/senec-home.mdx b/docs/devices-next/meters/senec-home.mdx index a3c851b442..e7dc6d671b 100644 --- a/docs/devices-next/meters/senec-home.mdx +++ b/docs/devices-next/meters/senec-home.mdx @@ -1,6 +1,7 @@ --- title: SENEC .Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senec-home.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -56,3 +57,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `senec-home` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| `schema` | | Standard: `https`
Auswahl: `https`, `http` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx b/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx new file mode 100644 index 0000000000..fc23b04970 --- /dev/null +++ b/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx @@ -0,0 +1,34 @@ +--- +title: Senergy SE 4/5/6KTL-S1/G2 Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Senergy SE 4/5/6KTL-S1/G2 Inverter + + + + + +## Template Parameter `senergy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx b/docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx deleted file mode 100644 index d26588fdbf..0000000000 --- a/docs/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Senergy SE 4/5/6KTL-S1/G2 Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Senergy SE 4/5/6KTL-S1/G2 Inverter - - - - - diff --git a/docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx b/docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx deleted file mode 100644 index c57cbb81e0..0000000000 --- a/docs/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/shelly-1pm-mini.mdx b/docs/devices-next/meters/shelly-1pm-mini.mdx new file mode 100644 index 0000000000..26ddcd3dbf --- /dev/null +++ b/docs/devices-next/meters/shelly-1pm-mini.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly 1PM mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1PM mini + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-1pm.mdx b/docs/devices-next/meters/shelly-1pm.mdx new file mode 100644 index 0000000000..6154a05728 --- /dev/null +++ b/docs/devices-next/meters/shelly-1pm.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly 1PM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1PM + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-3em.mdx b/docs/devices-next/meters/shelly-3em.mdx index e225573d88..a1b8476efe 100644 --- a/docs/devices-next/meters/shelly-3em.mdx +++ b/docs/devices-next/meters/shelly-3em.mdx @@ -1,6 +1,7 @@ --- title: Shelly 3EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-3em.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -67,3 +68,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `shelly-3em` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/meters/shelly-em.mdx b/docs/devices-next/meters/shelly-em.mdx new file mode 100644 index 0000000000..fd6b6c0657 --- /dev/null +++ b/docs/devices-next/meters/shelly-em.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly EM + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-plug-s.mdx b/docs/devices-next/meters/shelly-plug-s.mdx new file mode 100644 index 0000000000..9507c07ef1 --- /dev/null +++ b/docs/devices-next/meters/shelly-plug-s.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Plug S +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Plug S + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-pm-mini.mdx b/docs/devices-next/meters/shelly-pm-mini.mdx new file mode 100644 index 0000000000..14f5e21651 --- /dev/null +++ b/docs/devices-next/meters/shelly-pm-mini.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly PM mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly PM mini + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-pro-1pm.mdx b/docs/devices-next/meters/shelly-pro-1pm.mdx new file mode 100644 index 0000000000..89ba5d3f8e --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-1pm.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Pro 1PM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 1PM + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-pro-3-em.mdx b/docs/devices-next/meters/shelly-pro-3-em.mdx index b65782f38b..49e1fb8918 100644 --- a/docs/devices-next/meters/shelly-pro-3-em.mdx +++ b/docs/devices-next/meters/shelly-pro-3-em.mdx @@ -1,6 +1,7 @@ --- title: Shelly Pro 3 EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-pro-3em.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `shelly-pro-3em` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx b/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx new file mode 100644 index 0000000000..02981a5287 --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Pro 3EM (monophase mode) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 3EM (monophase mode) + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-pro-em.mdx b/docs/devices-next/meters/shelly-pro-em.mdx new file mode 100644 index 0000000000..3188e90108 --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-em.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Pro EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro EM + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `shelly-1pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| `channel` | | | no | + diff --git a/docs/devices-next/meters/siemens-7kt1665.mdx b/docs/devices-next/meters/siemens-7kt1665.mdx index a9815304c2..8c75e1a416 100644 --- a/docs/devices-next/meters/siemens-7kt1665.mdx +++ b/docs/devices-next/meters/siemens-7kt1665.mdx @@ -1,6 +1,7 @@ --- title: Siemens 7KT1665 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-7kt1665.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `siemens-7kt1665` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/siemens-junelight-smart-battery.mdx b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx index b25f6fee52..7a5645dca5 100644 --- a/docs/devices-next/meters/siemens-junelight-smart-battery.mdx +++ b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -1,6 +1,7 @@ --- title: Siemens Junelight Smart Battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-junelight.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,10 @@ The battery has to be set to Loxone with the installer account. +## Template Parameter `siemens-junelight` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/siemens-pac-2200.mdx b/docs/devices-next/meters/siemens-pac-2200.mdx index cd228bffb5..4f2773e5f6 100644 --- a/docs/devices-next/meters/siemens-pac-2200.mdx +++ b/docs/devices-next/meters/siemens-pac-2200.mdx @@ -1,6 +1,7 @@ --- title: Siemens PAC 2200 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-pac2200.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `siemens-pac2200` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx b/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx new file mode 100644 index 0000000000..cec44117dd --- /dev/null +++ b/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx @@ -0,0 +1,75 @@ +--- +title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC + + + +The electrician needs to enable the Modbus via TCP/IP in their service app before the setup is functional. This is not available in the customers mySigen app. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sigenergy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| `id` | | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx b/docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx deleted file mode 100644 index 000b5aa928..0000000000 --- a/docs/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC - - - -The electrician needs to enable the Modbus via TCP/IP in their service app before the setup is functional. This is not available in the customers mySigen app. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/sma-data-manager.mdx b/docs/devices-next/meters/sma-data-manager.mdx index 9361cf11c5..f2b3f298e5 100644 --- a/docs/devices-next/meters/sma-data-manager.mdx +++ b/docs/devices-next/meters/sma-data-manager.mdx @@ -1,6 +1,7 @@ --- title: SMA Data Manager custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-data-manager.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,10 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server +## Template Parameter `sma-data-manager` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sma-energy-meter.mdx b/docs/devices-next/meters/sma-energy-meter.mdx index 9e605b4070..868a380ba7 100644 --- a/docs/devices-next/meters/sma-energy-meter.mdx +++ b/docs/devices-next/meters/sma-energy-meter.mdx @@ -1,6 +1,7 @@ --- title: SMA Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-energy-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -48,3 +49,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sma-energy-meter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Network interface
`interface` | | Beispiel: `eth0` | no | + diff --git a/docs/devices-next/meters/sma-inverter-speedwire.mdx b/docs/devices-next/meters/sma-inverter-speedwire.mdx index 89de5718fd..009e01b44e 100644 --- a/docs/devices-next/meters/sma-inverter-speedwire.mdx +++ b/docs/devices-next/meters/sma-inverter-speedwire.mdx @@ -1,6 +1,7 @@ --- title: SMA Inverter (Speedwire) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-speedwire.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -45,3 +46,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sma-inverter-speedwire` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Password
`password` | Password for user group Standard | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx index 852ac254de..3a14008e49 100644 --- a/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: SMA Smart Energy Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -70,3 +71,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sma-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx new file mode 100644 index 0000000000..1aaf69675a --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx @@ -0,0 +1,50 @@ +--- +title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) + + + + + +## Template Parameter `sma-sbs-15-25-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx deleted file mode 100644 index 5d32ffaf65..0000000000 --- a/docs/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) - - - - - diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx new file mode 100644 index 0000000000..8fbf08be32 --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx @@ -0,0 +1,50 @@ +--- +title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) + + + + + +## Template Parameter `sma-sbs-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx deleted file mode 100644 index 1e90164620..0000000000 --- a/docs/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) - - - - - diff --git a/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx b/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx new file mode 100644 index 0000000000..e8874c81ef --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -0,0 +1,36 @@ +--- +title: SMA Sunny Home Manager 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Home Manager 2.0 + + + + + +## Template Parameter `sma-home-manager` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Network interface
`interface` | | Beispiel: `eth0` | no | + diff --git a/docs/devices-next/meters/sma-sunny-home-manager-20.mdx b/docs/devices-next/meters/sma-sunny-home-manager-20.mdx deleted file mode 100644 index 9de48da6c9..0000000000 --- a/docs/devices-next/meters/sma-sunny-home-manager-20.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: SMA Sunny Home Manager 2.0 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA Sunny Home Manager 2.0 - - - - - diff --git a/docs/devices-next/meters/sma-sunny-island-modbus.mdx b/docs/devices-next/meters/sma-sunny-island-modbus.mdx index 34deb14402..67e85816b6 100644 --- a/docs/devices-next/meters/sma-sunny-island-modbus.mdx +++ b/docs/devices-next/meters/sma-sunny-island-modbus.mdx @@ -1,6 +1,7 @@ --- title: SMA Sunny Island (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-si-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,12 @@ import TabItem from '@theme/TabItem'; maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) watchdog: 60s # optional`} /> +## Template Parameter `sma-si-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/sma-webbox.mdx b/docs/devices-next/meters/sma-webbox.mdx index f10b8ce114..d162cd8f78 100644 --- a/docs/devices-next/meters/sma-webbox.mdx +++ b/docs/devices-next/meters/sma-webbox.mdx @@ -1,6 +1,7 @@ --- title: SMA WebBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-webbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `sma-webbox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/sma-wechselrichter-modbus.mdx b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx index ab7199b1f5..f80531e0b4 100644 --- a/docs/devices-next/meters/sma-wechselrichter-modbus.mdx +++ b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -1,6 +1,7 @@ --- title: SMA Wechselrichter (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `sma-inverter-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx b/docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx deleted file mode 100644 index b1e69f10a3..0000000000 --- a/docs/devices-next/meters/smartfox-box-reg-reg-extended.mdx +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Smartfox Box, Reg, Reg extended -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Smartfox Box, Reg, Reg extended - - - -`aux` can be used for water heating power. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/smartfox-box.mdx b/docs/devices-next/meters/smartfox-box.mdx new file mode 100644 index 0000000000..c99ed8450b --- /dev/null +++ b/docs/devices-next/meters/smartfox-box.mdx @@ -0,0 +1,58 @@ +--- +title: Smartfox Box +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Box + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/smartfox-light-em2-firmware.mdx b/docs/devices-next/meters/smartfox-light-em2-firmware.mdx new file mode 100644 index 0000000000..dbe4ccdc7f --- /dev/null +++ b/docs/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Light (EM2 firmware) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Light (EM2 firmware) + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox-em2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/smartfox-pro-2.mdx b/docs/devices-next/meters/smartfox-pro-2.mdx new file mode 100644 index 0000000000..0b1245ae3a --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro-2.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro 2 + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox-em2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/smartfox-pro-light-2.mdx b/docs/devices-next/meters/smartfox-pro-light-2.mdx new file mode 100644 index 0000000000..58512e774a --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro-light-2.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro Light 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro Light 2 + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox-em2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/smartfox-pro-light.mdx b/docs/devices-next/meters/smartfox-pro-light.mdx new file mode 100644 index 0000000000..5fc9ce950a --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro-light.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro Light +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro Light + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox-em2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx b/docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx deleted file mode 100644 index 812290df4b..0000000000 --- a/docs/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) - - - -`aux` can be used for water heating power. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/smartfox-pro.mdx b/docs/devices-next/meters/smartfox-pro.mdx new file mode 100644 index 0000000000..4a88e7476b --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox-em2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/smartfox-reg-extended.mdx b/docs/devices-next/meters/smartfox-reg-extended.mdx new file mode 100644 index 0000000000..1b1c664a03 --- /dev/null +++ b/docs/devices-next/meters/smartfox-reg-extended.mdx @@ -0,0 +1,58 @@ +--- +title: Smartfox Reg extended +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Reg extended + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/smartfox-reg.mdx b/docs/devices-next/meters/smartfox-reg.mdx new file mode 100644 index 0000000000..146d2c8cbd --- /dev/null +++ b/docs/devices-next/meters/smartfox-reg.mdx @@ -0,0 +1,58 @@ +--- +title: Smartfox Reg +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Reg + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `smartfox` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx b/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx new file mode 100644 index 0000000000..299c0b2e87 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: SofarSolar Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx b/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx new file mode 100644 index 0000000000..74f34bd5f9 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar HYD 3…6K-EP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 3…6K-EP + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | + diff --git a/docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx b/docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx deleted file mode 100644 index b756880eed..0000000000 --- a/docs/devices-next/meters/sofarsolar-hyd-36k-ep.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar HYD 3…6K-EP -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar HYD 3…6K-EP - - - -LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx b/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx new file mode 100644 index 0000000000..17f24fb396 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar HYD 5…20K-3PH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 5…20K-3PH + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | + diff --git a/docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx b/docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx deleted file mode 100644 index 566fe90bf7..0000000000 --- a/docs/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar HYD 5…20K-3PH -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar HYD 5…20K-3PH - - - -LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx b/docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx deleted file mode 100644 index 123d02bab2..0000000000 --- a/docs/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: SofarSolar Inverter, Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar Inverter, Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/sofarsolar-inverter.mdx b/docs/devices-next/meters/sofarsolar-inverter.mdx new file mode 100644 index 0000000000..00beddb5b5 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: SofarSolar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar Inverter + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx b/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx new file mode 100644 index 0000000000..54eb8de6bc --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar SOFAR 5…24KTL-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 5…24KTL-G3 + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | + diff --git a/docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx b/docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx deleted file mode 100644 index 1cd2aafbef..0000000000 --- a/docs/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar SOFAR 5…24KTL-G3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar SOFAR 5…24KTL-G3 - - - -LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx b/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx new file mode 100644 index 0000000000..fc6becf89b --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar SOFAR 80…136KTL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 80…136KTL + + + +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | + diff --git a/docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx b/docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx deleted file mode 100644 index c5300ca81b..0000000000 --- a/docs/devices-next/meters/sofarsolar-sofar-80136ktl.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar SOFAR 80…136KTL -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar SOFAR 80…136KTL - - - -LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/solaranzeige-solaranzeige.mdx b/docs/devices-next/meters/solaranzeige-solaranzeige.mdx new file mode 100644 index 0000000000..ba70968929 --- /dev/null +++ b/docs/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -0,0 +1,76 @@ +--- +title: Solaranzeige Solaranzeige +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solaranzeige Solaranzeige + + + + + + + + + + + + + + + + +## Template Parameter `solaranzeige` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | IP address or hostname of the MQTT broker | Beispiel: `192.0.2.2` | yes | +| Port
`port` | MQTT broker port | Standard: `1883` | no | +| Topic
`topic` | Topic (omit leading /) | Standard: `solaranzeige/box1` | no | +| Timeout
`timeout` | Don't accept values older than this value | Standard: `30s`
Beispiel: `10s` | no | +| Username
`user` | e.g. email address, user id, etc. | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/meters/solaranzeige.mdx b/docs/devices-next/meters/solaranzeige.mdx deleted file mode 100644 index 6eed5d6d9e..0000000000 --- a/docs/devices-next/meters/solaranzeige.mdx +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Solaranzeige Solaranzeige -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Solaranzeige Solaranzeige - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/solaredge-hybrid-inverter.mdx b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx index 6ecafc9d28..d2e576e651 100644 --- a/docs/devices-next/meters/solaredge-hybrid-inverter.mdx +++ b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: SolarEdge Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -184,3 +185,13 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re +## Template Parameter `solaredge-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/solaredge-inverter.mdx b/docs/devices-next/meters/solaredge-inverter.mdx index c013c75139..583d32dfcd 100644 --- a/docs/devices-next/meters/solaredge-inverter.mdx +++ b/docs/devices-next/meters/solaredge-inverter.mdx @@ -1,6 +1,7 @@ --- title: SolarEdge Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -77,3 +78,10 @@ Only one system may access the inverter! +## Template Parameter `solaredge-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | + diff --git a/docs/devices-next/meters/solarlog.mdx b/docs/devices-next/meters/solarlog.mdx index 2d94cec90b..3903900e6b 100644 --- a/docs/devices-next/meters/solarlog.mdx +++ b/docs/devices-next/meters/solarlog.mdx @@ -1,6 +1,7 @@ --- title: Solarlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarlog.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,10 @@ If you have a home battery installed, please do not use this device at all for g +## Template Parameter `solarlog` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | + diff --git a/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx b/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx new file mode 100644 index 0000000000..da18c7e75f --- /dev/null +++ b/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -0,0 +1,111 @@ +--- +title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax MAX.STORAGE / MAX.STORAGE Ultimate + + + +For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. + + + + + + + + + + + + + + + + + + + + +## Template Parameter `solarmax-maxstorage` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| `watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx b/docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx deleted file mode 100644 index 59a26af390..0000000000 --- a/docs/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SolarMax MAX.STORAGE / MAX.STORAGE Ultimate - - - -For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/solarmax-solarmax-smt.mdx b/docs/devices-next/meters/solarmax-solarmax-smt.mdx index 5b22bd5fb9..e4577948e3 100644 --- a/docs/devices-next/meters/solarmax-solarmax-smt.mdx +++ b/docs/devices-next/meters/solarmax-solarmax-smt.mdx @@ -1,6 +1,7 @@ --- title: SolarMax SolarMax SMT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-smt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `solarmax-smt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/solarmax-sp-series-inverter.mdx b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx index bf77b4110b..ebe6c4fd3e 100644 --- a/docs/devices-next/meters/solarmax-sp-series-inverter.mdx +++ b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -1,6 +1,7 @@ --- title: SolarMax SP Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `senergy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx b/docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx deleted file mode 100644 index e0c50e1af2..0000000000 --- a/docs/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Solarwatt EnergyManager, EnergyManager Pro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Solarwatt EnergyManager, EnergyManager Pro - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/solarwatt-energymanager-pro.mdx b/docs/devices-next/meters/solarwatt-energymanager-pro.mdx new file mode 100644 index 0000000000..252a89a629 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -0,0 +1,62 @@ +--- +title: Solarwatt EnergyManager Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt EnergyManager Pro + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `solarwatt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/solarwatt-energymanager.mdx b/docs/devices-next/meters/solarwatt-energymanager.mdx new file mode 100644 index 0000000000..7f76b2b67f --- /dev/null +++ b/docs/devices-next/meters/solarwatt-energymanager.mdx @@ -0,0 +1,62 @@ +--- +title: Solarwatt EnergyManager +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt EnergyManager + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `solarwatt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/solarwatt-manager-flex.mdx b/docs/devices-next/meters/solarwatt-manager-flex.mdx index 83d149b69f..dda70e6eb1 100644 --- a/docs/devices-next/meters/solarwatt-manager-flex.mdx +++ b/docs/devices-next/meters/solarwatt-manager-flex.mdx @@ -1,6 +1,7 @@ --- title: Solarwatt Manager flex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-flex.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -55,3 +56,10 @@ Combines data of all connected PV inverters or batteries. +## Template Parameter `solarwatt-flex` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx index 107f04ea22..2f82b995e7 100644 --- a/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx +++ b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -1,6 +1,7 @@ --- title: Solarwatt MyReserve Matrix (LAN oder PowerGateway) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-myreserve-matrix.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -56,3 +57,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `solarwatt-myreserve-matrix` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `8080` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/solarwatt-myreserve.mdx b/docs/devices-next/meters/solarwatt-myreserve.mdx index cc22037ed8..3452287ef3 100644 --- a/docs/devices-next/meters/solarwatt-myreserve.mdx +++ b/docs/devices-next/meters/solarwatt-myreserve.mdx @@ -1,6 +1,7 @@ --- title: Solarwatt MyReserve custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `solarwatt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx index b248b2c9bc..6006df6843 100644 --- a/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx +++ b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -1,6 +1,7 @@ --- title: Solax Hybrid-Inverter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-hybrid-cloud.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -61,3 +62,11 @@ The Solax hybrid inverter has to be registered in the SolaxCloud. +## Template Parameter `solax-hybrid-cloud` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') | | yes | +| Serial number
`serial` | https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number | | yes | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx b/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx new file mode 100644 index 0000000000..58692e41bd --- /dev/null +++ b/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -0,0 +1,195 @@ +--- +title: Solax Hybrid X1/X3 G3/G4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax Hybrid X1/X3 G3/G4 + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| The inverter has a third PV input (MPPT3)
`mppt3` | | | no | +| `storageunit` | | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | | no | + diff --git a/docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx b/docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx deleted file mode 100644 index 0873052f76..0000000000 --- a/docs/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Solax Hybrid X1/X3 G3/G4 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Solax Hybrid X1/X3 G3/G4 - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/solax-inverter-cloud.mdx b/docs/devices-next/meters/solax-inverter-cloud.mdx index b7a9d8eb54..3ebaac7820 100644 --- a/docs/devices-next/meters/solax-inverter-cloud.mdx +++ b/docs/devices-next/meters/solax-inverter-cloud.mdx @@ -1,6 +1,7 @@ --- title: Solax Inverter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-inverter-cloud.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ The Solax inverter has to be registered in the SolaxCloud. tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of \`tokenID\` here in single quotes (Example: '20241028488283838') serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number`} /> +## Template Parameter `solax-inverter-cloud` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') | | yes | +| Serial number
`serial` | https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number | | yes | + diff --git a/docs/devices-next/meters/solinteng.mdx b/docs/devices-next/meters/solinteng.mdx index 3dfe513494..ec34c33155 100644 --- a/docs/devices-next/meters/solinteng.mdx +++ b/docs/devices-next/meters/solinteng.mdx @@ -1,6 +1,7 @@ --- title: Solinteng custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `delay` | | Standard: `100ms` | no | + diff --git a/docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx b/docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx deleted file mode 100644 index 27a377851f..0000000000 --- a/docs/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Sonnen comfort, eco 5, eco 6, oem 6.5 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Sonnen comfort, eco 5, eco 6, oem 6.5 - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/sonnen-comfort.mdx b/docs/devices-next/meters/sonnen-comfort.mdx new file mode 100644 index 0000000000..a71444e384 --- /dev/null +++ b/docs/devices-next/meters/sonnen-comfort.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen comfort +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen comfort + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sonnenbatterie-eco56` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `7979` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Einheit: W | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `5s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/sonnen-eco-5.mdx b/docs/devices-next/meters/sonnen-eco-5.mdx new file mode 100644 index 0000000000..8cc05f0f3c --- /dev/null +++ b/docs/devices-next/meters/sonnen-eco-5.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen eco 5 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen eco 5 + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sonnenbatterie-eco56` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `7979` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Einheit: W | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `5s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/sonnen-eco-6.mdx b/docs/devices-next/meters/sonnen-eco-6.mdx new file mode 100644 index 0000000000..bddb11e02d --- /dev/null +++ b/docs/devices-next/meters/sonnen-eco-6.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen eco 6 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen eco 6 + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sonnenbatterie-eco56` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `7979` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Einheit: W | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `5s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/sonnen-oem-6-5.mdx b/docs/devices-next/meters/sonnen-oem-6-5.mdx new file mode 100644 index 0000000000..cf9abb4013 --- /dev/null +++ b/docs/devices-next/meters/sonnen-oem-6-5.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen oem 6.5 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen oem 6.5 + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sonnenbatterie-eco56` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `7979` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Einheit: W | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `5s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/sonnen-sonnenbatterie.mdx b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx index d4c6806660..4ad0955e34 100644 --- a/docs/devices-next/meters/sonnen-sonnenbatterie.mdx +++ b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -1,6 +1,7 @@ --- title: Sonnen sonnenBatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -65,3 +66,14 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa +## Template Parameter `sonnenbatterie` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `8080` | no | +| `token` | API Token (required for active battery control) | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `3300`
Einheit: W | no | +| Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | Standard: `self-consumption`
Auswahl: `self-consumption`, `time-of-use` | yes | + diff --git a/docs/devices-next/meters/st-ems.mdx b/docs/devices-next/meters/st-ems.mdx index ca9e00fed2..b1537aa04a 100644 --- a/docs/devices-next/meters/st-ems.mdx +++ b/docs/devices-next/meters/st-ems.mdx @@ -1,6 +1,7 @@ --- title: St-ems custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `delay` | | Standard: `100ms` | no | + diff --git a/docs/devices-next/meters/steca-coolcept-flex.mdx b/docs/devices-next/meters/steca-coolcept-flex.mdx index c72fb7271f..185a785d6f 100644 --- a/docs/devices-next/meters/steca-coolcept-flex.mdx +++ b/docs/devices-next/meters/steca-coolcept-flex.mdx @@ -1,6 +1,7 @@ --- title: Steca coolcept fleX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `kostal-piko-mp-plus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/sungrow-sg-series-inverter.mdx b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx index de772b59f6..5ab5fde275 100644 --- a/docs/devices-next/meters/sungrow-sg-series-inverter.mdx +++ b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sungrow SG Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sungrow-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx index 088e8fb891..18a23a32cd 100644 --- a/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sungrow SH Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -157,3 +158,13 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw +## Template Parameter `sungrow-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Timeout
`timeout` | | Beispiel: `10s` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Maximum charge power
`maxchargepower` | Maximum charge power for forced charging of the battery in watts. (0 to automatically set the value of the maximum BDC rated power) | Einheit: W | no | + diff --git a/docs/devices-next/meters/sunspec-battery-model-124.mdx b/docs/devices-next/meters/sunspec-battery-model-124.mdx index 19db0ad988..85f8406965 100644 --- a/docs/devices-next/meters/sunspec-battery-model-124.mdx +++ b/docs/devices-next/meters/sunspec-battery-model-124.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Battery (Model 124) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter-control.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -63,3 +64,11 @@ import TabItem from '@theme/TabItem'; maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) capacity: 50 # Battery capacity (kWh), optional`} /> +## Template Parameter `sunspec-inverter-control` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sunspec-battery-model-802.mdx b/docs/devices-next/meters/sunspec-battery-model-802.mdx index eb0b4c5bb5..7d01f4ab5e 100644 --- a/docs/devices-next/meters/sunspec-battery-model-802.mdx +++ b/docs/devices-next/meters/sunspec-battery-model-802.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Battery (Model 802) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-battery-control.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -64,3 +65,12 @@ import TabItem from '@theme/TabItem'; minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> +## Template Parameter `sunspec-battery-control` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | + diff --git a/docs/devices-next/meters/sunspec-hybrid-inverter.mdx b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx index 9e5b86a1d3..211b4a3ea9 100644 --- a/docs/devices-next/meters/sunspec-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -148,3 +149,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sunspec-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/sunspec-inverter.mdx b/docs/devices-next/meters/sunspec-inverter.mdx index a872d35dc3..d8c23c5897 100644 --- a/docs/devices-next/meters/sunspec-inverter.mdx +++ b/docs/devices-next/meters/sunspec-inverter.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sunspec-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sunspec-meter.mdx b/docs/devices-next/meters/sunspec-meter.mdx index f1bb229ba2..5d3f06f24f 100644 --- a/docs/devices-next/meters/sunspec-meter.mdx +++ b/docs/devices-next/meters/sunspec-meter.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `sunspec-meter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx index 03d3e7ff13..852f2b63b0 100644 --- a/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `deye-hybrid-3p` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | + diff --git a/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx index 59f1a2bb2d..76d9b81afa 100644 --- a/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -183,3 +184,15 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `deye-hybrid-hp3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| `storageunit` | | Standard: `1` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Treat GEN port as solar input
`includegenport` | | | no | + diff --git a/docs/devices-next/meters/sunsynk-micro-inverter.mdx b/docs/devices-next/meters/sunsynk-micro-inverter.mdx index dde97fc54c..aaddf387bc 100644 --- a/docs/devices-next/meters/sunsynk-micro-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `deye-mi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx index 8c6b0f2f8c..7cd222a65f 100644 --- a/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `deye-storage` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/sunsynk-string-inverter.mdx b/docs/devices-next/meters/sunsynk-string-inverter.mdx index ed155ffd63..7669e57a5a 100644 --- a/docs/devices-next/meters/sunsynk-string-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-string-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Template Parameter `deye-string` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/sunway.mdx b/docs/devices-next/meters/sunway.mdx index f0ab49c8d1..e664161b45 100644 --- a/docs/devices-next/meters/sunway.mdx +++ b/docs/devices-next/meters/sunway.mdx @@ -1,6 +1,7 @@ --- title: Sunway custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `delay` | | Standard: `100ms` | no | + diff --git a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx new file mode 100644 index 0000000000..97c52d35bf --- /dev/null +++ b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx @@ -0,0 +1,100 @@ +--- +title: Tasmota SML IR-reader for smartmeters e.g. Hichi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota SML IR-reader for smartmeters e.g. Hichi + + + +To be able to read the values of the smart meter for evcc correctly, the IR reader script must be changed so that the following JSON tags are generated: +- **SML** as the group name of the read parameters +- **Total_in** for the total consumption in KWh (4 decimal places) +- **Total_out** for the total feed-in in KWh (4 decimal places) +- **Power_curr** for the current consumption or the current feed-in in W (0 decimal places) + +A corresponding IR reader script looks like this: +``` +>D +>B +=>sensor53 r +>M 1 +// highlight-next-line ++1,3,s,16,9600,SML +// highlight-next-line +1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 +// highlight-next-line +1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 +// highlight-next-line +1,77070100100700ff@1,Verbrauch,W,Power_curr,0 +1,77070100600100ff@#,Zählernummer,,Meter_Id,0 +# +``` + + + + + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `tasmota-sml` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | admin is default | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx deleted file mode 100644 index 36348858be..0000000000 --- a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Tasmota SML IR-reader for smartmeters e.g. Hichi -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Tasmota SML IR-reader for smartmeters e.g. Hichi - - - -To be able to read the values of the smart meter for evcc correctly, the IR reader script must be changed so that the following JSON tags are generated: -- **SML** as the group name of the read parameters -- **Total_in** for the total consumption in KWh (4 decimal places) -- **Total_out** for the total feed-in in KWh (4 decimal places) -- **Power_curr** for the current consumption or the current feed-in in W (0 decimal places) - -A corresponding IR reader script looks like this: -``` ->D ->B -=>sensor53 r ->M 1 -// highlight-next-line -+1,3,s,16,9600,SML -// highlight-next-line -1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 -// highlight-next-line -1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 -// highlight-next-line -1,77070100100700ff@1,Verbrauch,W,Power_curr,0 -1,77070100600100ff@#,Zählernummer,,Meter_Id,0 -# -``` - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx b/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx new file mode 100644 index 0000000000..e3a1683700 --- /dev/null +++ b/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -0,0 +1,80 @@ +--- +title: Tasmota Tasmota (1 Phase + SML Meter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota Tasmota (1 Phase + SML Meter) + + + + + + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `tasmota` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | admin is default | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | +| Channel number
`channel` | Meterchannel number (1-8) | Standard: `1` | yes | + diff --git a/docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx b/docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx deleted file mode 100644 index 84d7d76495..0000000000 --- a/docs/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Tasmota Tasmota (1 Phase + SML Meter) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Tasmota Tasmota (1 Phase + SML Meter) - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/tasmota-three-phase.mdx b/docs/devices-next/meters/tasmota-three-phase.mdx index 90b20adb5e..e510467e69 100644 --- a/docs/devices-next/meters/tasmota-three-phase.mdx +++ b/docs/devices-next/meters/tasmota-three-phase.mdx @@ -1,6 +1,7 @@ --- title: Tasmota three phase custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-3p.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -67,3 +68,11 @@ Meter channels 1,2,3 must be used. +## Template Parameter `tasmota-3p` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | admin is default | | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/meters/tesla-powerwall.mdx b/docs/devices-next/meters/tesla-powerwall.mdx index ef925a48b0..81e74e65f6 100644 --- a/docs/devices-next/meters/tesla-powerwall.mdx +++ b/docs/devices-next/meters/tesla-powerwall.mdx @@ -1,6 +1,7 @@ --- title: Tesla Powerwall custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tesla-powerwall.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -93,3 +94,14 @@ The following apps allow to create the token: +## Template Parameter `tesla-powerwall` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Password
`password` | Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. | | yes | +| `refreshToken` | | | no | +| `siteId` | optional product identifier of the energy site, use to override autodectction | | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | + diff --git a/docs/devices-next/meters/tibber-pulse.mdx b/docs/devices-next/meters/tibber-pulse.mdx index 774b3942f6..bcb4e8abc4 100644 --- a/docs/devices-next/meters/tibber-pulse.mdx +++ b/docs/devices-next/meters/tibber-pulse.mdx @@ -1,6 +1,7 @@ --- title: Tibber Pulse custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tibber-pulse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,10 @@ import TabItem from '@theme/TabItem'; token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional`} /> +## Template Parameter `tibber-pulse` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | | Beispiel: `5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE` | yes | +| `homeid` | | Beispiel: `96a14971-525a-4420-aae9-e5aedaa129ff` | no | + diff --git a/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx index 6ba99a46a3..2c9f82bdcc 100644 --- a/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx +++ b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tplink.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP address or hostname`} /> +## Template Parameter `tplink` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx index e3f0a0e34c..c62d8f17cc 100644 --- a/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx +++ b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tapo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros`} /> +## Template Parameter `tapo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | + diff --git a/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx b/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx new file mode 100644 index 0000000000..1d0a0f9f08 --- /dev/null +++ b/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -0,0 +1,33 @@ +--- +title: TQ Energy Manager EM2xx/EM3xx +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TQ Energy Manager EM2xx/EM3xx + + + + + +## Template Parameter `tq-em` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `80` | no | +| Password
`password` | Use single quotes in case of leading zeros | | no | + diff --git a/docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx b/docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx deleted file mode 100644 index f61385462d..0000000000 --- a/docs/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: TQ Energy Manager EM2xx/EM3xx -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# TQ Energy Manager EM2xx/EM3xx - - - - - diff --git a/docs/devices-next/meters/tq-energy-manager-em420.mdx b/docs/devices-next/meters/tq-energy-manager-em420.mdx index 1b00749fdd..6391d106ac 100644 --- a/docs/devices-next/meters/tq-energy-manager-em420.mdx +++ b/docs/devices-next/meters/tq-energy-manager-em420.mdx @@ -1,6 +1,7 @@ --- title: TQ Energy Manager EM420 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em420.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,12 @@ import TabItem from '@theme/TabItem'; device: local # API Device Path, JSON-API -> Data Endpoint (optional) token: ey... # Access token, Access token for EM420 (Create in Profile -> Access tokens)`} /> +## Template Parameter `tq-em420` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `80` | no | +| API Device Path
`device` | JSON-API -> Data Endpoint | Standard: `local` | no | +| Access token
`token` | Access token for EM420 (Create in Profile -> Access tokens) | Beispiel: `ey...` | yes | + diff --git a/docs/devices-next/meters/varta-element.mdx b/docs/devices-next/meters/varta-element.mdx new file mode 100644 index 0000000000..8ab28b64be --- /dev/null +++ b/docs/devices-next/meters/varta-element.mdx @@ -0,0 +1,70 @@ +--- +title: VARTA element +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA element + + + +PV only available with PV sensor + + + + + + + + + + + + + + + + + + + + +## Template Parameter `varta` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/varta-pulse-neo.mdx b/docs/devices-next/meters/varta-pulse-neo.mdx new file mode 100644 index 0000000000..8b28e3a402 --- /dev/null +++ b/docs/devices-next/meters/varta-pulse-neo.mdx @@ -0,0 +1,70 @@ +--- +title: VARTA pulse neo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA pulse neo + + + +PV only available with PV sensor + + + + + + + + + + + + + + + + + + + + +## Template Parameter `varta` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx b/docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx deleted file mode 100644 index c4d3dccdb3..0000000000 --- a/docs/devices-next/meters/varta-pulse-pulse-neo-element.mdx +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: VARTA pulse, pulse neo, element -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# VARTA pulse, pulse neo, element - - - -PV only available with PV sensor - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/varta-pulse.mdx b/docs/devices-next/meters/varta-pulse.mdx new file mode 100644 index 0000000000..abc4aa0308 --- /dev/null +++ b/docs/devices-next/meters/varta-pulse.mdx @@ -0,0 +1,70 @@ +--- +title: VARTA pulse +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA pulse + + + +PV only available with PV sensor + + + + + + + + + + + + + + + + + + + + +## Template Parameter `varta` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/victron-em24.mdx b/docs/devices-next/meters/victron-em24.mdx index bd3408e6cf..82cce12e81 100644 --- a/docs/devices-next/meters/victron-em24.mdx +++ b/docs/devices-next/meters/victron-em24.mdx @@ -1,6 +1,7 @@ --- title: Victron EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -63,3 +64,9 @@ EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Etherne +## Template Parameter `cg-em24` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/victron-em24_e1.mdx b/docs/devices-next/meters/victron-em24_e1.mdx new file mode 100644 index 0000000000..ca609c0e80 --- /dev/null +++ b/docs/devices-next/meters/victron-em24_e1.mdx @@ -0,0 +1,59 @@ +--- +title: Victron EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM24_E1 + + + +EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. +The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + +## Template Parameter `cg-em24_e1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/victron-em24e1.mdx b/docs/devices-next/meters/victron-em24e1.mdx deleted file mode 100644 index 3c5c9d793f..0000000000 --- a/docs/devices-next/meters/victron-em24e1.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Victron EM24_E1 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Victron EM24_E1 - - - -EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. -The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/victron-em530-em540.mdx b/docs/devices-next/meters/victron-em530-em540.mdx new file mode 100644 index 0000000000..ccbc77e50c --- /dev/null +++ b/docs/devices-next/meters/victron-em530-em540.mdx @@ -0,0 +1,81 @@ +--- +title: Victron EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM530/EM540 + + + + + + + + + + + + + + + + +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/victron-em530em540.mdx b/docs/devices-next/meters/victron-em530em540.mdx deleted file mode 100644 index f6e9cd487d..0000000000 --- a/docs/devices-next/meters/victron-em530em540.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Victron EM530/EM540 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Victron EM530/EM540 - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/victron-energy.mdx b/docs/devices-next/meters/victron-energy.mdx index 89ee78ae08..009d9a5fe2 100644 --- a/docs/devices-next/meters/victron-energy.mdx +++ b/docs/devices-next/meters/victron-energy.mdx @@ -1,6 +1,7 @@ --- title: Victron Energy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/victron-energy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -80,3 +81,15 @@ For grid usage, a grid meter VRM instance is require to enabled load management. +## Template Parameter `victron-energy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | no | +| `meterid` | Grid meter VRM instance- can be read out in VRM portal or via remoteUI. | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | +| Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | +| Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | + diff --git a/docs/devices-next/meters/victron-et340.mdx b/docs/devices-next/meters/victron-et340.mdx index 3cad3678a7..718a79e59f 100644 --- a/docs/devices-next/meters/victron-et340.mdx +++ b/docs/devices-next/meters/victron-et340.mdx @@ -1,6 +1,7 @@ --- title: Victron ET340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx index 8121597c44..b0fba6d670 100644 --- a/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx +++ b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -1,6 +1,7 @@ --- title: Volkszähler HTTP API, Import & Export custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-importexport.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; importuuid: exportuuid:`} /> +## Template Parameter `volkszaehler-importexport` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| URL of the middleware's "data" context
`url` | The URL is for example: http://zaehler.network.local:8080/api/data | | no | +| `importuuid` | | | yes | +| `exportuuid` | | | yes | + diff --git a/docs/devices-next/meters/volkszahler-http-api.mdx b/docs/devices-next/meters/volkszahler-http-api.mdx index c91f6f7260..8495b8a2da 100644 --- a/docs/devices-next/meters/volkszahler-http-api.mdx +++ b/docs/devices-next/meters/volkszahler-http-api.mdx @@ -1,6 +1,7 @@ --- title: Volkszähler HTTP API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-http.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,10 @@ import TabItem from '@theme/TabItem'; url: # URL of the middleware's "data" context, Example: http://zaehler.network.local:8080/api/data (optional) uuid:`} /> +## Template Parameter `volkszaehler-http` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| URL of the middleware's "data" context
`url` | Example: http://zaehler.network.local:8080/api/data | | no | +| `uuid` | | | yes | + diff --git a/docs/devices-next/meters/volkszahler-websocket-api.mdx b/docs/devices-next/meters/volkszahler-websocket-api.mdx index 67e11eea78..ae212f1525 100644 --- a/docs/devices-next/meters/volkszahler-websocket-api.mdx +++ b/docs/devices-next/meters/volkszahler-websocket-api.mdx @@ -1,6 +1,7 @@ --- title: Volkszähler WebSocket API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-ws.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; port: 8082 # Port, optional uuid:`} /> +## Template Parameter `volkszaehler-ws` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `8082` | no | +| `uuid` | | | yes | + diff --git a/docs/devices-next/meters/vzlogger.mdx b/docs/devices-next/meters/vzlogger.mdx index cb354b6df1..22e41feb42 100644 --- a/docs/devices-next/meters/vzlogger.mdx +++ b/docs/devices-next/meters/vzlogger.mdx @@ -1,6 +1,7 @@ --- title: vzlogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/vzlogger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,3 +41,22 @@ import TabItem from '@theme/TabItem'; l3voltageuuid: # The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0), optional cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `vzlogger` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `8081` | no | +| `uuid` | | | yes | +| Scale factor
`scale` | Multiply by this value | Standard: `1` | no | +| The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0)
`l1currentuuid` | | | no | +| The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0)
`l2currentuuid` | | | no | +| The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0)
`l3currentuuid` | | | no | +| The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0)
`l1poweruuid` | | | no | +| The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0)
`l2poweruuid` | | | no | +| The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0)
`l3poweruuid` | | | no | +| The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0)
`l1voltageuuid` | | | no | +| The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0)
`l2voltageuuid` | | | no | +| The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0)
`l3voltageuuid` | | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/meters/wago-879-30xx.mdx b/docs/devices-next/meters/wago-879-30xx.mdx index 5903b20a53..ead445d006 100644 --- a/docs/devices-next/meters/wago-879-30xx.mdx +++ b/docs/devices-next/meters/wago-879-30xx.mdx @@ -1,6 +1,7 @@ --- title: Wago 879-30xx custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wago-879-30xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `wago-879-30xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/wattsonic.mdx b/docs/devices-next/meters/wattsonic.mdx index 903b59a496..113b2155ff 100644 --- a/docs/devices-next/meters/wattsonic.mdx +++ b/docs/devices-next/meters/wattsonic.mdx @@ -1,6 +1,7 @@ --- title: Wattsonic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `delay` | | Standard: `100ms` | no | + diff --git a/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx index 7b6cb2571c..2d24554ffc 100644 --- a/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM110-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron-sdm220_230` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx index 59d3a1d638..11ee8a4924 100644 --- a/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM111-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron-sdm220_230` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx index e90cc3f695..5c88cff21f 100644 --- a/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM120-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx index ec24869654..71272265e3 100644 --- a/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM122-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/youless-energy-monitor.mdx b/docs/devices-next/meters/youless-energy-monitor.mdx index 749b03c1ff..c027086f1a 100644 --- a/docs/devices-next/meters/youless-energy-monitor.mdx +++ b/docs/devices-next/meters/youless-energy-monitor.mdx @@ -1,6 +1,7 @@ --- title: Youless Energy Monitor custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/youless.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,9 @@ An externally connected S0 generation meter is required to record the solar prod +## Template Parameter `youless` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx new file mode 100644 index 0000000000..eda4fd7870 --- /dev/null +++ b/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: ZCS Azzurro Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZCS Azzurro Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx deleted file mode 100644 index f01fc07703..0000000000 --- a/docs/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: ZCS Azzurro Inverter, Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ZCS Azzurro Inverter, Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/devices-next/meters/zcs-azzurro-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-inverter.mdx new file mode 100644 index 0000000000..36237710be --- /dev/null +++ b/docs/devices-next/meters/zcs-azzurro-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: ZCS Azzurro Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZCS Azzurro Inverter + + + + + + + + + + + + + + + + + + + + + +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/zendure-hyper-2000.mdx b/docs/devices-next/meters/zendure-hyper-2000.mdx index b62c4750f4..7e813e31be 100644 --- a/docs/devices-next/meters/zendure-hyper-2000.mdx +++ b/docs/devices-next/meters/zendure-hyper-2000.mdx @@ -1,6 +1,7 @@ --- title: Zendure Hyper 2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/zendure.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -51,3 +52,13 @@ import TabItem from '@theme/TabItem'; +## Template Parameter `zendure` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `account` | | Beispiel: `dev@zendure.com` | yes | +| `serial` | You can find this in the Zendure App in the settings of the device | Beispiel: `VU5D99F74021B04` | yes | +| `region` | | Standard: `EU`
Auswahl: `EU`, `Global` | yes | +| Timeout
`timeout` | | Beispiel: `10s` | no | +| Battery capacity
`capacity` | | Standard: `2`
Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx deleted file mode 100644 index a5938fb7a8..0000000000 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Zuidwijk SlimmeLezer(+) in Luxembourg -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Zuidwijk SlimmeLezer(+) in Luxembourg - - - -Slimmelezer devices use different sensor names in Luxembourg. - - - - diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx new file mode 100644 index 0000000000..e1452aee57 --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -0,0 +1,32 @@ +--- +title: Zuidwijk SlimmeLezer(+) in Luxembourg +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) in Luxembourg + + + +Slimmelezer devices use different sensor names in Luxembourg. + + + + +## Template Parameter `slimmelezer-luxembourg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx new file mode 100644 index 0000000000..13d071c614 --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -0,0 +1,32 @@ +--- +title: Zuidwijk SlimmeLezer(+) V2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) V2 + + + +More recent slimmelezer devices use a different configuration. Try this template if the other one fails. + + + + +## Template Parameter `slimmelezer-V2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx new file mode 100644 index 0000000000..68c0c71ab7 --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -0,0 +1,36 @@ +--- +title: Zuidwijk SlimmeLezer(+) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) + + + + + +## Template Parameter `slimmelezer` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Scale factor
`scale` | Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle | Standard: `1000`
Beispiel: `1 \| 10 \| 100 \| 1000` | yes | + diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx deleted file mode 100644 index 2835de85da..0000000000 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-v2.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Zuidwijk SlimmeLezer(+) V2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Zuidwijk SlimmeLezer(+) V2 - - - -More recent slimmelezer devices use a different configuration. Try this template if the other one fails. - - - - diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer.mdx deleted file mode 100644 index 22a6369aed..0000000000 --- a/docs/devices-next/meters/zuidwijk-slimmelezer.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Zuidwijk SlimmeLezer(+) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Zuidwijk SlimmeLezer(+) - - - - - diff --git a/docs/devices-next/tariffs/amber-electric.mdx b/docs/devices-next/tariffs/amber-electric.mdx index dfd75521bc..a59237258e 100644 --- a/docs/devices-next/tariffs/amber-electric.mdx +++ b/docs/devices-next/tariffs/amber-electric.mdx @@ -1,6 +1,7 @@ --- title: Amber Electric custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/amber.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,14 @@ import TabItem from '@theme/TabItem'; tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `amber` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | | | no | +| `siteid` | | | no | +| `channel` | | | no | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/awattar.mdx b/docs/devices-next/tariffs/awattar.mdx index c79a84f5ed..30e88ded82 100644 --- a/docs/devices-next/tariffs/awattar.mdx +++ b/docs/devices-next/tariffs/awattar.mdx @@ -1,6 +1,7 @@ --- title: Awattar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/awattar.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,12 @@ import TabItem from '@theme/TabItem'; tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `awattar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `region` | | Beispiel: `AT`
Auswahl: `DE`, `AT` | yes | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx index b193512531..8d619bd385 100644 --- a/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx +++ b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -1,6 +1,7 @@ --- title: Electricity Maps Commercial API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps token: zone: DE # see https://api.electricitymap.org/v3/zones`} /> +## Template Parameter `electricitymaps` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| URI
`uri` | HTTP(S) address | Beispiel: `https://api-access.electricitymaps.com/2w...1g/` | yes | +| `token` | | | yes | +| `zone` | see https://api.electricitymap.org/v3/zones | Beispiel: `DE` | yes | + diff --git a/docs/devices-next/tariffs/electricity-maps-free-api.mdx b/docs/devices-next/tariffs/electricity-maps-free-api.mdx index 1ede6a4222..0b5d69ed1e 100644 --- a/docs/devices-next/tariffs/electricity-maps-free-api.mdx +++ b/docs/devices-next/tariffs/electricity-maps-free-api.mdx @@ -1,6 +1,7 @@ --- title: Electricity Maps Free API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps-free.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps token: zone: DE # see https://api.electricitymap.org/v3/zones`} /> +## Template Parameter `electricitymaps-free` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | | | yes | +| `zone` | see https://api.electricitymap.org/v3/zones | Beispiel: `DE` | yes | + diff --git a/docs/devices-next/tariffs/energinet.mdx b/docs/devices-next/tariffs/energinet.mdx index 39424d692a..4ab2487b35 100644 --- a/docs/devices-next/tariffs/energinet.mdx +++ b/docs/devices-next/tariffs/energinet.mdx @@ -1,6 +1,7 @@ --- title: Energinet custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energinet.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,12 @@ import TabItem from '@theme/TabItem'; tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `energinet` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `region` | | Beispiel: `dk1`
Auswahl: `dk1`, `dk2` | yes | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/enever.mdx b/docs/devices-next/tariffs/enever.mdx index d8bb6a6ffd..288cbdfaee 100644 --- a/docs/devices-next/tariffs/enever.mdx +++ b/docs/devices-next/tariffs/enever.mdx @@ -1,6 +1,7 @@ --- title: Enever custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/enever.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,14 @@ import TabItem from '@theme/TabItem'; formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) interval: 3h # optional`} /> +## Template Parameter `enever` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | | | yes | +| `provider` | | Auswahl: ``, `AA`, `AIP`, `ANWB`, `BE`
, `EE`, `EN`, `EVO`, `EZ`, `FR`
, `GSL`, `MDE`, `NE`, `PE`, `TI`
, `VDB`, `VON`, `WE`, `ZG`, `ZP`
| yes | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | +| `interval` | | Standard: `3h` | no | + diff --git a/docs/devices-next/tariffs/entso-e.mdx b/docs/devices-next/tariffs/entso-e.mdx index 48a2f9d3db..539099674c 100644 --- a/docs/devices-next/tariffs/entso-e.mdx +++ b/docs/devices-next/tariffs/entso-e.mdx @@ -1,6 +1,7 @@ --- title: ENTSO-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/entsoe.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,13 @@ Basis for many dynamic tariffs. tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `entsoe` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `securitytoken` | Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation | | no | +| `domain` | see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas | Beispiel: `BZN\|DE-LU` | no | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/forecast-solar.mdx b/docs/devices-next/tariffs/forecast-solar.mdx new file mode 100644 index 0000000000..2ac10302c2 --- /dev/null +++ b/docs/devices-next/tariffs/forecast-solar.mdx @@ -0,0 +1,53 @@ +--- +title: Forecast.Solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Forecast.Solar + + + +[forecast.solar](https://forecast.solar) can be used for free. Paid plans can also be used by specifying an API key. + + + + +## Template Parameter `forecast-solar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Latitude
`lat` | | Beispiel: `55.7351` | yes | +| Longitude
`lon` | | Beispiel: `9.1275` | yes | +| Decline
`dec` | 0 = horizontal, 90 = vertical | Beispiel: `25` | yes | +| Maximum generator power
`kwp` | | Beispiel: `9.8`
Einheit: kWp | yes | +| Azimuth
`az` | -180 = north, -90 = east, 0 = south, 90 = west, 180 = north | Beispiel: `180` | yes | +| Horizon
`horizon` | Simulates terrain shadows, \[more information\](https://doc.forecast.solar/horizon) | Beispiel: `0,0,15,30,45,60,60,60,45,30,15,0` | no | +| API key
`apikey` | | | no | +| `interval` | | Standard: `1h` | no | + diff --git a/docs/devices-next/tariffs/forecastsolar.mdx b/docs/devices-next/tariffs/forecastsolar.mdx deleted file mode 100644 index ffc8669d16..0000000000 --- a/docs/devices-next/tariffs/forecastsolar.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Forecast.Solar -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Forecast.Solar - - - -[forecast.solar](https://forecast.solar) can be used for free. Paid plans can also be used by specifying an API key. - - - - diff --git a/docs/devices-next/tariffs/fraunhofer-ise.mdx b/docs/devices-next/tariffs/fraunhofer-ise.mdx index f4b9825c5b..258fc4ddf4 100644 --- a/docs/devices-next/tariffs/fraunhofer-ise.mdx +++ b/docs/devices-next/tariffs/fraunhofer-ise.mdx @@ -1,6 +1,7 @@ --- title: Fraunhofer ISE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energy-charts-api.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,12 @@ Day-ahead forecast of energy prices (per kWh) on the exchange. No prior registra tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `energy-charts-api` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `bzn` | Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get | Standard: `DE-LU`
Auswahl: `AT`, `BE`, `CH`, `CZ`, `DE-LU`
, `DE-AT-LU`, `DK1`, `DK2`, `FR`, `HU`
, `IT-NORTH`, `NL`, `NO2`, `PL`, `SE4`
, `SI` | yes | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/green-grid-compass.mdx b/docs/devices-next/tariffs/green-grid-compass.mdx index 2a08dc19d7..c0b6d16c72 100644 --- a/docs/devices-next/tariffs/green-grid-compass.mdx +++ b/docs/devices-next/tariffs/green-grid-compass.mdx @@ -1,6 +1,7 @@ --- title: Green Grid Compass custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/green-grid-compass.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ European CO₂ intensity data from [greengrid-compass.eu](https://www.greengrid- apiKey: # API Key, Create an app in https://api-portal.eco2grid.com and copy the key zone: DE_LU # Zone code, [BE, DE_LU]`} /> +## Template Parameter `green-grid-compass` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| API Key
`apiKey` | Create an app in https://api-portal.eco2grid.com and copy the key | | yes | +| Zone code
`zone` | | Standard: `DE_LU`
Auswahl: `BE`, `DE_LU` | yes | + diff --git a/docs/devices-next/tariffs/groupe-e-vario-plus.mdx b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx index ea4defe600..0f662fe55f 100644 --- a/docs/devices-next/tariffs/groupe-e-vario-plus.mdx +++ b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -1,6 +1,7 @@ --- title: Groupe E Vario Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/groupe-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ import TabItem from '@theme/TabItem'; tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `groupe-e` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/grunstromindex.mdx b/docs/devices-next/tariffs/grunstromindex.mdx index 73118929b8..7fbe4e49d3 100644 --- a/docs/devices-next/tariffs/grunstromindex.mdx +++ b/docs/devices-next/tariffs/grunstromindex.mdx @@ -1,6 +1,7 @@ --- title: Grünstromindex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/grünstromindex.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ Regional emission data from https://gruenstromindex.de zip: token: # Token for accessing the API from https://console.corrently.io (optional)`} /> +## Template Parameter `grünstromindex` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `zip` | | | yes | +| `token` | Token for accessing the API from https://console.corrently.io | | no | + diff --git a/docs/devices-next/tariffs/index.mdx b/docs/devices-next/tariffs/index.mdx index 7892c964e1..f75f1d80c9 100644 --- a/docs/devices-next/tariffs/index.mdx +++ b/docs/devices-next/tariffs/index.mdx @@ -89,13 +89,13 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; +## Template Parameter `ngeso` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `region` | Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list | Beispiel: `1` | no | +| `postalcode` | Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. | Beispiel: `SW1` | no | + diff --git a/docs/devices-next/tariffs/nordpool-spot-prices.mdx b/docs/devices-next/tariffs/nordpool-spot-prices.mdx index b754f73fc2..0257bf98cc 100644 --- a/docs/devices-next/tariffs/nordpool-spot-prices.mdx +++ b/docs/devices-next/tariffs/nordpool-spot-prices.mdx @@ -1,6 +1,7 @@ --- title: Nordpool spot prices custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/nordpool.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,13 @@ Nordpool spot prices in day-ahead market for all markets in the Nordpool region. tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `nordpool` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `region` | | Beispiel: `GER`
Auswahl: `EE`, `LT`, `LV`, `AT`, `BE`
, `FR`, `GER`, `NL`, `PL`, `DK1`
, `DK2`, `FI`, `NO1`, `NO2`, `NO3`
, `NO4`, `NO5`, `SE1`, `SE2`, `SE3`
, `SE4`, `TEL`, `SYS` | no | +| `currency` | | Standard: `EUR`
Auswahl: `DKK`, `EUR`, `NOK`, `PLN`, `RON`, `SEK` | yes | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/octopus-energy-api.mdx b/docs/devices-next/tariffs/octopus-energy-api.mdx index f1628fe52c..7a0090081e 100644 --- a/docs/devices-next/tariffs/octopus-energy-api.mdx +++ b/docs/devices-next/tariffs/octopus-energy-api.mdx @@ -1,6 +1,7 @@ --- title: Octopus Energy API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-api.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ You can get the API key in the Octopus portal https://octopus.energy/dashboard/n apiKey: # Octopus Energy API Key. accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional)`} /> +## Template Parameter `octopus-api` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `apiKey` | Octopus Energy API Key. | | yes | +| `accountNumber` | Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. | | no | + diff --git a/docs/devices-next/tariffs/octopus-energy-product-code.mdx b/docs/devices-next/tariffs/octopus-energy-product-code.mdx index 620611ff49..019ceb4516 100644 --- a/docs/devices-next/tariffs/octopus-energy-product-code.mdx +++ b/docs/devices-next/tariffs/octopus-energy-product-code.mdx @@ -1,6 +1,7 @@ --- title: Octopus Energy Product Code custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-productcode.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,11 @@ import TabItem from '@theme/TabItem'; region: # The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] directDebit: true # Use Direct Debit tariff rates. (optional)`} /> +## Template Parameter `octopus-productcode` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `productCode` | The tariff code for your energy contract. Make sure this is set to your import tariff code. | Beispiel: `AGILE-FLEX-22-11-25` | yes | +| `region` | The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ | Auswahl: `A`, `B`, `C`, `D`, `E`
, `F`, `G`, `H`, `J`, `K`
, `L`, `M`, `N`, `P` | yes | +| `directDebit` | Use Direct Debit tariff rates. | Standard: `true` | no | + diff --git a/docs/devices-next/tariffs/open-meteo.mdx b/docs/devices-next/tariffs/open-meteo.mdx index c63ef9cf94..e77c9935f4 100644 --- a/docs/devices-next/tariffs/open-meteo.mdx +++ b/docs/devices-next/tariffs/open-meteo.mdx @@ -1,6 +1,7 @@ --- title: Open-Meteo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/open-meteo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -41,3 +42,20 @@ Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open- rossmodel: 0.0342 # Cooling type [Ross Model], Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) interval: 1h # optional`} /> +## Template Parameter `open-meteo` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Latitude
`lat` | | Beispiel: `55.7351` | yes | +| Longitude
`lon` | | Beispiel: `9.1275` | yes | +| Decline
`dec` | 0 = horizontal, 90 = vertical | Beispiel: `25` | yes | +| Maximum generator power
`kwp` | | Beispiel: `9.8`
Einheit: kWp | yes | +| Azimuth
`az` | -180 = north, -90 = east, 0 = south, 90 = west, 180 = north | | yes | +| AC Power \[kW\]
`ac` | | Standard: `1000` | no | +| Damping morning \[%\]
`dm` | | | no | +| Damping evening \[%\]
`de` | | | no | +| Efficiency \[%\]
`efficiency` | | Standard: `100` | no | +| Temperature coefficient
`alphatemp` | | Standard: `-0.004` | no | +| Cooling type \[Ross Model\]
`rossmodel` | Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) \[Paper\](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) | Standard: `0.0342` | no | +| `interval` | | Standard: `1h` | no | + diff --git a/docs/devices-next/tariffs/ostrom.mdx b/docs/devices-next/tariffs/ostrom.mdx index 016c687e81..040affa0d2 100644 --- a/docs/devices-next/tariffs/ostrom.mdx +++ b/docs/devices-next/tariffs/ostrom.mdx @@ -1,6 +1,7 @@ --- title: Ostrom custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ostrom.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ Create a 'Production Client' in the Ostrom developer portal: https://developer.o clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a contract: 100523456 # Only required if multiple contracts belong to the same user (optional)`} /> +## Template Parameter `ostrom` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `clientid` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | yes | +| `clientsecret` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a` | yes | +| `contract` | Only required if multiple contracts belong to the same user | Beispiel: `100523456` | no | + diff --git a/docs/devices-next/tariffs/pun-orario.mdx b/docs/devices-next/tariffs/pun-orario.mdx index a49676fd08..6233268936 100644 --- a/docs/devices-next/tariffs/pun-orario.mdx +++ b/docs/devices-next/tariffs/pun-orario.mdx @@ -1,6 +1,7 @@ --- title: PUN Orario custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/pun.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,11 @@ Price data from https://www.mercatoelettrico.org/it/. Often used for feeding int tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `pun` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx index 7f4d04cfb7..81bf2b8fa6 100644 --- a/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx +++ b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -1,6 +1,7 @@ --- title: SmartEnergy smartCONTROL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/smartenergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ import TabItem from '@theme/TabItem'; tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `smartenergy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/solcast.mdx b/docs/devices-next/tariffs/solcast.mdx index 122760dd28..1a855b2064 100644 --- a/docs/devices-next/tariffs/solcast.mdx +++ b/docs/devices-next/tariffs/solcast.mdx @@ -1,6 +1,7 @@ --- title: Solcast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/solcast.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,13 @@ Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) acc to: # End time of data retrieval, specified in full hours, e.g. "20" (optional) interval: 3h # optional`} /> +## Template Parameter `solcast` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `site` | ressource ID of your site | | yes | +| `token` | Solcast API Token | | yes | +| `from` | Start time of data retrieval, specified in full hours, e.g. "6" | | no | +| `to` | End time of data retrieval, specified in full hours, e.g. "20" | | no | +| `interval` | | Standard: `3h` | no | + diff --git a/docs/devices-next/tariffs/spotty-energie.mdx b/docs/devices-next/tariffs/spotty-energie.mdx index a69400e446..91596f7cf2 100644 --- a/docs/devices-next/tariffs/spotty-energie.mdx +++ b/docs/devices-next/tariffs/spotty-energie.mdx @@ -1,6 +1,7 @@ --- title: Spotty Energie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/spottyenergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `spottyenergy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `contractid` | You can get your contract id from the customer portal https://i.spottyenergie.at/ | Beispiel: `ffffffff-4444-6666-2222-aaaaaabbbbbb` | yes | +| `pricetype` | Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren | Standard: `CONSUMPTION`
Auswahl: `MARKET`, `CONSUMPTION`, `GENERATION` | yes | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/tibber.mdx b/docs/devices-next/tariffs/tibber.mdx index 55f139a2f7..d54e51eec1 100644 --- a/docs/devices-next/tariffs/tibber.mdx +++ b/docs/devices-next/tariffs/tibber.mdx @@ -1,6 +1,7 @@ --- title: Tibber custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/tibber.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,13 @@ Get your API token from the Tibber developer portal: https://developer.tibber.co tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +## Template Parameter `tibber` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `token` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | yes | +| `homeid` | Only required if you have multiple homes in your Tibber account. | Beispiel: `cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c` | no | +| Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | +| Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | +| Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | + diff --git a/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx index faa19fc55a..2f956fb480 100644 --- a/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx +++ b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -1,6 +1,7 @@ --- title: Victron VRM Solar Forecast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/victron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,11 @@ import TabItem from '@theme/TabItem'; token: # API access token, Tokens can be created in VRM in Preferences->Integrations interval: 1h # optional`} /> +## Template Parameter `victron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| VRM Site ID of the installation
`idsite` | The VRM Site ID is displayed in the installation settings under "General" | Beispiel: `123456` | yes | +| API access token
`token` | Tokens can be created in VRM in Preferences->Integrations | | yes | +| `interval` | | Standard: `1h` | no | + diff --git a/docs/devices-next/vehicles/aiways.mdx b/docs/devices-next/vehicles/aiways.mdx index c65e070b5a..743725cd33 100644 --- a/docs/devices-next/vehicles/aiways.mdx +++ b/docs/devices-next/vehicles/aiways.mdx @@ -1,6 +1,7 @@ --- title: Aiways custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/aiways.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `aiways` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/audi.mdx b/docs/devices-next/vehicles/audi.mdx index 1ef9502a5a..a11ce1a7c1 100644 --- a/docs/devices-next/vehicles/audi.mdx +++ b/docs/devices-next/vehicles/audi.mdx @@ -1,6 +1,7 @@ --- title: Audi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/audi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `audi` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WAUZZZ...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/bmw.mdx b/docs/devices-next/vehicles/bmw.mdx index 62a0da7c9a..07c90f9641 100644 --- a/docs/devices-next/vehicles/bmw.mdx +++ b/docs/devices-next/vehicles/bmw.mdx @@ -1,6 +1,7 @@ --- title: BMW custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/bmw.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,6 +43,28 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) region: EU # Region, [EU, NA] - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `bmw` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WBMW...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `hcaptcha` | | | yes | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `NA` | yes | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/citroen.mdx b/docs/devices-next/vehicles/citroen.mdx index 429286ed1e..2c7a49bd31 100644 --- a/docs/devices-next/vehicles/citroen.mdx +++ b/docs/devices-next/vehicles/citroen.mdx @@ -1,6 +1,7 @@ --- title: Citroën custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/citroen.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `citroen` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| `accessToken` | | | yes | +| `refreshToken` | | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/dacia.mdx b/docs/devices-next/vehicles/dacia.mdx index f7f0346884..138713b0ef 100644 --- a/docs/devices-next/vehicles/dacia.mdx +++ b/docs/devices-next/vehicles/dacia.mdx @@ -1,6 +1,7 @@ --- title: Dacia custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/dacia.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,6 +37,26 @@ import TabItem from '@theme/TabItem'; identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `dacia` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/ds.mdx b/docs/devices-next/vehicles/ds.mdx index 67af522764..eb39abd430 100644 --- a/docs/devices-next/vehicles/ds.mdx +++ b/docs/devices-next/vehicles/ds.mdx @@ -1,6 +1,7 @@ --- title: DS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ds.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `ds` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| `accessToken` | | | yes | +| `refreshToken` | | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/evnotify.mdx b/docs/devices-next/vehicles/evnotify.mdx index a511614830..5e5ef1dee1 100644 --- a/docs/devices-next/vehicles/evnotify.mdx +++ b/docs/devices-next/vehicles/evnotify.mdx @@ -1,6 +1,7 @@ --- title: evNotify custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/evnotify.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,19 @@ import TabItem from '@theme/TabItem'; identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `evnotify` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `akey` | | | yes | +| `token` | | | yes | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/fiat.mdx b/docs/devices-next/vehicles/fiat.mdx index 6c69c79844..1bb7d6f668 100644 --- a/docs/devices-next/vehicles/fiat.mdx +++ b/docs/devices-next/vehicles/fiat.mdx @@ -1,6 +1,7 @@ --- title: Fiat custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,6 +39,27 @@ import TabItem from '@theme/TabItem'; identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `fiat` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `ZFAE...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `pin` | Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. | | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/ford.mdx b/docs/devices-next/vehicles/ford.mdx index 4dba08939b..92ea2aeb8f 100644 --- a/docs/devices-next/vehicles/ford.mdx +++ b/docs/devices-next/vehicles/ford.mdx @@ -1,6 +1,7 @@ --- title: Ford custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ford-connect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -41,3 +42,23 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `ford-connect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| FordConnect API Client ID
`clientid` | Setup at https://developer.ford.com | | yes | +| FordConnect API Client Secret
`clientsecret` | Setup at https://developer.ford.com | | yes | +| `accessToken` | | | yes | +| `refreshToken` | | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WF0FXX...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/generic-vehicle-without-api.mdx b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx index 8c2fc02fad..1bd97d28c2 100644 --- a/docs/devices-next/vehicles/generic-vehicle-without-api.mdx +++ b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -1,6 +1,7 @@ --- title: Generic vehicle (without API) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/offline.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,17 @@ import TabItem from '@theme/TabItem'; identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `offline` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/hyundai-bluelink.mdx b/docs/devices-next/vehicles/hyundai-bluelink.mdx index da17034532..ea1887b90e 100644 --- a/docs/devices-next/vehicles/hyundai-bluelink.mdx +++ b/docs/devices-next/vehicles/hyundai-bluelink.mdx @@ -1,6 +1,7 @@ --- title: Hyundai Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/hyundai.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Some models (e.g. Kona) switch internally to 2 phases at low charging currents ( priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `hyundai` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Language
`language` | | Standard: `en`
Auswahl: `en`, `de` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/index.mdx b/docs/devices-next/vehicles/index.mdx index 9229186377..d5d2e93d85 100644 --- a/docs/devices-next/vehicles/index.mdx +++ b/docs/devices-next/vehicles/index.mdx @@ -34,13 +34,13 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; + +## Template Parameter `ioBroker.bmw` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Vehicle Identification Number
`vin` | BMW VehicleIdentificationNumber | Beispiel: `WBA8E9G50GM091234` | yes | +| ioBroker URL inlcuding ioBroker.simple-api Port
`uri` | HTTP(S) address | | yes | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Instance ID
`id` | | | no | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/iobrokerbmw.mdx b/docs/devices-next/vehicles/iobrokerbmw.mdx deleted file mode 100644 index d8c2750002..0000000000 --- a/docs/devices-next/vehicles/iobrokerbmw.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: ioBroker.bmw -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ioBroker.bmw.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ioBroker.bmw - -ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api - - - - diff --git a/docs/devices-next/vehicles/iso15118.mdx b/docs/devices-next/vehicles/iso15118.mdx index 6aaa231ec5..dde55a6588 100644 --- a/docs/devices-next/vehicles/iso15118.mdx +++ b/docs/devices-next/vehicles/iso15118.mdx @@ -1,6 +1,7 @@ --- title: ISO15118 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/iso15118.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,17 @@ Otherwise the vehicle cannot be put into sleep mode. identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `iso15118` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/jeep.mdx b/docs/devices-next/vehicles/jeep.mdx index 77f6a2b580..a2dba1d04f 100644 --- a/docs/devices-next/vehicles/jeep.mdx +++ b/docs/devices-next/vehicles/jeep.mdx @@ -1,6 +1,7 @@ --- title: Jeep custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,6 +39,27 @@ import TabItem from '@theme/TabItem'; identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `fiat` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `ZFAE...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `pin` | Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. | | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/kia-bluelink.mdx b/docs/devices-next/vehicles/kia-bluelink.mdx index ef54efdaf4..315116913f 100644 --- a/docs/devices-next/vehicles/kia-bluelink.mdx +++ b/docs/devices-next/vehicles/kia-bluelink.mdx @@ -1,6 +1,7 @@ --- title: Kia Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/kia.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Some models (e.g. Niro EV) switch internally to 2 phases at low charging current priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `kia` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Language
`language` | | Standard: `en`
Auswahl: `en`, `de` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/mercedes-benz.mdx b/docs/devices-next/vehicles/mercedes-benz.mdx index ab09b0c5e4..a4dab6ea0d 100644 --- a/docs/devices-next/vehicles/mercedes-benz.mdx +++ b/docs/devices-next/vehicles/mercedes-benz.mdx @@ -1,6 +1,7 @@ --- title: Mercedes-Benz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mercedes.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -44,3 +45,23 @@ Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/ priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `mercedes` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | yes | +| `accessToken` | | | yes | +| `refreshToken` | | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/mg.mdx b/docs/devices-next/vehicles/mg.mdx index be2503dc94..a6ad7bfb48 100644 --- a/docs/devices-next/vehicles/mg.mdx +++ b/docs/devices-next/vehicles/mg.mdx @@ -1,6 +1,7 @@ --- title: MG custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,22 @@ import TabItem from '@theme/TabItem'; cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) region: EU # Region, [EU, AU]`} /> +## Template Parameter `mg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `AU` | yes | + diff --git a/docs/devices-next/vehicles/mg2mqtt.mdx b/docs/devices-next/vehicles/mg2mqtt.mdx index 5089bef531..2f468e07a0 100644 --- a/docs/devices-next/vehicles/mg2mqtt.mdx +++ b/docs/devices-next/vehicles/mg2mqtt.mdx @@ -1,6 +1,7 @@ --- title: mg2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg2mqtt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/S identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `mg2mqtt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Timeout
`timeout` | | Standard: `1h`
Beispiel: `10s` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/mini.mdx b/docs/devices-next/vehicles/mini.mdx index 6bda216cec..a6f5e61d03 100644 --- a/docs/devices-next/vehicles/mini.mdx +++ b/docs/devices-next/vehicles/mini.mdx @@ -1,6 +1,7 @@ --- title: Mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mini.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,6 +43,28 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) region: EU # Region, [EU, NA] - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `mini` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WBMW...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `hcaptcha` | | | yes | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `NA` | yes | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/mz2mqtt.mdx b/docs/devices-next/vehicles/mz2mqtt.mdx index 185d2cb80a..06f0ad0d41 100644 --- a/docs/devices-next/vehicles/mz2mqtt.mdx +++ b/docs/devices-next/vehicles/mz2mqtt.mdx @@ -1,6 +1,7 @@ --- title: mz2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mz2mqtt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,19 @@ myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation h priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) timeout: 720h # Timeout, optional`} /> +## Template Parameter `mz2mqtt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Timeout
`timeout` | | Standard: `720h`
Beispiel: `10s` | no | + diff --git a/docs/devices-next/vehicles/nissan-ariya.mdx b/docs/devices-next/vehicles/nissan-ariya.mdx index 35f5c15ef1..ae050f9728 100644 --- a/docs/devices-next/vehicles/nissan-ariya.mdx +++ b/docs/devices-next/vehicles/nissan-ariya.mdx @@ -1,6 +1,7 @@ --- title: Nissan Ariya custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan-ariya.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `nissan-ariya` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx index 668fab14bb..c89fe1235e 100644 --- a/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx +++ b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -1,6 +1,7 @@ --- title: Nissan Leaf (pre 2019) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/carwings.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `carwings` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/nissan-leaf.mdx b/docs/devices-next/vehicles/nissan-leaf.mdx index e3e18ed656..5962597639 100644 --- a/docs/devices-next/vehicles/nissan-leaf.mdx +++ b/docs/devices-next/vehicles/nissan-leaf.mdx @@ -1,6 +1,7 @@ --- title: Nissan Leaf custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `nissan` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/niu-e-scooter.mdx b/docs/devices-next/vehicles/niu-e-scooter.mdx index 0661329040..70509aabec 100644 --- a/docs/devices-next/vehicles/niu-e-scooter.mdx +++ b/docs/devices-next/vehicles/niu-e-scooter.mdx @@ -1,6 +1,7 @@ --- title: NIU E-Scooter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/niu-e-scooter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,14 @@ import TabItem from '@theme/TabItem'; serial: # Scooter serial number like shown in NIU app capacity: 4 # Battery capacity (kWh), optional`} /> +## Template Parameter `niu-e-scooter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `scooter`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Scooter serial number like shown in NIU app
`serial` | | | yes | +| Battery capacity
`capacity` | | Standard: `4`
Beispiel: `50`
Einheit: kWh | no | + diff --git a/docs/devices-next/vehicles/opel.mdx b/docs/devices-next/vehicles/opel.mdx index e6c7004492..b038f1e95d 100644 --- a/docs/devices-next/vehicles/opel.mdx +++ b/docs/devices-next/vehicles/opel.mdx @@ -1,6 +1,7 @@ --- title: Opel custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/opel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `opel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| `accessToken` | | | yes | +| `refreshToken` | | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx index 8dbb58863d..ff76082257 100644 --- a/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx +++ b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -1,6 +1,7 @@ --- title: Open Vehicle Monitoring System custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ovms.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -41,3 +42,22 @@ Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Veh server: dexters-web.de cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `ovms` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| `vehicleid` | | | yes | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| `server` | | Standard: `dexters-web.de` | yes | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/peugeot.mdx b/docs/devices-next/vehicles/peugeot.mdx index 90b6167b5f..aca315f31e 100644 --- a/docs/devices-next/vehicles/peugeot.mdx +++ b/docs/devices-next/vehicles/peugeot.mdx @@ -1,6 +1,7 @@ --- title: Peugeot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/peugeot.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `peugeot` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| `accessToken` | | | yes | +| `refreshToken` | | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/polestar.mdx b/docs/devices-next/vehicles/polestar.mdx index a55cc9f6d8..1ba09cf783 100644 --- a/docs/devices-next/vehicles/polestar.mdx +++ b/docs/devices-next/vehicles/polestar.mdx @@ -1,6 +1,7 @@ --- title: Polestar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/polestar.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `polestar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `LPSVS...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/psa-car-controller.mdx b/docs/devices-next/vehicles/psa-car-controller.mdx index 0c52d668db..1c8f459346 100644 --- a/docs/devices-next/vehicles/psa-car-controller.mdx +++ b/docs/devices-next/vehicles/psa-car-controller.mdx @@ -1,6 +1,7 @@ --- title: PSA Car Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/flobz.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,20 @@ Remote Control of PSA car https://github.com/flobz/psa_car_controller priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) wakeup_alt: false # alternative wakeup-code; could lead to increased discharge of the 12V battery. (optional)`} /> +## Template Parameter `flobz` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| `url` | | Beispiel: `http://192.0.2.2` | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| `wakeup_alt` | alternative wakeup-code; could lead to increased discharge of the 12V battery. | | no | + diff --git a/docs/devices-next/vehicles/renault.mdx b/docs/devices-next/vehicles/renault.mdx index 62af5d8465..52ba787fdb 100644 --- a/docs/devices-next/vehicles/renault.mdx +++ b/docs/devices-next/vehicles/renault.mdx @@ -1,6 +1,7 @@ --- title: Renault custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/renault.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,22 @@ import TabItem from '@theme/TabItem'; cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) wakeupmode: default # Wakeup mechanism, [default, alternative, MY24] (optional)`} /> +## Template Parameter `renault` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WREN...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| Wakeup mechanism
`wakeupmode` | | Standard: `default`
Auswahl: `default`, `alternative`, `MY24` | no | + diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx index 8f58026bfe..cd14ce34be 100644 --- a/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -1,6 +1,7 @@ --- title: Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/seat.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `seat` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx index 2b0ecabc22..748b2c4c31 100644 --- a/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -1,6 +1,7 @@ --- title: Seat CupraConnect Gen4 (Born, Formentor, Tavascan) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/cupra.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,6 +37,26 @@ import TabItem from '@theme/TabItem'; identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +## Template Parameter `cupra` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/skoda-enyaq.mdx b/docs/devices-next/vehicles/skoda-enyaq.mdx index cbdf283450..36fdca4bc5 100644 --- a/docs/devices-next/vehicles/skoda-enyaq.mdx +++ b/docs/devices-next/vehicles/skoda-enyaq.mdx @@ -1,6 +1,7 @@ --- title: Skoda Enyaq custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/enyaq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,22 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `enyaq` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Timeout
`timeout` | | Standard: `10s`
Beispiel: `10s` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/smart-1.mdx b/docs/devices-next/vehicles/smart-1.mdx new file mode 100644 index 0000000000..aedff82345 --- /dev/null +++ b/docs/devices-next/vehicles/smart-1.mdx @@ -0,0 +1,62 @@ +--- +title: Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smart + + + +## Template Parameter `smart-hello` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | + diff --git a/docs/devices-next/vehicles/smart-eq.mdx b/docs/devices-next/vehicles/smart-eq.mdx index e2908cf38e..dd9a74a8ee 100644 --- a/docs/devices-next/vehicles/smart-eq.mdx +++ b/docs/devices-next/vehicles/smart-eq.mdx @@ -1,6 +1,7 @@ --- title: Smart EQ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -44,3 +45,23 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `smart` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | yes | +| `accessToken` | | | yes | +| `refreshToken` | | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/smart.mdx b/docs/devices-next/vehicles/smart.mdx deleted file mode 100644 index 801cd0529d..0000000000 --- a/docs/devices-next/vehicles/smart.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Smart -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Smart - - - diff --git a/docs/devices-next/vehicles/tesla-ble.mdx b/docs/devices-next/vehicles/tesla-ble.mdx index 40dcffe600..5fd32582ba 100644 --- a/docs/devices-next/vehicles/tesla-ble.mdx +++ b/docs/devices-next/vehicles/tesla-ble.mdx @@ -1,6 +1,7 @@ --- title: Tesla BLE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla-ble.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `tesla-ble` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Vehicle Identification Number
`vin` | Required for BLE connection | Beispiel: `W...` | yes | +| `url` | URL of the Tesla BLE HTTP Proxy | Beispiel: `http://192.168.178.27` | yes | +| Port
`port` | Port of the Tesla BLE HTTP Proxy | Standard: `8080`
Beispiel: `8080` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/tesla.mdx b/docs/devices-next/vehicles/tesla.mdx index f09ea4d2d2..fc5c6b4365 100644 --- a/docs/devices-next/vehicles/tesla.mdx +++ b/docs/devices-next/vehicles/tesla.mdx @@ -1,6 +1,7 @@ --- title: Tesla custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -57,3 +58,24 @@ More information and alternatives can be found in [our blog post](https://docs.e proxyToken: # Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `tesla` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `clientId` | Client ID of your \[Tesla Developer App\](https://developer.tesla.com/dashboard). | | yes | +| `accessToken` | from \[myteslamate.com\](https://app.myteslamate.com/). | | yes | +| `refreshToken` | from \[myteslamate.com\](https://app.myteslamate.com/). | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| `commandProxy` | When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the \[myteslamate.com\](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example \[TeslaBleHttpProxy\](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. | Standard: `https://api.myteslamate.com` | no | +| `proxyToken` | Token for the \[myteslamate.com\](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/teslalogger.mdx b/docs/devices-next/vehicles/teslalogger.mdx index dd0582ab1e..6a2c0eb3b4 100644 --- a/docs/devices-next/vehicles/teslalogger.mdx +++ b/docs/devices-next/vehicles/teslalogger.mdx @@ -1,6 +1,7 @@ --- title: TeslaLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslalogger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `teslalogger` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| TeslaLogger CarID
`id` | | Standard: `1` | no | +| `url` | | Beispiel: `http://192.0.2.2` | yes | +| Port
`port` | | Standard: `5000`
Beispiel: `5000` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/teslamate.mdx b/docs/devices-next/vehicles/teslamate.mdx index cc5c79f0f2..44eed6b68c 100644 --- a/docs/devices-next/vehicles/teslamate.mdx +++ b/docs/devices-next/vehicles/teslamate.mdx @@ -1,6 +1,7 @@ --- title: TeslaMate custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslamate.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -35,3 +36,18 @@ Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT bro identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `teslamate` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Vehicle ID
`id` | | Standard: `1` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/tessie.mdx b/docs/devices-next/vehicles/tessie.mdx index 4bc93d2f84..5cddb14b5b 100644 --- a/docs/devices-next/vehicles/tessie.mdx +++ b/docs/devices-next/vehicles/tessie.mdx @@ -1,6 +1,7 @@ --- title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tessie.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,19 @@ Connect your Tesla using the Tessie API. This will never wake up the car, pollin identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `tessie` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Vehicle VIN
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Tessie API Token
`token` | | | yes | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/toyota.mdx b/docs/devices-next/vehicles/toyota.mdx index ec1ba5771b..c482188ac4 100644 --- a/docs/devices-next/vehicles/toyota.mdx +++ b/docs/devices-next/vehicles/toyota.mdx @@ -1,6 +1,7 @@ --- title: Toyota custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/toyota.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,3 +41,21 @@ Requires Toyota Connected Services Account. priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `toyota` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `JT...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/tronity.mdx b/docs/devices-next/vehicles/tronity.mdx index 34feaf523d..8477a2a02f 100644 --- a/docs/devices-next/vehicles/tronity.mdx +++ b/docs/devices-next/vehicles/tronity.mdx @@ -1,6 +1,7 @@ --- title: Tronity custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tronity.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,23 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `tronity` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Tronity API Client ID
`clientid` | Setup at https://app.tronity.tech | | yes | +| Tronity API Client Secret
`clientsecret` | Setup at https://app.tronity.tech | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx index 01590a0805..007bce4d78 100644 --- a/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx +++ b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen We Connect ID custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/vw.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,5 +41,28 @@ e-Golf, e-Up, ID family maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> + +## Template Parameter `vw` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WVWZZZ...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Timeout
`timeout` | | Standard: `10s`
Beispiel: `10s` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | +| 1A current control
`coarsecurrent` | Vehicle supports 1A current steps only | | no | +| Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/vehicles/volvo.mdx b/docs/devices-next/vehicles/volvo.mdx index dd4e473fe4..2c6aff7d7b 100644 --- a/docs/devices-next/vehicles/volvo.mdx +++ b/docs/devices-next/vehicles/volvo.mdx @@ -1,6 +1,7 @@ --- title: Volvo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo-connected.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -50,3 +51,22 @@ Log in with your Volvo account and allow access to the data. If the authorizatio identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `volvo-connected` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| `vccapikey` | VCC API Key of your \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | +| `clientId` | Client ID of your \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | +| `clientSecret` | Client Secret of your \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | +| `redirectUri` | Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WF0FXX...` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/volvo2mqtt.mdx b/docs/devices-next/vehicles/volvo2mqtt.mdx index 7964106228..ad9ad19cc7 100644 --- a/docs/devices-next/vehicles/volvo2mqtt.mdx +++ b/docs/devices-next/vehicles/volvo2mqtt.mdx @@ -1,6 +1,7 @@ --- title: volvo2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo2mqtt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,19 @@ Requires MQTT broker configuration and a volvo2mqtt installation https://github. identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +## Template Parameter `volvo2mqtt` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | +| Timeout
`timeout` | | Standard: `720h`
Beispiel: `10s` | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | + diff --git a/docs/devices-next/vehicles/zero-motorcycles.mdx b/docs/devices-next/vehicles/zero-motorcycles.mdx index 8ebd7d9217..6c55f5a218 100644 --- a/docs/devices-next/vehicles/zero-motorcycles.mdx +++ b/docs/devices-next/vehicles/zero-motorcycles.mdx @@ -1,6 +1,7 @@ --- title: Zero Motorcycles custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/zero.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +## Template Parameter `zero` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Username
`user` | e.g. email address, user id, etc. | | yes | +| Password
`password` | Use single quotes in case of leading zeros | | yes | +| Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | +| Title
`title` | Will be displayed in the user interface | | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | +| Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | +| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | +| Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | +| Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | +| Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | +| Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | + diff --git a/docs/devices/chargers.mdx b/docs/devices/chargers.mdx index d9acd7b6eb..93becf2722 100644 --- a/docs/devices/chargers.mdx +++ b/docs/devices/chargers.mdx @@ -89,7 +89,7 @@ Erfordert Firmware >= 1.6.5 -### Terra AC +### Terra AC (OCPP) @@ -119,7 +119,33 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C ## ABL -### eM4 (SBCx) +### eM4 Single (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + + + + + +### eM4 Single (SBCx) @@ -150,28 +176,56 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH1 +### eM4 Twin (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + + + + + + + +### eM4 Twin (SBCx) + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> @@ -179,7 +233,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH2 +### eMH1 @@ -208,27 +262,28 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -## ABL Sursum - ### eMH2 - + :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional`} /> @@ -236,7 +291,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH3 +### eMH2 (OCPP) @@ -262,7 +317,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH4 +### eMH3 (OCPP) @@ -313,7 +368,7 @@ Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus exte -### Eve +### Eve (OCPP) @@ -528,29 +583,6 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü ## Ampure -### Live - - - -Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. - - - - - - - - - ### NEXT @@ -979,7 +1011,32 @@ Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigescha -## CUBOS C11E, C22E +## CUBOS + +### C11E + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + + + + +### C22E @@ -2231,7 +2288,37 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri -## Free2Move eProWallbox +## Free2Move + +### eProWallbox + + + + + + + + + + + +### eProWallbox Move @@ -2285,7 +2372,7 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri -## Fronius Wattpilot +## Fronius Wattpilot (OCPP) @@ -2311,7 +2398,78 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri -## Garo GLB, GLB+, LS4, LS4 compact +## Garo + +### GLB + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + + + + +### GLB+ + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + + + + +### LS4 + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + + + + + + +### LS4 compact @@ -2356,7 +2514,7 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak -### Charger Gemini +### Charger Gemini (OCPP) @@ -2438,7 +2596,7 @@ Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss akt -### Charger PRO +### Charger PRO (OCPP) @@ -2484,7 +2642,7 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak -### Charger V3 +### Charger V3 (OCPP) @@ -2512,15 +2670,22 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak ## Hardy Barth -### cPH2 +### cPH1 +Als Betriebsmodus muss `manual` ausgewählt sein + + template: hardybarth-ecb1 + host: 192.0.2.2 # IP-Adresse oder Hostname`} advanced={`chargers: + - name: my_charger + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP-Adresse oder Hostname + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> @@ -2528,7 +2693,7 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak -### cPμ2 +### cPH2 @@ -2544,22 +2709,15 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak -## HardyBarth cPH1 +### cPμ2 -Als Betriebsmodus muss `manual` ausgewählt sein - 1 Ladepunkt), optional`} /> + template: hardybarth-salia + host: 192.0.2.2 # IP-Adresse oder Hostname`} /> @@ -5977,6 +6135,24 @@ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gel + + + + + + + + +### Go (OCPP) + + + OCPP Native mode https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ @@ -5999,24 +6175,6 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - - - - -### Go - - - - - - - diff --git a/docs/devices/meters.mdx b/docs/devices/meters.mdx index fdf4d85d74..1209967729 100644 --- a/docs/devices/meters.mdx +++ b/docs/devices/meters.mdx @@ -215,7 +215,180 @@ Die meisten modernen PV-Technikkomponenten, insbesondere Wechselrichter und Batt -## ABB A43, A44, B23, B24 +## ABB + +### A43 + + + + + + + + + + + + + + + + + + + + + + +### A44 + + + + + + + + + + + + + + + + + + + + + + +### B23 + + + + + + + + + + + + + + + + + + + + + + +### B24 @@ -272,7 +445,7 @@ Die meisten modernen PV-Technikkomponenten, insbesondere Wechselrichter und Batt -## Acrel ADW300 Wireless Metering Meter +## Acrel ADW300 @@ -3567,7 +3740,7 @@ Solar API sollte nur als Fallback genutzt werden. Die Integration über Modbus i Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt. -**Achtung**: Die aktive Batteriesteuerung sollte nur verwendet werden, wenn keine weiteren Einstellungen für die zeitabhängige Batteriesteuerung in der Wechselrichter-Konfiguration unter "Energiemanagement" - "Batteriemanagement" getätigt wurden, denn bestehende Einstellungen werden überschrieben. +**Achtung**: Die aktive Batteriesteuerung sollte nur verwendet werden, wenn keine weiteren Einstellungen für die zeitabhängige Batteriesteuerung in der Wechselrichter-Konfiguration unter "Energiemanagement" - "Batteriemanagement" getätigt wurden, denn bestehende Einstellungen werden überschrieben. Es ist der geeignete Konfigurationspfad auszuwählen! @@ -3579,7 +3752,15 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} advanced={`meters: + - name: my_grid + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> @@ -3593,7 +3774,15 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} advanced={`meters: + - name: my_pv + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> @@ -3615,7 +3804,8 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - capacity: 50 # Akkukapazität (kWh), optional`} /> + capacity: 50 # Akkukapazität (kWh), optional + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> @@ -5206,7 +5396,78 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering -## Janitza B series, UMG series +## Janitza + +### B series + + + + + + + + + + + + + + + + + + + + + + +### UMG series @@ -5418,6 +5679,39 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering + + + + + +### Piko + + + + + + + + + + + + + + + + + @@ -5438,6 +5732,39 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering + + +### Piko BA + + + + + + + + + + + + + + + + + + + + ### Piko Hybrid @@ -5504,39 +5831,6 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering - - -### Piko, Piko BA - - - - - - - - - - - - - - - - - - - - ### Plenticore Hybrid @@ -6373,7 +6667,66 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries -## Orno OR-WE-516, OR-WE-517 +## ORNO + +### OR-WE-516 + + + + + + + + + + + + + + + + + + + + + + +### OR-WE-517 @@ -6610,11 +6963,13 @@ Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `int -## QCells Hybrid-Wechselrichter (Cloud) +## Qcells + +### Hybrid-Wechselrichter (Cloud) -Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. +Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. @@ -6626,7 +6981,7 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. type: template template: qcells-hybrid-cloud usage: grid - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen.`} /> @@ -6639,7 +6994,7 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. type: template template: qcells-hybrid-cloud usage: pv - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen.`} /> @@ -6652,13 +7007,13 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen.`} advanced={`meters: - name: my_battery type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -6669,7 +7024,7 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. -## Qcells Q.HOME ESS HYB-G3 +### Q.HOME ESS HYB-G3 @@ -6923,7 +7278,66 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. -## Saia-Burgess Controls ALE3, AWD3 +## Saia-Burgess Controls (SBC) + +### ALE3 + + + + + + + + + + + + + + + + + + + + + + +### AWD3 @@ -8219,7 +8633,7 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio ## Smartfox -### Box, Reg, Reg extended +### Box @@ -8266,7 +8680,7 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio -### Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) +### Light (EM2 firmware) @@ -8331,13 +8745,11 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio -## SofarSolar - -### HYD 3…6K-EP +### Pro - + -Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -8345,51 +8757,15 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -8399,108 +8775,33 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> - + + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -8509,11 +8810,11 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T -### HYD 5…20K-3PH +### Pro 2 - + -Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -8521,51 +8822,15 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -8575,108 +8840,257 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> - + + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> + + + + + + + + +### Pro Light + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Pro Light 2 + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Reg + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Reg extended + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + @@ -8685,7 +9099,9 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T -### Inverter, Hybrid Inverter +## SofarSolar + +### Hybrid Inverter @@ -8808,7 +9224,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T -### SOFAR 5…24KTL-G3 +### HYD 3…6K-EP @@ -8984,7 +9400,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T -### SOFAR 80…136KTL +### HYD 5…20K-3PH @@ -9160,7 +9576,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T -## Solaranzeige Solaranzeige +### Inverter @@ -9170,22 +9586,27 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> @@ -9195,22 +9616,81 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T + + + + + + + + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} advanced={`meters: + - name: my_battery + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -9219,14 +9699,11 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T -## SolarEdge - -### Hybrid Inverter +### SOFAR 5…24KTL-G3 -Nur ein System kann und darf zeitgleich eine Modbus TCP-Verbindung zum Wechselrichter haben! -Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "Remote" stehen. +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. @@ -9234,7 +9711,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -9290,7 +9765,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -9347,7 +9820,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> @@ -9403,11 +9875,11 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R -### Wechselrichter +### SOFAR 80…136KTL - + -Nur ein System kann und darf auf den Wechselrichter zugreifen! +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. @@ -9415,7 +9887,7 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! + port: 8899 # Port`} advanced={`meters: + - name: my_grid + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -9446,7 +9941,7 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! + port: 8899 # Port`} advanced={`meters: + - name: my_pv + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> - - - - -## Solarlog - - - -Wir empfehlen dieses Gerät für den Netzbezug/Einspeisewerte nur zu verwenden, wenn kein anderes Gerät diese Daten liefert. -Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall für die erwähnten Werte verwendet werden! - - - + - + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port`} advanced={`meters: + - name: my_battery + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> + + + + + + + + +## Solaranzeige Solaranzeige + + + + + + + + @@ -9502,10 +10086,22 @@ Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall f + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional)`} advanced={`meters: + - name: my_pv + type: template + template: solaranzeige + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> @@ -9514,13 +10110,14 @@ Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall f -## SolarMax +## SolarEdge -### MAX.STORAGE / MAX.STORAGE Ultimate +### Hybrid Inverter -Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. +Nur ein System kann und darf zeitgleich eine Modbus TCP-Verbindung zum Wechselrichter haben! +Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "Remote" stehen. @@ -9528,24 +10125,52 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit @@ -9556,24 +10181,52 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit @@ -9585,24 +10238,52 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit @@ -9613,39 +10294,249 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit -### SolarMax SMT +### Wechselrichter +Nur ein System kann und darf auf den Wechselrichter zugreifen! + + + + - - + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional`} /> - -### SP Series Inverter - + + + + + + + + + + +## Solarlog + + + +Wir empfehlen dieses Gerät für den Netzbezug/Einspeisewerte nur zu verwenden, wenn kein anderes Gerät diese Daten liefert. +Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall für die erwähnten Werte verwendet werden! + + + + + + + + + + + + + + + + + + + + +## SolarMax + +### MAX.STORAGE / MAX.STORAGE Ultimate + + + +Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### SolarMax SMT + + + + + + + + + +### SP Series Inverter + + + + @@ -9655,7 +10546,58 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit ## Solarwatt -### EnergyManager, EnergyManager Pro +### EnergyManager + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### EnergyManager Pro @@ -10264,7 +11206,7 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. ## Sonnen -### comfort, eco 5, eco 6, oem 6.5 +### comfort @@ -10335,13 +11277,9 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. -### sonnenBatterie - - +### eco 5 -Für die aktive Batteriesteuerung muss über das Webinterface der sonnenBatterie (unter Software-Integration) das "JSON Write API" aktiviert und das dort generierte API-Token in der Batteriekonfiguration unter `token` eingetragen werden. -Als Betriebsart der sonnenBatterie werden die beiden Modi "Eigenverbrauch" (Standard) und "Time-of-use" unterstützt. Der Modus kann über den Parameter `defaultmode` an die Konfiguration der sonnenBatterie angepasst werden. -Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBatterie über den Parameter `maxchargepower` angepasst werden. + @@ -10349,7 +11287,224 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat + + + + + + + + + + + + + + + + + + + + + + +### eco 6 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### oem 6.5 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### sonnenBatterie + + + +Für die aktive Batteriesteuerung muss über das Webinterface der sonnenBatterie (unter Software-Integration) das "JSON Write API" aktiviert und das dort generierte API-Token in der Batteriekonfiguration unter `token` eingetragen werden. +Als Betriebsart der sonnenBatterie werden die beiden Modi "Eigenverbrauch" (Standard) und "Time-of-use" unterstützt. Der Modus kann über den Parameter `defaultmode` an die Konfiguration der sonnenBatterie angepasst werden. +Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBatterie über den Parameter `maxchargepower` angepasst werden. + + + + + @@ -11736,7 +12891,9 @@ Folgende Apps ermöglichen das Erstellen des Tokens: -## VARTA pulse, pulse neo, element +## VARTA + +### element @@ -11793,13 +12950,11 @@ PV nur verfügbar mit PV-Sensor -## Victron - -### EM24 +### pulse -EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. +PV nur verfügbar mit PV-Sensor @@ -11807,44 +12962,160 @@ EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschl + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional`} /> - + + + + + + + + + + + + + + + + +### pulse neo + + + +PV nur verfügbar mit PV-Sensor + + + + + + + + + + + + + + + + + + + + + + + + + + + +## Victron + +### EM24 + + + +EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. + + + + + + + + + + + + @@ -12574,7 +13845,9 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh -## ZCS Azzurro Inverter, Hybrid Inverter +## ZCS Azzurro + +### Hybrid Inverter @@ -12697,22 +13970,67 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh -## Zendure Hyper 2000 +### Inverter - + + + + + + + + + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> @@ -12722,21 +14040,51 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -12745,9 +14093,57 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh -## Zuidwijk - -### SlimmeLezer(+) +## Zendure Hyper 2000 + + + + + + + + + + + + + + + + + + + + + + +## Zuidwijk + +### SlimmeLezer(+) @@ -13348,115 +14744,453 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. - + + + + +### Volkszähler + +#### HTTP API + + + + + + + + + +#### HTTP API, Import & Export + + + + + + + + + +#### WebSocket API + + + + + + + + + +### vzlogger + + + + + + + + + +## Schaltbare Steckdosen + +### AVM FritzDECT + + + + + + + + + + + + + + + + + + + + + + +### Homematic IP + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### myStrom Switch + + + + + + + + + + + + + + + + + + + + + + +### Shelly + +#### 1PM + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +#### 1PM mini + + + + + + + + + + + + - + -### Volkszähler -#### HTTP API - + + + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> + + + -#### HTTP API, Import & Export +#### EM + + + + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> - + + -#### WebSocket API + - + + + + + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> + + + -### vzlogger +#### Plug S + + + - - - - - -## Schaltbare Steckdosen + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> -### AVM FritzDECT - - - + + + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> @@ -13466,12 +15200,12 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> @@ -13480,7 +15214,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. -### Homematic IP +#### PM mini @@ -13490,75 +15224,96 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. + + + + + + + + channel: 0 # optional`} /> - + + + + + + + + + +#### Pro 1PM + + + + + + + + channel: 0 # optional`} /> - + + + + + + + + + channel: 0 # optional`} /> @@ -13567,19 +15322,37 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. -### myStrom Switch +#### Pro 3EM (monophase mode) - + + + + + + + + + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> @@ -13589,9 +15362,12 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional`} /> @@ -13600,7 +15376,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. -### Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode +#### Pro EM diff --git a/docs/devices/smartswitches.mdx b/docs/devices/smartswitches.mdx index bbab8f9ec3..3a109fd812 100644 --- a/docs/devices/smartswitches.mdx +++ b/docs/devices/smartswitches.mdx @@ -243,7 +243,90 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al -### Shelly +### Shelly + +#### 1 + + + + + + + +#### Plug S + + + + + + + +#### Plus 1 + + + + + + + +#### Pro 1 @@ -207,7 +207,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> @@ -279,7 +279,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> @@ -387,7 +387,7 @@ Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> @@ -533,7 +533,7 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) region: EU # Region, [EU, NA] - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> @@ -836,7 +836,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> @@ -906,7 +906,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> @@ -1067,7 +1067,7 @@ e-Golf, e-Up, ID Familie identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> @@ -1250,15 +1250,15 @@ ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api template: ioBroker.bmw title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - uri: # URI, HTTP(S) Adresse`} advanced={`vehicles: + vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer + uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse`} advanced={`vehicles: - name: my_car type: template template: ioBroker.bmw title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - uri: # URI, HTTP(S) Adresse + vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer + uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) @@ -1266,8 +1266,8 @@ ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - id: 0 # Instanz-ID (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + id: 0 # Instanz-ID, optional + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx new file mode 100644 index 0000000000..a77bb0802e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -0,0 +1,49 @@ +--- +title: ABB Terra AC (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB Terra AC (OCPP) + + + +https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-abb-tac` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx index c8239304ef..f916303050 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx @@ -1,6 +1,7 @@ --- title: ABB Terra AC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,26 +12,40 @@ import TabItem from '@theme/TabItem'; # ABB Terra AC - + -https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf +Erfordert Firmware >= 1.6.5 :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + template: abb + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> + +## Templateparameter `abb` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx deleted file mode 100644 index 3daa17da9c..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-sbcx.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: ABL eM4 (SBCx) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL eM4 (SBCx) - - - -1 Ladepunkt), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx new file mode 100644 index 0000000000..91ede7a3f0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Single (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Single (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-abl` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx new file mode 100644 index 0000000000..911d43ac09 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Single (SBCx) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Single (SBCx) + + + +1 Ladepunkt), optional`} /> + +## Templateparameter `abl-em4` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx new file mode 100644 index 0000000000..0295b30c6e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Twin (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Twin (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-abl` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx new file mode 100644 index 0000000000..10aec80620 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eM4 Twin (SBCx) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eM4 Twin (SBCx) + + + +1 Ladepunkt), optional`} /> + +## Templateparameter `abl-em4` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx index e4a22d768e..03924f47dc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx @@ -1,6 +1,7 @@ --- title: ABL eMH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port timeout: 10s # Zeitüberschreitung, optional`} /> +## Templateparameter `abl` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx new file mode 100644 index 0000000000..bbe90647b8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eMH2 (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH2 (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-abl` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx index f7a78501ed..b9fcf8f6e9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx @@ -1,6 +1,7 @@ --- title: ABL eMH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port timeout: 10s # Zeitüberschreitung, optional`} /> +## Templateparameter `abl` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx new file mode 100644 index 0000000000..16049cbd9a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: ABL eMH3 (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABL eMH3 (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-abl` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx deleted file mode 100644 index 07a6893b96..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh2.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: ABL Sursum eMH2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL Sursum eMH2 - - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx deleted file mode 100644 index dad4fdff0c..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh3.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: ABL Sursum eMH3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL Sursum eMH3 - - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx deleted file mode 100644 index 1e815a9890..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-sursum-emh4.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: ABL Sursum eMH4 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABL Sursum eMH4 - - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx new file mode 100644 index 0000000000..804b35e0d8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: Alfen Eve (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alfen Eve (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-alfen` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx index ef2fc08e37..19940c1dcb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx @@ -1,6 +1,7 @@ --- title: Alfen Eve -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alfen.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,27 @@ import TabItem from '@theme/TabItem'; # Alfen Eve - + + +Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus extern zu steuern. In den Einstellungen muss "Active Load Balancing" aktiviert und "Energy Management System" als Data Source ausgewählt werden. Es wird empfohlen "ValidityTime" (Menu "TCP/IP EMS") auf 300s einzustellen. Falls die "Double"-Box verwendet wird müssen beide Ladepunkte getrennt voneinander hinzugefügt werden. Der erste Port (oder einzelne Port) ist unter ID 1 zugänglich, der zweite unter ID 2. + :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + template: alfen + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> + +## Templateparameter `alfen` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx new file mode 100644 index 0000000000..4a9edc711c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx @@ -0,0 +1,50 @@ +--- +title: alpha innotec +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# alpha innotec + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx index 764aa447b8..58ca24a2a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -1,6 +1,7 @@ --- title: Alphatec Ladesäule Twin custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx deleted file mode 100644 index 4a48cf8e2a..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini-power.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Alphatec Wallbox Mini, Power -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Alphatec Wallbox Mini, Power - - - -Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx new file mode 100644 index 0000000000..cee191fd04 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -0,0 +1,45 @@ +--- +title: Alphatec Wallbox Mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Wallbox Mini + + + +Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. + + + + +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx new file mode 100644 index 0000000000..2a274ac38b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx @@ -0,0 +1,45 @@ +--- +title: Alphatec Wallbox Power +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Alphatec Wallbox Power + + + +Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. + + + + +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx new file mode 100644 index 0000000000..d910c96bb4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -0,0 +1,35 @@ +--- +title: Amperfied Wallbox connect.business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.business + + + + + +## Templateparameter `amperfied` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx new file mode 100644 index 0000000000..b517ec0867 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -0,0 +1,35 @@ +--- +title: Amperfied Wallbox connect.home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.home + + + + + +## Templateparameter `amperfied` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx new file mode 100644 index 0000000000..931307ed5d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -0,0 +1,35 @@ +--- +title: Amperfied Wallbox connect.solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Amperfied Wallbox connect.solar + + + + + +## Templateparameter `amperfied-solar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx deleted file mode 100644 index 6a4d20c236..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectbusiness.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Amperfied Wallbox connect.business -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Amperfied Wallbox connect.business - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx deleted file mode 100644 index a0db0963ae..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connecthome.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Amperfied Wallbox connect.home -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Amperfied Wallbox connect.home - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx deleted file mode 100644 index 257e44333f..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connectsolar.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Amperfied Wallbox connect.solar -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Amperfied Wallbox connect.solar - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx index 4bb565d640..fee0b5bebe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -1,6 +1,7 @@ --- title: Amperfied Wallbox Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx deleted file mode 100644 index d3b883090f..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-live.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Ampure Live -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Ampure Live - - - -Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx index 71cc322316..7c976b1ab6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx @@ -1,6 +1,7 @@ --- title: Ampure NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gel host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +## Templateparameter `webasto-next` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx index a57d49de16..ae69f9c9f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx @@ -1,6 +1,7 @@ --- title: Ampure Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx deleted file mode 100644 index cf2a7e674f..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-audi-wallbox-pro.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Audi Audi Wallbox pro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Audi Audi Wallbox pro - - - -Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - -Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx index 29c68ef04a..c3757833ef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx @@ -1,6 +1,7 @@ --- title: Audi Wallbox plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elliconnect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx new file mode 100644 index 0000000000..982939e3b0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx @@ -0,0 +1,37 @@ +--- +title: Audi Wallbox pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Audi Wallbox pro + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + + + +## Templateparameter `ellipro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx index f160eaff25..9a54127824 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx @@ -1,6 +1,7 @@ --- title: AUTEL AC Compact custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,17 @@ Anleitung: meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-autel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx index 23c030fcba..239894b47f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx @@ -1,6 +1,7 @@ --- title: AUTEL AC MaxiCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,17 @@ Anleitung: meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-autel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx index efa46fcc4a..7517091984 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Autoaid Business Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-autoaid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx index 632cff33cb..6f5fab7108 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Autoaid Intelligent Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-autoaid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx index 5d596badae..7aa2b8ab62 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx @@ -1,6 +1,7 @@ --- title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/fritzdect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,16 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `fritzdect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| URI
`uri` | HTTP(S) Adresse | Standard: `https://fritz.box` | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Aktoridentifikationsnummer (AIN)
`ain` | Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. | Beispiel: `307788992233` | ja | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx index e80c6b9658..b91540a2b3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx @@ -1,6 +1,7 @@ --- title: Bender CC612 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx index b4e514540d..d968a220fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx @@ -1,6 +1,7 @@ --- title: Bender CC613 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx index cf8c96eaf0..4f431eefd4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx @@ -1,6 +1,7 @@ --- title: Bender ICC1314 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx index b0292cb722..122ef519e1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx @@ -1,6 +1,7 @@ --- title: Bender ICC1324 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx index 02f6d14440..5eb5aaea56 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx @@ -1,6 +1,7 @@ --- title: BMW i Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,12 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx index a869361774..bcbb5b8453 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Bosch SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,12 @@ Eingebunden via [EMSESP](https://emsesp.org/) powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> +## Templateparameter `emsesp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| `token` | | | nein | +| Leistungsquelle
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx index ea15cfdde8..124bce1281 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx @@ -1,6 +1,7 @@ --- title: Bösch x-change custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,11 @@ import TabItem from '@theme/TabItem'; tempsource: # Temperaturquelle, [warmwater, buffer] (optional) watchdog: 60s # optional`} /> +## Templateparameter `kermi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx new file mode 100644 index 0000000000..36da472e1d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -0,0 +1,50 @@ +--- +title: Buderus Logamatic HMC 20 Z +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Buderus Logamatic HMC 20 Z + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx new file mode 100644 index 0000000000..6f36debcd0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -0,0 +1,50 @@ +--- +title: Buderus Logamatic HMC 20 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Buderus Logamatic HMC 20 + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx index 93e33c8321..95a70864f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Buderus SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,12 @@ Eingebunden via [EMSESP](https://emsesp.org/) powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> +## Templateparameter `emsesp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| `token` | | | nein | +| Leistungsquelle
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx index 35995cd704..84e55b7eae 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx @@ -1,6 +1,7 @@ --- title: cFos Power Brain Solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,11 @@ Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigescha template: cfos host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `cfos` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx index 00d8848185..df3d837799 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx @@ -1,6 +1,7 @@ --- title: cFos Power Brain custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,11 @@ Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigescha template: cfos host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `cfos` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx index 40c0f82189..53670bddca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx @@ -1,6 +1,7 @@ --- title: Charge Amps Halo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-chargeamps.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-chargeamps` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx index c09694e8f9..d0799bde2c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx @@ -1,6 +1,7 @@ --- title: Compleo eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `innogy-ebox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx new file mode 100644 index 0000000000..b26342a58f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -0,0 +1,50 @@ +--- +title: CTA All-In-One Aeroplus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CTA All-In-One Aeroplus + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx deleted file mode 100644 index 7d0db981ea..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e-c22e.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: CUBOS C11E, C22E -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# CUBOS C11E, C22E - - - -Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx new file mode 100644 index 0000000000..7ef53bd179 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx @@ -0,0 +1,38 @@ +--- +title: CUBOS C11E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CUBOS C11E + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx new file mode 100644 index 0000000000..cd3ed97f2b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx @@ -0,0 +1,38 @@ +--- +title: CUBOS C22E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# CUBOS C22E + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx index 07f0d79d40..a62a48601c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx index b31b4c6bce..7338920cfa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elliconnect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx index 879b03b8ac..307d04aecd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx index 532da112f8..13437dc1d2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx index 344b8f534e..025073dbda 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Cupra Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `ellipro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx index 0d871b2d82..a941ce3341 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Dadapower Premium Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/dadapower.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `dadapower` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx index 2651375a8e..e12ed27c24 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx @@ -1,6 +1,7 @@ --- title: DaheimLaden Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daheimladen-mb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ Die Wallbox muss über eine aktuelle Firmware mit Modbus-Unterstützung verfüge host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +## Templateparameter `daheimladen-mb` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx index fc17322427..1635511dc2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Daikin HomeHub (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daikin-homehub.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperaturquelle, [warmwater, buffer] (optional)`} /> +## Templateparameter `daikin-homehub` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx index 5c317e2163..ab847ee320 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx @@ -1,6 +1,7 @@ --- title: Delta AC Max Basic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `delta` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx index 9264c3b98e..1fc4bfd14a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx @@ -1,6 +1,7 @@ --- title: Delta AC MAX Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `delta` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx index 712c74c969..285ab09cae 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx @@ -1,6 +1,7 @@ --- title: Delta SLIM Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `delta` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx index 622fd76e87..486e27c47d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -1,6 +1,7 @@ --- title: Delta Ultra Fast Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,5 +61,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `delta` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx index fa4065da89..b4ddf1cbd7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx @@ -1,6 +1,7 @@ --- title: Demowallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/demo-charger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,13 @@ Zu Demonstrationszwecken. Wallbox mit festen Werten. maxcurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) phases1p3p: false # Phasenumschaltung, optional`} /> +## Templateparameter `demo-charger` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Ladezustand
`status` | | Standard: `A`
Auswahl: `A`, `B`, `C` | ja | +| Leistung
`power` | | | nein | +| Ladebereit
`enabled` | | Standard: `true` | nein | +| Maximale Stromstärke
`maxcurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Phasenumschaltung
`phases1p3p` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx new file mode 100644 index 0000000000..152fa5c34c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx @@ -0,0 +1,35 @@ +--- +title: E.ON Drive eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive eBox + + + + + +## Templateparameter `innogy-ebox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx new file mode 100644 index 0000000000..0c24618572 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx @@ -0,0 +1,38 @@ +--- +title: E.ON Drive vBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E.ON Drive vBox + + + +1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. + + + + +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx new file mode 100644 index 0000000000..b3c8a1b2b6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx @@ -0,0 +1,38 @@ +--- +title: E3/DC Easy Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC Easy Connect + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx deleted file mode 100644 index c374d2a493..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3dc-easy-connect.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: E3/DC Easy Connect -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E3/DC Easy Connect - - - -DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx index 457329d5ae..cf611b3c5e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx @@ -1,6 +1,7 @@ --- title: Easee Charge Core custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +## Templateparameter `easee` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | Emailadresse | | ja | +| Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | +| `charger` | | Beispiel: `EH______` | ja | +| Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | +| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx index 448d566c6e..1cac202664 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx @@ -1,6 +1,7 @@ --- title: Easee Charge Lite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +## Templateparameter `easee` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | Emailadresse | | ja | +| Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | +| `charger` | | Beispiel: `EH______` | ja | +| Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | +| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx index b16d62d0bd..f240b39169 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx @@ -1,6 +1,7 @@ --- title: Easee Charge custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +## Templateparameter `easee` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | Emailadresse | | ja | +| Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | +| `charger` | | Beispiel: `EH______` | ja | +| Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | +| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx index dd33b0fae7..6187b3e09a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx @@ -1,6 +1,7 @@ --- title: Easee Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,15 @@ import TabItem from '@theme/TabItem'; timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +## Templateparameter `easee` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | Emailadresse | | ja | +| Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | +| `charger` | | Beispiel: `EH______` | ja | +| Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | +| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx index 597efd2665..2b44fb2154 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Ebee Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx index fc08f2bca0..2ce9d1ece5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx @@ -1,6 +1,7 @@ --- title: echarge cPH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,12 @@ Als Betriebsmodus muss `manual` ausgewählt sein host: 192.0.2.2 # IP-Adresse oder Hostname connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `hardybarth-ecb1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx deleted file mode 100644 index 21d39bf964..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2-cpm2.mdx +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: echarge cPH2, cPμ2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# echarge cPH2, cPμ2 - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx new file mode 100644 index 0000000000..4fae3f7cf7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx @@ -0,0 +1,30 @@ +--- +title: echarge cPH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPH2 + + + + + +## Templateparameter `hardybarth-salia` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx new file mode 100644 index 0000000000..25c40222af --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx @@ -0,0 +1,30 @@ +--- +title: echarge cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# echarge cPμ2 + + + + + +## Templateparameter `hardybarth-salia` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx new file mode 100644 index 0000000000..edcb76c4e8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -0,0 +1,46 @@ +--- +title: EcoHarmony EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EcoHarmony EVSE EPC 2.0 Plus + + + + + +## Templateparameter `obo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx deleted file mode 100644 index 2b99761d93..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-20-plus.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: EcoHarmony EVSE EPC 2.0 Plus -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# EcoHarmony EVSE EPC 2.0 Plus - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx index d9f3b3f146..0279e5d50c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx @@ -1,6 +1,7 @@ --- title: Edgetech Smart EVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartevse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `smartevse` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx index 9559d9b4c4..a6288fde94 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx @@ -1,6 +1,7 @@ --- title: EEBUS kompatibel custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eebus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,10 @@ import TabItem from '@theme/TabItem'; ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `eebus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx new file mode 100644 index 0000000000..b800712d30 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx @@ -0,0 +1,50 @@ +--- +title: Elco +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Elco + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx index 6555c5d030..0774648ccd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx @@ -1,6 +1,7 @@ --- title: Elecq Biz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-elecq` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx index d4b9cb2b1d..a111d8007d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx @@ -1,6 +1,7 @@ --- title: Elecq Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-elecq` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx index 88b6e95cba..60ae317742 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx @@ -1,6 +1,7 @@ --- title: Elecq Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-elecq` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx index dcee848127..b97894dd70 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx @@ -1,6 +1,7 @@ --- title: eledio go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-enercab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx index cd7341d763..f7ca69121d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx index b4e7b608e2..110c73f4fa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elliconnect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx index 7c96c6e5a6..bfd46ddc3f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx index 65082823ca..0ff0622702 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx index 234d71f3f0..0b3cde9f4a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Elli Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `ellipro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx index 90d7722850..2d97291649 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx @@ -1,6 +1,7 @@ --- title: EM2GO Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go-home.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,9 @@ Benötigt FW version >= E3C_V1.1. mA Regelung benötigt FW version >= E3C_V1.3. template: em2go-home host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `em2go-home` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx new file mode 100644 index 0000000000..351c5072a4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -0,0 +1,36 @@ +--- +title: EM2GO Pro Power (OCPP/ONC) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EM2GO Pro Power (OCPP/ONC) + + + +Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP/ONC: 3.15) + + + + +## Templateparameter `em2go` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx deleted file mode 100644 index 465546684d..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpponc.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: EM2GO Pro Power, OCPP/ONC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# EM2GO Pro Power, OCPP/ONC - - - -Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP/ONC: 3.15) - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx deleted file mode 100644 index ebbf437be2..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/en-ac-ev-charger.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: EN+ AC EV Charger -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# EN+ AC EV Charger - - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx index 04fe3749f2..0ef1bc4c8e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx @@ -1,6 +1,7 @@ --- title: enercab smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-enercab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx new file mode 100644 index 0000000000..7e57226e7d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -0,0 +1,46 @@ +--- +title: EN+ AC EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# EN+ AC EV Charger + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-enplus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx index 0ce47cbff5..7223a27c60 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Ensto Chago Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx index 34b172692c..b9aff698ca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx @@ -1,6 +1,7 @@ --- title: EntraTek Power Dot Fix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-entratek` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx index 973bfc6056..45a0127257 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -1,6 +1,7 @@ --- title: EntraTek Power Dot Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-entratek` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx deleted file mode 100644 index 9fa1d98fbf..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-ebox.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: E.ON Drive eBox -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E.ON Drive eBox - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx deleted file mode 100644 index df665bef5d..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eon-drive-vbox.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: E.ON Drive vBox -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E.ON Drive vBox - - - -1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx index f997dfda9f..8c8e70f71f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx @@ -1,6 +1,7 @@ --- title: ESL Walli LIGHT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx index a1234d1645..7f09f1eede 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx @@ -1,6 +1,7 @@ --- title: eSystems ghostONE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `ghost` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx index 917ebda6aa..97ab281f71 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx @@ -1,6 +1,7 @@ --- title: Etrel INCH Duo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel-duo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,13 @@ Die Wallbox muss sich im "Power" Modus befinden. port: 502 # Port, optional connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `etrel-duo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx index c6e0dd292d..08d98f6f44 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx @@ -1,6 +1,7 @@ --- title: Etrel INCH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Die Wallbox muss sich im "Power" Modus befinden. host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +## Templateparameter `etrel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx index f34690357f..0d1556b6b5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx @@ -1,6 +1,7 @@ --- title: EVBox Elvi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-evbox-elvi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,5 +31,17 @@ import TabItem from '@theme/TabItem'; connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-evbox-elvi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| `meter` | | Standard: `true` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx index 3dc1991fa8..6c30e36ba1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx @@ -1,6 +1,7 @@ --- title: EVBox Livo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/livo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `livo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx index 66343afe2a..7b11372241 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx @@ -1,6 +1,7 @@ --- title: EVSE DIN custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `evse-din` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx index 720e20a4b4..0b52393415 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx @@ -1,6 +1,7 @@ --- title: EVSE-WiFi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evsewifi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: evsewifi host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `evsewifi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx new file mode 100644 index 0000000000..40539c3e70 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -0,0 +1,42 @@ +--- +title: Free2Move eProWallbox Move +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Free2Move eProWallbox Move + + + + + +## Templateparameter `eprowallbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx index fa1915c2c6..b20d65aeb4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx @@ -1,6 +1,7 @@ --- title: Free2Move eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,5 +32,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `eprowallbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx index 56ca6cd792..31452169b6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -1,6 +1,7 @@ --- title: Free2move eSolutions eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-esolutions.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-esolutions` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx new file mode 100644 index 0000000000..1d961dee53 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: Fronius Wattpilot (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Fronius Wattpilot (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-goe` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx deleted file mode 100644 index bb728764bb..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Fronius Wattpilot -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Fronius Wattpilot - - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx deleted file mode 100644 index 8dadfcb8f7..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb-glb-ls4-ls4-compact.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Garo GLB, GLB+, LS4, LS4 compact -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Garo GLB, GLB+, LS4, LS4 compact - - - -Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx new file mode 100644 index 0000000000..14b7db4bf5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx @@ -0,0 +1,38 @@ +--- +title: Garo GLB +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo GLB + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx new file mode 100644 index 0000000000..92b7a6cdbf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx @@ -0,0 +1,38 @@ +--- +title: Garo GLB+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo GLB+ + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx new file mode 100644 index 0000000000..6dfa4b91c2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx @@ -0,0 +1,38 @@ +--- +title: Garo LS4 compact +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo LS4 compact + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx new file mode 100644 index 0000000000..57146d397e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx @@ -0,0 +1,38 @@ +--- +title: Garo LS4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Garo LS4 + + + +Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. + + + + +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx new file mode 100644 index 0000000000..4b21e52e83 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: go-e Charger Gemini (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger Gemini (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-goe` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx index 44b5105cfa..6265a6ec30 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger Gemini -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,24 @@ import TabItem from '@theme/TabItem'; # go-e Charger Gemini - + + +Benötigt mindestens Firmware 052.1 oder neuer. +Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". +In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. + :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + template: go-e-v3 + host: 192.0.2.2 # IP-Adresse oder Hostname`} /> + +## Templateparameter `go-e-v3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx deleted file mode 100644 index f1aec89ca1..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-home.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: go-e Charger HOME+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# go-e Charger HOME+ - - - -Benötigt mindestens Firmware 052.1 oder neuer. -Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". -In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx index 5c26e6487e..a08bf476b6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger HOMEfix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,5 +23,11 @@ Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss akt template: go-e host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `go-e` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx new file mode 100644 index 0000000000..e790137020 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx @@ -0,0 +1,35 @@ +--- +title: go-e Charger HOME+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger HOME+ + + + +Benötigt mindestens Firmware 052.1 oder neuer. +Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". +In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. + + + + +## Templateparameter `go-e-v3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx new file mode 100644 index 0000000000..0925c13fdc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: go-e Charger PRO (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger PRO (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-goe` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx index b21c0f1dad..393ce1c00f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger PRO -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,22 @@ import TabItem from '@theme/TabItem'; # go-e Charger PRO - + + +Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. + :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + template: go-e + host: 192.0.2.2 # IP-Adresse oder Hostname`} /> + +## Templateparameter `go-e` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx new file mode 100644 index 0000000000..e841717538 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -0,0 +1,46 @@ +--- +title: go-e Charger V3 (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# go-e Charger V3 (OCPP) + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-goe` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx index 6e98ee746f..795fb76615 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx @@ -1,6 +1,7 @@ --- title: go-e Charger V3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -11,23 +12,24 @@ import TabItem from '@theme/TabItem'; # go-e Charger V3 - + + +Benötigt mindestens Firmware 052.1 oder neuer. +Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". +In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. + :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + template: go-e-v3 + host: 192.0.2.2 # IP-Adresse oder Hostname`} /> + +## Templateparameter `go-e-v3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx new file mode 100644 index 0000000000..0d70505ccd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx @@ -0,0 +1,39 @@ +--- +title: Hardy Barth cPH1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hardy Barth cPH1 + + + +Als Betriebsmodus muss `manual` ausgewählt sein + + +1 Ladepunkt), optional`} /> + +## Templateparameter `hardybarth-ecb1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx new file mode 100644 index 0000000000..79deeef9e2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx @@ -0,0 +1,30 @@ +--- +title: Hardy Barth cPH2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hardy Barth cPH2 + + + + + +## Templateparameter `hardybarth-salia` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx new file mode 100644 index 0000000000..18d6ba0839 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx @@ -0,0 +1,30 @@ +--- +title: Hardy Barth cPμ2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hardy Barth cPμ2 + + + + + +## Templateparameter `hardybarth-salia` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx deleted file mode 100644 index b992f86a44..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph1.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: HardyBarth cPH1 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# HardyBarth cPH1 - - - -Als Betriebsmodus muss `manual` ausgewählt sein - - -1 Ladepunkt), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx deleted file mode 100644 index d5282058c8..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardybarth-cph2-cpm2.mdx +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: HardyBarth cPH2, cPμ2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# HardyBarth cPH2, cPμ2 - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx index 4158348201..52ed4f6fca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx @@ -1,6 +1,7 @@ --- title: Heidelberg Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx new file mode 100644 index 0000000000..4ac140cdaf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx @@ -0,0 +1,35 @@ +--- +title: Hesotec eBox +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hesotec eBox + + + + + +## Templateparameter `hesotec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx deleted file mode 100644 index 815f7bf64a..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat-ebox.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Hesotec eSat, eBox -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Hesotec eSat, eBox - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx new file mode 100644 index 0000000000..1cd4fe35ae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx @@ -0,0 +1,35 @@ +--- +title: Hesotec eSat +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Hesotec eSat + + + + + +## Templateparameter `hesotec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx index 5c3160a3ba..976da4d73b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx @@ -1,6 +1,7 @@ --- title: Home Assistant Schalter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homeassistant-switch.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,16 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `homeassistant-switch` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Basis-URL der Home Assistant Instanz
`baseurl` | | Beispiel: `http://homeassistant.local:8123` | ja | +| Long-Lived Access Token
`token` | aus Home Assistant Profil | | ja | +| Entity ID des schaltbaren Geräts
`switchentity` | | Beispiel: `switch.smartsocket` | ja | +| Entity ID für Leistungsmessung
`powerentity` | | Beispiel: `sensor.smartsocket_power` | nein | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx index 6ef7a0d2b1..890cb58fe4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx @@ -1,6 +1,7 @@ --- title: Homecharge Homecharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-homecharge.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händl meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-homecharge` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx index 765f81fd06..f51fccf0a3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx @@ -1,6 +1,7 @@ --- title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homematic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `homematic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010)
`port` | | Standard: `2010` | nein | +| Geräteadresse/Seriennummer
`device` | Homematic Geräte Id, wie im CCU Webfrontend angezeigt. | Beispiel: `0001EE89AAD848` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2)
`meterchannel` | Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. | Standard: `6` | ja | +| Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1)
`switchchannel` | Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. | Standard: `3` | ja | +| XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h)
`cache` | Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. | Standard: `1s`
Beispiel: `5m` | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx index 974c6e90f0..1611ce4932 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx @@ -1,6 +1,7 @@ --- title: HomeWizard custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homewizard.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `homewizard` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx new file mode 100644 index 0000000000..e36814c744 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -0,0 +1,46 @@ +--- +title: Huawei SCharger-22KT-S0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SCharger-22KT-S0 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-huawei` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx deleted file mode 100644 index a29c21fadb..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0-22kt-s0.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Huawei SCharger-7KS-S0 / 22KT-S0 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Huawei SCharger-7KS-S0 / 22KT-S0 - - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx new file mode 100644 index 0000000000..8788bdb97c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -0,0 +1,46 @@ +--- +title: Huawei SCharger-7KS-S0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Huawei SCharger-7KS-S0 + + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-huawei` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx index db410ccdea..70398f6d4e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx @@ -1,6 +1,7 @@ --- title: IDM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/idm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer] (optional)`} /> +## Templateparameter `idm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx index 9b332ad7a1..9fb0a72ef7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx @@ -56,13 +56,13 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; + + + - + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `innogy-ebox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx index ecc499bd64..cd5d26cac9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx @@ -1,6 +1,7 @@ --- title: INRO Pantabox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pantabox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: pantabox host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `pantabox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx index 7a7aa20ec3..8ba1d48b81 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx @@ -1,6 +1,7 @@ --- title: Juice Charger Me custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx index add5607e18..7c5786070a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Junkers SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,12 @@ Eingebunden via [EMSESP](https://emsesp.org/) powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> +## Templateparameter `emsesp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| `token` | | | nein | +| Leistungsquelle
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx deleted file mode 100644 index 576315e128..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20-kwb-ac40-kwb-ac60-kwb-ac40e-kwb-ac60e.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Kathrein KWB-AC20, KWB-AC40, KWB-AC60, KWB-AC40E, KWB-AC60E - - - -Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx new file mode 100644 index 0000000000..2b82c631db --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC20 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC20 + + + +Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 + + + + +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx new file mode 100644 index 0000000000..0957bccd41 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC35 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC35 + + + +Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 + + + + +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx new file mode 100644 index 0000000000..e7fcb00b36 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC40 E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC40 E + + + +Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 + + + + +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx new file mode 100644 index 0000000000..670e41c669 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC40 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC40 + + + +Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 + + + + +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx new file mode 100644 index 0000000000..173df76fa1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC60 E +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC60 E + + + +Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 + + + + +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx new file mode 100644 index 0000000000..6d550e604d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -0,0 +1,38 @@ +--- +title: Kathrein KWB-AC60 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kathrein KWB-AC60 + + + +Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 + + + + +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx deleted file mode 100644 index 5563e413cc..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20-p30-cx-series.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: KEBA KeContact P20, P30, C/X Series -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# KEBA KeContact P20, P30, C/X Series - - - -Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx new file mode 100644 index 0000000000..7f20e61c47 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P20 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P20 + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx new file mode 100644 index 0000000000..df9640175a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P30 C-Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P30 C-Series + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx new file mode 100644 index 0000000000..23a3005875 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P30 X-Series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P30 X-Series + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx deleted file mode 100644 index 6779ab31aa..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-p40-pro.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: KEBA KeContact P40, P40 Pro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# KEBA KeContact P40, P40 Pro - - - -Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx new file mode 100644 index 0000000000..7d1d6397c5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P40 Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P40 Pro + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx new file mode 100644 index 0000000000..d6e1c6eddf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx @@ -0,0 +1,49 @@ +--- +title: KEBA KeContact P40 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# KEBA KeContact P40 + + + +Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. + + + + +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx index 5cbdc0b7b5..3ab60cb8e2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx @@ -1,6 +1,7 @@ --- title: Kermi x-center pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,11 @@ import TabItem from '@theme/TabItem'; tempsource: # Temperaturquelle, [warmwater, buffer] (optional) watchdog: 60s # optional`} /> +## Templateparameter `kermi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx index 7dd39d743e..32e82b2a8d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx @@ -1,6 +1,7 @@ --- title: Kontron Solar Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `ghost` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx index 86348fbd8d..0af651ca5f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx @@ -1,6 +1,7 @@ --- title: Kostal Enector custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,5 +37,11 @@ Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivieru host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `mennekes-compact` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx index 0dfbe570c2..def0f6e5cd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx @@ -1,6 +1,7 @@ --- title: KSE wBX16 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,5 +32,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `kse` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx deleted file mode 100644 index ae8a1f0277..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload-mikro-20.mdx +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: LadeFoxx EvLoad, Mikro 2.0 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# LadeFoxx EvLoad, Mikro 2.0 - - - -1 Ladepunkt), optional`} /> - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx new file mode 100644 index 0000000000..f84dd9fb3e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx @@ -0,0 +1,44 @@ +--- +title: LadeFoxx EvLoad +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LadeFoxx EvLoad + + + +1 Ladepunkt), optional`} /> + +## Templateparameter `phoenix-charx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx new file mode 100644 index 0000000000..99c269e977 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -0,0 +1,44 @@ +--- +title: LadeFoxx Mikro 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LadeFoxx Mikro 2.0 + + + +1 Ladepunkt), optional`} /> + +## Templateparameter `phoenix-charx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx index 294f6bd8b1..1a2a499c45 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx @@ -1,6 +1,7 @@ --- title: Lambda EU-L Serie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,11 @@ Energiemanagementeinstellungen am Gerät: tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) watchdog: 60s # optional`} /> +## Templateparameter `lambda-zewotherm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx deleted file mode 100644 index 4cc424b501..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essential.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: LRT HOME Essential+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# LRT HOME Essential+ - - - -Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx new file mode 100644 index 0000000000..1277b05d33 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx @@ -0,0 +1,45 @@ +--- +title: LRT HOME Essential+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LRT HOME Essential+ + + + +Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. + + + + +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx index 7a3553001b..ca5e8f8de5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMEDIO Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx index 4bfe3ffffb..5720234954 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON 4Business 700 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx index 8df966c59b..c599d968bc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON 4You 300 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,5 +37,11 @@ Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivieru host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `mennekes-compact` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx index fc9715e9cb..b121ba311a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON 4You 500 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx index 4694b8715e..74a6a7d48c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON ChargeControl custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx new file mode 100644 index 0000000000..b8669dcb91 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -0,0 +1,47 @@ +--- +title: Mennekes AMTRON Compact 2.0s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Mennekes AMTRON Compact 2.0s + + + +Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). +Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. +Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. + + + + +## Templateparameter `mennekes-compact` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx deleted file mode 100644 index cf8d55ea1f..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-20s.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Mennekes AMTRON Compact 2.0s -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Mennekes AMTRON Compact 2.0s - - - -Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). -Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. -Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx index 96b0d859a3..f2f092d1d3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON Premium custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `mennekes-hcc3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx index 2a83abd777..7f2ca9841b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx index 4aa744660a..3a4919633b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -1,6 +1,7 @@ --- title: Mennekes AMTRON Xtra custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `mennekes-hcc3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx index 84022299a3..41571186bd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -1,6 +1,7 @@ --- title: Mennekes eMobility Gateway (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-mennekes-acu` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx index 255f35deab..51026a279f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx @@ -1,6 +1,7 @@ --- title: Mennekes Smart (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-mennekes-acu` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx index 32f5c63e10..7c9b660c18 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -1,6 +1,7 @@ --- title: Mennekes Smart T (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,17 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-mennekes-acu` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx index 7d6b77542e..b6e2abb6c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -1,6 +1,7 @@ --- title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-elwa-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional`} /> +## Templateparameter `ac-elwa-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Skalierungsfaktor der Leistungsvorgabe
`scale` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx new file mode 100644 index 0000000000..bdda33641d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -0,0 +1,39 @@ +--- +title: my-PV AC•THOR 9s +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR 9s + + + + + +## Templateparameter `ac-thor` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Temperatursensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | nein | +| Skalierungsfaktor der Leistungsvorgabe
`scale` | | Standard: `1` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx deleted file mode 100644 index 51c16355db..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-ac-thor-9s.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: my-PV AC THOR, AC THOR 9s -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# my-PV AC THOR, AC THOR 9s - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx new file mode 100644 index 0000000000..731ad93d74 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx @@ -0,0 +1,39 @@ +--- +title: my-PV AC•THOR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR + + + + + +## Templateparameter `ac-thor` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Temperatursensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | nein | +| Skalierungsfaktor der Leistungsvorgabe
`scale` | | Standard: `1` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx index af51c6d3b9..2c909ef518 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx @@ -1,6 +1,7 @@ --- title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mystrom.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `mystrom` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx new file mode 100644 index 0000000000..d4eb515755 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx @@ -0,0 +1,50 @@ +--- +title: Nibe AP-AW10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Nibe AP-AW10 + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx new file mode 100644 index 0000000000..5bb99b4bcf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx @@ -0,0 +1,50 @@ +--- +title: Novelan WPR NET +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Novelan WPR NET + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx index c2cb820d14..bc6eeef729 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx @@ -1,6 +1,7 @@ --- -title: NRGKick Connect +title: NRGkick Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrgkick-connect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,7 +10,7 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# NRGKick Connect +# NRGkick Connect @@ -24,3 +25,11 @@ NRGkick Ladeeinheit via HTTP (älter als 2022/2023) mac: password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen`} /> +## Templateparameter `nrgkick-connect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| `mac` | | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx index 0cac5e27bd..1b1740d2b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx @@ -1,6 +1,7 @@ --- -title: NRGKick Gen2 +title: NRGkick Gen2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrggen2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,7 +10,7 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# NRGKick Gen2 +# NRGkick Gen2 @@ -34,5 +35,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port phases1p3p: false # Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional)`} /> +## Templateparameter `nrggen2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `phases1p3p` | Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx index 229ff8177a..72d5cb29e8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx @@ -1,6 +1,7 @@ --- title: OBO Bettermann Ion custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `obo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx new file mode 100644 index 0000000000..33b4ce4723 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -0,0 +1,67 @@ +--- +title: OCPP 1.6J kompatibel (Smart Charging) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# OCPP 1.6J kompatibel (Smart Charging) + + + +Bei OCPP verbindet sich die Wallbox (Client) zu evcc (Server). +Die Wallbox muss daher evcc via Hostname (funktionierende DNS-Auflösung erforderlich!) oder über die IP-Adresse auf Port 8887 erreichen können. +Standardmäßig wird die erste eingehende Verbindung mit einer beliebigen Ladepunktkennung verwendet. +Um mehrere Ladepunkte eindeutig zuordnen zu können müssen die jeweilige Stationskennung (`stationid: `) und Anschlussnummer (`connector: `) hinterlegt werden. +Viele Wallboxen fügen die `stationid` automatisch der Backend-URL hinzu, bei manchen muss dies manuell geschehen `ws://:8887/`. +Für Zählermesswerte sollte in der Wallbox wenn möglich ein kurzes Zeitintervall (< 10s) konfiguriert werden. +Nutzen Sie Ihre RFID-Tags (dies ermöglicht z. B. eine Fahrzeugidentifizierung) oder setzen Sie Ihre Wallbox auf "freies Laden" oder "Autostart" um die für die Ladefreigabe benötigte Transaktion zu erzeugen. + +Falls die Wallbox keine Möglichkeit bietet die Transaktionen lokal zu starten, kann die erweiterte Option `remotestart` genutzt werden um automatisch eine Transaktion zu starten sobald ein Fahrzeug angeschlossen wird. +Dies sollte nur in Ausnahmefällen erforderlich sein. + +Voraussetzungen: +* Ggf. zuvor konfigurierte OCPP-Profile (z.B. durch eine andere Backend-Anbindung) in der Wallboxkonfiguration entfernen +* Backend-URL (Central System) in der Wallboxkonfiguration: `ws://[evcc-adresse]:8887/` (eventuell noch um `stationid` erweitern) +* Protokoll: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// o.ä. +* Keine Verschlüsselung, keine Authentifizierung, kein Passwort +* Verbindung über das lokale Netzwerk + +Die konkrete Konfiguration und der tatsächlich nutzbare Funktionsumfang hängen vom Wallbox-Modell und dessen Software ab. + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx deleted file mode 100644 index 62e94ade0e..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-16j-compatible-smart-charging.mdx +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: OCPP 1.6J kompatibel (Smart Charging) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# OCPP 1.6J kompatibel (Smart Charging) - - - -Bei OCPP verbindet sich die Wallbox (Client) zu evcc (Server). -Die Wallbox muss daher evcc via Hostname (funktionierende DNS-Auflösung erforderlich!) oder über die IP-Adresse auf Port 8887 erreichen können. -Standardmäßig wird die erste eingehende Verbindung mit einer beliebigen Ladepunktkennung verwendet. -Um mehrere Ladepunkte eindeutig zuordnen zu können müssen die jeweilige Stationskennung (`stationid: `) und Anschlussnummer (`connector: `) hinterlegt werden. -Viele Wallboxen fügen die `stationid` automatisch der Backend-URL hinzu, bei manchen muss dies manuell geschehen `ws://:8887/`. -Für Zählermesswerte sollte in der Wallbox wenn möglich ein kurzes Zeitintervall (< 10s) konfiguriert werden. -Nutzen Sie Ihre RFID-Tags (dies ermöglicht z. B. eine Fahrzeugidentifizierung) oder setzen Sie Ihre Wallbox auf "freies Laden" oder "Autostart" um die für die Ladefreigabe benötigte Transaktion zu erzeugen. - -Falls die Wallbox keine Möglichkeit bietet die Transaktionen lokal zu starten, kann die erweiterte Option `remotestart` genutzt werden um automatisch eine Transaktion zu starten sobald ein Fahrzeug angeschlossen wird. -Dies sollte nur in Ausnahmefällen erforderlich sein. - -Voraussetzungen: -* Ggf. zuvor konfigurierte OCPP-Profile (z.B. durch eine andere Backend-Anbindung) in der Wallboxkonfiguration entfernen -* Backend-URL (Central System) in der Wallboxkonfiguration: `ws://[evcc-adresse]:8887/` (eventuell noch um `stationid` erweitern) -* Protokoll: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// o.ä. -* Keine Verschlüsselung, keine Authentifizierung, kein Passwort -* Verbindung über das lokale Netzwerk - -Die konkrete Konfiguration und der tatsächlich nutzbare Funktionsumfang hängen vom Wallbox-Modell und dessen Software ab. - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx index 3d6de169c3..c3fca183ce 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx @@ -1,6 +1,7 @@ --- title: OpenEVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openevse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ Benötigt mindestens Firmware 7.0 oder neuer. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `openevse` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx index fbd569aa01..6f7cbdeb1a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx @@ -1,6 +1,7 @@ --- title: openWB Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-pro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: openwb-pro host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `openwb-pro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx index 4ba305dfc2..ff39e51d05 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx @@ -1,6 +1,7 @@ --- title: openWB series2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,11 @@ Die Wallbox muss als Ladepunkt konfiguriert sein. connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional phases1p3p: false # Phasenumschaltung vorhanden, optional`} /> +## Templateparameter `openwb` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Phasenumschaltung vorhanden
`phases1p3p` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx new file mode 100644 index 0000000000..2ed389ad0e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx @@ -0,0 +1,53 @@ +--- +title: openWB Software 2.x +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# openWB Software 2.x + + + +Erfordert [`Software 2.x`](https://github.com/openWB/core). +Folgende Änderungen sind unter dem `Einstellungen`-Reiter erforderlich: + +* Steuerungsmodus: `secondary` +* Steuerung über Modbus als secondary: `An` + + +1 Ladepunkt), optional + phases1p3p: true # Phasenumschaltung vorhanden, optional`} /> + +## Templateparameter `openwb-2.0` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Phasenumschaltung vorhanden
`phases1p3p` | | Standard: `true` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx deleted file mode 100644 index d9746900f6..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2x.mdx +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: openWB Software 2.x -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# openWB Software 2.x - - - -Erfordert [`Software 2.x`](https://github.com/openWB/core). -Folgende Änderungen sind unter dem `Einstellungen`-Reiter erforderlich: - -* Steuerungsmodus: `secondary` -* Steuerung über Modbus als secondary: `An` - - -1 Ladepunkt), optional - phases1p3p: true # Phasenumschaltung vorhanden, optional`} /> - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx index 336896e3d6..fdcd8407be 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx @@ -1,6 +1,7 @@ --- title: Optec Mobility One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx index 62c438bd9e..2a827a67ea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx @@ -1,6 +1,7 @@ --- title: Orbis Viaris custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-orbis.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-orbis` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx index 0798c42b6c..63f10f1762 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx @@ -1,6 +1,7 @@ --- title: PC Electric Garo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pcelectric-garo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Es können momentan nur als Master konfigurierte Geräte verwendet werden! host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional`} /> +## Templateparameter `pcelectric-garo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `8080` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx new file mode 100644 index 0000000000..e9304f71d9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx @@ -0,0 +1,38 @@ +--- +title: Peblar Business +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Business + + + +Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. + + + + +## Templateparameter `peblar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx deleted file mode 100644 index c1b9e64dab..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-home-plus-business.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Peblar Home, Home Plus, Business -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Peblar Home, Home Plus, Business - - - -Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx new file mode 100644 index 0000000000..1528b514f1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx @@ -0,0 +1,38 @@ +--- +title: Peblar Home Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Home Plus + + + +Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. + + + + +## Templateparameter `peblar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx new file mode 100644 index 0000000000..ea14452341 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx @@ -0,0 +1,38 @@ +--- +title: Peblar Home +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Peblar Home + + + +Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. + + + + +## Templateparameter `peblar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx index 70a17c8f50..5014738e72 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact CHARX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `phoenix-charx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx index a22dc03947..253ff24f16 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EM-CP-PP-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-em-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-em-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx index 1ce4dfef3a..1652bdee12 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx index 8b1d2bd42b..645ef77635 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx index da755f7761..fd7136f5a8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx index 13bd5e578d..adfa4c975e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx index 1dce994e0f..933fea0dee 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -1,6 +1,7 @@ --- title: Phoenix Contact EV-SER custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-ser.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-ser` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx index d9b0a30cba..eb7fc20685 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx @@ -1,6 +1,7 @@ --- title: Plugchoice custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/plugchoice.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,5 +37,13 @@ Diese Anpassungen ermöglichen eine häufigere und detailliertere Meldung der La identity: # Identity des Ladepunkts (z.B. AA123456) connector: 1 # Ladepunkt (falls >1 Ladepunkt), Anschluss-ID (üblicherweise 1)`} /> +## Templateparameter `plugchoice` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | API Token | | ja | +| `identity` | Identity des Ladepunkts (z.B. AA123456) | | ja | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | Anschluss-ID (üblicherweise 1) | Standard: `1` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx index 21fbffc3ff..1c8bb313de 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Porsche Mobile Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,10 @@ import TabItem from '@theme/TabItem'; ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `pmcc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx index 38702225a8..a56e4d26ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -1,6 +1,7 @@ --- title: Porsche Mobile Charger Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,10 @@ import TabItem from '@theme/TabItem'; ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `pmcp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx index f95f2f6e01..e411cd46ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx @@ -1,6 +1,7 @@ --- title: Porsche Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/porsche-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `porsche-wallbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx index b636ea9625..9b4deb3d72 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx @@ -1,6 +1,7 @@ --- title: Pracht Alpha XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -62,5 +63,13 @@ import TabItem from '@theme/TabItem'; timeout: 10s # Zeitüberschreitung, optional connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `pracht-alpha` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx index 97a070820a..2e8b630717 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx @@ -1,6 +1,7 @@ --- title: Pracht Mono XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -62,5 +63,13 @@ import TabItem from '@theme/TabItem'; timeout: 10s # Zeitüberschreitung, optional connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `pracht-alpha` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx index f3c8ef3e99..cd560aa9e4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx @@ -1,6 +1,7 @@ --- title: Pracht PNI custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -62,5 +63,13 @@ import TabItem from '@theme/TabItem'; timeout: 10s # Zeitüberschreitung, optional connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +## Templateparameter `pracht-alpha` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx deleted file mode 100644 index f0394a0ac3..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xt.mdx +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Pracht XT+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Pracht XT+ - - - -1 Ladepunkt), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx new file mode 100644 index 0000000000..ce766e0539 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx @@ -0,0 +1,75 @@ +--- +title: Pracht XT+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Pracht XT+ + + + +1 Ladepunkt), optional`} /> + +## Templateparameter `pracht-alpha` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx index 4b9dbce34f..5d2644cc92 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx @@ -1,6 +1,7 @@ --- title: Pulsares SimpleBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsares.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `pulsares` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx index 3b44162c12..8bbc52ec56 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx @@ -1,6 +1,7 @@ --- title: Pulsatrix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsatrix.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,5 +20,11 @@ import TabItem from '@theme/TabItem'; template: pulsatrix host: 192.0.2.2 # IP-Adresse oder Hostname, Wird auf der dritten Displayseite des SECC angezeigt`} /> +## Templateparameter `pulsatrix` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | Wird auf der dritten Displayseite des SECC angezeigt | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx new file mode 100644 index 0000000000..c37ab4dd03 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -0,0 +1,45 @@ +--- +title: Qcells Q.HOME EDRIVE A +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME EDRIVE A + + + +Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. + + + + +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx deleted file mode 100644 index d107a6d43c..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-qhome-edrive-a.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Qcells Q.HOME EDRIVE A -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Qcells Q.HOME EDRIVE A - - - -Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx new file mode 100644 index 0000000000..a966da08b7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx @@ -0,0 +1,50 @@ +--- +title: Roth ThermoAura +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Roth ThermoAura + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx new file mode 100644 index 0000000000..83a157f2c0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx @@ -0,0 +1,50 @@ +--- +title: Roth ThermoTerra +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Roth ThermoTerra + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx index 46e0ecba3f..f31550ad51 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx @@ -1,6 +1,7 @@ --- title: Schneider EVlink Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/schneider-evlink-v3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,5 +25,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `schneider-evlink-v3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx index 823e8052be..6d68959462 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx @@ -1,6 +1,7 @@ --- title: Schrack i-CHARGE CION custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `ichargecion` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx index c5b75790d0..5dcc642663 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -1,6 +1,7 @@ --- title: SENEC Wallbox pro s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx index 90c4df5132..f7e4791aee 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx @@ -1,6 +1,7 @@ --- title: SENEC Wallbox pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,5 +33,12 @@ import TabItem from '@theme/TabItem'; port: 502 # Port timeout: 10s # Zeitüberschreitung, optional`} /> +## Templateparameter `abl` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx new file mode 100644 index 0000000000..59f9038219 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly 1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1 + + + + + +## Templateparameter `shelly` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx new file mode 100644 index 0000000000..2f8cb3548f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly Plug S +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Plug S + + + + + +## Templateparameter `shelly` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx new file mode 100644 index 0000000000..5d2272d6d0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly Plus 1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Plus 1 + + + + + +## Templateparameter `shelly` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx new file mode 100644 index 0000000000..679db318f6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx @@ -0,0 +1,50 @@ +--- +title: Shelly Pro 1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 1 + + + + + +## Templateparameter `shelly` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx deleted file mode 100644 index 8430a32a58..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly.mdx +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Shelly -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Shelly - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx index a95fbec292..065e9f07c0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -1,6 +1,7 @@ --- title: Siemens Versicharge GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/versicharge.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Erfordert Firmware >= 2.135 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `versicharge` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx index ce2c96e2ea..3142169e55 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Skoda Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx index a12627c2af..96c0b32360 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -1,6 +1,7 @@ --- title: Skoda Charger Pro Eichrecht custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx index 2290c464a1..1428ea0bcd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Skoda Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx index b7dc6b671e..e6b714629f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -1,6 +1,7 @@ --- -title: Skoda iV Charger Connect+ -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +title: Skoda iV Charger Connect +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,7 +10,7 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# Skoda iV Charger Connect+ +# Skoda iV Charger Connect @@ -19,11 +20,20 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. +Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + +## Templateparameter `elliconnect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx new file mode 100644 index 0000000000..88e95b309c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -0,0 +1,37 @@ +--- +title: Skoda iV Charger Connect+ +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Skoda iV Charger Connect+ + + + +Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + + + +## Templateparameter `ellipro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx new file mode 100644 index 0000000000..27c1dd418f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx @@ -0,0 +1,37 @@ +--- +title: SMA eCharger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA eCharger + + + +Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. + + + + +## Templateparameter `smaevcharger` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx deleted file mode 100644 index b813a61d22..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger-echarger.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: SMA EV Charger, eCharger -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA EV Charger, eCharger - - - -Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx new file mode 100644 index 0000000000..73f81afccb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx @@ -0,0 +1,37 @@ +--- +title: SMA EV Charger +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA EV Charger + + + +Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. + + + + +## Templateparameter `smaevcharger` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx index 61f6c01afe..d67129dc9f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx @@ -1,6 +1,7 @@ --- title: Smartfox Pro Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `ichargecion` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx index 1bd8cafd72..3ae4e7958d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx @@ -1,6 +1,7 @@ --- title: smartWB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartwb.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,3 +20,9 @@ import TabItem from '@theme/TabItem'; template: smartwb host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `smartwb` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx index 24f535390d..627c1e4b61 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -1,6 +1,7 @@ --- title: SolarEdge Home EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,12 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx index d120715344..5a8830372b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx @@ -1,6 +1,7 @@ --- title: Solax X3-EVC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem e host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx index 58d7bb72c3..1504eb382f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx @@ -1,6 +1,7 @@ --- title: Sonnen sonnenCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Die Wallbox muss sich im "Power" Modus befinden. host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +## Templateparameter `etrel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx index b187ccf0ea..9371153c2c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -1,6 +1,7 @@ --- title: Spelsberg Wallbox Smart Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx index 17e1380699..013c3ea84d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx @@ -1,6 +1,7 @@ --- title: Stark in Strom Easy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `evse-din` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx new file mode 100644 index 0000000000..7fafd494f3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -0,0 +1,35 @@ +--- +title: Stiebel Eltron LWA/LWZ (SG Ready) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Stiebel Eltron LWA/LWZ (SG Ready) + + + + + +## Templateparameter `stiebel-lwa` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx deleted file mode 100644 index 0e82b0b167..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwalwz-sg-ready.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Stiebel Eltron LWA/LWZ (SG Ready) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Stiebel Eltron LWA/LWZ (SG Ready) - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx index 06d76f6cc1..11c5272f77 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Stiebel Eltron WPM (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-wpm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperaturquelle, [warmwater, buffer] (optional)`} /> +## Templateparameter `stiebel-wpm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx index 3ee7b944e7..f2e0142503 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx @@ -1,6 +1,7 @@ --- title: Sungrow AC011E-01 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `sungrow` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx index c19099b74b..bd19607162 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx @@ -1,6 +1,7 @@ --- title: Sungrow AC011E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-sungrow.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-sungrow` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx new file mode 100644 index 0000000000..33e2a52349 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx @@ -0,0 +1,48 @@ +--- +title: Sungrow AC22E-01 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sungrow AC22E-01 + + + + + +## Templateparameter `sungrow` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx index 3f8e724bf4..fcdf240a74 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx @@ -1,6 +1,7 @@ --- title: Tasmota einphasig custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tasmota.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,16 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `tasmota` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | Standard-User ist admin | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| Schaltkanal Nummer
`channel` | Schaltkanal (1-8) | Standard: `1` | ja | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx index af8cb81b98..e8a4081fba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Tecalor THZ (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port tempsource: # Temperaturquelle, [warmwater] (optional)`} /> +## Templateparameter `stiebel-lwa` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx index 7ed51d2d09..8a6a17792c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx @@ -1,6 +1,7 @@ --- title: TechniSat Technivolt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx deleted file mode 100644 index 50c87660ab..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-twc3.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Tesla TWC3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Tesla TWC3 - - - -Die TWC Wallbox ist nicht direkt regelbar. Die Regelung erfolgt über das Fahrzeug. Das Fahrzeug muss am TWC3 Ladepunkt ausgewählt sein. Aktuell ausschließlich mit [Tesla Fahrzeugen](https://docs.evcc.io/docs/devices/vehicles#tesla) nutzbar. - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx new file mode 100644 index 0000000000..0f552fdf64 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -0,0 +1,31 @@ +--- +title: Tesla Wall Connector (Gen 3) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tesla Wall Connector (Gen 3) + + + +Die TWC Wallbox ist nicht direkt regelbar. Die Regelung erfolgt über das Fahrzeug. Das Fahrzeug muss am TWC3 Ladepunkt ausgewählt sein. Aktuell ausschließlich mit [Tesla Fahrzeugen](https://docs.evcc.io/docs/devices/vehicles#tesla) nutzbar. + + + + +## Templateparameter `twc3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx index b9009a1e18..ee8146b422 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx @@ -1,6 +1,7 @@ --- title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tessie.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung de token: # Tessie API Token location: tessiehome # Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive)`} /> +## Templateparameter `tessie` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Tessie API Token
`token` | | | ja | +| Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive)
`location` | | Beispiel: `tessiehome` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx index 7453e94e74..e31f177625 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx @@ -1,6 +1,7 @@ --- title: Tigo GO EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem e host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx index cbfeaa496d..998eebba39 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,15 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `tinkerforge-warp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | IP Adresse oder der Hostname des MQTT Brokers | Beispiel: `192.0.2.2` | ja | +| Port
`port` | MQTT Broker Port | Standard: `1883` | nein | +| Topic
`topic` | Topic (ohne / am Anfang) | Standard: `warp` | nein | +| Zeitüberschreitung
`timeout` | Akzeptiere keine Daten die älter sind als dieser Wert | Standard: `30s`
Beispiel: `10s` | nein | +| `energymanager` | WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) | | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx index 63b110d8bd..61ebcda67e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,15 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `tinkerforge-warp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | IP Adresse oder der Hostname des MQTT Brokers | Beispiel: `192.0.2.2` | ja | +| Port
`port` | MQTT Broker Port | Standard: `1883` | nein | +| Topic
`topic` | Topic (ohne / am Anfang) | Standard: `warp` | nein | +| Zeitüberschreitung
`timeout` | Akzeptiere keine Daten die älter sind als dieser Wert | Standard: `30s`
Beispiel: `10s` | nein | +| `energymanager` | WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) | | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx index a2087d6d2b..3f936b9a96 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP3 Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,14 @@ Die automatische Phasenumschaltung bei 1p Fahrzeugen muss deaktiviert sein. Sieh user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `tinkerforge-warp3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | IP Adresse oder der Hostname des MQTT Brokers | Beispiel: `192.0.2.2` | ja | +| Port
`port` | MQTT Broker Port | Standard: `1883` | nein | +| Topic
`topic` | Topic (ohne / am Anfang) | Standard: `warp` | nein | +| Zeitüberschreitung
`timeout` | Akzeptiere keine Daten die älter sind als dieser Wert | Standard: `30s`
Beispiel: `10s` | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx index 69846404ec..b391e7f494 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -1,6 +1,7 @@ --- title: TinkerForge WARP3 Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3-smart.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,14 @@ import TabItem from '@theme/TabItem'; user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `tinkerforge-warp3-smart` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | IP Adresse oder der Hostname des MQTT Brokers | Beispiel: `192.0.2.2` | ja | +| Port
`port` | MQTT Broker Port | Standard: `1883` | nein | +| Topic
`topic` | Topic (ohne / am Anfang) | Standard: `warp` | nein | +| Zeitüberschreitung
`timeout` | Akzeptiere keine Daten die älter sind als dieser Wert | Standard: `30s`
Beispiel: `10s` | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx index e577e404c2..f8bd2a1ce3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tplink.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `tplink` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx index e061ba0e87..13b3482f2d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tapo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,15 @@ import TabItem from '@theme/TabItem'; heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> +## Templateparameter `tapo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | +| Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | +| Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx index d52f371489..dc71bf9799 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx @@ -1,6 +1,7 @@ --- title: Ubitricity Heinz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx index e82c26347e..bdbce3d5e1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx @@ -1,6 +1,7 @@ --- title: V2C Trydan custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/trydan.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,5 +20,11 @@ import TabItem from '@theme/TabItem'; template: trydan host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `trydan` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx index e5d4e67049..803773dc48 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Vaillant SensoNET (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vaillant.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,13 @@ Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird d zone: # Id der Boostzone (optional) setpoint: # Boost Temperatur (optional)`} /> +## Templateparameter `vaillant` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `realm` | | Standard: `DE`
Auswahl: `DE`, `AT` | nein | +| `zone` | Id der Boostzone | | nein | +| `setpoint` | Boost Temperatur | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx new file mode 100644 index 0000000000..392b57ef36 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx @@ -0,0 +1,38 @@ +--- +title: Vestel Connect Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vestel Connect Plus + + + +1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. + + + + +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx deleted file mode 100644 index ea9ecb7d05..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart-connect-plus.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Vestel EVC04 Home Smart, Connect Plus -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Vestel EVC04 Home Smart, Connect Plus - - - -1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx new file mode 100644 index 0000000000..07bac2a8e7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -0,0 +1,38 @@ +--- +title: Vestel EVC04 Home Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Vestel EVC04 Home Smart + + + +1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. + + + + +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx index c1c5da1cb9..f8ff064976 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -1,6 +1,7 @@ --- title: Victron EV Charging Station (via GX) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,9 @@ Trage den Host des GX-Gerätes (nicht der Wallbox) ein. Die Wallbox muss sich im host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `victron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx index 0e1ebfc8c3..b61b976d3e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx @@ -1,6 +1,7 @@ --- title: Victron EV Charging Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron-evcs.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,9 @@ Trage den Host der Wallbox (nicht des GX-Geräts) ein und stelle sicher, dass di host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `victron-evcs` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx index 18ffb396a7..4ecb8dff72 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -1,6 +1,7 @@ --- title: Viessmann Heatpump (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/viessmann.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,7 +25,19 @@ Einmalige Warmwasserbereitung auf eine konfigurierbare Solltemperatur. Das Gerä password: # Passwort, Für den konfigurierten Viessmann Account. clientid: # Client ID, Konfigurieren in [app.developer.viessmann.com](https://app.developer.viessmann.com) gateway_serial: # Gateway Serial, Seriennummer des VitoConnect modul (VitoCare App -> Einstellungen -> Kommunikationsmodul -> Seriennummer) - installation_id: # Installation ID, siehe https://docs.evcc.io/en/docs/devices/heating#viessmann + installation_id: # Installation ID, Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...
Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: \`\`\` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= \`\`\` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable 'CODE' nur 20 Sekunden gültig ist): \`\`\` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\\?code=\\(.*\\).*/\\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) \`\`\` Damit können wir jetzt die Installation ID abfragen: \`\`\` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' \`\`\` device_id: 0 # Device ID, normalerweise \`0\` target_temperature: 45 # Zieltemperatur für Einmal-Warmwasser-Zubereitung (°C), max. 60°C`} /> +## Templateparameter `viessmann` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | Registrieren auf \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | ja | +| Passwort
`password` | Für den konfigurierten Viessmann Account. | | ja | +| Client ID
`clientid` | Konfigurieren in \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | ja | +| Gateway Serial
`gateway_serial` | Seriennummer des VitoConnect modul (VitoCare App -> Einstellungen -> Kommunikationsmodul -> Seriennummer) | | ja | +| Installation ID
`installation_id` | Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...<br/> Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: ``` VIESSMANN_USER=<your-user> VIESSMANN_PASS=<your-password> VIESSMANN_CLIENT_ID=<your-clientid> ``` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable 'CODE' nur 20 Sekunden gültig ist): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ \| grep "^location: " \ \| sed 's/.*\?code=\(.*\).*/\1/' \ \| tr -d '\[:space:\]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE \| jq --raw-output .access_token) ``` Damit können wir jetzt die Installation ID abfragen: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ \| jq '.data\[\].id' ``` | | ja | +| Device ID
`device_id` | normalerweise `0` | | ja | +| Zieltemperatur für Einmal-Warmwasser-Zubereitung
`target_temperature` | max. 60°C | Standard: `45`
Einheit: °C | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx new file mode 100644 index 0000000000..7f7d6a4b21 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -0,0 +1,46 @@ +--- +title: Viridian EV EVSE EPC 2.0 Plus +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Viridian EV EVSE EPC 2.0 Plus + + + + + +## Templateparameter `obo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx deleted file mode 100644 index 3325e35d37..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-20-plus.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Viridian EV EVSE EPC 2.0 Plus -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Viridian EV EVSE EPC 2.0 Plus - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx index b6fdaf99b8..dbb67fdfb2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx index 6b06fbf8f8..c35e8f3e1c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx index c99e491002..fe6acb2b94 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elli-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx index c62c584763..abd76c27d6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen ID. Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,10 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `elliconnect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx index fab670518c..b843e7d5df 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen ID. Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,10 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +## Templateparameter `ellipro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Identifikationsschlüssel (SKI)
`ski` | Üblicherweise im Web Interface der Wallbox zu finden | | ja | +| IP-Adresse
`ip` | | Beispiel: `192.0.2.2` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx index e767e9d7a5..385ea4b2e2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx @@ -1,6 +1,7 @@ --- title: Volt Time One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Seriennummer (z. B. 1008621)`} /> +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| `serial_number` | Seriennummer (z. B. 1008621) | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx index e71f1369fb..b0199ff719 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx @@ -1,6 +1,7 @@ --- title: Volt Time Source 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Seriennummer (z. B. 1008621)`} /> +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| `serial_number` | Seriennummer (z. B. 1008621) | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx index f71a1d8e70..8d4b4e3e3d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx @@ -1,6 +1,7 @@ --- title: Volt Time Source 2s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Seriennummer (z. B. 1008621)`} /> +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| `serial_number` | Seriennummer (z. B. 1008621) | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx index 8cba9adbb9..b82cdb0065 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx @@ -1,6 +1,7 @@ --- title: Volt Time Source custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,5 +21,12 @@ import TabItem from '@theme/TabItem'; token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) serial_number: # Seriennummer (z. B. 1008621)`} /> +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| `serial_number` | Seriennummer (z. B. 1008621) | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx new file mode 100644 index 0000000000..ef56c59886 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -0,0 +1,38 @@ +--- +title: Wallbe Eco 2.0(s) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wallbe Eco 2.0(s) + + + +DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. + + + + +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx deleted file mode 100644 index d7dd84203c..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-20s.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Wallbe Eco 2.0(s) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Wallbe Eco 2.0(s) - - - -DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx index c7e188c01f..8c8dbb905e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx @@ -1,6 +1,7 @@ --- title: Wallbe Eco custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx index 8a1336f455..6ab2dd59df 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx @@ -1,6 +1,7 @@ --- title: Wallbe Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx new file mode 100644 index 0000000000..33b68eea42 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Commander 2 (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Commander 2 (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `wallbox-fw5` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx deleted file mode 100644 index 45cfcedde7..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Commander 2 (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Commander 2 (FW 5.x) - - - -Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren -* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) -* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird -* Passwort: leer lassen - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx index 970f13a9b1..4b0be8a1f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx @@ -1,6 +1,7 @@ --- title: wallbox Commander 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-wallbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx new file mode 100644 index 0000000000..5bf247b395 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Copper SB (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Copper SB (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `wallbox-fw5` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx deleted file mode 100644 index 6c147c884e..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Copper SB (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Copper SB (FW 5.x) - - - -Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren -* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) -* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird -* Passwort: leer lassen - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx index 33a94a6b01..34f9db496d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx @@ -1,6 +1,7 @@ --- title: wallbox Copper SB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-wallbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx new file mode 100644 index 0000000000..6887a5d29d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Pulsar Max (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Max (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `wallbox-fw5` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx deleted file mode 100644 index 7ca98d6ee5..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Pulsar Max (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Pulsar Max (FW 5.x) - - - -Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren -* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) -* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird -* Passwort: leer lassen - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx index 70a81a7dc2..385c11544d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx @@ -1,6 +1,7 @@ --- title: wallbox Pulsar Max custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-wallbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx new file mode 100644 index 0000000000..294310a8fb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -0,0 +1,55 @@ +--- +title: wallbox Pulsar Plus (FW 5.x) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# wallbox Pulsar Plus (FW 5.x) + + + +Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + +* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren +* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) +* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) +* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird +* Passwort: leer lassen + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `wallbox-fw5` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx deleted file mode 100644 index 172fb23942..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5x.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: wallbox Pulsar Plus (FW 5.x) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# wallbox Pulsar Plus (FW 5.x) - - - -Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - -* “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren -* Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) -* URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) -* Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird -* Passwort: leer lassen - - -:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx index 904fab7f39..aa6bdefcff 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -1,6 +1,7 @@ --- title: wallbox Pulsar Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,5 +39,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-wallbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx index 2d4eeaf490..13eab1c834 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -1,6 +1,7 @@ --- title: Walther Werke Basic Evo Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,5 +35,11 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx index 6d3990bb06..06564f93b2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx @@ -1,6 +1,7 @@ --- title: Webasto Live custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx index cc3bbed86a..6687836b0b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx @@ -1,6 +1,7 @@ --- title: Webasto NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,5 +24,12 @@ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gel host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +## Templateparameter `webasto-next` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx index 0440efb17b..aa68bc935b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx @@ -1,6 +1,7 @@ --- title: Webasto Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,5 +28,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx index 97fa1efa45..bd6161e5f9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller AC Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/weidmüller.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -19,5 +20,11 @@ import TabItem from '@theme/TabItem'; template: weidmüller host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `weidmüller` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx new file mode 100644 index 0000000000..f2c4533606 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx @@ -0,0 +1,50 @@ +--- +title: Wolf BWL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wolf BWL + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx new file mode 100644 index 0000000000..515d74d3cd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx @@ -0,0 +1,50 @@ +--- +title: Wolf BWS +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Wolf BWS + + + +Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. + + + + +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx index ec8e3c7796..14bc7bc52f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx @@ -1,6 +1,7 @@ --- title: Zaptec Go 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,5 +22,13 @@ import TabItem from '@theme/TabItem'; user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `zaptec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `id` | Wallbox ID | | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx new file mode 100644 index 0000000000..339def8e98 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx @@ -0,0 +1,51 @@ +--- +title: Zaptec Go (OCPP) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-zaptec.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zaptec Go (OCPP) + + + +OCPP Native mode + +https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ + + +:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-zaptec + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + +## Templateparameter `ocpp-zaptec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx index 892f2dbeff..0c6aedc83b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx @@ -1,6 +1,7 @@ --- title: Zaptec Go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,5 +22,13 @@ import TabItem from '@theme/TabItem'; user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `zaptec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `id` | Wallbox ID | | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx index 83b19e4d18..4ae91fb588 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx @@ -1,6 +1,7 @@ --- title: Zaptec Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,5 +22,13 @@ import TabItem from '@theme/TabItem'; user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `zaptec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `id` | Wallbox ID | | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx index 64d20c8755..a7970062c4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -1,6 +1,7 @@ --- title: Zewotherm EU-L Serie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,11 @@ Energiemanagementeinstellungen am Gerät: tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) watchdog: 60s # optional`} /> +## Templateparameter `lambda-zewotherm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Temperaturquelle
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx index f88bb2b3b8..27244a3ef5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -1,6 +1,7 @@ --- title: ZJ Beny BCP EV charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-beny.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,5 +30,17 @@ import TabItem from '@theme/TabItem'; meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> +## Templateparameter `ocpp-beny` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | +| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | +| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | +| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx index 05e6f82e57..034c2000d0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx @@ -1,6 +1,7 @@ --- title: A-Tronix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `delay` | | Standard: `100ms` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx deleted file mode 100644 index 0598b30e97..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43-a44-b23-b24.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: ABB A43, A44, B23, B24 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ABB A43, A44, B23, B24 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx new file mode 100644 index 0000000000..43a3c91f65 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx @@ -0,0 +1,69 @@ +--- +title: ABB A43 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB A43 + + + + + + + + + + + + + + + + +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx new file mode 100644 index 0000000000..774ec57e93 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx @@ -0,0 +1,69 @@ +--- +title: ABB A44 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB A44 + + + + + + + + + + + + + + + + +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx new file mode 100644 index 0000000000..cc5a096fce --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx @@ -0,0 +1,69 @@ +--- +title: ABB B23 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB B23 + + + + + + + + + + + + + + + + +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx new file mode 100644 index 0000000000..ea71c609e4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx @@ -0,0 +1,69 @@ +--- +title: ABB B24 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ABB B24 + + + + + + + + + + + + + + + + +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx deleted file mode 100644 index 97d8372e11..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300-wireless-metering-meter.mdx +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Acrel ADW300 Wireless Metering Meter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Acrel ADW300 Wireless Metering Meter - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx new file mode 100644 index 0000000000..2d40765701 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx @@ -0,0 +1,109 @@ +--- +title: Acrel ADW300 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Acrel ADW300 + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `acrel-adw300` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx index 1767123f8d..3d4e4b48cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx @@ -1,6 +1,7 @@ --- title: Ads-tec StoraXe custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/storaxe.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,10 @@ import TabItem from '@theme/TabItem'; port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional`} /> +## Templateparameter `storaxe` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx index e8200aa134..664267d1cb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx @@ -1,6 +1,7 @@ --- title: Alpha ESS Storion SMILE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/alpha-ess-smile.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -180,3 +181,13 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder +## Templateparameter `alpha-ess-smile` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx new file mode 100644 index 0000000000..1b5b4f5624 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx @@ -0,0 +1,190 @@ +--- +title: Ampere Ampere.StoragePro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Ampere Ampere.StoragePro + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `saj-h2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | Standard: `2` | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx deleted file mode 100644 index f130e884b1..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-amperestoragepro.mdx +++ /dev/null @@ -1,179 +0,0 @@ ---- -title: Ampere Ampere.StoragePro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Ampere Ampere.StoragePro - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx index 440d80e22e..41da27a8d8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Anker Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `deye-mi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx index 3269bbd6d1..7a84f287e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx @@ -1,6 +1,7 @@ --- title: APsystems EZ1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/apsystems-ez1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `apsystems-ez1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx index b1e741b5af..907cf00f93 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx @@ -1,6 +1,7 @@ --- title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fritzdect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,12 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `fritzdect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| URI
`uri` | HTTP(S) Adresse | Standard: `https://fritz.box` | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Aktoridentifikationsnummer (AIN)
`ain` | Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. | Beispiel: `307788992233` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx index c41d0e73cd..1b3812cebf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -1,6 +1,7 @@ --- title: Axitec AXIhycon 12-15H custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -118,3 +119,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `solis-hybrid-s` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx index 8316da5f1c..6760c68ae1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -1,6 +1,7 @@ --- title: Bernecker Engineering MPM3PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mpm3pm.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `mpm3pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx index c647d3f014..5e3d5482ba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx @@ -1,6 +1,7 @@ --- title: BGEtech DS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ds100.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -128,3 +129,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `bge_tech_ds100` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx index 0b5dce5c2d..f750a26124 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx @@ -1,6 +1,7 @@ --- title: BGEtech WS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ws100.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -128,3 +129,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `bge_tech_ws100` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx index 608638a888..6b7d70e416 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -1,6 +1,7 @@ --- title: Bosch BPT-S 5 Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bosch-bpt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `bosch-bpt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| URI
`uri` | HTTP(S) Adresse | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx index 3e097c9564..b275c69de4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Bosswerk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `deye-mi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx new file mode 100644 index 0000000000..5a648dd9ce --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -0,0 +1,69 @@ +--- +title: Carlo Gavazzi EM110/111/112 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM110/111/112 + + + + + + + + + + + + + + + + +## Templateparameter `cg-emt1xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx deleted file mode 100644 index 2c0f809f50..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110111112.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Carlo Gavazzi EM110/111/112 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM110/111/112 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx index 8060895e58..0be77cfd07 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx @@ -1,6 +1,7 @@ --- title: Carlo Gavazzi EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -63,3 +64,9 @@ EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschl +## Templateparameter `cg-em24` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx new file mode 100644 index 0000000000..97f565f87e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -0,0 +1,59 @@ +--- +title: Carlo Gavazzi EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM24_E1 + + + +EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. +Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + +## Templateparameter `cg-em24_e1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx deleted file mode 100644 index bcd372e093..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24e1.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Carlo Gavazzi EM24_E1 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM24_E1 - - - -EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. -Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx new file mode 100644 index 0000000000..0e70cf17fc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -0,0 +1,81 @@ +--- +title: Carlo Gavazzi EM330/EM340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM330/EM340 + + + + + + + + + + + + + + + + +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx deleted file mode 100644 index 183343d433..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330em340.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Carlo Gavazzi EM330/EM340 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM330/EM340 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx new file mode 100644 index 0000000000..8f9a7dacde --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -0,0 +1,81 @@ +--- +title: Carlo Gavazzi EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi EM530/EM540 + + + + + + + + + + + + + + + + +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx deleted file mode 100644 index fde201846d..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530em540.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Carlo Gavazzi EM530/EM540 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi EM530/EM540 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx index 03e0ba9f5d..16cc3f033e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx @@ -1,6 +1,7 @@ --- title: Carlo Gavazzi ET112 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `cg-emt1xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx new file mode 100644 index 0000000000..ae737b6440 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -0,0 +1,81 @@ +--- +title: Carlo Gavazzi ET330/ET340 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Carlo Gavazzi ET330/ET340 + + + + + + + + + + + + + + + + +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx deleted file mode 100644 index df0fd9dd0b..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330et340.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Carlo Gavazzi ET330/ET340 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Carlo Gavazzi ET330/ET340 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx index 4f8f0459bd..727412dce4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx @@ -1,6 +1,7 @@ --- title: cFos PowerBrain Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cfos.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,5 +26,11 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 4702 # Port`} /> +## Templateparameter `cfos` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx index 4913718983..87ea7e4c86 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx @@ -1,6 +1,7 @@ --- title: Demobatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-battery.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,15 @@ Zu Demonstrationszwecken. Hausbatterie mit festen Werten. currentL2: # L2 Stromstärke (A), optional currentL3: # L3 Stromstärke (A), optional`} /> +## Templateparameter `demo-battery` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Leistung
`power` | | Einheit: W | nein | +| Ladestand
`soc` | | Einheit: % | nein | +| Steuerbar
`controllable` | Unterstützt aktive Batteriesteuerung | | nein | +| Zählerstand
`energy` | | Einheit: kWh | nein | +| L1 Stromstärke
`currentL1` | | Einheit: A | nein | +| L2 Stromstärke
`currentL2` | | Einheit: A | nein | +| L3 Stromstärke
`currentL3` | | Einheit: A | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx index a9eea10c5e..7b2101396a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx @@ -1,6 +1,7 @@ --- title: Demozähler custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -95,3 +96,13 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. +## Templateparameter `demo-meter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Leistung
`power` | | Einheit: W | nein | +| Zählerstand
`energy` | | Einheit: kWh | nein | +| L1 Stromstärke
`currentL1` | | Einheit: A | nein | +| L2 Stromstärke
`currentL2` | | Einheit: A | nein | +| L3 Stromstärke
`currentL3` | | Einheit: A | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx index b54b13284c..18acec57a1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `deye-hybrid-3p` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx index a8c602e952..3ac8c2b567 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -183,3 +184,15 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `deye-hybrid-hp3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| `storageunit` | | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| GEN-Anschluss als Solar-Eingang verwenden
`includegenport` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx index ecdbcc3b76..6df694d6ed 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `deye-mi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx index bd3e96b7a6..1f02cbf912 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `deye-storage` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx index a2c6861fe6..a7f6523687 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx @@ -1,6 +1,7 @@ --- title: Deye String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `deye-string` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx index ced4a791da..371519b021 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx @@ -1,6 +1,7 @@ --- title: Discovergy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/discovergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,3 +41,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `discovergy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| `meter` | | Beispiel: `1ESY1161229886` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx index 6e777f338f..6ab03c1cdc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx @@ -1,6 +1,7 @@ --- title: DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dsmr.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,11 @@ import TabItem from '@theme/TabItem'; port: 1502 # Port, optional energy: # OBIS Kennzahl für Energieverbrauch, Typischerweise 1-0:1.8.0, bei Mehrtarifzählern 1-0:1.8.1 oder 1-0:1.8.2 (optional)`} /> +## Templateparameter `dsmr` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `1502` | nein | +| OBIS Kennzahl für Energieverbrauch
`energy` | Typischerweise 1-0:1.8.0, bei Mehrtarifzählern 1-0:1.8.1 oder 1-0:1.8.2 | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx index 2aa2c5fae7..8a84b58ac3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx @@ -1,6 +1,7 @@ --- title: DZG DVH4013 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dzg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `dzg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx new file mode 100644 index 0000000000..3638b6f4ba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx @@ -0,0 +1,111 @@ +--- +title: E3/DC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# E3/DC + + + +Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key (=RSCP-Passwort) muss im Hauskraftwerk unter Personalisieren/Benutzerprofil angelegt werden. Die IP-Adressen von evcc und des Hauskraftwerks müssen sich im selben Subnetz befinden. + +**Achtung**: Die aktive Batteriesteuerung überschreibt Einstellungen im Smart-Power/Betriebsbereich. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `e3dc-rscp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `5033` | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| `key` | | | ja | +| Entladelimit in W
`dischargelimit` | Limitiert die Entladeleistung im 'Halten' Batteriemodus | | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx deleted file mode 100644 index 721deb28a5..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3dc.mdx +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: E3/DC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# E3/DC - - - -Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key (=RSCP-Passwort) muss im Hauskraftwerk unter Personalisieren/Benutzerprofil angelegt werden. Die IP-Adressen von evcc und des Hauskraftwerks müssen sich im selben Subnetz befinden. - -**Achtung**: Die aktive Batteriesteuerung überschreibt Einstellungen im Smart-Power/Betriebsbereich. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx index 29837af174..09c27b44b2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM120-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm120.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -82,3 +83,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron-sdm120` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx new file mode 100644 index 0000000000..37cd676367 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx @@ -0,0 +1,69 @@ +--- +title: Eastron SDM220/230 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Eastron SDM220/230 + + + + + + + + + + + + + + + + +## Templateparameter `eastron-sdm220_230` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx deleted file mode 100644 index 38337014d0..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220230.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Eastron SDM220/230 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Eastron SDM220/230 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx index 9dff8a8c0c..d146a5e6cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM630-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx index a2408b439d..9345728bab 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM72D-M custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm72.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron-sdm72` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx index 25c8b12d1a..ad958e9660 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -1,6 +1,7 @@ --- title: Eastron SDM72DM-V2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx index 8d461098e3..c1a56d7a13 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx @@ -1,6 +1,7 @@ --- title: Enphase IQ Envoy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/enphase.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -74,3 +75,12 @@ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vo +## Templateparameter `enphase` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| `token` | Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx index 8ee11a4d1d..214211d2db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -1,6 +1,7 @@ --- title: ESPHome DLMS Meter Austria custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/esphome-dlms-austria.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,10 @@ konfiguriert für österreichische DLMS-Zähler. host: 192.0.2.2 # IP-Adresse oder Hostname timeout: 10s # Zeitüberschreitung, optional`} /> +## Templateparameter `esphome-dlms-austria` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Zeitüberschreitung
`timeout` | | Standard: `10s`
Beispiel: `10s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx index a1d4d8c87e..ad6cac2aec 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx @@ -1,6 +1,7 @@ --- title: ESPHome DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle`} /> +## Templateparameter `slimmelezer` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Skalierungsfaktor
`scale` | Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle | Standard: `1000`
Beispiel: `1 \| 10 \| 100 \| 1000` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx index 5665d4f5b1..3dac12461a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx @@ -1,6 +1,7 @@ --- title: FENECON custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries +## Templateparameter `openems` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | Standard: `user` | nein | +| `battery` | steuerbare Batterie Komponente | Beispiel: `ess0` | nein | +| `watchdog` | abgestimmt auf das API-Timeout | Standard: `60s` | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx index dd45265132..dc2718ea03 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: FoxESS H1 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `fox-ess-h1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx index 0a83251695..5582d47d30 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: FoxESS H3 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `fox-ess-h3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx index db5cff44fa..e93dd23f7e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: FoxESS H3-Smart Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3-smart.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `fox-ess-h3-smart` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx index aeb56e21b6..2c1d672f9b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx @@ -1,6 +1,7 @@ --- title: Fronius Ohmpilot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-ohmpilot.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname key: 0 # ID des Ohmpilot im SolarAPI, optional`} /> +## Templateparameter `fronius-ohmpilot` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| ID des Ohmpilot im SolarAPI
`key` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx index 515353965c..3b98dcda71 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -1,6 +1,7 @@ --- title: Fronius Primo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `fronius-gen24` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| `id` | Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). | Standard: `200` | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx index 3c6dbc17c6..5beeb8c359 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -1,6 +1,7 @@ --- title: Fronius Smartmeter (über Wechselrichter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sunspec-meter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx index ebfa339507..b24d0c4857 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx @@ -1,6 +1,7 @@ --- title: Fronius Solar API V1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-solarapi-v1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -17,7 +18,7 @@ Solar API sollte nur als Fallback genutzt werden. Die Integration über Modbus i Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt. -**Achtung**: Die aktive Batteriesteuerung sollte nur verwendet werden, wenn keine weiteren Einstellungen für die zeitabhängige Batteriesteuerung in der Wechselrichter-Konfiguration unter "Energiemanagement" - "Batteriemanagement" getätigt wurden, denn bestehende Einstellungen werden überschrieben. +**Achtung**: Die aktive Batteriesteuerung sollte nur verwendet werden, wenn keine weiteren Einstellungen für die zeitabhängige Batteriesteuerung in der Wechselrichter-Konfiguration unter "Energiemanagement" - "Batteriemanagement" getätigt wurden, denn bestehende Einstellungen werden überschrieben. Es ist der geeignete Konfigurationspfad auszuwählen! @@ -30,7 +31,15 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} advanced={`meters: + - name: my_grid + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> @@ -42,7 +51,15 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} advanced={`meters: + - name: my_pv + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> @@ -62,8 +79,19 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - capacity: 50 # Akkukapazität (kWh), optional`} /> + capacity: 50 # Akkukapazität (kWh), optional + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> +## Templateparameter `fronius-solarapi-v1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzername (für aktive Batteriesteuerung)
`user` | bspw. E-Mail Adresse, User Id, etc. | Standard: `customer` | nein | +| Passwort (für aktive Batteriesteuerung)
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Firmware Versionen ab 1.36.5-1 erfordern /api/config.
`batteryconfiguri` | | Standard: `/config`
Auswahl: `/config`, `/api/config` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx index 20b404c71e..1e414de808 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -1,6 +1,7 @@ --- title: Fronius Symo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `fronius-gen24` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| `id` | Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). | Standard: `200` | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx index cbd10dd517..fa02ac36c7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -1,6 +1,7 @@ --- title: Ginlong Solis Hybrid Inverter (RHI series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -118,3 +119,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `solis-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx index cd8b88c9a8..87d282643e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -1,6 +1,7 @@ --- title: Ginlong Solis Hybrid Inverter (S Series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -118,3 +119,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `solis-hybrid-s` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx index 645a149fcd..fbe8d5dbc9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx @@ -1,6 +1,7 @@ --- title: Ginlong Solis Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `solis` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx index 87c3ba9b15..b8c81bd86f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx @@ -1,6 +1,7 @@ --- title: go-e Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/go-e-controller.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `go-e-controller` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx new file mode 100644 index 0000000000..01b0b52d83 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -0,0 +1,165 @@ +--- +title: GoodWe ET/EH/BH/BT Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe ET/EH/BH/BT Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `goodwe-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip`, `udp` | nein | +| `battery` | | Standard: `1`
Auswahl: `1`, `2` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx deleted file mode 100644 index 64eb78fef2..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-etehbhbt-hybrid-inverter.mdx +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: GoodWe ET/EH/BH/BT Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# GoodWe ET/EH/BH/BT Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx index 60119199fc..bde8abfe0b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -1,6 +1,7 @@ --- title: GoodWe GoodWe over Wifi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-wifi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `goodwe-wifi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse des Hostname
`uri` | HTTP(S) Adresse | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx new file mode 100644 index 0000000000..e6c865cef4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -0,0 +1,47 @@ +--- +title: GoodWe SDT/DT Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# GoodWe SDT/DT Inverter + + + + + +## Templateparameter `goodwe-dt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx deleted file mode 100644 index 0809d0ea25..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdtdt-inverter.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: GoodWe SDT/DT Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# GoodWe SDT/DT Inverter - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx index 4f78e350b4..e9a917a812 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Growatt Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -154,3 +155,11 @@ Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modu +## Templateparameter `growatt-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx new file mode 100644 index 0000000000..50b6222b38 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -0,0 +1,159 @@ +--- +title: Growatt TL-X(H) Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Growatt TL-X(H) Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `growatt-hybrid-tlxh` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx deleted file mode 100644 index f8b4211411..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-xh-hybrid-inverter.mdx +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: Growatt TL-X(H) Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Growatt TL-X(H) Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx index c992f77738..1e3dd33706 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx @@ -1,6 +1,7 @@ --- title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homematic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -88,3 +89,14 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `homematic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Geräteadresse/Seriennummer
`device` | Homematic Geräte Id, wie im CCU Webfrontend angezeigt. | Beispiel: `0001EE89AAD848` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1)
`meterchannel` | Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. | Standard: `6` | ja | +| XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h)
`cache` | Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx index 187c382c7f..76ea382498 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx @@ -1,6 +1,7 @@ --- title: HomeWizard kWh Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard-kwh.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `homewizard-kwh` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx index e8ff6e6ce3..66dc3f860c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -1,6 +1,7 @@ --- title: HomeWizard Wi-Fi P1 Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `homewizard` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx index 68fa9e9e09..feb94c6cd1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -1,6 +1,7 @@ --- title: Hoymiles HM & HMS Series (via AhoyDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-ahoydtu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname id: 0 # Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID], optional`} /> +## Templateparameter `hoymiles-ahoydtu` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #\[ID\]
`id` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx index 55f5fa2e6a..b542461b85 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -1,6 +1,7 @@ --- title: Hoymiles HM & HMS Series (via OpenDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-opendtu.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `hoymiles-opendtu` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx index afcb6cc18b..50f58ffee8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx @@ -1,6 +1,7 @@ --- title: Huawei EMMA custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-emma.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `huawei-emma` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx index a32874a53b..a44c2adab1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx @@ -1,6 +1,7 @@ --- title: Huawei SmartLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-smartlogger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -102,3 +103,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `huawei-smartlogger` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | nein | +| `storageunit` | | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx index 798459305d..52df54cff8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -1,6 +1,7 @@ --- title: Huawei SUN2000 (SDongle) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-dongle.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,10 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 port: 502 # Port timeout: 15s # Zeitüberschreitung, optional`} /> +## Templateparameter `huawei-dongle` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx index 408b6a32de..9a000c0e82 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx @@ -1,6 +1,7 @@ --- title: Huawei SUN2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-sun2000.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -187,3 +188,15 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 +## Templateparameter `huawei-sun2000` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | nein | +| `storageunit` | | Standard: `1` | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `10000`
Einheit: W | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Wechselrichterkaskade
`forceaccharging` | AC-Laden bleibt aktiv zum Laden des Speichers aus anderen AC Quellen für Wechselrichterkaskaden. Verhindert Stand-by. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx index cf6acab8cc..4a0b9f2147 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx @@ -1,6 +1,7 @@ --- title: IAMMETER WEM3080 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -50,3 +51,9 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering +## Templateparameter `iammeter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx new file mode 100644 index 0000000000..76189261f8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -0,0 +1,59 @@ +--- +title: IAMMETER WEM3080T/WEM3046T/WEM3050T +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# IAMMETER WEM3080T/WEM3046T/WEM3050T + + + +Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). +Siehe https://www.iammeter.com/newsshow/net-energy-metering + + + + + + + + + + + + + + + + + + + + +## Templateparameter `iammeter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx deleted file mode 100644 index a7cff11808..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080twem3046twem3050t.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: IAMMETER WEM3080T/WEM3046T/WEM3050T -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# IAMMETER WEM3080T/WEM3046T/WEM3050T - - - -Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). -Siehe https://www.iammeter.com/newsshow/net-energy-metering - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx index a69485b9e0..8982398efc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx @@ -1,6 +1,7 @@ --- title: IGEN Tech Solarman Logger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarman.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; user: admin # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: admin # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +## Templateparameter `solarman` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | Standard: `admin` | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | Standard: `admin` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx index df9953760e..8ef5ae3917 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx @@ -154,25 +154,58 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; /> + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx index e840f09dcb..29b38145b6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx @@ -1,6 +1,7 @@ --- title: inepro PRO380-MOD custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/inepro.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `inepro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx index 85f9888f1e..3ee0e284ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx @@ -1,6 +1,7 @@ --- title: IOmeter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iometer.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP deines IOmeter`} /> +## Templateparameter `iometer` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP deines IOmeter
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx deleted file mode 100644 index 9f18c74b02..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series-umg-series.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Janitza B series, UMG series -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Janitza B series, UMG series - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx new file mode 100644 index 0000000000..dd105c37af --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx @@ -0,0 +1,81 @@ +--- +title: Janitza B series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Janitza B series + + + + + + + + + + + + + + + + +## Templateparameter `janitza` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx new file mode 100644 index 0000000000..599fb7cf00 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx @@ -0,0 +1,81 @@ +--- +title: Janitza UMG series +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Janitza UMG series + + + + + + + + + + + + + + + + +## Templateparameter `janitza` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx index 95a5cde714..5bb16d766f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx @@ -1,6 +1,7 @@ --- title: KEBA KeContact E10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/keba-kecontact.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `keba-kecontact` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx index 364ceb991e..ff2b6b7443 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -1,6 +1,7 @@ --- title: Kostal Energy Meter C (KEM-C) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx index 5e3eaec0e7..2e9698b572 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -1,6 +1,7 @@ --- title: Kostal Energy Meter P (KEM-P) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx new file mode 100644 index 0000000000..426a8f0197 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx @@ -0,0 +1,45 @@ +--- +title: Kostal Piko BA +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko BA + + + + + + + + + + + + + + + + +## Templateparameter `kostal-piko-pv` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx index 73fc1da83d..9edddb84e0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx @@ -1,6 +1,7 @@ --- title: Kostal Piko Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `kostal-piko-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx index 8998deab6e..69a5ee26cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx @@ -1,6 +1,7 @@ --- title: Kostal Piko (legacy) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-legacy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen`} /> +## Templateparameter `kostal-piko-legacy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx index 690832a957..d2e8e0bec2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx @@ -1,6 +1,7 @@ --- title: Kostal Piko MP Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `kostal-piko-mp-plus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx deleted file mode 100644 index ec4a1eae3e..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-piko-ba.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Kostal Piko, Piko BA -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Kostal Piko, Piko BA - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx new file mode 100644 index 0000000000..8bf2671f6a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx @@ -0,0 +1,45 @@ +--- +title: Kostal Piko +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Kostal Piko + + + + + + + + + + + + + + + + +## Templateparameter `kostal-piko-pv` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx index 2f0d2b0510..907e19e0f1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -1,6 +1,7 @@ --- title: Kostal Plenticore Hybrid, inkl. Netzladung der Hausbatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore-gen2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -78,3 +79,14 @@ _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ +## Templateparameter `kostal-plenticore-gen2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Byte-Reihenfolge (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx index 0e6e2ecf1b..6dec8a6975 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -1,6 +1,7 @@ --- title: Kostal Plenticore Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -80,3 +81,15 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive B +## Templateparameter `kostal-plenticore` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Byte-Reihenfolge (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx index d5c5a801ae..188f64d939 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -1,6 +1,7 @@ --- title: Kostal Smart Energy Meter (über den Wechselrichter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,9 @@ Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorpos host: 192.0.2.2 # Hostname port: 1502 # Port`} /> +## Templateparameter `kostal-ksem-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx index ef381a7bf3..1760873255 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx @@ -1,6 +1,7 @@ --- title: Kostal Smart Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `kostal-ksem` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx index b8046a8c8b..8da937727a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx @@ -1,6 +1,7 @@ --- title: LG ESS Home 15 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-15.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -77,3 +78,14 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `lg-ess-home-15` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Passwort
`password` | Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. | | nein | +| `registration` | Registriernummer des LG ESS HOME Wechselrichters. | Beispiel: `DE200...` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx new file mode 100644 index 0000000000..b26e625dc5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx @@ -0,0 +1,94 @@ +--- +title: LG ESS Home 8/10 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# LG ESS Home 8/10 + + + +Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich 10.05.7433 / R2155 benötigt + + + + + + + + + + + + + + + + + + + + +## Templateparameter `lg-ess-home-8-10` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Passwort
`password` | Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. | | nein | +| `registration` | Registriernummer des LG ESS HOME Wechselrichters. | Beispiel: `DE200...` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx deleted file mode 100644 index cea57e9171..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-810.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: LG ESS Home 8/10 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# LG ESS Home 8/10 - - - -Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich 10.05.7433 / R2155 benötigt - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx index b4fd95746a..f18516d203 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx @@ -1,6 +1,7 @@ --- title: Loxone Miniserver custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/loxone.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `loxone` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| Zählerbaustein
`meterblock` | Bezeichnung aus Loxone Config | | ja | +| Bausteinbezeichnung für Ladezustand
`socblock` | Bezeichnung aus Loxone Config, nur für Batterie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx index c2f4545bf4..d3bde2e4c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -1,6 +1,7 @@ --- title: M-TEC Energy Butler GEN2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -82,3 +83,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `mtec-eb-gen2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx index f037642050..7312de16be 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -1,6 +1,7 @@ --- title: M-TEC Energy Butler GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `mtec-eb-gen3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx index e0b1ca7ebb..5f8d703592 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx @@ -1,6 +1,7 @@ --- title: Marstek Venus Battery Storage custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/marstek-venus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -55,3 +56,14 @@ import TabItem from '@theme/TabItem'; maxchargepower: 2500 # Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus. (W), Für erzwungenes Laden des Speichers. (optional) work_mode_normal: 1 # Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung., optional`} /> +## Templateparameter `marstek-venus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | Venus-E 5.12 kWh, Venus-C 2.56 kWh | Standard: `5.12`
Beispiel: `50`
Einheit: kWh | nein | +| Venus kann nur bis 11% entladen werden.
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `11`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `100`
Beispiel: `95`
Einheit: % | nein | +| Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus.
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `2500`
Einheit: W | nein | +| Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung.
`work_mode_normal` | | Standard: `1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx index d07d2f0749..448856a088 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx @@ -1,6 +1,7 @@ --- title: mhendriks P1 dongle custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle`} /> +## Templateparameter `slimmelezer` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Skalierungsfaktor
`scale` | Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle | Standard: `1000`
Beispiel: `1 \| 10 \| 100 \| 1000` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx index 3f702aa5a6..5914665c8d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -1,6 +1,7 @@ --- title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: aux host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `ac-elwa-2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx index f21341c735..b49367d38e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -1,6 +1,7 @@ --- title: my-PV AC ELWA-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: aux host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `ac-elwa-e` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx new file mode 100644 index 0000000000..ea142ec908 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx @@ -0,0 +1,29 @@ +--- +title: my-PV AC•THOR +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# my-PV AC•THOR + + + + + +## Templateparameter `thor` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx deleted file mode 100644 index 531a511c52..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-acthor.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: my-PV AC•THOR -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# my-PV AC•THOR - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx index 50b9dea362..c261c4829d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx @@ -1,6 +1,7 @@ --- title: my-PV WiFi Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mypv-wifi-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `mypv-wifi-meter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx index c5b5623342..6bab29de9e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx @@ -1,6 +1,7 @@ --- title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mystrom.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `mystrom` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx index 6a46df9297..21fbba4ffe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx @@ -1,6 +1,7 @@ --- title: OpenEMS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -71,3 +72,14 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries +## Templateparameter `openems` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | Standard: `user` | nein | +| `battery` | steuerbare Batterie Komponente | Beispiel: `ess0` | nein | +| `watchdog` | abgestimmt auf das API-Timeout | Standard: `60s` | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx deleted file mode 100644 index cd30c1d512..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516-or-we-517.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Orno OR-WE-516, OR-WE-517 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Orno OR-WE-516, OR-WE-517 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx new file mode 100644 index 0000000000..ab7df5806f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx @@ -0,0 +1,69 @@ +--- +title: ORNO OR-WE-516 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ORNO OR-WE-516 + + + + + + + + + + + + + + + + +## Templateparameter `orno` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx new file mode 100644 index 0000000000..6e84b66fb7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx @@ -0,0 +1,69 @@ +--- +title: ORNO OR-WE-517 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ORNO OR-WE-517 + + + + + + + + + + + + + + + + +## Templateparameter `orno` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx new file mode 100644 index 0000000000..0fb07dba23 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx @@ -0,0 +1,29 @@ +--- +title: P1Monitor P1 Monitor +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# P1Monitor P1 Monitor + + + + + +## Templateparameter `p1monitor` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx deleted file mode 100644 index a73fb7f77b..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: P1Monitor P1 Monitor -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# P1Monitor P1 Monitor - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx index 3b2413c086..9281593daa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx @@ -1,6 +1,7 @@ --- title: Plexlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/plexlog.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,10 @@ Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `int +## Templateparameter `plexlog` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx index 382ffb6127..07c6b92c4c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx @@ -1,6 +1,7 @@ --- title: Powerdog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerdog.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `powerdog` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx index bebe0d5074..8dfa05b19a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx @@ -1,6 +1,7 @@ --- title: Powerfox Poweropti custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerfox-poweropti.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `powerfox-poweropti` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| `id` | Id im Falle mehrerer PowerOpti | Standard: `main` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx index 87fd5561c9..fd6d9d5cc3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -1,6 +1,7 @@ --- -title: QCells Hybrid-Wechselrichter (Cloud) +title: Qcells Hybrid-Wechselrichter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/qcells-hybrid-cloud.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -9,11 +10,11 @@ import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# QCells Hybrid-Wechselrichter (Cloud) +# Qcells Hybrid-Wechselrichter (Cloud) -Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. +Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. @@ -26,7 +27,7 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. type: template template: qcells-hybrid-cloud usage: grid - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen.`} /> @@ -37,7 +38,7 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. type: template template: qcells-hybrid-cloud usage: pv - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen.`} /> @@ -48,16 +49,24 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen.`} advanced={`meters: - name: my_battery type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. capacity: 50 # Akkukapazität (kWh), optional`} /> +## Templateparameter `qcells-hybrid-cloud` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| QcellsCloud TokenID
`tokenid` | Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. | | ja | +| Seriennummer
`serial` | Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. | | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx new file mode 100644 index 0000000000..218be9eef9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -0,0 +1,195 @@ +--- +title: Qcells Q.HOME ESS HYB-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Qcells Q.HOME ESS HYB-G3 + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Der Wechselrichter hat einen dritten PV-Eingang (MPPT3)
`mppt3` | | | nein | +| `storageunit` | | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx deleted file mode 100644 index 0ef1ded469..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-qhome-ess-hyb-g3.mdx +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Qcells Q.HOME ESS HYB-G3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Qcells Q.HOME ESS HYB-G3 - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx index 6f0f3c6da4..ebad8223e1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx @@ -1,6 +1,7 @@ --- title: RCT Power custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/rct-power.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,15 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `rct-power` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `7`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `97`
Beispiel: `95`
Einheit: % | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `30s`
Beispiel: `5m` | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Einheit: W | nein | +| Externe Leistung
`externalpower` | Externe Leistung aller an S0 angeschlossenen Geräte abfragen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx deleted file mode 100644 index 99661015ef..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-ale3-awd3.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Saia-Burgess Controls ALE3, AWD3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Saia-Burgess Controls ALE3, AWD3 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx new file mode 100644 index 0000000000..6c5db4b11b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -0,0 +1,69 @@ +--- +title: Saia-Burgess Controls (SBC) ALE3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Saia-Burgess Controls (SBC) ALE3 + + + + + + + + + + + + + + + + +## Templateparameter `sbc-axx3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx new file mode 100644 index 0000000000..e13ce243f8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -0,0 +1,69 @@ +--- +title: Saia-Burgess Controls (SBC) AWD3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Saia-Burgess Controls (SBC) AWD3 + + + + + + + + + + + + + + + + +## Templateparameter `sbc-axx3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx index c5c45b2afb..38b02e8d0d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -1,6 +1,7 @@ --- title: SAJ H1 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h1.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -76,3 +77,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `saj-h1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Standard: `5s`
Beispiel: `10s` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx index 16b50ef9db..6be395639f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -1,6 +1,7 @@ --- title: SAJ H2 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `saj-h2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | Standard: `2` | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx index be836300ca..d0589dcfbe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -1,6 +1,7 @@ --- title: SAJ R5 Series Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-r5.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `saj-r5` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx index 4bc53dd146..515c5685d2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx @@ -1,6 +1,7 @@ --- title: SAX Homespeicher custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sax.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx index 437f552eae..dc70c798b9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -1,6 +1,7 @@ --- title: Schneider Electric iEM3xxx Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/schneider-iem3000.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `schneider-iem3000` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx index 303f104b4f..9d70c5a93a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx @@ -1,6 +1,7 @@ --- title: SENEC .Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senec-home.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -56,3 +57,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `senec-home` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| `schema` | | Standard: `https`
Auswahl: `https`, `http` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx new file mode 100644 index 0000000000..4e958de9ac --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx @@ -0,0 +1,34 @@ +--- +title: Senergy SE 4/5/6KTL-S1/G2 Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Senergy SE 4/5/6KTL-S1/G2 Inverter + + + + + +## Templateparameter `senergy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx deleted file mode 100644 index d26588fdbf..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-456ktl-s1g2-inverter.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Senergy SE 4/5/6KTL-S1/G2 Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Senergy SE 4/5/6KTL-S1/G2 Inverter - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx deleted file mode 100644 index 6f108dfc18..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-em-plug-s-pro-3em-in-monophase-mode.mdx +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx new file mode 100644 index 0000000000..1f4e226777 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly 1PM mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1PM mini + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx new file mode 100644 index 0000000000..0f5a7b8846 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly 1PM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly 1PM + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx index 7d50fa1040..cf9a37cbab 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx @@ -1,6 +1,7 @@ --- title: Shelly 3EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-3em.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -67,3 +68,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `shelly-3em` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx new file mode 100644 index 0000000000..601ff88a20 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly EM + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx new file mode 100644 index 0000000000..c865363933 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Plug S +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Plug S + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx new file mode 100644 index 0000000000..d53789a723 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly PM mini +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly PM mini + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx new file mode 100644 index 0000000000..bfb482e21b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Pro 1PM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 1PM + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx index 4a78238e50..98e5a246e9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx @@ -1,6 +1,7 @@ --- title: Shelly Pro 3 EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-pro-3em.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `shelly-pro-3em` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx new file mode 100644 index 0000000000..83c5e90985 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Pro 3EM (monophase mode) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro 3EM (monophase mode) + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx new file mode 100644 index 0000000000..c292c58fc5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx @@ -0,0 +1,67 @@ +--- +title: Shelly Pro EM +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Shelly Pro EM + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `shelly-1pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| `channel` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx index 40405f5fa0..ef2e6cc609 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx @@ -1,6 +1,7 @@ --- title: Siemens 7KT1665 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-7kt1665.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `siemens-7kt1665` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx index 81498bd6d3..d4b1e4d36c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -1,6 +1,7 @@ --- title: Siemens Junelight Smart Battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-junelight.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,10 @@ Die Batterie muss mit dem Installer Zugang auf Loxone gestellt werden. +## Templateparameter `siemens-junelight` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx index 71a4971d6d..dd9816c083 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx @@ -1,6 +1,7 @@ --- title: Siemens PAC 2200 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-pac2200.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `siemens-pac2200` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx new file mode 100644 index 0000000000..138a3901f5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx @@ -0,0 +1,75 @@ +--- +title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC + + + +Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen App aktivieren bevor diese Konfiguration funktional ist. Diese Option ist in der mySigen App für Kunden nicht verfügbar. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sigenergy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| `id` | | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx deleted file mode 100644 index d93f9e25db..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybridsigen-pv-maxsigenstore-ec.mdx +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC - - - -Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen App aktivieren bevor diese Konfiguration funktional ist. Diese Option ist in der mySigen App für Kunden nicht verfügbar. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx index 5da329a43c..689611e411 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx @@ -1,6 +1,7 @@ --- title: SMA Data Manager custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-data-manager.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -75,3 +76,10 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio +## Templateparameter `sma-data-manager` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx index ff473752d3..06e5c26c2f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx @@ -1,6 +1,7 @@ --- title: SMA Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-energy-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -48,3 +49,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sma-energy-meter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Netzwerkschnittstelle
`interface` | | Beispiel: `eth0` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx index d173dd90be..17f69efce1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx @@ -1,6 +1,7 @@ --- title: SMA Wechselrichter (Speedwire) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-speedwire.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -45,3 +46,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sma-inverter-speedwire` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Passwort
`password` | Passwort für Benutzergruppe Benutzer | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx index c132041f4f..407c7c1033 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: SMA Smart Energy Hybrid-Wechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -70,3 +71,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sma-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx new file mode 100644 index 0000000000..7579520b6e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx @@ -0,0 +1,50 @@ +--- +title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) + + + + + +## Templateparameter `sma-sbs-15-25-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx deleted file mode 100644 index f0c3c21c5a..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-152025-modbus.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx new file mode 100644 index 0000000000..6142465087 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx @@ -0,0 +1,50 @@ +--- +title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) + + + + + +## Templateparameter `sma-sbs-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx deleted file mode 100644 index fa094bea4d..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-375060-modbus.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx new file mode 100644 index 0000000000..872a6bc832 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -0,0 +1,36 @@ +--- +title: SMA Sunny Home Manager 2.0 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SMA Sunny Home Manager 2.0 + + + + + +## Templateparameter `sma-home-manager` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Netzwerkschnittstelle
`interface` | | Beispiel: `eth0` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx deleted file mode 100644 index 87b810e76a..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-20.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: SMA Sunny Home Manager 2.0 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SMA Sunny Home Manager 2.0 - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx index 0c5030c1dd..d16d3ed958 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx @@ -1,6 +1,7 @@ --- title: SMA Sunny Island (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-si-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,12 @@ import TabItem from '@theme/TabItem'; maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) watchdog: 60s # optional`} /> +## Templateparameter `sma-si-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx index f10b8ce114..650d2bb8e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx @@ -1,6 +1,7 @@ --- title: SMA WebBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-webbox.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `sma-webbox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx index ab7199b1f5..83fe9ca292 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -1,6 +1,7 @@ --- title: SMA Wechselrichter (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-modbus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `sma-inverter-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx deleted file mode 100644 index 6794312191..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box-reg-reg-extended.mdx +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Smartfox Box, Reg, Reg extended -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Smartfox Box, Reg, Reg extended - - - -`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx new file mode 100644 index 0000000000..fe1f9905b3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx @@ -0,0 +1,58 @@ +--- +title: Smartfox Box +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Box + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx new file mode 100644 index 0000000000..1ea191d0f6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Light (EM2 firmware) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Light (EM2 firmware) + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox-em2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx new file mode 100644 index 0000000000..dab21187f8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro 2 + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox-em2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx new file mode 100644 index 0000000000..a8586ef35d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro Light 2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro Light 2 + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox-em2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx new file mode 100644 index 0000000000..39fcb7537e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro Light +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro Light + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox-em2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx deleted file mode 100644 index fca340eac2..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-pro-2-pro-light-pro-light-2-light-em2-firmware.mdx +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Smartfox Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) - - - -`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx new file mode 100644 index 0000000000..0826070a21 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx @@ -0,0 +1,77 @@ +--- +title: Smartfox Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Pro + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox-em2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx new file mode 100644 index 0000000000..577063b99c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx @@ -0,0 +1,58 @@ +--- +title: Smartfox Reg extended +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Reg extended + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx new file mode 100644 index 0000000000..b9bd76498a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx @@ -0,0 +1,58 @@ +--- +title: Smartfox Reg +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smartfox Reg + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `smartfox` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx new file mode 100644 index 0000000000..b3ac87e4be --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: SofarSolar Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx new file mode 100644 index 0000000000..a3aea78fe6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar HYD 3…6K-EP +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 3…6K-EP + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx deleted file mode 100644 index b5712f315e..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-36k-ep.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar HYD 3…6K-EP -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar HYD 3…6K-EP - - - -Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx new file mode 100644 index 0000000000..5fa66ea3d3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar HYD 5…20K-3PH +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar HYD 5…20K-3PH + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx deleted file mode 100644 index ca0c1e2dc4..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-520k-3ph.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar HYD 5…20K-3PH -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar HYD 5…20K-3PH - - - -Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx deleted file mode 100644 index 65d48290d6..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter-hybrid-inverter.mdx +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: SofarSolar Inverter, Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar Inverter, Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx new file mode 100644 index 0000000000..f5fabc4a15 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: SofarSolar Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar Inverter + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx new file mode 100644 index 0000000000..8cab00a12d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar SOFAR 5…24KTL-G3 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 5…24KTL-G3 + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx deleted file mode 100644 index 45a3e6f954..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-524ktl-g3.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar SOFAR 5…24KTL-G3 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar SOFAR 5…24KTL-G3 - - - -Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx new file mode 100644 index 0000000000..04b3bf8aac --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -0,0 +1,191 @@ +--- +title: SofarSolar SOFAR 80…136KTL +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SofarSolar SOFAR 80…136KTL + + + +Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx deleted file mode 100644 index b1bf44d201..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80136ktl.mdx +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: SofarSolar SOFAR 80…136KTL -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SofarSolar SOFAR 80…136KTL - - - -Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx new file mode 100644 index 0000000000..025c1ca24f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -0,0 +1,76 @@ +--- +title: Solaranzeige Solaranzeige +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solaranzeige Solaranzeige + + + + + + + + + + + + + + + + +## Templateparameter `solaranzeige` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | IP Adresse oder der Hostname des MQTT Brokers | Beispiel: `192.0.2.2` | ja | +| Port
`port` | MQTT Broker Port | Standard: `1883` | nein | +| Topic
`topic` | Topic (ohne / am Anfang) | Standard: `solaranzeige/box1` | nein | +| Zeitüberschreitung
`timeout` | Akzeptiere keine Daten die älter sind als dieser Wert | Standard: `30s`
Beispiel: `10s` | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx deleted file mode 100644 index 4bf54bb1b6..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige.mdx +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Solaranzeige Solaranzeige -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Solaranzeige Solaranzeige - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx index c926501a36..9f42a4b631 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: SolarEdge Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -184,3 +185,13 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R +## Templateparameter `solaredge-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx index 860a5e8b12..4e987cd500 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx @@ -1,6 +1,7 @@ --- title: SolarEdge Wechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -77,3 +78,10 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! +## Templateparameter `solaredge-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx index a180ba1f0f..7adf835db9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx @@ -1,6 +1,7 @@ --- title: Solarlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarlog.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,10 @@ Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall f +## Templateparameter `solarlog` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx new file mode 100644 index 0000000000..588ef6e91d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -0,0 +1,111 @@ +--- +title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# SolarMax MAX.STORAGE / MAX.STORAGE Ultimate + + + +Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. + + + + + + + + + + + + + + + + + + + + +## Templateparameter `solarmax-maxstorage` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| `watchdog` | | Standard: `60s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx deleted file mode 100644 index e4d8cb4d73..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-maxstorage-maxstorage-ultimate.mdx +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# SolarMax MAX.STORAGE / MAX.STORAGE Ultimate - - - -Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx index 5b22bd5fb9..9925e6c81b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx @@ -1,6 +1,7 @@ --- title: SolarMax SolarMax SMT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-smt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `solarmax-smt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx index bf77b4110b..fa278807d1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -1,6 +1,7 @@ --- title: SolarMax SP Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -25,3 +26,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `senergy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx deleted file mode 100644 index 01c8912c14..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-energymanager-pro.mdx +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Solarwatt EnergyManager, EnergyManager Pro -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Solarwatt EnergyManager, EnergyManager Pro - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx new file mode 100644 index 0000000000..83c902c98f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -0,0 +1,62 @@ +--- +title: Solarwatt EnergyManager Pro +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt EnergyManager Pro + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `solarwatt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx new file mode 100644 index 0000000000..3bd165c6e8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx @@ -0,0 +1,62 @@ +--- +title: Solarwatt EnergyManager +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solarwatt EnergyManager + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `solarwatt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx index f9a2a4844d..b7851ccb1f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx @@ -1,6 +1,7 @@ --- title: Solarwatt Manager flex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-flex.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -55,3 +56,10 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. +## Templateparameter `solarwatt-flex` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx index c54cb6fe69..d465eaf3c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -1,6 +1,7 @@ --- title: Solarwatt MyReserve Matrix (LAN oder PowerGateway) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-myreserve-matrix.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -56,3 +57,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `solarwatt-myreserve-matrix` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `8080` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx index 97ecf2a87b..b754c95e7f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx @@ -1,6 +1,7 @@ --- title: Solarwatt MyReserve custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -52,3 +53,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `solarwatt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx index 65ec328cde..d0cf64650f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -1,6 +1,7 @@ --- title: Solax Hybrid-Wechselrichter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-hybrid-cloud.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -61,3 +62,11 @@ Der Solax Hybrid-Wechselrichter muss in der SolaxCloud angemeldet sein. +## Templateparameter `solax-hybrid-cloud` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') | | ja | +| Seriennummer
`serial` | https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen | | ja | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx new file mode 100644 index 0000000000..eb1332ca1c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -0,0 +1,195 @@ +--- +title: Solax Hybrid X1/X3 G3/G4 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Solax Hybrid X1/X3 G3/G4 + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Der Wechselrichter hat einen dritten PV-Eingang (MPPT3)
`mppt3` | | | nein | +| `storageunit` | | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx deleted file mode 100644 index 82b743b6a6..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1x3-g3g4.mdx +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Solax Hybrid X1/X3 G3/G4 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Solax Hybrid X1/X3 G3/G4 - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx index 77896cf6d9..b6818e123d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx @@ -1,6 +1,7 @@ --- title: Solax PV-Wechselrichter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-inverter-cloud.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,10 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von \`tokenID\` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen`} /> +## Templateparameter `solax-inverter-cloud` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') | | ja | +| Seriennummer
`serial` | https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx index fcdc8fd750..e15f993450 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx @@ -1,6 +1,7 @@ --- title: Solinteng custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `delay` | | Standard: `100ms` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx deleted file mode 100644 index 6e3436ba14..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort-eco-5-eco-6-oem-65.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Sonnen comfort, eco 5, eco 6, oem 6.5 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Sonnen comfort, eco 5, eco 6, oem 6.5 - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx new file mode 100644 index 0000000000..a8cb1b6c8d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen comfort +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen comfort + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sonnenbatterie-eco56` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `7979` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Einheit: W | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `5s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx new file mode 100644 index 0000000000..3aaa3df3ac --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen eco 5 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen eco 5 + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sonnenbatterie-eco56` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `7979` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Einheit: W | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `5s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx new file mode 100644 index 0000000000..cdf2d7dda0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen eco 6 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen eco 6 + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sonnenbatterie-eco56` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `7979` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Einheit: W | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `5s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx new file mode 100644 index 0000000000..45bd8ad524 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx @@ -0,0 +1,85 @@ +--- +title: Sonnen oem 6.5 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Sonnen oem 6.5 + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sonnenbatterie-eco56` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `7979` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Einheit: W | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `5s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx index 1f1454befc..8c84c7f77e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -1,6 +1,7 @@ --- title: Sonnen sonnenBatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -65,3 +66,14 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat +## Templateparameter `sonnenbatterie` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `8080` | nein | +| `token` | API Token (benötigt für aktive Batteriesteuerung) | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `3300`
Einheit: W | nein | +| Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | Standard: `self-consumption`
Auswahl: `self-consumption`, `time-of-use` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx index e8434ed24c..7af099bab7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx @@ -1,6 +1,7 @@ --- title: St-ems custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `delay` | | Standard: `100ms` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx index 5f2ad9ba3c..834855417c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx @@ -1,6 +1,7 @@ --- title: Steca coolcept fleX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `kostal-piko-mp-plus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx index b0fe41ad46..5405e437db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sungrow SG Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sungrow-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx index e47aa97360..c0a217f352 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sungrow SH Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -157,3 +158,13 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu +## Templateparameter `sungrow-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Maximale Ladeleistung
`maxchargepower` | Maximale Ladeleistung für erzwungenes Laden des Speichers in Watt. (0 um automatisch den Wert der maximalen BDC-Nennleistung einzustellen) | Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx index 2131e8b38d..d0ade717b0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Batterie (Model 124) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter-control.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -63,3 +64,11 @@ import TabItem from '@theme/TabItem'; maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> +## Templateparameter `sunspec-inverter-control` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx index 3708ffc938..2f5275665e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Batterie (Model 802) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-battery-control.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -64,3 +65,12 @@ import TabItem from '@theme/TabItem'; minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> +## Templateparameter `sunspec-battery-control` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx index facaac4383..e4edb7b0e0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Hybridwechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-hybrid.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -148,3 +149,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sunspec-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx index 7fd09bc67f..28a0118eae 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Wechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sunspec-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx index 03f3917388..617a7db682 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx @@ -1,6 +1,7 @@ --- title: SunSpec Zähler custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -46,3 +47,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `sunspec-meter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx index 5cc53ba7d8..1f3c51b006 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -177,3 +178,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `deye-hybrid-3p` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx index 218bfe23ac..0064b68c9a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -183,3 +184,15 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `deye-hybrid-hp3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| `storageunit` | | Standard: `1` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| GEN-Anschluss als Solar-Eingang verwenden
`includegenport` | | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx index dde97fc54c..0897fee320 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `deye-mi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx index cafe274f8e..353815961b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -124,3 +125,10 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `deye-storage` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx index ed155ffd63..d39bedf162 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx @@ -1,6 +1,7 @@ --- title: Sunsynk String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,9 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port`} /> +## Templateparameter `deye-string` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx index f36a39bc06..3703c569fa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx @@ -1,6 +1,7 @@ --- title: Sunway custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `delay` | | Standard: `100ms` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx new file mode 100644 index 0000000000..00540e6c47 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx @@ -0,0 +1,100 @@ +--- +title: Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi + + + +Um die Werte des Smartmeters für evcc korrekt auslesen zu können, muss das Lesekopf-Script so geändert werden, dass folgende JSON-Tags erzeugt werden: +- **SML** als Gruppenname der ausgelesenen Parameter +- **Total_in** für den Gesamtverbrauch in KWh (4 Nachkommastellen) +- **Total_out** für den Gesamteinspeisung in KWh mit (4 Nachkommastellen) +- **Power_curr** für den aktuellen Verbrauch bzw. die aktuelle Einspeisung (0 Nachkommastellen) + +Ein entsprechendes Lesekopf-Script sieht wie folgt aus: +``` +>D +>B +=>sensor53 r +>M 1 +// highlight-next-line ++1,3,s,16,9600,SML +// highlight-next-line +1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 +// highlight-next-line +1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 +// highlight-next-line +1,77070100100700ff@1,Verbrauch,W,Power_curr,0 +1,77070100600100ff@#,Zählernummer,,Meter_Id,0 +# +``` + + + + + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `tasmota-sml` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | Standard-User ist admin | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx deleted file mode 100644 index d9898bfb62..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-eg-hichi.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi - - - -Um die Werte des Smartmeters für evcc korrekt auslesen zu können, muss das Lesekopf-Script so geändert werden, dass folgende JSON-Tags erzeugt werden: -- **SML** als Gruppenname der ausgelesenen Parameter -- **Total_in** für den Gesamtverbrauch in KWh (4 Nachkommastellen) -- **Total_out** für den Gesamteinspeisung in KWh mit (4 Nachkommastellen) -- **Power_curr** für den aktuellen Verbrauch bzw. die aktuelle Einspeisung (0 Nachkommastellen) - -Ein entsprechendes Lesekopf-Script sieht wie folgt aus: -``` ->D ->B -=>sensor53 r ->M 1 -// highlight-next-line -+1,3,s,16,9600,SML -// highlight-next-line -1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 -// highlight-next-line -1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 -// highlight-next-line -1,77070100100700ff@1,Verbrauch,W,Power_curr,0 -1,77070100600100ff@#,Zählernummer,,Meter_Id,0 -# -``` - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx new file mode 100644 index 0000000000..5714ecfe43 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -0,0 +1,80 @@ +--- +title: Tasmota Tasmota (1 Phase + SML Meter) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Tasmota Tasmota (1 Phase + SML Meter) + + + + + + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `tasmota` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | Standard-User ist admin | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | +| Kanal Nummer
`channel` | Meterkanal (1-8) | Standard: `1` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx deleted file mode 100644 index 7b088d254f..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-sml-meter.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Tasmota Tasmota (1 Phase + SML Meter) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Tasmota Tasmota (1 Phase + SML Meter) - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx index f065aee823..53bb807793 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx @@ -1,6 +1,7 @@ --- title: Tasmota dreiphasig custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-3p.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -67,3 +68,11 @@ Kanäle 1,2,3 müssen verwendet werden. +## Templateparameter `tasmota-3p` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | Standard-User ist admin | | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx index cf620e755f..5a4b45aa90 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx @@ -1,6 +1,7 @@ --- title: Tesla Powerwall custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tesla-powerwall.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -93,3 +94,14 @@ Folgende Apps ermöglichen das Erstellen des Tokens: +## Templateparameter `tesla-powerwall` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Passwort
`password` | Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. | | ja | +| `refreshToken` | | | nein | +| `siteId` | optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung | | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx index 774b3942f6..d4519fd468 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx @@ -1,6 +1,7 @@ --- title: Tibber Pulse custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tibber-pulse.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,10 @@ import TabItem from '@theme/TabItem'; token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional`} /> +## Templateparameter `tibber-pulse` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | | Beispiel: `5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE` | ja | +| `homeid` | | Beispiel: `96a14971-525a-4420-aae9-e5aedaa129ff` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx index d20a6eae89..6780ebbc6a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tplink.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -20,3 +21,9 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +## Templateparameter `tplink` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx index a91e2b8476..6e4862ceba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -1,6 +1,7 @@ --- title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tapo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen`} /> +## Templateparameter `tapo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx new file mode 100644 index 0000000000..84bd29f912 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -0,0 +1,33 @@ +--- +title: TQ Energy Manager EM2xx/EM3xx +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# TQ Energy Manager EM2xx/EM3xx + + + + + +## Templateparameter `tq-em` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `80` | nein | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx deleted file mode 100644 index b5e62d115a..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xxem3xx.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: TQ Energy Manager EM2xx/EM3xx -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# TQ Energy Manager EM2xx/EM3xx - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx index 4e93f55530..5514b8ad45 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx @@ -1,6 +1,7 @@ --- title: TQ Energy Manager EM420 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em420.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,12 @@ import TabItem from '@theme/TabItem'; device: local # API Gerätepfad, JSON-Schnittstelle -> Datenendpunkt (optional) token: ey... # Accesstoken, Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel)`} /> +## Templateparameter `tq-em420` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `80` | nein | +| API Gerätepfad
`device` | JSON-Schnittstelle -> Datenendpunkt | Standard: `local` | nein | +| Accesstoken
`token` | Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel) | Beispiel: `ey...` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx new file mode 100644 index 0000000000..b0a7b15254 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx @@ -0,0 +1,70 @@ +--- +title: VARTA element +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA element + + + +PV nur verfügbar mit PV-Sensor + + + + + + + + + + + + + + + + + + + + +## Templateparameter `varta` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx new file mode 100644 index 0000000000..6af1eb6ec3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx @@ -0,0 +1,70 @@ +--- +title: VARTA pulse neo +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA pulse neo + + + +PV nur verfügbar mit PV-Sensor + + + + + + + + + + + + + + + + + + + + +## Templateparameter `varta` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx deleted file mode 100644 index d0f77af2e2..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-pulse-neo-element.mdx +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: VARTA pulse, pulse neo, element -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# VARTA pulse, pulse neo, element - - - -PV nur verfügbar mit PV-Sensor - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx new file mode 100644 index 0000000000..0ef29d3fa8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx @@ -0,0 +1,70 @@ +--- +title: VARTA pulse +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# VARTA pulse + + + +PV nur verfügbar mit PV-Sensor + + + + + + + + + + + + + + + + + + + + +## Templateparameter `varta` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx index 042805c7fa..d3634052c0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx @@ -1,6 +1,7 @@ --- title: Victron EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -63,3 +64,9 @@ EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschl +## Templateparameter `cg-em24` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx new file mode 100644 index 0000000000..54399affd7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx @@ -0,0 +1,59 @@ +--- +title: Victron EM24_E1 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM24_E1 + + + +EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. +Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + + + + + + + + + + + + + + + +## Templateparameter `cg-em24_e1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx deleted file mode 100644 index 282944c248..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24e1.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Victron EM24_E1 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Victron EM24_E1 - - - -EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. -Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx new file mode 100644 index 0000000000..7c8152b5ee --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx @@ -0,0 +1,81 @@ +--- +title: Victron EM530/EM540 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Victron EM530/EM540 + + + + + + + + + + + + + + + + +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx deleted file mode 100644 index 9925778553..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530em540.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Victron EM530/EM540 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Victron EM530/EM540 - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx index af1ac6abff..07cdfda647 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx @@ -1,6 +1,7 @@ --- title: Victron Energy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/victron-energy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -80,3 +81,15 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer +## Templateparameter `victron-energy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | nein | +| `meterid` | Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | +| Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | +| Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx index 84e7a9a10d..63d9220ac6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx @@ -1,6 +1,7 @@ --- title: Victron ET340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -72,3 +73,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx index 64b046306d..df34db790a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -1,6 +1,7 @@ --- title: Volkszähler HTTP API, Import & Export custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-importexport.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; importuuid: exportuuid:`} /> +## Templateparameter `volkszaehler-importexport` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| URL des "data" Kontexts der Volkszähler Middleware
`url` | Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data | | nein | +| `importuuid` | | | ja | +| `exportuuid` | | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx index 0cd45c7f81..f89c920713 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx @@ -1,6 +1,7 @@ --- title: Volkszähler HTTP API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-http.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,10 @@ import TabItem from '@theme/TabItem'; url: # URL des "data" Kontexts der Volkszähler Middleware, Beispiel: http://zaehler.network.local:8080/api/data (optional) uuid:`} /> +## Templateparameter `volkszaehler-http` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| URL des "data" Kontexts der Volkszähler Middleware
`url` | Beispiel: http://zaehler.network.local:8080/api/data | | nein | +| `uuid` | | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx index 4211ea8be5..93e7249a46 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx @@ -1,6 +1,7 @@ --- title: Volkszähler WebSocket API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-ws.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,11 @@ import TabItem from '@theme/TabItem'; port: 8082 # Port, optional uuid:`} /> +## Templateparameter `volkszaehler-ws` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `8082` | nein | +| `uuid` | | | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx index 5217bbacea..4d82eec231 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx @@ -1,6 +1,7 @@ --- title: vzlogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/vzlogger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,3 +41,22 @@ import TabItem from '@theme/TabItem'; l3voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0), optional cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `vzlogger` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `8081` | nein | +| `uuid` | | | ja | +| Skalierungsfaktor
`scale` | Multipliziere Rohwert mit diesem Faktor | Standard: `1` | nein | +| Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0)
`l1currentuuid` | | | nein | +| Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0)
`l2currentuuid` | | | nein | +| Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0)
`l3currentuuid` | | | nein | +| Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0)
`l1poweruuid` | | | nein | +| Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0)
`l2poweruuid` | | | nein | +| Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0)
`l3poweruuid` | | | nein | +| Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0)
`l1voltageuuid` | | | nein | +| Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0)
`l2voltageuuid` | | | nein | +| Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0)
`l3voltageuuid` | | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx index 3d07cd7c87..1d4a6be57b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx @@ -1,6 +1,7 @@ --- title: Wago 879-30xx custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wago-879-30xx.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `wago-879-30xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx index 6c38588e47..b9af12f013 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx @@ -1,6 +1,7 @@ --- title: Wattsonic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -137,3 +138,11 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `delay` | | Standard: `100ms` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx index d61d11c12a..f37ea26704 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM110-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron-sdm220_230` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx index 98f2b79f3d..d09251e953 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM111-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron-sdm220_230` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx index 8b70536e33..21cea49bd6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM120-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx index fb072ac6d6..f4e0ade113 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -1,6 +1,7 @@ --- title: Weidmüller EM122-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -60,3 +61,9 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx index afec18634c..16d17dde07 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx @@ -1,6 +1,7 @@ --- title: Youless Energy Monitor custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/youless.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,9 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh +## Templateparameter `youless` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx new file mode 100644 index 0000000000..7f22c74c94 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: ZCS Azzurro Hybrid Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZCS Azzurro Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx deleted file mode 100644 index e9842c465b..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter-hybrid-inverter.mdx +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: ZCS Azzurro Inverter, Hybrid Inverter -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ZCS Azzurro Inverter, Hybrid Inverter - - - - - - - - - - - - - - - - - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx new file mode 100644 index 0000000000..4a7bd8edea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx @@ -0,0 +1,134 @@ +--- +title: ZCS Azzurro Inverter +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# ZCS Azzurro Inverter + + + + + + + + + + + + + + + + + + + + + +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx index 6a9bdd72b2..a22e1112fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx @@ -1,6 +1,7 @@ --- title: Zendure Hyper 2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/zendure.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -51,3 +52,13 @@ import TabItem from '@theme/TabItem'; +## Templateparameter `zendure` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `account` | | Beispiel: `dev@zendure.com` | ja | +| `serial` | Zu finden in der Zendure App in den Einstellungen des Geräts | Beispiel: `VU5D99F74021B04` | ja | +| `region` | | Standard: `EU`
Auswahl: `EU`, `Global` | ja | +| Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | +| Akkukapazität
`capacity` | | Standard: `2`
Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx deleted file mode 100644 index 1253494f87..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-in-luxembourg.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Zuidwijk SlimmeLezer(+) in Luxembourg -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Zuidwijk SlimmeLezer(+) in Luxembourg - - - -Slimmelezer-Geräte in Luxemburg verwenden für verschiedene Sensoren andere Namen. - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx new file mode 100644 index 0000000000..88eb90fd75 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -0,0 +1,32 @@ +--- +title: Zuidwijk SlimmeLezer(+) in Luxembourg +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) in Luxembourg + + + +Slimmelezer-Geräte in Luxemburg verwenden für verschiedene Sensoren andere Namen. + + + + +## Templateparameter `slimmelezer-luxembourg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx new file mode 100644 index 0000000000..9726ef6664 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -0,0 +1,32 @@ +--- +title: Zuidwijk SlimmeLezer(+) V2 +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) V2 + + + +Neuere Slimmelezer-Geräte verwenden eine andere Konfiguration. Probieren Sie diese Vorlage aus, wenn die andere fehlschlägt. + + + + +## Templateparameter `slimmelezer-V2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx new file mode 100644 index 0000000000..8ebef4e269 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -0,0 +1,36 @@ +--- +title: Zuidwijk SlimmeLezer(+) +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Zuidwijk SlimmeLezer(+) + + + + + +## Templateparameter `slimmelezer` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Skalierungsfaktor
`scale` | Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle | Standard: `1000`
Beispiel: `1 \| 10 \| 100 \| 1000` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx deleted file mode 100644 index 3283aa9029..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-v2.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Zuidwijk SlimmeLezer(+) V2 -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Zuidwijk SlimmeLezer(+) V2 - - - -Neuere Slimmelezer-Geräte verwenden eine andere Konfiguration. Probieren Sie diese Vorlage aus, wenn die andere fehlschlägt. - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx deleted file mode 100644 index 4853ca8019..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Zuidwijk SlimmeLezer(+) -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Zuidwijk SlimmeLezer(+) - - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx index 7e88f4df11..6c98728d56 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx @@ -1,6 +1,7 @@ --- title: Amber Electric custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/amber.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,14 @@ import TabItem from '@theme/TabItem'; tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `amber` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | | | nein | +| `siteid` | | | nein | +| `channel` | | | nein | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx index 7b4a539415..d20e527ff7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx @@ -1,6 +1,7 @@ --- title: Awattar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/awattar.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,12 @@ import TabItem from '@theme/TabItem'; tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `awattar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `region` | | Beispiel: `AT`
Auswahl: `DE`, `AT` | ja | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx index 27bdb1ac24..1613d62671 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -1,6 +1,7 @@ --- title: Electricity Maps Commercial API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps token: zone: DE # siehe https://api.electricitymap.org/v3/zones`} /> +## Templateparameter `electricitymaps` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| URI
`uri` | HTTP(S) Adresse | Beispiel: `https://api-access.electricitymaps.com/2w...1g/` | ja | +| `token` | | | ja | +| `zone` | siehe https://api.electricitymap.org/v3/zones | Beispiel: `DE` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx index b2d534c2f3..3cd687d904 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx @@ -1,6 +1,7 @@ --- title: Electricity Maps Free API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps-free.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps token: zone: DE # siehe https://api.electricitymap.org/v3/zones`} /> +## Templateparameter `electricitymaps-free` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | | | ja | +| `zone` | siehe https://api.electricitymap.org/v3/zones | Beispiel: `DE` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx index 4a4549035f..d9a7b61bd2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx @@ -1,6 +1,7 @@ --- title: Energinet custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energinet.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -26,3 +27,12 @@ import TabItem from '@theme/TabItem'; tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `energinet` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `region` | | Beispiel: `dk1`
Auswahl: `dk1`, `dk2` | ja | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx index 792500844f..ff1f9e0040 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx @@ -1,6 +1,7 @@ --- title: Enever custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/enever.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,14 @@ import TabItem from '@theme/TabItem'; formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) interval: 3h # optional`} /> +## Templateparameter `enever` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | | | ja | +| `provider` | | Auswahl: ``, `AA`, `AIP`, `ANWB`, `BE`
, `EE`, `EN`, `EVO`, `EZ`, `FR`
, `GSL`, `MDE`, `NE`, `PE`, `TI`
, `VDB`, `VON`, `WE`, `ZG`, `ZP`
| ja | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | +| `interval` | | Standard: `3h` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx index f4ea380c15..ccc14d8de9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx @@ -1,6 +1,7 @@ --- title: ENTSO-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/entsoe.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -32,3 +33,13 @@ Basis für viele dynamische Tarife. tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `entsoe` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `securitytoken` | Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation | | nein | +| `domain` | siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas | Beispiel: `BZN\|DE-LU` | nein | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx new file mode 100644 index 0000000000..75ad5056a0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx @@ -0,0 +1,53 @@ +--- +title: Forecast.Solar +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Forecast.Solar + + + +[forecast.solar](https://forecast.solar) kann kostenlos verwendet werden. Kostenpflichtige Pläne können ebenfalls verwendet werden, indem ein API-Key angegeben wird. + + + + +## Templateparameter `forecast-solar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Breitengrad
`lat` | | Beispiel: `55.7351` | ja | +| Längengrad
`lon` | | Beispiel: `9.1275` | ja | +| Neigung
`dec` | 0 = horizontal, 90 = vertikal | Beispiel: `25` | ja | +| Maximale Generatorleistung
`kwp` | | Beispiel: `9.8`
Einheit: kWp | ja | +| Azimut
`az` | -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden | Beispiel: `180` | ja | +| Horizont
`horizon` | Simuliert Verschattung durch Gelände, \[mehr Informationen\](https://doc.forecast.solar/horizon) | Beispiel: `0,0,15,30,45,60,60,60,45,30,15,0` | nein | +| API-Key
`apikey` | | | nein | +| `interval` | | Standard: `1h` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx deleted file mode 100644 index 17cbf205ee..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecastsolar.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Forecast.Solar -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Forecast.Solar - - - -[forecast.solar](https://forecast.solar) kann kostenlos verwendet werden. Kostenpflichtige Pläne können ebenfalls verwendet werden, indem ein API-Key angegeben wird. - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx index 7110afd6d0..4c4c14abf9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx @@ -1,6 +1,7 @@ --- title: Fraunhofer ISE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energy-charts-api.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,12 @@ Day-ahead Energiepreise (je kWh) an der Börse. Kann ohne vorherige Anmeldung au tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `energy-charts-api` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `bzn` | Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get | Standard: `DE-LU`
Auswahl: `AT`, `BE`, `CH`, `CZ`, `DE-LU`
, `DE-AT-LU`, `DK1`, `DK2`, `FR`, `HU`
, `IT-NORTH`, `NL`, `NO2`, `PL`, `SE4`
, `SI` | ja | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx index 990de751dc..6435bc387b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx @@ -1,6 +1,7 @@ --- title: Green Grid Compass custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/green-grid-compass.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ Europäische CO₂-Intensitätsdaten von [greengrid-compass.eu](https://www.gree apiKey: # API-Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key zone: DE_LU # Zonencode, [BE, DE_LU]`} /> +## Templateparameter `green-grid-compass` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| API-Key
`apiKey` | Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key | | ja | +| Zonencode
`zone` | | Standard: `DE_LU`
Auswahl: `BE`, `DE_LU` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx index 1dc0ce5f31..9ad6dc8c2a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -1,6 +1,7 @@ --- title: Groupe E Vario Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/groupe-e.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ import TabItem from '@theme/TabItem'; tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `groupe-e` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx index ec18edccca..b9bef4a18f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx @@ -1,6 +1,7 @@ --- title: Grünstromindex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/grünstromindex.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ Regionale Emissionsdaten von https://gruenstromindex.de zip: token: # Token für den Zugriff auf die API von https://console.corrently.io/ (optional)`} /> +## Templateparameter `grünstromindex` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `zip` | | | ja | +| `token` | Token für den Zugriff auf die API von https://console.corrently.io/ | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx index 144d49f855..a9f34dab47 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx @@ -89,13 +89,13 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; +## Templateparameter `ngeso` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `region` | Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list | Beispiel: `1` | nein | +| `postalcode` | Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. | Beispiel: `SW1` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx index 2f06490646..e77b043369 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx @@ -1,6 +1,7 @@ --- title: Nordpool spot prices custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/nordpool.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,13 @@ Nordpool Spot Preise im Day-Ahead-Markt für alle Märkte in der Nordpool-Region tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `nordpool` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `region` | | Beispiel: `GER`
Auswahl: `EE`, `LT`, `LV`, `AT`, `BE`
, `FR`, `GER`, `NL`, `PL`, `DK1`
, `DK2`, `FI`, `NO1`, `NO2`, `NO3`
, `NO4`, `NO5`, `SE1`, `SE2`, `SE3`
, `SE4`, `TEL`, `SYS` | nein | +| `currency` | | Standard: `EUR`
Auswahl: `DKK`, `EUR`, `NOK`, `PLN`, `RON`, `SEK` | ja | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx index 0afe2b0f9e..29d5d5fb3d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx @@ -1,6 +1,7 @@ --- title: Octopus Energy API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-api.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -23,3 +24,10 @@ Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/a apiKey: # Octopus Energy API Key. accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional)`} /> +## Templateparameter `octopus-api` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `apiKey` | Octopus Energy API Key. | | ja | +| `accountNumber` | Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx index 79b9cbd31e..f51c5b874e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx @@ -1,6 +1,7 @@ --- title: Octopus Energy Product Code custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-productcode.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -21,3 +22,11 @@ import TabItem from '@theme/TabItem'; region: # Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] directDebit: true # Ich benutze den BACS-Lastschrifttarif. (optional)`} /> +## Templateparameter `octopus-productcode` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `productCode` | Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. | Beispiel: `AGILE-FLEX-22-11-25` | ja | +| `region` | Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ | Auswahl: `A`, `B`, `C`, `D`, `E`
, `F`, `G`, `H`, `J`, `K`
, `L`, `M`, `N`, `P` | ja | +| `directDebit` | Ich benutze den BACS-Lastschrifttarif. | Standard: `true` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx index dc78dcb7b6..4249e155a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx @@ -1,6 +1,7 @@ --- title: Open-Meteo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/open-meteo.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -41,3 +42,20 @@ Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Op rossmodel: 0.0342 # Kühlung [Ross-Modell], Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) interval: 1h # optional`} /> +## Templateparameter `open-meteo` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Breitengrad
`lat` | | Beispiel: `55.7351` | ja | +| Längengrad
`lon` | | Beispiel: `9.1275` | ja | +| Neigung
`dec` | 0 = horizontal, 90 = vertikal | Beispiel: `25` | ja | +| Maximale Generatorleistung
`kwp` | | Beispiel: `9.8`
Einheit: kWp | ja | +| Azimut
`az` | -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden | | ja | +| AC Leistung \[kW\]
`ac` | | Standard: `1000` | nein | +| Dämpfung morgens \[%\]
`dm` | | | nein | +| Dämpfung abends \[%\]
`de` | | | nein | +| Wirkungsgrad \[%\]
`efficiency` | | Standard: `100` | nein | +| Temperaturkoeffizient
`alphatemp` | | Standard: `-0.004` | nein | +| Kühlung \[Ross-Modell\]
`rossmodel` | Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) \[Paper\](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) | Standard: `0.0342` | nein | +| `interval` | | Standard: `1h` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx index f7119fd630..0ec4d183f8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx @@ -1,6 +1,7 @@ --- title: Ostrom custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ostrom.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ Erzeuge einen 'Production Client' im Ostrom-Entwicklerportal: https://developer. clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a contract: 100523456 # Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional)`} /> +## Templateparameter `ostrom` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `clientid` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | ja | +| `clientsecret` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a` | ja | +| `contract` | Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren | Beispiel: `100523456` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx index 1b8bb51c4c..67afbd0fd5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx @@ -1,6 +1,7 @@ --- title: PUN Orario custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/pun.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -27,3 +28,11 @@ Preisdaten von https://www.mercatoelettrico.org/it/. Wird oft zur Einspeisung in tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `pun` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx index 8823e718c7..8c9447a16f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -1,6 +1,7 @@ --- title: SmartEnergy smartCONTROL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/smartenergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -24,3 +25,11 @@ import TabItem from '@theme/TabItem'; tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `smartenergy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx index 93949ecbd9..01d7f22952 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx @@ -1,6 +1,7 @@ --- title: Solcast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/solcast.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,13 @@ Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting to: # Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) interval: 3h # optional`} /> +## Templateparameter `solcast` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `site` | Ressource ID deiner Anlage | | ja | +| `token` | Solcast API Token | | ja | +| `from` | Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" | | nein | +| `to` | Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" | | nein | +| `interval` | | Standard: `3h` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx index 3d52452ae9..cd8054a1b7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx @@ -1,6 +1,7 @@ --- title: Spotty Energie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/spottyenergy.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -28,3 +29,13 @@ import TabItem from '@theme/TabItem'; tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `spottyenergy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `contractid` | Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ | Beispiel: `ffffffff-4444-6666-2222-aaaaaabbbbbb` | ja | +| `pricetype` | Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren | Standard: `CONSUMPTION`
Auswahl: `MARKET`, `CONSUMPTION`, `GENERATION` | ja | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx index 54c739edc7..36a8ce1a67 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx @@ -1,6 +1,7 @@ --- title: Tibber custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/tibber.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -31,3 +32,13 @@ Hol dir deinen API-Token aus dem Tibber-Entwicklerportal: https://developer.tibb tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +## Templateparameter `tibber` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `token` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | ja | +| `homeid` | Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. | Beispiel: `cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c` | nein | +| Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | +| Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | +| Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx index de5c656730..50ffc55e70 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -1,6 +1,7 @@ --- title: Victron VRM Solar Forecast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/victron.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -29,3 +30,11 @@ import TabItem from '@theme/TabItem'; token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen interval: 1h # optional`} /> +## Templateparameter `victron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| VRM-Installations-ID der Installation
`idsite` | Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt | Beispiel: `123456` | ja | +| API Zugriffstoken
`token` | Token können im VRM erstellt werden unter Präferenzen->Integrationen | | ja | +| `interval` | | Standard: `1h` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx index 320fc0b208..28a77fd586 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx @@ -1,6 +1,7 @@ --- title: Aiways custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/aiways.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `aiways` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx index 6237540664..bb7aed0ffb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx @@ -1,6 +1,7 @@ --- title: Audi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/audi.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `audi` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WAUZZZ...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx index d6323455b9..2e392a73ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx @@ -1,6 +1,7 @@ --- title: BMW custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/bmw.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,6 +43,28 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) region: EU # Region, [EU, NA] - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `bmw` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WBMW...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `hcaptcha` | | | ja | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `NA` | ja | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx index 5764bf8694..d71318d3b9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx @@ -1,6 +1,7 @@ --- title: Citroën custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/citroen.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `citroen` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| `accessToken` | | | ja | +| `refreshToken` | | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx index c7f265ebdc..2db9881835 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx @@ -1,6 +1,7 @@ --- title: Dacia custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/dacia.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,6 +37,26 @@ import TabItem from '@theme/TabItem'; identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `dacia` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx index f2571aff6f..1824af68f2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx @@ -1,6 +1,7 @@ --- title: DS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ds.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `ds` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| `accessToken` | | | ja | +| `refreshToken` | | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx index 73daebe9c0..ffc1087f81 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx @@ -1,6 +1,7 @@ --- title: evNotify custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/evnotify.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -34,3 +35,19 @@ import TabItem from '@theme/TabItem'; identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `evnotify` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `akey` | | | ja | +| `token` | | | ja | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx index f81147c5db..5864f5ec78 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx @@ -1,6 +1,7 @@ --- title: Fiat custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,6 +39,27 @@ import TabItem from '@theme/TabItem'; identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `fiat` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `ZFAE...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `pin` | Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx index f3bcae5d4a..4437193c1a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx @@ -1,6 +1,7 @@ --- title: Ford custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ford-connect.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -41,3 +42,23 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `ford-connect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| FordConnect API Client ID
`clientid` | Einrichtung unter https://developer.ford.com | | ja | +| FordConnect API Client Secret
`clientsecret` | Einrichtung unter https://developer.ford.com | | ja | +| `accessToken` | | | ja | +| `refreshToken` | | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WF0FXX...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx index a0ad8557fd..de46a4b083 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -1,6 +1,7 @@ --- title: Generisches Fahrzeug (ohne API) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/offline.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -30,3 +31,17 @@ import TabItem from '@theme/TabItem'; identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `offline` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx index 6ac00d56e8..d5b3b50feb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx @@ -1,6 +1,7 @@ --- title: Hyundai Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/hyundai.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `hyundai` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Sprache
`language` | | Standard: `en`
Auswahl: `en`, `de` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx index 14d17d1a2f..a319516ae8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx @@ -34,13 +34,13 @@ import DeviceGrid from '@site/src/components/DeviceGrid'; + +## Templateparameter `ioBroker.bmw` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Fahrzeugidentifikationsnummer
`vin` | BMW Fahrzeugidentifikationsnummer | Beispiel: `WBA8E9G50GM091234` | ja | +| ioBroker URL einschliesslich ioBroker.simple-api Port
`uri` | HTTP(S) Adresse | | ja | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Instanz-ID
`id` | | | nein | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx deleted file mode 100644 index 6a60b4d11b..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobrokerbmw.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: ioBroker.bmw -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ioBroker.bmw.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# ioBroker.bmw - -ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api - - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx index bb8d6d44e4..c3149bc0c3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx @@ -1,6 +1,7 @@ --- title: ISO15118 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/iso15118.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,17 @@ angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `iso15118` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx index 2352d89ce4..b990425542 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx @@ -1,6 +1,7 @@ --- title: Jeep custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,6 +39,27 @@ import TabItem from '@theme/TabItem'; identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `fiat` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `ZFAE...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `pin` | Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx index 7a2a9f3ed1..b3f4272aff 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx @@ -1,6 +1,7 @@ --- title: Kia Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/kia.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern a priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `kia` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Sprache
`language` | | Standard: `en`
Auswahl: `en`, `de` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx index c70fdd75d6..1bee6f3498 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx @@ -1,6 +1,7 @@ --- title: Mercedes-Benz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mercedes.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -44,3 +45,23 @@ Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https:/ priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `mercedes` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | ja | +| `accessToken` | | | ja | +| `refreshToken` | | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx index b7b591d670..23f37582ef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx @@ -1,6 +1,7 @@ --- title: MG custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,22 @@ import TabItem from '@theme/TabItem'; cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) region: EU # Region, [EU, AU]`} /> +## Templateparameter `mg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `AU` | ja | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx index c165dbb0c3..60dc449a33 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx @@ -1,6 +1,7 @@ --- title: mg2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg2mqtt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (http identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `mg2mqtt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Zeitüberschreitung
`timeout` | | Standard: `1h`
Beispiel: `10s` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx index 8342922c50..2692280d32 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx @@ -1,6 +1,7 @@ --- title: Mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mini.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,6 +43,28 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) region: EU # Region, [EU, NA] - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `mini` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WBMW...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `hcaptcha` | | | ja | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `NA` | ja | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx index 6eb62f3832..85cbc1d249 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx @@ -1,6 +1,7 @@ --- title: mz2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mz2mqtt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,3 +37,19 @@ myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mq priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) timeout: 720h # Zeitüberschreitung, optional`} /> +## Templateparameter `mz2mqtt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Zeitüberschreitung
`timeout` | | Standard: `720h`
Beispiel: `10s` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx index cfacc95a13..34105418f4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx @@ -1,6 +1,7 @@ --- title: Nissan Ariya custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan-ariya.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `nissan-ariya` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx index f27a797239..4ed7588c2e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -1,6 +1,7 @@ --- title: Nissan Leaf (pre 2019) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/carwings.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `carwings` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx index f3909de688..de9c4cffd3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx @@ -1,6 +1,7 @@ --- title: Nissan Leaf custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `nissan` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx index 00c3367ac2..1cc3d69700 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx @@ -1,6 +1,7 @@ --- title: NIU E-Scooter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/niu-e-scooter.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -22,3 +23,14 @@ import TabItem from '@theme/TabItem'; serial: # Scooter Seriennummer, wie in der NIU app angegeben capacity: 4 # Akkukapazität (kWh), optional`} /> +## Templateparameter `niu-e-scooter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `scooter`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Scooter Seriennummer, wie in der NIU app angegeben
`serial` | | | ja | +| Akkukapazität
`capacity` | | Standard: `4`
Beispiel: `50`
Einheit: kWh | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx index d25c710d6e..bfc6d3dd91 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx @@ -1,6 +1,7 @@ --- title: Opel custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/opel.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `opel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| `accessToken` | | | ja | +| `refreshToken` | | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx index 8ecc11fce8..3fe697a26f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -1,6 +1,7 @@ --- title: Open Vehicle Monitoring System custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ovms.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -41,3 +42,22 @@ Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei server: dexters-web.de cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `ovms` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| `vehicleid` | | | ja | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| `server` | | Standard: `dexters-web.de` | ja | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx index 2bb8f8d990..8a359d2ca4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx @@ -1,6 +1,7 @@ --- title: Peugeot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/peugeot.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -42,3 +43,22 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `peugeot` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| `accessToken` | | | ja | +| `refreshToken` | | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx index 03fdf17495..c7522d8ee8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx @@ -1,6 +1,7 @@ --- title: Polestar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/polestar.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `polestar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `LPSVS...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx index 9afd3a6d29..5fe3266216 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx @@ -1,6 +1,7 @@ --- title: PSA Car Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/flobz.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,20 @@ Remote Control of PSA car https://github.com/flobz/psa_car_controller priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) wakeup_alt: false # alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. (optional)`} /> +## Templateparameter `flobz` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| `url` | | Beispiel: `http://192.0.2.2` | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| `wakeup_alt` | alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx index 382165f4a6..2384a2104c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx @@ -1,6 +1,7 @@ --- title: Renault custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/renault.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -38,3 +39,22 @@ import TabItem from '@theme/TabItem'; cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) wakeupmode: default # Aufweckmechanismus, [default, alternative, MY24] (optional)`} /> +## Templateparameter `renault` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WREN...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| Aufweckmechanismus
`wakeupmode` | | Standard: `default`
Auswahl: `default`, `alternative`, `MY24` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx index 530ca99abd..185126ba83 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -1,6 +1,7 @@ --- title: Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/seat.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `seat` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx index b5ebe28cda..b576d59a9c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -1,6 +1,7 @@ --- title: Seat CupraConnect Gen4 (Born, Formentor, Tavascan) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/cupra.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -36,6 +37,26 @@ import TabItem from '@theme/TabItem'; identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +## Templateparameter `cupra` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx index eab2157926..412dcd118f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx @@ -1,6 +1,7 @@ --- title: Skoda Enyaq custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/enyaq.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,22 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `enyaq` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Zeitüberschreitung
`timeout` | | Standard: `10s`
Beispiel: `10s` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx new file mode 100644 index 0000000000..8e6688e249 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx @@ -0,0 +1,62 @@ +--- +title: Smart +custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml +hide_table_of_contents: true +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@site/src/components/DeviceFeatures'; +import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Smart + + + +## Templateparameter `smart-hello` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx index 7675572fe4..85b6b45d52 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx @@ -1,6 +1,7 @@ --- title: Smart EQ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -44,3 +45,23 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `smart` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | ja | +| `accessToken` | | | ja | +| `refreshToken` | | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx deleted file mode 100644 index 2c7e3bf190..0000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Smart -custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml ---- - -import DeviceConfig from '@site/src/components/DeviceConfig'; -import DeviceFeatures from '@site/src/components/DeviceFeatures'; -import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Smart - - - diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx index d25b9d96b3..d63f47fd01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx @@ -1,6 +1,7 @@ --- title: Tesla BLE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla-ble.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `tesla-ble` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Fahrzeugidentifikationsnummer
`vin` | Erforderlich für BLE-Verbindung | Beispiel: `W...` | ja | +| `url` | URL des Tesla BLE HTTP Proxy | Beispiel: `http://192.168.178.27` | ja | +| Port
`port` | Port des Tesla BLE HTTP Proxy | Standard: `8080`
Beispiel: `8080` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx index 1044ef66d7..c3e69c06ef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx @@ -1,6 +1,7 @@ --- title: Tesla custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -57,3 +58,24 @@ Weitere Informationen und Alternativen findest du in [unserem Blogbeitrag](https proxyToken: # Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `tesla` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `clientId` | Kunden ID deiner \[Tesla Developer App\](https://developer.tesla.com/dashboard). | | ja | +| `accessToken` | von \[myteslamate.com\](https://app.myteslamate.com/). | | ja | +| `refreshToken` | von \[myteslamate.com\](https://app.myteslamate.com/). | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| `commandProxy` | Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der \[myteslamate.com\](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel \[TeslaBleHttpProxy\](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. | Standard: `https://api.myteslamate.com` | nein | +| `proxyToken` | Token für den Command Proxy von \[myteslamate.com\](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx index a5671cb553..31bcb2ef52 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx @@ -1,6 +1,7 @@ --- title: TeslaLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslalogger.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -39,3 +40,20 @@ Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `teslalogger` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| TeslaLogger CarID
`id` | | Standard: `1` | nein | +| `url` | | Beispiel: `http://192.0.2.2` | ja | +| Port
`port` | | Standard: `5000`
Beispiel: `5000` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx index e427fa69d1..0e976919fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx @@ -1,6 +1,7 @@ --- title: TeslaMate custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslamate.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -35,3 +36,18 @@ Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Vorausse identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `teslamate` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Fahrzeug-ID
`id` | | Standard: `1` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx index b244bde94f..327b71c728 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx @@ -1,6 +1,7 @@ --- title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tessie.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,19 @@ Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug ni identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `tessie` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Fahrzeug-VIN
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Tessie API Token
`token` | | | ja | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx index db02a1ec73..aedf7e8b38 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx @@ -1,6 +1,7 @@ --- title: Toyota custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/toyota.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,3 +41,21 @@ Benötigt Toyota Connected Services Account. priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `toyota` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `JT...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx index 88585fef63..0335cb1776 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx @@ -1,6 +1,7 @@ --- title: Tronity custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tronity.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,5 +38,23 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `tronity` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Tronity API Client ID
`clientid` | Einrichtung unter https://app.tronity.tech | | ja | +| Tronity API Client Secret
`clientsecret` | Einrichtung unter https://app.tronity.tech | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx index 79fd1d7abb..f428ac1a17 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -1,6 +1,7 @@ --- title: Volkswagen We Connect ID custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/vw.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -40,5 +41,28 @@ e-Golf, e-Up, ID Familie maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> + +## Templateparameter `vw` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WVWZZZ...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Zeitüberschreitung
`timeout` | | Standard: `10s`
Beispiel: `10s` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | +| 1A Ladestromvorgabe
`coarsecurrent` | Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe | | nein | +| Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx index f033629235..aa232dcd2a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx @@ -1,6 +1,7 @@ --- title: Volvo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo-connected.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -50,3 +51,22 @@ Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Is identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `volvo-connected` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| `vccapikey` | VCC API Key deiner \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | +| `clientId` | Client ID deiner \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | +| `clientSecret` | Client Secret deiner \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | +| `redirectUri` | Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WF0FXX...` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx index 4aa05cd54b..91b66a1187 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx @@ -1,6 +1,7 @@ --- title: volvo2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo2mqtt.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,19 @@ Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqt identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +## Templateparameter `volvo2mqtt` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Zeitüberschreitung
`timeout` | | Standard: `720h`
Beispiel: `10s` | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | + diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx index e39ad06e4a..67ba0c3bd9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx @@ -1,6 +1,7 @@ --- title: Zero Motorcycles custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/zero.yaml +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -37,3 +38,21 @@ import TabItem from '@theme/TabItem'; priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +## Templateparameter `zero` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | +| Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | +| Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | +| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | +| Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | +| Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | +| Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | +| Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | + diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx index e0b48a7821..a324d1dcd1 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx @@ -90,7 +90,7 @@ Requires firmware >= 1.6.5 -### Terra AC +### Terra AC (OCPP) @@ -120,7 +120,33 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C ## ABL -### eM4 (SBCx) +### eM4 Single (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + + + + + +### eM4 Single (SBCx) @@ -151,28 +177,56 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH1 +### eM4 Twin (OCPP) + + + +:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + - name: my_charger + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + + + + + + + +### eM4 Twin (SBCx) + connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> @@ -180,7 +234,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH2 +### eMH1 @@ -209,27 +263,28 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -## ABL Sursum - ### eMH2 - + :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - - name: my_charger - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional`} /> @@ -237,7 +292,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH3 +### eMH2 (OCPP) @@ -263,7 +318,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH4 +### eMH3 (OCPP) @@ -314,7 +369,7 @@ The "Active load balancing" license is required for external Modbus control of t -### Eve +### Eve (OCPP) @@ -529,29 +584,6 @@ Please read the wiring and configuration manual carefully. All boxes must be con ## Ampure -### Live - - - -The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. - - - - - - - - - ### NEXT @@ -980,7 +1012,32 @@ Phase switching is only available with the Solar variant and must be enabled by -## CUBOS C11E, C22E +## CUBOS + +### C11E + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + + + + +### C22E @@ -2232,7 +2289,37 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft -## Free2Move eProWallbox +## Free2Move + +### eProWallbox + + + + + + + + + + + +### eProWallbox Move @@ -2286,7 +2373,7 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft -## Fronius Wattpilot +## Fronius Wattpilot (OCPP) @@ -2312,7 +2399,78 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft -## Garo GLB, GLB+, LS4, LS4 compact +## Garo + +### GLB + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + + + + +### GLB+ + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + + + + +### LS4 + + + +The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. + + + + + + + + + +### LS4 compact @@ -2357,7 +2515,7 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" -### Charger Gemini +### Charger Gemini (OCPP) @@ -2439,7 +2597,7 @@ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. -### Charger PRO +### Charger PRO (OCPP) @@ -2485,7 +2643,7 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" -### Charger V3 +### Charger V3 (OCPP) @@ -2513,15 +2671,22 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" ## Hardy Barth -### cPH2 +### cPH1 +Charge mode must be configured as `manual` + + template: hardybarth-ecb1 + host: 192.0.2.2 # IP address or hostname`} advanced={`chargers: + - name: my_charger + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP address or hostname + connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> @@ -2529,7 +2694,7 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" -### cPμ2 +### cPH2 @@ -2545,22 +2710,15 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" -## HardyBarth cPH1 +### cPμ2 -Charge mode must be configured as `manual` - 1 loadpoint), optional`} /> + template: hardybarth-salia + host: 192.0.2.2 # IP address or hostname`} /> @@ -5980,6 +6138,24 @@ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. + + + + + + + + +### Go (OCPP) + + + OCPP Native mode https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ @@ -6002,24 +6178,6 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - - - - -### Go - - - - - - - diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx index 5e643cdad5..db860dc942 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx @@ -216,7 +216,180 @@ If your system isn't listed here, that might mean that it is 100% SunSpec-compat -## ABB A43, A44, B23, B24 +## ABB + +### A43 + + + + + + + + + + + + + + + + + + + + + + +### A44 + + + + + + + + + + + + + + + + + + + + + + +### B23 + + + + + + + + + + + + + + + + + + + + + + +### B24 @@ -273,7 +446,7 @@ If your system isn't listed here, that might mean that it is 100% SunSpec-compat -## Acrel ADW300 Wireless Metering Meter +## Acrel ADW300 @@ -3568,7 +3741,7 @@ Solar API should only be used as fallback. Integration via Modbus is preferred. Username and password are only required for active battery control. -**Attention**: Active battery control should only be used if no other settings for time-dependent battery control were made in the inverter configuration under "Energy Management" - "Battery Management", as existing settings will be overwritten. +**Attention**: Active battery control should only be used if no other settings for time-dependent battery control were made in the inverter configuration under "Energy Management" - "Battery Management", as existing settings will be overwritten. Choose corresponding configuration URI! @@ -3580,7 +3753,15 @@ Username and password are only required for active battery control. usage: grid host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} /> + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} advanced={`meters: + - name: my_grid + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> @@ -3594,7 +3775,15 @@ Username and password are only required for active battery control. usage: pv host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} /> + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional)`} advanced={`meters: + - name: my_pv + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> @@ -3616,7 +3805,8 @@ Username and password are only required for active battery control. host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - capacity: 50 # Battery capacity (kWh), optional`} /> + capacity: 50 # Battery capacity (kWh), optional + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> @@ -5207,7 +5397,78 @@ See https://www.iammeter.com/newsshow/net-energy-metering -## Janitza B series, UMG series +## Janitza + +### B series + + + + + + + + + + + + + + + + + + + + + + +### UMG series @@ -5419,6 +5680,39 @@ See https://www.iammeter.com/newsshow/net-energy-metering + + + + + +### Piko + + + + + + + + + + + + + + + + + @@ -5439,6 +5733,39 @@ See https://www.iammeter.com/newsshow/net-energy-metering + + +### Piko BA + + + + + + + + + + + + + + + + + + + + ### Piko Hybrid @@ -5505,39 +5832,6 @@ See https://www.iammeter.com/newsshow/net-energy-metering - - -### Piko, Piko BA - - - - - - - - - - - - - - - - - - - - ### Plenticore Hybrid @@ -6374,7 +6668,66 @@ A commercial license is required for FEMS FENECON systems for active battery con -## Orno OR-WE-516, OR-WE-517 +## ORNO + +### OR-WE-516 + + + + + + + + + + + + + + + + + + + + + + +### OR-WE-517 @@ -6611,11 +6964,13 @@ The values are updated approximately every 15 seconds, hence the evcc `interval` -## QCells Hybrid-Inverter (Cloud) +## Qcells + +### Hybrid-Inverter (Cloud) -The QCells hybrid inverter has to be registered in the QCellsCloud. +The Qcells hybrid inverter has to be registered in the QcellsCloud. **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. @@ -6627,7 +6982,7 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. type: template template: qcells-hybrid-cloud usage: grid - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number.`} /> @@ -6640,7 +6995,7 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. type: template template: qcells-hybrid-cloud usage: pv - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number.`} /> @@ -6653,13 +7008,13 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number.`} advanced={`meters: - name: my_battery type: template template: qcells-hybrid-cloud usage: battery - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. capacity: 50 # Battery capacity (kWh), optional`} /> @@ -6670,7 +7025,7 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. -## Qcells Q.HOME ESS HYB-G3 +### Q.HOME ESS HYB-G3 @@ -6924,7 +7279,66 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. -## Saia-Burgess Controls ALE3, AWD3 +## Saia-Burgess Controls (SBC) + +### ALE3 + + + + + + + + + + + + + + + + + + + + + + +### AWD3 @@ -8220,7 +8634,7 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server ## Smartfox -### Box, Reg, Reg extended +### Box @@ -8267,7 +8681,7 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server -### Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) +### Light (EM2 firmware) @@ -8332,13 +8746,11 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server -## SofarSolar - -### HYD 3…6K-EP +### Pro - + -LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. +`aux` can be used for water heating power. @@ -8346,51 +8758,15 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -8400,108 +8776,33 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> - + + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -8510,11 +8811,11 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th -### HYD 5…20K-3PH +### Pro 2 - + -LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. +`aux` can be used for water heating power. @@ -8522,51 +8823,15 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -8576,108 +8841,257 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> - + + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> + + + + + + + + +### Pro Light + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Pro Light 2 + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Reg + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Reg extended + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + @@ -8686,7 +9100,9 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th -### Inverter, Hybrid Inverter +## SofarSolar + +### Hybrid Inverter @@ -8809,7 +9225,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th -### SOFAR 5…24KTL-G3 +### HYD 3…6K-EP @@ -8985,7 +9401,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th -### SOFAR 80…136KTL +### HYD 5…20K-3PH @@ -9161,7 +9577,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th -## Solaranzeige Solaranzeige +### Inverter @@ -9171,22 +9587,27 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> @@ -9196,22 +9617,81 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th + + + + + + + + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} advanced={`meters: + - name: my_battery + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional`} /> @@ -9220,14 +9700,11 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th -## SolarEdge - -### Hybrid Inverter +### SOFAR 5…24KTL-G3 -Only one system can and may have a Modbus TCP connection to the inverter at the same time! -For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Remote". +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. @@ -9235,7 +9712,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -9291,7 +9766,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -9348,7 +9821,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re + defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> @@ -9404,11 +9876,11 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re -### Inverter +### SOFAR 80…136KTL - + -Only one system may access the inverter! +LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. @@ -9416,7 +9888,7 @@ Only one system may access the inverter! + port: 8899 # Port`} advanced={`meters: + - name: my_grid + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -9447,7 +9942,7 @@ Only one system may access the inverter! + port: 8899 # Port`} advanced={`meters: + - name: my_pv + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> - - - - -## Solarlog - - - -We recommend to use this device for grid power values only, if no other device is available providing this data. -If you have a home battery installed, please do not use this device at all for grid power values. - - - + + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port`} advanced={`meters: + - name: my_battery + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> + + + + + + + + +## Solaranzeige Solaranzeige + + + + + + + @@ -9503,10 +10087,22 @@ If you have a home battery installed, please do not use this device at all for g + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional)`} advanced={`meters: + - name: my_pv + type: template + template: solaranzeige + usage: pv + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional)`} /> @@ -9515,13 +10111,14 @@ If you have a home battery installed, please do not use this device at all for g -## SolarMax +## SolarEdge -### MAX.STORAGE / MAX.STORAGE Ultimate +### Hybrid Inverter -For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. +Only one system can and may have a Modbus TCP connection to the inverter at the same time! +For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Remote". @@ -9529,24 +10126,52 @@ For batter control, the "Connectivity+" function must be activated via the Solar @@ -9557,24 +10182,52 @@ For batter control, the "Connectivity+" function must be activated via the Solar @@ -9586,24 +10239,52 @@ For batter control, the "Connectivity+" function must be activated via the Solar @@ -9614,38 +10295,248 @@ For batter control, the "Connectivity+" function must be activated via the Solar -### SolarMax SMT +### Inverter +Only one system may access the inverter! + + + + - - + port: 1502 # Port + timeout: 10s # Timeout, optional`} /> - -### SP Series Inverter - + + + + + + + + + + +## Solarlog + + + +We recommend to use this device for grid power values only, if no other device is available providing this data. +If you have a home battery installed, please do not use this device at all for grid power values. + + + + + + + + + + + + + + + + + + + + +## SolarMax + +### MAX.STORAGE / MAX.STORAGE Ultimate + + + +For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### SolarMax SMT + + + + + + + + + +### SP Series Inverter + + + + @@ -9656,7 +10547,58 @@ For batter control, the "Connectivity+" function must be activated via the Solar ## Solarwatt -### EnergyManager, EnergyManager Pro +### EnergyManager + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### EnergyManager Pro @@ -10265,7 +11207,7 @@ The Solax inverter has to be registered in the SolaxCloud. ## Sonnen -### comfort, eco 5, eco 6, oem 6.5 +### comfort @@ -10336,13 +11278,9 @@ The Solax inverter has to be registered in the SolaxCloud. -### sonnenBatterie - - +### eco 5 -For active battery control, the "JSON Write API" must be activated via the sonnenBatterie web interface (under Software-Integration) and the API token generated there must be entered in the battery configuration under `token`. -The two operating modes supported for the sonnenBatterie are “self-consumption” (default) and “time-of-use”. The mode can be adapted to the configuration of the sonnenBatterie via the 'defaultmode' parameter. -The power for grid charging can be adapted to the inverter power of the sonnenBatterie via the `maxchargepower` parameter. + @@ -10350,12 +11288,229 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa - - + port: 7979 # Port, optional`} advanced={`meters: + - name: my_grid + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> + + + + + + + + + + + + + + + + + + + + + + +### eco 6 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### oem 6.5 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### sonnenBatterie + + + +For active battery control, the "JSON Write API" must be activated via the sonnenBatterie web interface (under Software-Integration) and the API token generated there must be entered in the battery configuration under `token`. +The two operating modes supported for the sonnenBatterie are “self-consumption” (default) and “time-of-use”. The mode can be adapted to the configuration of the sonnenBatterie via the 'defaultmode' parameter. +The power for grid charging can be adapted to the inverter power of the sonnenBatterie via the `maxchargepower` parameter. + + + + + + + @@ -11737,7 +12892,9 @@ The following apps allow to create the token: -## VARTA pulse, pulse neo, element +## VARTA + +### element @@ -11794,13 +12951,11 @@ PV only available with PV sensor -## Victron - -### EM24 +### pulse -EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. +PV only available with PV sensor @@ -11808,41 +12963,157 @@ EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Etherne + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional`} /> - + + + + + + + + + + + + + + + + +### pulse neo + + + +PV only available with PV sensor + + + + + + + + + + + + + + + + + + + + + + + + + + + +## Victron + +### EM24 + + + +EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. + + + + + + + + + + + + -## ZCS Azzurro Inverter, Hybrid Inverter +## ZCS Azzurro + +### Hybrid Inverter @@ -12698,22 +13971,67 @@ An externally connected S0 generation meter is required to record the solar prod -## Zendure Hyper 2000 +### Inverter - + + + + + + + + + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> @@ -12723,21 +14041,51 @@ An externally connected S0 generation meter is required to record the solar prod + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional`} /> @@ -12746,14 +14094,62 @@ An externally connected S0 generation meter is required to record the solar prod -## Zuidwijk - -### SlimmeLezer(+) +## Zendure Hyper 2000 - + + + + + + + + + + + + + + + + + + +## Zuidwijk + +### SlimmeLezer(+) + + + + - + + + + +### Volkszähler + +#### HTTP API + + + + + + + + + +#### HTTP API, Import & Export + + + + + + + + + +#### WebSocket API + + + + + + + + + +### vzlogger + + + + + + + + + +## Switchable sockets + +### AVM FritzDECT + + + + + + + + + + + + + + + + + + + + + + +### Homematic IP + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### myStrom Switch + + + + + + + + + + + + + + + + + + + + + + +### Shelly + +#### 1PM + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +#### 1PM mini + + + + + + + + + + + + - + -### Volkszähler -#### HTTP API - + + + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> + + + -#### HTTP API, Import & Export +#### EM + + + + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> - + + -#### WebSocket API + - + + + + + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> + + + -### vzlogger +#### Plug S + + + - - - - - -## Switchable sockets + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> -### AVM FritzDECT - - - + + + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> @@ -13467,12 +15201,12 @@ For demonstration purposes. Meter with a fixed set of values. + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> @@ -13481,7 +15215,7 @@ For demonstration purposes. Meter with a fixed set of values. -### Homematic IP +#### PM mini @@ -13491,75 +15225,96 @@ For demonstration purposes. Meter with a fixed set of values. + + + + + + + + channel: 0 # optional`} /> - + + + + + + + + + +#### Pro 1PM + + + + + + + + channel: 0 # optional`} /> - + + + + + + + + + channel: 0 # optional`} /> @@ -13568,19 +15323,37 @@ For demonstration purposes. Meter with a fixed set of values. -### myStrom Switch +#### Pro 3EM (monophase mode) - + + + + + + + + + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> @@ -13590,9 +15363,12 @@ For demonstration purposes. Meter with a fixed set of values. + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional`} /> @@ -13601,7 +15377,7 @@ For demonstration purposes. Meter with a fixed set of values. -### Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode +#### Pro EM diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx index 7a87644edf..fc0277ff0d 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx @@ -245,7 +245,90 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in -### Shelly +### Shelly + +#### 1 + + + + + + + +#### Plug S + + + + + + + +#### Plus 1 + + + + + + + +#### Pro 1 @@ -210,7 +210,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> @@ -282,7 +282,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> @@ -390,7 +390,7 @@ Some models (e.g. Kona) switch internally to 2 phases at low charging currents ( identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> @@ -536,7 +536,7 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) region: EU # Region, [EU, NA] - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> @@ -839,7 +839,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> @@ -909,7 +909,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> @@ -1071,7 +1071,7 @@ e-Golf, e-Up, ID family identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> @@ -1254,15 +1254,15 @@ ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api template: ioBroker.bmw title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - uri: # URI, HTTP(S) address`} advanced={`vehicles: + vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber + uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address`} advanced={`vehicles: - name: my_car type: template template: ioBroker.bmw title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - uri: # URI, HTTP(S) address + vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber + uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) @@ -1270,8 +1270,8 @@ ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - id: 0 # Instance ID (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) + id: 0 # Instance ID, optional + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> diff --git a/src/css/custom.css b/src/css/custom.css index 24908ab513..75a3b6f390 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -147,3 +147,16 @@ article.margin-bottom--xl footer .text--right a { ol ol { list-style-type: decimal; } + +/* Parameter table styling - allow code wrapping */ +table td code { + word-break: break-word; + white-space: normal; +} + +/* Parameter table alignment - left and top aligned */ +table td, +table th { + text-align: left; + vertical-align: top; +} diff --git a/src/generateDevicesNext.ts b/src/generateDevicesNext.ts index 3b47cf5086..36d385fbaa 100644 --- a/src/generateDevicesNext.ts +++ b/src/generateDevicesNext.ts @@ -2,7 +2,6 @@ import * as fs from "fs"; import * as path from "path"; import * as yaml from "js-yaml"; import * as countries from "i18n-iso-countries"; -import slugify from "slugify"; // Register locale data countries.registerLocale(require("i18n-iso-countries/langs/en.json")); @@ -13,11 +12,25 @@ interface ProductData { brand: string; description?: string; group?: string; + identifier: string; }; + template: string; capabilities?: string[]; requirements?: string[]; countries?: string[]; description?: string; + params?: Array<{ + name: string; + description: string; + help?: string; + type?: string; + unit?: string; + example?: any; + default?: any; + choice?: any[]; + optional?: boolean; + advanced?: boolean; + }>; render: Array<{ usage?: string; default: string; @@ -33,7 +46,7 @@ interface DeviceCard { capabilities: string[]; requirements: string[]; countries: string[]; - slug: string; + identifier: string; group?: string; } @@ -70,6 +83,13 @@ const TRANSLATIONS_DE: Record = { "tab.charge": "Wallbox", "tab.aux": "AUX", global: "Global", + "params.title": "## Templateparameter", + "params.header": "| Name | Erklärung | Wert | Optional |", + "params.separator": "|-----------|-----------|------|----------|", + "params.required.yes": "nein", + "params.required.no": "ja", + "params.advanced": "erweitert", + "params.basic": "standard", }; const TRANSLATIONS_EN: Record = { @@ -79,6 +99,13 @@ const TRANSLATIONS_EN: Record = { "tab.charge": "Wallbox", "tab.aux": "AUX", global: "Global", + "params.title": "## Template Parameter", + "params.header": "| Name | Explanation | Value | Optional |", + "params.separator": "|-----------|-------------|-------|----------|", + "params.required.yes": "no", + "params.required.no": "yes", + "params.advanced": "advanced", + "params.basic": "basic", }; interface TemplateWithFilename extends ProductData { @@ -121,80 +148,13 @@ const readTemplates = (templatePath: string): TemplateWithFilename[] => { }); }; -const extractTemplateNameFromFilename = (filename: string): string => { - // Extract template name from filename like "tesla_0.yaml" -> "tesla" - return filename.replace(/_\d+\.yaml$/, "").replace(/\.yaml$/, ""); -}; - -const normalizeForComparison = (text: string): string => { - return text - .toLowerCase() - .normalize("NFD") // Decompose accented characters - .replace(/[\u0300-\u036f]/g, "") // Remove diacritics - .replace(/[^a-z0-9]/g, ""); // Remove all non-alphanumeric characters -}; - -const createSlug = ( - brand: string, - description: string, - templateName: string, -): string => { - const parts: string[] = []; - - // Add brand if it exists and is not empty - if (brand && brand.trim()) { - parts.push(brand); - } - - // Add description if it exists AND is different from brand (normalized comparison) - if (description && description.trim()) { - const normalizedBrand = normalizeForComparison(brand); - const normalizedDescription = normalizeForComparison(description); - - if (normalizedDescription !== normalizedBrand) { - parts.push(description); - } - } - - // If no parts, we have a problem - skip this template - if (parts.length === 0) { - console.warn( - `No brand or description found for template: ${templateName} - skipping`, - ); - return ""; - } - - return slugify(parts.join(" "), { - lower: true, - strict: true, - remove: /[*+~.()'"!:@]/g, - }); -}; - -const getEnglishDescription = ( - template: TemplateWithFilename, - deviceType: string, -): string => { - // Try to find the corresponding English template - const englishTemplatePath = `./templates/release/en/${deviceType}`; - try { - const englishTemplates = readTemplates(englishTemplatePath); - const matchingTemplate = englishTemplates.find( - (t) => t._filename === template._filename, - ); - - if (matchingTemplate && matchingTemplate.product.description) { - return matchingTemplate.product.description; - } - } catch (e) { - // If we can't find English template, fall back to current description - } - - return template.product.description || ""; -}; - const indentCode = (code: string, list = false): string => { - let result = code.replace(/`/g, "\\`"); + let result = code + .replace(/`/g, "\\`") + .replace(/\\(\d)/g, "\\\\$1") // escape backreferences like \1, \2 + .replace(/\\\?/g, "\\\\?") // escape literal ? in regex + .replace(/\\\(/g, "\\\\(") // escape literal ( in regex + .replace(/\\\)/g, "\\\\)"); // escape literal ) in regex if (list) { result = result.replace(/^/, " - "); @@ -212,14 +172,14 @@ const generateDeviceCard = ( language: string, ): DeviceCard | null => { const brand = data.product.brand || ""; - // Always use English description for slug consistency - const englishDescription = getEnglishDescription(data, deviceType); const description = data.product.description || ""; - const templateName = extractTemplateNameFromFilename(data._filename); - const slug = createSlug(brand, englishDescription, templateName); + const identifier = data.product.identifier; - // Skip if no valid slug could be created - if (!slug) { + // Skip if no identifier is provided + if (!identifier) { + console.warn( + `No identifier found for template: ${data._filename} - skipping`, + ); return null; } @@ -227,11 +187,11 @@ const generateDeviceCard = ( id: `${brand}-${description}`.replace(/\s+/g, "-").toLowerCase(), brand, description, - thumbnail: `/img/devices/${deviceType}/${slug}.jpg`, + thumbnail: `/img/devices/${deviceType}/${identifier}.jpg`, capabilities: data.capabilities || [], requirements: data.requirements || [], countries: data.countries || [], - slug, + identifier, group: data.product.group, }; }; @@ -289,10 +249,10 @@ ${cards thumbnail="${card.thumbnail}" capabilities={[${features.map((f) => `"${f}"`).join(", ")}]} requirements={[]} - href="/docs/devices-next/${deviceType}s/${card.slug}" + href="/docs/devices-next/${deviceType}s/${card.identifier}" group="${card.group || ""}" type="${deviceType}" - name="${card.slug}" + name="${card.identifier}" />`; }) .join("\n")} @@ -300,6 +260,103 @@ ${cards `; }; +const escapeMarkdown = (text: string): string => { + return text + .replace(//g, ">") + .replace(/\|/g, "\\|") + .replace(/\[/g, "\\[") + .replace(/\]/g, "\\]"); +}; + +const getParameterTable = ( + data: TemplateWithFilename, + language: string, +): string => { + const translate = makeTranslate(language); + + if (!data.params || data.params.length === 0) { + return ""; + } + + const headerRow = translate("params.header"); + const separatorRow = translate("params.separator"); + + const paramRows = data.params + .map((param) => { + const name = param.name || ""; + const description = param.description || ""; + + // Parameter: Description
`technical_name` + const paramColumn = description + ? `${escapeMarkdown(description)}
\`${escapeMarkdown(name)}\`` + : `\`${escapeMarkdown(name)}\``; + + // Erklärung: help text + const explanation = param.help ? escapeMarkdown(param.help) : ""; + + // Wert: Standard, Beispiel, Typ, Einheit + let value = ""; + const valueParts: string[] = []; + + if (param.default) { + valueParts.push( + `Standard: \`${escapeMarkdown(String(param.default))}\``, + ); + } + if (param.example) { + valueParts.push( + `Beispiel: \`${escapeMarkdown(String(param.example))}\``, + ); + } + if (param.type) { + valueParts.push(`Typ: ${param.type}`); + } + if (param.unit) { + valueParts.push(`Einheit: ${param.unit}`); + } + if (param.choice && param.choice.length > 0) { + // Alle Werte anzeigen, aber bei langen Listen mit Zeilenumbrüchen für bessere Lesbarkeit + if (param.choice.length > 10) { + // Sehr lange Listen: alle 5 Werte einen Umbruch + const choices = param.choice + .map((c, index) => { + const escaped = `\`${escapeMarkdown(String(c))}\``; + return (index + 1) % 5 === 0 ? escaped + "
" : escaped; + }) + .join(", ") + .replace(/, /g, "
"); // Letztes Komma vor Umbruch entfernen + valueParts.push(`Auswahl: ${choices}`); + } else { + // Normale Listen: alle Werte in einer Zeile + const choices = param.choice + .map((c) => `\`${escapeMarkdown(String(c))}\``) + .join(", "); + valueParts.push(`Auswahl: ${choices}`); + } + } + + value = valueParts.join("
"); + + // Optional status + const optional = + param.optional !== false + ? translate("params.required.yes") + : translate("params.required.no"); + + return `| ${paramColumn} | ${explanation} | ${value} | ${optional} |`; + }) + .join("\n"); + + const title = translate("params.title"); + + return `${title} \`${data.template}\` + +${headerRow} +${separatorRow} +${paramRows}`; +}; + const generateDetailPage = ( data: TemplateWithFilename, deviceType: string, @@ -371,16 +428,19 @@ ${block.code} : ""; // Create title from available parts - const titleParts = [brand, description].filter((part) => part.trim()); - const title = titleParts.join(" ") || "Device"; + const titleParts = [brand, description].filter((part) => part); + const title = titleParts.join(" ").trim() || "Device"; // Generate custom edit URL pointing to the original template - const cleanFilename = data._filename.replace(/_\d+\.yaml$/, ".yaml"); - const editUrl = `https://github.com/evcc-io/evcc/blob/master/templates/definition/${deviceType}/${cleanFilename}`; + const editUrl = `https://github.com/evcc-io/evcc/blob/master/templates/definition/${deviceType}/${data.template}.yaml`; + + // Get parameter table for this device type + const parameterTable = getParameterTable(data, language); return `--- title: ${title} custom_edit_url: ${editUrl} +hide_table_of_contents: true --- import DeviceConfig from '@site/src/components/DeviceConfig'; @@ -393,7 +453,7 @@ import TabItem from '@theme/TabItem'; ${deviceFeatures}${longDescription ? longDescription + "\n\n" : ""}${codeSection} -${sponsor}`; +${parameterTable ? parameterTable + "\n\n" : ""}${sponsor}`; }; const cleanDeviceFolders = () => { @@ -457,7 +517,7 @@ const generateDevicePages = () => { language, ); fs.writeFileSync( - path.join(deviceDir, `${card.slug}.mdx`), + path.join(deviceDir, `${card.identifier}.mdx`), detailContent, ); } diff --git a/templates/release/de/charger/Kathrein_0.yaml b/templates/release/de/charger/Kathrein_0.yaml deleted file mode 100644 index d955ccb705..0000000000 --- a/templates/release/de/charger/Kathrein_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC20 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/Kathrein_1.yaml b/templates/release/de/charger/Kathrein_1.yaml deleted file mode 100644 index 2746ca56c2..0000000000 --- a/templates/release/de/charger/Kathrein_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC35 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/Kathrein_2.yaml b/templates/release/de/charger/Kathrein_2.yaml deleted file mode 100644 index b6166e9840..0000000000 --- a/templates/release/de/charger/Kathrein_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC40 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/Kathrein_3.yaml b/templates/release/de/charger/Kathrein_3.yaml deleted file mode 100644 index ca7f52614b..0000000000 --- a/templates/release/de/charger/Kathrein_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC60 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/Kathrein_4.yaml b/templates/release/de/charger/Kathrein_4.yaml deleted file mode 100644 index 49a865ed56..0000000000 --- a/templates/release/de/charger/Kathrein_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC40 E -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/Kathrein_5.yaml b/templates/release/de/charger/Kathrein_5.yaml deleted file mode 100644 index 58bc15d24d..0000000000 --- a/templates/release/de/charger/Kathrein_5.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC60 E -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/abb-terra-ac-ocpp.yaml b/templates/release/de/charger/abb-terra-ac-ocpp.yaml new file mode 100644 index 0000000000..d6421baa6e --- /dev/null +++ b/templates/release/de/charger/abb-terra-ac-ocpp.yaml @@ -0,0 +1,88 @@ +template: ocpp-abb-tac +product: + identifier: abb-terra-ac-ocpp + brand: ABB + description: Terra AC (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf +render: + - default: | + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abb-terra-ac.yaml b/templates/release/de/charger/abb-terra-ac.yaml new file mode 100644 index 0000000000..0b8c1198bc --- /dev/null +++ b/templates/release/de/charger/abb-terra-ac.yaml @@ -0,0 +1,52 @@ +template: abb +product: + identifier: abb-terra-ac + brand: ABB + description: Terra AC +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Erfordert Firmware >= 1.6.5 +render: + - default: | + type: template + template: abb + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/abb_0.yaml b/templates/release/de/charger/abb_0.yaml deleted file mode 100644 index b5713aa394..0000000000 --- a/templates/release/de/charger/abb_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: ABB - description: Terra AC -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Erfordert Firmware >= 1.6.5 -render: - - default: | - type: template - template: abb - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/abl-em4-single-ocpp.yaml b/templates/release/de/charger/abl-em4-single-ocpp.yaml new file mode 100644 index 0000000000..0f8db48915 --- /dev/null +++ b/templates/release/de/charger/abl-em4-single-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-em4-single-ocpp + brand: ABL + description: eM4 Single (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-em4-single-sbcx.yaml b/templates/release/de/charger/abl-em4-single-sbcx.yaml new file mode 100644 index 0000000000..72d5a56e1e --- /dev/null +++ b/templates/release/de/charger/abl-em4-single-sbcx.yaml @@ -0,0 +1,52 @@ +template: abl-em4 +product: + identifier: abl-em4-single-sbcx + brand: ABL + description: eM4 Single (SBCx) +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-em4-twin-ocpp.yaml b/templates/release/de/charger/abl-em4-twin-ocpp.yaml new file mode 100644 index 0000000000..fbee674238 --- /dev/null +++ b/templates/release/de/charger/abl-em4-twin-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-em4-twin-ocpp + brand: ABL + description: eM4 Twin (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-em4-twin-sbcx.yaml b/templates/release/de/charger/abl-em4-twin-sbcx.yaml new file mode 100644 index 0000000000..42c3303621 --- /dev/null +++ b/templates/release/de/charger/abl-em4-twin-sbcx.yaml @@ -0,0 +1,52 @@ +template: abl-em4 +product: + identifier: abl-em4-twin-sbcx + brand: ABL + description: eM4 Twin (SBCx) +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-em4_0.yaml b/templates/release/de/charger/abl-em4_0.yaml deleted file mode 100644 index e4a7c746b2..0000000000 --- a/templates/release/de/charger/abl-em4_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: ABL - description: eM4 (SBCx) -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl-em4 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: abl-em4 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/abl-emh1.yaml b/templates/release/de/charger/abl-emh1.yaml new file mode 100644 index 0000000000..9cbb582bfe --- /dev/null +++ b/templates/release/de/charger/abl-emh1.yaml @@ -0,0 +1,53 @@ +template: abl +product: + identifier: abl-emh1 + brand: ABL + description: eMH1 +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true +modbus: + baudrate: 38400 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-emh2-ocpp.yaml b/templates/release/de/charger/abl-emh2-ocpp.yaml new file mode 100644 index 0000000000..bac10760a4 --- /dev/null +++ b/templates/release/de/charger/abl-emh2-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-emh2-ocpp + brand: ABL + description: eMH2 (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-emh2.yaml b/templates/release/de/charger/abl-emh2.yaml new file mode 100644 index 0000000000..55ad16e372 --- /dev/null +++ b/templates/release/de/charger/abl-emh2.yaml @@ -0,0 +1,53 @@ +template: abl +product: + identifier: abl-emh2 + brand: ABL + description: eMH2 +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true +modbus: + baudrate: 38400 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-emh3-ocpp.yaml b/templates/release/de/charger/abl-emh3-ocpp.yaml new file mode 100644 index 0000000000..3c69c83b73 --- /dev/null +++ b/templates/release/de/charger/abl-emh3-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-emh3-ocpp + brand: ABL + description: eMH3 (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abl_0.yaml b/templates/release/de/charger/abl_0.yaml deleted file mode 100644 index 2db141ddc7..0000000000 --- a/templates/release/de/charger/abl_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: ABL - description: eMH1 -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional diff --git a/templates/release/de/charger/abl_1.yaml b/templates/release/de/charger/abl_1.yaml deleted file mode 100644 index fe121664f0..0000000000 --- a/templates/release/de/charger/abl_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: ABL - description: eMH2 -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional diff --git a/templates/release/de/charger/abl_2.yaml b/templates/release/de/charger/abl_2.yaml deleted file mode 100644 index b2d358efb7..0000000000 --- a/templates/release/de/charger/abl_2.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: SENEC - description: Wallbox pro -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional diff --git a/templates/release/de/charger/ac-elwa-2_0.yaml b/templates/release/de/charger/ac-elwa-2_0.yaml deleted file mode 100644 index 0761b56204..0000000000 --- a/templates/release/de/charger/ac-elwa-2_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: my-PV - description: AC ELWA 2 - group: Wärmeerzeuger -requirements: ["sponsorship"] -render: - - default: | - type: template - template: ac-elwa-2 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional diff --git a/templates/release/de/charger/ac-thor_0.yaml b/templates/release/de/charger/ac-thor_0.yaml deleted file mode 100644 index 3bee385fb6..0000000000 --- a/templates/release/de/charger/ac-thor_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: my-PV - description: AC•THOR - group: Wärmeerzeuger -requirements: ["sponsorship"] -render: - - default: | - type: template - template: ac-thor - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) - scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional diff --git a/templates/release/de/charger/ac-thor_1.yaml b/templates/release/de/charger/ac-thor_1.yaml deleted file mode 100644 index 6c3e454aeb..0000000000 --- a/templates/release/de/charger/ac-thor_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: my-PV - description: AC•THOR 9s - group: Wärmeerzeuger -requirements: ["sponsorship"] -render: - - default: | - type: template - template: ac-thor - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) - scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional diff --git a/templates/release/de/charger/alfen-eve-ocpp.yaml b/templates/release/de/charger/alfen-eve-ocpp.yaml new file mode 100644 index 0000000000..173d4e72fb --- /dev/null +++ b/templates/release/de/charger/alfen-eve-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-alfen +product: + identifier: alfen-eve-ocpp + brand: Alfen + description: Eve (OCPP) +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/alfen-eve.yaml b/templates/release/de/charger/alfen-eve.yaml new file mode 100644 index 0000000000..e54c4d0a05 --- /dev/null +++ b/templates/release/de/charger/alfen-eve.yaml @@ -0,0 +1,35 @@ +template: alfen +product: + identifier: alfen-eve + brand: Alfen + description: Eve +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus extern zu steuern. In den Einstellungen muss "Active Load Balancing" aktiviert und "Energy Management System" als Data Source ausgewählt werden. Es wird empfohlen "ValidityTime" (Menu "TCP/IP EMS") auf 300s einzustellen. Falls die "Double"-Box verwendet wird müssen beide Ladepunkte getrennt voneinander hinzugefügt werden. Der erste Port (oder einzelne Port) ist unter ID 1 zugänglich, der zweite unter ID 2. +render: + - default: | + type: template + template: alfen + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/alfen_0.yaml b/templates/release/de/charger/alfen_0.yaml deleted file mode 100644 index dab2234bbe..0000000000 --- a/templates/release/de/charger/alfen_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Alfen - description: Eve -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus extern zu steuern. In den Einstellungen muss "Active Load Balancing" aktiviert und "Energy Management System" als Data Source ausgewählt werden. Es wird empfohlen "ValidityTime" (Menu "TCP/IP EMS") auf 300s einzustellen. Falls die "Double"-Box verwendet wird müssen beide Ladepunkte getrennt voneinander hinzugefügt werden. Der erste Port (oder einzelne Port) ist unter ID 1 zugänglich, der zweite unter ID 2. -render: - - default: | - type: template - template: alfen - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/alpha-innotec.yaml b/templates/release/de/charger/alpha-innotec.yaml new file mode 100644 index 0000000000..f16d018d86 --- /dev/null +++ b/templates/release/de/charger/alpha-innotec.yaml @@ -0,0 +1,63 @@ +template: luxtronik +product: + identifier: alpha-innotec + brand: alpha innotec + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/alphatec-ladesaule-twin.yaml b/templates/release/de/charger/alphatec-ladesaule-twin.yaml new file mode 100644 index 0000000000..37a36d85c3 --- /dev/null +++ b/templates/release/de/charger/alphatec-ladesaule-twin.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: alphatec-ladesaule-twin + brand: Alphatec + description: Ladesäule Twin +requirements: ["sponsorship"] +description: | + Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/alphatec-wallbox-mini.yaml b/templates/release/de/charger/alphatec-wallbox-mini.yaml new file mode 100644 index 0000000000..ab7f35f86c --- /dev/null +++ b/templates/release/de/charger/alphatec-wallbox-mini.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: alphatec-wallbox-mini + brand: Alphatec + description: Wallbox Mini +requirements: ["sponsorship"] +description: | + Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/alphatec-wallbox-power.yaml b/templates/release/de/charger/alphatec-wallbox-power.yaml new file mode 100644 index 0000000000..698c648197 --- /dev/null +++ b/templates/release/de/charger/alphatec-wallbox-power.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: alphatec-wallbox-power + brand: Alphatec + description: Wallbox Power +requirements: ["sponsorship"] +description: | + Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/alphatec_0.yaml b/templates/release/de/charger/alphatec_0.yaml deleted file mode 100644 index f366788511..0000000000 --- a/templates/release/de/charger/alphatec_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Alphatec - description: Wallbox Mini -requirements: ["sponsorship"] -description: | - Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/alphatec_1.yaml b/templates/release/de/charger/alphatec_1.yaml deleted file mode 100644 index 63b255a2f7..0000000000 --- a/templates/release/de/charger/alphatec_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Alphatec - description: Wallbox Power -requirements: ["sponsorship"] -description: | - Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/alphatec_2.yaml b/templates/release/de/charger/alphatec_2.yaml deleted file mode 100644 index ac6c3362ed..0000000000 --- a/templates/release/de/charger/alphatec_2.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Alphatec - description: Ladesäule Twin -requirements: ["sponsorship"] -description: | - Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/alphatec_3.yaml b/templates/release/de/charger/alphatec_3.yaml deleted file mode 100644 index 3b9d09a6e5..0000000000 --- a/templates/release/de/charger/alphatec_3.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: LRT - description: HOME Essential+ -requirements: ["sponsorship"] -description: | - Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/amperfied-solar_0.yaml b/templates/release/de/charger/amperfied-solar_0.yaml deleted file mode 100644 index 3a2dc38062..0000000000 --- a/templates/release/de/charger/amperfied-solar_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Amperfied - description: Wallbox connect.solar -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: amperfied-solar - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/amperfied-wallbox-connect-business.yaml b/templates/release/de/charger/amperfied-wallbox-connect-business.yaml new file mode 100644 index 0000000000..9aa1661f93 --- /dev/null +++ b/templates/release/de/charger/amperfied-wallbox-connect-business.yaml @@ -0,0 +1,33 @@ +template: amperfied +product: + identifier: amperfied-wallbox-connect-business + brand: Amperfied + description: Wallbox connect.business +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: amperfied + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/amperfied-wallbox-connect-home.yaml b/templates/release/de/charger/amperfied-wallbox-connect-home.yaml new file mode 100644 index 0000000000..31f18ff3e1 --- /dev/null +++ b/templates/release/de/charger/amperfied-wallbox-connect-home.yaml @@ -0,0 +1,33 @@ +template: amperfied +product: + identifier: amperfied-wallbox-connect-home + brand: Amperfied + description: Wallbox connect.home +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: amperfied + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/amperfied-wallbox-connect-solar.yaml b/templates/release/de/charger/amperfied-wallbox-connect-solar.yaml new file mode 100644 index 0000000000..976171a73b --- /dev/null +++ b/templates/release/de/charger/amperfied-wallbox-connect-solar.yaml @@ -0,0 +1,33 @@ +template: amperfied-solar +product: + identifier: amperfied-wallbox-connect-solar + brand: Amperfied + description: Wallbox connect.solar +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: amperfied-solar + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/amperfied-wallbox-energy-control.yaml b/templates/release/de/charger/amperfied-wallbox-energy-control.yaml new file mode 100644 index 0000000000..e662f751f4 --- /dev/null +++ b/templates/release/de/charger/amperfied-wallbox-energy-control.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: amperfied-wallbox-energy-control + brand: Amperfied + description: Wallbox Energy Control +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/amperfied_0.yaml b/templates/release/de/charger/amperfied_0.yaml deleted file mode 100644 index 98a6dd4e94..0000000000 --- a/templates/release/de/charger/amperfied_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Amperfied - description: Wallbox connect.home -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: amperfied - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/amperfied_1.yaml b/templates/release/de/charger/amperfied_1.yaml deleted file mode 100644 index 630984a204..0000000000 --- a/templates/release/de/charger/amperfied_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Amperfied - description: Wallbox connect.business -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: amperfied - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/ampure-next.yaml b/templates/release/de/charger/ampure-next.yaml new file mode 100644 index 0000000000..3ad8079787 --- /dev/null +++ b/templates/release/de/charger/ampure-next.yaml @@ -0,0 +1,34 @@ +template: webasto-next +product: + identifier: ampure-next + brand: Ampure + description: NEXT +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. +render: + - default: | + type: template + template: webasto-next + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/ampure-unite.yaml b/templates/release/de/charger/ampure-unite.yaml new file mode 100644 index 0000000000..5fc3a05171 --- /dev/null +++ b/templates/release/de/charger/ampure-unite.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: ampure-unite + brand: Ampure + description: Unite +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/audi-wallbox-plus.yaml b/templates/release/de/charger/audi-wallbox-plus.yaml new file mode 100644 index 0000000000..ee49cf9af0 --- /dev/null +++ b/templates/release/de/charger/audi-wallbox-plus.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: audi-wallbox-plus + brand: Audi + description: Wallbox plus +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/audi-wallbox-pro.yaml b/templates/release/de/charger/audi-wallbox-pro.yaml new file mode 100644 index 0000000000..5556ffdc81 --- /dev/null +++ b/templates/release/de/charger/audi-wallbox-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: audi-wallbox-pro + brand: Audi + description: Wallbox pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +render: + - default: | + type: template + template: ellipro + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/autel-ac-compact.yaml b/templates/release/de/charger/autel-ac-compact.yaml new file mode 100644 index 0000000000..0fe6c585ba --- /dev/null +++ b/templates/release/de/charger/autel-ac-compact.yaml @@ -0,0 +1,94 @@ +template: ocpp-autel +product: + identifier: autel-ac-compact + brand: AUTEL + description: AC Compact +capabilities: ["mA"] +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: + * In der Autel Charge app, klicken sie auf “OCPP Server” + * Geben Sie "Custom" in das Feld ein und wählen Sie "Personalisierung" darunter + * Server-URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladegerät-ID: Leer lassen (zur Verwendung der Seriennummer) oder einen benutzerdefinierten Wert definieren, der in der Konfiguration als *stationid* wiederverwendet wird + * Autorisierungsschlüssel: leer lassen + +render: + - default: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/autel-ac-maxicharger.yaml b/templates/release/de/charger/autel-ac-maxicharger.yaml new file mode 100644 index 0000000000..ac5b6c262e --- /dev/null +++ b/templates/release/de/charger/autel-ac-maxicharger.yaml @@ -0,0 +1,94 @@ +template: ocpp-autel +product: + identifier: autel-ac-maxicharger + brand: AUTEL + description: AC MaxiCharger +capabilities: ["mA"] +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: + * In der Autel Charge app, klicken sie auf “OCPP Server” + * Geben Sie "Custom" in das Feld ein und wählen Sie "Personalisierung" darunter + * Server-URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladegerät-ID: Leer lassen (zur Verwendung der Seriennummer) oder einen benutzerdefinierten Wert definieren, der in der Konfiguration als *stationid* wiederverwendet wird + * Autorisierungsschlüssel: leer lassen + +render: + - default: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/autoaid-business-wallbox.yaml b/templates/release/de/charger/autoaid-business-wallbox.yaml new file mode 100644 index 0000000000..5c7444081f --- /dev/null +++ b/templates/release/de/charger/autoaid-business-wallbox.yaml @@ -0,0 +1,86 @@ +template: ocpp-autoaid +product: + identifier: autoaid-business-wallbox + brand: Autoaid + description: Business Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/autoaid-intelligent-wallbox.yaml b/templates/release/de/charger/autoaid-intelligent-wallbox.yaml new file mode 100644 index 0000000000..0591622ba8 --- /dev/null +++ b/templates/release/de/charger/autoaid-intelligent-wallbox.yaml @@ -0,0 +1,86 @@ +template: ocpp-autoaid +product: + identifier: autoaid-intelligent-wallbox + brand: Autoaid + description: Intelligent Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/avm-fritzdect.yaml b/templates/release/de/charger/avm-fritzdect.yaml new file mode 100644 index 0000000000..467f553919 --- /dev/null +++ b/templates/release/de/charger/avm-fritzdect.yaml @@ -0,0 +1,99 @@ +template: fritzdect +product: + identifier: avm-fritzdect + brand: AVM + description: FritzDECT + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: fritzdect + uri: https://fritz.box # URI, HTTP(S) Adresse (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: fritzdect + uri: https://fritz.box # URI, HTTP(S) Adresse (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: uri + example: + default: https://fritz.box + choice: [] + unit: + description: URI + help: HTTP(S) Adresse + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: ain + example: 307788992233 + default: + choice: [] + unit: + description: Aktoridentifikationsnummer (AIN) + help: Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/bender-cc612.yaml b/templates/release/de/charger/bender-cc612.yaml new file mode 100644 index 0000000000..f0304a76ca --- /dev/null +++ b/templates/release/de/charger/bender-cc612.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: bender-cc612 + brand: Bender + description: CC612 +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/bender-cc613.yaml b/templates/release/de/charger/bender-cc613.yaml new file mode 100644 index 0000000000..3a4642f9ae --- /dev/null +++ b/templates/release/de/charger/bender-cc613.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: bender-cc613 + brand: Bender + description: CC613 +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/bender-cc_0.yaml b/templates/release/de/charger/bender-cc_0.yaml deleted file mode 100644 index 417e1e4f47..0000000000 --- a/templates/release/de/charger/bender-cc_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ampure - description: Live -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_1.yaml b/templates/release/de/charger/bender-cc_1.yaml deleted file mode 100644 index c953ec2b7c..0000000000 --- a/templates/release/de/charger/bender-cc_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: CC612 -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_10.yaml b/templates/release/de/charger/bender-cc_10.yaml deleted file mode 100644 index bc12f6cbf6..0000000000 --- a/templates/release/de/charger/bender-cc_10.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Optec - description: Mobility One -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_11.yaml b/templates/release/de/charger/bender-cc_11.yaml deleted file mode 100644 index b134497655..0000000000 --- a/templates/release/de/charger/bender-cc_11.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Garo - description: GLB, GLB+, LS4, LS4 compact -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_12.yaml b/templates/release/de/charger/bender-cc_12.yaml deleted file mode 100644 index 17d1f30add..0000000000 --- a/templates/release/de/charger/bender-cc_12.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ensto - description: Chago Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_13.yaml b/templates/release/de/charger/bender-cc_13.yaml deleted file mode 100644 index ff9f0b1a4a..0000000000 --- a/templates/release/de/charger/bender-cc_13.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ubitricity - description: Heinz -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_14.yaml b/templates/release/de/charger/bender-cc_14.yaml deleted file mode 100644 index 8f1e781283..0000000000 --- a/templates/release/de/charger/bender-cc_14.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: CUBOS - description: C11E, C22E -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_15.yaml b/templates/release/de/charger/bender-cc_15.yaml deleted file mode 100644 index eb69b8adf4..0000000000 --- a/templates/release/de/charger/bender-cc_15.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Spelsberg - description: Wallbox Smart Pro -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_2.yaml b/templates/release/de/charger/bender-cc_2.yaml deleted file mode 100644 index a96a8bb279..0000000000 --- a/templates/release/de/charger/bender-cc_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: CC613 -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_3.yaml b/templates/release/de/charger/bender-cc_3.yaml deleted file mode 100644 index d775fa375b..0000000000 --- a/templates/release/de/charger/bender-cc_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Professional -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_4.yaml b/templates/release/de/charger/bender-cc_4.yaml deleted file mode 100644 index e6c46fb514..0000000000 --- a/templates/release/de/charger/bender-cc_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMEDIO Professional -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_5.yaml b/templates/release/de/charger/bender-cc_5.yaml deleted file mode 100644 index 2d1787be61..0000000000 --- a/templates/release/de/charger/bender-cc_5.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON ChargeControl -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_6.yaml b/templates/release/de/charger/bender-cc_6.yaml deleted file mode 100644 index 664f9d82d6..0000000000 --- a/templates/release/de/charger/bender-cc_6.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Webasto - description: Live -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_7.yaml b/templates/release/de/charger/bender-cc_7.yaml deleted file mode 100644 index 3a86e05e4e..0000000000 --- a/templates/release/de/charger/bender-cc_7.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Juice - description: Charger Me -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_8.yaml b/templates/release/de/charger/bender-cc_8.yaml deleted file mode 100644 index 4f28a641c7..0000000000 --- a/templates/release/de/charger/bender-cc_8.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: TechniSat - description: Technivolt -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-cc_9.yaml b/templates/release/de/charger/bender-cc_9.yaml deleted file mode 100644 index 3931ee6864..0000000000 --- a/templates/release/de/charger/bender-cc_9.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ebee - description: Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-icc1314.yaml b/templates/release/de/charger/bender-icc1314.yaml new file mode 100644 index 0000000000..8eb9a1bd73 --- /dev/null +++ b/templates/release/de/charger/bender-icc1314.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: bender-icc1314 + brand: Bender + description: ICC1314 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/bender-icc1324.yaml b/templates/release/de/charger/bender-icc1324.yaml new file mode 100644 index 0000000000..091f7aa4c5 --- /dev/null +++ b/templates/release/de/charger/bender-icc1324.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: bender-icc1324 + brand: Bender + description: ICC1324 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/bender-icc_0.yaml b/templates/release/de/charger/bender-icc_0.yaml deleted file mode 100644 index 190d28e58e..0000000000 --- a/templates/release/de/charger/bender-icc_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: ICC1314 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-icc_1.yaml b/templates/release/de/charger/bender-icc_1.yaml deleted file mode 100644 index 31eed15680..0000000000 --- a/templates/release/de/charger/bender-icc_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: ICC1324 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-icc_2.yaml b/templates/release/de/charger/bender-icc_2.yaml deleted file mode 100644 index 56fd24702a..0000000000 --- a/templates/release/de/charger/bender-icc_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON 4You 500 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bender-icc_3.yaml b/templates/release/de/charger/bender-icc_3.yaml deleted file mode 100644 index bbb7bf6a40..0000000000 --- a/templates/release/de/charger/bender-icc_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON 4Business 700 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/bmw-i-wallbox.yaml b/templates/release/de/charger/bmw-i-wallbox.yaml new file mode 100644 index 0000000000..f77abf8d8b --- /dev/null +++ b/templates/release/de/charger/bmw-i-wallbox.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: bmw-i-wallbox + brand: BMW + description: i Wallbox +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/bosch-sg-ready.yaml b/templates/release/de/charger/bosch-sg-ready.yaml new file mode 100644 index 0000000000..994ce5d8f4 --- /dev/null +++ b/templates/release/de/charger/bosch-sg-ready.yaml @@ -0,0 +1,53 @@ +template: emsesp +product: + identifier: bosch-sg-ready + brand: Bosch + description: SG Ready + group: Wärmeerzeuger +description: | + Eingebunden via [EMSESP](https://emsesp.org/) +render: + - default: | + type: template + template: emsesp + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # optional + powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) + tempsource: # Temperaturquelle, [warmwater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: powersource + example: + default: hpcurrpower + choice: ['hpcurrpower', 'hppower'] + unit: + description: Leistungsquelle + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/bosch-x-change.yaml b/templates/release/de/charger/bosch-x-change.yaml new file mode 100644 index 0000000000..287b92f1c4 --- /dev/null +++ b/templates/release/de/charger/bosch-x-change.yaml @@ -0,0 +1,46 @@ +template: kermi +product: + identifier: bosch-x-change + brand: Bösch + description: x-change + group: Wärmeerzeuger +render: + - default: | + type: template + template: kermi + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater, buffer] (optional) + advanced: | + type: template + template: kermi + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater, buffer] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml b/templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml new file mode 100644 index 0000000000..6cf5e1ae2e --- /dev/null +++ b/templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: buderus-logamatic-hmc-20-z + brand: Buderus + description: Logamatic HMC 20 Z + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/buderus-logamatic-hmc-20.yaml b/templates/release/de/charger/buderus-logamatic-hmc-20.yaml new file mode 100644 index 0000000000..09fc5b1f99 --- /dev/null +++ b/templates/release/de/charger/buderus-logamatic-hmc-20.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: buderus-logamatic-hmc-20 + brand: Buderus + description: Logamatic HMC 20 + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/buderus-sg-ready.yaml b/templates/release/de/charger/buderus-sg-ready.yaml new file mode 100644 index 0000000000..5d2dceb14c --- /dev/null +++ b/templates/release/de/charger/buderus-sg-ready.yaml @@ -0,0 +1,53 @@ +template: emsesp +product: + identifier: buderus-sg-ready + brand: Buderus + description: SG Ready + group: Wärmeerzeuger +description: | + Eingebunden via [EMSESP](https://emsesp.org/) +render: + - default: | + type: template + template: emsesp + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # optional + powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) + tempsource: # Temperaturquelle, [warmwater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: powersource + example: + default: hpcurrpower + choice: ['hpcurrpower', 'hppower'] + unit: + description: Leistungsquelle + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/cfos-power-brain-solar.yaml b/templates/release/de/charger/cfos-power-brain-solar.yaml new file mode 100644 index 0000000000..9fd6477e83 --- /dev/null +++ b/templates/release/de/charger/cfos-power-brain-solar.yaml @@ -0,0 +1,28 @@ +template: cfos +product: + identifier: cfos-power-brain-solar + brand: cFos + description: Power Brain Solar +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. + Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: + 1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) + 2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) + +render: + - default: | + type: template + template: cfos + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/cfos-power-brain.yaml b/templates/release/de/charger/cfos-power-brain.yaml new file mode 100644 index 0000000000..c71a98028c --- /dev/null +++ b/templates/release/de/charger/cfos-power-brain.yaml @@ -0,0 +1,28 @@ +template: cfos +product: + identifier: cfos-power-brain + brand: cFos + description: Power Brain +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. + Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: + 1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) + 2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) + +render: + - default: | + type: template + template: cfos + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/cfos_0.yaml b/templates/release/de/charger/cfos_0.yaml deleted file mode 100644 index 163f712d3e..0000000000 --- a/templates/release/de/charger/cfos_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: cFos - description: Power Brain -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. - Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: - 1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) - 2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) - -render: - - default: | - type: template - template: cfos - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/cfos_1.yaml b/templates/release/de/charger/cfos_1.yaml deleted file mode 100644 index 4f14aadc39..0000000000 --- a/templates/release/de/charger/cfos_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: cFos - description: Power Brain Solar -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. - Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: - 1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) - 2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) - -render: - - default: | - type: template - template: cfos - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/charge-amps-halo.yaml b/templates/release/de/charger/charge-amps-halo.yaml new file mode 100644 index 0000000000..a3e7810c65 --- /dev/null +++ b/templates/release/de/charger/charge-amps-halo.yaml @@ -0,0 +1,86 @@ +template: ocpp-chargeamps +product: + identifier: charge-amps-halo + brand: Charge Amps + description: Halo +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-chargeamps + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-chargeamps + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/compleo-ebox.yaml b/templates/release/de/charger/compleo-ebox.yaml new file mode 100644 index 0000000000..7f5a029899 --- /dev/null +++ b/templates/release/de/charger/compleo-ebox.yaml @@ -0,0 +1,33 @@ +template: innogy-ebox +product: + identifier: compleo-ebox + brand: Compleo + description: eBox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: innogy-ebox + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/cta-all-in-one-aeroplus.yaml b/templates/release/de/charger/cta-all-in-one-aeroplus.yaml new file mode 100644 index 0000000000..e4cc9a92fc --- /dev/null +++ b/templates/release/de/charger/cta-all-in-one-aeroplus.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: cta-all-in-one-aeroplus + brand: CTA All-In-One + description: Aeroplus + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/cubos-c11e.yaml b/templates/release/de/charger/cubos-c11e.yaml new file mode 100644 index 0000000000..5385bf6ef6 --- /dev/null +++ b/templates/release/de/charger/cubos-c11e.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: cubos-c11e + brand: CUBOS + description: C11E +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/cubos-c22e.yaml b/templates/release/de/charger/cubos-c22e.yaml new file mode 100644 index 0000000000..f013af38a8 --- /dev/null +++ b/templates/release/de/charger/cubos-c22e.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: cubos-c22e + brand: CUBOS + description: C22E +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/cupra-charger-connect-2.yaml b/templates/release/de/charger/cupra-charger-connect-2.yaml new file mode 100644 index 0000000000..af0a32d240 --- /dev/null +++ b/templates/release/de/charger/cupra-charger-connect-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: cupra-charger-connect-2 + brand: Cupra + description: Charger Connect 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/cupra-charger-connect.yaml b/templates/release/de/charger/cupra-charger-connect.yaml new file mode 100644 index 0000000000..e6c9cfd3c9 --- /dev/null +++ b/templates/release/de/charger/cupra-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: cupra-charger-connect + brand: Cupra + description: Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/cupra-charger-pro-2.yaml b/templates/release/de/charger/cupra-charger-pro-2.yaml new file mode 100644 index 0000000000..333a5b16d9 --- /dev/null +++ b/templates/release/de/charger/cupra-charger-pro-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: cupra-charger-pro-2 + brand: Cupra + description: Charger Pro 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/cupra-charger-pro-eichrecht-2.yaml b/templates/release/de/charger/cupra-charger-pro-eichrecht-2.yaml new file mode 100644 index 0000000000..b6fd01cab6 --- /dev/null +++ b/templates/release/de/charger/cupra-charger-pro-eichrecht-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: cupra-charger-pro-eichrecht-2 + brand: Cupra + description: Charger Pro Eichrecht 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/cupra-charger-pro.yaml b/templates/release/de/charger/cupra-charger-pro.yaml new file mode 100644 index 0000000000..de1c86b220 --- /dev/null +++ b/templates/release/de/charger/cupra-charger-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: cupra-charger-pro + brand: Cupra + description: Charger Pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +render: + - default: | + type: template + template: ellipro + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/dadapower-premium-wallbox.yaml b/templates/release/de/charger/dadapower-premium-wallbox.yaml new file mode 100644 index 0000000000..8774b672ed --- /dev/null +++ b/templates/release/de/charger/dadapower-premium-wallbox.yaml @@ -0,0 +1,33 @@ +template: dadapower +product: + identifier: dadapower-premium-wallbox + brand: Dadapower + description: Premium Wallbox +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: dadapower + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/dadapower_0.yaml b/templates/release/de/charger/dadapower_0.yaml deleted file mode 100644 index 7a916c80ea..0000000000 --- a/templates/release/de/charger/dadapower_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Dadapower - description: Premium Wallbox -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: dadapower - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/daheimladen-mb_0.yaml b/templates/release/de/charger/daheimladen-mb_0.yaml deleted file mode 100644 index 6704210356..0000000000 --- a/templates/release/de/charger/daheimladen-mb_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: DaheimLaden - description: Wallbox -description: | - Die Wallbox muss über eine aktuelle Firmware mit Modbus-Unterstützung verfügen. In den Einstellungen muss "Nachladen" (Smart) bzw. "RSDA" (Touch) aktiviert sein -render: - - default: | - type: template - template: daheimladen-mb - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional diff --git a/templates/release/de/charger/daheimladen-wallbox.yaml b/templates/release/de/charger/daheimladen-wallbox.yaml new file mode 100644 index 0000000000..753c0e884b --- /dev/null +++ b/templates/release/de/charger/daheimladen-wallbox.yaml @@ -0,0 +1,32 @@ +template: daheimladen-mb +product: + identifier: daheimladen-wallbox + brand: DaheimLaden + description: Wallbox +description: | + Die Wallbox muss über eine aktuelle Firmware mit Modbus-Unterstützung verfügen. In den Einstellungen muss "Nachladen" (Smart) bzw. "RSDA" (Touch) aktiviert sein +render: + - default: | + type: template + template: daheimladen-mb + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/daikin-homehub-sg-ready.yaml b/templates/release/de/charger/daikin-homehub-sg-ready.yaml new file mode 100644 index 0000000000..1c9b1fa49d --- /dev/null +++ b/templates/release/de/charger/daikin-homehub-sg-ready.yaml @@ -0,0 +1,42 @@ +template: daikin-homehub +product: + identifier: daikin-homehub-sg-ready + brand: Daikin + description: HomeHub (SG Ready) + group: Wärmeerzeuger +render: + - default: | + type: template + template: daikin-homehub + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperaturquelle, [warmwater, buffer] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/daikin-homehub_0.yaml b/templates/release/de/charger/daikin-homehub_0.yaml deleted file mode 100644 index 94e598bf3d..0000000000 --- a/templates/release/de/charger/daikin-homehub_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Daikin - description: HomeHub (SG Ready) - group: Wärmeerzeuger -render: - - default: | - type: template - template: daikin-homehub - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperaturquelle, [warmwater, buffer] (optional) diff --git a/templates/release/de/charger/delta-ac-max-basic.yaml b/templates/release/de/charger/delta-ac-max-basic.yaml new file mode 100644 index 0000000000..d9a320d592 --- /dev/null +++ b/templates/release/de/charger/delta-ac-max-basic.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-ac-max-basic + brand: Delta + description: AC Max Basic +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/delta-ac-max-smart.yaml b/templates/release/de/charger/delta-ac-max-smart.yaml new file mode 100644 index 0000000000..3e0118be87 --- /dev/null +++ b/templates/release/de/charger/delta-ac-max-smart.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-ac-max-smart + brand: Delta + description: AC MAX Smart +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/delta-slim-charger.yaml b/templates/release/de/charger/delta-slim-charger.yaml new file mode 100644 index 0000000000..ad0564c181 --- /dev/null +++ b/templates/release/de/charger/delta-slim-charger.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-slim-charger + brand: Delta + description: SLIM Charger +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/delta-ultra-fast-charger.yaml b/templates/release/de/charger/delta-ultra-fast-charger.yaml new file mode 100644 index 0000000000..1d195f6d7e --- /dev/null +++ b/templates/release/de/charger/delta-ultra-fast-charger.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-ultra-fast-charger + brand: Delta + description: Ultra Fast Charger +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/delta_0.yaml b/templates/release/de/charger/delta_0.yaml deleted file mode 100644 index 03b583921f..0000000000 --- a/templates/release/de/charger/delta_0.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: AC Max Basic -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/delta_1.yaml b/templates/release/de/charger/delta_1.yaml deleted file mode 100644 index d1e9371bf7..0000000000 --- a/templates/release/de/charger/delta_1.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: AC MAX Smart -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/delta_2.yaml b/templates/release/de/charger/delta_2.yaml deleted file mode 100644 index 87a93af3d6..0000000000 --- a/templates/release/de/charger/delta_2.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: SLIM Charger -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/delta_3.yaml b/templates/release/de/charger/delta_3.yaml deleted file mode 100644 index effcd7f087..0000000000 --- a/templates/release/de/charger/delta_3.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: Ultra Fast Charger -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/demo-charger.yaml b/templates/release/de/charger/demo-charger.yaml new file mode 100644 index 0000000000..3bc95d1c81 --- /dev/null +++ b/templates/release/de/charger/demo-charger.yaml @@ -0,0 +1,68 @@ +template: demo-charger +product: + identifier: demo-charger + description: Demowallbox + group: Generische Unterstützung +description: | + Zu Demonstrationszwecken. Wallbox mit festen Werten. +render: + - default: | + type: template + template: demo-charger + status: A # Ladezustand, [A, B, C] + power: 0 # Leistung, optional + enabled: true # Ladebereit, optional + advanced: | + type: template + template: demo-charger + status: A # Ladezustand, [A, B, C] + power: 0 # Leistung, optional + enabled: true # Ladebereit, optional + maxcurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + phases1p3p: false # Phasenumschaltung, optional +params: + - name: status + example: + default: A + choice: ['A', 'B', 'C'] + unit: + description: Ladezustand + help: + advanced: false + optional: false + - name: power + example: + default: 0 + choice: [] + unit: + description: Leistung + help: + advanced: false + optional: true + - name: enabled + example: + default: true + choice: [] + unit: + description: Ladebereit + help: + advanced: false + optional: true + - name: maxcurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: Phasenumschaltung + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/demo-charger_0.yaml b/templates/release/de/charger/demo-charger_0.yaml deleted file mode 100644 index b72e91f488..0000000000 --- a/templates/release/de/charger/demo-charger_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - description: Demowallbox - group: Generische Unterstützung -description: | - Zu Demonstrationszwecken. Wallbox mit festen Werten. -render: - - default: | - type: template - template: demo-charger - status: A # Ladezustand, [A, B, C] - power: 0 # Leistung, optional - enabled: true # Ladebereit, optional - advanced: | - type: template - template: demo-charger - status: A # Ladezustand, [A, B, C] - power: 0 # Leistung, optional - enabled: true # Ladebereit, optional - maxcurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - phases1p3p: false # Phasenumschaltung, optional diff --git a/templates/release/de/charger/e-on-drive-ebox.yaml b/templates/release/de/charger/e-on-drive-ebox.yaml new file mode 100644 index 0000000000..932f0f1f8c --- /dev/null +++ b/templates/release/de/charger/e-on-drive-ebox.yaml @@ -0,0 +1,33 @@ +template: innogy-ebox +product: + identifier: e-on-drive-ebox + brand: E.ON Drive + description: eBox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: innogy-ebox + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/e-on-drive-vbox.yaml b/templates/release/de/charger/e-on-drive-vbox.yaml new file mode 100644 index 0000000000..0274136030 --- /dev/null +++ b/templates/release/de/charger/e-on-drive-vbox.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: e-on-drive-vbox + brand: E.ON Drive + description: vBox +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/e3-dc-easy-connect.yaml b/templates/release/de/charger/e3-dc-easy-connect.yaml new file mode 100644 index 0000000000..27587a0abf --- /dev/null +++ b/templates/release/de/charger/e3-dc-easy-connect.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: e3-dc-easy-connect + brand: E3/DC + description: Easy Connect +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/easee-charge-core.yaml b/templates/release/de/charger/easee-charge-core.yaml new file mode 100644 index 0000000000..cf8be6d548 --- /dev/null +++ b/templates/release/de/charger/easee-charge-core.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-charge-core + brand: Easee + description: Charge Core +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Benutzerkonto, Emailadresse + password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) + authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Emailadresse + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: wie Login für Easee App oder Web Portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Zeitüberschreitung + help: Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/easee-charge-lite.yaml b/templates/release/de/charger/easee-charge-lite.yaml new file mode 100644 index 0000000000..5dee53c0d6 --- /dev/null +++ b/templates/release/de/charger/easee-charge-lite.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-charge-lite + brand: Easee + description: Charge Lite +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Benutzerkonto, Emailadresse + password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) + authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Emailadresse + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: wie Login für Easee App oder Web Portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Zeitüberschreitung + help: Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/easee-charge.yaml b/templates/release/de/charger/easee-charge.yaml new file mode 100644 index 0000000000..74fd3a0f57 --- /dev/null +++ b/templates/release/de/charger/easee-charge.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-charge + brand: Easee + description: Charge +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Benutzerkonto, Emailadresse + password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) + authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Emailadresse + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: wie Login für Easee App oder Web Portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Zeitüberschreitung + help: Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/easee-home.yaml b/templates/release/de/charger/easee-home.yaml new file mode 100644 index 0000000000..f5effefe3e --- /dev/null +++ b/templates/release/de/charger/easee-home.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-home + brand: Easee + description: Home +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Benutzerkonto, Emailadresse + password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) + authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Emailadresse + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: wie Login für Easee App oder Web Portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Zeitüberschreitung + help: Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/easee_0.yaml b/templates/release/de/charger/easee_0.yaml deleted file mode 100644 index 8144e12715..0000000000 --- a/templates/release/de/charger/easee_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Home -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Benutzerkonto, Emailadresse - password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) diff --git a/templates/release/de/charger/easee_1.yaml b/templates/release/de/charger/easee_1.yaml deleted file mode 100644 index e1ca34184d..0000000000 --- a/templates/release/de/charger/easee_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Charge -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Benutzerkonto, Emailadresse - password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) diff --git a/templates/release/de/charger/easee_2.yaml b/templates/release/de/charger/easee_2.yaml deleted file mode 100644 index 75a9cb6436..0000000000 --- a/templates/release/de/charger/easee_2.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Charge Lite -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Benutzerkonto, Emailadresse - password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) diff --git a/templates/release/de/charger/easee_3.yaml b/templates/release/de/charger/easee_3.yaml deleted file mode 100644 index 6db44a18fd..0000000000 --- a/templates/release/de/charger/easee_3.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Charge Core -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Benutzerkonto, Emailadresse - password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) diff --git a/templates/release/de/charger/ebee-wallbox.yaml b/templates/release/de/charger/ebee-wallbox.yaml new file mode 100644 index 0000000000..75fb55c6a5 --- /dev/null +++ b/templates/release/de/charger/ebee-wallbox.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: ebee-wallbox + brand: Ebee + description: Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/echarge-cph1.yaml b/templates/release/de/charger/echarge-cph1.yaml new file mode 100644 index 0000000000..4797ef67db --- /dev/null +++ b/templates/release/de/charger/echarge-cph1.yaml @@ -0,0 +1,37 @@ +template: hardybarth-ecb1 +product: + identifier: echarge-cph1 + brand: echarge + description: cPH1 +requirements: ["sponsorship"] +description: | + Als Betriebsmodus muss `manual` ausgewählt sein +render: + - default: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP-Adresse oder Hostname + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/echarge-cph2.yaml b/templates/release/de/charger/echarge-cph2.yaml new file mode 100644 index 0000000000..ee0c716928 --- /dev/null +++ b/templates/release/de/charger/echarge-cph2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: echarge-cph2 + brand: echarge + description: cPH2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/echarge-cpm2.yaml b/templates/release/de/charger/echarge-cpm2.yaml new file mode 100644 index 0000000000..51f9266748 --- /dev/null +++ b/templates/release/de/charger/echarge-cpm2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: echarge-cpm2 + brand: echarge + description: cPμ2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml b/templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml new file mode 100644 index 0000000000..d648bddcec --- /dev/null +++ b/templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml @@ -0,0 +1,48 @@ +template: obo +product: + identifier: ecoharmony-evse-epc-2-0-plus + brand: EcoHarmony + description: EVSE EPC 2.0 Plus +render: + - default: | + type: template + template: obo + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 101 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 101 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/edgetech-smart-evse.yaml b/templates/release/de/charger/edgetech-smart-evse.yaml new file mode 100644 index 0000000000..c34cb02e76 --- /dev/null +++ b/templates/release/de/charger/edgetech-smart-evse.yaml @@ -0,0 +1,42 @@ +template: smartevse +product: + identifier: edgetech-smart-evse + brand: Edgetech + description: Smart EVSE +capabilities: ["1p3p"] +render: + - default: | + type: template + template: smartevse + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/eebus-compatible.yaml b/templates/release/de/charger/eebus-compatible.yaml new file mode 100644 index 0000000000..5e5fbae4b4 --- /dev/null +++ b/templates/release/de/charger/eebus-compatible.yaml @@ -0,0 +1,32 @@ +template: eebus +product: + identifier: eebus-compatible + description: EEBUS kompatibel + group: Generische Unterstützung +capabilities: ["mA"] +requirements: ["eebus"] +render: + - default: | + type: template + template: eebus + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/eebus_0.yaml b/templates/release/de/charger/eebus_0.yaml deleted file mode 100644 index 7417b1acd5..0000000000 --- a/templates/release/de/charger/eebus_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - description: EEBUS kompatibel - group: Generische Unterstützung -capabilities: ["mA"] -requirements: ["eebus"] -render: - - default: | - type: template - template: eebus - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elco.yaml b/templates/release/de/charger/elco.yaml new file mode 100644 index 0000000000..444c4c2cb8 --- /dev/null +++ b/templates/release/de/charger/elco.yaml @@ -0,0 +1,63 @@ +template: luxtronik +product: + identifier: elco + brand: Elco + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/elecq-biz.yaml b/templates/release/de/charger/elecq-biz.yaml new file mode 100644 index 0000000000..3f6374d69c --- /dev/null +++ b/templates/release/de/charger/elecq-biz.yaml @@ -0,0 +1,85 @@ +template: ocpp-elecq +product: + identifier: elecq-biz + brand: Elecq + description: Biz +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elecq-home.yaml b/templates/release/de/charger/elecq-home.yaml new file mode 100644 index 0000000000..7d0758639e --- /dev/null +++ b/templates/release/de/charger/elecq-home.yaml @@ -0,0 +1,85 @@ +template: ocpp-elecq +product: + identifier: elecq-home + brand: Elecq + description: Home +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elecq-station.yaml b/templates/release/de/charger/elecq-station.yaml new file mode 100644 index 0000000000..1f457969c3 --- /dev/null +++ b/templates/release/de/charger/elecq-station.yaml @@ -0,0 +1,85 @@ +template: ocpp-elecq +product: + identifier: elecq-station + brand: Elecq + description: Station +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/eledio-go.yaml b/templates/release/de/charger/eledio-go.yaml new file mode 100644 index 0000000000..c4228fe64c --- /dev/null +++ b/templates/release/de/charger/eledio-go.yaml @@ -0,0 +1,89 @@ +template: ocpp-enercab +product: + identifier: eledio-go + brand: eledio + description: go +capabilities: ["1p3p"] +requirements: ["sponsorship", "skiptest"] +description: | + https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + +render: + - default: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elli-2_0.yaml b/templates/release/de/charger/elli-2_0.yaml deleted file mode 100644 index 9474c19547..0000000000 --- a/templates/release/de/charger/elli-2_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Connect 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_1.yaml b/templates/release/de/charger/elli-2_1.yaml deleted file mode 100644 index 1c57637857..0000000000 --- a/templates/release/de/charger/elli-2_1.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Pro 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_10.yaml b/templates/release/de/charger/elli-2_10.yaml deleted file mode 100644 index d632dcffdf..0000000000 --- a/templates/release/de/charger/elli-2_10.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Pro 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_11.yaml b/templates/release/de/charger/elli-2_11.yaml deleted file mode 100644 index 3c8f2210a5..0000000000 --- a/templates/release/de/charger/elli-2_11.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Pro Eichrecht 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_2.yaml b/templates/release/de/charger/elli-2_2.yaml deleted file mode 100644 index c38f27a64c..0000000000 --- a/templates/release/de/charger/elli-2_2.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Pro Eichrecht 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_3.yaml b/templates/release/de/charger/elli-2_3.yaml deleted file mode 100644 index 070b64b6ff..0000000000 --- a/templates/release/de/charger/elli-2_3.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: Charger Connect 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_4.yaml b/templates/release/de/charger/elli-2_4.yaml deleted file mode 100644 index c5b447e8fd..0000000000 --- a/templates/release/de/charger/elli-2_4.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: Charger Pro 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_5.yaml b/templates/release/de/charger/elli-2_5.yaml deleted file mode 100644 index 2e832b39d2..0000000000 --- a/templates/release/de/charger/elli-2_5.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: Charger Pro Eichrecht 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_6.yaml b/templates/release/de/charger/elli-2_6.yaml deleted file mode 100644 index f4dc95e580..0000000000 --- a/templates/release/de/charger/elli-2_6.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: Charger Connect -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_7.yaml b/templates/release/de/charger/elli-2_7.yaml deleted file mode 100644 index 42d3662327..0000000000 --- a/templates/release/de/charger/elli-2_7.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: Charger Pro -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_8.yaml b/templates/release/de/charger/elli-2_8.yaml deleted file mode 100644 index d17fc70233..0000000000 --- a/templates/release/de/charger/elli-2_8.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: Charger Pro Eichrecht -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-2_9.yaml b/templates/release/de/charger/elli-2_9.yaml deleted file mode 100644 index 78ced4df6d..0000000000 --- a/templates/release/de/charger/elli-2_9.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Connect 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: elli-2 - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elli-charger-connect-2.yaml b/templates/release/de/charger/elli-charger-connect-2.yaml new file mode 100644 index 0000000000..60a699e2ae --- /dev/null +++ b/templates/release/de/charger/elli-charger-connect-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: elli-charger-connect-2 + brand: Elli + description: Charger Connect 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elli-charger-connect.yaml b/templates/release/de/charger/elli-charger-connect.yaml new file mode 100644 index 0000000000..00048ac154 --- /dev/null +++ b/templates/release/de/charger/elli-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: elli-charger-connect + brand: Elli + description: Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elli-charger-pro-2.yaml b/templates/release/de/charger/elli-charger-pro-2.yaml new file mode 100644 index 0000000000..cc93424de3 --- /dev/null +++ b/templates/release/de/charger/elli-charger-pro-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: elli-charger-pro-2 + brand: Elli + description: Charger Pro 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elli-charger-pro-eichrecht-2.yaml b/templates/release/de/charger/elli-charger-pro-eichrecht-2.yaml new file mode 100644 index 0000000000..753595136c --- /dev/null +++ b/templates/release/de/charger/elli-charger-pro-eichrecht-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: elli-charger-pro-eichrecht-2 + brand: Elli + description: Charger Pro Eichrecht 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elli-charger-pro.yaml b/templates/release/de/charger/elli-charger-pro.yaml new file mode 100644 index 0000000000..e7c01f0baf --- /dev/null +++ b/templates/release/de/charger/elli-charger-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: elli-charger-pro + brand: Elli + description: Charger Pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +render: + - default: | + type: template + template: ellipro + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elliconnect_0.yaml b/templates/release/de/charger/elliconnect_0.yaml deleted file mode 100644 index 4595516d73..0000000000 --- a/templates/release/de/charger/elliconnect_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Elli - description: Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - - Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elliconnect_1.yaml b/templates/release/de/charger/elliconnect_1.yaml deleted file mode 100644 index fa6aa49bac..0000000000 --- a/templates/release/de/charger/elliconnect_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Volkswagen - description: ID. Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - - Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elliconnect_2.yaml b/templates/release/de/charger/elliconnect_2.yaml deleted file mode 100644 index 055b735acf..0000000000 --- a/templates/release/de/charger/elliconnect_2.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Skoda - description: iV Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - - Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elliconnect_3.yaml b/templates/release/de/charger/elliconnect_3.yaml deleted file mode 100644 index ee4fa3488d..0000000000 --- a/templates/release/de/charger/elliconnect_3.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Cupra - description: Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - - Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/elliconnect_4.yaml b/templates/release/de/charger/elliconnect_4.yaml deleted file mode 100644 index c045860b2a..0000000000 --- a/templates/release/de/charger/elliconnect_4.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Audi - description: Wallbox plus -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - - Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/ellipro_0.yaml b/templates/release/de/charger/ellipro_0.yaml deleted file mode 100644 index b426e7a0e7..0000000000 --- a/templates/release/de/charger/ellipro_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - -render: - - default: | - type: template - template: ellipro - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/ellipro_1.yaml b/templates/release/de/charger/ellipro_1.yaml deleted file mode 100644 index 95cdf8440c..0000000000 --- a/templates/release/de/charger/ellipro_1.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: ID. Charger Pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - -render: - - default: | - type: template - template: ellipro - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/ellipro_2.yaml b/templates/release/de/charger/ellipro_2.yaml deleted file mode 100644 index e1ae3bcb13..0000000000 --- a/templates/release/de/charger/ellipro_2.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: iV Charger Connect+ -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - -render: - - default: | - type: template - template: ellipro - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/ellipro_3.yaml b/templates/release/de/charger/ellipro_3.yaml deleted file mode 100644 index e130bcc8cf..0000000000 --- a/templates/release/de/charger/ellipro_3.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - -render: - - default: | - type: template - template: ellipro - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/ellipro_4.yaml b/templates/release/de/charger/ellipro_4.yaml deleted file mode 100644 index 97ea9872ed..0000000000 --- a/templates/release/de/charger/ellipro_4.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Audi - description: Wallbox pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - - Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. - -render: - - default: | - type: template - template: ellipro - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/em2go-home.yaml b/templates/release/de/charger/em2go-home.yaml new file mode 100644 index 0000000000..9e5e4eba7b --- /dev/null +++ b/templates/release/de/charger/em2go-home.yaml @@ -0,0 +1,23 @@ +template: em2go-home +product: + identifier: em2go-home + brand: EM2GO + description: Home +capabilities: ["1p3p", "mA"] +description: | + Benötigt FW version >= E3C_V1.1. mA Regelung benötigt FW version >= E3C_V1.3. +render: + - default: | + type: template + template: em2go-home + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/em2go-home_0.yaml b/templates/release/de/charger/em2go-home_0.yaml deleted file mode 100644 index 7edf8d42ec..0000000000 --- a/templates/release/de/charger/em2go-home_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: EM2GO - description: Home -capabilities: ["1p3p", "mA"] -description: | - Benötigt FW version >= E3C_V1.1. mA Regelung benötigt FW version >= E3C_V1.3. -render: - - default: | - type: template - template: em2go-home - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml b/templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml new file mode 100644 index 0000000000..c54734b7d4 --- /dev/null +++ b/templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml @@ -0,0 +1,34 @@ +template: em2go +product: + identifier: em2go-pro-power-ocpp-onc + brand: EM2GO + description: Pro Power (OCPP/ONC) +capabilities: ["mA"] +description: | + Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP/ONC: 3.15) +render: + - default: | + type: template + template: em2go + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/em2go_0.yaml b/templates/release/de/charger/em2go_0.yaml deleted file mode 100644 index b49c408d62..0000000000 --- a/templates/release/de/charger/em2go_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: EM2GO - description: Pro Power (OCPP/ONC) -capabilities: ["mA"] -description: | - Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP/ONC: 3.15) -render: - - default: | - type: template - template: em2go - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/emsesp_0.yaml b/templates/release/de/charger/emsesp_0.yaml deleted file mode 100644 index f3cc2a544e..0000000000 --- a/templates/release/de/charger/emsesp_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Buderus - description: SG Ready - group: Wärmeerzeuger -description: | - Eingebunden via [EMSESP](https://emsesp.org/) -render: - - default: | - type: template - template: emsesp - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional - powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) - tempsource: # Temperaturquelle, [warmwater] (optional) diff --git a/templates/release/de/charger/emsesp_1.yaml b/templates/release/de/charger/emsesp_1.yaml deleted file mode 100644 index 9d40022abb..0000000000 --- a/templates/release/de/charger/emsesp_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Bosch - description: SG Ready - group: Wärmeerzeuger -description: | - Eingebunden via [EMSESP](https://emsesp.org/) -render: - - default: | - type: template - template: emsesp - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional - powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) - tempsource: # Temperaturquelle, [warmwater] (optional) diff --git a/templates/release/de/charger/emsesp_2.yaml b/templates/release/de/charger/emsesp_2.yaml deleted file mode 100644 index cc082e51ae..0000000000 --- a/templates/release/de/charger/emsesp_2.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Junkers - description: SG Ready - group: Wärmeerzeuger -description: | - Eingebunden via [EMSESP](https://emsesp.org/) -render: - - default: | - type: template - template: emsesp - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional - powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) - tempsource: # Temperaturquelle, [warmwater] (optional) diff --git a/templates/release/de/charger/enercab-smart.yaml b/templates/release/de/charger/enercab-smart.yaml new file mode 100644 index 0000000000..fe17dd8dbf --- /dev/null +++ b/templates/release/de/charger/enercab-smart.yaml @@ -0,0 +1,89 @@ +template: ocpp-enercab +product: + identifier: enercab-smart + brand: enercab + description: smart +capabilities: ["1p3p"] +requirements: ["sponsorship", "skiptest"] +description: | + https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + +render: + - default: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/enplus-ac-ev-charger.yaml b/templates/release/de/charger/enplus-ac-ev-charger.yaml new file mode 100644 index 0000000000..9081985c40 --- /dev/null +++ b/templates/release/de/charger/enplus-ac-ev-charger.yaml @@ -0,0 +1,86 @@ +template: ocpp-enplus +product: + identifier: enplus-ac-ev-charger + brand: EN+ + description: AC EV Charger +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/ensto-chago-wallbox.yaml b/templates/release/de/charger/ensto-chago-wallbox.yaml new file mode 100644 index 0000000000..8a1f54f289 --- /dev/null +++ b/templates/release/de/charger/ensto-chago-wallbox.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: ensto-chago-wallbox + brand: Ensto + description: Chago Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/entratek-power-dot-fix.yaml b/templates/release/de/charger/entratek-power-dot-fix.yaml new file mode 100644 index 0000000000..f39b93530f --- /dev/null +++ b/templates/release/de/charger/entratek-power-dot-fix.yaml @@ -0,0 +1,86 @@ +template: ocpp-entratek +product: + identifier: entratek-power-dot-fix + brand: EntraTek + description: Power Dot Fix +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/entratek-power-dot-pro-2.yaml b/templates/release/de/charger/entratek-power-dot-pro-2.yaml new file mode 100644 index 0000000000..9fdf5c0145 --- /dev/null +++ b/templates/release/de/charger/entratek-power-dot-pro-2.yaml @@ -0,0 +1,86 @@ +template: ocpp-entratek +product: + identifier: entratek-power-dot-pro-2 + brand: EntraTek + description: Power Dot Pro 2 +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/eprowallbox_0.yaml b/templates/release/de/charger/eprowallbox_0.yaml deleted file mode 100644 index 9f74cf8d50..0000000000 --- a/templates/release/de/charger/eprowallbox_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: Free2Move - description: eProWallbox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: eprowallbox - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/esl-walli-light.yaml b/templates/release/de/charger/esl-walli-light.yaml new file mode 100644 index 0000000000..1740917849 --- /dev/null +++ b/templates/release/de/charger/esl-walli-light.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: esl-walli-light + brand: ESL + description: Walli LIGHT +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/esystems-ghostone.yaml b/templates/release/de/charger/esystems-ghostone.yaml new file mode 100644 index 0000000000..99625d502a --- /dev/null +++ b/templates/release/de/charger/esystems-ghostone.yaml @@ -0,0 +1,39 @@ +template: ghost +product: + identifier: esystems-ghostone + brand: eSystems + description: ghostONE +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: ghost + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/etrel-duo_0.yaml b/templates/release/de/charger/etrel-duo_0.yaml deleted file mode 100644 index f46fb2c3e4..0000000000 --- a/templates/release/de/charger/etrel-duo_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Etrel - description: INCH Duo -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss sich im "Power" Modus befinden. -render: - - default: | - type: template - template: etrel-duo - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: etrel-duo - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/etrel-inch-duo.yaml b/templates/release/de/charger/etrel-inch-duo.yaml new file mode 100644 index 0000000000..f4dba34512 --- /dev/null +++ b/templates/release/de/charger/etrel-inch-duo.yaml @@ -0,0 +1,49 @@ +template: etrel-duo +product: + identifier: etrel-inch-duo + brand: Etrel + description: INCH Duo +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss sich im "Power" Modus befinden. +render: + - default: | + type: template + template: etrel-duo + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: etrel-duo + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/etrel-inch.yaml b/templates/release/de/charger/etrel-inch.yaml new file mode 100644 index 0000000000..9dcb739e36 --- /dev/null +++ b/templates/release/de/charger/etrel-inch.yaml @@ -0,0 +1,34 @@ +template: etrel +product: + identifier: etrel-inch + brand: Etrel + description: INCH +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss sich im "Power" Modus befinden. +render: + - default: | + type: template + template: etrel + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/etrel_0.yaml b/templates/release/de/charger/etrel_0.yaml deleted file mode 100644 index 408ee7eb44..0000000000 --- a/templates/release/de/charger/etrel_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Etrel - description: INCH -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss sich im "Power" Modus befinden. -render: - - default: | - type: template - template: etrel - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional diff --git a/templates/release/de/charger/etrel_1.yaml b/templates/release/de/charger/etrel_1.yaml deleted file mode 100644 index bba25c0e48..0000000000 --- a/templates/release/de/charger/etrel_1.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Sonnen - description: sonnenCharger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss sich im "Power" Modus befinden. -render: - - default: | - type: template - template: etrel - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional diff --git a/templates/release/de/charger/evbox-elvi.yaml b/templates/release/de/charger/evbox-elvi.yaml new file mode 100644 index 0000000000..1dd629924a --- /dev/null +++ b/templates/release/de/charger/evbox-elvi.yaml @@ -0,0 +1,86 @@ +template: ocpp-evbox-elvi +product: + identifier: evbox-elvi + brand: EVBox + description: Elvi +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-evbox-elvi + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # optional + advanced: | + type: template + template: ocpp-evbox-elvi + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # optional + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: meter + example: + default: true + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/evbox-livo.yaml b/templates/release/de/charger/evbox-livo.yaml new file mode 100644 index 0000000000..3ca4c701f6 --- /dev/null +++ b/templates/release/de/charger/evbox-livo.yaml @@ -0,0 +1,33 @@ +template: livo +product: + identifier: evbox-livo + brand: EVBox + description: Livo +requirements: ["eebus"] +description: | + Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzurichten. Danach erkennt das Ladegerät evcc als HEMS-Gerät im Netzwerk. Verwende das Installationstool, um evcc als HEMS auszuwählen. Kopiere anschließend den angegebenen SKI aus der Installations-App und fügen ihn zu Ihrem YAML hinzu. +render: + - default: | + type: template + template: livo + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/evse-din.yaml b/templates/release/de/charger/evse-din.yaml new file mode 100644 index 0000000000..782107d0b0 --- /dev/null +++ b/templates/release/de/charger/evse-din.yaml @@ -0,0 +1,40 @@ +template: evse-din +product: + identifier: evse-din + description: EVSE DIN +render: + - default: | + type: template + template: evse-din + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/evse-din_0.yaml b/templates/release/de/charger/evse-din_0.yaml deleted file mode 100644 index 4f2a93b261..0000000000 --- a/templates/release/de/charger/evse-din_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Stark in Strom - description: Easy -render: - - default: | - type: template - template: evse-din - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/evse-din_1.yaml b/templates/release/de/charger/evse-din_1.yaml deleted file mode 100644 index caf6f20729..0000000000 --- a/templates/release/de/charger/evse-din_1.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - description: EVSE DIN -render: - - default: | - type: template - template: evse-din - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/evse-wifi.yaml b/templates/release/de/charger/evse-wifi.yaml new file mode 100644 index 0000000000..4a931562ca --- /dev/null +++ b/templates/release/de/charger/evse-wifi.yaml @@ -0,0 +1,19 @@ +template: evsewifi +product: + identifier: evse-wifi + description: EVSE-WiFi +render: + - default: | + type: template + template: evsewifi + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/evsewifi_0.yaml b/templates/release/de/charger/evsewifi_0.yaml deleted file mode 100644 index 33c11648df..0000000000 --- a/templates/release/de/charger/evsewifi_0.yaml +++ /dev/null @@ -1,7 +0,0 @@ -product: - description: EVSE-WiFi -render: - - default: | - type: template - template: evsewifi - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/free2move-eprowallbox-move.yaml b/templates/release/de/charger/free2move-eprowallbox-move.yaml new file mode 100644 index 0000000000..1e8b314567 --- /dev/null +++ b/templates/release/de/charger/free2move-eprowallbox-move.yaml @@ -0,0 +1,43 @@ +template: eprowallbox +product: + identifier: free2move-eprowallbox-move + brand: Free2Move + description: eProWallbox Move +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: eprowallbox + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/free2move-eprowallbox.yaml b/templates/release/de/charger/free2move-eprowallbox.yaml new file mode 100644 index 0000000000..095c5fd108 --- /dev/null +++ b/templates/release/de/charger/free2move-eprowallbox.yaml @@ -0,0 +1,43 @@ +template: eprowallbox +product: + identifier: free2move-eprowallbox + brand: Free2Move + description: eProWallbox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: eprowallbox + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/free2move-esolutions-eprowallbox.yaml b/templates/release/de/charger/free2move-esolutions-eprowallbox.yaml new file mode 100644 index 0000000000..9fea841975 --- /dev/null +++ b/templates/release/de/charger/free2move-esolutions-eprowallbox.yaml @@ -0,0 +1,86 @@ +template: ocpp-esolutions +product: + identifier: free2move-esolutions-eprowallbox + brand: Free2move eSolutions + description: eProWallbox +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-esolutions + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-esolutions + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/fritzdect_0.yaml b/templates/release/de/charger/fritzdect_0.yaml deleted file mode 100644 index 247dfd7c6d..0000000000 --- a/templates/release/de/charger/fritzdect_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: AVM - description: FritzDECT - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: fritzdect - uri: https://fritz.box # URI, HTTP(S) Adresse (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: fritzdect - uri: https://fritz.box # URI, HTTP(S) Adresse (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/fronius-wattpilot-ocpp.yaml b/templates/release/de/charger/fronius-wattpilot-ocpp.yaml new file mode 100644 index 0000000000..5d6fb3269f --- /dev/null +++ b/templates/release/de/charger/fronius-wattpilot-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: fronius-wattpilot-ocpp + brand: Fronius + description: Wattpilot (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/garo-glb.yaml b/templates/release/de/charger/garo-glb.yaml new file mode 100644 index 0000000000..938216481a --- /dev/null +++ b/templates/release/de/charger/garo-glb.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-glb + brand: Garo + description: GLB +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/garo-glbplus.yaml b/templates/release/de/charger/garo-glbplus.yaml new file mode 100644 index 0000000000..ff88b3dc4d --- /dev/null +++ b/templates/release/de/charger/garo-glbplus.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-glbplus + brand: Garo + description: GLB+ +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/garo-ls4-compact.yaml b/templates/release/de/charger/garo-ls4-compact.yaml new file mode 100644 index 0000000000..811930c681 --- /dev/null +++ b/templates/release/de/charger/garo-ls4-compact.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-ls4-compact + brand: Garo + description: LS4 compact +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/garo-ls4.yaml b/templates/release/de/charger/garo-ls4.yaml new file mode 100644 index 0000000000..3fe2f24b1c --- /dev/null +++ b/templates/release/de/charger/garo-ls4.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-ls4 + brand: Garo + description: LS4 +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/ghost_0.yaml b/templates/release/de/charger/ghost_0.yaml deleted file mode 100644 index c8b4b1b7c6..0000000000 --- a/templates/release/de/charger/ghost_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: eSystems - description: ghostONE -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: ghost - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/ghost_1.yaml b/templates/release/de/charger/ghost_1.yaml deleted file mode 100644 index 60e62580dd..0000000000 --- a/templates/release/de/charger/ghost_1.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Kontron Solar - description: Charger -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: ghost - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/go-e-charger-gemini-ocpp.yaml b/templates/release/de/charger/go-e-charger-gemini-ocpp.yaml new file mode 100644 index 0000000000..8de4b0744c --- /dev/null +++ b/templates/release/de/charger/go-e-charger-gemini-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: go-e-charger-gemini-ocpp + brand: go-e + description: Charger Gemini (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-gemini.yaml b/templates/release/de/charger/go-e-charger-gemini.yaml new file mode 100644 index 0000000000..00ae8f43c7 --- /dev/null +++ b/templates/release/de/charger/go-e-charger-gemini.yaml @@ -0,0 +1,27 @@ +template: go-e-v3 +product: + identifier: go-e-charger-gemini + brand: go-e + description: Charger Gemini +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +description: | + Benötigt mindestens Firmware 052.1 oder neuer. + Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". + In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. + +render: + - default: | + type: template + template: go-e-v3 + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-homefix.yaml b/templates/release/de/charger/go-e-charger-homefix.yaml new file mode 100644 index 0000000000..a555f03464 --- /dev/null +++ b/templates/release/de/charger/go-e-charger-homefix.yaml @@ -0,0 +1,24 @@ +template: go-e +product: + identifier: go-e-charger-homefix + brand: go-e + description: Charger HOMEfix +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. +render: + - default: | + type: template + template: go-e + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-homeplus.yaml b/templates/release/de/charger/go-e-charger-homeplus.yaml new file mode 100644 index 0000000000..cbed5e9d13 --- /dev/null +++ b/templates/release/de/charger/go-e-charger-homeplus.yaml @@ -0,0 +1,27 @@ +template: go-e-v3 +product: + identifier: go-e-charger-homeplus + brand: go-e + description: Charger HOME+ +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +description: | + Benötigt mindestens Firmware 052.1 oder neuer. + Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". + In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. + +render: + - default: | + type: template + template: go-e-v3 + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-pro-ocpp.yaml b/templates/release/de/charger/go-e-charger-pro-ocpp.yaml new file mode 100644 index 0000000000..01cd4a4e3f --- /dev/null +++ b/templates/release/de/charger/go-e-charger-pro-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: go-e-charger-pro-ocpp + brand: go-e + description: Charger PRO (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-pro.yaml b/templates/release/de/charger/go-e-charger-pro.yaml new file mode 100644 index 0000000000..836b0d80b6 --- /dev/null +++ b/templates/release/de/charger/go-e-charger-pro.yaml @@ -0,0 +1,24 @@ +template: go-e +product: + identifier: go-e-charger-pro + brand: go-e + description: Charger PRO +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. +render: + - default: | + type: template + template: go-e + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-v3-ocpp.yaml b/templates/release/de/charger/go-e-charger-v3-ocpp.yaml new file mode 100644 index 0000000000..e3f5223cb0 --- /dev/null +++ b/templates/release/de/charger/go-e-charger-v3-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: go-e-charger-v3-ocpp + brand: go-e + description: Charger V3 (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-v3.yaml b/templates/release/de/charger/go-e-charger-v3.yaml new file mode 100644 index 0000000000..ecd77842ee --- /dev/null +++ b/templates/release/de/charger/go-e-charger-v3.yaml @@ -0,0 +1,27 @@ +template: go-e-v3 +product: + identifier: go-e-charger-v3 + brand: go-e + description: Charger V3 +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +description: | + Benötigt mindestens Firmware 052.1 oder neuer. + Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". + In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. + +render: + - default: | + type: template + template: go-e-v3 + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/go-e-v3_0.yaml b/templates/release/de/charger/go-e-v3_0.yaml deleted file mode 100644 index 1fb8887640..0000000000 --- a/templates/release/de/charger/go-e-v3_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: go-e - description: Charger Gemini -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -description: | - Benötigt mindestens Firmware 052.1 oder neuer. - Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". - In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. - -render: - - default: | - type: template - template: go-e-v3 - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/go-e-v3_1.yaml b/templates/release/de/charger/go-e-v3_1.yaml deleted file mode 100644 index 006a89ab51..0000000000 --- a/templates/release/de/charger/go-e-v3_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: go-e - description: Charger HOME+ -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -description: | - Benötigt mindestens Firmware 052.1 oder neuer. - Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". - In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. - -render: - - default: | - type: template - template: go-e-v3 - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/go-e-v3_2.yaml b/templates/release/de/charger/go-e-v3_2.yaml deleted file mode 100644 index 1bc9b5a2e9..0000000000 --- a/templates/release/de/charger/go-e-v3_2.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: go-e - description: Charger V3 -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -description: | - Benötigt mindestens Firmware 052.1 oder neuer. - Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". - In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" aktiviert sein. - -render: - - default: | - type: template - template: go-e-v3 - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/go-e_0.yaml b/templates/release/de/charger/go-e_0.yaml deleted file mode 100644 index 9039c6d0a6..0000000000 --- a/templates/release/de/charger/go-e_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: go-e - description: Charger HOMEfix -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. -render: - - default: | - type: template - template: go-e - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/go-e_1.yaml b/templates/release/de/charger/go-e_1.yaml deleted file mode 100644 index 839e2d1876..0000000000 --- a/templates/release/de/charger/go-e_1.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: go-e - description: Charger PRO -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. -render: - - default: | - type: template - template: go-e - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/hardy-barth-cph1.yaml b/templates/release/de/charger/hardy-barth-cph1.yaml new file mode 100644 index 0000000000..6e6b94ced7 --- /dev/null +++ b/templates/release/de/charger/hardy-barth-cph1.yaml @@ -0,0 +1,37 @@ +template: hardybarth-ecb1 +product: + identifier: hardy-barth-cph1 + brand: Hardy Barth + description: cPH1 +requirements: ["sponsorship"] +description: | + Als Betriebsmodus muss `manual` ausgewählt sein +render: + - default: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP-Adresse oder Hostname + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/hardy-barth-cph2.yaml b/templates/release/de/charger/hardy-barth-cph2.yaml new file mode 100644 index 0000000000..9a93143004 --- /dev/null +++ b/templates/release/de/charger/hardy-barth-cph2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: hardy-barth-cph2 + brand: Hardy Barth + description: cPH2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/hardy-barth-cpm2.yaml b/templates/release/de/charger/hardy-barth-cpm2.yaml new file mode 100644 index 0000000000..15128f37c6 --- /dev/null +++ b/templates/release/de/charger/hardy-barth-cpm2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: hardy-barth-cpm2 + brand: Hardy Barth + description: cPμ2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/hardybarth-ecb1_0.yaml b/templates/release/de/charger/hardybarth-ecb1_0.yaml deleted file mode 100644 index 1ac96480b2..0000000000 --- a/templates/release/de/charger/hardybarth-ecb1_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: HardyBarth - description: cPH1 -requirements: ["sponsorship"] -description: | - Als Betriebsmodus muss `manual` ausgewählt sein -render: - - default: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP-Adresse oder Hostname - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/hardybarth-ecb1_1.yaml b/templates/release/de/charger/hardybarth-ecb1_1.yaml deleted file mode 100644 index f54240d0e5..0000000000 --- a/templates/release/de/charger/hardybarth-ecb1_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: echarge - description: cPH1 -requirements: ["sponsorship"] -description: | - Als Betriebsmodus muss `manual` ausgewählt sein -render: - - default: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP-Adresse oder Hostname - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/hardybarth-salia_0.yaml b/templates/release/de/charger/hardybarth-salia_0.yaml deleted file mode 100644 index 02a8fa4f77..0000000000 --- a/templates/release/de/charger/hardybarth-salia_0.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: Hardy Barth - description: cPH2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/hardybarth-salia_1.yaml b/templates/release/de/charger/hardybarth-salia_1.yaml deleted file mode 100644 index 63b821d59b..0000000000 --- a/templates/release/de/charger/hardybarth-salia_1.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: Hardy Barth - description: cPμ2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/hardybarth-salia_2.yaml b/templates/release/de/charger/hardybarth-salia_2.yaml deleted file mode 100644 index 521f72ee0d..0000000000 --- a/templates/release/de/charger/hardybarth-salia_2.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: echarge - description: cPH2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/hardybarth-salia_3.yaml b/templates/release/de/charger/hardybarth-salia_3.yaml deleted file mode 100644 index aca2915fdf..0000000000 --- a/templates/release/de/charger/hardybarth-salia_3.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: echarge - description: cPμ2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/heidelberg-energy-control.yaml b/templates/release/de/charger/heidelberg-energy-control.yaml new file mode 100644 index 0000000000..fad2544155 --- /dev/null +++ b/templates/release/de/charger/heidelberg-energy-control.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: heidelberg-energy-control + brand: Heidelberg + description: Energy Control +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/heidelberg_0.yaml b/templates/release/de/charger/heidelberg_0.yaml deleted file mode 100644 index 2d61df78d9..0000000000 --- a/templates/release/de/charger/heidelberg_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Heidelberg - description: Energy Control -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/heidelberg_1.yaml b/templates/release/de/charger/heidelberg_1.yaml deleted file mode 100644 index af44549230..0000000000 --- a/templates/release/de/charger/heidelberg_1.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: SENEC - description: Wallbox pro s -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/heidelberg_2.yaml b/templates/release/de/charger/heidelberg_2.yaml deleted file mode 100644 index 29e4368257..0000000000 --- a/templates/release/de/charger/heidelberg_2.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Walther Werke - description: Basic Evo Pro -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/heidelberg_3.yaml b/templates/release/de/charger/heidelberg_3.yaml deleted file mode 100644 index 4e1b9cc739..0000000000 --- a/templates/release/de/charger/heidelberg_3.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Amperfied - description: Wallbox Energy Control -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/hesotec-ebox.yaml b/templates/release/de/charger/hesotec-ebox.yaml new file mode 100644 index 0000000000..5c80164d4a --- /dev/null +++ b/templates/release/de/charger/hesotec-ebox.yaml @@ -0,0 +1,32 @@ +template: hesotec +product: + identifier: hesotec-ebox + brand: Hesotec + description: eBox +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hesotec + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/hesotec-esat.yaml b/templates/release/de/charger/hesotec-esat.yaml new file mode 100644 index 0000000000..4c93f63fa0 --- /dev/null +++ b/templates/release/de/charger/hesotec-esat.yaml @@ -0,0 +1,32 @@ +template: hesotec +product: + identifier: hesotec-esat + brand: Hesotec + description: eSat +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hesotec + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/hesotec_0.yaml b/templates/release/de/charger/hesotec_0.yaml deleted file mode 100644 index f709745da2..0000000000 --- a/templates/release/de/charger/hesotec_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Hesotec - description: eSat -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hesotec - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/hesotec_1.yaml b/templates/release/de/charger/hesotec_1.yaml deleted file mode 100644 index 387c70b2fa..0000000000 --- a/templates/release/de/charger/hesotec_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Hesotec - description: eBox -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hesotec - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/home-assistant-switch.yaml b/templates/release/de/charger/home-assistant-switch.yaml new file mode 100644 index 0000000000..36a9afd957 --- /dev/null +++ b/templates/release/de/charger/home-assistant-switch.yaml @@ -0,0 +1,100 @@ +template: homeassistant-switch +product: + identifier: home-assistant-switch + brand: Home Assistant + description: Schalter + group: Schaltbare Steckdosen +requirements: ["skiptest"] +render: + - default: | + type: template + template: homeassistant-switch + baseurl: http://homeassistant.local:8123 # Basis-URL der Home Assistant Instanz + token: # Long-Lived Access Token, aus Home Assistant Profil + switchentity: switch.smartsocket # Entity ID des schaltbaren Geräts + powerentity: sensor.smartsocket_power # Entity ID für Leistungsmessung, optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: homeassistant-switch + baseurl: http://homeassistant.local:8123 # Basis-URL der Home Assistant Instanz + token: # Long-Lived Access Token, aus Home Assistant Profil + switchentity: switch.smartsocket # Entity ID des schaltbaren Geräts + powerentity: sensor.smartsocket_power # Entity ID für Leistungsmessung, optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: baseurl + example: http://homeassistant.local:8123 + default: + choice: [] + unit: + description: Basis-URL der Home Assistant Instanz + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Long-Lived Access Token + help: aus Home Assistant Profil + advanced: false + optional: false + - name: switchentity + example: switch.smartsocket + default: + choice: [] + unit: + description: Entity ID des schaltbaren Geräts + help: + advanced: false + optional: false + - name: powerentity + example: sensor.smartsocket_power + default: + choice: [] + unit: + description: Entity ID für Leistungsmessung + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/homeassistant-switch_0.yaml b/templates/release/de/charger/homeassistant-switch_0.yaml deleted file mode 100644 index b3ce40b4a8..0000000000 --- a/templates/release/de/charger/homeassistant-switch_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Home Assistant - description: Schalter - group: Schaltbare Steckdosen -requirements: ["skiptest"] -render: - - default: | - type: template - template: homeassistant-switch - baseurl: http://homeassistant.local:8123 # Basis-URL der Home Assistant Instanz - token: # Long-Lived Access Token, aus Home Assistant Profil - switchentity: switch.smartsocket # Entity ID des schaltbaren Geräts - powerentity: sensor.smartsocket_power # Entity ID für Leistungsmessung, optional - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: homeassistant-switch - baseurl: http://homeassistant.local:8123 # Basis-URL der Home Assistant Instanz - token: # Long-Lived Access Token, aus Home Assistant Profil - switchentity: switch.smartsocket # Entity ID des schaltbaren Geräts - powerentity: sensor.smartsocket_power # Entity ID für Leistungsmessung, optional - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/homecharge-homecharger.yaml b/templates/release/de/charger/homecharge-homecharger.yaml new file mode 100644 index 0000000000..51de9dd475 --- /dev/null +++ b/templates/release/de/charger/homecharge-homecharger.yaml @@ -0,0 +1,90 @@ +template: ocpp-homecharge +product: + identifier: homecharge-homecharger + brand: Homecharge + description: Homecharger +requirements: ["sponsorship", "skiptest"] +description: | + Die Verwendung mit evcc erfordert einen eingebauten Stromzähler (Ausführungen HC11L/HC22L Energy oder Profi). + Die OCPP-Konfiguration erfolgt über den EFR-SECC-Ladecontroller über die URL http://host/secc. + Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händler. + +render: + - default: | + type: template + template: ocpp-homecharge + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-homecharge + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/homematic-ip.yaml b/templates/release/de/charger/homematic-ip.yaml new file mode 100644 index 0000000000..d43f79e31e --- /dev/null +++ b/templates/release/de/charger/homematic-ip.yaml @@ -0,0 +1,139 @@ +template: homematic +product: + identifier: homematic-ip + brand: Homematic IP + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: homematic + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: homematic + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + meterchannel: 6 # Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. + switchchannel: 3 # Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 2010 + choice: [] + unit: + description: XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010) + help: + advanced: false + optional: true + - name: device + example: 0001EE89AAD848 + default: + choice: [] + unit: + description: Geräteadresse/Seriennummer + help: Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: meterchannel + example: + default: 6 + choice: [] + unit: + description: Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2) + help: Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. + advanced: true + optional: false + - name: switchchannel + example: + default: 3 + choice: [] + unit: + description: Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1) + help: Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. + advanced: true + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h) + help: Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. + advanced: true + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/homematic_0.yaml b/templates/release/de/charger/homematic_0.yaml deleted file mode 100644 index 51b6e6ca45..0000000000 --- a/templates/release/de/charger/homematic_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Homematic IP - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: homematic - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: homematic - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - meterchannel: 6 # Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. - switchchannel: 3 # Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/homewizard.yaml b/templates/release/de/charger/homewizard.yaml new file mode 100644 index 0000000000..420e05c8f1 --- /dev/null +++ b/templates/release/de/charger/homewizard.yaml @@ -0,0 +1,65 @@ +template: homewizard +product: + identifier: homewizard + brand: HomeWizard + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: homewizard + host: 192.0.2.2 # IP-Adresse oder Hostname + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: homewizard + host: 192.0.2.2 # IP-Adresse oder Hostname + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/homewizard_0.yaml b/templates/release/de/charger/homewizard_0.yaml deleted file mode 100644 index 35b369962e..0000000000 --- a/templates/release/de/charger/homewizard_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: HomeWizard - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: homewizard - host: 192.0.2.2 # IP-Adresse oder Hostname - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: homewizard - host: 192.0.2.2 # IP-Adresse oder Hostname - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/huawei-scharger-22kt-s0.yaml b/templates/release/de/charger/huawei-scharger-22kt-s0.yaml new file mode 100644 index 0000000000..7a398121f5 --- /dev/null +++ b/templates/release/de/charger/huawei-scharger-22kt-s0.yaml @@ -0,0 +1,85 @@ +template: ocpp-huawei +product: + identifier: huawei-scharger-22kt-s0 + brand: Huawei + description: SCharger-22KT-S0 +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/huawei-scharger-7ks-s0.yaml b/templates/release/de/charger/huawei-scharger-7ks-s0.yaml new file mode 100644 index 0000000000..c74282da42 --- /dev/null +++ b/templates/release/de/charger/huawei-scharger-7ks-s0.yaml @@ -0,0 +1,85 @@ +template: ocpp-huawei +product: + identifier: huawei-scharger-7ks-s0 + brand: Huawei + description: SCharger-7KS-S0 +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/ichargecion_0.yaml b/templates/release/de/charger/ichargecion_0.yaml deleted file mode 100644 index b17e5e89dd..0000000000 --- a/templates/release/de/charger/ichargecion_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Schrack - description: i-CHARGE CION -render: - - default: | - type: template - template: ichargecion - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/ichargecion_1.yaml b/templates/release/de/charger/ichargecion_1.yaml deleted file mode 100644 index 2e266ef1bc..0000000000 --- a/templates/release/de/charger/ichargecion_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Smartfox - description: Pro Charger -render: - - default: | - type: template - template: ichargecion - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/idm.yaml b/templates/release/de/charger/idm.yaml new file mode 100644 index 0000000000..84517e70a3 --- /dev/null +++ b/templates/release/de/charger/idm.yaml @@ -0,0 +1,41 @@ +template: idm +product: + identifier: idm + brand: IDM + group: Wärmeerzeuger +render: + - default: | + type: template + template: idm + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater_top', 'warmwater_bottom', 'buffer'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/idm_0.yaml b/templates/release/de/charger/idm_0.yaml deleted file mode 100644 index b2951cb4da..0000000000 --- a/templates/release/de/charger/idm_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: IDM - group: Wärmeerzeuger -render: - - default: | - type: template - template: idm - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer] (optional) diff --git a/templates/release/de/charger/innogy-ebox.yaml b/templates/release/de/charger/innogy-ebox.yaml new file mode 100644 index 0000000000..4d8616ac7e --- /dev/null +++ b/templates/release/de/charger/innogy-ebox.yaml @@ -0,0 +1,33 @@ +template: innogy-ebox +product: + identifier: innogy-ebox + brand: Innogy + description: eBox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: innogy-ebox + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/innogy-ebox_0.yaml b/templates/release/de/charger/innogy-ebox_0.yaml deleted file mode 100644 index 805ac61c0d..0000000000 --- a/templates/release/de/charger/innogy-ebox_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Innogy - description: eBox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: innogy-ebox - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/innogy-ebox_1.yaml b/templates/release/de/charger/innogy-ebox_1.yaml deleted file mode 100644 index 628cd32186..0000000000 --- a/templates/release/de/charger/innogy-ebox_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: E.ON Drive - description: eBox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: innogy-ebox - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/innogy-ebox_2.yaml b/templates/release/de/charger/innogy-ebox_2.yaml deleted file mode 100644 index a35d5b1986..0000000000 --- a/templates/release/de/charger/innogy-ebox_2.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Compleo - description: eBox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: innogy-ebox - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/inro-pantabox.yaml b/templates/release/de/charger/inro-pantabox.yaml new file mode 100644 index 0000000000..66c6e76705 --- /dev/null +++ b/templates/release/de/charger/inro-pantabox.yaml @@ -0,0 +1,20 @@ +template: pantabox +product: + identifier: inro-pantabox + brand: INRO + description: Pantabox +render: + - default: | + type: template + template: pantabox + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/juice-charger-me.yaml b/templates/release/de/charger/juice-charger-me.yaml new file mode 100644 index 0000000000..9e16e437c0 --- /dev/null +++ b/templates/release/de/charger/juice-charger-me.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: juice-charger-me + brand: Juice + description: Charger Me +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/junkers-sg-ready.yaml b/templates/release/de/charger/junkers-sg-ready.yaml new file mode 100644 index 0000000000..7dba7ecbb0 --- /dev/null +++ b/templates/release/de/charger/junkers-sg-ready.yaml @@ -0,0 +1,53 @@ +template: emsesp +product: + identifier: junkers-sg-ready + brand: Junkers + description: SG Ready + group: Wärmeerzeuger +description: | + Eingebunden via [EMSESP](https://emsesp.org/) +render: + - default: | + type: template + template: emsesp + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # optional + powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) + tempsource: # Temperaturquelle, [warmwater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: powersource + example: + default: hpcurrpower + choice: ['hpcurrpower', 'hppower'] + unit: + description: Leistungsquelle + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/kathrein-kwb-ac20.yaml b/templates/release/de/charger/kathrein-kwb-ac20.yaml new file mode 100644 index 0000000000..4eb68796f2 --- /dev/null +++ b/templates/release/de/charger/kathrein-kwb-ac20.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac20 + brand: Kathrein + description: KWB-AC20 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/kathrein-kwb-ac35.yaml b/templates/release/de/charger/kathrein-kwb-ac35.yaml new file mode 100644 index 0000000000..7d102a6ec0 --- /dev/null +++ b/templates/release/de/charger/kathrein-kwb-ac35.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac35 + brand: Kathrein + description: KWB-AC35 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/kathrein-kwb-ac40-e.yaml b/templates/release/de/charger/kathrein-kwb-ac40-e.yaml new file mode 100644 index 0000000000..a711193f79 --- /dev/null +++ b/templates/release/de/charger/kathrein-kwb-ac40-e.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac40-e + brand: Kathrein + description: KWB-AC40 E +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/kathrein-kwb-ac40.yaml b/templates/release/de/charger/kathrein-kwb-ac40.yaml new file mode 100644 index 0000000000..b1472a0e4b --- /dev/null +++ b/templates/release/de/charger/kathrein-kwb-ac40.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac40 + brand: Kathrein + description: KWB-AC40 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/kathrein-kwb-ac60-e.yaml b/templates/release/de/charger/kathrein-kwb-ac60-e.yaml new file mode 100644 index 0000000000..5bdab9c459 --- /dev/null +++ b/templates/release/de/charger/kathrein-kwb-ac60-e.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac60-e + brand: Kathrein + description: KWB-AC60 E +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/kathrein-kwb-ac60.yaml b/templates/release/de/charger/kathrein-kwb-ac60.yaml new file mode 100644 index 0000000000..264c841887 --- /dev/null +++ b/templates/release/de/charger/kathrein-kwb-ac60.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac60 + brand: Kathrein + description: KWB-AC60 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/keba-kecontact-p20.yaml b/templates/release/de/charger/keba-kecontact-p20.yaml new file mode 100644 index 0000000000..dac7ec1e2c --- /dev/null +++ b/templates/release/de/charger/keba-kecontact-p20.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p20 + brand: KEBA + description: KeContact P20 +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/keba-kecontact-p30-c-series.yaml b/templates/release/de/charger/keba-kecontact-p30-c-series.yaml new file mode 100644 index 0000000000..5a91b2cfe0 --- /dev/null +++ b/templates/release/de/charger/keba-kecontact-p30-c-series.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p30-c-series + brand: KEBA + description: KeContact P30 C-Series +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/keba-kecontact-p30-x-series.yaml b/templates/release/de/charger/keba-kecontact-p30-x-series.yaml new file mode 100644 index 0000000000..032fbb8696 --- /dev/null +++ b/templates/release/de/charger/keba-kecontact-p30-x-series.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p30-x-series + brand: KEBA + description: KeContact P30 X-Series +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/keba-kecontact-p40-pro.yaml b/templates/release/de/charger/keba-kecontact-p40-pro.yaml new file mode 100644 index 0000000000..0caa3a1854 --- /dev/null +++ b/templates/release/de/charger/keba-kecontact-p40-pro.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p40-pro + brand: KEBA + description: KeContact P40 Pro +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/keba-kecontact-p40.yaml b/templates/release/de/charger/keba-kecontact-p40.yaml new file mode 100644 index 0000000000..ba9b925817 --- /dev/null +++ b/templates/release/de/charger/keba-kecontact-p40.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p40 + brand: KEBA + description: KeContact P40 +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/keba-modbus_0.yaml b/templates/release/de/charger/keba-modbus_0.yaml deleted file mode 100644 index 99dbde127e..0000000000 --- a/templates/release/de/charger/keba-modbus_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P20 -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/charger/keba-modbus_1.yaml b/templates/release/de/charger/keba-modbus_1.yaml deleted file mode 100644 index 73cc12a65c..0000000000 --- a/templates/release/de/charger/keba-modbus_1.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P30 C-Series -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/charger/keba-modbus_2.yaml b/templates/release/de/charger/keba-modbus_2.yaml deleted file mode 100644 index 2311c5c227..0000000000 --- a/templates/release/de/charger/keba-modbus_2.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P30 X-Series -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/charger/keba-modbus_3.yaml b/templates/release/de/charger/keba-modbus_3.yaml deleted file mode 100644 index 847f7cf466..0000000000 --- a/templates/release/de/charger/keba-modbus_3.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P40 -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/charger/keba-modbus_4.yaml b/templates/release/de/charger/keba-modbus_4.yaml deleted file mode 100644 index f69b93543b..0000000000 --- a/templates/release/de/charger/keba-modbus_4.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P40 Pro -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/charger/keba-modbus_5.yaml b/templates/release/de/charger/keba-modbus_5.yaml deleted file mode 100644 index 8be233b0cf..0000000000 --- a/templates/release/de/charger/keba-modbus_5.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: BMW - description: i Wallbox -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/charger/keba-modbus_6.yaml b/templates/release/de/charger/keba-modbus_6.yaml deleted file mode 100644 index a7fb0fbcbb..0000000000 --- a/templates/release/de/charger/keba-modbus_6.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: SolarEdge - description: Home EV Charger -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/charger/kermi-x-center-pro.yaml b/templates/release/de/charger/kermi-x-center-pro.yaml new file mode 100644 index 0000000000..7fd350fa4a --- /dev/null +++ b/templates/release/de/charger/kermi-x-center-pro.yaml @@ -0,0 +1,46 @@ +template: kermi +product: + identifier: kermi-x-center-pro + brand: Kermi + description: x-center pro + group: Wärmeerzeuger +render: + - default: | + type: template + template: kermi + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater, buffer] (optional) + advanced: | + type: template + template: kermi + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater, buffer] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/kermi_0.yaml b/templates/release/de/charger/kermi_0.yaml deleted file mode 100644 index a4a1752602..0000000000 --- a/templates/release/de/charger/kermi_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Bösch - description: x-change - group: Wärmeerzeuger -render: - - default: | - type: template - template: kermi - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - advanced: | - type: template - template: kermi - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional diff --git a/templates/release/de/charger/kermi_1.yaml b/templates/release/de/charger/kermi_1.yaml deleted file mode 100644 index a0ac73c8a0..0000000000 --- a/templates/release/de/charger/kermi_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Kermi - description: x-center pro - group: Wärmeerzeuger -render: - - default: | - type: template - template: kermi - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - advanced: | - type: template - template: kermi - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional diff --git a/templates/release/de/charger/kontron-solar-charger.yaml b/templates/release/de/charger/kontron-solar-charger.yaml new file mode 100644 index 0000000000..2d52154b5d --- /dev/null +++ b/templates/release/de/charger/kontron-solar-charger.yaml @@ -0,0 +1,39 @@ +template: ghost +product: + identifier: kontron-solar-charger + brand: Kontron Solar + description: Charger +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: ghost + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/kostal-enector.yaml b/templates/release/de/charger/kostal-enector.yaml new file mode 100644 index 0000000000..2d6f648e29 --- /dev/null +++ b/templates/release/de/charger/kostal-enector.yaml @@ -0,0 +1,48 @@ +template: mennekes-compact +product: + identifier: kostal-enector + brand: Kostal + description: Enector +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). + Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. + Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. + +render: + - default: | + type: template + template: mennekes-compact + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 50 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N2" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 50 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 57600 + comset: 8N2 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 50 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/kse-wbx16.yaml b/templates/release/de/charger/kse-wbx16.yaml new file mode 100644 index 0000000000..c562f20efd --- /dev/null +++ b/templates/release/de/charger/kse-wbx16.yaml @@ -0,0 +1,43 @@ +template: kse +product: + identifier: kse-wbx16 + brand: KSE + description: wBX16 +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: kse + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 100 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 100 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 100 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/kse_0.yaml b/templates/release/de/charger/kse_0.yaml deleted file mode 100644 index eb69e1c9fe..0000000000 --- a/templates/release/de/charger/kse_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: KSE - description: wBX16 -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: kse - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 100 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 100 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/ladefoxx-evload.yaml b/templates/release/de/charger/ladefoxx-evload.yaml new file mode 100644 index 0000000000..3b0b965d16 --- /dev/null +++ b/templates/release/de/charger/ladefoxx-evload.yaml @@ -0,0 +1,50 @@ +template: phoenix-charx +product: + identifier: ladefoxx-evload + brand: LadeFoxx + description: EvLoad +render: + - default: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/ladefoxx-mikro-2-0.yaml b/templates/release/de/charger/ladefoxx-mikro-2-0.yaml new file mode 100644 index 0000000000..3011b371d1 --- /dev/null +++ b/templates/release/de/charger/ladefoxx-mikro-2-0.yaml @@ -0,0 +1,50 @@ +template: phoenix-charx +product: + identifier: ladefoxx-mikro-2-0 + brand: LadeFoxx + description: Mikro 2.0 +render: + - default: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/lambda-eu-l-series.yaml b/templates/release/de/charger/lambda-eu-l-series.yaml new file mode 100644 index 0000000000..7125ef40bd --- /dev/null +++ b/templates/release/de/charger/lambda-eu-l-series.yaml @@ -0,0 +1,52 @@ +template: lambda-zewotherm +product: + identifier: lambda-eu-l-series + brand: Lambda + description: EU-L Serie + group: Wärmeerzeuger +description: | + Energiemanagementeinstellungen am Gerät: + + - E-Meter Kommunikationsart: "ModBus Client" + - E-Meter Messpunkt: "Pos. E-Überschuss" + +render: + - default: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + advanced: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater_top', 'warmwater_bottom', 'buffer_top', 'buffer_bottom'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/lambda-zewotherm_0.yaml b/templates/release/de/charger/lambda-zewotherm_0.yaml deleted file mode 100644 index bcc8437035..0000000000 --- a/templates/release/de/charger/lambda-zewotherm_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: Lambda - description: EU-L Serie - group: Wärmeerzeuger -description: | - Energiemanagementeinstellungen am Gerät: - - - E-Meter Kommunikationsart: "ModBus Client" - - E-Meter Messpunkt: "Pos. E-Überschuss" - -render: - - default: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - advanced: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional diff --git a/templates/release/de/charger/lambda-zewotherm_1.yaml b/templates/release/de/charger/lambda-zewotherm_1.yaml deleted file mode 100644 index 186e53c95c..0000000000 --- a/templates/release/de/charger/lambda-zewotherm_1.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: Zewotherm - description: EU-L Serie - group: Wärmeerzeuger -description: | - Energiemanagementeinstellungen am Gerät: - - - E-Meter Kommunikationsart: "ModBus Client" - - E-Meter Messpunkt: "Pos. E-Überschuss" - -render: - - default: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - advanced: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP-Adresse oder Hostname - tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional diff --git a/templates/release/de/charger/livo_0.yaml b/templates/release/de/charger/livo_0.yaml deleted file mode 100644 index c004446d9c..0000000000 --- a/templates/release/de/charger/livo_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: EVBox - description: Livo -requirements: ["eebus"] -description: | - Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzurichten. Danach erkennt das Ladegerät evcc als HEMS-Gerät im Netzwerk. Verwende das Installationstool, um evcc als HEMS auszuwählen. Kopiere anschließend den angegebenen SKI aus der Installations-App und fügen ihn zu Ihrem YAML hinzu. -render: - - default: | - type: template - template: livo - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/lrt-home-essentialplus.yaml b/templates/release/de/charger/lrt-home-essentialplus.yaml new file mode 100644 index 0000000000..f5e9070c68 --- /dev/null +++ b/templates/release/de/charger/lrt-home-essentialplus.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: lrt-home-essentialplus + brand: LRT + description: HOME Essential+ +requirements: ["sponsorship"] +description: | + Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/luxtronik_0.yaml b/templates/release/de/charger/luxtronik_0.yaml deleted file mode 100644 index 8700ecb0c5..0000000000 --- a/templates/release/de/charger/luxtronik_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Buderus - description: Logamatic HMC 20 - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_1.yaml b/templates/release/de/charger/luxtronik_1.yaml deleted file mode 100644 index 88885d6a78..0000000000 --- a/templates/release/de/charger/luxtronik_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Buderus - description: Logamatic HMC 20 Z - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_10.yaml b/templates/release/de/charger/luxtronik_10.yaml deleted file mode 100644 index 677637919b..0000000000 --- a/templates/release/de/charger/luxtronik_10.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Wolf - description: BWS - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_2.yaml b/templates/release/de/charger/luxtronik_2.yaml deleted file mode 100644 index 420f6a0a7e..0000000000 --- a/templates/release/de/charger/luxtronik_2.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: alpha innotec - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_3.yaml b/templates/release/de/charger/luxtronik_3.yaml deleted file mode 100644 index ca9894c541..0000000000 --- a/templates/release/de/charger/luxtronik_3.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: CTA All-In-One - description: Aeroplus - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_4.yaml b/templates/release/de/charger/luxtronik_4.yaml deleted file mode 100644 index 417b9744c8..0000000000 --- a/templates/release/de/charger/luxtronik_4.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Elco - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_5.yaml b/templates/release/de/charger/luxtronik_5.yaml deleted file mode 100644 index 63ff9bd021..0000000000 --- a/templates/release/de/charger/luxtronik_5.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nibe - description: AP-AW10 - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_6.yaml b/templates/release/de/charger/luxtronik_6.yaml deleted file mode 100644 index 285677baa3..0000000000 --- a/templates/release/de/charger/luxtronik_6.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Roth - description: ThermoAura - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_7.yaml b/templates/release/de/charger/luxtronik_7.yaml deleted file mode 100644 index 3b6d6985bc..0000000000 --- a/templates/release/de/charger/luxtronik_7.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Roth - description: ThermoTerra - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_8.yaml b/templates/release/de/charger/luxtronik_8.yaml deleted file mode 100644 index 02666f38ac..0000000000 --- a/templates/release/de/charger/luxtronik_8.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Novelan - description: WPR NET - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/luxtronik_9.yaml b/templates/release/de/charger/luxtronik_9.yaml deleted file mode 100644 index b193a60ad2..0000000000 --- a/templates/release/de/charger/luxtronik_9.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Wolf - description: BWL - group: Wärmeerzeuger -description: | - Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) diff --git a/templates/release/de/charger/mennekes-amedio-professional.yaml b/templates/release/de/charger/mennekes-amedio-professional.yaml new file mode 100644 index 0000000000..7b066198f6 --- /dev/null +++ b/templates/release/de/charger/mennekes-amedio-professional.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: mennekes-amedio-professional + brand: Mennekes + description: AMEDIO Professional +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-4business-700.yaml b/templates/release/de/charger/mennekes-amtron-4business-700.yaml new file mode 100644 index 0000000000..2045673b14 --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-4business-700.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: mennekes-amtron-4business-700 + brand: Mennekes + description: AMTRON 4Business 700 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-4you-300.yaml b/templates/release/de/charger/mennekes-amtron-4you-300.yaml new file mode 100644 index 0000000000..abadbdcdec --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-4you-300.yaml @@ -0,0 +1,48 @@ +template: mennekes-compact +product: + identifier: mennekes-amtron-4you-300 + brand: Mennekes + description: AMTRON 4You 300 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). + Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. + Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. + +render: + - default: | + type: template + template: mennekes-compact + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 50 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N2" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 50 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 57600 + comset: 8N2 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 50 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-4you-500.yaml b/templates/release/de/charger/mennekes-amtron-4you-500.yaml new file mode 100644 index 0000000000..d0bb2c5f69 --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-4you-500.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: mennekes-amtron-4you-500 + brand: Mennekes + description: AMTRON 4You 500 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-chargecontrol.yaml b/templates/release/de/charger/mennekes-amtron-chargecontrol.yaml new file mode 100644 index 0000000000..23e1751dd7 --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-chargecontrol.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: mennekes-amtron-chargecontrol + brand: Mennekes + description: AMTRON ChargeControl +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml b/templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml new file mode 100644 index 0000000000..09a0bbe1c4 --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml @@ -0,0 +1,48 @@ +template: mennekes-compact +product: + identifier: mennekes-amtron-compact-2-0s + brand: Mennekes + description: AMTRON Compact 2.0s +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). + Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. + Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. + +render: + - default: | + type: template + template: mennekes-compact + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 50 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N2" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 50 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 57600 + comset: 8N2 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 50 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-premium.yaml b/templates/release/de/charger/mennekes-amtron-premium.yaml new file mode 100644 index 0000000000..4d919d93dc --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-premium.yaml @@ -0,0 +1,32 @@ +template: mennekes-hcc3 +product: + identifier: mennekes-amtron-premium + brand: Mennekes + description: AMTRON Premium +requirements: ["sponsorship"] +render: + - default: | + type: template + template: mennekes-hcc3 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-professional.yaml b/templates/release/de/charger/mennekes-amtron-professional.yaml new file mode 100644 index 0000000000..98b6e2589b --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-professional.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: mennekes-amtron-professional + brand: Mennekes + description: AMTRON Professional +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-amtron-xtra.yaml b/templates/release/de/charger/mennekes-amtron-xtra.yaml new file mode 100644 index 0000000000..1669a80f46 --- /dev/null +++ b/templates/release/de/charger/mennekes-amtron-xtra.yaml @@ -0,0 +1,32 @@ +template: mennekes-hcc3 +product: + identifier: mennekes-amtron-xtra + brand: Mennekes + description: AMTRON Xtra +requirements: ["sponsorship"] +render: + - default: | + type: template + template: mennekes-hcc3 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-compact_0.yaml b/templates/release/de/charger/mennekes-compact_0.yaml deleted file mode 100644 index 574993287c..0000000000 --- a/templates/release/de/charger/mennekes-compact_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Compact 2.0s -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). - Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. - Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. - -render: - - default: | - type: template - template: mennekes-compact - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 50 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N2" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 50 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/mennekes-compact_1.yaml b/templates/release/de/charger/mennekes-compact_1.yaml deleted file mode 100644 index b40c85ddad..0000000000 --- a/templates/release/de/charger/mennekes-compact_1.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Mennekes - description: AMTRON 4You 300 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). - Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. - Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. - -render: - - default: | - type: template - template: mennekes-compact - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 50 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N2" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 50 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/mennekes-compact_2.yaml b/templates/release/de/charger/mennekes-compact_2.yaml deleted file mode 100644 index 7cd6f0b650..0000000000 --- a/templates/release/de/charger/mennekes-compact_2.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Kostal - description: Enector -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). - Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. - Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivierungscode (Solar Pure Mode / Solar Plus Mode) für das KSEM *nicht* erforderlich. - -render: - - default: | - type: template - template: mennekes-compact - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 50 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N2" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 50 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/mennekes-emobility-gateway-acu.yaml b/templates/release/de/charger/mennekes-emobility-gateway-acu.yaml new file mode 100644 index 0000000000..2e48c11733 --- /dev/null +++ b/templates/release/de/charger/mennekes-emobility-gateway-acu.yaml @@ -0,0 +1,91 @@ +template: ocpp-mennekes-acu +product: + identifier: mennekes-emobility-gateway-acu + brand: Mennekes + description: eMobility Gateway (ACU) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + Zur Konfiguration die Weboberfläche der ACU aufrufen. + Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J + Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. + +render: + - default: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-hcc3_0.yaml b/templates/release/de/charger/mennekes-hcc3_0.yaml deleted file mode 100644 index 327f8b99ed..0000000000 --- a/templates/release/de/charger/mennekes-hcc3_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Xtra -requirements: ["sponsorship"] -render: - - default: | - type: template - template: mennekes-hcc3 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/mennekes-hcc3_1.yaml b/templates/release/de/charger/mennekes-hcc3_1.yaml deleted file mode 100644 index dbcb5fe2d6..0000000000 --- a/templates/release/de/charger/mennekes-hcc3_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Premium -requirements: ["sponsorship"] -render: - - default: | - type: template - template: mennekes-hcc3 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/mennekes-smart-acu.yaml b/templates/release/de/charger/mennekes-smart-acu.yaml new file mode 100644 index 0000000000..fa120f0afa --- /dev/null +++ b/templates/release/de/charger/mennekes-smart-acu.yaml @@ -0,0 +1,91 @@ +template: ocpp-mennekes-acu +product: + identifier: mennekes-smart-acu + brand: Mennekes + description: Smart (ACU) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + Zur Konfiguration die Weboberfläche der ACU aufrufen. + Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J + Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. + +render: + - default: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-smart-t-acu.yaml b/templates/release/de/charger/mennekes-smart-t-acu.yaml new file mode 100644 index 0000000000..d36c94dbea --- /dev/null +++ b/templates/release/de/charger/mennekes-smart-t-acu.yaml @@ -0,0 +1,91 @@ +template: ocpp-mennekes-acu +product: + identifier: mennekes-smart-t-acu + brand: Mennekes + description: Smart T (ACU) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + Zur Konfiguration die Weboberfläche der ACU aufrufen. + Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J + Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. + +render: + - default: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/my-pv-ac-elwa-2.yaml b/templates/release/de/charger/my-pv-ac-elwa-2.yaml new file mode 100644 index 0000000000..32472270e8 --- /dev/null +++ b/templates/release/de/charger/my-pv-ac-elwa-2.yaml @@ -0,0 +1,43 @@ +template: ac-elwa-2 +product: + identifier: my-pv-ac-elwa-2 + brand: my-PV + description: AC ELWA 2 + group: Wärmeerzeuger +requirements: ["sponsorship"] +render: + - default: | + type: template + template: ac-elwa-2 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: scale + example: + default: 1 + choice: [] + unit: + description: Skalierungsfaktor der Leistungsvorgabe + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/my-pv-ac-thor-9s.yaml b/templates/release/de/charger/my-pv-ac-thor-9s.yaml new file mode 100644 index 0000000000..be309fb33c --- /dev/null +++ b/templates/release/de/charger/my-pv-ac-thor-9s.yaml @@ -0,0 +1,53 @@ +template: ac-thor +product: + identifier: my-pv-ac-thor-9s + brand: my-PV + description: AC•THOR 9s + group: Wärmeerzeuger +requirements: ["sponsorship"] +render: + - default: | + type: template + template: ac-thor + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperatursensor + help: + advanced: false + optional: true + - name: scale + example: + default: 1 + choice: [] + unit: + description: Skalierungsfaktor der Leistungsvorgabe + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/my-pv-ac-thor.yaml b/templates/release/de/charger/my-pv-ac-thor.yaml new file mode 100644 index 0000000000..a5a0b93f43 --- /dev/null +++ b/templates/release/de/charger/my-pv-ac-thor.yaml @@ -0,0 +1,53 @@ +template: ac-thor +product: + identifier: my-pv-ac-thor + brand: my-PV + description: AC•THOR + group: Wärmeerzeuger +requirements: ["sponsorship"] +render: + - default: | + type: template + template: ac-thor + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperatursensor + help: + advanced: false + optional: true + - name: scale + example: + default: 1 + choice: [] + unit: + description: Skalierungsfaktor der Leistungsvorgabe + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/mystrom-switch.yaml b/templates/release/de/charger/mystrom-switch.yaml new file mode 100644 index 0000000000..521e8aa13e --- /dev/null +++ b/templates/release/de/charger/mystrom-switch.yaml @@ -0,0 +1,66 @@ +template: mystrom +product: + identifier: mystrom-switch + brand: myStrom + description: Switch + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: mystrom + host: 192.0.2.2 # IP-Adresse oder Hostname + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: mystrom + host: 192.0.2.2 # IP-Adresse oder Hostname + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/mystrom_0.yaml b/templates/release/de/charger/mystrom_0.yaml deleted file mode 100644 index 81b0f1102e..0000000000 --- a/templates/release/de/charger/mystrom_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: myStrom - description: Switch - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: mystrom - host: 192.0.2.2 # IP-Adresse oder Hostname - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: mystrom - host: 192.0.2.2 # IP-Adresse oder Hostname - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/nibe-ap-aw10.yaml b/templates/release/de/charger/nibe-ap-aw10.yaml new file mode 100644 index 0000000000..a82ed267da --- /dev/null +++ b/templates/release/de/charger/nibe-ap-aw10.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: nibe-ap-aw10 + brand: Nibe + description: AP-AW10 + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/novelan-wpr-net.yaml b/templates/release/de/charger/novelan-wpr-net.yaml new file mode 100644 index 0000000000..d87c82753d --- /dev/null +++ b/templates/release/de/charger/novelan-wpr-net.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: novelan-wpr-net + brand: Novelan + description: WPR NET + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/nrggen2_0.yaml b/templates/release/de/charger/nrggen2_0.yaml deleted file mode 100644 index 07040fbeeb..0000000000 --- a/templates/release/de/charger/nrggen2_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: NRGkick - description: Gen2 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: nrggen2 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: nrggen2 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - phases1p3p: false # Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional) diff --git a/templates/release/de/charger/nrgkick-connect.yaml b/templates/release/de/charger/nrgkick-connect.yaml new file mode 100644 index 0000000000..a0e682ef62 --- /dev/null +++ b/templates/release/de/charger/nrgkick-connect.yaml @@ -0,0 +1,42 @@ +template: nrgkick-connect +product: + identifier: nrgkick-connect + brand: NRGkick + description: Connect +description: | + NRGkick Ladeeinheit via HTTP (älter als 2022/2023) +render: + - default: | + type: template + template: nrgkick-connect + host: 192.0.2.2 # IP-Adresse oder Hostname + mac: + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: mac + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/nrgkick-connect_0.yaml b/templates/release/de/charger/nrgkick-connect_0.yaml deleted file mode 100644 index 6e06568f0a..0000000000 --- a/templates/release/de/charger/nrgkick-connect_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: NRGkick - description: Connect -description: | - NRGkick Ladeeinheit via HTTP (älter als 2022/2023) -render: - - default: | - type: template - template: nrgkick-connect - host: 192.0.2.2 # IP-Adresse oder Hostname - mac: - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen diff --git a/templates/release/de/charger/nrgkick-gen2.yaml b/templates/release/de/charger/nrgkick-gen2.yaml new file mode 100644 index 0000000000..994b3fa68b --- /dev/null +++ b/templates/release/de/charger/nrgkick-gen2.yaml @@ -0,0 +1,52 @@ +template: nrggen2 +product: + identifier: nrgkick-gen2 + brand: NRGkick + description: Gen2 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: nrggen2 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: nrggen2 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + phases1p3p: false # Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: + help: Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/obo-bettermann-ion.yaml b/templates/release/de/charger/obo-bettermann-ion.yaml new file mode 100644 index 0000000000..f0eb202144 --- /dev/null +++ b/templates/release/de/charger/obo-bettermann-ion.yaml @@ -0,0 +1,48 @@ +template: obo +product: + identifier: obo-bettermann-ion + brand: OBO Bettermann + description: Ion +render: + - default: | + type: template + template: obo + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 101 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 101 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/obo_0.yaml b/templates/release/de/charger/obo_0.yaml deleted file mode 100644 index bf4300498c..0000000000 --- a/templates/release/de/charger/obo_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: EcoHarmony - description: EVSE EPC 2.0 Plus -render: - - default: | - type: template - template: obo - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 101 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/obo_1.yaml b/templates/release/de/charger/obo_1.yaml deleted file mode 100644 index b47bf8b176..0000000000 --- a/templates/release/de/charger/obo_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: OBO Bettermann - description: Ion -render: - - default: | - type: template - template: obo - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 101 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/obo_2.yaml b/templates/release/de/charger/obo_2.yaml deleted file mode 100644 index 920581ce88..0000000000 --- a/templates/release/de/charger/obo_2.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Viridian EV - description: EVSE EPC 2.0 Plus -render: - - default: | - type: template - template: obo - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 101 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml b/templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml new file mode 100644 index 0000000000..fba46f8c63 --- /dev/null +++ b/templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml @@ -0,0 +1,107 @@ +template: ocpp +product: + identifier: ocpp-1-6j-compatible-smart-charging + description: OCPP 1.6J kompatibel (Smart Charging) + group: Generische Unterstützung +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +description: | + Bei OCPP verbindet sich die Wallbox (Client) zu evcc (Server). + Die Wallbox muss daher evcc via Hostname (funktionierende DNS-Auflösung erforderlich!) oder über die IP-Adresse auf Port 8887 erreichen können. + Standardmäßig wird die erste eingehende Verbindung mit einer beliebigen Ladepunktkennung verwendet. + Um mehrere Ladepunkte eindeutig zuordnen zu können müssen die jeweilige Stationskennung (`stationid: `) und Anschlussnummer (`connector: `) hinterlegt werden. + Viele Wallboxen fügen die `stationid` automatisch der Backend-URL hinzu, bei manchen muss dies manuell geschehen `ws://:8887/`. + Für Zählermesswerte sollte in der Wallbox wenn möglich ein kurzes Zeitintervall (< 10s) konfiguriert werden. + Nutzen Sie Ihre RFID-Tags (dies ermöglicht z. B. eine Fahrzeugidentifizierung) oder setzen Sie Ihre Wallbox auf "freies Laden" oder "Autostart" um die für die Ladefreigabe benötigte Transaktion zu erzeugen. + + Falls die Wallbox keine Möglichkeit bietet die Transaktionen lokal zu starten, kann die erweiterte Option `remotestart` genutzt werden um automatisch eine Transaktion zu starten sobald ein Fahrzeug angeschlossen wird. + Dies sollte nur in Ausnahmefällen erforderlich sein. + + Voraussetzungen: + * Ggf. zuvor konfigurierte OCPP-Profile (z.B. durch eine andere Backend-Anbindung) in der Wallboxkonfiguration entfernen + * Backend-URL (Central System) in der Wallboxkonfiguration: `ws://[evcc-adresse]:8887/` (eventuell noch um `stationid` erweitern) + * Protokoll: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// o.ä. + * Keine Verschlüsselung, keine Authentifizierung, kein Passwort + * Verbindung über das lokale Netzwerk + + Die konkrete Konfiguration und der tatsächlich nutzbare Funktionsumfang hängen vom Wallbox-Modell und dessen Software ab. + +render: + - default: | + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/ocpp-abb-tac_0.yaml b/templates/release/de/charger/ocpp-abb-tac_0.yaml deleted file mode 100644 index d49e471c24..0000000000 --- a/templates/release/de/charger/ocpp-abb-tac_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: ABB - description: Terra AC -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf -render: - - default: | - type: template - template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-abl_0.yaml b/templates/release/de/charger/ocpp-abl_0.yaml deleted file mode 100644 index a6ee4bbdfe..0000000000 --- a/templates/release/de/charger/ocpp-abl_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ABL Sursum - description: eMH2 -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-abl_1.yaml b/templates/release/de/charger/ocpp-abl_1.yaml deleted file mode 100644 index e8b2388b23..0000000000 --- a/templates/release/de/charger/ocpp-abl_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ABL Sursum - description: eMH3 -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-abl_2.yaml b/templates/release/de/charger/ocpp-abl_2.yaml deleted file mode 100644 index 7664a276fc..0000000000 --- a/templates/release/de/charger/ocpp-abl_2.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ABL Sursum - description: eMH4 -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-alfen_0.yaml b/templates/release/de/charger/ocpp-alfen_0.yaml deleted file mode 100644 index 74fc3cda24..0000000000 --- a/templates/release/de/charger/ocpp-alfen_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Alfen - description: Eve -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-autel_0.yaml b/templates/release/de/charger/ocpp-autel_0.yaml deleted file mode 100644 index 3732d9bf00..0000000000 --- a/templates/release/de/charger/ocpp-autel_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: AUTEL - description: AC MaxiCharger -capabilities: ["mA"] -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: - * In der Autel Charge app, klicken sie auf “OCPP Server” - * Geben Sie "Custom" in das Feld ein und wählen Sie "Personalisierung" darunter - * Server-URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladegerät-ID: Leer lassen (zur Verwendung der Seriennummer) oder einen benutzerdefinierten Wert definieren, der in der Konfiguration als *stationid* wiederverwendet wird - * Autorisierungsschlüssel: leer lassen - -render: - - default: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-autel_1.yaml b/templates/release/de/charger/ocpp-autel_1.yaml deleted file mode 100644 index da537f97e5..0000000000 --- a/templates/release/de/charger/ocpp-autel_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: AUTEL - description: AC Compact -capabilities: ["mA"] -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: - * In der Autel Charge app, klicken sie auf “OCPP Server” - * Geben Sie "Custom" in das Feld ein und wählen Sie "Personalisierung" darunter - * Server-URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladegerät-ID: Leer lassen (zur Verwendung der Seriennummer) oder einen benutzerdefinierten Wert definieren, der in der Konfiguration als *stationid* wiederverwendet wird - * Autorisierungsschlüssel: leer lassen - -render: - - default: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-autoaid_0.yaml b/templates/release/de/charger/ocpp-autoaid_0.yaml deleted file mode 100644 index 6849e1f739..0000000000 --- a/templates/release/de/charger/ocpp-autoaid_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Autoaid - description: Intelligent Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-autoaid_1.yaml b/templates/release/de/charger/ocpp-autoaid_1.yaml deleted file mode 100644 index b204a5b7db..0000000000 --- a/templates/release/de/charger/ocpp-autoaid_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Autoaid - description: Business Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-beny_0.yaml b/templates/release/de/charger/ocpp-beny_0.yaml deleted file mode 100644 index 3ef507746f..0000000000 --- a/templates/release/de/charger/ocpp-beny_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ZJ Beny - description: BCP EV charger -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-chargeamps_0.yaml b/templates/release/de/charger/ocpp-chargeamps_0.yaml deleted file mode 100644 index 561d3b5058..0000000000 --- a/templates/release/de/charger/ocpp-chargeamps_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Charge Amps - description: Halo -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-elecq_0.yaml b/templates/release/de/charger/ocpp-elecq_0.yaml deleted file mode 100644 index a23c3ff5fd..0000000000 --- a/templates/release/de/charger/ocpp-elecq_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Elecq - description: Home -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-elecq_1.yaml b/templates/release/de/charger/ocpp-elecq_1.yaml deleted file mode 100644 index f027617e9b..0000000000 --- a/templates/release/de/charger/ocpp-elecq_1.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Elecq - description: Biz -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-elecq_2.yaml b/templates/release/de/charger/ocpp-elecq_2.yaml deleted file mode 100644 index d11eda37b0..0000000000 --- a/templates/release/de/charger/ocpp-elecq_2.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Elecq - description: Station -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-enercab_0.yaml b/templates/release/de/charger/ocpp-enercab_0.yaml deleted file mode 100644 index 86d7ae826d..0000000000 --- a/templates/release/de/charger/ocpp-enercab_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: enercab - description: smart -capabilities: ["1p3p"] -requirements: ["sponsorship", "skiptest"] -description: | - https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - -render: - - default: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-enercab_1.yaml b/templates/release/de/charger/ocpp-enercab_1.yaml deleted file mode 100644 index 1f9d62264b..0000000000 --- a/templates/release/de/charger/ocpp-enercab_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: eledio - description: go -capabilities: ["1p3p"] -requirements: ["sponsorship", "skiptest"] -description: | - https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - -render: - - default: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-enplus_0.yaml b/templates/release/de/charger/ocpp-enplus_0.yaml deleted file mode 100644 index f6fa835c17..0000000000 --- a/templates/release/de/charger/ocpp-enplus_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EN+ - description: AC EV Charger -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-entratek_0.yaml b/templates/release/de/charger/ocpp-entratek_0.yaml deleted file mode 100644 index bd2dcfeec2..0000000000 --- a/templates/release/de/charger/ocpp-entratek_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EntraTek - description: Power Dot Fix -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-entratek_1.yaml b/templates/release/de/charger/ocpp-entratek_1.yaml deleted file mode 100644 index c6bed0d3fa..0000000000 --- a/templates/release/de/charger/ocpp-entratek_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EntraTek - description: Power Dot Pro 2 -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-esolutions_0.yaml b/templates/release/de/charger/ocpp-esolutions_0.yaml deleted file mode 100644 index 8c4a28ec10..0000000000 --- a/templates/release/de/charger/ocpp-esolutions_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Free2move eSolutions - description: eProWallbox -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-evbox-elvi_0.yaml b/templates/release/de/charger/ocpp-evbox-elvi_0.yaml deleted file mode 100644 index d4ef2bc5ff..0000000000 --- a/templates/release/de/charger/ocpp-evbox-elvi_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EVBox - description: Elvi -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional - advanced: | - type: template - template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-goe_0.yaml b/templates/release/de/charger/ocpp-goe_0.yaml deleted file mode 100644 index c730f6b5c7..0000000000 --- a/templates/release/de/charger/ocpp-goe_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: go-e - description: Charger V3 -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-goe_1.yaml b/templates/release/de/charger/ocpp-goe_1.yaml deleted file mode 100644 index 0686c75828..0000000000 --- a/templates/release/de/charger/ocpp-goe_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: go-e - description: Charger Gemini -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-goe_2.yaml b/templates/release/de/charger/ocpp-goe_2.yaml deleted file mode 100644 index db3aa1e83c..0000000000 --- a/templates/release/de/charger/ocpp-goe_2.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: go-e - description: Charger PRO -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-goe_3.yaml b/templates/release/de/charger/ocpp-goe_3.yaml deleted file mode 100644 index 160fa8580a..0000000000 --- a/templates/release/de/charger/ocpp-goe_3.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Fronius - description: Wattpilot -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-homecharge_0.yaml b/templates/release/de/charger/ocpp-homecharge_0.yaml deleted file mode 100644 index f00c789a9b..0000000000 --- a/templates/release/de/charger/ocpp-homecharge_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Homecharge - description: Homecharger -requirements: ["sponsorship", "skiptest"] -description: | - Die Verwendung mit evcc erfordert einen eingebauten Stromzähler (Ausführungen HC11L/HC22L Energy oder Profi). - Die OCPP-Konfiguration erfolgt über den EFR-SECC-Ladecontroller über die URL http://host/secc. - Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händler. - -render: - - default: | - type: template - template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-huawei_0.yaml b/templates/release/de/charger/ocpp-huawei_0.yaml deleted file mode 100644 index e191e3533d..0000000000 --- a/templates/release/de/charger/ocpp-huawei_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Huawei - description: SCharger-7KS-S0 -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-huawei_1.yaml b/templates/release/de/charger/ocpp-huawei_1.yaml deleted file mode 100644 index c105d7a4eb..0000000000 --- a/templates/release/de/charger/ocpp-huawei_1.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Huawei - description: SCharger-22KT-S0 -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-mennekes-acu_0.yaml b/templates/release/de/charger/ocpp-mennekes-acu_0.yaml deleted file mode 100644 index 70c5852a49..0000000000 --- a/templates/release/de/charger/ocpp-mennekes-acu_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Mennekes - description: eMobility Gateway (ACU) -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - Zur Konfiguration die Weboberfläche der ACU aufrufen. - Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J - Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. - -render: - - default: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-mennekes-acu_1.yaml b/templates/release/de/charger/ocpp-mennekes-acu_1.yaml deleted file mode 100644 index 4416b9def1..0000000000 --- a/templates/release/de/charger/ocpp-mennekes-acu_1.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Mennekes - description: Smart (ACU) -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - Zur Konfiguration die Weboberfläche der ACU aufrufen. - Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J - Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. - -render: - - default: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-mennekes-acu_2.yaml b/templates/release/de/charger/ocpp-mennekes-acu_2.yaml deleted file mode 100644 index b2e2a620a2..0000000000 --- a/templates/release/de/charger/ocpp-mennekes-acu_2.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Mennekes - description: Smart T (ACU) -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - Zur Konfiguration die Weboberfläche der ACU aufrufen. - Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J - Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887/` eingetragen sein. Basic Authentication: deaktivieren. OCPP 1.6 Einstellungen: alle Optionen aktivieren. - -render: - - default: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-orbis_0.yaml b/templates/release/de/charger/ocpp-orbis_0.yaml deleted file mode 100644 index 5000ce59af..0000000000 --- a/templates/release/de/charger/ocpp-orbis_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Orbis - description: Viaris -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-sungrow_0.yaml b/templates/release/de/charger/ocpp-sungrow_0.yaml deleted file mode 100644 index c824f92751..0000000000 --- a/templates/release/de/charger/ocpp-sungrow_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Sungrow - description: AC011E -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-wallbox_0.yaml b/templates/release/de/charger/ocpp-wallbox_0.yaml deleted file mode 100644 index 1cdb473ccd..0000000000 --- a/templates/release/de/charger/ocpp-wallbox_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Plus -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-wallbox_1.yaml b/templates/release/de/charger/ocpp-wallbox_1.yaml deleted file mode 100644 index 0773ee7bda..0000000000 --- a/templates/release/de/charger/ocpp-wallbox_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Max -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-wallbox_2.yaml b/templates/release/de/charger/ocpp-wallbox_2.yaml deleted file mode 100644 index 4ceb3b7497..0000000000 --- a/templates/release/de/charger/ocpp-wallbox_2.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Commander 2 -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-wallbox_3.yaml b/templates/release/de/charger/ocpp-wallbox_3.yaml deleted file mode 100644 index 81da526ad3..0000000000 --- a/templates/release/de/charger/ocpp-wallbox_3.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Copper SB -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp-zaptec_0.yaml b/templates/release/de/charger/ocpp-zaptec_0.yaml deleted file mode 100644 index 5a8e2ac9e8..0000000000 --- a/templates/release/de/charger/ocpp-zaptec_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Zaptec - description: Go -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - OCPP Native mode - - https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ - -render: - - default: | - type: template - template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/ocpp_0.yaml b/templates/release/de/charger/ocpp_0.yaml deleted file mode 100644 index 83e12aca23..0000000000 --- a/templates/release/de/charger/ocpp_0.yaml +++ /dev/null @@ -1,41 +0,0 @@ -product: - description: OCPP 1.6J kompatibel (Smart Charging) - group: Generische Unterstützung -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -description: | - Bei OCPP verbindet sich die Wallbox (Client) zu evcc (Server). - Die Wallbox muss daher evcc via Hostname (funktionierende DNS-Auflösung erforderlich!) oder über die IP-Adresse auf Port 8887 erreichen können. - Standardmäßig wird die erste eingehende Verbindung mit einer beliebigen Ladepunktkennung verwendet. - Um mehrere Ladepunkte eindeutig zuordnen zu können müssen die jeweilige Stationskennung (`stationid: `) und Anschlussnummer (`connector: `) hinterlegt werden. - Viele Wallboxen fügen die `stationid` automatisch der Backend-URL hinzu, bei manchen muss dies manuell geschehen `ws://:8887/`. - Für Zählermesswerte sollte in der Wallbox wenn möglich ein kurzes Zeitintervall (< 10s) konfiguriert werden. - Nutzen Sie Ihre RFID-Tags (dies ermöglicht z. B. eine Fahrzeugidentifizierung) oder setzen Sie Ihre Wallbox auf "freies Laden" oder "Autostart" um die für die Ladefreigabe benötigte Transaktion zu erzeugen. - - Falls die Wallbox keine Möglichkeit bietet die Transaktionen lokal zu starten, kann die erweiterte Option `remotestart` genutzt werden um automatisch eine Transaktion zu starten sobald ein Fahrzeug angeschlossen wird. - Dies sollte nur in Ausnahmefällen erforderlich sein. - - Voraussetzungen: - * Ggf. zuvor konfigurierte OCPP-Profile (z.B. durch eine andere Backend-Anbindung) in der Wallboxkonfiguration entfernen - * Backend-URL (Central System) in der Wallboxkonfiguration: `ws://[evcc-adresse]:8887/` (eventuell noch um `stationid` erweitern) - * Protokoll: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// o.ä. - * Keine Verschlüsselung, keine Authentifizierung, kein Passwort - * Verbindung über das lokale Netzwerk - - Die konkrete Konfiguration und der tatsächlich nutzbare Funktionsumfang hängen vom Wallbox-Modell und dessen Software ab. - -render: - - default: | - type: template - template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/openevse.yaml b/templates/release/de/charger/openevse.yaml new file mode 100644 index 0000000000..e8f35ec886 --- /dev/null +++ b/templates/release/de/charger/openevse.yaml @@ -0,0 +1,41 @@ +template: openevse +product: + identifier: openevse + brand: OpenEVSE +description: | + Benötigt mindestens Firmware 7.0 oder neuer. +render: + - default: | + type: template + template: openevse + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/openevse_0.yaml b/templates/release/de/charger/openevse_0.yaml deleted file mode 100644 index 9920e2ab60..0000000000 --- a/templates/release/de/charger/openevse_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: OpenEVSE -description: | - Benötigt mindestens Firmware 7.0 oder neuer. -render: - - default: | - type: template - template: openevse - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/openwb-2.0_0.yaml b/templates/release/de/charger/openwb-2.0_0.yaml deleted file mode 100644 index e53819d573..0000000000 --- a/templates/release/de/charger/openwb-2.0_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: openWB - description: Software 2.x -capabilities: ["1p3p", "mA", "rfid"] -description: | - Erfordert [`Software 2.x`](https://github.com/openWB/core). - Folgende Änderungen sind unter dem `Einstellungen`-Reiter erforderlich: - - * Steuerungsmodus: `secondary` - * Steuerung über Modbus als secondary: `An` - -render: - - default: | - type: template - template: openwb-2.0 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: openwb-2.0 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional - phases1p3p: true # Phasenumschaltung vorhanden, optional diff --git a/templates/release/de/charger/openwb-pro.yaml b/templates/release/de/charger/openwb-pro.yaml new file mode 100644 index 0000000000..24abd785f5 --- /dev/null +++ b/templates/release/de/charger/openwb-pro.yaml @@ -0,0 +1,21 @@ +template: openwb-pro +product: + identifier: openwb-pro + brand: openWB + description: Pro +capabilities: ["1p3p", "mA", "iso151182"] +render: + - default: | + type: template + template: openwb-pro + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/openwb-pro_0.yaml b/templates/release/de/charger/openwb-pro_0.yaml deleted file mode 100644 index cef53f45b7..0000000000 --- a/templates/release/de/charger/openwb-pro_0.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: openWB - description: Pro -capabilities: ["1p3p", "mA", "iso151182"] -render: - - default: | - type: template - template: openwb-pro - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/openwb-series2.yaml b/templates/release/de/charger/openwb-series2.yaml new file mode 100644 index 0000000000..9ee47fabd8 --- /dev/null +++ b/templates/release/de/charger/openwb-series2.yaml @@ -0,0 +1,46 @@ +template: openwb +product: + identifier: openwb-series2 + brand: openWB + description: series2 +description: | + Die Wallbox muss als Ladepunkt konfiguriert sein. +render: + - default: | + type: template + template: openwb + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: openwb + host: 192.0.2.2 # IP-Adresse oder Hostname + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional + phases1p3p: false # Phasenumschaltung vorhanden, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: Phasenumschaltung vorhanden + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/openwb-software-2-x.yaml b/templates/release/de/charger/openwb-software-2-x.yaml new file mode 100644 index 0000000000..c803661461 --- /dev/null +++ b/templates/release/de/charger/openwb-software-2-x.yaml @@ -0,0 +1,68 @@ +template: openwb-2.0 +product: + identifier: openwb-software-2-x + brand: openWB + description: Software 2.x +capabilities: ["1p3p", "mA", "rfid"] +description: | + Erfordert [`Software 2.x`](https://github.com/openWB/core). + Folgende Änderungen sind unter dem `Einstellungen`-Reiter erforderlich: + + * Steuerungsmodus: `secondary` + * Steuerung über Modbus als secondary: `An` + +render: + - default: | + type: template + template: openwb-2.0 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: openwb-2.0 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional + phases1p3p: true # Phasenumschaltung vorhanden, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true + - name: phases1p3p + example: + default: true + choice: [] + unit: + description: Phasenumschaltung vorhanden + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/openwb_0.yaml b/templates/release/de/charger/openwb_0.yaml deleted file mode 100644 index c74044dcc3..0000000000 --- a/templates/release/de/charger/openwb_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: openWB - description: series2 -description: | - Die Wallbox muss als Ladepunkt konfiguriert sein. -render: - - default: | - type: template - template: openwb - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: openwb - host: 192.0.2.2 # IP-Adresse oder Hostname - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional - phases1p3p: false # Phasenumschaltung vorhanden, optional diff --git a/templates/release/de/charger/optec-mobility-one.yaml b/templates/release/de/charger/optec-mobility-one.yaml new file mode 100644 index 0000000000..a0402b919e --- /dev/null +++ b/templates/release/de/charger/optec-mobility-one.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: optec-mobility-one + brand: Optec + description: Mobility One +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/orbis-viaris.yaml b/templates/release/de/charger/orbis-viaris.yaml new file mode 100644 index 0000000000..5e20b6a215 --- /dev/null +++ b/templates/release/de/charger/orbis-viaris.yaml @@ -0,0 +1,85 @@ +template: ocpp-orbis +product: + identifier: orbis-viaris + brand: Orbis + description: Viaris +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-orbis + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-orbis + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/pantabox_0.yaml b/templates/release/de/charger/pantabox_0.yaml deleted file mode 100644 index eacffea211..0000000000 --- a/templates/release/de/charger/pantabox_0.yaml +++ /dev/null @@ -1,8 +0,0 @@ -product: - brand: INRO - description: Pantabox -render: - - default: | - type: template - template: pantabox - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/pc-electric-garo.yaml b/templates/release/de/charger/pc-electric-garo.yaml new file mode 100644 index 0000000000..999fca325f --- /dev/null +++ b/templates/release/de/charger/pc-electric-garo.yaml @@ -0,0 +1,33 @@ +template: pcelectric-garo +product: + identifier: pc-electric-garo + brand: PC Electric + description: Garo +requirements: ["sponsorship"] +description: | + Es können momentan nur als Master konfigurierte Geräte verwendet werden! +render: + - default: | + type: template + template: pcelectric-garo + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8080 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/pcelectric-garo_0.yaml b/templates/release/de/charger/pcelectric-garo_0.yaml deleted file mode 100644 index 72e8e0b93d..0000000000 --- a/templates/release/de/charger/pcelectric-garo_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: PC Electric - description: Garo -requirements: ["sponsorship"] -description: | - Es können momentan nur als Master konfigurierte Geräte verwendet werden! -render: - - default: | - type: template - template: pcelectric-garo - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional diff --git a/templates/release/de/charger/peblar-business.yaml b/templates/release/de/charger/peblar-business.yaml new file mode 100644 index 0000000000..45be43b2c3 --- /dev/null +++ b/templates/release/de/charger/peblar-business.yaml @@ -0,0 +1,35 @@ +template: peblar +product: + identifier: peblar-business + brand: Peblar + description: Business +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. +render: + - default: | + type: template + template: peblar + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/peblar-home-plus.yaml b/templates/release/de/charger/peblar-home-plus.yaml new file mode 100644 index 0000000000..026ae5d434 --- /dev/null +++ b/templates/release/de/charger/peblar-home-plus.yaml @@ -0,0 +1,35 @@ +template: peblar +product: + identifier: peblar-home-plus + brand: Peblar + description: Home Plus +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. +render: + - default: | + type: template + template: peblar + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/peblar-home.yaml b/templates/release/de/charger/peblar-home.yaml new file mode 100644 index 0000000000..6bc09e6134 --- /dev/null +++ b/templates/release/de/charger/peblar-home.yaml @@ -0,0 +1,35 @@ +template: peblar +product: + identifier: peblar-home + brand: Peblar + description: Home +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. +render: + - default: | + type: template + template: peblar + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/peblar_0.yaml b/templates/release/de/charger/peblar_0.yaml deleted file mode 100644 index aaba4467c9..0000000000 --- a/templates/release/de/charger/peblar_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Peblar - description: Home -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. -render: - - default: | - type: template - template: peblar - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/peblar_1.yaml b/templates/release/de/charger/peblar_1.yaml deleted file mode 100644 index b1a08f4a07..0000000000 --- a/templates/release/de/charger/peblar_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Peblar - description: Home Plus -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. -render: - - default: | - type: template - template: peblar - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/peblar_2.yaml b/templates/release/de/charger/peblar_2.yaml deleted file mode 100644 index 79d496fdde..0000000000 --- a/templates/release/de/charger/peblar_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Peblar - description: Business -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. -render: - - default: | - type: template - template: peblar - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-charx_0.yaml b/templates/release/de/charger/phoenix-charx_0.yaml deleted file mode 100644 index 2b068337e1..0000000000 --- a/templates/release/de/charger/phoenix-charx_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Phoenix Contact - description: CHARX -render: - - default: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/phoenix-charx_1.yaml b/templates/release/de/charger/phoenix-charx_1.yaml deleted file mode 100644 index 000d6b204e..0000000000 --- a/templates/release/de/charger/phoenix-charx_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: LadeFoxx - description: EvLoad -render: - - default: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/phoenix-charx_2.yaml b/templates/release/de/charger/phoenix-charx_2.yaml deleted file mode 100644 index a753dfbbbd..0000000000 --- a/templates/release/de/charger/phoenix-charx_2.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: LadeFoxx - description: Mikro 2.0 -render: - - default: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/phoenix-contact-charx.yaml b/templates/release/de/charger/phoenix-contact-charx.yaml new file mode 100644 index 0000000000..a14778ed35 --- /dev/null +++ b/templates/release/de/charger/phoenix-contact-charx.yaml @@ -0,0 +1,50 @@ +template: phoenix-charx +product: + identifier: phoenix-contact-charx + brand: Phoenix Contact + description: CHARX +render: + - default: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml b/templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml new file mode 100644 index 0000000000..61f1ab493f --- /dev/null +++ b/templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml @@ -0,0 +1,31 @@ +template: phoenix-em-eth +product: + identifier: phoenix-contact-em-cp-pp-eth + brand: Phoenix Contact + description: EM-CP-PP-ETH +render: + - default: | + type: template + template: phoenix-em-eth + + # Modbus TCP + modbus: tcpip + id: 180 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 180 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml new file mode 100644 index 0000000000..a7212791c7 --- /dev/null +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g + brand: Phoenix Contact + description: EV-CC-AC1-M3-CBC-RCM-ETH-3G +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml new file mode 100644 index 0000000000..e97dea064a --- /dev/null +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth + brand: Phoenix Contact + description: EV-CC-AC1-M3-CBC-RCM-ETH +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml new file mode 100644 index 0000000000..857cd048a5 --- /dev/null +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp + brand: Phoenix Contact + description: EV-CC-AC1-M3-RCM-ETH-3G-XP +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml new file mode 100644 index 0000000000..b91663fdcd --- /dev/null +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp + brand: Phoenix Contact + description: EV-CC-AC1-M3-RCM-ETH-XP +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/phoenix-contact-ev-ser.yaml b/templates/release/de/charger/phoenix-contact-ev-ser.yaml new file mode 100644 index 0000000000..ff1e20eb68 --- /dev/null +++ b/templates/release/de/charger/phoenix-contact-ev-ser.yaml @@ -0,0 +1,41 @@ +template: phoenix-ev-ser +product: + identifier: phoenix-contact-ev-ser + brand: Phoenix Contact + description: EV-SER +render: + - default: | + type: template + template: phoenix-ev-ser + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/phoenix-em-eth_0.yaml b/templates/release/de/charger/phoenix-em-eth_0.yaml deleted file mode 100644 index 761efe9d6d..0000000000 --- a/templates/release/de/charger/phoenix-em-eth_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Phoenix Contact - description: EM-CP-PP-ETH -render: - - default: | - type: template - template: phoenix-em-eth - - # Modbus TCP - modbus: tcpip - id: 180 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_0.yaml b/templates/release/de/charger/phoenix-ev-eth_0.yaml deleted file mode 100644 index cd186871fa..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-CBC-RCM-ETH -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_1.yaml b/templates/release/de/charger/phoenix-ev-eth_1.yaml deleted file mode 100644 index cf66636316..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-CBC-RCM-ETH-3G -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_2.yaml b/templates/release/de/charger/phoenix-ev-eth_2.yaml deleted file mode 100644 index 2be0c69263..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-RCM-ETH-XP -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_3.yaml b/templates/release/de/charger/phoenix-ev-eth_3.yaml deleted file mode 100644 index 5aab2de5e7..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-RCM-ETH-3G-XP -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_4.yaml b/templates/release/de/charger/phoenix-ev-eth_4.yaml deleted file mode 100644 index 33434ab164..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Wallbe - description: Eco -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_5.yaml b/templates/release/de/charger/phoenix-ev-eth_5.yaml deleted file mode 100644 index 7bdc73f10c..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_5.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Wallbe - description: Eco 2.0(s) -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_6.yaml b/templates/release/de/charger/phoenix-ev-eth_6.yaml deleted file mode 100644 index 6416af0f0b..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_6.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Wallbe - description: Pro -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_7.yaml b/templates/release/de/charger/phoenix-ev-eth_7.yaml deleted file mode 100644 index 25e23bc1cd..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_7.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: ESL - description: Walli LIGHT -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-eth_8.yaml b/templates/release/de/charger/phoenix-ev-eth_8.yaml deleted file mode 100644 index 47334ad705..0000000000 --- a/templates/release/de/charger/phoenix-ev-eth_8.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: E3/DC - description: Easy Connect -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/phoenix-ev-ser_0.yaml b/templates/release/de/charger/phoenix-ev-ser_0.yaml deleted file mode 100644 index 63128dfb43..0000000000 --- a/templates/release/de/charger/phoenix-ev-ser_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-SER -render: - - default: | - type: template - template: phoenix-ev-ser - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/plugchoice.yaml b/templates/release/de/charger/plugchoice.yaml new file mode 100644 index 0000000000..613685d21e --- /dev/null +++ b/templates/release/de/charger/plugchoice.yaml @@ -0,0 +1,56 @@ +template: plugchoice +product: + identifier: plugchoice + brand: Plugchoice + group: Generische Unterstützung +requirements: ["sponsorship"] +description: | + Über Plugchoice angeschlossene Ladegeräte können die OCPP-Proxy-Funktionalität nutzen, um eine Verbindung zu anderen Backoffices herzustellen und gleichzeitig die volle Kontrolle über EVCC zu behalten. Dies ermöglicht eine nahtlose Verwaltung der bei Plugchoice registrierten Ladegeräte direkt vom EVCC aus. + + Für eine optimierte Zählerablesung empfehlen wir, die folgenden Einstellungen im Plugchoice-Portal unter `Konfiguration` zu konfigurieren: + + – Stellen Sie `MeterValueSampleInterval` auf 10 Sekunden (oder ein anderes Intervall Ihrer Wahl) ein. + – Stellen Sie `MeterValuesSampledData` auf `Energy.Active.Import.Register,Current.Offered,Current.Import,Voltage` ein. + + Diese Anpassungen ermöglichen eine häufigere und detailliertere Meldung der Ladedaten an EVCC. + +render: + - default: | + type: template + template: plugchoice + token: # API Token + identity: # Identity des Ladepunkts (z.B. AA123456) + advanced: | + type: template + template: plugchoice + token: # API Token + identity: # Identity des Ladepunkts (z.B. AA123456) + connector: 1 # Ladepunkt (falls >1 Ladepunkt), Anschluss-ID (üblicherweise 1) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token + advanced: false + optional: false + - name: identity + example: + default: + choice: [] + unit: + description: + help: Identity des Ladepunkts (z.B. AA123456) + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: Anschluss-ID (üblicherweise 1) + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/plugchoice_0.yaml b/templates/release/de/charger/plugchoice_0.yaml deleted file mode 100644 index 92fbdf4e20..0000000000 --- a/templates/release/de/charger/plugchoice_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Plugchoice - group: Generische Unterstützung -requirements: ["sponsorship"] -description: | - Über Plugchoice angeschlossene Ladegeräte können die OCPP-Proxy-Funktionalität nutzen, um eine Verbindung zu anderen Backoffices herzustellen und gleichzeitig die volle Kontrolle über EVCC zu behalten. Dies ermöglicht eine nahtlose Verwaltung der bei Plugchoice registrierten Ladegeräte direkt vom EVCC aus. - - Für eine optimierte Zählerablesung empfehlen wir, die folgenden Einstellungen im Plugchoice-Portal unter `Konfiguration` zu konfigurieren: - - – Stellen Sie `MeterValueSampleInterval` auf 10 Sekunden (oder ein anderes Intervall Ihrer Wahl) ein. - – Stellen Sie `MeterValuesSampledData` auf `Energy.Active.Import.Register,Current.Offered,Current.Import,Voltage` ein. - - Diese Anpassungen ermöglichen eine häufigere und detailliertere Meldung der Ladedaten an EVCC. - -render: - - default: | - type: template - template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456) - advanced: | - type: template - template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456) - connector: 1 # Ladepunkt (falls >1 Ladepunkt), Anschluss-ID (üblicherweise 1) diff --git a/templates/release/de/charger/pmcc_0.yaml b/templates/release/de/charger/pmcc_0.yaml deleted file mode 100644 index d11994fdaa..0000000000 --- a/templates/release/de/charger/pmcc_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: Porsche - description: Mobile Charger Connect -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -render: - - default: | - type: template - template: pmcc - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/pmcp_0.yaml b/templates/release/de/charger/pmcp_0.yaml deleted file mode 100644 index d6d9ae7043..0000000000 --- a/templates/release/de/charger/pmcp_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Porsche - description: Mobile Charger Plus -requirements: ["eebus"] -render: - - default: | - type: template - template: pmcp - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/porsche-mobile-charger-connect.yaml b/templates/release/de/charger/porsche-mobile-charger-connect.yaml new file mode 100644 index 0000000000..38029048e1 --- /dev/null +++ b/templates/release/de/charger/porsche-mobile-charger-connect.yaml @@ -0,0 +1,32 @@ +template: pmcc +product: + identifier: porsche-mobile-charger-connect + brand: Porsche + description: Mobile Charger Connect +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +render: + - default: | + type: template + template: pmcc + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/porsche-mobile-charger-plus.yaml b/templates/release/de/charger/porsche-mobile-charger-plus.yaml new file mode 100644 index 0000000000..26a177db0b --- /dev/null +++ b/templates/release/de/charger/porsche-mobile-charger-plus.yaml @@ -0,0 +1,31 @@ +template: pmcp +product: + identifier: porsche-mobile-charger-plus + brand: Porsche + description: Mobile Charger Plus +requirements: ["eebus"] +render: + - default: | + type: template + template: pmcp + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/porsche-wallbox.yaml b/templates/release/de/charger/porsche-wallbox.yaml new file mode 100644 index 0000000000..9404b73d57 --- /dev/null +++ b/templates/release/de/charger/porsche-wallbox.yaml @@ -0,0 +1,39 @@ +template: porsche-wallbox +product: + identifier: porsche-wallbox + brand: Porsche + description: Wallbox +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: porsche-wallbox + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/porsche-wallbox_0.yaml b/templates/release/de/charger/porsche-wallbox_0.yaml deleted file mode 100644 index 8bd09070f5..0000000000 --- a/templates/release/de/charger/porsche-wallbox_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Porsche - description: Wallbox -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - Die Wallbox muss im normalen Lademodus betrieben werden. - - Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. - - Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. - -render: - - default: | - type: template - template: porsche-wallbox - ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden - ip: 192.0.2.2 # IP-Adresse, optional diff --git a/templates/release/de/charger/pracht-alpha-xt.yaml b/templates/release/de/charger/pracht-alpha-xt.yaml new file mode 100644 index 0000000000..f0ee4ef8c9 --- /dev/null +++ b/templates/release/de/charger/pracht-alpha-xt.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-alpha-xt + brand: Pracht + description: Alpha XT +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/pracht-alpha_0.yaml b/templates/release/de/charger/pracht-alpha_0.yaml deleted file mode 100644 index 4dfb8cfd26..0000000000 --- a/templates/release/de/charger/pracht-alpha_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: Alpha XT -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/pracht-alpha_1.yaml b/templates/release/de/charger/pracht-alpha_1.yaml deleted file mode 100644 index 35708e4845..0000000000 --- a/templates/release/de/charger/pracht-alpha_1.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: XT+ -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/pracht-alpha_2.yaml b/templates/release/de/charger/pracht-alpha_2.yaml deleted file mode 100644 index 5092cc3755..0000000000 --- a/templates/release/de/charger/pracht-alpha_2.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: Mono XT -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/pracht-alpha_3.yaml b/templates/release/de/charger/pracht-alpha_3.yaml deleted file mode 100644 index ee9a1bc7e6..0000000000 --- a/templates/release/de/charger/pracht-alpha_3.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: PNI -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional diff --git a/templates/release/de/charger/pracht-mono-xt.yaml b/templates/release/de/charger/pracht-mono-xt.yaml new file mode 100644 index 0000000000..6bc3139149 --- /dev/null +++ b/templates/release/de/charger/pracht-mono-xt.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-mono-xt + brand: Pracht + description: Mono XT +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/pracht-pni.yaml b/templates/release/de/charger/pracht-pni.yaml new file mode 100644 index 0000000000..b744685fc9 --- /dev/null +++ b/templates/release/de/charger/pracht-pni.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-pni + brand: Pracht + description: PNI +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/pracht-xtplus.yaml b/templates/release/de/charger/pracht-xtplus.yaml new file mode 100644 index 0000000000..21d1aa5b24 --- /dev/null +++ b/templates/release/de/charger/pracht-xtplus.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-xtplus + brand: Pracht + description: XT+ +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Ladepunkt (falls >1 Ladepunkt) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/pulsares-simplebox.yaml b/templates/release/de/charger/pulsares-simplebox.yaml new file mode 100644 index 0000000000..089c80a4d5 --- /dev/null +++ b/templates/release/de/charger/pulsares-simplebox.yaml @@ -0,0 +1,41 @@ +template: pulsares +product: + identifier: pulsares-simplebox + brand: Pulsares + description: SimpleBox +render: + - default: | + type: template + template: pulsares + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/pulsares_0.yaml b/templates/release/de/charger/pulsares_0.yaml deleted file mode 100644 index 3b68b02181..0000000000 --- a/templates/release/de/charger/pulsares_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Pulsares - description: SimpleBox -render: - - default: | - type: template - template: pulsares - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/pulsatrix.yaml b/templates/release/de/charger/pulsatrix.yaml new file mode 100644 index 0000000000..00495b8b4a --- /dev/null +++ b/templates/release/de/charger/pulsatrix.yaml @@ -0,0 +1,20 @@ +template: pulsatrix +product: + identifier: pulsatrix + brand: Pulsatrix +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pulsatrix + host: 192.0.2.2 # IP-Adresse oder Hostname, Wird auf der dritten Displayseite des SECC angezeigt +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: Wird auf der dritten Displayseite des SECC angezeigt + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/pulsatrix_0.yaml b/templates/release/de/charger/pulsatrix_0.yaml deleted file mode 100644 index d26f958865..0000000000 --- a/templates/release/de/charger/pulsatrix_0.yaml +++ /dev/null @@ -1,8 +0,0 @@ -product: - brand: Pulsatrix -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pulsatrix - host: 192.0.2.2 # IP-Adresse oder Hostname, Wird auf der dritten Displayseite des SECC angezeigt diff --git a/templates/release/de/charger/qcells-q-home-edrive-a.yaml b/templates/release/de/charger/qcells-q-home-edrive-a.yaml new file mode 100644 index 0000000000..06b2a2efe0 --- /dev/null +++ b/templates/release/de/charger/qcells-q-home-edrive-a.yaml @@ -0,0 +1,45 @@ +template: solax +product: + identifier: qcells-q-home-edrive-a + brand: Qcells + description: Q.HOME EDRIVE A +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. +render: + - default: | + type: template + template: solax + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 70 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 70 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 70 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/roth-thermoaura.yaml b/templates/release/de/charger/roth-thermoaura.yaml new file mode 100644 index 0000000000..d6599d4798 --- /dev/null +++ b/templates/release/de/charger/roth-thermoaura.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: roth-thermoaura + brand: Roth + description: ThermoAura + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/roth-thermoterra.yaml b/templates/release/de/charger/roth-thermoterra.yaml new file mode 100644 index 0000000000..b1302bab28 --- /dev/null +++ b/templates/release/de/charger/roth-thermoterra.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: roth-thermoterra + brand: Roth + description: ThermoTerra + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/schneider-evlink-pro.yaml b/templates/release/de/charger/schneider-evlink-pro.yaml new file mode 100644 index 0000000000..2204af38ba --- /dev/null +++ b/templates/release/de/charger/schneider-evlink-pro.yaml @@ -0,0 +1,32 @@ +template: schneider-evlink-v3 +product: + identifier: schneider-evlink-pro + brand: Schneider + description: EVlink Pro +requirements: ["sponsorship"] +render: + - default: | + type: template + template: schneider-evlink-v3 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/schneider-evlink-v3_0.yaml b/templates/release/de/charger/schneider-evlink-v3_0.yaml deleted file mode 100644 index 080654a253..0000000000 --- a/templates/release/de/charger/schneider-evlink-v3_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Schneider - description: EVlink Pro -requirements: ["sponsorship"] -render: - - default: | - type: template - template: schneider-evlink-v3 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/schrack-i-charge-cion.yaml b/templates/release/de/charger/schrack-i-charge-cion.yaml new file mode 100644 index 0000000000..921cd93531 --- /dev/null +++ b/templates/release/de/charger/schrack-i-charge-cion.yaml @@ -0,0 +1,41 @@ +template: ichargecion +product: + identifier: schrack-i-charge-cion + brand: Schrack + description: i-CHARGE CION +render: + - default: | + type: template + template: ichargecion + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/senec-wallbox-pro-s.yaml b/templates/release/de/charger/senec-wallbox-pro-s.yaml new file mode 100644 index 0000000000..314cdc6473 --- /dev/null +++ b/templates/release/de/charger/senec-wallbox-pro-s.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: senec-wallbox-pro-s + brand: SENEC + description: Wallbox pro s +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/senec-wallbox-pro.yaml b/templates/release/de/charger/senec-wallbox-pro.yaml new file mode 100644 index 0000000000..bc39234a9b --- /dev/null +++ b/templates/release/de/charger/senec-wallbox-pro.yaml @@ -0,0 +1,53 @@ +template: abl +product: + identifier: senec-wallbox-pro + brand: SENEC + description: Wallbox pro +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true +modbus: + baudrate: 38400 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/shelly-1.yaml b/templates/release/de/charger/shelly-1.yaml new file mode 100644 index 0000000000..a3f7c74131 --- /dev/null +++ b/templates/release/de/charger/shelly-1.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-1 + brand: Shelly + description: 1 + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/shelly-plug-s.yaml b/templates/release/de/charger/shelly-plug-s.yaml new file mode 100644 index 0000000000..8c9faefea4 --- /dev/null +++ b/templates/release/de/charger/shelly-plug-s.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-plug-s + brand: Shelly + description: Plug S + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/shelly-plus-1.yaml b/templates/release/de/charger/shelly-plus-1.yaml new file mode 100644 index 0000000000..ab01f4812c --- /dev/null +++ b/templates/release/de/charger/shelly-plus-1.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-plus-1 + brand: Shelly + description: Plus 1 + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/shelly-pro-1.yaml b/templates/release/de/charger/shelly-pro-1.yaml new file mode 100644 index 0000000000..4de931dfe1 --- /dev/null +++ b/templates/release/de/charger/shelly-pro-1.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-pro-1 + brand: Shelly + description: Pro 1 + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/shelly_0.yaml b/templates/release/de/charger/shelly_0.yaml deleted file mode 100644 index cd0b8d0f0a..0000000000 --- a/templates/release/de/charger/shelly_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Shelly - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: shelly - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: shelly - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/siemens-versicharge-gen3.yaml b/templates/release/de/charger/siemens-versicharge-gen3.yaml new file mode 100644 index 0000000000..c91ceb946e --- /dev/null +++ b/templates/release/de/charger/siemens-versicharge-gen3.yaml @@ -0,0 +1,34 @@ +template: versicharge +product: + identifier: siemens-versicharge-gen3 + brand: Siemens + description: Versicharge GEN3 +requirements: ["sponsorship"] +description: | + Erfordert Firmware >= 2.135 +render: + - default: | + type: template + template: versicharge + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/skoda-charger-connect.yaml b/templates/release/de/charger/skoda-charger-connect.yaml new file mode 100644 index 0000000000..899b112fef --- /dev/null +++ b/templates/release/de/charger/skoda-charger-connect.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: skoda-charger-connect + brand: Skoda + description: Charger Connect +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/skoda-charger-pro-eichrecht.yaml b/templates/release/de/charger/skoda-charger-pro-eichrecht.yaml new file mode 100644 index 0000000000..733a4a5fcb --- /dev/null +++ b/templates/release/de/charger/skoda-charger-pro-eichrecht.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: skoda-charger-pro-eichrecht + brand: Skoda + description: Charger Pro Eichrecht +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/skoda-charger-pro.yaml b/templates/release/de/charger/skoda-charger-pro.yaml new file mode 100644 index 0000000000..685aa667e2 --- /dev/null +++ b/templates/release/de/charger/skoda-charger-pro.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: skoda-charger-pro + brand: Skoda + description: Charger Pro +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/skoda-iv-charger-connect.yaml b/templates/release/de/charger/skoda-iv-charger-connect.yaml new file mode 100644 index 0000000000..e41f5f1204 --- /dev/null +++ b/templates/release/de/charger/skoda-iv-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: skoda-iv-charger-connect + brand: Skoda + description: iV Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/skoda-iv-charger-connectplus.yaml b/templates/release/de/charger/skoda-iv-charger-connectplus.yaml new file mode 100644 index 0000000000..b474be89c0 --- /dev/null +++ b/templates/release/de/charger/skoda-iv-charger-connectplus.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: skoda-iv-charger-connectplus + brand: Skoda + description: iV Charger Connect+ +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +render: + - default: | + type: template + template: ellipro + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/sma-echarger.yaml b/templates/release/de/charger/sma-echarger.yaml new file mode 100644 index 0000000000..8cb9bde403 --- /dev/null +++ b/templates/release/de/charger/sma-echarger.yaml @@ -0,0 +1,44 @@ +template: smaevcharger +product: + identifier: sma-echarger + brand: SMA + description: eCharger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. +render: + - default: | + type: template + template: smaevcharger + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/sma-ev-charger.yaml b/templates/release/de/charger/sma-ev-charger.yaml new file mode 100644 index 0000000000..d9a6f2c1c9 --- /dev/null +++ b/templates/release/de/charger/sma-ev-charger.yaml @@ -0,0 +1,44 @@ +template: smaevcharger +product: + identifier: sma-ev-charger + brand: SMA + description: EV Charger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. +render: + - default: | + type: template + template: smaevcharger + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/smaevcharger_0.yaml b/templates/release/de/charger/smaevcharger_0.yaml deleted file mode 100644 index 89f47e8f1d..0000000000 --- a/templates/release/de/charger/smaevcharger_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: SMA - description: EV Charger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. -render: - - default: | - type: template - template: smaevcharger - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen diff --git a/templates/release/de/charger/smaevcharger_1.yaml b/templates/release/de/charger/smaevcharger_1.yaml deleted file mode 100644 index 7bc3b18232..0000000000 --- a/templates/release/de/charger/smaevcharger_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: SMA - description: eCharger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. -render: - - default: | - type: template - template: smaevcharger - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen diff --git a/templates/release/de/charger/smartevse_0.yaml b/templates/release/de/charger/smartevse_0.yaml deleted file mode 100644 index 4ef89c2ede..0000000000 --- a/templates/release/de/charger/smartevse_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - brand: Edgetech - description: Smart EVSE -capabilities: ["1p3p"] -render: - - default: | - type: template - template: smartevse - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/smartfox-pro-charger.yaml b/templates/release/de/charger/smartfox-pro-charger.yaml new file mode 100644 index 0000000000..488e3de539 --- /dev/null +++ b/templates/release/de/charger/smartfox-pro-charger.yaml @@ -0,0 +1,41 @@ +template: ichargecion +product: + identifier: smartfox-pro-charger + brand: Smartfox + description: Pro Charger +render: + - default: | + type: template + template: ichargecion + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/smartwb.yaml b/templates/release/de/charger/smartwb.yaml new file mode 100644 index 0000000000..f34a51d83e --- /dev/null +++ b/templates/release/de/charger/smartwb.yaml @@ -0,0 +1,19 @@ +template: smartwb +product: + identifier: smartwb + description: smartWB +render: + - default: | + type: template + template: smartwb + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/smartwb_0.yaml b/templates/release/de/charger/smartwb_0.yaml deleted file mode 100644 index f98b8afc17..0000000000 --- a/templates/release/de/charger/smartwb_0.yaml +++ /dev/null @@ -1,7 +0,0 @@ -product: - description: smartWB -render: - - default: | - type: template - template: smartwb - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/solaredge-home-ev-charger.yaml b/templates/release/de/charger/solaredge-home-ev-charger.yaml new file mode 100644 index 0000000000..726e707bdd --- /dev/null +++ b/templates/release/de/charger/solaredge-home-ev-charger.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: solaredge-home-ev-charger + brand: SolarEdge + description: Home EV Charger +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/solax-x3-evc.yaml b/templates/release/de/charger/solax-x3-evc.yaml new file mode 100644 index 0000000000..da82455cc4 --- /dev/null +++ b/templates/release/de/charger/solax-x3-evc.yaml @@ -0,0 +1,45 @@ +template: solax +product: + identifier: solax-x3-evc + brand: Solax + description: X3-EVC +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. +render: + - default: | + type: template + template: solax + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 70 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 70 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 70 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/solax_0.yaml b/templates/release/de/charger/solax_0.yaml deleted file mode 100644 index 05065ed30e..0000000000 --- a/templates/release/de/charger/solax_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Solax - description: X3-EVC -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. -render: - - default: | - type: template - template: solax - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 70 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 70 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/solax_1.yaml b/templates/release/de/charger/solax_1.yaml deleted file mode 100644 index d608c09255..0000000000 --- a/templates/release/de/charger/solax_1.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Tigo - description: GO EV Charger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. -render: - - default: | - type: template - template: solax - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 70 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 70 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/solax_2.yaml b/templates/release/de/charger/solax_2.yaml deleted file mode 100644 index 24f484d8e3..0000000000 --- a/templates/release/de/charger/solax_2.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Qcells - description: Q.HOME EDRIVE A -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. -render: - - default: | - type: template - template: solax - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 70 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 70 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/sonnen-sonnencharger.yaml b/templates/release/de/charger/sonnen-sonnencharger.yaml new file mode 100644 index 0000000000..5920ce43d2 --- /dev/null +++ b/templates/release/de/charger/sonnen-sonnencharger.yaml @@ -0,0 +1,34 @@ +template: etrel +product: + identifier: sonnen-sonnencharger + brand: Sonnen + description: sonnenCharger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss sich im "Power" Modus befinden. +render: + - default: | + type: template + template: etrel + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml b/templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml new file mode 100644 index 0000000000..323466109a --- /dev/null +++ b/templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: spelsberg-wallbox-smart-pro + brand: Spelsberg + description: Wallbox Smart Pro +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/stark-in-strom-easy.yaml b/templates/release/de/charger/stark-in-strom-easy.yaml new file mode 100644 index 0000000000..34909a8afe --- /dev/null +++ b/templates/release/de/charger/stark-in-strom-easy.yaml @@ -0,0 +1,41 @@ +template: evse-din +product: + identifier: stark-in-strom-easy + brand: Stark in Strom + description: Easy +render: + - default: | + type: template + template: evse-din + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml b/templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml new file mode 100644 index 0000000000..f735a994e9 --- /dev/null +++ b/templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml @@ -0,0 +1,42 @@ +template: stiebel-lwa +product: + identifier: stiebel-eltron-lwa-lwz-sg-ready + brand: Stiebel Eltron + description: LWA/LWZ (SG Ready) + group: Wärmeerzeuger +render: + - default: | + type: template + template: stiebel-lwa + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperaturquelle, [warmwater] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml b/templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml new file mode 100644 index 0000000000..ff996cefa1 --- /dev/null +++ b/templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml @@ -0,0 +1,42 @@ +template: stiebel-wpm +product: + identifier: stiebel-eltron-wpm-sg-ready + brand: Stiebel Eltron + description: WPM (SG Ready) + group: Wärmeerzeuger +render: + - default: | + type: template + template: stiebel-wpm + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperaturquelle, [warmwater, buffer] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/stiebel-lwa_0.yaml b/templates/release/de/charger/stiebel-lwa_0.yaml deleted file mode 100644 index 5b8f2235c6..0000000000 --- a/templates/release/de/charger/stiebel-lwa_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Stiebel Eltron - description: LWA/LWZ (SG Ready) - group: Wärmeerzeuger -render: - - default: | - type: template - template: stiebel-lwa - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperaturquelle, [warmwater] (optional) diff --git a/templates/release/de/charger/stiebel-lwa_1.yaml b/templates/release/de/charger/stiebel-lwa_1.yaml deleted file mode 100644 index 30859d9c1a..0000000000 --- a/templates/release/de/charger/stiebel-lwa_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Tecalor - description: THZ (SG Ready) - group: Wärmeerzeuger -render: - - default: | - type: template - template: stiebel-lwa - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperaturquelle, [warmwater] (optional) diff --git a/templates/release/de/charger/stiebel-wpm_0.yaml b/templates/release/de/charger/stiebel-wpm_0.yaml deleted file mode 100644 index 2ffc3d6fb5..0000000000 --- a/templates/release/de/charger/stiebel-wpm_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Stiebel Eltron - description: WPM (SG Ready) - group: Wärmeerzeuger -render: - - default: | - type: template - template: stiebel-wpm - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperaturquelle, [warmwater, buffer] (optional) diff --git a/templates/release/de/charger/sungrow-ac011e-01.yaml b/templates/release/de/charger/sungrow-ac011e-01.yaml new file mode 100644 index 0000000000..5b3e3e81ce --- /dev/null +++ b/templates/release/de/charger/sungrow-ac011e-01.yaml @@ -0,0 +1,50 @@ +template: sungrow +product: + identifier: sungrow-ac011e-01 + brand: Sungrow + description: AC011E-01 +capabilities: ["mA", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: sungrow + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 248 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 248 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/sungrow-ac011e.yaml b/templates/release/de/charger/sungrow-ac011e.yaml new file mode 100644 index 0000000000..b9fe80048c --- /dev/null +++ b/templates/release/de/charger/sungrow-ac011e.yaml @@ -0,0 +1,86 @@ +template: ocpp-sungrow +product: + identifier: sungrow-ac011e + brand: Sungrow + description: AC011E +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-sungrow + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-sungrow + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/sungrow-ac22e-01.yaml b/templates/release/de/charger/sungrow-ac22e-01.yaml new file mode 100644 index 0000000000..64254227f2 --- /dev/null +++ b/templates/release/de/charger/sungrow-ac22e-01.yaml @@ -0,0 +1,50 @@ +template: sungrow +product: + identifier: sungrow-ac22e-01 + brand: Sungrow + description: AC22E-01 +capabilities: ["mA", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: sungrow + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 248 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 248 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/sungrow_0.yaml b/templates/release/de/charger/sungrow_0.yaml deleted file mode 100644 index 84322afc67..0000000000 --- a/templates/release/de/charger/sungrow_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Sungrow - description: AC011E-01 -capabilities: ["mA", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: sungrow - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 248 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/sungrow_1.yaml b/templates/release/de/charger/sungrow_1.yaml deleted file mode 100644 index 13687bf675..0000000000 --- a/templates/release/de/charger/sungrow_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Sungrow - description: AC22E-01 -capabilities: ["mA", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: sungrow - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 248 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/tapo_0.yaml b/templates/release/de/charger/tapo_0.yaml deleted file mode 100644 index 691ea518a5..0000000000 --- a/templates/release/de/charger/tapo_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: TP-Link - description: Tapo P-Series Smart Plug - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: tapo - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: tapo - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/tasmota-single-phase.yaml b/templates/release/de/charger/tasmota-single-phase.yaml new file mode 100644 index 0000000000..34eec6a8ed --- /dev/null +++ b/templates/release/de/charger/tasmota-single-phase.yaml @@ -0,0 +1,99 @@ +template: tasmota +product: + identifier: tasmota-single-phase + brand: Tasmota + description: einphasig + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: tasmota + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 1 # Schaltkanal Nummer, Schaltkanal (1-8) + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: tasmota + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 1 # Schaltkanal Nummer, Schaltkanal (1-8) + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Standard-User ist admin + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 1 + choice: [] + unit: + description: Schaltkanal Nummer + help: Schaltkanal (1-8) + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/tasmota_0.yaml b/templates/release/de/charger/tasmota_0.yaml deleted file mode 100644 index 2d99cb82c9..0000000000 --- a/templates/release/de/charger/tasmota_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Tasmota - description: einphasig - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: tasmota - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 1 # Schaltkanal Nummer, Schaltkanal (1-8) - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: tasmota - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 1 # Schaltkanal Nummer, Schaltkanal (1-8) - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/tecalor-thz-sg-ready.yaml b/templates/release/de/charger/tecalor-thz-sg-ready.yaml new file mode 100644 index 0000000000..d20c72b300 --- /dev/null +++ b/templates/release/de/charger/tecalor-thz-sg-ready.yaml @@ -0,0 +1,42 @@ +template: stiebel-lwa +product: + identifier: tecalor-thz-sg-ready + brand: Tecalor + description: THZ (SG Ready) + group: Wärmeerzeuger +render: + - default: | + type: template + template: stiebel-lwa + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperaturquelle, [warmwater] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/technisat-technivolt.yaml b/templates/release/de/charger/technisat-technivolt.yaml new file mode 100644 index 0000000000..965528d401 --- /dev/null +++ b/templates/release/de/charger/technisat-technivolt.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: technisat-technivolt + brand: TechniSat + description: Technivolt +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/tesla-wall-connector-gen-3.yaml b/templates/release/de/charger/tesla-wall-connector-gen-3.yaml new file mode 100644 index 0000000000..7ec06ed58f --- /dev/null +++ b/templates/release/de/charger/tesla-wall-connector-gen-3.yaml @@ -0,0 +1,22 @@ +template: twc3 +product: + identifier: tesla-wall-connector-gen-3 + brand: Tesla + description: Wall Connector (Gen 3) +description: | + Die TWC Wallbox ist nicht direkt regelbar. Die Regelung erfolgt über das Fahrzeug. Das Fahrzeug muss am TWC3 Ladepunkt ausgewählt sein. Aktuell ausschließlich mit [Tesla Fahrzeugen](https://docs.evcc.io/docs/devices/vehicles#tesla) nutzbar. +render: + - default: | + type: template + template: twc3 + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/tessie.yaml b/templates/release/de/charger/tessie.yaml new file mode 100644 index 0000000000..00fe8ef9d3 --- /dev/null +++ b/templates/release/de/charger/tessie.yaml @@ -0,0 +1,41 @@ +template: tessie +product: + identifier: tessie + description: Tessie +description: | + Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung des Ladezustands und die Konfiguration des maximalen Stroms. +render: + - default: | + type: template + template: tessie + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + token: # Tessie API Token + location: tessiehome # Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) +params: + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Tessie API Token + help: + advanced: false + optional: false + - name: location + example: tessiehome + default: + choice: [] + unit: + description: Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/tessie_0.yaml b/templates/release/de/charger/tessie_0.yaml deleted file mode 100644 index 763f872d56..0000000000 --- a/templates/release/de/charger/tessie_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - description: Tessie -description: | - Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung des Ladezustands und die Konfiguration des maximalen Stroms. -render: - - default: | - type: template - template: tessie - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - token: # Tessie API Token - location: tessiehome # Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) diff --git a/templates/release/de/charger/tigo-go-ev-charger.yaml b/templates/release/de/charger/tigo-go-ev-charger.yaml new file mode 100644 index 0000000000..0f43a25eed --- /dev/null +++ b/templates/release/de/charger/tigo-go-ev-charger.yaml @@ -0,0 +1,45 @@ +template: solax +product: + identifier: tigo-go-ev-charger + brand: Tigo + description: GO EV Charger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. +render: + - default: | + type: template + template: solax + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 70 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 70 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 70 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/tinkerforge-warp-charger-pro.yaml b/templates/release/de/charger/tinkerforge-warp-charger-pro.yaml new file mode 100644 index 0000000000..d99a541211 --- /dev/null +++ b/templates/release/de/charger/tinkerforge-warp-charger-pro.yaml @@ -0,0 +1,92 @@ +template: tinkerforge-warp +product: + identifier: tinkerforge-warp-charger-pro + brand: TinkerForge + description: WARP Charger Pro +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +description: | + WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. +render: + - default: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + advanced: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: IP Adresse oder der Hostname des MQTT Brokers + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT Broker Port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (ohne / am Anfang) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Zeitüberschreitung + help: Akzeptiere keine Daten die älter sind als dieser Wert + advanced: false + optional: true + - name: energymanager + example: + default: + choice: [] + unit: + description: + help: WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/tinkerforge-warp-charger-smart.yaml b/templates/release/de/charger/tinkerforge-warp-charger-smart.yaml new file mode 100644 index 0000000000..d2a718362a --- /dev/null +++ b/templates/release/de/charger/tinkerforge-warp-charger-smart.yaml @@ -0,0 +1,92 @@ +template: tinkerforge-warp +product: + identifier: tinkerforge-warp-charger-smart + brand: TinkerForge + description: WARP Charger Smart +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +description: | + WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. +render: + - default: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + advanced: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: IP Adresse oder der Hostname des MQTT Brokers + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT Broker Port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (ohne / am Anfang) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Zeitüberschreitung + help: Akzeptiere keine Daten die älter sind als dieser Wert + advanced: false + optional: true + - name: energymanager + example: + default: + choice: [] + unit: + description: + help: WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/tinkerforge-warp3-charger-pro.yaml b/templates/release/de/charger/tinkerforge-warp3-charger-pro.yaml new file mode 100644 index 0000000000..4dae9f1ca8 --- /dev/null +++ b/templates/release/de/charger/tinkerforge-warp3-charger-pro.yaml @@ -0,0 +1,81 @@ +template: tinkerforge-warp3 +product: + identifier: tinkerforge-warp3-charger-pro + brand: TinkerForge + description: WARP3 Charger Pro +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +description: | + Die automatische Phasenumschaltung bei 1p Fahrzeugen muss deaktiviert sein. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. +render: + - default: | + type: template + template: tinkerforge-warp3 + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + advanced: | + type: template + template: tinkerforge-warp3 + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: IP Adresse oder der Hostname des MQTT Brokers + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT Broker Port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (ohne / am Anfang) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Zeitüberschreitung + help: Akzeptiere keine Daten die älter sind als dieser Wert + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/tinkerforge-warp3-charger-smart.yaml b/templates/release/de/charger/tinkerforge-warp3-charger-smart.yaml new file mode 100644 index 0000000000..190a59edfb --- /dev/null +++ b/templates/release/de/charger/tinkerforge-warp3-charger-smart.yaml @@ -0,0 +1,79 @@ +template: tinkerforge-warp3-smart +product: + identifier: tinkerforge-warp3-charger-smart + brand: TinkerForge + description: WARP3 Charger Smart +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: tinkerforge-warp3-smart + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + advanced: | + type: template + template: tinkerforge-warp3-smart + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: warp # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: IP Adresse oder der Hostname des MQTT Brokers + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT Broker Port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (ohne / am Anfang) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Zeitüberschreitung + help: Akzeptiere keine Daten die älter sind als dieser Wert + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/tinkerforge-warp3-smart_0.yaml b/templates/release/de/charger/tinkerforge-warp3-smart_0.yaml deleted file mode 100644 index 777edb0dd7..0000000000 --- a/templates/release/de/charger/tinkerforge-warp3-smart_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: TinkerForge - description: WARP3 Charger Smart -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: tinkerforge-warp3-smart - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - advanced: | - type: template - template: tinkerforge-warp3-smart - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/tinkerforge-warp3_0.yaml b/templates/release/de/charger/tinkerforge-warp3_0.yaml deleted file mode 100644 index d89068290c..0000000000 --- a/templates/release/de/charger/tinkerforge-warp3_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: TinkerForge - description: WARP3 Charger Pro -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -description: | - Die automatische Phasenumschaltung bei 1p Fahrzeugen muss deaktiviert sein. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. -render: - - default: | - type: template - template: tinkerforge-warp3 - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - advanced: | - type: template - template: tinkerforge-warp3 - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/tinkerforge-warp_0.yaml b/templates/release/de/charger/tinkerforge-warp_0.yaml deleted file mode 100644 index 99329162a8..0000000000 --- a/templates/release/de/charger/tinkerforge-warp_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: TinkerForge - description: WARP Charger Smart -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -description: | - WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. -render: - - default: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) - advanced: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/tinkerforge-warp_1.yaml b/templates/release/de/charger/tinkerforge-warp_1.yaml deleted file mode 100644 index dc6fcf72de..0000000000 --- a/templates/release/de/charger/tinkerforge-warp_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: TinkerForge - description: WARP Charger Pro -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -description: | - WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. -render: - - default: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) - advanced: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: warp # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/tp-link-h-series-smart-plug.yaml b/templates/release/de/charger/tp-link-h-series-smart-plug.yaml new file mode 100644 index 0000000000..e02bc6028f --- /dev/null +++ b/templates/release/de/charger/tp-link-h-series-smart-plug.yaml @@ -0,0 +1,66 @@ +template: tplink +product: + identifier: tp-link-h-series-smart-plug + brand: TP-Link + description: H-Series Smart Plug + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: tplink + host: 192.0.2.2 # IP-Adresse oder Hostname + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: tplink + host: 192.0.2.2 # IP-Adresse oder Hostname + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/tp-link-tapo-p-series-smart-plug.yaml b/templates/release/de/charger/tp-link-tapo-p-series-smart-plug.yaml new file mode 100644 index 0000000000..a70bc3ff4e --- /dev/null +++ b/templates/release/de/charger/tp-link-tapo-p-series-smart-plug.yaml @@ -0,0 +1,88 @@ +template: tapo +product: + identifier: tp-link-tapo-p-series-smart-plug + brand: TP-Link + description: Tapo P-Series Smart Plug + group: Schaltbare Steckdosen +render: + - default: | + type: template + template: tapo + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + advanced: | + type: template + template: tapo + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) + integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) + heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) + icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby-Leistung + help: Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integriertes Gerät + help: Fest angeschlossenes Gerät. Keine Ladevorgänge + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Wärmeerzeuger + help: Zeigt °C anstatt % an + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/tplink_0.yaml b/templates/release/de/charger/tplink_0.yaml deleted file mode 100644 index 862457b9e4..0000000000 --- a/templates/release/de/charger/tplink_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: TP-Link - description: H-Series Smart Plug - group: Schaltbare Steckdosen -render: - - default: | - type: template - template: tplink - host: 192.0.2.2 # IP-Adresse oder Hostname - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - advanced: | - type: template - template: tplink - host: 192.0.2.2 # IP-Adresse oder Hostname - standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) - heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) - icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/de/charger/trydan_0.yaml b/templates/release/de/charger/trydan_0.yaml deleted file mode 100644 index 2bda8f5e1b..0000000000 --- a/templates/release/de/charger/trydan_0.yaml +++ /dev/null @@ -1,8 +0,0 @@ -product: - brand: V2C Trydan -requirements: ["sponsorship"] -render: - - default: | - type: template - template: trydan - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/twc3_0.yaml b/templates/release/de/charger/twc3_0.yaml deleted file mode 100644 index 79f79c6e57..0000000000 --- a/templates/release/de/charger/twc3_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Tesla - description: Wall Connector (Gen 3) -description: | - Die TWC Wallbox ist nicht direkt regelbar. Die Regelung erfolgt über das Fahrzeug. Das Fahrzeug muss am TWC3 Ladepunkt ausgewählt sein. Aktuell ausschließlich mit [Tesla Fahrzeugen](https://docs.evcc.io/docs/devices/vehicles#tesla) nutzbar. -render: - - default: | - type: template - template: twc3 - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/ubitricity-heinz.yaml b/templates/release/de/charger/ubitricity-heinz.yaml new file mode 100644 index 0000000000..59638f5b2b --- /dev/null +++ b/templates/release/de/charger/ubitricity-heinz.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: ubitricity-heinz + brand: Ubitricity + description: Heinz +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/v2c-trydan.yaml b/templates/release/de/charger/v2c-trydan.yaml new file mode 100644 index 0000000000..08cd5c6cc9 --- /dev/null +++ b/templates/release/de/charger/v2c-trydan.yaml @@ -0,0 +1,20 @@ +template: trydan +product: + identifier: v2c-trydan + brand: V2C Trydan +requirements: ["sponsorship"] +render: + - default: | + type: template + template: trydan + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/vaillant-sensonet-sg-ready.yaml b/templates/release/de/charger/vaillant-sensonet-sg-ready.yaml new file mode 100644 index 0000000000..9f42ea2ffb --- /dev/null +++ b/templates/release/de/charger/vaillant-sensonet-sg-ready.yaml @@ -0,0 +1,63 @@ +template: vaillant +product: + identifier: vaillant-sensonet-sg-ready + brand: Vaillant + description: SensoNET (SG Ready) + group: Wärmeerzeuger +description: | + Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird durch die ID identifiziert. Die Boost Temperatur wird in Grad Celsius angegeben. Ist eine Boost Temperatur angegeben, wird die Boostzone aktiviert, anderenfalls Warmwasser. +render: + - default: | + type: template + template: vaillant + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + realm: DE # [DE, AT] (optional) + zone: # Id der Boostzone (optional) + setpoint: # Boost Temperatur (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: realm + example: + default: DE + choice: ['DE', 'AT'] + unit: + description: + help: + advanced: false + optional: true + - name: zone + example: + default: + choice: [] + unit: + description: + help: Id der Boostzone + advanced: false + optional: true + - name: setpoint + example: + default: + choice: [] + unit: + description: + help: Boost Temperatur + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/vaillant_0.yaml b/templates/release/de/charger/vaillant_0.yaml deleted file mode 100644 index 5192cd5876..0000000000 --- a/templates/release/de/charger/vaillant_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Vaillant - description: SensoNET (SG Ready) - group: Wärmeerzeuger -description: | - Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird durch die ID identifiziert. Die Boost Temperatur wird in Grad Celsius angegeben. Ist eine Boost Temperatur angegeben, wird die Boostzone aktiviert, anderenfalls Warmwasser. -render: - - default: | - type: template - template: vaillant - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - realm: DE # [DE, AT] (optional) - zone: # Id der Boostzone (optional) - setpoint: # Boost Temperatur (optional) diff --git a/templates/release/de/charger/versicharge_0.yaml b/templates/release/de/charger/versicharge_0.yaml deleted file mode 100644 index 6f095ac40e..0000000000 --- a/templates/release/de/charger/versicharge_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Siemens - description: Versicharge GEN3 -requirements: ["sponsorship"] -description: | - Erfordert Firmware >= 2.135 -render: - - default: | - type: template - template: versicharge - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/vestel-connect-plus.yaml b/templates/release/de/charger/vestel-connect-plus.yaml new file mode 100644 index 0000000000..d5ad92c1b4 --- /dev/null +++ b/templates/release/de/charger/vestel-connect-plus.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: vestel-connect-plus + brand: Vestel + description: Connect Plus +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/vestel-evc04-home-smart.yaml b/templates/release/de/charger/vestel-evc04-home-smart.yaml new file mode 100644 index 0000000000..16b6d6a113 --- /dev/null +++ b/templates/release/de/charger/vestel-evc04-home-smart.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: vestel-evc04-home-smart + brand: Vestel + description: EVC04 Home Smart +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/vestel_0.yaml b/templates/release/de/charger/vestel_0.yaml deleted file mode 100644 index c3da79ac2f..0000000000 --- a/templates/release/de/charger/vestel_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ampure - description: Unite -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/vestel_1.yaml b/templates/release/de/charger/vestel_1.yaml deleted file mode 100644 index 84470c63e1..0000000000 --- a/templates/release/de/charger/vestel_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Vestel - description: EVC04 Home Smart -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/vestel_2.yaml b/templates/release/de/charger/vestel_2.yaml deleted file mode 100644 index c677bc61dc..0000000000 --- a/templates/release/de/charger/vestel_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Vestel - description: Connect Plus -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/vestel_3.yaml b/templates/release/de/charger/vestel_3.yaml deleted file mode 100644 index 8f23c8bdae..0000000000 --- a/templates/release/de/charger/vestel_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Webasto - description: Unite -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/vestel_4.yaml b/templates/release/de/charger/vestel_4.yaml deleted file mode 100644 index e3c651bcc0..0000000000 --- a/templates/release/de/charger/vestel_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: E.ON Drive - description: vBox -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/victron-ev-charging-station-via-gx.yaml b/templates/release/de/charger/victron-ev-charging-station-via-gx.yaml new file mode 100644 index 0000000000..f4cd502869 --- /dev/null +++ b/templates/release/de/charger/victron-ev-charging-station-via-gx.yaml @@ -0,0 +1,33 @@ +template: victron +product: + identifier: victron-ev-charging-station-via-gx + brand: Victron + description: EV Charging Station (via GX) +description: | + Trage den Host des GX-Gerätes (nicht der Wallbox) ein. Die Wallbox muss sich im Modus "Manual" befinden und Modbus ID 100 konfiguriert sein. +render: + - default: | + type: template + template: victron + + # Modbus TCP + modbus: tcpip + id: 100 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 100 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/victron-ev-charging-station.yaml b/templates/release/de/charger/victron-ev-charging-station.yaml new file mode 100644 index 0000000000..0f34cb551e --- /dev/null +++ b/templates/release/de/charger/victron-ev-charging-station.yaml @@ -0,0 +1,33 @@ +template: victron-evcs +product: + identifier: victron-ev-charging-station + brand: Victron + description: EV Charging Station +description: | + Trage den Host der Wallbox (nicht des GX-Geräts) ein und stelle sicher, dass die Wallbox sich im Modus "Manual" befindet. +render: + - default: | + type: template + template: victron-evcs + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/victron-evcs_0.yaml b/templates/release/de/charger/victron-evcs_0.yaml deleted file mode 100644 index 410967397f..0000000000 --- a/templates/release/de/charger/victron-evcs_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Victron - description: EV Charging Station -description: | - Trage den Host der Wallbox (nicht des GX-Geräts) ein und stelle sicher, dass die Wallbox sich im Modus "Manual" befindet. -render: - - default: | - type: template - template: victron-evcs - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/victron_0.yaml b/templates/release/de/charger/victron_0.yaml deleted file mode 100644 index 7e0a575de3..0000000000 --- a/templates/release/de/charger/victron_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Victron - description: EV Charging Station (via GX) -description: | - Trage den Host des GX-Gerätes (nicht der Wallbox) ein. Die Wallbox muss sich im Modus "Manual" befinden und Modbus ID 100 konfiguriert sein. -render: - - default: | - type: template - template: victron - - # Modbus TCP - modbus: tcpip - id: 100 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/charger/viessmann-heatpump-sg-ready.yaml b/templates/release/de/charger/viessmann-heatpump-sg-ready.yaml new file mode 100644 index 0000000000..b60f612e36 --- /dev/null +++ b/templates/release/de/charger/viessmann-heatpump-sg-ready.yaml @@ -0,0 +1,85 @@ +template: viessmann +product: + identifier: viessmann-heatpump-sg-ready + brand: Viessmann + description: Heatpump (SG Ready) + group: Wärmeerzeuger +requirements: ["skiptest"] +description: | + Einmalige Warmwasserbereitung auf eine konfigurierbare Solltemperatur. Das Gerät entscheidet eigenständig, ob die Wärmepumpe oder die elektrische Zusatzheizung (falls vorhanden) genutzt wird. + +render: + - default: | + type: template + template: viessmann + user: # Benutzerkonto, Registrieren auf [app.developer.viessmann.com](https://app.developer.viessmann.com) + password: # Passwort, Für den konfigurierten Viessmann Account. + clientid: # Client ID, Konfigurieren in [app.developer.viessmann.com](https://app.developer.viessmann.com) + gateway_serial: # Gateway Serial, Seriennummer des VitoConnect modul (VitoCare App -> Einstellungen -> Kommunikationsmodul -> Seriennummer) + installation_id: # Installation ID, Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...
Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable 'CODE' nur 20 Sekunden gültig ist): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\?code=\(.*\).*/\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) ``` Damit können wir jetzt die Installation ID abfragen: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' ``` + device_id: 0 # Device ID, normalerweise `0` + target_temperature: 45 # Zieltemperatur für Einmal-Warmwasser-Zubereitung (°C), max. 60°C +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Registrieren auf [app.developer.viessmann.com](https://app.developer.viessmann.com) + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Für den konfigurierten Viessmann Account. + advanced: false + optional: false + - name: clientid + example: + default: + choice: [] + unit: + description: Client ID + help: Konfigurieren in [app.developer.viessmann.com](https://app.developer.viessmann.com) + advanced: false + optional: false + - name: gateway_serial + example: + default: + choice: [] + unit: + description: Gateway Serial + help: Seriennummer des VitoConnect modul (VitoCare App -> Einstellungen -> Kommunikationsmodul -> Seriennummer) + advanced: false + optional: false + - name: installation_id + example: + default: + choice: [] + unit: + description: Installation ID + help: 'Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...
Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable ''CODE'' nur 20 Sekunden gültig ist): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed ''s/.*\?code=\(.*\).*/\1/'' \ | tr -d ''[:space:]'') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) ``` Damit können wir jetzt die Installation ID abfragen: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq ''.data[].id'' ```' + advanced: false + optional: false + - name: device_id + example: + default: 0 + choice: [] + unit: + description: Device ID + help: normalerweise `0` + advanced: false + optional: false + - name: target_temperature + example: + default: 45 + choice: [] + unit: °C + description: Zieltemperatur für Einmal-Warmwasser-Zubereitung + help: max. 60°C + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/viessmann_0.yaml b/templates/release/de/charger/viessmann_0.yaml deleted file mode 100644 index 5f39bb4b16..0000000000 --- a/templates/release/de/charger/viessmann_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Viessmann - description: Heatpump (SG Ready) - group: Wärmeerzeuger -requirements: ["skiptest"] -description: | - Einmalige Warmwasserbereitung auf eine konfigurierbare Solltemperatur. Das Gerät entscheidet eigenständig, ob die Wärmepumpe oder die elektrische Zusatzheizung (falls vorhanden) genutzt wird. - -render: - - default: | - type: template - template: viessmann - user: # Benutzerkonto, Registrieren auf [app.developer.viessmann.com](https://app.developer.viessmann.com) - password: # Passwort, Für den konfigurierten Viessmann Account. - clientid: # Client ID, Konfigurieren in [app.developer.viessmann.com](https://app.developer.viessmann.com) - gateway_serial: # Gateway Serial, Seriennummer des VitoConnect modul (VitoCare App -> Einstellungen -> Kommunikationsmodul -> Seriennummer) - installation_id: # Installation ID, Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...
Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable 'CODE' nur 20 Sekunden gültig ist): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\?code=\(.*\).*/\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) ``` Damit können wir jetzt die Installation ID abfragen: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' ``` - device_id: 0 # Device ID, normalerweise `0` - target_temperature: 45 # Zieltemperatur für Einmal-Warmwasser-Zubereitung (°C), max. 60°C diff --git a/templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml b/templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml new file mode 100644 index 0000000000..53ecd1be96 --- /dev/null +++ b/templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml @@ -0,0 +1,48 @@ +template: obo +product: + identifier: viridian-ev-evse-epc-2-0-plus + brand: Viridian EV + description: EVSE EPC 2.0 Plus +render: + - default: | + type: template + template: obo + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 101 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 101 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/volkswagen-charger-connect-2.yaml b/templates/release/de/charger/volkswagen-charger-connect-2.yaml new file mode 100644 index 0000000000..24e3e0dbf7 --- /dev/null +++ b/templates/release/de/charger/volkswagen-charger-connect-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: volkswagen-charger-connect-2 + brand: Volkswagen + description: Charger Connect 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/volkswagen-charger-pro-2.yaml b/templates/release/de/charger/volkswagen-charger-pro-2.yaml new file mode 100644 index 0000000000..5c1d275190 --- /dev/null +++ b/templates/release/de/charger/volkswagen-charger-pro-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: volkswagen-charger-pro-2 + brand: Volkswagen + description: Charger Pro 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/volkswagen-charger-pro-eichrecht-2.yaml b/templates/release/de/charger/volkswagen-charger-pro-eichrecht-2.yaml new file mode 100644 index 0000000000..b737830722 --- /dev/null +++ b/templates/release/de/charger/volkswagen-charger-pro-eichrecht-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: volkswagen-charger-pro-eichrecht-2 + brand: Volkswagen + description: Charger Pro Eichrecht 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + Die Wallbox muss im normalen Lademodus betrieben werden. + + Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + +render: + - default: | + type: template + template: elli-2 + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/volkswagen-id-charger-connect.yaml b/templates/release/de/charger/volkswagen-id-charger-connect.yaml new file mode 100644 index 0000000000..7c37ec6de5 --- /dev/null +++ b/templates/release/de/charger/volkswagen-id-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: volkswagen-id-charger-connect + brand: Volkswagen + description: ID. Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + + Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt hast, nutze bitte die Pro bzw. Connected+ Integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/volkswagen-id-charger-pro.yaml b/templates/release/de/charger/volkswagen-id-charger-pro.yaml new file mode 100644 index 0000000000..2df57dd479 --- /dev/null +++ b/templates/release/de/charger/volkswagen-id-charger-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: volkswagen-id-charger-pro + brand: Volkswagen + description: ID. Charger Pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). + + Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-Fehlern in der Wallbox nur mit einem externen Energiezähler und ohne Stromwandlerspulen möglich! Eine LAN Anbindung wird sehr empfohlen. + +render: + - default: | + type: template + template: ellipro + ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden + ip: 192.0.2.2 # IP-Adresse, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Identifikationsschlüssel (SKI) + help: Üblicherweise im Web Interface der Wallbox zu finden + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/volt-time-one.yaml b/templates/release/de/charger/volt-time-one.yaml new file mode 100644 index 0000000000..545bda3266 --- /dev/null +++ b/templates/release/de/charger/volt-time-one.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-one + brand: Volt Time + description: One +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer (z. B. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Seriennummer (z. B. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/volt-time-source-2.yaml b/templates/release/de/charger/volt-time-source-2.yaml new file mode 100644 index 0000000000..f3abc89c09 --- /dev/null +++ b/templates/release/de/charger/volt-time-source-2.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-source-2 + brand: Volt Time + description: Source 2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer (z. B. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Seriennummer (z. B. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/volt-time-source-2s.yaml b/templates/release/de/charger/volt-time-source-2s.yaml new file mode 100644 index 0000000000..52097c42c6 --- /dev/null +++ b/templates/release/de/charger/volt-time-source-2s.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-source-2s + brand: Volt Time + description: Source 2s +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer (z. B. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Seriennummer (z. B. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/volt-time-source.yaml b/templates/release/de/charger/volt-time-source.yaml new file mode 100644 index 0000000000..392ae38266 --- /dev/null +++ b/templates/release/de/charger/volt-time-source.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-source + brand: Volt Time + description: Source +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer (z. B. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Seriennummer (z. B. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/charger/volttime_0.yaml b/templates/release/de/charger/volttime_0.yaml deleted file mode 100644 index 8e66d02768..0000000000 --- a/templates/release/de/charger/volttime_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: Source -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) diff --git a/templates/release/de/charger/volttime_1.yaml b/templates/release/de/charger/volttime_1.yaml deleted file mode 100644 index 80c8e993ed..0000000000 --- a/templates/release/de/charger/volttime_1.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: Source 2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) diff --git a/templates/release/de/charger/volttime_2.yaml b/templates/release/de/charger/volttime_2.yaml deleted file mode 100644 index d4ec84c01f..0000000000 --- a/templates/release/de/charger/volttime_2.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: Source 2s -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) diff --git a/templates/release/de/charger/volttime_3.yaml b/templates/release/de/charger/volttime_3.yaml deleted file mode 100644 index 2931d640b3..0000000000 --- a/templates/release/de/charger/volttime_3.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: One -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) diff --git a/templates/release/de/charger/wallbe-eco-2-0-s.yaml b/templates/release/de/charger/wallbe-eco-2-0-s.yaml new file mode 100644 index 0000000000..d4f9b0c086 --- /dev/null +++ b/templates/release/de/charger/wallbe-eco-2-0-s.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: wallbe-eco-2-0-s + brand: Wallbe + description: Eco 2.0(s) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbe-eco.yaml b/templates/release/de/charger/wallbe-eco.yaml new file mode 100644 index 0000000000..5b22c722b4 --- /dev/null +++ b/templates/release/de/charger/wallbe-eco.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: wallbe-eco + brand: Wallbe + description: Eco +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbe-pro.yaml b/templates/release/de/charger/wallbe-pro.yaml new file mode 100644 index 0000000000..0155f274c4 --- /dev/null +++ b/templates/release/de/charger/wallbe-pro.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: wallbe-pro + brand: Wallbe + description: Pro +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml b/templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml new file mode 100644 index 0000000000..7647304710 --- /dev/null +++ b/templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-commander-2-fw-5-x + brand: wallbox + description: Commander 2 (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-commander-2.yaml b/templates/release/de/charger/wallbox-commander-2.yaml new file mode 100644 index 0000000000..db242cee82 --- /dev/null +++ b/templates/release/de/charger/wallbox-commander-2.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-commander-2 + brand: wallbox + description: Commander 2 +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml b/templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml new file mode 100644 index 0000000000..6ef4e83a30 --- /dev/null +++ b/templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-copper-sb-fw-5-x + brand: wallbox + description: Copper SB (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-copper-sb.yaml b/templates/release/de/charger/wallbox-copper-sb.yaml new file mode 100644 index 0000000000..29ee4ad073 --- /dev/null +++ b/templates/release/de/charger/wallbox-copper-sb.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-copper-sb + brand: wallbox + description: Copper SB +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-fw5_0.yaml b/templates/release/de/charger/wallbox-fw5_0.yaml deleted file mode 100644 index 70d0007760..0000000000 --- a/templates/release/de/charger/wallbox-fw5_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Plus (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/wallbox-fw5_1.yaml b/templates/release/de/charger/wallbox-fw5_1.yaml deleted file mode 100644 index bbf605765b..0000000000 --- a/templates/release/de/charger/wallbox-fw5_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Max (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/wallbox-fw5_2.yaml b/templates/release/de/charger/wallbox-fw5_2.yaml deleted file mode 100644 index 5925725714..0000000000 --- a/templates/release/de/charger/wallbox-fw5_2.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Commander 2 (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/wallbox-fw5_3.yaml b/templates/release/de/charger/wallbox-fw5_3.yaml deleted file mode 100644 index cf2b6ef898..0000000000 --- a/templates/release/de/charger/wallbox-fw5_3.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Copper SB (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren - * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) - * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird - * Passwort: leer lassen - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional diff --git a/templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml b/templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml new file mode 100644 index 0000000000..aa23253e98 --- /dev/null +++ b/templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-pulsar-max-fw-5-x + brand: wallbox + description: Pulsar Max (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-pulsar-max.yaml b/templates/release/de/charger/wallbox-pulsar-max.yaml new file mode 100644 index 0000000000..bf9ebc3609 --- /dev/null +++ b/templates/release/de/charger/wallbox-pulsar-max.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-pulsar-max + brand: wallbox + description: Pulsar Max +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml b/templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml new file mode 100644 index 0000000000..a2d8008de7 --- /dev/null +++ b/templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-pulsar-plus-fw-5-x + brand: wallbox + description: Pulsar Plus (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-pulsar-plus.yaml b/templates/release/de/charger/wallbox-pulsar-plus.yaml new file mode 100644 index 0000000000..35864274bd --- /dev/null +++ b/templates/release/de/charger/wallbox-pulsar-plus.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-pulsar-plus + brand: wallbox + description: Pulsar Plus +requirements: ["sponsorship", "skiptest"] +description: | + Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * “OCPP aktivieren” (myWallbox app) bzw. den “OCPP-WebSocket-Verbindung” Schalter (myWallbox Portal) aktivieren + * Zusätzlich die “Verbesserte Ladegerätsteuerung” (Profil -> Experimentelle Funktionen) einschalten (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (Verbindung über das lokale Netzwerk) + * Ladepunktidentität: beliebiger Wert (z.B. die Seriennummer der Box), der als *stationid* verwendet wird + * Passwort: leer lassen + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/walther-werke-basic-evo-pro.yaml b/templates/release/de/charger/walther-werke-basic-evo-pro.yaml new file mode 100644 index 0000000000..003876400c --- /dev/null +++ b/templates/release/de/charger/walther-werke-basic-evo-pro.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: walther-werke-basic-evo-pro + brand: Walther Werke + description: Basic Evo Pro +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/webasto-live.yaml b/templates/release/de/charger/webasto-live.yaml new file mode 100644 index 0000000000..49dcd3dc6b --- /dev/null +++ b/templates/release/de/charger/webasto-live.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: webasto-live + brand: Webasto + description: Live +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/webasto-next.yaml b/templates/release/de/charger/webasto-next.yaml new file mode 100644 index 0000000000..cd6446d5ad --- /dev/null +++ b/templates/release/de/charger/webasto-next.yaml @@ -0,0 +1,34 @@ +template: webasto-next +product: + identifier: webasto-next + brand: Webasto + description: NEXT +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. +render: + - default: | + type: template + template: webasto-next + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/webasto-next_0.yaml b/templates/release/de/charger/webasto-next_0.yaml deleted file mode 100644 index 150b0916d6..0000000000 --- a/templates/release/de/charger/webasto-next_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Ampure - description: NEXT -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. -render: - - default: | - type: template - template: webasto-next - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional diff --git a/templates/release/de/charger/webasto-next_1.yaml b/templates/release/de/charger/webasto-next_1.yaml deleted file mode 100644 index 4b1d540c7f..0000000000 --- a/templates/release/de/charger/webasto-next_1.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Webasto - description: NEXT -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. -render: - - default: | - type: template - template: webasto-next - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional diff --git a/templates/release/de/charger/webasto-unite.yaml b/templates/release/de/charger/webasto-unite.yaml new file mode 100644 index 0000000000..1bc88d681f --- /dev/null +++ b/templates/release/de/charger/webasto-unite.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: webasto-unite + brand: Webasto + description: Unite +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/weidmuller-ac-smart.yaml b/templates/release/de/charger/weidmuller-ac-smart.yaml new file mode 100644 index 0000000000..ede3bf112e --- /dev/null +++ b/templates/release/de/charger/weidmuller-ac-smart.yaml @@ -0,0 +1,22 @@ +template: weidmüller +product: + identifier: weidmuller-ac-smart + brand: Weidmüller + description: AC Smart +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: weidmüller + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git "a/templates/release/de/charger/weidm\303\274ller_0.yaml" "b/templates/release/de/charger/weidm\303\274ller_0.yaml" deleted file mode 100644 index b8cf338a7b..0000000000 --- "a/templates/release/de/charger/weidm\303\274ller_0.yaml" +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Weidmüller - description: AC Smart -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: weidmüller - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/charger/wolf-bwl.yaml b/templates/release/de/charger/wolf-bwl.yaml new file mode 100644 index 0000000000..463ac00783 --- /dev/null +++ b/templates/release/de/charger/wolf-bwl.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: wolf-bwl + brand: Wolf + description: BWL + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/wolf-bws.yaml b/templates/release/de/charger/wolf-bws.yaml new file mode 100644 index 0000000000..00923e24ef --- /dev/null +++ b/templates/release/de/charger/wolf-bws.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: wolf-bws + brand: Wolf + description: BWS + group: Wärmeerzeuger +description: | + Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Heizwassertemperatur. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/charger/zaptec-go-2.yaml b/templates/release/de/charger/zaptec-go-2.yaml new file mode 100644 index 0000000000..7ee42d1e79 --- /dev/null +++ b/templates/release/de/charger/zaptec-go-2.yaml @@ -0,0 +1,42 @@ +template: zaptec +product: + identifier: zaptec-go-2 + brand: Zaptec + description: Go 2 +capabilities: ["rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: zaptec + id: # Wallbox ID (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: id + example: + default: + choice: [] + unit: + description: + help: Wallbox ID + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/zaptec-go-ocpp.yaml b/templates/release/de/charger/zaptec-go-ocpp.yaml new file mode 100644 index 0000000000..4d92602c0f --- /dev/null +++ b/templates/release/de/charger/zaptec-go-ocpp.yaml @@ -0,0 +1,91 @@ +template: ocpp-zaptec +product: + identifier: zaptec-go-ocpp + brand: Zaptec + description: Go (OCPP) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + OCPP Native mode + + https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ + +render: + - default: | + type: template + template: ocpp-zaptec + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-zaptec + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/zaptec-go.yaml b/templates/release/de/charger/zaptec-go.yaml new file mode 100644 index 0000000000..1d0029bbed --- /dev/null +++ b/templates/release/de/charger/zaptec-go.yaml @@ -0,0 +1,42 @@ +template: zaptec +product: + identifier: zaptec-go + brand: Zaptec + description: Go +capabilities: ["rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: zaptec + id: # Wallbox ID (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: id + example: + default: + choice: [] + unit: + description: + help: Wallbox ID + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/zaptec-pro.yaml b/templates/release/de/charger/zaptec-pro.yaml new file mode 100644 index 0000000000..f6e04b5a89 --- /dev/null +++ b/templates/release/de/charger/zaptec-pro.yaml @@ -0,0 +1,42 @@ +template: zaptec +product: + identifier: zaptec-pro + brand: Zaptec + description: Pro +capabilities: ["rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: zaptec + id: # Wallbox ID (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: id + example: + default: + choice: [] + unit: + description: + help: Wallbox ID + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/zaptec_0.yaml b/templates/release/de/charger/zaptec_0.yaml deleted file mode 100644 index d6f026688a..0000000000 --- a/templates/release/de/charger/zaptec_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zaptec - description: Go -capabilities: ["rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: zaptec - id: # Wallbox ID (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/zaptec_1.yaml b/templates/release/de/charger/zaptec_1.yaml deleted file mode 100644 index ca11a7a246..0000000000 --- a/templates/release/de/charger/zaptec_1.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zaptec - description: Go 2 -capabilities: ["rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: zaptec - id: # Wallbox ID (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/zaptec_2.yaml b/templates/release/de/charger/zaptec_2.yaml deleted file mode 100644 index 3f05593ea5..0000000000 --- a/templates/release/de/charger/zaptec_2.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zaptec - description: Pro -capabilities: ["rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: zaptec - id: # Wallbox ID (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/charger/zewotherm-eu-l-series.yaml b/templates/release/de/charger/zewotherm-eu-l-series.yaml new file mode 100644 index 0000000000..b02ced9352 --- /dev/null +++ b/templates/release/de/charger/zewotherm-eu-l-series.yaml @@ -0,0 +1,52 @@ +template: lambda-zewotherm +product: + identifier: zewotherm-eu-l-series + brand: Zewotherm + description: EU-L Serie + group: Wärmeerzeuger +description: | + Energiemanagementeinstellungen am Gerät: + + - E-Meter Kommunikationsart: "ModBus Client" + - E-Meter Messpunkt: "Pos. E-Überschuss" + +render: + - default: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + advanced: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP-Adresse oder Hostname + tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater_top', 'warmwater_bottom', 'buffer_top', 'buffer_bottom'] + unit: + description: Temperaturquelle + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/charger/zj-beny-bcp-ev-charger.yaml b/templates/release/de/charger/zj-beny-bcp-ev-charger.yaml new file mode 100644 index 0000000000..0b453dbc7a --- /dev/null +++ b/templates/release/de/charger/zj-beny-bcp-ev-charger.yaml @@ -0,0 +1,86 @@ +template: ocpp-beny +product: + identifier: zj-beny-bcp-ev-charger + brand: ZJ Beny + description: BCP EV charger +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-beny + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + advanced: | + type: template + template: ocpp-beny + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) + remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) + idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional + meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Anschlussnummer + help: Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung des Ladepunktes + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/a-tronix.yaml b/templates/release/de/meter/a-tronix.yaml new file mode 100644 index 0000000000..9e45ad87c1 --- /dev/null +++ b/templates/release/de/meter/a-tronix.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: a-tronix + brand: A-Tronix +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/abb-a43.yaml b/templates/release/de/meter/abb-a43.yaml new file mode 100644 index 0000000000..b8f9cde212 --- /dev/null +++ b/templates/release/de/meter/abb-a43.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-a43 + brand: ABB + description: A43 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/abb-a44.yaml b/templates/release/de/meter/abb-a44.yaml new file mode 100644 index 0000000000..73a54d0f01 --- /dev/null +++ b/templates/release/de/meter/abb-a44.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-a44 + brand: ABB + description: A44 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/abb-ab_0.yaml b/templates/release/de/meter/abb-ab_0.yaml deleted file mode 100644 index 8555cd10ce..0000000000 --- a/templates/release/de/meter/abb-ab_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: ABB - description: A43, A44, B23, B24 -render: - - usage: grid - default: | - type: template - template: abb-ab - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: abb-ab - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/abb-b23.yaml b/templates/release/de/meter/abb-b23.yaml new file mode 100644 index 0000000000..064db6b31f --- /dev/null +++ b/templates/release/de/meter/abb-b23.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-b23 + brand: ABB + description: B23 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/abb-b24.yaml b/templates/release/de/meter/abb-b24.yaml new file mode 100644 index 0000000000..b82fd16671 --- /dev/null +++ b/templates/release/de/meter/abb-b24.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-b24 + brand: ABB + description: B24 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/ac-elwa-2_0.yaml b/templates/release/de/meter/ac-elwa-2_0.yaml deleted file mode 100644 index 8c3bc2e02b..0000000000 --- a/templates/release/de/meter/ac-elwa-2_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: my-PV - description: AC ELWA 2 -render: - - usage: aux - default: | - type: template - template: ac-elwa-2 - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/ac-elwa-e_0.yaml b/templates/release/de/meter/ac-elwa-e_0.yaml deleted file mode 100644 index 219c7e4204..0000000000 --- a/templates/release/de/meter/ac-elwa-e_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: my-PV - description: AC ELWA-E -render: - - usage: aux - default: | - type: template - template: ac-elwa-e - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/acrel-adw300.yaml b/templates/release/de/meter/acrel-adw300.yaml new file mode 100644 index 0000000000..ed0f7ea506 --- /dev/null +++ b/templates/release/de/meter/acrel-adw300.yaml @@ -0,0 +1,98 @@ +template: acrel-adw300 +product: + identifier: acrel-adw300 + brand: Acrel + description: ADW300 +render: + - usage: grid + default: | + type: template + template: acrel-adw300 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: acrel-adw300 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: acrel-adw300 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 1200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/acrel-adw300_0.yaml b/templates/release/de/meter/acrel-adw300_0.yaml deleted file mode 100644 index 158d7b0051..0000000000 --- a/templates/release/de/meter/acrel-adw300_0.yaml +++ /dev/null @@ -1,76 +0,0 @@ -product: - brand: Acrel - description: ADW300 Wireless Metering Meter -render: - - usage: grid - default: | - type: template - template: acrel-adw300 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: acrel-adw300 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: acrel-adw300 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/ads-tec-storaxe.yaml b/templates/release/de/meter/ads-tec-storaxe.yaml new file mode 100644 index 0000000000..3bf8874ee5 --- /dev/null +++ b/templates/release/de/meter/ads-tec-storaxe.yaml @@ -0,0 +1,53 @@ +template: storaxe +product: + identifier: ads-tec-storaxe + brand: Ads-tec + description: StoraXe +render: + - usage: battery + default: | + type: template + template: storaxe + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: storaxe + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/alpha-ess-smile_0.yaml b/templates/release/de/meter/alpha-ess-smile_0.yaml deleted file mode 100644 index c6fbcfa470..0000000000 --- a/templates/release/de/meter/alpha-ess-smile_0.yaml +++ /dev/null @@ -1,157 +0,0 @@ -product: - brand: Alpha ESS - description: Storion SMILE -capabilities: ["battery-control"] -description: | - Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder App Zeiten für das Netzladen definiert werden. (Einstellungen->Funktionseinstellungen->Netzladen/Entladen) Hier sollte ein durchgehender Zeitraum (z.B: Ladezeit 1 00:00-23:00, Ladezeit 2 23:00-00:00) eingetragen werden. Den Schalter "Netzladen" aber deaktivieren. Die eigentliche Steuerung erfolgt über evcc. Der Entladestopp wird über eine geplante Netzladung mit einem Ziel-SoC von 10% realisiert. Alternativ können die Zeiten auch über Modbus konfiguriert werden. Dafür die Register `2134,2142,2135,2136,2144,2137,2175` auf die Werte `0,0,23,0,23,0,0,0` setzen. - -render: - - usage: grid - default: | - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: alpha-ess-smile - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: alpha-ess-smile - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: alpha-ess-smile - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: alpha-ess-smile - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/alpha-ess-storion-smile.yaml b/templates/release/de/meter/alpha-ess-storion-smile.yaml new file mode 100644 index 0000000000..6975203c19 --- /dev/null +++ b/templates/release/de/meter/alpha-ess-storion-smile.yaml @@ -0,0 +1,215 @@ +template: alpha-ess-smile +product: + identifier: alpha-ess-storion-smile + brand: Alpha ESS + description: Storion SMILE +capabilities: ["battery-control"] +description: | + Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder App Zeiten für das Netzladen definiert werden. (Einstellungen->Funktionseinstellungen->Netzladen/Entladen) Hier sollte ein durchgehender Zeitraum (z.B: Ladezeit 1 00:00-23:00, Ladezeit 2 23:00-00:00) eingetragen werden. Den Schalter "Netzladen" aber deaktivieren. Die eigentliche Steuerung erfolgt über evcc. Der Entladestopp wird über eine geplante Netzladung mit einem Ziel-SoC von 10% realisiert. Alternativ können die Zeiten auch über Modbus konfiguriert werden. Dafür die Register `2134,2142,2135,2136,2144,2137,2175` auf die Werte `0,0,23,0,23,0,0,0` setzen. + +render: + - usage: grid + default: | + type: template + template: alpha-ess-smile + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: alpha-ess-smile + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: alpha-ess-smile + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: alpha-ess-smile + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: alpha-ess-smile + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: alpha-ess-smile + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 85 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/ampere-ampere-storagepro.yaml b/templates/release/de/meter/ampere-ampere-storagepro.yaml new file mode 100644 index 0000000000..db897964dd --- /dev/null +++ b/templates/release/de/meter/ampere-ampere-storagepro.yaml @@ -0,0 +1,211 @@ +template: saj-h2 +product: + identifier: ampere-ampere-storagepro + brand: Ampere + description: Ampere.StoragePro +render: + - usage: grid + default: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: battery + default: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 2 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 2 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/anker-micro-inverter.yaml b/templates/release/de/meter/anker-micro-inverter.yaml new file mode 100644 index 0000000000..c2b07840a3 --- /dev/null +++ b/templates/release/de/meter/anker-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: anker-micro-inverter + brand: Anker + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/apsystems-ez1.yaml b/templates/release/de/meter/apsystems-ez1.yaml new file mode 100644 index 0000000000..790a3a8e9d --- /dev/null +++ b/templates/release/de/meter/apsystems-ez1.yaml @@ -0,0 +1,22 @@ +template: apsystems-ez1 +product: + identifier: apsystems-ez1 + brand: APsystems + description: EZ1 +render: + - usage: pv + default: | + type: template + template: apsystems-ez1 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/apsystems-ez1_0.yaml b/templates/release/de/meter/apsystems-ez1_0.yaml deleted file mode 100644 index 74bd19b9a0..0000000000 --- a/templates/release/de/meter/apsystems-ez1_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: APsystems - description: EZ1 -render: - - usage: pv - default: | - type: template - template: apsystems-ez1 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/avm-fritzdect.yaml b/templates/release/de/meter/avm-fritzdect.yaml new file mode 100644 index 0000000000..7e38573c61 --- /dev/null +++ b/templates/release/de/meter/avm-fritzdect.yaml @@ -0,0 +1,62 @@ +template: fritzdect +product: + identifier: avm-fritzdect + brand: AVM + description: FritzDECT + group: Schaltbare Steckdosen +render: + - usage: pv + default: | + type: template + template: fritzdect + usage: pv + uri: https://fritz.box # URI, HTTP(S) Adresse (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. + - usage: charge + default: | + type: template + template: fritzdect + usage: charge + uri: https://fritz.box # URI, HTTP(S) Adresse (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. +params: + - name: uri + example: + default: https://fritz.box + choice: [] + unit: + description: URI + help: HTTP(S) Adresse + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: ain + example: 307788992233 + default: + choice: [] + unit: + description: Aktoridentifikationsnummer (AIN) + help: Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/axitec-axihycon-12-15h.yaml b/templates/release/de/meter/axitec-axihycon-12-15h.yaml new file mode 100644 index 0000000000..b225532c7c --- /dev/null +++ b/templates/release/de/meter/axitec-axihycon-12-15h.yaml @@ -0,0 +1,150 @@ +template: solis-hybrid-s +product: + identifier: axitec-axihycon-12-15h + brand: Axitec + description: AXIhycon 12-15H +render: + - usage: grid + default: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/bernecker-engineering-mpm3pm.yaml b/templates/release/de/meter/bernecker-engineering-mpm3pm.yaml new file mode 100644 index 0000000000..7d3910399f --- /dev/null +++ b/templates/release/de/meter/bernecker-engineering-mpm3pm.yaml @@ -0,0 +1,61 @@ +template: mpm3pm +product: + identifier: bernecker-engineering-mpm3pm + brand: Bernecker Engineering + description: MPM3PM +render: + - usage: grid + default: | + type: template + template: mpm3pm + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: mpm3pm + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/bge_tech_ds100_0.yaml b/templates/release/de/meter/bge_tech_ds100_0.yaml deleted file mode 100644 index 14bc06d873..0000000000 --- a/templates/release/de/meter/bge_tech_ds100_0.yaml +++ /dev/null @@ -1,100 +0,0 @@ -product: - brand: BGEtech - description: DS100 -render: - - usage: grid - default: | - type: template - template: bge_tech_ds100 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: bge_tech_ds100 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: bge_tech_ds100 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: aux - default: | - type: template - template: bge_tech_ds100 - usage: aux - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/bge_tech_ws100_0.yaml b/templates/release/de/meter/bge_tech_ws100_0.yaml deleted file mode 100644 index 13119038a7..0000000000 --- a/templates/release/de/meter/bge_tech_ws100_0.yaml +++ /dev/null @@ -1,100 +0,0 @@ -product: - brand: BGEtech - description: WS100 -render: - - usage: grid - default: | - type: template - template: bge_tech_ws100 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: bge_tech_ws100 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: bge_tech_ws100 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: aux - default: | - type: template - template: bge_tech_ws100 - usage: aux - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/bgetech-ds100.yaml b/templates/release/de/meter/bgetech-ds100.yaml new file mode 100644 index 0000000000..c4718cb5cc --- /dev/null +++ b/templates/release/de/meter/bgetech-ds100.yaml @@ -0,0 +1,122 @@ +template: bge_tech_ds100 +product: + identifier: bgetech-ds100 + brand: BGEtech + description: DS100 +render: + - usage: grid + default: | + type: template + template: bge_tech_ds100 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: bge_tech_ds100 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: bge_tech_ds100 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: aux + default: | + type: template + template: bge_tech_ds100 + usage: aux + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 1200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/bgetech-ws100.yaml b/templates/release/de/meter/bgetech-ws100.yaml new file mode 100644 index 0000000000..b1f7bbd153 --- /dev/null +++ b/templates/release/de/meter/bgetech-ws100.yaml @@ -0,0 +1,122 @@ +template: bge_tech_ws100 +product: + identifier: bgetech-ws100 + brand: BGEtech + description: WS100 +render: + - usage: grid + default: | + type: template + template: bge_tech_ws100 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: bge_tech_ws100 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: bge_tech_ws100 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: aux + default: | + type: template + template: bge_tech_ws100 + usage: aux + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 1200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/bosch-bpt-s-5-hybrid.yaml b/templates/release/de/meter/bosch-bpt-s-5-hybrid.yaml new file mode 100644 index 0000000000..ef0ce9c2de --- /dev/null +++ b/templates/release/de/meter/bosch-bpt-s-5-hybrid.yaml @@ -0,0 +1,60 @@ +template: bosch-bpt +product: + identifier: bosch-bpt-s-5-hybrid + brand: Bosch + description: BPT-S 5 Hybrid +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: bosch-bpt + usage: grid + uri: # URI, HTTP(S) Adresse (optional) + advanced: | + type: template + template: bosch-bpt + usage: grid + uri: # URI, HTTP(S) Adresse (optional) + - usage: pv + default: | + type: template + template: bosch-bpt + usage: pv + uri: # URI, HTTP(S) Adresse (optional) + advanced: | + type: template + template: bosch-bpt + usage: pv + uri: # URI, HTTP(S) Adresse (optional) + - usage: battery + default: | + type: template + template: bosch-bpt + usage: battery + uri: # URI, HTTP(S) Adresse (optional) + advanced: | + type: template + template: bosch-bpt + usage: battery + uri: # URI, HTTP(S) Adresse (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: uri + example: + default: + choice: [] + unit: + description: URI + help: HTTP(S) Adresse + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/bosch-bpt_0.yaml b/templates/release/de/meter/bosch-bpt_0.yaml deleted file mode 100644 index 24872b8781..0000000000 --- a/templates/release/de/meter/bosch-bpt_0.yaml +++ /dev/null @@ -1,39 +0,0 @@ -product: - brand: Bosch - description: BPT-S 5 Hybrid -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: bosch-bpt - usage: grid - uri: # URI, HTTP(S) Adresse (optional) - advanced: | - type: template - template: bosch-bpt - usage: grid - uri: # URI, HTTP(S) Adresse (optional) - - usage: pv - default: | - type: template - template: bosch-bpt - usage: pv - uri: # URI, HTTP(S) Adresse (optional) - advanced: | - type: template - template: bosch-bpt - usage: pv - uri: # URI, HTTP(S) Adresse (optional) - - usage: battery - default: | - type: template - template: bosch-bpt - usage: battery - uri: # URI, HTTP(S) Adresse (optional) - advanced: | - type: template - template: bosch-bpt - usage: battery - uri: # URI, HTTP(S) Adresse (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/bosswerk-micro-inverter.yaml b/templates/release/de/meter/bosswerk-micro-inverter.yaml new file mode 100644 index 0000000000..0434da45af --- /dev/null +++ b/templates/release/de/meter/bosswerk-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: bosswerk-micro-inverter + brand: Bosswerk + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml b/templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml new file mode 100644 index 0000000000..b75d465d27 --- /dev/null +++ b/templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml @@ -0,0 +1,61 @@ +template: cg-emt1xx +product: + identifier: carlo-gavazzi-em110-111-112 + brand: Carlo Gavazzi + description: EM110/111/112 +render: + - usage: pv + default: | + type: template + template: cg-emt1xx + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt1xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/carlo-gavazzi-em24.yaml b/templates/release/de/meter/carlo-gavazzi-em24.yaml new file mode 100644 index 0000000000..aa73f0e9a6 --- /dev/null +++ b/templates/release/de/meter/carlo-gavazzi-em24.yaml @@ -0,0 +1,64 @@ +template: cg-em24 +product: + identifier: carlo-gavazzi-em24 + brand: Carlo Gavazzi + description: EM24 +description: | + EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. + +render: + - usage: grid + default: | + type: template + template: cg-em24 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/carlo-gavazzi-em24_e1.yaml b/templates/release/de/meter/carlo-gavazzi-em24_e1.yaml new file mode 100644 index 0000000000..ec04cf056f --- /dev/null +++ b/templates/release/de/meter/carlo-gavazzi-em24_e1.yaml @@ -0,0 +1,48 @@ +template: cg-em24_e1 +product: + identifier: carlo-gavazzi-em24_e1 + brand: Carlo Gavazzi + description: EM24_E1 +description: | + EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. + Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + +render: + - usage: grid + default: | + type: template + template: cg-em24_e1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24_e1 + usage: charge + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/carlo-gavazzi-em330-em340.yaml b/templates/release/de/meter/carlo-gavazzi-em330-em340.yaml new file mode 100644 index 0000000000..71771d9771 --- /dev/null +++ b/templates/release/de/meter/carlo-gavazzi-em330-em340.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: carlo-gavazzi-em330-em340 + brand: Carlo Gavazzi + description: EM330/EM340 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/carlo-gavazzi-em530-em540.yaml b/templates/release/de/meter/carlo-gavazzi-em530-em540.yaml new file mode 100644 index 0000000000..d0f5a82c17 --- /dev/null +++ b/templates/release/de/meter/carlo-gavazzi-em530-em540.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: carlo-gavazzi-em530-em540 + brand: Carlo Gavazzi + description: EM530/EM540 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/carlo-gavazzi-et112.yaml b/templates/release/de/meter/carlo-gavazzi-et112.yaml new file mode 100644 index 0000000000..16680813b5 --- /dev/null +++ b/templates/release/de/meter/carlo-gavazzi-et112.yaml @@ -0,0 +1,61 @@ +template: cg-emt1xx +product: + identifier: carlo-gavazzi-et112 + brand: Carlo Gavazzi + description: ET112 +render: + - usage: pv + default: | + type: template + template: cg-emt1xx + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt1xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/carlo-gavazzi-et330-et340.yaml b/templates/release/de/meter/carlo-gavazzi-et330-et340.yaml new file mode 100644 index 0000000000..da396ac6cc --- /dev/null +++ b/templates/release/de/meter/carlo-gavazzi-et330-et340.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: carlo-gavazzi-et330-et340 + brand: Carlo Gavazzi + description: ET330/ET340 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/cfos-powerbrain-meter.yaml b/templates/release/de/meter/cfos-powerbrain-meter.yaml new file mode 100644 index 0000000000..3eb38abc45 --- /dev/null +++ b/templates/release/de/meter/cfos-powerbrain-meter.yaml @@ -0,0 +1,34 @@ +template: cfos +product: + identifier: cfos-powerbrain-meter + brand: cFos + description: PowerBrain Meter +requirements: ["sponsorship"] +render: + - usage: charge + default: | + type: template + template: cfos + usage: charge + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 4702 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 4702 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/cfos_0.yaml b/templates/release/de/meter/cfos_0.yaml deleted file mode 100644 index c7b87e0fcf..0000000000 --- a/templates/release/de/meter/cfos_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: cFos - description: PowerBrain Meter -requirements: ["sponsorship"] -render: - - usage: charge - default: | - type: template - template: cfos - usage: charge - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 4702 # Port diff --git a/templates/release/de/meter/cg-em24_0.yaml b/templates/release/de/meter/cg-em24_0.yaml deleted file mode 100644 index 75aa358e1a..0000000000 --- a/templates/release/de/meter/cg-em24_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM24 -description: | - EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. - -render: - - usage: grid - default: | - type: template - template: cg-em24 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-em24_1.yaml b/templates/release/de/meter/cg-em24_1.yaml deleted file mode 100644 index c67f2a32e5..0000000000 --- a/templates/release/de/meter/cg-em24_1.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Victron - description: EM24 -description: | - EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. - -render: - - usage: grid - default: | - type: template - template: cg-em24 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-em24_e1_0.yaml b/templates/release/de/meter/cg-em24_e1_0.yaml deleted file mode 100644 index 569c31be32..0000000000 --- a/templates/release/de/meter/cg-em24_e1_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM24_E1 -description: | - EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. - Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - -render: - - usage: grid - default: | - type: template - template: cg-em24_e1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24_e1 - usage: charge - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-em24_e1_1.yaml b/templates/release/de/meter/cg-em24_e1_1.yaml deleted file mode 100644 index eb7ce78fba..0000000000 --- a/templates/release/de/meter/cg-em24_e1_1.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Victron - description: EM24_E1 -description: | - EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. - Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - -render: - - usage: grid - default: | - type: template - template: cg-em24_e1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24_e1 - usage: charge - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt1xx_0.yaml b/templates/release/de/meter/cg-emt1xx_0.yaml deleted file mode 100644 index f888b1d08a..0000000000 --- a/templates/release/de/meter/cg-emt1xx_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM110/111/112 -render: - - usage: pv - default: | - type: template - template: cg-emt1xx - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt1xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt1xx_1.yaml b/templates/release/de/meter/cg-emt1xx_1.yaml deleted file mode 100644 index 2e307a267d..0000000000 --- a/templates/release/de/meter/cg-emt1xx_1.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Carlo Gavazzi - description: ET112 -render: - - usage: pv - default: | - type: template - template: cg-emt1xx - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt1xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt3xx_0.yaml b/templates/release/de/meter/cg-emt3xx_0.yaml deleted file mode 100644 index c9e82d203f..0000000000 --- a/templates/release/de/meter/cg-emt3xx_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Carlo Gavazzi - description: ET330/ET340 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt3xx_1.yaml b/templates/release/de/meter/cg-emt3xx_1.yaml deleted file mode 100644 index 20f08771e4..0000000000 --- a/templates/release/de/meter/cg-emt3xx_1.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM330/EM340 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt3xx_2.yaml b/templates/release/de/meter/cg-emt3xx_2.yaml deleted file mode 100644 index 5d4dad42c1..0000000000 --- a/templates/release/de/meter/cg-emt3xx_2.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM530/EM540 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt3xx_3.yaml b/templates/release/de/meter/cg-emt3xx_3.yaml deleted file mode 100644 index c2d1600b67..0000000000 --- a/templates/release/de/meter/cg-emt3xx_3.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Victron - description: ET340 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt3xx_4.yaml b/templates/release/de/meter/cg-emt3xx_4.yaml deleted file mode 100644 index 7235030cd2..0000000000 --- a/templates/release/de/meter/cg-emt3xx_4.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Victron - description: EM530/EM540 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/cg-emt3xx_5.yaml b/templates/release/de/meter/cg-emt3xx_5.yaml deleted file mode 100644 index 335ed59fe7..0000000000 --- a/templates/release/de/meter/cg-emt3xx_5.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Kostal - description: Energy Meter C (KEM-C) -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/demo-battery.yaml b/templates/release/de/meter/demo-battery.yaml new file mode 100644 index 0000000000..ec68afe17e --- /dev/null +++ b/templates/release/de/meter/demo-battery.yaml @@ -0,0 +1,91 @@ +template: demo-battery +product: + identifier: demo-battery + description: Demobatterie + group: Generische Unterstützung +description: | + Zu Demonstrationszwecken. Hausbatterie mit festen Werten. +render: + - usage: battery + default: | + type: template + template: demo-battery + usage: battery + power: # Leistung (W), optional + soc: # Ladestand (%), optional + controllable: # Steuerbar, Unterstützt aktive Batteriesteuerung (optional) + advanced: | + type: template + template: demo-battery + usage: battery + power: # Leistung (W), optional + soc: # Ladestand (%), optional + controllable: # Steuerbar, Unterstützt aktive Batteriesteuerung (optional) + energy: # Zählerstand (kWh), optional + currentL1: # L1 Stromstärke (A), optional + currentL2: # L2 Stromstärke (A), optional + currentL3: # L3 Stromstärke (A), optional +params: + - name: power + example: + default: + choice: [] + unit: W + description: Leistung + help: + advanced: false + optional: true + - name: soc + example: + default: + choice: [] + unit: '%' + description: Ladestand + help: + advanced: false + optional: true + - name: controllable + example: + default: + choice: [] + unit: + description: Steuerbar + help: Unterstützt aktive Batteriesteuerung + advanced: false + optional: true + - name: energy + example: + default: + choice: [] + unit: kWh + description: Zählerstand + help: + advanced: true + optional: true + - name: currentL1 + example: + default: + choice: [] + unit: A + description: L1 Stromstärke + help: + advanced: true + optional: true + - name: currentL2 + example: + default: + choice: [] + unit: A + description: L2 Stromstärke + help: + advanced: true + optional: true + - name: currentL3 + example: + default: + choice: [] + unit: A + description: L3 Stromstärke + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/demo-battery_0.yaml b/templates/release/de/meter/demo-battery_0.yaml deleted file mode 100644 index 65d9941878..0000000000 --- a/templates/release/de/meter/demo-battery_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: Demobatterie - group: Generische Unterstützung -description: | - Zu Demonstrationszwecken. Hausbatterie mit festen Werten. -render: - - usage: battery - default: | - type: template - template: demo-battery - usage: battery - power: # Leistung (W), optional - soc: # Ladestand (%), optional - controllable: # Steuerbar, Unterstützt aktive Batteriesteuerung (optional) - advanced: | - type: template - template: demo-battery - usage: battery - power: # Leistung (W), optional - soc: # Ladestand (%), optional - controllable: # Steuerbar, Unterstützt aktive Batteriesteuerung (optional) - energy: # Zählerstand (kWh), optional - currentL1: # L1 Stromstärke (A), optional - currentL2: # L2 Stromstärke (A), optional - currentL3: # L3 Stromstärke (A), optional diff --git a/templates/release/de/meter/demo-meter.yaml b/templates/release/de/meter/demo-meter.yaml new file mode 100644 index 0000000000..df761caf53 --- /dev/null +++ b/templates/release/de/meter/demo-meter.yaml @@ -0,0 +1,114 @@ +template: demo-meter +product: + identifier: demo-meter + description: Demozähler + group: Generische Unterstützung +description: | + Zu Demonstrationszwecken. Zähler mit festen Werten. +render: + - usage: grid + default: | + type: template + template: demo-meter + usage: grid + power: # Leistung (W), optional + advanced: | + type: template + template: demo-meter + usage: grid + power: # Leistung (W), optional + energy: # Zählerstand (kWh), optional + currentL1: # L1 Stromstärke (A), optional + currentL2: # L2 Stromstärke (A), optional + currentL3: # L3 Stromstärke (A), optional + - usage: pv + default: | + type: template + template: demo-meter + usage: pv + power: # Leistung (W), optional + advanced: | + type: template + template: demo-meter + usage: pv + power: # Leistung (W), optional + energy: # Zählerstand (kWh), optional + currentL1: # L1 Stromstärke (A), optional + currentL2: # L2 Stromstärke (A), optional + currentL3: # L3 Stromstärke (A), optional + - usage: aux + default: | + type: template + template: demo-meter + usage: aux + power: # Leistung (W), optional + advanced: | + type: template + template: demo-meter + usage: aux + power: # Leistung (W), optional + energy: # Zählerstand (kWh), optional + currentL1: # L1 Stromstärke (A), optional + currentL2: # L2 Stromstärke (A), optional + currentL3: # L3 Stromstärke (A), optional + - usage: charge + default: | + type: template + template: demo-meter + usage: charge + power: # Leistung (W), optional + advanced: | + type: template + template: demo-meter + usage: charge + power: # Leistung (W), optional + energy: # Zählerstand (kWh), optional + currentL1: # L1 Stromstärke (A), optional + currentL2: # L2 Stromstärke (A), optional + currentL3: # L3 Stromstärke (A), optional +params: + - name: power + example: + default: + choice: [] + unit: W + description: Leistung + help: + advanced: false + optional: true + - name: energy + example: + default: + choice: [] + unit: kWh + description: Zählerstand + help: + advanced: true + optional: true + - name: currentL1 + example: + default: + choice: [] + unit: A + description: L1 Stromstärke + help: + advanced: true + optional: true + - name: currentL2 + example: + default: + choice: [] + unit: A + description: L2 Stromstärke + help: + advanced: true + optional: true + - name: currentL3 + example: + default: + choice: [] + unit: A + description: L3 Stromstärke + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/demo-meter_0.yaml b/templates/release/de/meter/demo-meter_0.yaml deleted file mode 100644 index 7850c682e8..0000000000 --- a/templates/release/de/meter/demo-meter_0.yaml +++ /dev/null @@ -1,66 +0,0 @@ -product: - description: Demozähler - group: Generische Unterstützung -description: | - Zu Demonstrationszwecken. Zähler mit festen Werten. -render: - - usage: grid - default: | - type: template - template: demo-meter - usage: grid - power: # Leistung (W), optional - advanced: | - type: template - template: demo-meter - usage: grid - power: # Leistung (W), optional - energy: # Zählerstand (kWh), optional - currentL1: # L1 Stromstärke (A), optional - currentL2: # L2 Stromstärke (A), optional - currentL3: # L3 Stromstärke (A), optional - - usage: pv - default: | - type: template - template: demo-meter - usage: pv - power: # Leistung (W), optional - advanced: | - type: template - template: demo-meter - usage: pv - power: # Leistung (W), optional - energy: # Zählerstand (kWh), optional - currentL1: # L1 Stromstärke (A), optional - currentL2: # L2 Stromstärke (A), optional - currentL3: # L3 Stromstärke (A), optional - - usage: aux - default: | - type: template - template: demo-meter - usage: aux - power: # Leistung (W), optional - advanced: | - type: template - template: demo-meter - usage: aux - power: # Leistung (W), optional - energy: # Zählerstand (kWh), optional - currentL1: # L1 Stromstärke (A), optional - currentL2: # L2 Stromstärke (A), optional - currentL3: # L3 Stromstärke (A), optional - - usage: charge - default: | - type: template - template: demo-meter - usage: charge - power: # Leistung (W), optional - advanced: | - type: template - template: demo-meter - usage: charge - power: # Leistung (W), optional - energy: # Zählerstand (kWh), optional - currentL1: # L1 Stromstärke (A), optional - currentL2: # L2 Stromstärke (A), optional - currentL3: # L3 Stromstärke (A), optional diff --git a/templates/release/de/meter/deye-3p-hybrid-inverter.yaml b/templates/release/de/meter/deye-3p-hybrid-inverter.yaml new file mode 100644 index 0000000000..d27fd593ae --- /dev/null +++ b/templates/release/de/meter/deye-3p-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: deye-hybrid-3p +product: + identifier: deye-3p-hybrid-inverter + brand: Deye + description: 3p hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml b/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml new file mode 100644 index 0000000000..a70db4a58a --- /dev/null +++ b/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml @@ -0,0 +1,236 @@ +template: deye-hybrid-hp3 +product: + identifier: deye-hp3-hybrid-inverter + brand: Deye + description: hp3 hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional + - usage: pv + default: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional + - usage: battery + default: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: includegenport + example: + default: + choice: [] + unit: + description: GEN-Anschluss als Solar-Eingang verwenden + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/deye-hybrid-3p_0.yaml b/templates/release/de/meter/deye-hybrid-3p_0.yaml deleted file mode 100644 index 5c3bc6d3c3..0000000000 --- a/templates/release/de/meter/deye-hybrid-3p_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: Deye - description: 3p hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/deye-hybrid-3p_1.yaml b/templates/release/de/meter/deye-hybrid-3p_1.yaml deleted file mode 100644 index dc40f5fac2..0000000000 --- a/templates/release/de/meter/deye-hybrid-3p_1.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: Sunsynk - description: 3p hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/deye-hybrid-hp3_0.yaml b/templates/release/de/meter/deye-hybrid-hp3_0.yaml deleted file mode 100644 index 829be8f3bb..0000000000 --- a/templates/release/de/meter/deye-hybrid-hp3_0.yaml +++ /dev/null @@ -1,160 +0,0 @@ -product: - brand: Deye - description: hp3 hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - - usage: pv - default: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - - usage: battery - default: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional diff --git a/templates/release/de/meter/deye-hybrid-hp3_1.yaml b/templates/release/de/meter/deye-hybrid-hp3_1.yaml deleted file mode 100644 index 31f546e2db..0000000000 --- a/templates/release/de/meter/deye-hybrid-hp3_1.yaml +++ /dev/null @@ -1,160 +0,0 @@ -product: - brand: Sunsynk - description: hp3 hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - - usage: pv - default: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - - usage: battery - default: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional diff --git a/templates/release/de/meter/deye-mi_0.yaml b/templates/release/de/meter/deye-mi_0.yaml deleted file mode 100644 index 330b3dd9a3..0000000000 --- a/templates/release/de/meter/deye-mi_0.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Deye - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/deye-mi_1.yaml b/templates/release/de/meter/deye-mi_1.yaml deleted file mode 100644 index aef8b45064..0000000000 --- a/templates/release/de/meter/deye-mi_1.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Bosswerk - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/deye-mi_2.yaml b/templates/release/de/meter/deye-mi_2.yaml deleted file mode 100644 index 02fbe72af3..0000000000 --- a/templates/release/de/meter/deye-mi_2.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Anker - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/deye-mi_3.yaml b/templates/release/de/meter/deye-mi_3.yaml deleted file mode 100644 index 8a119828bd..0000000000 --- a/templates/release/de/meter/deye-mi_3.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Sunsynk - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/deye-micro-inverter.yaml b/templates/release/de/meter/deye-micro-inverter.yaml new file mode 100644 index 0000000000..b8ec8bd1dc --- /dev/null +++ b/templates/release/de/meter/deye-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: deye-micro-inverter + brand: Deye + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/deye-storage-hybrid-inverter.yaml b/templates/release/de/meter/deye-storage-hybrid-inverter.yaml new file mode 100644 index 0000000000..00af002dbc --- /dev/null +++ b/templates/release/de/meter/deye-storage-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: deye-storage +product: + identifier: deye-storage-hybrid-inverter + brand: Deye + description: Storage (hybrid) inverter +render: + - usage: pv + default: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + - usage: grid + default: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/deye-storage_0.yaml b/templates/release/de/meter/deye-storage_0.yaml deleted file mode 100644 index e258199816..0000000000 --- a/templates/release/de/meter/deye-storage_0.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: Deye - description: Storage (hybrid) inverter -render: - - usage: pv - default: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - - usage: grid - default: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/deye-storage_1.yaml b/templates/release/de/meter/deye-storage_1.yaml deleted file mode 100644 index 8abcf56b70..0000000000 --- a/templates/release/de/meter/deye-storage_1.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: Sunsynk - description: Storage (hybrid) inverter -render: - - usage: pv - default: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - - usage: grid - default: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/deye-string-inverter.yaml b/templates/release/de/meter/deye-string-inverter.yaml new file mode 100644 index 0000000000..5c65be54c8 --- /dev/null +++ b/templates/release/de/meter/deye-string-inverter.yaml @@ -0,0 +1,50 @@ +template: deye-string +product: + identifier: deye-string-inverter + brand: Deye + description: String inverter +render: + - usage: pv + default: | + type: template + template: deye-string + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/deye-string_0.yaml b/templates/release/de/meter/deye-string_0.yaml deleted file mode 100644 index b584ebb31a..0000000000 --- a/templates/release/de/meter/deye-string_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Deye - description: String inverter -render: - - usage: pv - default: | - type: template - template: deye-string - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/deye-string_1.yaml b/templates/release/de/meter/deye-string_1.yaml deleted file mode 100644 index b1959c2963..0000000000 --- a/templates/release/de/meter/deye-string_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Sunsynk - description: String inverter -render: - - usage: pv - default: | - type: template - template: deye-string - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/discovergy.yaml b/templates/release/de/meter/discovergy.yaml new file mode 100644 index 0000000000..6e2da0bd6b --- /dev/null +++ b/templates/release/de/meter/discovergy.yaml @@ -0,0 +1,49 @@ +template: discovergy +product: + identifier: discovergy + description: Discovergy +render: + - usage: grid + default: | + type: template + template: discovergy + usage: grid + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + meter: 1ESY1161229886 + - usage: pv + default: | + type: template + template: discovergy + usage: pv + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + meter: 1ESY1161229886 +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: meter + example: 1ESY1161229886 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/discovergy_0.yaml b/templates/release/de/meter/discovergy_0.yaml deleted file mode 100644 index b32631de58..0000000000 --- a/templates/release/de/meter/discovergy_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - description: Discovergy -render: - - usage: grid - default: | - type: template - template: discovergy - usage: grid - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886 - - usage: pv - default: | - type: template - template: discovergy - usage: pv - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886 diff --git a/templates/release/de/meter/dsmr.yaml b/templates/release/de/meter/dsmr.yaml new file mode 100644 index 0000000000..c20c3a811d --- /dev/null +++ b/templates/release/de/meter/dsmr.yaml @@ -0,0 +1,47 @@ +template: dsmr +product: + identifier: dsmr + brand: DSMR +render: + - usage: grid + default: | + type: template + template: dsmr + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 1502 # Port, optional + advanced: | + type: template + template: dsmr + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 1502 # Port, optional + energy: # OBIS Kennzahl für Energieverbrauch, Typischerweise 1-0:1.8.0, bei Mehrtarifzählern 1-0:1.8.1 oder 1-0:1.8.2 (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 1502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: energy + example: + default: + choice: [] + unit: + description: OBIS Kennzahl für Energieverbrauch + help: Typischerweise 1-0:1.8.0, bei Mehrtarifzählern 1-0:1.8.1 oder 1-0:1.8.2 + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/dsmr_0.yaml b/templates/release/de/meter/dsmr_0.yaml deleted file mode 100644 index 2586b6d374..0000000000 --- a/templates/release/de/meter/dsmr_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: DSMR -render: - - usage: grid - default: | - type: template - template: dsmr - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 1502 # Port, optional - advanced: | - type: template - template: dsmr - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 1502 # Port, optional - energy: # OBIS Kennzahl für Energieverbrauch, Typischerweise 1-0:1.8.0, bei Mehrtarifzählern 1-0:1.8.1 oder 1-0:1.8.2 (optional) diff --git a/templates/release/de/meter/dzg-dvh4013.yaml b/templates/release/de/meter/dzg-dvh4013.yaml new file mode 100644 index 0000000000..8a56066ec7 --- /dev/null +++ b/templates/release/de/meter/dzg-dvh4013.yaml @@ -0,0 +1,43 @@ +template: dzg +product: + identifier: dzg-dvh4013 + brand: DZG + description: DVH4013 +render: + - usage: charge + default: | + type: template + template: dzg + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/dzg_0.yaml b/templates/release/de/meter/dzg_0.yaml deleted file mode 100644 index 944659a798..0000000000 --- a/templates/release/de/meter/dzg_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: DZG - description: DVH4013 -render: - - usage: charge - default: | - type: template - template: dzg - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/e3-dc.yaml b/templates/release/de/meter/e3-dc.yaml new file mode 100644 index 0000000000..bd4ea6138a --- /dev/null +++ b/templates/release/de/meter/e3-dc.yaml @@ -0,0 +1,146 @@ +template: e3dc-rscp +product: + identifier: e3-dc + brand: E3/DC +capabilities: ["battery-control"] +description: | + Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key (=RSCP-Passwort) muss im Hauskraftwerk unter Personalisieren/Benutzerprofil angelegt werden. Die IP-Adressen von evcc und des Hauskraftwerks müssen sich im selben Subnetz befinden. + + **Achtung**: Die aktive Batteriesteuerung überschreibt Einstellungen im Smart-Power/Betriebsbereich. + +render: + - usage: grid + default: | + type: template + template: e3dc-rscp + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 5033 # Port, optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + key: + advanced: | + type: template + template: e3dc-rscp + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 5033 # Port, optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + key: + dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) + - usage: pv + default: | + type: template + template: e3dc-rscp + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 5033 # Port, optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + key: + advanced: | + type: template + template: e3dc-rscp + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 5033 # Port, optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + key: + dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: e3dc-rscp + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 5033 # Port, optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + key: + advanced: | + type: template + template: e3dc-rscp + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 5033 # Port, optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + key: + dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 5033 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: key + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: dischargelimit + example: + default: + choice: [] + unit: + description: Entladelimit in W + help: Limitiert die Entladeleistung im 'Halten' Batteriemodus + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/e3dc-rscp_0.yaml b/templates/release/de/meter/e3dc-rscp_0.yaml deleted file mode 100644 index 5c940f94e7..0000000000 --- a/templates/release/de/meter/e3dc-rscp_0.yaml +++ /dev/null @@ -1,71 +0,0 @@ -product: - brand: E3/DC -capabilities: ["battery-control"] -description: | - Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key (=RSCP-Passwort) muss im Hauskraftwerk unter Personalisieren/Benutzerprofil angelegt werden. Die IP-Adressen von evcc und des Hauskraftwerks müssen sich im selben Subnetz befinden. - - **Achtung**: Die aktive Batteriesteuerung überschreibt Einstellungen im Smart-Power/Betriebsbereich. - -render: - - usage: grid - default: | - type: template - template: e3dc-rscp - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 5033 # Port, optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: - advanced: | - type: template - template: e3dc-rscp - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 5033 # Port, optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: - dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) - - usage: pv - default: | - type: template - template: e3dc-rscp - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 5033 # Port, optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: - advanced: | - type: template - template: e3dc-rscp - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 5033 # Port, optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: - dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: e3dc-rscp - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 5033 # Port, optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: - advanced: | - type: template - template: e3dc-rscp - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 5033 # Port, optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: - dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/eastron-sdm120-modbus.yaml b/templates/release/de/meter/eastron-sdm120-modbus.yaml new file mode 100644 index 0000000000..73b2709021 --- /dev/null +++ b/templates/release/de/meter/eastron-sdm120-modbus.yaml @@ -0,0 +1,79 @@ +template: eastron-sdm120 +product: + identifier: eastron-sdm120-modbus + brand: Eastron + description: SDM120-Modbus +render: + - usage: grid + default: | + type: template + template: eastron-sdm120 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm120 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: eastron-sdm120 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/eastron-sdm120_0.yaml b/templates/release/de/meter/eastron-sdm120_0.yaml deleted file mode 100644 index c523f27872..0000000000 --- a/templates/release/de/meter/eastron-sdm120_0.yaml +++ /dev/null @@ -1,58 +0,0 @@ -product: - brand: Eastron - description: SDM120-Modbus -render: - - usage: grid - default: | - type: template - template: eastron-sdm120 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm120 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: eastron-sdm120 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron-sdm220-230.yaml b/templates/release/de/meter/eastron-sdm220-230.yaml new file mode 100644 index 0000000000..c6cf09acf7 --- /dev/null +++ b/templates/release/de/meter/eastron-sdm220-230.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm220_230 +product: + identifier: eastron-sdm220-230 + brand: Eastron + description: SDM220/230 +render: + - usage: grid + default: | + type: template + template: eastron-sdm220_230 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm220_230 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/eastron-sdm220_230_0.yaml b/templates/release/de/meter/eastron-sdm220_230_0.yaml deleted file mode 100644 index 52e4d9b147..0000000000 --- a/templates/release/de/meter/eastron-sdm220_230_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM220/230 -render: - - usage: grid - default: | - type: template - template: eastron-sdm220_230 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm220_230 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron-sdm220_230_1.yaml b/templates/release/de/meter/eastron-sdm220_230_1.yaml deleted file mode 100644 index 17900c48e0..0000000000 --- a/templates/release/de/meter/eastron-sdm220_230_1.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM110-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron-sdm220_230 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm220_230 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron-sdm220_230_2.yaml b/templates/release/de/meter/eastron-sdm220_230_2.yaml deleted file mode 100644 index dc9eab47b9..0000000000 --- a/templates/release/de/meter/eastron-sdm220_230_2.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM111-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron-sdm220_230 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm220_230 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron-sdm630-modbus.yaml b/templates/release/de/meter/eastron-sdm630-modbus.yaml new file mode 100644 index 0000000000..bb5ee3cccb --- /dev/null +++ b/templates/release/de/meter/eastron-sdm630-modbus.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: eastron-sdm630-modbus + brand: Eastron + description: SDM630-Modbus +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/eastron-sdm72_0.yaml b/templates/release/de/meter/eastron-sdm72_0.yaml deleted file mode 100644 index bbc7de94e2..0000000000 --- a/templates/release/de/meter/eastron-sdm72_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM72D-M -render: - - usage: grid - default: | - type: template - template: eastron-sdm72 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm72 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron-sdm72d-m.yaml b/templates/release/de/meter/eastron-sdm72d-m.yaml new file mode 100644 index 0000000000..9ebaf66503 --- /dev/null +++ b/templates/release/de/meter/eastron-sdm72d-m.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm72 +product: + identifier: eastron-sdm72d-m + brand: Eastron + description: SDM72D-M +render: + - usage: grid + default: | + type: template + template: eastron-sdm72 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm72 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/eastron-sdm72dm-v2.yaml b/templates/release/de/meter/eastron-sdm72dm-v2.yaml new file mode 100644 index 0000000000..552313a71d --- /dev/null +++ b/templates/release/de/meter/eastron-sdm72dm-v2.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: eastron-sdm72dm-v2 + brand: Eastron + description: SDM72DM-V2 +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/eastron_0.yaml b/templates/release/de/meter/eastron_0.yaml deleted file mode 100644 index c15d696c08..0000000000 --- a/templates/release/de/meter/eastron_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM630-Modbus -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron_1.yaml b/templates/release/de/meter/eastron_1.yaml deleted file mode 100644 index dbc823ff78..0000000000 --- a/templates/release/de/meter/eastron_1.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM72DM-V2 -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron_2.yaml b/templates/release/de/meter/eastron_2.yaml deleted file mode 100644 index 02e5115691..0000000000 --- a/templates/release/de/meter/eastron_2.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM120-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron_3.yaml b/templates/release/de/meter/eastron_3.yaml deleted file mode 100644 index 3086ab92f7..0000000000 --- a/templates/release/de/meter/eastron_3.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM122-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/eastron_4.yaml b/templates/release/de/meter/eastron_4.yaml deleted file mode 100644 index 407eedce68..0000000000 --- a/templates/release/de/meter/eastron_4.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Kostal - description: Energy Meter P (KEM-P) -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/enphase-iq-envoy.yaml b/templates/release/de/meter/enphase-iq-envoy.yaml new file mode 100644 index 0000000000..c9b71016f1 --- /dev/null +++ b/templates/release/de/meter/enphase-iq-envoy.yaml @@ -0,0 +1,88 @@ +template: enphase +product: + identifier: enphase-iq-envoy + brand: Enphase + description: IQ Envoy +description: | + Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vom Typ "AC Battery" unterstützt. +render: + - usage: grid + default: | + type: template + template: enphase + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + advanced: | + type: template + template: enphase + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: enphase + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + advanced: | + type: template + template: enphase + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: battery + default: | + type: template + template: enphase + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + advanced: | + type: template + template: enphase + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + capacity: 50 # Akkukapazität (kWh), optional + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: 'Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication' + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/enphase_0.yaml b/templates/release/de/meter/enphase_0.yaml deleted file mode 100644 index 9d85fe1284..0000000000 --- a/templates/release/de/meter/enphase_0.yaml +++ /dev/null @@ -1,49 +0,0 @@ -product: - brand: Enphase - description: IQ Envoy -description: | - Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vom Typ "AC Battery" unterstützt. -render: - - usage: grid - default: | - type: template - template: enphase - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - advanced: | - type: template - template: enphase - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - - usage: pv - default: | - type: template - template: enphase - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - advanced: | - type: template - template: enphase - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - - usage: battery - default: | - type: template - template: enphase - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - advanced: | - type: template - template: enphase - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - capacity: 50 # Akkukapazität (kWh), optional - cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/meter/esphome-dlms-austria_0.yaml b/templates/release/de/meter/esphome-dlms-austria_0.yaml deleted file mode 100644 index e4071421d2..0000000000 --- a/templates/release/de/meter/esphome-dlms-austria_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ESPHome - description: DLMS Meter Austria -description: | - Benötigt ein ESPHome Gerät mit der `dlms_meter` Komponente (z.B. von `github://SimonFischer04/esphome@dlms-meter`), - konfiguriert für österreichische DLMS-Zähler. - -render: - - usage: grid - default: | - type: template - template: esphome-dlms-austria - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: esphome-dlms-austria - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - timeout: 10s # Zeitüberschreitung, optional diff --git a/templates/release/de/meter/esphome-dlms-meter-austria.yaml b/templates/release/de/meter/esphome-dlms-meter-austria.yaml new file mode 100644 index 0000000000..d0abc794bf --- /dev/null +++ b/templates/release/de/meter/esphome-dlms-meter-austria.yaml @@ -0,0 +1,41 @@ +template: esphome-dlms-austria +product: + identifier: esphome-dlms-meter-austria + brand: ESPHome + description: DLMS Meter Austria +description: | + Benötigt ein ESPHome Gerät mit der `dlms_meter` Komponente (z.B. von `github://SimonFischer04/esphome@dlms-meter`), + konfiguriert für österreichische DLMS-Zähler. + +render: + - usage: grid + default: | + type: template + template: esphome-dlms-austria + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: esphome-dlms-austria + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + timeout: 10s # Zeitüberschreitung, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 10s + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/esphome-dsmr.yaml b/templates/release/de/meter/esphome-dsmr.yaml new file mode 100644 index 0000000000..527965ccd1 --- /dev/null +++ b/templates/release/de/meter/esphome-dsmr.yaml @@ -0,0 +1,37 @@ +template: slimmelezer +product: + identifier: esphome-dsmr + brand: ESPHome + description: DSMR +render: + - usage: grid + default: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: scale + example: 1 | 10 | 100 | 1000 + default: 1000 + choice: [] + unit: + description: Skalierungsfaktor + help: Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/fenecon.yaml b/templates/release/de/meter/fenecon.yaml new file mode 100644 index 0000000000..6e2ab29009 --- /dev/null +++ b/templates/release/de/meter/fenecon.yaml @@ -0,0 +1,104 @@ +template: openems +product: + identifier: fenecon + brand: FENECON +capabilities: ["battery-control"] +description: | + Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. + +render: + - usage: grid + default: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: pv + default: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + battery: ess0 # steuerbare Batterie Komponente (optional) + watchdog: 60s # abgestimmt auf das API-Timeout (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: password + example: + default: user + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true + - name: battery + example: ess0 + default: + choice: [] + unit: + description: + help: steuerbare Batterie Komponente + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: abgestimmt auf das API-Timeout + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/fox-ess-h1_0.yaml b/templates/release/de/meter/fox-ess-h1_0.yaml deleted file mode 100644 index 5e59afc060..0000000000 --- a/templates/release/de/meter/fox-ess-h1_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: FoxESS - description: H1 Series Hybrid Inverter -render: - - usage: pv - default: | - type: template - template: fox-ess-h1 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: fox-ess-h1 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/fox-ess-h3-smart_0.yaml b/templates/release/de/meter/fox-ess-h3-smart_0.yaml deleted file mode 100644 index f4845b0e92..0000000000 --- a/templates/release/de/meter/fox-ess-h3-smart_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: FoxESS - description: H3-Smart Series Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: fox-ess-h3-smart - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3-smart - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: fox-ess-h3-smart - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3-smart - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/fox-ess-h3_0.yaml b/templates/release/de/meter/fox-ess-h3_0.yaml deleted file mode 100644 index 97c77b3ab0..0000000000 --- a/templates/release/de/meter/fox-ess-h3_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: FoxESS - description: H3 Series Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: fox-ess-h3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: fox-ess-h3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml b/templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..d696651368 --- /dev/null +++ b/templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml @@ -0,0 +1,74 @@ +template: fox-ess-h1 +product: + identifier: foxess-h1-series-hybrid-inverter + brand: FoxESS + description: H1 Series Hybrid Inverter +render: + - usage: pv + default: | + type: template + template: fox-ess-h1 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: fox-ess-h1 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml b/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..893a87b25b --- /dev/null +++ b/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: fox-ess-h3 +product: + identifier: foxess-h3-series-hybrid-inverter + brand: FoxESS + description: H3 Series Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fox-ess-h3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: fox-ess-h3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: fox-ess-h3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml b/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..0069b8b62f --- /dev/null +++ b/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: fox-ess-h3-smart +product: + identifier: foxess-h3-smart-series-hybrid-inverter + brand: FoxESS + description: H3-Smart Series Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fox-ess-h3-smart + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3-smart + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: fox-ess-h3-smart + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3-smart + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: fox-ess-h3-smart + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3-smart + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/fritzdect_0.yaml b/templates/release/de/meter/fritzdect_0.yaml deleted file mode 100644 index b25f7e9f3a..0000000000 --- a/templates/release/de/meter/fritzdect_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: AVM - description: FritzDECT - group: Schaltbare Steckdosen -render: - - usage: pv - default: | - type: template - template: fritzdect - usage: pv - uri: https://fritz.box # URI, HTTP(S) Adresse (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. - - usage: charge - default: | - type: template - template: fritzdect - usage: charge - uri: https://fritz.box # URI, HTTP(S) Adresse (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - ain: 307788992233 # Aktoridentifikationsnummer (AIN), Ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen. diff --git a/templates/release/de/meter/fronius-gen24_0.yaml b/templates/release/de/meter/fronius-gen24_0.yaml deleted file mode 100644 index bddc2cc7dc..0000000000 --- a/templates/release/de/meter/fronius-gen24_0.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Fronius - description: Symo GEN24 Plus -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) - - usage: pv - default: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/fronius-gen24_1.yaml b/templates/release/de/meter/fronius-gen24_1.yaml deleted file mode 100644 index 01aacb0db2..0000000000 --- a/templates/release/de/meter/fronius-gen24_1.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Fronius - description: Primo GEN24 Plus -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) - - usage: pv - default: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/fronius-ohmpilot.yaml b/templates/release/de/meter/fronius-ohmpilot.yaml new file mode 100644 index 0000000000..7c77e4bb17 --- /dev/null +++ b/templates/release/de/meter/fronius-ohmpilot.yaml @@ -0,0 +1,37 @@ +template: fronius-ohmpilot +product: + identifier: fronius-ohmpilot + brand: Fronius + description: Ohmpilot +render: + - usage: aux + default: | + type: template + template: fronius-ohmpilot + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: fronius-ohmpilot + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + key: 0 # ID des Ohmpilot im SolarAPI, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: key + example: + default: 0 + choice: [] + unit: + description: ID des Ohmpilot im SolarAPI + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/fronius-ohmpilot_0.yaml b/templates/release/de/meter/fronius-ohmpilot_0.yaml deleted file mode 100644 index 4899aae13f..0000000000 --- a/templates/release/de/meter/fronius-ohmpilot_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Fronius - description: Ohmpilot -render: - - usage: aux - default: | - type: template - template: fronius-ohmpilot - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: fronius-ohmpilot - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname - key: 0 # ID des Ohmpilot im SolarAPI, optional diff --git a/templates/release/de/meter/fronius-primo-gen24-plus.yaml b/templates/release/de/meter/fronius-primo-gen24-plus.yaml new file mode 100644 index 0000000000..07bdd65d70 --- /dev/null +++ b/templates/release/de/meter/fronius-primo-gen24-plus.yaml @@ -0,0 +1,105 @@ +template: fronius-gen24 +product: + identifier: fronius-primo-gen24-plus + brand: Fronius + description: Primo GEN24 Plus +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) + - usage: pv + default: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: id + example: + default: 200 + choice: [] + unit: + description: + help: 'Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201).' + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/fronius-smartmeter-via-inverter.yaml b/templates/release/de/meter/fronius-smartmeter-via-inverter.yaml new file mode 100644 index 0000000000..c56c0f0749 --- /dev/null +++ b/templates/release/de/meter/fronius-smartmeter-via-inverter.yaml @@ -0,0 +1,44 @@ +template: sunspec-meter +product: + identifier: fronius-smartmeter-via-inverter + brand: Fronius + description: Smartmeter (über Wechselrichter) +render: + - usage: grid + default: | + type: template + template: sunspec-meter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-meter + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/fronius-solar-api-v1.yaml b/templates/release/de/meter/fronius-solar-api-v1.yaml new file mode 100644 index 0000000000..c69ce0d5fe --- /dev/null +++ b/templates/release/de/meter/fronius-solar-api-v1.yaml @@ -0,0 +1,109 @@ +template: fronius-solarapi-v1 +product: + identifier: fronius-solar-api-v1 + brand: Fronius + description: Solar API V1 +capabilities: ["battery-control"] +description: | + Solar API sollte nur als Fallback genutzt werden. Die Integration über Modbus ist bevorzugt. + + Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt. + + **Achtung**: Die aktive Batteriesteuerung sollte nur verwendet werden, wenn keine weiteren Einstellungen für die zeitabhängige Batteriesteuerung in der Wechselrichter-Konfiguration unter "Energiemanagement" - "Batteriemanagement" getätigt wurden, denn bestehende Einstellungen werden überschrieben. Es ist der geeignete Konfigurationspfad auszuwählen! + +render: + - usage: grid + default: | + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + advanced: | + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional) + - usage: pv + default: | + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + advanced: | + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional) + - usage: battery + default: | + type: template + template: fronius-solarapi-v1 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + advanced: | + type: template + template: fronius-solarapi-v1 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + capacity: 50 # Akkukapazität (kWh), optional + batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: customer + choice: [] + unit: + description: Benutzername (für aktive Batteriesteuerung) + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort (für aktive Batteriesteuerung) + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: batteryconfiguri + example: + default: /config + choice: ['/config', '/api/config'] + unit: + description: Firmware Versionen ab 1.36.5-1 erfordern /api/config. + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/fronius-solarapi-v1_0.yaml b/templates/release/de/meter/fronius-solarapi-v1_0.yaml deleted file mode 100644 index a1b28239ef..0000000000 --- a/templates/release/de/meter/fronius-solarapi-v1_0.yaml +++ /dev/null @@ -1,58 +0,0 @@ -product: - brand: Fronius - description: Solar API V1 -capabilities: ["battery-control"] -description: | - Solar API sollte nur als Fallback genutzt werden. Die Integration über Modbus ist bevorzugt. - - Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt. - - **Achtung**: Die aktive Batteriesteuerung sollte nur verwendet werden, wenn keine weiteren Einstellungen für die zeitabhängige Batteriesteuerung in der Wechselrichter-Konfiguration unter "Energiemanagement" - "Batteriemanagement" getätigt wurden, denn bestehende Einstellungen werden überschrieben. - -render: - - usage: grid - default: | - type: template - template: fronius-solarapi-v1 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - advanced: | - type: template - template: fronius-solarapi-v1 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: fronius-solarapi-v1 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - advanced: | - type: template - template: fronius-solarapi-v1 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: battery - default: | - type: template - template: fronius-solarapi-v1 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - advanced: | - type: template - template: fronius-solarapi-v1 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/fronius-symo-gen24-plus.yaml b/templates/release/de/meter/fronius-symo-gen24-plus.yaml new file mode 100644 index 0000000000..8311dbc743 --- /dev/null +++ b/templates/release/de/meter/fronius-symo-gen24-plus.yaml @@ -0,0 +1,105 @@ +template: fronius-gen24 +product: + identifier: fronius-symo-gen24-plus + brand: Fronius + description: Symo GEN24 Plus +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) + - usage: pv + default: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: id + example: + default: 200 + choice: [] + unit: + description: + help: 'Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201).' + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml b/templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml new file mode 100644 index 0000000000..2a1bac8b9a --- /dev/null +++ b/templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml @@ -0,0 +1,150 @@ +template: solis-hybrid +product: + identifier: ginlong-solis-hybrid-inverter-rhi-series + brand: Ginlong + description: Solis Hybrid Inverter (RHI series) +render: + - usage: grid + default: | + type: template + template: solis-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: solis-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml b/templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml new file mode 100644 index 0000000000..f66ded4712 --- /dev/null +++ b/templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml @@ -0,0 +1,150 @@ +template: solis-hybrid-s +product: + identifier: ginlong-solis-hybrid-inverter-s-series + brand: Ginlong + description: Solis Hybrid Inverter (S Series) +render: + - usage: grid + default: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/ginlong-solis-inverter.yaml b/templates/release/de/meter/ginlong-solis-inverter.yaml new file mode 100644 index 0000000000..92f207ca67 --- /dev/null +++ b/templates/release/de/meter/ginlong-solis-inverter.yaml @@ -0,0 +1,61 @@ +template: solis +product: + identifier: ginlong-solis-inverter + brand: Ginlong + description: Solis Inverter +render: + - usage: grid + default: | + type: template + template: solis + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/go-e-controller.yaml b/templates/release/de/meter/go-e-controller.yaml new file mode 100644 index 0000000000..88aa70d397 --- /dev/null +++ b/templates/release/de/meter/go-e-controller.yaml @@ -0,0 +1,28 @@ +template: go-e-controller +product: + identifier: go-e-controller + brand: go-e + description: Controller +render: + - usage: grid + default: | + type: template + template: go-e-controller + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: go-e-controller + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/go-e-controller_0.yaml b/templates/release/de/meter/go-e-controller_0.yaml deleted file mode 100644 index 28b9140a62..0000000000 --- a/templates/release/de/meter/go-e-controller_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: go-e - description: Controller -render: - - usage: grid - default: | - type: template - template: go-e-controller - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: go-e-controller - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/goodwe-dt_0.yaml b/templates/release/de/meter/goodwe-dt_0.yaml deleted file mode 100644 index f4a2cd4b5e..0000000000 --- a/templates/release/de/meter/goodwe-dt_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: GoodWe - description: SDT/DT Inverter -render: - - usage: pv - default: | - type: template - template: goodwe-dt - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml b/templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml new file mode 100644 index 0000000000..ff06b0509b --- /dev/null +++ b/templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml @@ -0,0 +1,204 @@ +template: goodwe-hybrid +product: + identifier: goodwe-et-eh-bh-bt-hybrid-inverter + brand: GoodWe + description: ET/EH/BH/BT Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: goodwe-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + advanced: | + type: template + template: goodwe-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + - usage: pv + default: | + type: template + template: goodwe-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + advanced: | + type: template + template: goodwe-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: goodwe-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + advanced: | + type: template + template: goodwe-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip', 'udp'] + unit: + description: + help: + advanced: false + optional: true + - name: battery + example: + default: 1 + choice: ['1', '2'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true + udp: true \ No newline at end of file diff --git a/templates/release/de/meter/goodwe-goodwe-over-wifi.yaml b/templates/release/de/meter/goodwe-goodwe-over-wifi.yaml new file mode 100644 index 0000000000..d6a2350af9 --- /dev/null +++ b/templates/release/de/meter/goodwe-goodwe-over-wifi.yaml @@ -0,0 +1,35 @@ +template: goodwe-wifi +product: + identifier: goodwe-goodwe-over-wifi + brand: GoodWe + description: GoodWe over Wifi +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: goodwe-wifi + usage: grid + uri: # IP-Adresse des Hostname, HTTP(S) Adresse (optional) + - usage: pv + default: | + type: template + template: goodwe-wifi + usage: pv + uri: # IP-Adresse des Hostname, HTTP(S) Adresse (optional) + - usage: battery + default: | + type: template + template: goodwe-wifi + usage: battery + uri: # IP-Adresse des Hostname, HTTP(S) Adresse (optional) +params: + - name: uri + example: + default: + choice: [] + unit: + description: IP-Adresse des Hostname + help: HTTP(S) Adresse + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/goodwe-hybrid_0.yaml b/templates/release/de/meter/goodwe-hybrid_0.yaml deleted file mode 100644 index d0ad290186..0000000000 --- a/templates/release/de/meter/goodwe-hybrid_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: GoodWe - description: ET/EH/BH/BT Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: goodwe-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - advanced: | - type: template - template: goodwe-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - - usage: pv - default: | - type: template - template: goodwe-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - advanced: | - type: template - template: goodwe-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: goodwe-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - advanced: | - type: template - template: goodwe-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/goodwe-sdt-dt-inverter.yaml b/templates/release/de/meter/goodwe-sdt-dt-inverter.yaml new file mode 100644 index 0000000000..9780442ace --- /dev/null +++ b/templates/release/de/meter/goodwe-sdt-dt-inverter.yaml @@ -0,0 +1,50 @@ +template: goodwe-dt +product: + identifier: goodwe-sdt-dt-inverter + brand: GoodWe + description: SDT/DT Inverter +render: + - usage: pv + default: | + type: template + template: goodwe-dt + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/goodwe-wifi_0.yaml b/templates/release/de/meter/goodwe-wifi_0.yaml deleted file mode 100644 index 3029869815..0000000000 --- a/templates/release/de/meter/goodwe-wifi_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: GoodWe - description: GoodWe over Wifi -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: goodwe-wifi - usage: grid - uri: # IP-Adresse des Hostname, HTTP(S) Adresse (optional) - - usage: pv - default: | - type: template - template: goodwe-wifi - usage: pv - uri: # IP-Adresse des Hostname, HTTP(S) Adresse (optional) - - usage: battery - default: | - type: template - template: goodwe-wifi - usage: battery - uri: # IP-Adresse des Hostname, HTTP(S) Adresse (optional) diff --git a/templates/release/de/meter/growatt-hybrid-inverter.yaml b/templates/release/de/meter/growatt-hybrid-inverter.yaml new file mode 100644 index 0000000000..2306a0fb74 --- /dev/null +++ b/templates/release/de/meter/growatt-hybrid-inverter.yaml @@ -0,0 +1,194 @@ +template: growatt-hybrid +product: + identifier: growatt-hybrid-inverter + brand: Growatt + description: Hybrid Inverter +capabilities: ["battery-control"] +description: | + Um die aktive Ladesteuerung nutzen zu können ist eine einmalige manuelle Einrichtung notwendig. + Es müssen die Modbusregister `1100, 1101, 1102` gleichzeitig (via "write multiple", FC 16) auf die Werte `0, 5947, 0` gesetzt werden. + Das kann zB. mit der [Modbus CLI](https://github.com/favalex/modbus-cli) gemacht werden: `modbus [...] H@1100=0 H@1101=5947 H@1102=0`. + Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modus, d.h. dieser kann nicht anderweitig genutzt werden. + +render: + - usage: grid + default: | + type: template + template: growatt-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: growatt-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: growatt-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/growatt-hybrid-tlxh_0.yaml b/templates/release/de/meter/growatt-hybrid-tlxh_0.yaml deleted file mode 100644 index 15bd36a6f6..0000000000 --- a/templates/release/de/meter/growatt-hybrid-tlxh_0.yaml +++ /dev/null @@ -1,148 +0,0 @@ -product: - brand: Growatt - description: TL-X(H) Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: growatt-hybrid-tlxh - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid-tlxh - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: growatt-hybrid-tlxh - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid-tlxh - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: growatt-hybrid-tlxh - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid-tlxh - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/growatt-hybrid_0.yaml b/templates/release/de/meter/growatt-hybrid_0.yaml deleted file mode 100644 index 81e601ddbf..0000000000 --- a/templates/release/de/meter/growatt-hybrid_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: Growatt - description: Hybrid Inverter -capabilities: ["battery-control"] -description: | - Um die aktive Ladesteuerung nutzen zu können ist eine einmalige manuelle Einrichtung notwendig. - Es müssen die Modbusregister `1100, 1101, 1102` gleichzeitig (via "write multiple", FC 16) auf die Werte `0, 5947, 0` gesetzt werden. - Das kann zB. mit der [Modbus CLI](https://github.com/favalex/modbus-cli) gemacht werden: `modbus [...] H@1100=0 H@1101=5947 H@1102=0`. - Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modus, d.h. dieser kann nicht anderweitig genutzt werden. - -render: - - usage: grid - default: | - type: template - template: growatt-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: growatt-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: growatt-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml b/templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml new file mode 100644 index 0000000000..f579df5921 --- /dev/null +++ b/templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml @@ -0,0 +1,188 @@ +template: growatt-hybrid-tlxh +product: + identifier: growatt-tl-x-h-hybrid-inverter + brand: Growatt + description: TL-X(H) Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: growatt-hybrid-tlxh + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid-tlxh + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: growatt-hybrid-tlxh + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid-tlxh + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: growatt-hybrid-tlxh + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid-tlxh + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/homematic-ip.yaml b/templates/release/de/meter/homematic-ip.yaml new file mode 100644 index 0000000000..7fbebea3e7 --- /dev/null +++ b/templates/release/de/meter/homematic-ip.yaml @@ -0,0 +1,121 @@ +template: homematic +product: + identifier: homematic-ip + brand: Homematic IP + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: homematic + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + advanced: | + type: template + template: homematic + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + - usage: pv + default: | + type: template + template: homematic + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + advanced: | + type: template + template: homematic + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + - usage: charge + default: | + type: template + template: homematic + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + advanced: | + type: template + template: homematic + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: device + example: 0001EE89AAD848 + default: + choice: [] + unit: + description: Geräteadresse/Seriennummer + help: Homematic Geräte Id, wie im CCU Webfrontend angezeigt. + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: meterchannel + example: + default: 6 + choice: [] + unit: + description: Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1) + help: Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h) + help: Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/homematic_0.yaml b/templates/release/de/meter/homematic_0.yaml deleted file mode 100644 index 703dd245d1..0000000000 --- a/templates/release/de/meter/homematic_0.yaml +++ /dev/null @@ -1,64 +0,0 @@ -product: - brand: Homematic IP - group: Schaltbare Steckdosen -render: - - usage: grid - default: | - type: template - template: homematic - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - advanced: | - type: template - template: homematic - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) - - usage: pv - default: | - type: template - template: homematic - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - advanced: | - type: template - template: homematic - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) - - usage: charge - default: | - type: template - template: homematic - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - advanced: | - type: template - template: homematic - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) diff --git a/templates/release/de/meter/homewizard-kwh-meter.yaml b/templates/release/de/meter/homewizard-kwh-meter.yaml new file mode 100644 index 0000000000..1747f8c5c5 --- /dev/null +++ b/templates/release/de/meter/homewizard-kwh-meter.yaml @@ -0,0 +1,28 @@ +template: homewizard-kwh +product: + identifier: homewizard-kwh-meter + brand: HomeWizard + description: kWh Meter +render: + - usage: pv + default: | + type: template + template: homewizard-kwh + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: charge + default: | + type: template + template: homewizard-kwh + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/homewizard-kwh_0.yaml b/templates/release/de/meter/homewizard-kwh_0.yaml deleted file mode 100644 index 8e34586500..0000000000 --- a/templates/release/de/meter/homewizard-kwh_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: HomeWizard - description: kWh Meter -render: - - usage: pv - default: | - type: template - template: homewizard-kwh - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: charge - default: | - type: template - template: homewizard-kwh - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/homewizard-wi-fi-p1-meter.yaml b/templates/release/de/meter/homewizard-wi-fi-p1-meter.yaml new file mode 100644 index 0000000000..2c7ff6ad02 --- /dev/null +++ b/templates/release/de/meter/homewizard-wi-fi-p1-meter.yaml @@ -0,0 +1,22 @@ +template: homewizard +product: + identifier: homewizard-wi-fi-p1-meter + brand: HomeWizard + description: Wi-Fi P1 Meter +render: + - usage: grid + default: | + type: template + template: homewizard + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/homewizard_0.yaml b/templates/release/de/meter/homewizard_0.yaml deleted file mode 100644 index 4ccb23f894..0000000000 --- a/templates/release/de/meter/homewizard_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: HomeWizard - description: Wi-Fi P1 Meter -render: - - usage: grid - default: | - type: template - template: homewizard - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/hoymiles-ahoydtu_0.yaml b/templates/release/de/meter/hoymiles-ahoydtu_0.yaml deleted file mode 100644 index 44b5f853b2..0000000000 --- a/templates/release/de/meter/hoymiles-ahoydtu_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: Hoymiles - description: HM & HMS Series (via AhoyDTU) -render: - - usage: pv - default: | - type: template - template: hoymiles-ahoydtu - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - id: 0 # Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID], optional diff --git a/templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml b/templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml new file mode 100644 index 0000000000..08517f1767 --- /dev/null +++ b/templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml @@ -0,0 +1,32 @@ +template: hoymiles-ahoydtu +product: + identifier: hoymiles-hm-and-hms-series-via-ahoydtu + brand: Hoymiles + description: HM & HMS Series (via AhoyDTU) +render: + - usage: pv + default: | + type: template + template: hoymiles-ahoydtu + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + id: 0 # Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID], optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: id + example: + default: 0 + choice: [] + unit: + description: 'Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID]' + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml b/templates/release/de/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml new file mode 100644 index 0000000000..d3872c682e --- /dev/null +++ b/templates/release/de/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml @@ -0,0 +1,22 @@ +template: hoymiles-opendtu +product: + identifier: hoymiles-hm-and-hms-series-via-opendtu + brand: Hoymiles + description: HM & HMS Series (via OpenDTU) +render: + - usage: pv + default: | + type: template + template: hoymiles-opendtu + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/hoymiles-opendtu_0.yaml b/templates/release/de/meter/hoymiles-opendtu_0.yaml deleted file mode 100644 index 3017a63068..0000000000 --- a/templates/release/de/meter/hoymiles-opendtu_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Hoymiles - description: HM & HMS Series (via OpenDTU) -render: - - usage: pv - default: | - type: template - template: hoymiles-opendtu - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/huawei-dongle_0.yaml b/templates/release/de/meter/huawei-dongle_0.yaml deleted file mode 100644 index ff624097ed..0000000000 --- a/templates/release/de/meter/huawei-dongle_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Huawei - description: SUN2000 (SDongle) -description: | - Erfordert "Modbus/TCP". Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. - Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 - -render: - - usage: pv - default: | - type: template - template: huawei-dongle - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional diff --git a/templates/release/de/meter/huawei-emma.yaml b/templates/release/de/meter/huawei-emma.yaml new file mode 100644 index 0000000000..b4cff0e827 --- /dev/null +++ b/templates/release/de/meter/huawei-emma.yaml @@ -0,0 +1,95 @@ +template: huawei-emma +product: + identifier: huawei-emma + brand: Huawei + description: EMMA +render: + - usage: grid + default: | + type: template + template: huawei-emma + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: huawei-emma + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: huawei-emma + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: huawei-emma + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: huawei-emma + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: huawei-emma + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/huawei-emma_0.yaml b/templates/release/de/meter/huawei-emma_0.yaml deleted file mode 100644 index 5cec29505b..0000000000 --- a/templates/release/de/meter/huawei-emma_0.yaml +++ /dev/null @@ -1,68 +0,0 @@ -product: - brand: Huawei - description: EMMA -render: - - usage: grid - default: | - type: template - template: huawei-emma - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: huawei-emma - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: huawei-emma - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: huawei-emma - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: huawei-emma - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: huawei-emma - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/huawei-smartlogger.yaml b/templates/release/de/meter/huawei-smartlogger.yaml new file mode 100644 index 0000000000..2cb7a7e1df --- /dev/null +++ b/templates/release/de/meter/huawei-smartlogger.yaml @@ -0,0 +1,133 @@ +template: huawei-smartlogger +product: + identifier: huawei-smartlogger + brand: Huawei + description: SmartLogger +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: huawei-smartlogger + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + advanced: | + type: template + template: huawei-smartlogger + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: huawei-smartlogger + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + advanced: | + type: template + template: huawei-smartlogger + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + storageunit: 1 # optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: huawei-smartlogger + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + advanced: | + type: template + template: huawei-smartlogger + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + storageunit: 1 # optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 15s + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/huawei-smartlogger_0.yaml b/templates/release/de/meter/huawei-smartlogger_0.yaml deleted file mode 100644 index d476b93eac..0000000000 --- a/templates/release/de/meter/huawei-smartlogger_0.yaml +++ /dev/null @@ -1,79 +0,0 @@ -product: - brand: Huawei - description: SmartLogger -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: huawei-smartlogger - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - advanced: | - type: template - template: huawei-smartlogger - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: huawei-smartlogger - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - advanced: | - type: template - template: huawei-smartlogger - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: huawei-smartlogger - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - advanced: | - type: template - template: huawei-smartlogger - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/huawei-sun2000-sdongle.yaml b/templates/release/de/meter/huawei-sun2000-sdongle.yaml new file mode 100644 index 0000000000..f7bf90881c --- /dev/null +++ b/templates/release/de/meter/huawei-sun2000-sdongle.yaml @@ -0,0 +1,47 @@ +template: huawei-dongle +product: + identifier: huawei-sun2000-sdongle + brand: Huawei + description: SUN2000 (SDongle) +description: | + Erfordert "Modbus/TCP". Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. + Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + +render: + - usage: pv + default: | + type: template + template: huawei-dongle + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 15s + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/huawei-sun2000.yaml b/templates/release/de/meter/huawei-sun2000.yaml new file mode 100644 index 0000000000..b249bab017 --- /dev/null +++ b/templates/release/de/meter/huawei-sun2000.yaml @@ -0,0 +1,240 @@ +template: huawei-sun2000 +product: + identifier: huawei-sun2000 + brand: Huawei + description: SUN2000 +capabilities: ["battery-control"] +description: | + Grid und Batterie erfordern den PowerSensor. + "Modbus/TCP" erfordert Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. + Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + +render: + - usage: grid + default: | + type: template + template: huawei-sun2000 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + advanced: | + type: template + template: huawei-sun2000 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: huawei-sun2000 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + advanced: | + type: template + template: huawei-sun2000 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + storageunit: 1 # optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: huawei-sun2000 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + advanced: | + type: template + template: huawei-sun2000 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Zeitüberschreitung, optional + storageunit: 1 # optional + maxchargepower: 10000 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + capacity: 50 # Akkukapazität (kWh), optional + forceaccharging: false # Wechselrichterkaskade, AC-Laden bleibt aktiv zum Laden des Speichers aus anderen AC Quellen für Wechselrichterkaskaden. Verhindert Stand-by. (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 15s + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 10000 + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: forceaccharging + example: + default: false + choice: [] + unit: + description: Wechselrichterkaskade + help: AC-Laden bleibt aktiv zum Laden des Speichers aus anderen AC Quellen für Wechselrichterkaskaden. Verhindert Stand-by. + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/huawei-sun2000_0.yaml b/templates/release/de/meter/huawei-sun2000_0.yaml deleted file mode 100644 index 03b2b44639..0000000000 --- a/templates/release/de/meter/huawei-sun2000_0.yaml +++ /dev/null @@ -1,164 +0,0 @@ -product: - brand: Huawei - description: SUN2000 -capabilities: ["battery-control"] -description: | - Grid und Batterie erfordern den PowerSensor. - "Modbus/TCP" erfordert Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. - Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 - -render: - - usage: grid - default: | - type: template - template: huawei-sun2000 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - advanced: | - type: template - template: huawei-sun2000 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: huawei-sun2000 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - advanced: | - type: template - template: huawei-sun2000 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: huawei-sun2000 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - advanced: | - type: template - template: huawei-sun2000 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional - maxchargepower: 10000 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - capacity: 50 # Akkukapazität (kWh), optional - forceaccharging: false # Wechselrichterkaskade, AC-Laden bleibt aktiv zum Laden des Speichers aus anderen AC Quellen für Wechselrichterkaskaden. Verhindert Stand-by. (optional) diff --git a/templates/release/de/meter/iammeter-wem3080.yaml b/templates/release/de/meter/iammeter-wem3080.yaml new file mode 100644 index 0000000000..5c568947dd --- /dev/null +++ b/templates/release/de/meter/iammeter-wem3080.yaml @@ -0,0 +1,38 @@ +template: iammeter +product: + identifier: iammeter-wem3080 + brand: IAMMETER + description: WEM3080 +description: | + Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). + Siehe https://www.iammeter.com/newsshow/net-energy-metering + +render: + - usage: grid + default: | + type: template + template: iammeter + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: iammeter + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: charge + default: | + type: template + template: iammeter + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml b/templates/release/de/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml new file mode 100644 index 0000000000..a04c2db338 --- /dev/null +++ b/templates/release/de/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml @@ -0,0 +1,38 @@ +template: iammeter +product: + identifier: iammeter-wem3080t-wem3046t-wem3050t + brand: IAMMETER + description: WEM3080T/WEM3046T/WEM3050T +description: | + Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). + Siehe https://www.iammeter.com/newsshow/net-energy-metering + +render: + - usage: grid + default: | + type: template + template: iammeter + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: iammeter + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: charge + default: | + type: template + template: iammeter + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/iammeter_0.yaml b/templates/release/de/meter/iammeter_0.yaml deleted file mode 100644 index c2963ace29..0000000000 --- a/templates/release/de/meter/iammeter_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: IAMMETER - description: WEM3080T/WEM3046T/WEM3050T -description: | - Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). - Siehe https://www.iammeter.com/newsshow/net-energy-metering - -render: - - usage: grid - default: | - type: template - template: iammeter - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: iammeter - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: charge - default: | - type: template - template: iammeter - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/iammeter_1.yaml b/templates/release/de/meter/iammeter_1.yaml deleted file mode 100644 index 2db41ae12e..0000000000 --- a/templates/release/de/meter/iammeter_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: IAMMETER - description: WEM3080 -description: | - Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). - Siehe https://www.iammeter.com/newsshow/net-energy-metering - -render: - - usage: grid - default: | - type: template - template: iammeter - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: iammeter - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: charge - default: | - type: template - template: iammeter - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/igen-tech-solarman-logger.yaml b/templates/release/de/meter/igen-tech-solarman-logger.yaml new file mode 100644 index 0000000000..a0a006e1cf --- /dev/null +++ b/templates/release/de/meter/igen-tech-solarman-logger.yaml @@ -0,0 +1,42 @@ +template: solarman +product: + identifier: igen-tech-solarman-logger + brand: IGEN Tech + description: Solarman Logger +render: + - usage: pv + default: | + type: template + template: solarman + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: admin # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: admin # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: admin + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: admin + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/inepro-pro380-mod.yaml b/templates/release/de/meter/inepro-pro380-mod.yaml new file mode 100644 index 0000000000..66c63aefae --- /dev/null +++ b/templates/release/de/meter/inepro-pro380-mod.yaml @@ -0,0 +1,61 @@ +template: inepro +product: + identifier: inepro-pro380-mod + brand: inepro + description: PRO380-MOD +render: + - usage: grid + default: | + type: template + template: inepro + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: inepro + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/inepro_0.yaml b/templates/release/de/meter/inepro_0.yaml deleted file mode 100644 index a72a94dd1b..0000000000 --- a/templates/release/de/meter/inepro_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: inepro - description: PRO380-MOD -render: - - usage: grid - default: | - type: template - template: inepro - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: inepro - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/iometer.yaml b/templates/release/de/meter/iometer.yaml new file mode 100644 index 0000000000..4096e58497 --- /dev/null +++ b/templates/release/de/meter/iometer.yaml @@ -0,0 +1,21 @@ +template: iometer +product: + identifier: iometer + brand: IOmeter +render: + - usage: grid + default: | + type: template + template: iometer + usage: grid + host: 192.0.2.2 # IP deines IOmeter +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP deines IOmeter + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/iometer_0.yaml b/templates/release/de/meter/iometer_0.yaml deleted file mode 100644 index 9dba550860..0000000000 --- a/templates/release/de/meter/iometer_0.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: IOmeter -render: - - usage: grid - default: | - type: template - template: iometer - usage: grid - host: 192.0.2.2 # IP deines IOmeter diff --git a/templates/release/de/meter/janitza-b-series.yaml b/templates/release/de/meter/janitza-b-series.yaml new file mode 100644 index 0000000000..471cd33ce3 --- /dev/null +++ b/templates/release/de/meter/janitza-b-series.yaml @@ -0,0 +1,74 @@ +template: janitza +product: + identifier: janitza-b-series + brand: Janitza + description: B series +render: + - usage: grid + default: | + type: template + template: janitza + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: janitza + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/janitza-umg-series.yaml b/templates/release/de/meter/janitza-umg-series.yaml new file mode 100644 index 0000000000..c6c3c47f25 --- /dev/null +++ b/templates/release/de/meter/janitza-umg-series.yaml @@ -0,0 +1,74 @@ +template: janitza +product: + identifier: janitza-umg-series + brand: Janitza + description: UMG series +render: + - usage: grid + default: | + type: template + template: janitza + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: janitza + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/janitza_0.yaml b/templates/release/de/meter/janitza_0.yaml deleted file mode 100644 index 1c8d9b69ff..0000000000 --- a/templates/release/de/meter/janitza_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Janitza - description: B series, UMG series -render: - - usage: grid - default: | - type: template - template: janitza - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: janitza - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/keba-kecontact-e10.yaml b/templates/release/de/meter/keba-kecontact-e10.yaml new file mode 100644 index 0000000000..432af7879f --- /dev/null +++ b/templates/release/de/meter/keba-kecontact-e10.yaml @@ -0,0 +1,33 @@ +template: keba-kecontact +product: + identifier: keba-kecontact-e10 + brand: KEBA + description: KeContact E10 +render: + - usage: grid + default: | + type: template + template: keba-kecontact + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/keba-kecontact_0.yaml b/templates/release/de/meter/keba-kecontact_0.yaml deleted file mode 100644 index 8ac8658939..0000000000 --- a/templates/release/de/meter/keba-kecontact_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: KEBA - description: KeContact E10 -render: - - usage: grid - default: | - type: template - template: keba-kecontact - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml b/templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml new file mode 100644 index 0000000000..fdaed4b63f --- /dev/null +++ b/templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: kostal-energy-meter-c-kem-c + brand: Kostal + description: Energy Meter C (KEM-C) +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml b/templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml new file mode 100644 index 0000000000..a4f8d0cb8f --- /dev/null +++ b/templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: kostal-energy-meter-p-kem-p + brand: Kostal + description: Energy Meter P (KEM-P) +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/kostal-ksem-inverter_0.yaml b/templates/release/de/meter/kostal-ksem-inverter_0.yaml deleted file mode 100644 index 2481f1a06f..0000000000 --- a/templates/release/de/meter/kostal-ksem-inverter_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kostal - description: Smart Energy Meter (über den Wechselrichter) -description: | - Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorposition 1 (Haushaltsverbrauch) wird nicht unterstützt. -render: - - usage: grid - default: | - type: template - template: kostal-ksem-inverter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port diff --git a/templates/release/de/meter/kostal-ksem_0.yaml b/templates/release/de/meter/kostal-ksem_0.yaml deleted file mode 100644 index a2d146cf9c..0000000000 --- a/templates/release/de/meter/kostal-ksem_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Kostal - description: Smart Energy Meter -render: - - usage: grid - default: | - type: template - template: kostal-ksem - usage: grid - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/kostal-piko-ba.yaml b/templates/release/de/meter/kostal-piko-ba.yaml new file mode 100644 index 0000000000..156f5062df --- /dev/null +++ b/templates/release/de/meter/kostal-piko-ba.yaml @@ -0,0 +1,28 @@ +template: kostal-piko-pv +product: + identifier: kostal-piko-ba + brand: Kostal + description: Piko BA +render: + - usage: grid + default: | + type: template + template: kostal-piko-pv + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: kostal-piko-pv + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/kostal-piko-hybrid.yaml b/templates/release/de/meter/kostal-piko-hybrid.yaml new file mode 100644 index 0000000000..eceeb338fe --- /dev/null +++ b/templates/release/de/meter/kostal-piko-hybrid.yaml @@ -0,0 +1,59 @@ +template: kostal-piko-hybrid +product: + identifier: kostal-piko-hybrid + brand: Kostal + description: Piko Hybrid +render: + - usage: grid + default: | + type: template + template: kostal-piko-hybrid + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: kostal-piko-hybrid + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: kostal-piko-hybrid + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: kostal-piko-hybrid + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: battery + default: | + type: template + template: kostal-piko-hybrid + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: kostal-piko-hybrid + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/kostal-piko-hybrid_0.yaml b/templates/release/de/meter/kostal-piko-hybrid_0.yaml deleted file mode 100644 index d8f1aba733..0000000000 --- a/templates/release/de/meter/kostal-piko-hybrid_0.yaml +++ /dev/null @@ -1,38 +0,0 @@ -product: - brand: Kostal - description: Piko Hybrid -render: - - usage: grid - default: | - type: template - template: kostal-piko-hybrid - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: kostal-piko-hybrid - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: kostal-piko-hybrid - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: kostal-piko-hybrid - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: battery - default: | - type: template - template: kostal-piko-hybrid - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: kostal-piko-hybrid - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/kostal-piko-legacy.yaml b/templates/release/de/meter/kostal-piko-legacy.yaml new file mode 100644 index 0000000000..daa9f35868 --- /dev/null +++ b/templates/release/de/meter/kostal-piko-legacy.yaml @@ -0,0 +1,42 @@ +template: kostal-piko-legacy +product: + identifier: kostal-piko-legacy + brand: Kostal + description: Piko (legacy) +render: + - usage: pv + default: | + type: template + template: kostal-piko-legacy + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/kostal-piko-legacy_0.yaml b/templates/release/de/meter/kostal-piko-legacy_0.yaml deleted file mode 100644 index 065340d999..0000000000 --- a/templates/release/de/meter/kostal-piko-legacy_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Kostal - description: Piko (legacy) -render: - - usage: pv - default: | - type: template - template: kostal-piko-legacy - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen diff --git a/templates/release/de/meter/kostal-piko-mp-plus.yaml b/templates/release/de/meter/kostal-piko-mp-plus.yaml new file mode 100644 index 0000000000..f6509783c5 --- /dev/null +++ b/templates/release/de/meter/kostal-piko-mp-plus.yaml @@ -0,0 +1,22 @@ +template: kostal-piko-mp-plus +product: + identifier: kostal-piko-mp-plus + brand: Kostal + description: Piko MP Plus +render: + - usage: pv + default: | + type: template + template: kostal-piko-mp-plus + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/kostal-piko-mp-plus_0.yaml b/templates/release/de/meter/kostal-piko-mp-plus_0.yaml deleted file mode 100644 index 5162ec873e..0000000000 --- a/templates/release/de/meter/kostal-piko-mp-plus_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Kostal - description: Piko MP Plus -render: - - usage: pv - default: | - type: template - template: kostal-piko-mp-plus - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/kostal-piko-mp-plus_1.yaml b/templates/release/de/meter/kostal-piko-mp-plus_1.yaml deleted file mode 100644 index 304a091b25..0000000000 --- a/templates/release/de/meter/kostal-piko-mp-plus_1.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Steca - description: coolcept fleX -render: - - usage: pv - default: | - type: template - template: kostal-piko-mp-plus - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/kostal-piko-pv_0.yaml b/templates/release/de/meter/kostal-piko-pv_0.yaml deleted file mode 100644 index f0caf8f8bc..0000000000 --- a/templates/release/de/meter/kostal-piko-pv_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Kostal - description: Piko, Piko BA -render: - - usage: grid - default: | - type: template - template: kostal-piko-pv - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: kostal-piko-pv - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/kostal-piko.yaml b/templates/release/de/meter/kostal-piko.yaml new file mode 100644 index 0000000000..bf74ed89b4 --- /dev/null +++ b/templates/release/de/meter/kostal-piko.yaml @@ -0,0 +1,28 @@ +template: kostal-piko-pv +product: + identifier: kostal-piko + brand: Kostal + description: Piko +render: + - usage: grid + default: | + type: template + template: kostal-piko-pv + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: kostal-piko-pv + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/kostal-plenticore-gen2_0.yaml b/templates/release/de/meter/kostal-plenticore-gen2_0.yaml deleted file mode 100644 index 18b9a1eb93..0000000000 --- a/templates/release/de/meter/kostal-plenticore-gen2_0.yaml +++ /dev/null @@ -1,59 +0,0 @@ -product: - brand: Kostal - description: Plenticore Hybrid, inkl. Netzladung der Hausbatterie -capabilities: ["battery-control"] -description: | - Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. **_Ist grundsätzlich anwendbar für verschiedene Wechselrichter Generationen (G1/G2/G3)._** - **Das Netzladen der Batterie steht mit dieser Vorlage zur Verfügung, ist aktuell jedoch inkompatibel mit wenigen älteren Wechselrichtern - _sorgfältig testen_!** - _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ - -render: - - usage: pv - default: | - type: template - template: kostal-plenticore-gen2 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore-gen2 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: kostal-plenticore-gen2 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore-gen2 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) - capacity: 50 # Akkukapazität (kWh), optional - maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) - watchdog: 60s # optional diff --git a/templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml b/templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml new file mode 100644 index 0000000000..06a8a61eba --- /dev/null +++ b/templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml @@ -0,0 +1,122 @@ +template: kostal-plenticore-gen2 +product: + identifier: kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery + brand: Kostal + description: Plenticore Hybrid, inkl. Netzladung der Hausbatterie +capabilities: ["battery-control"] +description: | + Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. **_Ist grundsätzlich anwendbar für verschiedene Wechselrichter Generationen (G1/G2/G3)._** + **Das Netzladen der Batterie steht mit dieser Vorlage zur Verfügung, ist aktuell jedoch inkompatibel mit wenigen älteren Wechselrichtern - _sorgfältig testen_!** + _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + +render: + - usage: pv + default: | + type: template + template: kostal-plenticore-gen2 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore-gen2 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: kostal-plenticore-gen2 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore-gen2 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) + capacity: 50 # Akkukapazität (kWh), optional + maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: endianness + example: + default: little + choice: ['little', 'big'] + unit: + description: Byte-Reihenfolge (Little/Big) + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/kostal-plenticore-hybrid.yaml b/templates/release/de/meter/kostal-plenticore-hybrid.yaml new file mode 100644 index 0000000000..2eca97fc75 --- /dev/null +++ b/templates/release/de/meter/kostal-plenticore-hybrid.yaml @@ -0,0 +1,133 @@ +template: kostal-plenticore +product: + identifier: kostal-plenticore-hybrid + brand: Kostal + description: Plenticore Hybrid +capabilities: ["battery-control"] +description: | + Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. + **Das Netzladen der Batterie steht nicht zur Verfügung!** _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + +render: + - usage: pv + default: | + type: template + template: kostal-plenticore + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: kostal-plenticore + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: endianness + example: + default: little + choice: ['little', 'big'] + unit: + description: Byte-Reihenfolge (Little/Big) + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/kostal-plenticore_0.yaml b/templates/release/de/meter/kostal-plenticore_0.yaml deleted file mode 100644 index 35eaa37f0d..0000000000 --- a/templates/release/de/meter/kostal-plenticore_0.yaml +++ /dev/null @@ -1,61 +0,0 @@ -product: - brand: Kostal - description: Plenticore Hybrid -capabilities: ["battery-control"] -description: | - Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. - **Das Netzladen der Batterie steht nicht zur Verfügung!** _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ - -render: - - usage: pv - default: | - type: template - template: kostal-plenticore - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: kostal-plenticore - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional diff --git a/templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml b/templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml new file mode 100644 index 0000000000..445ad11caa --- /dev/null +++ b/templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml @@ -0,0 +1,35 @@ +template: kostal-ksem-inverter +product: + identifier: kostal-smart-energy-meter-via-inverter + brand: Kostal + description: Smart Energy Meter (über den Wechselrichter) +description: | + Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorposition 1 (Haushaltsverbrauch) wird nicht unterstützt. +render: + - usage: grid + default: | + type: template + template: kostal-ksem-inverter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/kostal-smart-energy-meter.yaml b/templates/release/de/meter/kostal-smart-energy-meter.yaml new file mode 100644 index 0000000000..63cad3375d --- /dev/null +++ b/templates/release/de/meter/kostal-smart-energy-meter.yaml @@ -0,0 +1,33 @@ +template: kostal-ksem +product: + identifier: kostal-smart-energy-meter + brand: Kostal + description: Smart Energy Meter +render: + - usage: grid + default: | + type: template + template: kostal-ksem + usage: grid + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/lg-ess-home-15.yaml b/templates/release/de/meter/lg-ess-home-15.yaml new file mode 100644 index 0000000000..bdb9dc9f59 --- /dev/null +++ b/templates/release/de/meter/lg-ess-home-15.yaml @@ -0,0 +1,111 @@ +template: lg-ess-home-15 +product: + identifier: lg-ess-home-15 + brand: LG + description: ESS Home 15 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: lg-ess-home-15 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + advanced: | + type: template + template: lg-ess-home-15 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: lg-ess-home-15 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + advanced: | + type: template + template: lg-ess-home-15 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: battery + default: | + type: template + template: lg-ess-home-15 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + advanced: | + type: template + template: lg-ess-home-15 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. + advanced: false + optional: true + - name: registration + example: DE200... + default: + choice: [] + unit: + description: + help: Registriernummer des LG ESS HOME Wechselrichters. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/lg-ess-home-15_0.yaml b/templates/release/de/meter/lg-ess-home-15_0.yaml deleted file mode 100644 index a3f0893d30..0000000000 --- a/templates/release/de/meter/lg-ess-home-15_0.yaml +++ /dev/null @@ -1,54 +0,0 @@ -product: - brand: LG - description: ESS Home 15 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: lg-ess-home-15 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - advanced: | - type: template - template: lg-ess-home-15 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: lg-ess-home-15 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - advanced: | - type: template - template: lg-ess-home-15 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: battery - default: | - type: template - template: lg-ess-home-15 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - advanced: | - type: template - template: lg-ess-home-15 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/lg-ess-home-8-10.yaml b/templates/release/de/meter/lg-ess-home-8-10.yaml new file mode 100644 index 0000000000..de2cd7e286 --- /dev/null +++ b/templates/release/de/meter/lg-ess-home-8-10.yaml @@ -0,0 +1,114 @@ +template: lg-ess-home-8-10 +product: + identifier: lg-ess-home-8-10 + brand: LG + description: ESS Home 8/10 +capabilities: ["battery-control"] +description: | + Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich 10.05.7433 / R2155 benötigt + +render: + - usage: grid + default: | + type: template + template: lg-ess-home-8-10 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + advanced: | + type: template + template: lg-ess-home-8-10 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: lg-ess-home-8-10 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + advanced: | + type: template + template: lg-ess-home-8-10 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: battery + default: | + type: template + template: lg-ess-home-8-10 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + advanced: | + type: template + template: lg-ess-home-8-10 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) + registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. + advanced: false + optional: true + - name: registration + example: DE200... + default: + choice: [] + unit: + description: + help: Registriernummer des LG ESS HOME Wechselrichters. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/lg-ess-home-8-10_0.yaml b/templates/release/de/meter/lg-ess-home-8-10_0.yaml deleted file mode 100644 index 56efaf74af..0000000000 --- a/templates/release/de/meter/lg-ess-home-8-10_0.yaml +++ /dev/null @@ -1,57 +0,0 @@ -product: - brand: LG - description: ESS Home 8/10 -capabilities: ["battery-control"] -description: | - Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich 10.05.7433 / R2155 benötigt - -render: - - usage: grid - default: | - type: template - template: lg-ess-home-8-10 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - advanced: | - type: template - template: lg-ess-home-8-10 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: lg-ess-home-8-10 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - advanced: | - type: template - template: lg-ess-home-8-10 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: battery - default: | - type: template - template: lg-ess-home-8-10 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - advanced: | - type: template - template: lg-ess-home-8-10 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/loxone-miniserver.yaml b/templates/release/de/meter/loxone-miniserver.yaml new file mode 100644 index 0000000000..22b2ac5fa8 --- /dev/null +++ b/templates/release/de/meter/loxone-miniserver.yaml @@ -0,0 +1,92 @@ +template: loxone +product: + identifier: loxone-miniserver + brand: Loxone + description: Miniserver +render: + - usage: grid + default: | + type: template + template: loxone + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config + socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) + - usage: pv + default: | + type: template + template: loxone + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config + socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) + - usage: battery + default: | + type: template + template: loxone + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config + socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) + - usage: charge + default: | + type: template + template: loxone + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config + socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: meterblock + example: + default: + choice: [] + unit: + description: Zählerbaustein + help: Bezeichnung aus Loxone Config + advanced: false + optional: false + - name: socblock + example: + default: + choice: [] + unit: + description: Bausteinbezeichnung für Ladezustand + help: Bezeichnung aus Loxone Config, nur für Batterie + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/loxone_0.yaml b/templates/release/de/meter/loxone_0.yaml deleted file mode 100644 index 7e5c8130c9..0000000000 --- a/templates/release/de/meter/loxone_0.yaml +++ /dev/null @@ -1,44 +0,0 @@ -product: - brand: Loxone - description: Miniserver -render: - - usage: grid - default: | - type: template - template: loxone - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config - socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) - - usage: pv - default: | - type: template - template: loxone - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config - socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) - - usage: battery - default: | - type: template - template: loxone - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config - socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) - - usage: charge - default: | - type: template - template: loxone - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterblock: # Zählerbaustein, Bezeichnung aus Loxone Config - socblock: # Bausteinbezeichnung für Ladezustand, Bezeichnung aus Loxone Config, nur für Batterie (optional) diff --git a/templates/release/de/meter/m-tec-energy-butler-gen2.yaml b/templates/release/de/meter/m-tec-energy-butler-gen2.yaml new file mode 100644 index 0000000000..d4e337c9b1 --- /dev/null +++ b/templates/release/de/meter/m-tec-energy-butler-gen2.yaml @@ -0,0 +1,79 @@ +template: mtec-eb-gen2 +product: + identifier: m-tec-energy-butler-gen2 + brand: M-TEC + description: Energy Butler GEN2 +render: + - usage: grid + default: | + type: template + template: mtec-eb-gen2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: mtec-eb-gen2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: mtec-eb-gen2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/m-tec-energy-butler-gen3.yaml b/templates/release/de/meter/m-tec-energy-butler-gen3.yaml new file mode 100644 index 0000000000..fb70968588 --- /dev/null +++ b/templates/release/de/meter/m-tec-energy-butler-gen3.yaml @@ -0,0 +1,178 @@ +template: mtec-eb-gen3 +product: + identifier: m-tec-energy-butler-gen3 + brand: M-TEC + description: Energy Butler GEN3 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: mtec-eb-gen3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: mtec-eb-gen3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: mtec-eb-gen3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: mtec-eb-gen3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: mtec-eb-gen3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: mtec-eb-gen3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 255 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/marstek-venus-battery-storage.yaml b/templates/release/de/meter/marstek-venus-battery-storage.yaml new file mode 100644 index 0000000000..e1cc5d92a3 --- /dev/null +++ b/templates/release/de/meter/marstek-venus-battery-storage.yaml @@ -0,0 +1,112 @@ +template: marstek-venus +product: + identifier: marstek-venus-battery-storage + brand: Marstek + description: Venus Battery Storage +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: marstek-venus + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 5.12 # Akkukapazität (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) + advanced: | + type: template + template: marstek-venus + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 5.12 # Akkukapazität (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) + minsoc: 11 # Venus kann nur bis 11% entladen werden. (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 100 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxchargepower: 2500 # Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus. (W), Für erzwungenes Laden des Speichers. (optional) + work_mode_normal: 1 # Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung., optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: 5.12 + choice: [] + unit: kWh + description: Akkukapazität + help: Venus-E 5.12 kWh, Venus-C 2.56 kWh + advanced: false + optional: true + - name: minsoc + example: 25 + default: 11 + choice: [] + unit: '%' + description: Venus kann nur bis 11% entladen werden. + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 100 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxchargepower + example: + default: 2500 + choice: [] + unit: W + description: Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus. + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: work_mode_normal + example: + default: 1 + choice: [] + unit: + description: Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung. + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/marstek-venus_0.yaml b/templates/release/de/meter/marstek-venus_0.yaml deleted file mode 100644 index cc5205b398..0000000000 --- a/templates/release/de/meter/marstek-venus_0.yaml +++ /dev/null @@ -1,46 +0,0 @@ -product: - brand: Marstek - description: Venus Battery Storage -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: marstek-venus - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 5.12 # Akkukapazität (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - advanced: | - type: template - template: marstek-venus - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 5.12 # Akkukapazität (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - minsoc: 11 # Venus kann nur bis 11% entladen werden. (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 100 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxchargepower: 2500 # Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus. (W), Für erzwungenes Laden des Speichers. (optional) - work_mode_normal: 1 # Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung., optional diff --git a/templates/release/de/meter/mhendriks-p1-dongle.yaml b/templates/release/de/meter/mhendriks-p1-dongle.yaml new file mode 100644 index 0000000000..bce07c0e11 --- /dev/null +++ b/templates/release/de/meter/mhendriks-p1-dongle.yaml @@ -0,0 +1,37 @@ +template: slimmelezer +product: + identifier: mhendriks-p1-dongle + brand: mhendriks + description: P1 dongle +render: + - usage: grid + default: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: scale + example: 1 | 10 | 100 | 1000 + default: 1000 + choice: [] + unit: + description: Skalierungsfaktor + help: Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/mpm3pm_0.yaml b/templates/release/de/meter/mpm3pm_0.yaml deleted file mode 100644 index e3d65077f7..0000000000 --- a/templates/release/de/meter/mpm3pm_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Bernecker Engineering - description: MPM3PM -render: - - usage: grid - default: | - type: template - template: mpm3pm - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: mpm3pm - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/mtec-eb-gen2_0.yaml b/templates/release/de/meter/mtec-eb-gen2_0.yaml deleted file mode 100644 index de33af6124..0000000000 --- a/templates/release/de/meter/mtec-eb-gen2_0.yaml +++ /dev/null @@ -1,58 +0,0 @@ -product: - brand: M-TEC - description: Energy Butler GEN2 -render: - - usage: grid - default: | - type: template - template: mtec-eb-gen2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: mtec-eb-gen2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: mtec-eb-gen2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/mtec-eb-gen3_0.yaml b/templates/release/de/meter/mtec-eb-gen3_0.yaml deleted file mode 100644 index b047089240..0000000000 --- a/templates/release/de/meter/mtec-eb-gen3_0.yaml +++ /dev/null @@ -1,147 +0,0 @@ -product: - brand: M-TEC - description: Energy Butler GEN3 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: mtec-eb-gen3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: mtec-eb-gen3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: mtec-eb-gen3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: mtec-eb-gen3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: mtec-eb-gen3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: mtec-eb-gen3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/my-pv-ac-elwa-2.yaml b/templates/release/de/meter/my-pv-ac-elwa-2.yaml new file mode 100644 index 0000000000..5086d23734 --- /dev/null +++ b/templates/release/de/meter/my-pv-ac-elwa-2.yaml @@ -0,0 +1,22 @@ +template: ac-elwa-2 +product: + identifier: my-pv-ac-elwa-2 + brand: my-PV + description: AC ELWA 2 +render: + - usage: aux + default: | + type: template + template: ac-elwa-2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/my-pv-ac-elwa-e.yaml b/templates/release/de/meter/my-pv-ac-elwa-e.yaml new file mode 100644 index 0000000000..d980ca6a30 --- /dev/null +++ b/templates/release/de/meter/my-pv-ac-elwa-e.yaml @@ -0,0 +1,22 @@ +template: ac-elwa-e +product: + identifier: my-pv-ac-elwa-e + brand: my-PV + description: AC ELWA-E +render: + - usage: aux + default: | + type: template + template: ac-elwa-e + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/my-pv-ac-thor.yaml b/templates/release/de/meter/my-pv-ac-thor.yaml new file mode 100644 index 0000000000..2e37b072ab --- /dev/null +++ b/templates/release/de/meter/my-pv-ac-thor.yaml @@ -0,0 +1,22 @@ +template: thor +product: + identifier: my-pv-ac-thor + brand: my-PV + description: AC•THOR +render: + - usage: aux + default: | + type: template + template: thor + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/my-pv-wifi-meter.yaml b/templates/release/de/meter/my-pv-wifi-meter.yaml new file mode 100644 index 0000000000..01129aa7e8 --- /dev/null +++ b/templates/release/de/meter/my-pv-wifi-meter.yaml @@ -0,0 +1,33 @@ +template: mypv-wifi-meter +product: + identifier: my-pv-wifi-meter + brand: my-PV + description: WiFi Meter +render: + - usage: grid + default: | + type: template + template: mypv-wifi-meter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/mypv-wifi-meter_0.yaml b/templates/release/de/meter/mypv-wifi-meter_0.yaml deleted file mode 100644 index f8d60b48a0..0000000000 --- a/templates/release/de/meter/mypv-wifi-meter_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: my-PV - description: WiFi Meter -render: - - usage: grid - default: | - type: template - template: mypv-wifi-meter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/mystrom-switch.yaml b/templates/release/de/meter/mystrom-switch.yaml new file mode 100644 index 0000000000..4184598aed --- /dev/null +++ b/templates/release/de/meter/mystrom-switch.yaml @@ -0,0 +1,29 @@ +template: mystrom +product: + identifier: mystrom-switch + brand: myStrom + description: Switch + group: Schaltbare Steckdosen +render: + - usage: pv + default: | + type: template + template: mystrom + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: charge + default: | + type: template + template: mystrom + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/mystrom_0.yaml b/templates/release/de/meter/mystrom_0.yaml deleted file mode 100644 index 4be2b4a636..0000000000 --- a/templates/release/de/meter/mystrom_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: myStrom - description: Switch - group: Schaltbare Steckdosen -render: - - usage: pv - default: | - type: template - template: mystrom - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: charge - default: | - type: template - template: mystrom - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/openems.yaml b/templates/release/de/meter/openems.yaml new file mode 100644 index 0000000000..ae8047f1ec --- /dev/null +++ b/templates/release/de/meter/openems.yaml @@ -0,0 +1,104 @@ +template: openems +product: + identifier: openems + brand: OpenEMS +capabilities: ["battery-control"] +description: | + Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. + +render: + - usage: grid + default: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: pv + default: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + battery: ess0 # steuerbare Batterie Komponente (optional) + watchdog: 60s # abgestimmt auf das API-Timeout (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: password + example: + default: user + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true + - name: battery + example: ess0 + default: + choice: [] + unit: + description: + help: steuerbare Batterie Komponente + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: abgestimmt auf das API-Timeout + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/openems_0.yaml b/templates/release/de/meter/openems_0.yaml deleted file mode 100644 index 63c4787d4e..0000000000 --- a/templates/release/de/meter/openems_0.yaml +++ /dev/null @@ -1,47 +0,0 @@ -product: - brand: OpenEMS -capabilities: ["battery-control"] -description: | - Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. - -render: - - usage: grid - default: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/openems_1.yaml b/templates/release/de/meter/openems_1.yaml deleted file mode 100644 index f37725bddf..0000000000 --- a/templates/release/de/meter/openems_1.yaml +++ /dev/null @@ -1,47 +0,0 @@ -product: - brand: FENECON -capabilities: ["battery-control"] -description: | - Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. - -render: - - usage: grid - default: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/orno-or-we-516.yaml b/templates/release/de/meter/orno-or-we-516.yaml new file mode 100644 index 0000000000..e5828f01eb --- /dev/null +++ b/templates/release/de/meter/orno-or-we-516.yaml @@ -0,0 +1,61 @@ +template: orno +product: + identifier: orno-or-we-516 + brand: ORNO + description: OR-WE-516 +render: + - usage: grid + default: | + type: template + template: orno + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: orno + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/orno-or-we-517.yaml b/templates/release/de/meter/orno-or-we-517.yaml new file mode 100644 index 0000000000..84efc46ba1 --- /dev/null +++ b/templates/release/de/meter/orno-or-we-517.yaml @@ -0,0 +1,61 @@ +template: orno +product: + identifier: orno-or-we-517 + brand: ORNO + description: OR-WE-517 +render: + - usage: grid + default: | + type: template + template: orno + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: orno + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/orno_0.yaml b/templates/release/de/meter/orno_0.yaml deleted file mode 100644 index 775ad5c2db..0000000000 --- a/templates/release/de/meter/orno_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Orno - description: OR-WE-516, OR-WE-517 -render: - - usage: grid - default: | - type: template - template: orno - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: orno - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/p1monitor-p1-monitor.yaml b/templates/release/de/meter/p1monitor-p1-monitor.yaml new file mode 100644 index 0000000000..4239758db3 --- /dev/null +++ b/templates/release/de/meter/p1monitor-p1-monitor.yaml @@ -0,0 +1,22 @@ +template: p1monitor +product: + identifier: p1monitor-p1-monitor + brand: P1Monitor + description: P1 Monitor +render: + - usage: grid + default: | + type: template + template: p1monitor + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/p1monitor_0.yaml b/templates/release/de/meter/p1monitor_0.yaml deleted file mode 100644 index 75df84cd05..0000000000 --- a/templates/release/de/meter/p1monitor_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: P1Monitor - description: P1 Monitor -render: - - usage: grid - default: | - type: template - template: p1monitor - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/plexlog.yaml b/templates/release/de/meter/plexlog.yaml new file mode 100644 index 0000000000..3ff2cfe6d7 --- /dev/null +++ b/templates/release/de/meter/plexlog.yaml @@ -0,0 +1,97 @@ +template: plexlog +product: + identifier: plexlog + description: Plexlog +description: | + Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `interval` nicht kleiner als 30 Sekunden gewählt werden. + +render: + - usage: grid + default: | + type: template + template: plexlog + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + advanced: | + type: template + template: plexlog + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + - usage: pv + default: | + type: template + template: plexlog + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + advanced: | + type: template + template: plexlog + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + - usage: battery + default: | + type: template + template: plexlog + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + advanced: | + type: template + template: plexlog + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 503 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/plexlog_0.yaml b/templates/release/de/meter/plexlog_0.yaml deleted file mode 100644 index 99d762b140..0000000000 --- a/templates/release/de/meter/plexlog_0.yaml +++ /dev/null @@ -1,70 +0,0 @@ -product: - description: Plexlog -description: | - Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `interval` nicht kleiner als 30 Sekunden gewählt werden. - -render: - - usage: grid - default: | - type: template - template: plexlog - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - advanced: | - type: template - template: plexlog - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - - usage: pv - default: | - type: template - template: plexlog - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - advanced: | - type: template - template: plexlog - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - - usage: battery - default: | - type: template - template: plexlog - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - advanced: | - type: template - template: plexlog - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/powerdog.yaml b/templates/release/de/meter/powerdog.yaml new file mode 100644 index 0000000000..5ec0e5a171 --- /dev/null +++ b/templates/release/de/meter/powerdog.yaml @@ -0,0 +1,43 @@ +template: powerdog +product: + identifier: powerdog + description: Powerdog +render: + - usage: grid + default: | + type: template + template: powerdog + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: powerdog + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/powerdog_0.yaml b/templates/release/de/meter/powerdog_0.yaml deleted file mode 100644 index e8ffec3dde..0000000000 --- a/templates/release/de/meter/powerdog_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: Powerdog -render: - - usage: grid - default: | - type: template - template: powerdog - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: powerdog - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/powerfox-poweropti.yaml b/templates/release/de/meter/powerfox-poweropti.yaml new file mode 100644 index 0000000000..e22397a646 --- /dev/null +++ b/templates/release/de/meter/powerfox-poweropti.yaml @@ -0,0 +1,62 @@ +template: powerfox-poweropti +product: + identifier: powerfox-poweropti + brand: Powerfox + description: Poweropti +render: + - usage: grid + default: | + type: template + template: powerfox-poweropti + usage: grid + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: | + type: template + template: powerfox-poweropti + usage: grid + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + id: main # Id im Falle mehrerer PowerOpti + - usage: pv + default: | + type: template + template: powerfox-poweropti + usage: pv + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: | + type: template + template: powerfox-poweropti + usage: pv + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + id: main # Id im Falle mehrerer PowerOpti +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: id + example: + default: main + choice: [] + unit: + description: + help: Id im Falle mehrerer PowerOpti + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/powerfox-poweropti_0.yaml b/templates/release/de/meter/powerfox-poweropti_0.yaml deleted file mode 100644 index 9b6536050a..0000000000 --- a/templates/release/de/meter/powerfox-poweropti_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Powerfox - description: Poweropti -render: - - usage: grid - default: | - type: template - template: powerfox-poweropti - usage: grid - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - advanced: | - type: template - template: powerfox-poweropti - usage: grid - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti - - usage: pv - default: | - type: template - template: powerfox-poweropti - usage: pv - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - advanced: | - type: template - template: powerfox-poweropti - usage: pv - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti diff --git a/templates/release/de/meter/qcells-hybrid-cloud_0.yaml b/templates/release/de/meter/qcells-hybrid-cloud_0.yaml deleted file mode 100644 index e3788f5c37..0000000000 --- a/templates/release/de/meter/qcells-hybrid-cloud_0.yaml +++ /dev/null @@ -1,49 +0,0 @@ -product: - brand: QCells - description: Hybrid-Wechselrichter (Cloud) -description: | - Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. - - **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. - -render: - - usage: grid - default: | - type: template - template: qcells-hybrid-cloud - usage: grid - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. - serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. - advanced: | - type: template - template: qcells-hybrid-cloud - usage: grid - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. - serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. - - usage: pv - default: | - type: template - template: qcells-hybrid-cloud - usage: pv - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. - serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. - advanced: | - type: template - template: qcells-hybrid-cloud - usage: pv - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. - serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. - - usage: battery - default: | - type: template - template: qcells-hybrid-cloud - usage: battery - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. - serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. - advanced: | - type: template - template: qcells-hybrid-cloud - usage: battery - tokenid: # QCellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. - serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/qcells-hybrid-inverter-cloud.yaml b/templates/release/de/meter/qcells-hybrid-inverter-cloud.yaml new file mode 100644 index 0000000000..8d0d1fecdb --- /dev/null +++ b/templates/release/de/meter/qcells-hybrid-inverter-cloud.yaml @@ -0,0 +1,79 @@ +template: qcells-hybrid-cloud +product: + identifier: qcells-hybrid-inverter-cloud + brand: Qcells + description: Hybrid-Wechselrichter (Cloud) +description: | + Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. + + **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. + +render: + - usage: grid + default: | + type: template + template: qcells-hybrid-cloud + usage: grid + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. + advanced: | + type: template + template: qcells-hybrid-cloud + usage: grid + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. + - usage: pv + default: | + type: template + template: qcells-hybrid-cloud + usage: pv + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. + advanced: | + type: template + template: qcells-hybrid-cloud + usage: pv + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. + - usage: battery + default: | + type: template + template: qcells-hybrid-cloud + usage: battery + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. + advanced: | + type: template + template: qcells-hybrid-cloud + usage: battery + tokenid: # QcellsCloud TokenID, Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + serial: # Seriennummer, Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: tokenid + example: + default: + choice: [] + unit: + description: QcellsCloud TokenID + help: Von https://qhome-ess-g3.q-cells.eu/#/api/ den Wert von "ObtaintokenID" hier eintragen. + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Seriennummer + help: Von https://qhome-ess-g3.q-cells.eu/blue/#/inverter die Registriernummer hier eintragen. + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml b/templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml new file mode 100644 index 0000000000..e4a1101455 --- /dev/null +++ b/templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml @@ -0,0 +1,225 @@ +template: solax +product: + identifier: qcells-q-home-ess-hyb-g3 + brand: Qcells + description: Q.HOME ESS HYB-G3 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + advanced: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + advanced: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + storageunit: 1 # optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + advanced: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + storageunit: 1 # optional + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. + advanced: true + optional: true +modbus: + baudrate: 19200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/rct-power.yaml b/templates/release/de/meter/rct-power.yaml new file mode 100644 index 0000000000..ec64bcf2e4 --- /dev/null +++ b/templates/release/de/meter/rct-power.yaml @@ -0,0 +1,118 @@ +template: rct-power +product: + identifier: rct-power + brand: RCT + description: Power +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: rct-power + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: rct-power + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) + - usage: pv + default: | + type: template + template: rct-power + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: rct-power + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) + - usage: battery + default: | + type: template + template: rct-power + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: rct-power + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 7 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 97 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: cache + example: 5m + default: 30s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: externalpower + example: + default: + choice: [] + unit: + description: Externe Leistung + help: Externe Leistung aller an S0 angeschlossenen Geräte abfragen + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/rct-power_0.yaml b/templates/release/de/meter/rct-power_0.yaml deleted file mode 100644 index d485fdb984..0000000000 --- a/templates/release/de/meter/rct-power_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: RCT - description: Power -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: rct-power - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: rct-power - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) - - usage: pv - default: | - type: template - template: rct-power - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: rct-power - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) - - usage: battery - default: | - type: template - template: rct-power - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: rct-power - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) diff --git a/templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml b/templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml new file mode 100644 index 0000000000..7a300b29b2 --- /dev/null +++ b/templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml @@ -0,0 +1,61 @@ +template: sbc-axx3 +product: + identifier: saia-burgess-controls-sbc-ale3 + brand: Saia-Burgess Controls (SBC) + description: ALE3 +render: + - usage: grid + default: | + type: template + template: sbc-axx3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: sbc-axx3 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml b/templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml new file mode 100644 index 0000000000..5d50d6befe --- /dev/null +++ b/templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml @@ -0,0 +1,61 @@ +template: sbc-axx3 +product: + identifier: saia-burgess-controls-sbc-awd3 + brand: Saia-Burgess Controls (SBC) + description: AWD3 +render: + - usage: grid + default: | + type: template + template: sbc-axx3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: sbc-axx3 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml b/templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml new file mode 100644 index 0000000000..54c49a08c9 --- /dev/null +++ b/templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml @@ -0,0 +1,110 @@ +template: saj-h1 +product: + identifier: saj-h1-series-hybrid-solar-inverter + brand: SAJ + description: H1 Series Hybrid Solar Inverter +render: + - usage: grid + default: | + type: template + template: saj-h1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Zeitüberschreitung, optional + advanced: | + type: template + template: saj-h1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Zeitüberschreitung, optional + - usage: pv + default: | + type: template + template: saj-h1 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Zeitüberschreitung, optional + advanced: | + type: template + template: saj-h1 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Zeitüberschreitung, optional + - usage: battery + default: | + type: template + template: saj-h1 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Zeitüberschreitung, optional + advanced: | + type: template + template: saj-h1 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Zeitüberschreitung, optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 5s + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/saj-h1_0.yaml b/templates/release/de/meter/saj-h1_0.yaml deleted file mode 100644 index db5c0070ce..0000000000 --- a/templates/release/de/meter/saj-h1_0.yaml +++ /dev/null @@ -1,74 +0,0 @@ -product: - brand: SAJ - description: H1 Series Hybrid Solar Inverter -render: - - usage: grid - default: | - type: template - template: saj-h1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Zeitüberschreitung, optional - advanced: | - type: template - template: saj-h1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Zeitüberschreitung, optional - - usage: pv - default: | - type: template - template: saj-h1 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Zeitüberschreitung, optional - advanced: | - type: template - template: saj-h1 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Zeitüberschreitung, optional - - usage: battery - default: | - type: template - template: saj-h1 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Zeitüberschreitung, optional - advanced: | - type: template - template: saj-h1 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Zeitüberschreitung, optional - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml b/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml new file mode 100644 index 0000000000..8195e1293d --- /dev/null +++ b/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml @@ -0,0 +1,211 @@ +template: saj-h2 +product: + identifier: saj-h2-series-hybrid-solar-inverter + brand: SAJ + description: H2 Series Hybrid Solar Inverter +render: + - usage: grid + default: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: battery + default: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 2 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 2 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/saj-h2_0.yaml b/templates/release/de/meter/saj-h2_0.yaml deleted file mode 100644 index 048623b02b..0000000000 --- a/templates/release/de/meter/saj-h2_0.yaml +++ /dev/null @@ -1,153 +0,0 @@ -product: - brand: SAJ - description: H2 Series Hybrid Solar Inverter -render: - - usage: grid - default: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: battery - default: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 2 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/saj-h2_1.yaml b/templates/release/de/meter/saj-h2_1.yaml deleted file mode 100644 index cc4c69e04f..0000000000 --- a/templates/release/de/meter/saj-h2_1.yaml +++ /dev/null @@ -1,153 +0,0 @@ -product: - brand: Ampere - description: Ampere.StoragePro -render: - - usage: grid - default: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: battery - default: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 2 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/saj-r5-series-solar-inverter.yaml b/templates/release/de/meter/saj-r5-series-solar-inverter.yaml new file mode 100644 index 0000000000..7ebc2899e9 --- /dev/null +++ b/templates/release/de/meter/saj-r5-series-solar-inverter.yaml @@ -0,0 +1,43 @@ +template: saj-r5 +product: + identifier: saj-r5-series-solar-inverter + brand: SAJ + description: R5 Series Solar Inverter +render: + - usage: pv + default: | + type: template + template: saj-r5 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/saj-r5_0.yaml b/templates/release/de/meter/saj-r5_0.yaml deleted file mode 100644 index dcf6d62b72..0000000000 --- a/templates/release/de/meter/saj-r5_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: SAJ - description: R5 Series Solar Inverter -render: - - usage: pv - default: | - type: template - template: saj-r5 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sax-homespeicher.yaml b/templates/release/de/meter/sax-homespeicher.yaml new file mode 100644 index 0000000000..b81b514f91 --- /dev/null +++ b/templates/release/de/meter/sax-homespeicher.yaml @@ -0,0 +1,44 @@ +template: sax +product: + identifier: sax-homespeicher + brand: SAX + description: Homespeicher +render: + - usage: grid + default: | + type: template + template: sax + usage: grid + + # Modbus TCP + modbus: tcpip + id: 64 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sax + usage: battery + + # Modbus TCP + modbus: tcpip + id: 64 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 64 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sax_0.yaml b/templates/release/de/meter/sax_0.yaml deleted file mode 100644 index 6b87e7b5ff..0000000000 --- a/templates/release/de/meter/sax_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: SAX - description: Homespeicher -render: - - usage: grid - default: | - type: template - template: sax - usage: grid - - # Modbus TCP - modbus: tcpip - id: 64 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sax - usage: battery - - # Modbus TCP - modbus: tcpip - id: 64 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sbc-axx3_0.yaml b/templates/release/de/meter/sbc-axx3_0.yaml deleted file mode 100644 index 0932eb8d3b..0000000000 --- a/templates/release/de/meter/sbc-axx3_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Saia-Burgess Controls - description: ALE3, AWD3 -render: - - usage: grid - default: | - type: template - template: sbc-axx3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: sbc-axx3 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml b/templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml new file mode 100644 index 0000000000..c57a0d25eb --- /dev/null +++ b/templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml @@ -0,0 +1,61 @@ +template: schneider-iem3000 +product: + identifier: schneider-electric-iem3xxx-modbus + brand: Schneider Electric + description: iEM3xxx Modbus +render: + - usage: grid + default: | + type: template + template: schneider-iem3000 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: schneider-iem3000 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/schneider-iem3000_0.yaml b/templates/release/de/meter/schneider-iem3000_0.yaml deleted file mode 100644 index c766da31fc..0000000000 --- a/templates/release/de/meter/schneider-iem3000_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Schneider Electric - description: iEM3xxx Modbus -render: - - usage: grid - default: | - type: template - template: schneider-iem3000 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: schneider-iem3000 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/senec-home.yaml b/templates/release/de/meter/senec-home.yaml new file mode 100644 index 0000000000..6dbe28eab0 --- /dev/null +++ b/templates/release/de/meter/senec-home.yaml @@ -0,0 +1,75 @@ +template: senec-home +product: + identifier: senec-home + brand: SENEC + description: .Home +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: senec-home + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + schema: https # [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + schema: https # [https, http] (optional) + - usage: pv + default: | + type: template + template: senec-home + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + schema: https # [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + schema: https # [https, http] (optional) + - usage: battery + default: | + type: template + template: senec-home + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + schema: https # [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + schema: https # [https, http] (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: schema + example: + default: https + choice: ['https', 'http'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/senec-home_0.yaml b/templates/release/de/meter/senec-home_0.yaml deleted file mode 100644 index f3ef295935..0000000000 --- a/templates/release/de/meter/senec-home_0.yaml +++ /dev/null @@ -1,45 +0,0 @@ -product: - brand: SENEC - description: .Home -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: senec-home - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) - advanced: | - type: template - template: senec-home - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) - - usage: pv - default: | - type: template - template: senec-home - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) - advanced: | - type: template - template: senec-home - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) - - usage: battery - default: | - type: template - template: senec-home - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) - advanced: | - type: template - template: senec-home - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml b/templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml new file mode 100644 index 0000000000..f54338773c --- /dev/null +++ b/templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml @@ -0,0 +1,33 @@ +template: senergy +product: + identifier: senergy-se-4-5-6ktl-s1-g2-inverter + brand: Senergy + description: SE 4/5/6KTL-S1/G2 Inverter +render: + - usage: pv + default: | + type: template + template: senergy + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/senergy_0.yaml b/templates/release/de/meter/senergy_0.yaml deleted file mode 100644 index 9a544572ac..0000000000 --- a/templates/release/de/meter/senergy_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Senergy - description: SE 4/5/6KTL-S1/G2 Inverter -render: - - usage: pv - default: | - type: template - template: senergy - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/senergy_1.yaml b/templates/release/de/meter/senergy_1.yaml deleted file mode 100644 index 1d9c00fb45..0000000000 --- a/templates/release/de/meter/senergy_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SolarMax - description: SP Series Inverter -render: - - usage: pv - default: | - type: template - template: senergy - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/shelly-1pm-mini.yaml b/templates/release/de/meter/shelly-1pm-mini.yaml new file mode 100644 index 0000000000..09f2db5ed3 --- /dev/null +++ b/templates/release/de/meter/shelly-1pm-mini.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-1pm-mini + brand: Shelly + description: 1PM mini + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-1pm.yaml b/templates/release/de/meter/shelly-1pm.yaml new file mode 100644 index 0000000000..07008d87c7 --- /dev/null +++ b/templates/release/de/meter/shelly-1pm.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-1pm + brand: Shelly + description: 1PM + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-1pm_0.yaml b/templates/release/de/meter/shelly-1pm_0.yaml deleted file mode 100644 index 3a058acc6d..0000000000 --- a/templates/release/de/meter/shelly-1pm_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Shelly - description: 1PM, EM, Plug S, Pro 3EM in monophase mode - group: Schaltbare Steckdosen -render: - - usage: grid - default: | - type: template - template: shelly-1pm - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional - - usage: pv - default: | - type: template - template: shelly-1pm - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional - - usage: charge - default: | - type: template - template: shelly-1pm - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional diff --git a/templates/release/de/meter/shelly-3em.yaml b/templates/release/de/meter/shelly-3em.yaml new file mode 100644 index 0000000000..7e8ebab9da --- /dev/null +++ b/templates/release/de/meter/shelly-3em.yaml @@ -0,0 +1,73 @@ +template: shelly-3em +product: + identifier: shelly-3em + brand: Shelly + description: 3EM +render: + - usage: grid + default: | + type: template + template: shelly-3em + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: shelly-3em + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: pv + default: | + type: template + template: shelly-3em + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: shelly-3em + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: charge + default: | + type: template + template: shelly-3em + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: shelly-3em + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-3em_0.yaml b/templates/release/de/meter/shelly-3em_0.yaml deleted file mode 100644 index aadea8b572..0000000000 --- a/templates/release/de/meter/shelly-3em_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Shelly - description: 3EM -render: - - usage: grid - default: | - type: template - template: shelly-3em - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: shelly-3em - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: shelly-3em - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: shelly-3em - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: charge - default: | - type: template - template: shelly-3em - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: shelly-3em - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/meter/shelly-em.yaml b/templates/release/de/meter/shelly-em.yaml new file mode 100644 index 0000000000..23bea3a866 --- /dev/null +++ b/templates/release/de/meter/shelly-em.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-em + brand: Shelly + description: EM + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-plug-s.yaml b/templates/release/de/meter/shelly-plug-s.yaml new file mode 100644 index 0000000000..9a5d074588 --- /dev/null +++ b/templates/release/de/meter/shelly-plug-s.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-plug-s + brand: Shelly + description: Plug S + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pm-mini.yaml b/templates/release/de/meter/shelly-pm-mini.yaml new file mode 100644 index 0000000000..715f252acb --- /dev/null +++ b/templates/release/de/meter/shelly-pm-mini.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pm-mini + brand: Shelly + description: PM mini + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pro-1pm.yaml b/templates/release/de/meter/shelly-pro-1pm.yaml new file mode 100644 index 0000000000..acb79b4c71 --- /dev/null +++ b/templates/release/de/meter/shelly-pro-1pm.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pro-1pm + brand: Shelly + description: Pro 1PM + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pro-3-em.yaml b/templates/release/de/meter/shelly-pro-3-em.yaml new file mode 100644 index 0000000000..eb4100b028 --- /dev/null +++ b/templates/release/de/meter/shelly-pro-3-em.yaml @@ -0,0 +1,58 @@ +template: shelly-pro-3em +product: + identifier: shelly-pro-3-em + brand: Shelly + description: Pro 3 EM +render: + - usage: grid + default: | + type: template + template: shelly-pro-3em + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: pv + default: | + type: template + template: shelly-pro-3em + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: charge + default: | + type: template + template: shelly-pro-3em + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml b/templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml new file mode 100644 index 0000000000..5b9a3446ce --- /dev/null +++ b/templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pro-3em-monophase-mode + brand: Shelly + description: Pro 3EM (monophase mode) + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pro-3em_0.yaml b/templates/release/de/meter/shelly-pro-3em_0.yaml deleted file mode 100644 index 5287e9eb9d..0000000000 --- a/templates/release/de/meter/shelly-pro-3em_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Shelly - description: Pro 3 EM -render: - - usage: grid - default: | - type: template - template: shelly-pro-3em - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: shelly-pro-3em - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: charge - default: | - type: template - template: shelly-pro-3em - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/meter/shelly-pro-em.yaml b/templates/release/de/meter/shelly-pro-em.yaml new file mode 100644 index 0000000000..f644bc9d16 --- /dev/null +++ b/templates/release/de/meter/shelly-pro-em.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pro-em + brand: Shelly + description: Pro EM + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/siemens-7kt1665.yaml b/templates/release/de/meter/siemens-7kt1665.yaml new file mode 100644 index 0000000000..f5dbf9221f --- /dev/null +++ b/templates/release/de/meter/siemens-7kt1665.yaml @@ -0,0 +1,74 @@ +template: siemens-7kt1665 +product: + identifier: siemens-7kt1665 + brand: Siemens + description: 7KT1665 +render: + - usage: grid + default: | + type: template + template: siemens-7kt1665 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: siemens-7kt1665 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/siemens-7kt1665_0.yaml b/templates/release/de/meter/siemens-7kt1665_0.yaml deleted file mode 100644 index 938c0727f0..0000000000 --- a/templates/release/de/meter/siemens-7kt1665_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Siemens - description: 7KT1665 -render: - - usage: grid - default: | - type: template - template: siemens-7kt1665 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: siemens-7kt1665 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/siemens-junelight-smart-battery.yaml b/templates/release/de/meter/siemens-junelight-smart-battery.yaml new file mode 100644 index 0000000000..795dbeb72c --- /dev/null +++ b/templates/release/de/meter/siemens-junelight-smart-battery.yaml @@ -0,0 +1,98 @@ +template: siemens-junelight +product: + identifier: siemens-junelight-smart-battery + brand: Siemens + description: Junelight Smart Battery +description: | + Die Batterie muss mit dem Installer Zugang auf Loxone gestellt werden. + +render: + - usage: grid + default: | + type: template + template: siemens-junelight + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: siemens-junelight + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: siemens-junelight + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: siemens-junelight + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: siemens-junelight + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: siemens-junelight + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/siemens-junelight_0.yaml b/templates/release/de/meter/siemens-junelight_0.yaml deleted file mode 100644 index e9bc6c3149..0000000000 --- a/templates/release/de/meter/siemens-junelight_0.yaml +++ /dev/null @@ -1,71 +0,0 @@ -product: - brand: Siemens - description: Junelight Smart Battery -description: | - Die Batterie muss mit dem Installer Zugang auf Loxone gestellt werden. - -render: - - usage: grid - default: | - type: template - template: siemens-junelight - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: siemens-junelight - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: siemens-junelight - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: siemens-junelight - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: siemens-junelight - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: siemens-junelight - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/siemens-pac-2200.yaml b/templates/release/de/meter/siemens-pac-2200.yaml new file mode 100644 index 0000000000..d508896cb5 --- /dev/null +++ b/templates/release/de/meter/siemens-pac-2200.yaml @@ -0,0 +1,74 @@ +template: siemens-pac2200 +product: + identifier: siemens-pac-2200 + brand: Siemens + description: PAC 2200 +render: + - usage: grid + default: | + type: template + template: siemens-pac2200 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: siemens-pac2200 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/siemens-pac2200_0.yaml b/templates/release/de/meter/siemens-pac2200_0.yaml deleted file mode 100644 index f4a8b1239f..0000000000 --- a/templates/release/de/meter/siemens-pac2200_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Siemens - description: PAC 2200 -render: - - usage: grid - default: | - type: template - template: siemens-pac2200 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: siemens-pac2200 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml b/templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml new file mode 100644 index 0000000000..8a39e5d207 --- /dev/null +++ b/templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml @@ -0,0 +1,91 @@ +template: sigenergy +product: + identifier: sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec + brand: Sigenergy + description: Sigen Hybrid/Sigen PV Max/SigenStore EC +description: | + Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen App aktivieren bevor diese Konfiguration funktional ist. Diese Option ist in der mySigen App für Kunden nicht verfügbar. +render: + - usage: grid + default: | + type: template + template: sigenergy + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # optional + advanced: | + type: template + template: sigenergy + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # optional + - usage: pv + default: | + type: template + template: sigenergy + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # optional + advanced: | + type: template + template: sigenergy + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # optional + - usage: battery + default: | + type: template + template: sigenergy + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # optional + advanced: | + type: template + template: sigenergy + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: id + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sigenergy_0.yaml b/templates/release/de/meter/sigenergy_0.yaml deleted file mode 100644 index 6a5b260418..0000000000 --- a/templates/release/de/meter/sigenergy_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Sigenergy - description: Sigen Hybrid/Sigen PV Max/SigenStore EC -description: | - Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen App aktivieren bevor diese Konfiguration funktional ist. Diese Option ist in der mySigen App für Kunden nicht verfügbar. -render: - - usage: grid - default: | - type: template - template: sigenergy - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 1 # optional - advanced: | - type: template - template: sigenergy - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 1 # optional - - usage: pv - default: | - type: template - template: sigenergy - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 1 # optional - advanced: | - type: template - template: sigenergy - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 1 # optional - - usage: battery - default: | - type: template - template: sigenergy - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 1 # optional - advanced: | - type: template - template: sigenergy - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - id: 1 # optional - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/slimmelezer-V2_0.yaml b/templates/release/de/meter/slimmelezer-V2_0.yaml deleted file mode 100644 index bbcd50edfb..0000000000 --- a/templates/release/de/meter/slimmelezer-V2_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zuidwijk - description: SlimmeLezer(+) V2 -description: | - Neuere Slimmelezer-Geräte verwenden eine andere Konfiguration. Probieren Sie diese Vorlage aus, wenn die andere fehlschlägt. -render: - - usage: grid - default: | - type: template - template: slimmelezer-V2 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/slimmelezer-luxembourg_0.yaml b/templates/release/de/meter/slimmelezer-luxembourg_0.yaml deleted file mode 100644 index bfb89cd89a..0000000000 --- a/templates/release/de/meter/slimmelezer-luxembourg_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zuidwijk - description: SlimmeLezer(+) in Luxembourg -description: | - Slimmelezer-Geräte in Luxemburg verwenden für verschiedene Sensoren andere Namen. -render: - - usage: grid - default: | - type: template - template: slimmelezer-luxembourg - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/slimmelezer_0.yaml b/templates/release/de/meter/slimmelezer_0.yaml deleted file mode 100644 index 8a5605e84c..0000000000 --- a/templates/release/de/meter/slimmelezer_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Zuidwijk - description: SlimmeLezer(+) -render: - - usage: grid - default: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle diff --git a/templates/release/de/meter/slimmelezer_1.yaml b/templates/release/de/meter/slimmelezer_1.yaml deleted file mode 100644 index e6c484c158..0000000000 --- a/templates/release/de/meter/slimmelezer_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: ESPHome - description: DSMR -render: - - usage: grid - default: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle diff --git a/templates/release/de/meter/slimmelezer_2.yaml b/templates/release/de/meter/slimmelezer_2.yaml deleted file mode 100644 index 5abf7efa29..0000000000 --- a/templates/release/de/meter/slimmelezer_2.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: mhendriks - description: P1 dongle -render: - - usage: grid - default: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle diff --git a/templates/release/de/meter/sma-data-manager.yaml b/templates/release/de/meter/sma-data-manager.yaml new file mode 100644 index 0000000000..45b70ffb2f --- /dev/null +++ b/templates/release/de/meter/sma-data-manager.yaml @@ -0,0 +1,97 @@ +template: sma-data-manager +product: + identifier: sma-data-manager + brand: SMA + description: Data Manager +description: | + In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikation" der Schalter "Modbus Server aktivieren" eingeschaltet sein. +render: + - usage: grid + default: | + type: template + template: sma-data-manager + usage: grid + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-data-manager + usage: grid + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sma-data-manager + usage: pv + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-data-manager + usage: pv + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sma-data-manager + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-data-manager + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-data-manager_0.yaml b/templates/release/de/meter/sma-data-manager_0.yaml deleted file mode 100644 index 7c38f5c962..0000000000 --- a/templates/release/de/meter/sma-data-manager_0.yaml +++ /dev/null @@ -1,70 +0,0 @@ -product: - brand: SMA - description: Data Manager -description: | - In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikation" der Schalter "Modbus Server aktivieren" eingeschaltet sein. -render: - - usage: grid - default: | - type: template - template: sma-data-manager - usage: grid - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-data-manager - usage: grid - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sma-data-manager - usage: pv - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-data-manager - usage: pv - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sma-data-manager - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-data-manager - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/sma-energy-meter.yaml b/templates/release/de/meter/sma-energy-meter.yaml new file mode 100644 index 0000000000..b9fddbb8c2 --- /dev/null +++ b/templates/release/de/meter/sma-energy-meter.yaml @@ -0,0 +1,49 @@ +template: sma-energy-meter +product: + identifier: sma-energy-meter + brand: SMA + description: Energy Meter +render: + - usage: grid + default: | + type: template + template: sma-energy-meter + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: sma-energy-meter + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + interface: eth0 # Netzwerkschnittstelle, optional + - usage: pv + default: | + type: template + template: sma-energy-meter + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: sma-energy-meter + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + interface: eth0 # Netzwerkschnittstelle, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: interface + example: eth0 + default: + choice: [] + unit: + description: Netzwerkschnittstelle + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-energy-meter_0.yaml b/templates/release/de/meter/sma-energy-meter_0.yaml deleted file mode 100644 index a95d06d013..0000000000 --- a/templates/release/de/meter/sma-energy-meter_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: SMA - description: Energy Meter -render: - - usage: grid - default: | - type: template - template: sma-energy-meter - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: sma-energy-meter - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - interface: eth0 # Netzwerkschnittstelle, optional - - usage: pv - default: | - type: template - template: sma-energy-meter - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: sma-energy-meter - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - interface: eth0 # Netzwerkschnittstelle, optional diff --git a/templates/release/de/meter/sma-home-manager_0.yaml b/templates/release/de/meter/sma-home-manager_0.yaml deleted file mode 100644 index 39ba851d74..0000000000 --- a/templates/release/de/meter/sma-home-manager_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: SMA - description: Sunny Home Manager 2.0 -capabilities: ["smahems"] -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: sma-home-manager - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: sma-home-manager - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - interface: eth0 # Netzwerkschnittstelle, optional diff --git a/templates/release/de/meter/sma-hybrid_0.yaml b/templates/release/de/meter/sma-hybrid_0.yaml deleted file mode 100644 index c4a3221706..0000000000 --- a/templates/release/de/meter/sma-hybrid_0.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: SMA - description: Smart Energy Hybrid-Wechselrichter -capabilities: ["battery-control"] -render: - - usage: pv - default: | - type: template - template: sma-hybrid - usage: pv - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-hybrid - usage: pv - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: sma-hybrid - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-hybrid - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional diff --git a/templates/release/de/meter/sma-inverter-modbus_0.yaml b/templates/release/de/meter/sma-inverter-modbus_0.yaml deleted file mode 100644 index cda83af755..0000000000 --- a/templates/release/de/meter/sma-inverter-modbus_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SMA - description: Wechselrichter (Modbus) -render: - - usage: pv - default: | - type: template - template: sma-inverter-modbus - usage: pv - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sma-inverter-speedwire.yaml b/templates/release/de/meter/sma-inverter-speedwire.yaml new file mode 100644 index 0000000000..da436c8550 --- /dev/null +++ b/templates/release/de/meter/sma-inverter-speedwire.yaml @@ -0,0 +1,62 @@ +template: sma-inverter-speedwire +product: + identifier: sma-inverter-speedwire + brand: SMA + description: Wechselrichter (Speedwire) +requirements: ["skiptest"] +render: + - usage: pv + default: | + type: template + template: sma-inverter-speedwire + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) + advanced: | + type: template + template: sma-inverter-speedwire + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) + - usage: battery + default: | + type: template + template: sma-inverter-speedwire + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) + advanced: | + type: template + template: sma-inverter-speedwire + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Passwort für Benutzergruppe Benutzer + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-inverter-speedwire_0.yaml b/templates/release/de/meter/sma-inverter-speedwire_0.yaml deleted file mode 100644 index 86c07ccbd3..0000000000 --- a/templates/release/de/meter/sma-inverter-speedwire_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: SMA - description: Wechselrichter (Speedwire) -requirements: ["skiptest"] -render: - - usage: pv - default: | - type: template - template: sma-inverter-speedwire - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) - advanced: | - type: template - template: sma-inverter-speedwire - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) - - usage: battery - default: | - type: template - template: sma-inverter-speedwire - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) - advanced: | - type: template - template: sma-inverter-speedwire - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort für Benutzergruppe Benutzer (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/sma-sbs-15-25-modbus_0.yaml b/templates/release/de/meter/sma-sbs-15-25-modbus_0.yaml deleted file mode 100644 index e8d1288ce3..0000000000 --- a/templates/release/de/meter/sma-sbs-15-25-modbus_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: SMA - description: Sunny Boy Storage 1.5/2.0/2.5 (Modbus) -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sma-sbs-15-25-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-sbs-15-25-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional diff --git a/templates/release/de/meter/sma-sbs-modbus_0.yaml b/templates/release/de/meter/sma-sbs-modbus_0.yaml deleted file mode 100644 index d992bdfcf5..0000000000 --- a/templates/release/de/meter/sma-sbs-modbus_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: SMA - description: Sunny Boy Storage 3.7/5.0/6.0 (Modbus) -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sma-sbs-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-sbs-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional diff --git a/templates/release/de/meter/sma-si-modbus_0.yaml b/templates/release/de/meter/sma-si-modbus_0.yaml deleted file mode 100644 index 390952c089..0000000000 --- a/templates/release/de/meter/sma-si-modbus_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: SMA - description: Sunny Island (Modbus) -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sma-si-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-si-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional diff --git a/templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml b/templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml new file mode 100644 index 0000000000..8dccb69d36 --- /dev/null +++ b/templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml @@ -0,0 +1,105 @@ +template: sma-hybrid +product: + identifier: sma-smart-energy-hybrid-inverter + brand: SMA + description: Smart Energy Hybrid-Wechselrichter +capabilities: ["battery-control"] +render: + - usage: pv + default: | + type: template + template: sma-hybrid + usage: pv + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-hybrid + usage: pv + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: sma-hybrid + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-hybrid + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: Der ModbusTCP Server muss aktiviert sein. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml b/templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml new file mode 100644 index 0000000000..8cd1a32f45 --- /dev/null +++ b/templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml @@ -0,0 +1,74 @@ +template: sma-sbs-15-25-modbus +product: + identifier: sma-sunny-boy-storage-1-5-2-0-2-5-modbus + brand: SMA + description: Sunny Boy Storage 1.5/2.0/2.5 (Modbus) +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sma-sbs-15-25-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-sbs-15-25-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: Der ModbusTCP Server muss aktiviert sein. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml b/templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml new file mode 100644 index 0000000000..e311fc4697 --- /dev/null +++ b/templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml @@ -0,0 +1,74 @@ +template: sma-sbs-modbus +product: + identifier: sma-sunny-boy-storage-3-7-5-0-6-0-modbus + brand: SMA + description: Sunny Boy Storage 3.7/5.0/6.0 (Modbus) +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sma-sbs-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-sbs-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: Der ModbusTCP Server muss aktiviert sein. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-sunny-home-manager-2-0.yaml b/templates/release/de/meter/sma-sunny-home-manager-2-0.yaml new file mode 100644 index 0000000000..191be61b5b --- /dev/null +++ b/templates/release/de/meter/sma-sunny-home-manager-2-0.yaml @@ -0,0 +1,39 @@ +template: sma-home-manager +product: + identifier: sma-sunny-home-manager-2-0 + brand: SMA + description: Sunny Home Manager 2.0 +capabilities: ["smahems"] +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: sma-home-manager + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: sma-home-manager + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + interface: eth0 # Netzwerkschnittstelle, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: interface + example: eth0 + default: + choice: [] + unit: + description: Netzwerkschnittstelle + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-sunny-island-modbus.yaml b/templates/release/de/meter/sma-sunny-island-modbus.yaml new file mode 100644 index 0000000000..1f28350869 --- /dev/null +++ b/templates/release/de/meter/sma-sunny-island-modbus.yaml @@ -0,0 +1,74 @@ +template: sma-si-modbus +product: + identifier: sma-sunny-island-modbus + brand: SMA + description: Sunny Island (Modbus) +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sma-si-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-si-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: Der ModbusTCP Server muss aktiviert sein. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-webbox.yaml b/templates/release/de/meter/sma-webbox.yaml new file mode 100644 index 0000000000..496c6f88e8 --- /dev/null +++ b/templates/release/de/meter/sma-webbox.yaml @@ -0,0 +1,33 @@ +template: sma-webbox +product: + identifier: sma-webbox + brand: SMA + description: WebBox +render: + - usage: pv + default: | + type: template + template: sma-webbox + usage: pv + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: Der ModbusTCP Server muss aktiviert sein. + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sma-webbox_0.yaml b/templates/release/de/meter/sma-webbox_0.yaml deleted file mode 100644 index 2d6962964d..0000000000 --- a/templates/release/de/meter/sma-webbox_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SMA - description: WebBox -render: - - usage: pv - default: | - type: template - template: sma-webbox - usage: pv - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sma-wechselrichter-modbus.yaml b/templates/release/de/meter/sma-wechselrichter-modbus.yaml new file mode 100644 index 0000000000..4c32d326ff --- /dev/null +++ b/templates/release/de/meter/sma-wechselrichter-modbus.yaml @@ -0,0 +1,33 @@ +template: sma-inverter-modbus +product: + identifier: sma-wechselrichter-modbus + brand: SMA + description: Wechselrichter (Modbus) +render: + - usage: pv + default: | + type: template + template: sma-inverter-modbus + usage: pv + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: Der ModbusTCP Server muss aktiviert sein. + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-box.yaml b/templates/release/de/meter/smartfox-box.yaml new file mode 100644 index 0000000000..e8f8f078db --- /dev/null +++ b/templates/release/de/meter/smartfox-box.yaml @@ -0,0 +1,37 @@ +template: smartfox +product: + identifier: smartfox-box + brand: Smartfox + description: Box +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: smartfox + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: aux + default: | + type: template + template: smartfox + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-em2_0.yaml b/templates/release/de/meter/smartfox-em2_0.yaml deleted file mode 100644 index c2cb695141..0000000000 --- a/templates/release/de/meter/smartfox-em2_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Smartfox - description: Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) -description: | - `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. - -render: - - usage: grid - default: | - type: template - template: smartfox-em2 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: smartfox-em2 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - - usage: pv - default: | - type: template - template: smartfox-em2 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: smartfox-em2 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - - usage: aux - default: | - type: template - template: smartfox-em2 - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: smartfox-em2 - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname - cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/meter/smartfox-light-em2-firmware.yaml b/templates/release/de/meter/smartfox-light-em2-firmware.yaml new file mode 100644 index 0000000000..9c2a0507e5 --- /dev/null +++ b/templates/release/de/meter/smartfox-light-em2-firmware.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-light-em2-firmware + brand: Smartfox + description: Light (EM2 firmware) +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-pro-2.yaml b/templates/release/de/meter/smartfox-pro-2.yaml new file mode 100644 index 0000000000..ed13eaa4ac --- /dev/null +++ b/templates/release/de/meter/smartfox-pro-2.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro-2 + brand: Smartfox + description: Pro 2 +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-pro-light-2.yaml b/templates/release/de/meter/smartfox-pro-light-2.yaml new file mode 100644 index 0000000000..9b12cf1c72 --- /dev/null +++ b/templates/release/de/meter/smartfox-pro-light-2.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro-light-2 + brand: Smartfox + description: Pro Light 2 +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-pro-light.yaml b/templates/release/de/meter/smartfox-pro-light.yaml new file mode 100644 index 0000000000..f35af7cc19 --- /dev/null +++ b/templates/release/de/meter/smartfox-pro-light.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro-light + brand: Smartfox + description: Pro Light +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-pro.yaml b/templates/release/de/meter/smartfox-pro.yaml new file mode 100644 index 0000000000..12fbfb7dbc --- /dev/null +++ b/templates/release/de/meter/smartfox-pro.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro + brand: Smartfox + description: Pro +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-reg-extended.yaml b/templates/release/de/meter/smartfox-reg-extended.yaml new file mode 100644 index 0000000000..4c9e878fd3 --- /dev/null +++ b/templates/release/de/meter/smartfox-reg-extended.yaml @@ -0,0 +1,37 @@ +template: smartfox +product: + identifier: smartfox-reg-extended + brand: Smartfox + description: Reg extended +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: smartfox + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: aux + default: | + type: template + template: smartfox + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/smartfox-reg.yaml b/templates/release/de/meter/smartfox-reg.yaml new file mode 100644 index 0000000000..7bdb46e558 --- /dev/null +++ b/templates/release/de/meter/smartfox-reg.yaml @@ -0,0 +1,37 @@ +template: smartfox +product: + identifier: smartfox-reg + brand: Smartfox + description: Reg +description: | + `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + +render: + - usage: grid + default: | + type: template + template: smartfox + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: smartfox + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: aux + default: | + type: template + template: smartfox + usage: aux + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/smartfox_0.yaml b/templates/release/de/meter/smartfox_0.yaml deleted file mode 100644 index 6e0a3bf228..0000000000 --- a/templates/release/de/meter/smartfox_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Smartfox - description: Box, Reg, Reg extended -description: | - `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. - -render: - - usage: grid - default: | - type: template - template: smartfox - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: smartfox - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: aux - default: | - type: template - template: smartfox - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/sofarsolar-g3_0.yaml b/templates/release/de/meter/sofarsolar-g3_0.yaml deleted file mode 100644 index d57c84827a..0000000000 --- a/templates/release/de/meter/sofarsolar-g3_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: HYD 5…20K-3PH -capabilities: ["battery-control"] -description: | - Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) diff --git a/templates/release/de/meter/sofarsolar-g3_1.yaml b/templates/release/de/meter/sofarsolar-g3_1.yaml deleted file mode 100644 index be2fe291a7..0000000000 --- a/templates/release/de/meter/sofarsolar-g3_1.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: HYD 3…6K-EP -capabilities: ["battery-control"] -description: | - Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) diff --git a/templates/release/de/meter/sofarsolar-g3_2.yaml b/templates/release/de/meter/sofarsolar-g3_2.yaml deleted file mode 100644 index 41d8746013..0000000000 --- a/templates/release/de/meter/sofarsolar-g3_2.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: SOFAR 80…136KTL -capabilities: ["battery-control"] -description: | - Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) diff --git a/templates/release/de/meter/sofarsolar-g3_3.yaml b/templates/release/de/meter/sofarsolar-g3_3.yaml deleted file mode 100644 index ac178d41d3..0000000000 --- a/templates/release/de/meter/sofarsolar-g3_3.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: SOFAR 5…24KTL-G3 -capabilities: ["battery-control"] -description: | - Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) diff --git a/templates/release/de/meter/sofarsolar-hybrid-inverter.yaml b/templates/release/de/meter/sofarsolar-hybrid-inverter.yaml new file mode 100644 index 0000000000..f298b6c3d7 --- /dev/null +++ b/templates/release/de/meter/sofarsolar-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: sofarsolar-hybrid-inverter + brand: SofarSolar + description: Hybrid Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml b/templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml new file mode 100644 index 0000000000..f5d640675e --- /dev/null +++ b/templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-hyd-3-6k-ep + brand: SofarSolar + description: HYD 3…6K-EP +capabilities: ["battery-control"] +description: | + Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml b/templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml new file mode 100644 index 0000000000..b040741cf2 --- /dev/null +++ b/templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-hyd-5-20k-3ph + brand: SofarSolar + description: HYD 5…20K-3PH +capabilities: ["battery-control"] +description: | + Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sofarsolar-inverter.yaml b/templates/release/de/meter/sofarsolar-inverter.yaml new file mode 100644 index 0000000000..8b1ca89011 --- /dev/null +++ b/templates/release/de/meter/sofarsolar-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: sofarsolar-inverter + brand: SofarSolar + description: Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml b/templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml new file mode 100644 index 0000000000..77d0626980 --- /dev/null +++ b/templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-sofar-5-24ktl-g3 + brand: SofarSolar + description: SOFAR 5…24KTL-G3 +capabilities: ["battery-control"] +description: | + Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml b/templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml new file mode 100644 index 0000000000..400591f37b --- /dev/null +++ b/templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-sofar-80-136ktl + brand: SofarSolar + description: SOFAR 80…136KTL +capabilities: ["battery-control"] +description: | + Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sofarsolar_0.yaml b/templates/release/de/meter/sofarsolar_0.yaml deleted file mode 100644 index aabea22821..0000000000 --- a/templates/release/de/meter/sofarsolar_0.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: SofarSolar - description: Inverter, Hybrid Inverter -render: - - usage: grid - default: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/sofarsolar_1.yaml b/templates/release/de/meter/sofarsolar_1.yaml deleted file mode 100644 index 73e04dfc74..0000000000 --- a/templates/release/de/meter/sofarsolar_1.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: ZCS Azzurro - description: Inverter, Hybrid Inverter -render: - - usage: grid - default: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solaranzeige-solaranzeige.yaml b/templates/release/de/meter/solaranzeige-solaranzeige.yaml new file mode 100644 index 0000000000..a8f3899d7f --- /dev/null +++ b/templates/release/de/meter/solaranzeige-solaranzeige.yaml @@ -0,0 +1,100 @@ +template: solaranzeige +product: + identifier: solaranzeige-solaranzeige + brand: Solaranzeige + description: Solaranzeige +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: solaranzeige + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + advanced: | + type: template + template: solaranzeige + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: pv + default: | + type: template + template: solaranzeige + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + advanced: | + type: template + template: solaranzeige + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers + port: 1883 # Port, MQTT Broker Port (optional) + topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) + timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: IP Adresse oder der Hostname des MQTT Brokers + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT Broker Port + advanced: false + optional: true + - name: topic + example: + default: solaranzeige/box1 + choice: [] + unit: + description: Topic + help: Topic (ohne / am Anfang) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Zeitüberschreitung + help: Akzeptiere keine Daten die älter sind als dieser Wert + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solaranzeige_0.yaml b/templates/release/de/meter/solaranzeige_0.yaml deleted file mode 100644 index 48718aad30..0000000000 --- a/templates/release/de/meter/solaranzeige_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Solaranzeige - description: Solaranzeige -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: solaranzeige - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - advanced: | - type: template - template: solaranzeige - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: solaranzeige - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - advanced: | - type: template - template: solaranzeige - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname, IP Adresse oder der Hostname des MQTT Brokers - port: 1883 # Port, MQTT Broker Port (optional) - topic: solaranzeige/box1 # Topic, Topic (ohne / am Anfang) (optional) - timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/meter/solaredge-hybrid-inverter.yaml b/templates/release/de/meter/solaredge-hybrid-inverter.yaml new file mode 100644 index 0000000000..3d0fd7df2f --- /dev/null +++ b/templates/release/de/meter/solaredge-hybrid-inverter.yaml @@ -0,0 +1,219 @@ +template: solaredge-hybrid +product: + identifier: solaredge-hybrid-inverter + brand: SolarEdge + description: Hybrid Inverter +capabilities: ["battery-control"] +description: | + Nur ein System kann und darf zeitgleich eine Modbus TCP-Verbindung zum Wechselrichter haben! + Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "Remote" stehen. + +render: + - usage: grid + default: | + type: template + template: solaredge-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: solaredge-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional + watchdog: 60s # optional + - usage: pv + default: | + type: template + template: solaredge-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: solaredge-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: solaredge-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: solaredge-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional + capacity: 50 # Akkukapazität (kWh), optional + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 1502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/solaredge-hybrid_0.yaml b/templates/release/de/meter/solaredge-hybrid_0.yaml deleted file mode 100644 index 9ed7288084..0000000000 --- a/templates/release/de/meter/solaredge-hybrid_0.yaml +++ /dev/null @@ -1,161 +0,0 @@ -product: - brand: SolarEdge - description: Hybrid Inverter -capabilities: ["battery-control"] -description: | - Nur ein System kann und darf zeitgleich eine Modbus TCP-Verbindung zum Wechselrichter haben! - Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "Remote" stehen. - -render: - - usage: grid - default: | - type: template - template: solaredge-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: solaredge-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional - watchdog: 60s # optional - - usage: pv - default: | - type: template - template: solaredge-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: solaredge-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: solaredge-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: solaredge-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional - capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional diff --git a/templates/release/de/meter/solaredge-inverter.yaml b/templates/release/de/meter/solaredge-inverter.yaml new file mode 100644 index 0000000000..0749031c49 --- /dev/null +++ b/templates/release/de/meter/solaredge-inverter.yaml @@ -0,0 +1,87 @@ +template: solaredge-inverter +product: + identifier: solaredge-inverter + brand: SolarEdge + description: Wechselrichter +description: | + Nur ein System kann und darf auf den Wechselrichter zugreifen! +render: + - usage: grid + default: | + type: template + template: solaredge-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional + - usage: pv + default: | + type: template + template: solaredge-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Zeitüberschreitung, optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 1502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/solaredge-inverter_0.yaml b/templates/release/de/meter/solaredge-inverter_0.yaml deleted file mode 100644 index a96acbb317..0000000000 --- a/templates/release/de/meter/solaredge-inverter_0.yaml +++ /dev/null @@ -1,56 +0,0 @@ -product: - brand: SolarEdge - description: Wechselrichter -description: | - Nur ein System kann und darf auf den Wechselrichter zugreifen! -render: - - usage: grid - default: | - type: template - template: solaredge-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional - - usage: pv - default: | - type: template - template: solaredge-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Zeitüberschreitung, optional diff --git a/templates/release/de/meter/solarlog.yaml b/templates/release/de/meter/solarlog.yaml new file mode 100644 index 0000000000..539b0b4341 --- /dev/null +++ b/templates/release/de/meter/solarlog.yaml @@ -0,0 +1,42 @@ +template: solarlog +product: + identifier: solarlog + description: Solarlog +description: | + Wir empfehlen dieses Gerät für den Netzbezug/Einspeisewerte nur zu verwenden, wenn kein anderes Gerät diese Daten liefert. + Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall für die erwähnten Werte verwendet werden! + +render: + - usage: grid + default: | + type: template + template: solarlog + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: solarlog + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solarlog_0.yaml b/templates/release/de/meter/solarlog_0.yaml deleted file mode 100644 index 0c6b7145f8..0000000000 --- a/templates/release/de/meter/solarlog_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - description: Solarlog -description: | - Wir empfehlen dieses Gerät für den Netzbezug/Einspeisewerte nur zu verwenden, wenn kein anderes Gerät diese Daten liefert. - Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall für die erwähnten Werte verwendet werden! - -render: - - usage: grid - default: | - type: template - template: solarlog - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - - usage: pv - default: | - type: template - template: solarlog - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional diff --git a/templates/release/de/meter/solarman_0.yaml b/templates/release/de/meter/solarman_0.yaml deleted file mode 100644 index 17dd0ec4c7..0000000000 --- a/templates/release/de/meter/solarman_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: IGEN Tech - description: Solarman Logger -render: - - usage: pv - default: | - type: template - template: solarman - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: admin # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) - password: admin # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml b/templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml new file mode 100644 index 0000000000..bc3b9188cd --- /dev/null +++ b/templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml @@ -0,0 +1,120 @@ +template: solarmax-maxstorage +product: + identifier: solarmax-max-storage-max-storage-ultimate + brand: SolarMax + description: MAX.STORAGE / MAX.STORAGE Ultimate +capabilities: ["battery-control"] +description: | + Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. +render: + - usage: grid + default: | + type: template + template: solarmax-maxstorage + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solarmax-maxstorage + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + watchdog: 60s # optional + - usage: pv + default: | + type: template + template: solarmax-maxstorage + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solarmax-maxstorage + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: solarmax-maxstorage + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solarmax-maxstorage + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/solarmax-maxstorage_0.yaml b/templates/release/de/meter/solarmax-maxstorage_0.yaml deleted file mode 100644 index 26cd9e902e..0000000000 --- a/templates/release/de/meter/solarmax-maxstorage_0.yaml +++ /dev/null @@ -1,75 +0,0 @@ -product: - brand: SolarMax - description: MAX.STORAGE / MAX.STORAGE Ultimate -capabilities: ["battery-control"] -description: | - Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. -render: - - usage: grid - default: | - type: template - template: solarmax-maxstorage - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solarmax-maxstorage - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - watchdog: 60s # optional - - usage: pv - default: | - type: template - template: solarmax-maxstorage - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solarmax-maxstorage - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: solarmax-maxstorage - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solarmax-maxstorage - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional diff --git a/templates/release/de/meter/solarmax-smt_0.yaml b/templates/release/de/meter/solarmax-smt_0.yaml deleted file mode 100644 index 177b29e4e3..0000000000 --- a/templates/release/de/meter/solarmax-smt_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SolarMax - description: SolarMax SMT -render: - - usage: pv - default: | - type: template - template: solarmax-smt - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/solarmax-solarmax-smt.yaml b/templates/release/de/meter/solarmax-solarmax-smt.yaml new file mode 100644 index 0000000000..f28a6b03f5 --- /dev/null +++ b/templates/release/de/meter/solarmax-solarmax-smt.yaml @@ -0,0 +1,33 @@ +template: solarmax-smt +product: + identifier: solarmax-solarmax-smt + brand: SolarMax + description: SolarMax SMT +render: + - usage: pv + default: | + type: template + template: solarmax-smt + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/solarmax-sp-series-inverter.yaml b/templates/release/de/meter/solarmax-sp-series-inverter.yaml new file mode 100644 index 0000000000..430c460089 --- /dev/null +++ b/templates/release/de/meter/solarmax-sp-series-inverter.yaml @@ -0,0 +1,33 @@ +template: senergy +product: + identifier: solarmax-sp-series-inverter + brand: SolarMax + description: SP Series Inverter +render: + - usage: pv + default: | + type: template + template: senergy + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/solarwatt-energymanager-pro.yaml b/templates/release/de/meter/solarwatt-energymanager-pro.yaml new file mode 100644 index 0000000000..41f71e88ce --- /dev/null +++ b/templates/release/de/meter/solarwatt-energymanager-pro.yaml @@ -0,0 +1,59 @@ +template: solarwatt +product: + identifier: solarwatt-energymanager-pro + brand: Solarwatt + description: EnergyManager Pro +render: + - usage: grid + default: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: battery + default: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solarwatt-energymanager.yaml b/templates/release/de/meter/solarwatt-energymanager.yaml new file mode 100644 index 0000000000..aa02b3831e --- /dev/null +++ b/templates/release/de/meter/solarwatt-energymanager.yaml @@ -0,0 +1,59 @@ +template: solarwatt +product: + identifier: solarwatt-energymanager + brand: Solarwatt + description: EnergyManager +render: + - usage: grid + default: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: battery + default: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solarwatt-flex_0.yaml b/templates/release/de/meter/solarwatt-flex_0.yaml deleted file mode 100644 index d78b9d9f23..0000000000 --- a/templates/release/de/meter/solarwatt-flex_0.yaml +++ /dev/null @@ -1,41 +0,0 @@ -product: - brand: Solarwatt - description: Manager flex -description: | - Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. - -render: - - usage: grid - default: | - type: template - template: solarwatt-flex - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt-flex - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: solarwatt-flex - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt-flex - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: battery - default: | - type: template - template: solarwatt-flex - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt-flex - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solarwatt-manager-flex.yaml b/templates/release/de/meter/solarwatt-manager-flex.yaml new file mode 100644 index 0000000000..ba7163d1fd --- /dev/null +++ b/templates/release/de/meter/solarwatt-manager-flex.yaml @@ -0,0 +1,62 @@ +template: solarwatt-flex +product: + identifier: solarwatt-manager-flex + brand: Solarwatt + description: Manager flex +description: | + Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. + +render: + - usage: grid + default: | + type: template + template: solarwatt-flex + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt-flex + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: solarwatt-flex + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt-flex + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: battery + default: | + type: template + template: solarwatt-flex + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt-flex + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml b/templates/release/de/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml new file mode 100644 index 0000000000..6a62c11ff6 --- /dev/null +++ b/templates/release/de/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml @@ -0,0 +1,74 @@ +template: solarwatt-myreserve-matrix +product: + identifier: solarwatt-myreserve-matrix-lan-oder-powergateway + brand: Solarwatt + description: MyReserve Matrix (LAN oder PowerGateway) +render: + - usage: grid + default: | + type: template + template: solarwatt-myreserve-matrix + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + advanced: | + type: template + template: solarwatt-myreserve-matrix + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + - usage: pv + default: | + type: template + template: solarwatt-myreserve-matrix + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + advanced: | + type: template + template: solarwatt-myreserve-matrix + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + - usage: battery + default: | + type: template + template: solarwatt-myreserve-matrix + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + advanced: | + type: template + template: solarwatt-myreserve-matrix + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8080 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solarwatt-myreserve-matrix_0.yaml b/templates/release/de/meter/solarwatt-myreserve-matrix_0.yaml deleted file mode 100644 index 9618db1a48..0000000000 --- a/templates/release/de/meter/solarwatt-myreserve-matrix_0.yaml +++ /dev/null @@ -1,44 +0,0 @@ -product: - brand: Solarwatt - description: MyReserve Matrix (LAN oder PowerGateway) -render: - - usage: grid - default: | - type: template - template: solarwatt-myreserve-matrix - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - advanced: | - type: template - template: solarwatt-myreserve-matrix - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - - usage: pv - default: | - type: template - template: solarwatt-myreserve-matrix - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - advanced: | - type: template - template: solarwatt-myreserve-matrix - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - - usage: battery - default: | - type: template - template: solarwatt-myreserve-matrix - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - advanced: | - type: template - template: solarwatt-myreserve-matrix - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solarwatt-myreserve.yaml b/templates/release/de/meter/solarwatt-myreserve.yaml new file mode 100644 index 0000000000..59f6ffdb0a --- /dev/null +++ b/templates/release/de/meter/solarwatt-myreserve.yaml @@ -0,0 +1,59 @@ +template: solarwatt +product: + identifier: solarwatt-myreserve + brand: Solarwatt + description: MyReserve +render: + - usage: grid + default: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: battery + default: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solarwatt_0.yaml b/templates/release/de/meter/solarwatt_0.yaml deleted file mode 100644 index e00a42656a..0000000000 --- a/templates/release/de/meter/solarwatt_0.yaml +++ /dev/null @@ -1,38 +0,0 @@ -product: - brand: Solarwatt - description: MyReserve -render: - - usage: grid - default: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: battery - default: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solarwatt_1.yaml b/templates/release/de/meter/solarwatt_1.yaml deleted file mode 100644 index ef9d59c6d9..0000000000 --- a/templates/release/de/meter/solarwatt_1.yaml +++ /dev/null @@ -1,38 +0,0 @@ -product: - brand: Solarwatt - description: EnergyManager, EnergyManager Pro -render: - - usage: grid - default: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: battery - default: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - advanced: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solax-hybrid-cloud_0.yaml b/templates/release/de/meter/solax-hybrid-cloud_0.yaml deleted file mode 100644 index b84f6d46e8..0000000000 --- a/templates/release/de/meter/solax-hybrid-cloud_0.yaml +++ /dev/null @@ -1,49 +0,0 @@ -product: - brand: Solax - description: Hybrid-Wechselrichter (Cloud) -description: | - Der Solax Hybrid-Wechselrichter muss in der SolaxCloud angemeldet sein. - - **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. - -render: - - usage: grid - default: | - type: template - template: solax-hybrid-cloud - usage: grid - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') - serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen - advanced: | - type: template - template: solax-hybrid-cloud - usage: grid - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') - serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen - - usage: pv - default: | - type: template - template: solax-hybrid-cloud - usage: pv - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') - serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen - advanced: | - type: template - template: solax-hybrid-cloud - usage: pv - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') - serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen - - usage: battery - default: | - type: template - template: solax-hybrid-cloud - usage: battery - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') - serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen - advanced: | - type: template - template: solax-hybrid-cloud - usage: battery - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') - serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solax-hybrid-inverter-cloud.yaml b/templates/release/de/meter/solax-hybrid-inverter-cloud.yaml new file mode 100644 index 0000000000..536cd48e44 --- /dev/null +++ b/templates/release/de/meter/solax-hybrid-inverter-cloud.yaml @@ -0,0 +1,79 @@ +template: solax-hybrid-cloud +product: + identifier: solax-hybrid-inverter-cloud + brand: Solax + description: Hybrid-Wechselrichter (Cloud) +description: | + Der Solax Hybrid-Wechselrichter muss in der SolaxCloud angemeldet sein. + + **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. + +render: + - usage: grid + default: | + type: template + template: solax-hybrid-cloud + usage: grid + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + advanced: | + type: template + template: solax-hybrid-cloud + usage: grid + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + - usage: pv + default: | + type: template + template: solax-hybrid-cloud + usage: pv + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + advanced: | + type: template + template: solax-hybrid-cloud + usage: pv + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + - usage: battery + default: | + type: template + template: solax-hybrid-cloud + usage: battery + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + advanced: | + type: template + template: solax-hybrid-cloud + usage: battery + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: tokenid + example: + default: + choice: [] + unit: + description: SolaxCloud TokenID + help: 'https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: ''20241028488283838'')' + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Seriennummer + help: https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml b/templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml new file mode 100644 index 0000000000..cd686566dd --- /dev/null +++ b/templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml @@ -0,0 +1,225 @@ +template: solax +product: + identifier: solax-hybrid-x1-x3-g3-g4 + brand: Solax + description: Hybrid X1/X3 G3/G4 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + advanced: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + advanced: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + storageunit: 1 # optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + advanced: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + storageunit: 1 # optional + capacity: 50 # Akkukapazität (kWh), optional + defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. + advanced: true + optional: true +modbus: + baudrate: 19200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/solax-inverter-cloud.yaml b/templates/release/de/meter/solax-inverter-cloud.yaml new file mode 100644 index 0000000000..01b891f2a3 --- /dev/null +++ b/templates/release/de/meter/solax-inverter-cloud.yaml @@ -0,0 +1,37 @@ +template: solax-inverter-cloud +product: + identifier: solax-inverter-cloud + brand: Solax + description: PV-Wechselrichter (Cloud) +description: | + Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. + + **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. + +render: + - usage: pv + default: | + type: template + template: solax-inverter-cloud + usage: pv + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') + serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen +params: + - name: tokenid + example: + default: + choice: [] + unit: + description: SolaxCloud TokenID + help: 'https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: ''20241028488283838'')' + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Seriennummer + help: https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/solax-inverter-cloud_0.yaml b/templates/release/de/meter/solax-inverter-cloud_0.yaml deleted file mode 100644 index 4b92cb14bc..0000000000 --- a/templates/release/de/meter/solax-inverter-cloud_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Solax - description: PV-Wechselrichter (Cloud) -description: | - Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. - - **Achtung**: Die Werte können nur alle 150s abgerufen werden und dann auch 5 Minuten alt sein. Die Laderegelung nach PV kann hiermit nicht optimal gesteuert werden! Nur als Notfalloption nutzen wenn kein lokaler Zugriff möglich ist. - -render: - - usage: pv - default: | - type: template - template: solax-inverter-cloud - usage: pv - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') - serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen diff --git a/templates/release/de/meter/solax_0.yaml b/templates/release/de/meter/solax_0.yaml deleted file mode 100644 index 8c86884e4d..0000000000 --- a/templates/release/de/meter/solax_0.yaml +++ /dev/null @@ -1,158 +0,0 @@ -product: - brand: Solax - description: Hybrid X1/X3 G3/G4 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - advanced: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - advanced: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - advanced: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) diff --git a/templates/release/de/meter/solax_1.yaml b/templates/release/de/meter/solax_1.yaml deleted file mode 100644 index 3298fca71e..0000000000 --- a/templates/release/de/meter/solax_1.yaml +++ /dev/null @@ -1,158 +0,0 @@ -product: - brand: Qcells - description: Q.HOME ESS HYB-G3 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - advanced: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - advanced: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - advanced: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional - capacity: 50 # Akkukapazität (kWh), optional - defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) diff --git a/templates/release/de/meter/solinteng.yaml b/templates/release/de/meter/solinteng.yaml new file mode 100644 index 0000000000..3f1385cf13 --- /dev/null +++ b/templates/release/de/meter/solinteng.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: solinteng + brand: Solinteng +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/solis-hybrid-s_0.yaml b/templates/release/de/meter/solis-hybrid-s_0.yaml deleted file mode 100644 index ee694fa3c8..0000000000 --- a/templates/release/de/meter/solis-hybrid-s_0.yaml +++ /dev/null @@ -1,111 +0,0 @@ -product: - brand: Ginlong - description: Solis Hybrid Inverter (S Series) -render: - - usage: grid - default: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solis-hybrid-s_1.yaml b/templates/release/de/meter/solis-hybrid-s_1.yaml deleted file mode 100644 index 82b4dacf82..0000000000 --- a/templates/release/de/meter/solis-hybrid-s_1.yaml +++ /dev/null @@ -1,111 +0,0 @@ -product: - brand: Axitec - description: AXIhycon 12-15H -render: - - usage: grid - default: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solis-hybrid_0.yaml b/templates/release/de/meter/solis-hybrid_0.yaml deleted file mode 100644 index 471ad04ed5..0000000000 --- a/templates/release/de/meter/solis-hybrid_0.yaml +++ /dev/null @@ -1,111 +0,0 @@ -product: - brand: Ginlong - description: Solis Hybrid Inverter (RHI series) -render: - - usage: grid - default: | - type: template - template: solis-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: solis-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/solis_0.yaml b/templates/release/de/meter/solis_0.yaml deleted file mode 100644 index 060c4546dc..0000000000 --- a/templates/release/de/meter/solis_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Ginlong - description: Solis Inverter -render: - - usage: grid - default: | - type: template - template: solis - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sonnen-comfort.yaml b/templates/release/de/meter/sonnen-comfort.yaml new file mode 100644 index 0000000000..86e0e3ac18 --- /dev/null +++ b/templates/release/de/meter/sonnen-comfort.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-comfort + brand: Sonnen + description: comfort +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sonnen-eco-5.yaml b/templates/release/de/meter/sonnen-eco-5.yaml new file mode 100644 index 0000000000..f1cdab990c --- /dev/null +++ b/templates/release/de/meter/sonnen-eco-5.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-eco-5 + brand: Sonnen + description: eco 5 +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sonnen-eco-6.yaml b/templates/release/de/meter/sonnen-eco-6.yaml new file mode 100644 index 0000000000..5d1da0d9d7 --- /dev/null +++ b/templates/release/de/meter/sonnen-eco-6.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-eco-6 + brand: Sonnen + description: eco 6 +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sonnen-oem-6-5.yaml b/templates/release/de/meter/sonnen-oem-6-5.yaml new file mode 100644 index 0000000000..fa3c8646a1 --- /dev/null +++ b/templates/release/de/meter/sonnen-oem-6-5.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-oem-6-5 + brand: Sonnen + description: oem 6.5 +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 7979 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/sonnen-sonnenbatterie.yaml b/templates/release/de/meter/sonnen-sonnenbatterie.yaml new file mode 100644 index 0000000000..8c7709f177 --- /dev/null +++ b/templates/release/de/meter/sonnen-sonnenbatterie.yaml @@ -0,0 +1,111 @@ +template: sonnenbatterie +product: + identifier: sonnen-sonnenbatterie + brand: Sonnen + description: sonnenBatterie +capabilities: ["battery-control"] +description: | + Für die aktive Batteriesteuerung muss über das Webinterface der sonnenBatterie (unter Software-Integration) das "JSON Write API" aktiviert und das dort generierte API-Token in der Batteriekonfiguration unter `token` eingetragen werden. + Als Betriebsart der sonnenBatterie werden die beiden Modi "Eigenverbrauch" (Standard) und "Time-of-use" unterstützt. Der Modus kann über den Parameter `defaultmode` an die Konfiguration der sonnenBatterie angepasst werden. + Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBatterie über den Parameter `maxchargepower` angepasst werden. + +render: + - usage: grid + default: | + type: template + template: sonnenbatterie + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + advanced: | + type: template + template: sonnenbatterie + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + - usage: pv + default: | + type: template + template: sonnenbatterie + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + advanced: | + type: template + template: sonnenbatterie + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + - usage: battery + default: | + type: template + template: sonnenbatterie + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + token: # API Token (benötigt für aktive Batteriesteuerung) (optional) + advanced: | + type: template + template: sonnenbatterie + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8080 # Port, optional + token: # API Token (benötigt für aktive Batteriesteuerung) (optional) + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: 3300 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) + defaultmode: self-consumption # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. [self-consumption, time-of-use] +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8080 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (benötigt für aktive Batteriesteuerung) + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 3300 + choice: [] + unit: W + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers. + advanced: true + optional: true + - name: defaultmode + example: + default: self-consumption + choice: ['self-consumption', 'time-of-use'] + unit: + description: Standardmodus für die aktive Batteriesteuerung + help: Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/sonnenbatterie-eco56_0.yaml b/templates/release/de/meter/sonnenbatterie-eco56_0.yaml deleted file mode 100644 index 7f7e19f87c..0000000000 --- a/templates/release/de/meter/sonnenbatterie-eco56_0.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Sonnen - description: comfort, eco 5, eco 6, oem 6.5 -render: - - usage: grid - default: | - type: template - template: sonnenbatterie-eco56 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 7979 # Port, optional - advanced: | - type: template - template: sonnenbatterie-eco56 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 7979 # Port, optional - cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - - usage: pv - default: | - type: template - template: sonnenbatterie-eco56 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 7979 # Port, optional - advanced: | - type: template - template: sonnenbatterie-eco56 - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 7979 # Port, optional - cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - - usage: battery - default: | - type: template - template: sonnenbatterie-eco56 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 7979 # Port, optional - advanced: | - type: template - template: sonnenbatterie-eco56 - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 7979 # Port, optional - capacity: 50 # Akkukapazität (kWh), optional - maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - cache: 5s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/meter/sonnenbatterie_0.yaml b/templates/release/de/meter/sonnenbatterie_0.yaml deleted file mode 100644 index 5b0735b29d..0000000000 --- a/templates/release/de/meter/sonnenbatterie_0.yaml +++ /dev/null @@ -1,54 +0,0 @@ -product: - brand: Sonnen - description: sonnenBatterie -capabilities: ["battery-control"] -description: | - Für die aktive Batteriesteuerung muss über das Webinterface der sonnenBatterie (unter Software-Integration) das "JSON Write API" aktiviert und das dort generierte API-Token in der Batteriekonfiguration unter `token` eingetragen werden. - Als Betriebsart der sonnenBatterie werden die beiden Modi "Eigenverbrauch" (Standard) und "Time-of-use" unterstützt. Der Modus kann über den Parameter `defaultmode` an die Konfiguration der sonnenBatterie angepasst werden. - Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBatterie über den Parameter `maxchargepower` angepasst werden. - -render: - - usage: grid - default: | - type: template - template: sonnenbatterie - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - advanced: | - type: template - template: sonnenbatterie - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - - usage: pv - default: | - type: template - template: sonnenbatterie - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - advanced: | - type: template - template: sonnenbatterie - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - - usage: battery - default: | - type: template - template: sonnenbatterie - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional) - advanced: | - type: template - template: sonnenbatterie - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional) - capacity: 50 # Akkukapazität (kWh), optional - maxchargepower: 3300 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - defaultmode: self-consumption # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. [self-consumption, time-of-use] diff --git a/templates/release/de/meter/st-ems.yaml b/templates/release/de/meter/st-ems.yaml new file mode 100644 index 0000000000..cbc6161fe6 --- /dev/null +++ b/templates/release/de/meter/st-ems.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: st-ems + brand: St-ems +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/steca-coolcept-flex.yaml b/templates/release/de/meter/steca-coolcept-flex.yaml new file mode 100644 index 0000000000..a63ed7e1af --- /dev/null +++ b/templates/release/de/meter/steca-coolcept-flex.yaml @@ -0,0 +1,22 @@ +template: kostal-piko-mp-plus +product: + identifier: steca-coolcept-flex + brand: Steca + description: coolcept fleX +render: + - usage: pv + default: | + type: template + template: kostal-piko-mp-plus + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/storaxe_0.yaml b/templates/release/de/meter/storaxe_0.yaml deleted file mode 100644 index 6a93bdd4fb..0000000000 --- a/templates/release/de/meter/storaxe_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Ads-tec - description: StoraXe -render: - - usage: battery - default: | - type: template - template: storaxe - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: storaxe - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/sungrow-hybrid_0.yaml b/templates/release/de/meter/sungrow-hybrid_0.yaml deleted file mode 100644 index c8e5ddc054..0000000000 --- a/templates/release/de/meter/sungrow-hybrid_0.yaml +++ /dev/null @@ -1,157 +0,0 @@ -product: - brand: Sungrow - description: SH Series Hybrid Inverter -capabilities: ["battery-control"] -description: | - Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktueller Firmware. Ältere Versionen liefern nicht alle benötigten Daten (Leistung, Ladestand). -render: - - usage: grid - default: | - type: template - template: sungrow-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: sungrow-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - - usage: pv - default: | - type: template - template: sungrow-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: sungrow-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: sungrow-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: sungrow-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Zeitüberschreitung, optional - capacity: 50 # Akkukapazität (kWh), optional - maxchargepower: # Maximale Ladeleistung (W), Maximale Ladeleistung für erzwungenes Laden des Speichers in Watt. (0 um automatisch den Wert der maximalen BDC-Nennleistung einzustellen) (optional) diff --git a/templates/release/de/meter/sungrow-inverter_0.yaml b/templates/release/de/meter/sungrow-inverter_0.yaml deleted file mode 100644 index 3bc755a5b5..0000000000 --- a/templates/release/de/meter/sungrow-inverter_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Sungrow - description: SG Series Inverter -render: - - usage: grid - default: | - type: template - template: sungrow-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sungrow-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sungrow-sg-series-inverter.yaml b/templates/release/de/meter/sungrow-sg-series-inverter.yaml new file mode 100644 index 0000000000..5616956caf --- /dev/null +++ b/templates/release/de/meter/sungrow-sg-series-inverter.yaml @@ -0,0 +1,74 @@ +template: sungrow-inverter +product: + identifier: sungrow-sg-series-inverter + brand: Sungrow + description: SG Series Inverter +render: + - usage: grid + default: | + type: template + template: sungrow-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sungrow-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml b/templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..d9153452b0 --- /dev/null +++ b/templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml @@ -0,0 +1,215 @@ +template: sungrow-hybrid +product: + identifier: sungrow-sh-series-hybrid-inverter + brand: Sungrow + description: SH Series Hybrid Inverter +capabilities: ["battery-control"] +description: | + Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktueller Firmware. Ältere Versionen liefern nicht alle benötigten Daten (Leistung, Ladestand). +render: + - usage: grid + default: | + type: template + template: sungrow-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: sungrow-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + - usage: pv + default: | + type: template + template: sungrow-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: sungrow-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: sungrow-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: sungrow-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Zeitüberschreitung, optional + capacity: 50 # Akkukapazität (kWh), optional + maxchargepower: # Maximale Ladeleistung (W), Maximale Ladeleistung für erzwungenes Laden des Speichers in Watt. (0 um automatisch den Wert der maximalen BDC-Nennleistung einzustellen) (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximale Ladeleistung + help: Maximale Ladeleistung für erzwungenes Laden des Speichers in Watt. (0 um automatisch den Wert der maximalen BDC-Nennleistung einzustellen) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunspec-battery-control_0.yaml b/templates/release/de/meter/sunspec-battery-control_0.yaml deleted file mode 100644 index 893b81ef31..0000000000 --- a/templates/release/de/meter/sunspec-battery-control_0.yaml +++ /dev/null @@ -1,55 +0,0 @@ -product: - description: SunSpec Batterie (Model 802) - group: Generische Unterstützung -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sunspec-battery-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-battery-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/sunspec-battery-model-124.yaml b/templates/release/de/meter/sunspec-battery-model-124.yaml new file mode 100644 index 0000000000..81ce04bb59 --- /dev/null +++ b/templates/release/de/meter/sunspec-battery-model-124.yaml @@ -0,0 +1,94 @@ +template: sunspec-inverter-control +product: + identifier: sunspec-battery-model-124 + description: SunSpec Batterie (Model 124) + group: Generische Unterstützung +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sunspec-inverter-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximale Ladeleistung + help: Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunspec-battery-model-802.yaml b/templates/release/de/meter/sunspec-battery-model-802.yaml new file mode 100644 index 0000000000..9852433270 --- /dev/null +++ b/templates/release/de/meter/sunspec-battery-model-802.yaml @@ -0,0 +1,104 @@ +template: sunspec-battery-control +product: + identifier: sunspec-battery-model-802 + description: SunSpec Batterie (Model 802) + group: Generische Unterstützung +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sunspec-battery-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-battery-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunspec-hybrid-inverter.yaml b/templates/release/de/meter/sunspec-hybrid-inverter.yaml new file mode 100644 index 0000000000..26d7635bdd --- /dev/null +++ b/templates/release/de/meter/sunspec-hybrid-inverter.yaml @@ -0,0 +1,187 @@ +template: sunspec-hybrid +product: + identifier: sunspec-hybrid-inverter + description: SunSpec Hybridwechselrichter + group: Generische Unterstützung +render: + - usage: grid + default: | + type: template + template: sunspec-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: sunspec-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunspec-hybrid_0.yaml b/templates/release/de/meter/sunspec-hybrid_0.yaml deleted file mode 100644 index 56fc6b6d08..0000000000 --- a/templates/release/de/meter/sunspec-hybrid_0.yaml +++ /dev/null @@ -1,147 +0,0 @@ -product: - description: SunSpec Hybridwechselrichter - group: Generische Unterstützung -render: - - usage: grid - default: | - type: template - template: sunspec-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - - usage: battery - default: | - type: template - template: sunspec-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/sunspec-inverter-control_0.yaml b/templates/release/de/meter/sunspec-inverter-control_0.yaml deleted file mode 100644 index 0cac73304d..0000000000 --- a/templates/release/de/meter/sunspec-inverter-control_0.yaml +++ /dev/null @@ -1,54 +0,0 @@ -product: - description: SunSpec Batterie (Model 124) - group: Generische Unterstützung -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sunspec-inverter-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/sunspec-inverter.yaml b/templates/release/de/meter/sunspec-inverter.yaml new file mode 100644 index 0000000000..ffcfa39f00 --- /dev/null +++ b/templates/release/de/meter/sunspec-inverter.yaml @@ -0,0 +1,177 @@ +template: sunspec-inverter +product: + identifier: sunspec-inverter + description: SunSpec Wechselrichter + group: Generische Unterstützung +render: + - usage: grid + default: | + type: template + template: sunspec-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sunspec-inverter + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunspec-inverter_0.yaml b/templates/release/de/meter/sunspec-inverter_0.yaml deleted file mode 100644 index 821d3f3d1e..0000000000 --- a/templates/release/de/meter/sunspec-inverter_0.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - description: SunSpec Wechselrichter - group: Generische Unterstützung -render: - - usage: grid - default: | - type: template - template: sunspec-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sunspec-inverter - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/sunspec-meter.yaml b/templates/release/de/meter/sunspec-meter.yaml new file mode 100644 index 0000000000..dcfe6f9db0 --- /dev/null +++ b/templates/release/de/meter/sunspec-meter.yaml @@ -0,0 +1,43 @@ +template: sunspec-meter +product: + identifier: sunspec-meter + description: SunSpec Zähler +render: + - usage: grid + default: | + type: template + template: sunspec-meter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-meter + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunspec-meter_0.yaml b/templates/release/de/meter/sunspec-meter_0.yaml deleted file mode 100644 index 4e1856e3c1..0000000000 --- a/templates/release/de/meter/sunspec-meter_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: SunSpec Zähler -render: - - usage: grid - default: | - type: template - template: sunspec-meter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-meter - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sunspec-meter_1.yaml b/templates/release/de/meter/sunspec-meter_1.yaml deleted file mode 100644 index fad003856a..0000000000 --- a/templates/release/de/meter/sunspec-meter_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Fronius - description: Smartmeter (über Wechselrichter) -render: - - usage: grid - default: | - type: template - template: sunspec-meter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-meter - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml b/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml new file mode 100644 index 0000000000..294c2c5e24 --- /dev/null +++ b/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: deye-hybrid-3p +product: + identifier: sunsynk-3p-hybrid-inverter + brand: Sunsynk + description: 3p hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + - usage: battery + default: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml b/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml new file mode 100644 index 0000000000..d713276792 --- /dev/null +++ b/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml @@ -0,0 +1,236 @@ +template: deye-hybrid-hp3 +product: + identifier: sunsynk-hp3-hybrid-inverter + brand: Sunsynk + description: hp3 hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional + - usage: pv + default: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional + - usage: battery + default: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: includegenport + example: + default: + choice: [] + unit: + description: GEN-Anschluss als Solar-Eingang verwenden + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunsynk-micro-inverter.yaml b/templates/release/de/meter/sunsynk-micro-inverter.yaml new file mode 100644 index 0000000000..69b8cde633 --- /dev/null +++ b/templates/release/de/meter/sunsynk-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: sunsynk-micro-inverter + brand: Sunsynk + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml b/templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml new file mode 100644 index 0000000000..8a9e93a574 --- /dev/null +++ b/templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: deye-storage +product: + identifier: sunsynk-storage-hybrid-inverter + brand: Sunsynk + description: Storage (hybrid) inverter +render: + - usage: pv + default: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + - usage: grid + default: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunsynk-string-inverter.yaml b/templates/release/de/meter/sunsynk-string-inverter.yaml new file mode 100644 index 0000000000..ed15c76121 --- /dev/null +++ b/templates/release/de/meter/sunsynk-string-inverter.yaml @@ -0,0 +1,50 @@ +template: deye-string +product: + identifier: sunsynk-string-inverter + brand: Sunsynk + description: String inverter +render: + - usage: pv + default: | + type: template + template: deye-string + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/sunway.yaml b/templates/release/de/meter/sunway.yaml new file mode 100644 index 0000000000..6e6d696f8a --- /dev/null +++ b/templates/release/de/meter/sunway.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: sunway + brand: Sunway +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/tapo_0.yaml b/templates/release/de/meter/tapo_0.yaml deleted file mode 100644 index 41d94d8994..0000000000 --- a/templates/release/de/meter/tapo_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: TP-Link - description: Tapo P-Series Smart Plug - group: Schaltbare Steckdosen -render: - - usage: pv - default: | - type: template - template: tapo - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen diff --git a/templates/release/de/meter/tasmota-3p_0.yaml b/templates/release/de/meter/tasmota-3p_0.yaml deleted file mode 100644 index 319c76ecc4..0000000000 --- a/templates/release/de/meter/tasmota-3p_0.yaml +++ /dev/null @@ -1,39 +0,0 @@ -product: - brand: Tasmota - description: dreiphasig - group: Schaltbare Steckdosen -description: | - Kanäle 1,2,3 müssen verwendet werden. -render: - - usage: grid - default: | - type: template - template: tasmota-3p - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: tasmota-3p - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: battery - default: | - type: template - template: tasmota-3p - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: charge - default: | - type: template - template: tasmota-3p - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml b/templates/release/de/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml new file mode 100644 index 0000000000..8e270d6470 --- /dev/null +++ b/templates/release/de/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml @@ -0,0 +1,91 @@ +template: tasmota-sml +product: + identifier: tasmota-sml-ir-reader-for-smartmeters-e-g-hichi + brand: Tasmota + description: SML IR-Lesekopf für smarte Stromzähler bspw Hichi +description: | + Um die Werte des Smartmeters für evcc korrekt auslesen zu können, muss das Lesekopf-Script so geändert werden, dass folgende JSON-Tags erzeugt werden: + - **SML** als Gruppenname der ausgelesenen Parameter + - **Total_in** für den Gesamtverbrauch in KWh (4 Nachkommastellen) + - **Total_out** für den Gesamteinspeisung in KWh mit (4 Nachkommastellen) + - **Power_curr** für den aktuellen Verbrauch bzw. die aktuelle Einspeisung (0 Nachkommastellen) + + Ein entsprechendes Lesekopf-Script sieht wie folgt aus: + ``` + >D + >B + =>sensor53 r + >M 1 + // highlight-next-line + +1,3,s,16,9600,SML + // highlight-next-line + 1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 + // highlight-next-line + 1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 + // highlight-next-line + 1,77070100100700ff@1,Verbrauch,W,Power_curr,0 + 1,77070100600100ff@#,Zählernummer,,Meter_Id,0 + # + ``` + +render: + - usage: grid + default: | + type: template + template: tasmota-sml + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: pv + default: | + type: template + template: tasmota-sml + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: battery + default: | + type: template + template: tasmota-sml + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: charge + default: | + type: template + template: tasmota-sml + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Standard-User ist admin + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/tasmota-sml_0.yaml b/templates/release/de/meter/tasmota-sml_0.yaml deleted file mode 100644 index bb5ae33455..0000000000 --- a/templates/release/de/meter/tasmota-sml_0.yaml +++ /dev/null @@ -1,61 +0,0 @@ -product: - brand: Tasmota - description: SML IR-Lesekopf für smarte Stromzähler bspw Hichi -description: | - Um die Werte des Smartmeters für evcc korrekt auslesen zu können, muss das Lesekopf-Script so geändert werden, dass folgende JSON-Tags erzeugt werden: - - **SML** als Gruppenname der ausgelesenen Parameter - - **Total_in** für den Gesamtverbrauch in KWh (4 Nachkommastellen) - - **Total_out** für den Gesamteinspeisung in KWh mit (4 Nachkommastellen) - - **Power_curr** für den aktuellen Verbrauch bzw. die aktuelle Einspeisung (0 Nachkommastellen) - - Ein entsprechendes Lesekopf-Script sieht wie folgt aus: - ``` - >D - >B - =>sensor53 r - >M 1 - // highlight-next-line - +1,3,s,16,9600,SML - // highlight-next-line - 1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 - // highlight-next-line - 1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 - // highlight-next-line - 1,77070100100700ff@1,Verbrauch,W,Power_curr,0 - 1,77070100600100ff@#,Zählernummer,,Meter_Id,0 - # - ``` - -render: - - usage: grid - default: | - type: template - template: tasmota-sml - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: pv - default: | - type: template - template: tasmota-sml - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: battery - default: | - type: template - template: tasmota-sml - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - - usage: charge - default: | - type: template - template: tasmota-sml - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml b/templates/release/de/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml new file mode 100644 index 0000000000..002558a062 --- /dev/null +++ b/templates/release/de/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml @@ -0,0 +1,80 @@ +template: tasmota +product: + identifier: tasmota-tasmota-1-phase-plus-sml-meter + brand: Tasmota + description: Tasmota (1 Phase + SML Meter) + group: Schaltbare Steckdosen +render: + - usage: grid + default: | + type: template + template: tasmota + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 1 # Kanal Nummer, Meterkanal (1-8) + - usage: pv + default: | + type: template + template: tasmota + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 1 # Kanal Nummer, Meterkanal (1-8) + - usage: battery + default: | + type: template + template: tasmota + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 1 # Kanal Nummer, Meterkanal (1-8) + - usage: charge + default: | + type: template + template: tasmota + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 1 # Kanal Nummer, Meterkanal (1-8) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Standard-User ist admin + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true + - name: channel + example: + default: 1 + choice: [] + unit: + description: Kanal Nummer + help: Meterkanal (1-8) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/tasmota-three-phase.yaml b/templates/release/de/meter/tasmota-three-phase.yaml new file mode 100644 index 0000000000..07916271ec --- /dev/null +++ b/templates/release/de/meter/tasmota-three-phase.yaml @@ -0,0 +1,69 @@ +template: tasmota-3p +product: + identifier: tasmota-three-phase + brand: Tasmota + description: dreiphasig + group: Schaltbare Steckdosen +description: | + Kanäle 1,2,3 müssen verwendet werden. +render: + - usage: grid + default: | + type: template + template: tasmota-3p + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: pv + default: | + type: template + template: tasmota-3p + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: battery + default: | + type: template + template: tasmota-3p + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + - usage: charge + default: | + type: template + template: tasmota-3p + usage: charge + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, Standard-User ist admin (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: Standard-User ist admin + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/tasmota_0.yaml b/templates/release/de/meter/tasmota_0.yaml deleted file mode 100644 index 3744be7893..0000000000 --- a/templates/release/de/meter/tasmota_0.yaml +++ /dev/null @@ -1,41 +0,0 @@ -product: - brand: Tasmota - description: Tasmota (1 Phase + SML Meter) - group: Schaltbare Steckdosen -render: - - usage: grid - default: | - type: template - template: tasmota - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 1 # Kanal Nummer, Meterkanal (1-8) - - usage: pv - default: | - type: template - template: tasmota - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 1 # Kanal Nummer, Meterkanal (1-8) - - usage: battery - default: | - type: template - template: tasmota - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 1 # Kanal Nummer, Meterkanal (1-8) - - usage: charge - default: | - type: template - template: tasmota - usage: charge - host: 192.0.2.2 # IP-Adresse oder Hostname - user: # Benutzerkonto, Standard-User ist admin (optional) - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 1 # Kanal Nummer, Meterkanal (1-8) diff --git a/templates/release/de/meter/tesla-powerwall.yaml b/templates/release/de/meter/tesla-powerwall.yaml new file mode 100644 index 0000000000..fef95c3956 --- /dev/null +++ b/templates/release/de/meter/tesla-powerwall.yaml @@ -0,0 +1,127 @@ +template: tesla-powerwall +product: + identifier: tesla-powerwall + brand: Tesla + description: Powerwall +capabilities: ["battery-control"] +description: | + Um die optionale Entladesteuerung der Battery zu nutzen wird ein `refresh` Token für die Kommunikation mit der Tesla API benötigt. + + Folgende Apps ermöglichen das Erstellen des Tokens: + - [Auth app for Tesla (iOS)](https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613#?platform=iphone) + - [Tesla Tokens (Android)](https://play.google.com/store/apps/details?id=net.leveugle.teslatokens) + - [Tesla Auth (macOS, Linux)](https://github.com/adriankumpf/tesla_auth) + +render: + - usage: grid + default: | + type: template + template: tesla-powerwall + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. + refreshToken: # optional + siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + advanced: | + type: template + template: tesla-powerwall + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. + refreshToken: # optional + siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: tesla-powerwall + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. + refreshToken: # optional + siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + advanced: | + type: template + template: tesla-powerwall + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. + refreshToken: # optional + siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: battery + default: | + type: template + template: tesla-powerwall + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. + refreshToken: # optional + siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + advanced: | + type: template + template: tesla-powerwall + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. + refreshToken: # optional + siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: siteId + example: + default: + choice: [] + unit: + description: + help: optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung + advanced: false + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/tesla-powerwall_0.yaml b/templates/release/de/meter/tesla-powerwall_0.yaml deleted file mode 100644 index 0cbb9a7b12..0000000000 --- a/templates/release/de/meter/tesla-powerwall_0.yaml +++ /dev/null @@ -1,70 +0,0 @@ -product: - brand: Tesla - description: Powerwall -capabilities: ["battery-control"] -description: | - Um die optionale Entladesteuerung der Battery zu nutzen wird ein `refresh` Token für die Kommunikation mit der Tesla API benötigt. - - Folgende Apps ermöglichen das Erstellen des Tokens: - - [Auth app for Tesla (iOS)](https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613#?platform=iphone) - - [Tesla Tokens (Android)](https://play.google.com/store/apps/details?id=net.leveugle.teslatokens) - - [Tesla Auth (macOS, Linux)](https://github.com/adriankumpf/tesla_auth) - -render: - - usage: grid - default: | - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - advanced: | - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - advanced: | - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: battery - default: | - type: template - template: tesla-powerwall - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - advanced: | - type: template - template: tesla-powerwall - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/thor_0.yaml b/templates/release/de/meter/thor_0.yaml deleted file mode 100644 index 0c93f82c08..0000000000 --- a/templates/release/de/meter/thor_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: my-PV - description: AC•THOR -render: - - usage: aux - default: | - type: template - template: thor - usage: aux - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/tibber-pulse.yaml b/templates/release/de/meter/tibber-pulse.yaml new file mode 100644 index 0000000000..a81ed20044 --- /dev/null +++ b/templates/release/de/meter/tibber-pulse.yaml @@ -0,0 +1,33 @@ +template: tibber-pulse +product: + identifier: tibber-pulse + brand: Tibber + description: Pulse +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: tibber-pulse + usage: grid + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional +params: + - name: token + example: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: homeid + example: 96a14971-525a-4420-aae9-e5aedaa129ff + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/tibber-pulse_0.yaml b/templates/release/de/meter/tibber-pulse_0.yaml deleted file mode 100644 index 6da33b3f35..0000000000 --- a/templates/release/de/meter/tibber-pulse_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Tibber - description: Pulse -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: tibber-pulse - usage: grid - token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE - homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional diff --git a/templates/release/de/meter/tp-link-h-series-smart-plug.yaml b/templates/release/de/meter/tp-link-h-series-smart-plug.yaml new file mode 100644 index 0000000000..5a8e959788 --- /dev/null +++ b/templates/release/de/meter/tp-link-h-series-smart-plug.yaml @@ -0,0 +1,23 @@ +template: tplink +product: + identifier: tp-link-h-series-smart-plug + brand: TP-Link + description: H-Series Smart Plug + group: Schaltbare Steckdosen +render: + - usage: pv + default: | + type: template + template: tplink + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/tp-link-tapo-p-series-smart-plug.yaml b/templates/release/de/meter/tp-link-tapo-p-series-smart-plug.yaml new file mode 100644 index 0000000000..a84c861e43 --- /dev/null +++ b/templates/release/de/meter/tp-link-tapo-p-series-smart-plug.yaml @@ -0,0 +1,43 @@ +template: tapo +product: + identifier: tp-link-tapo-p-series-smart-plug + brand: TP-Link + description: Tapo P-Series Smart Plug + group: Schaltbare Steckdosen +render: + - usage: pv + default: | + type: template + template: tapo + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/tplink_0.yaml b/templates/release/de/meter/tplink_0.yaml deleted file mode 100644 index e7b9fde4e8..0000000000 --- a/templates/release/de/meter/tplink_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: TP-Link - description: H-Series Smart Plug - group: Schaltbare Steckdosen -render: - - usage: pv - default: | - type: template - template: tplink - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/tq-em420_0.yaml b/templates/release/de/meter/tq-em420_0.yaml deleted file mode 100644 index b6d0652b66..0000000000 --- a/templates/release/de/meter/tq-em420_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: TQ - description: Energy Manager EM420 -render: - - usage: grid - default: | - type: template - template: tq-em420 - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 80 # Port, optional - device: local # API Gerätepfad, JSON-Schnittstelle -> Datenendpunkt (optional) - token: ey... # Accesstoken, Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel) diff --git a/templates/release/de/meter/tq-em_0.yaml b/templates/release/de/meter/tq-em_0.yaml deleted file mode 100644 index 8f9d89f923..0000000000 --- a/templates/release/de/meter/tq-em_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: TQ - description: Energy Manager EM2xx/EM3xx -render: - - usage: grid - default: | - type: template - template: tq-em - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 80 # Port, optional - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) diff --git a/templates/release/de/meter/tq-energy-manager-em2xx-em3xx.yaml b/templates/release/de/meter/tq-energy-manager-em2xx-em3xx.yaml new file mode 100644 index 0000000000..321ca257f5 --- /dev/null +++ b/templates/release/de/meter/tq-energy-manager-em2xx-em3xx.yaml @@ -0,0 +1,42 @@ +template: tq-em +product: + identifier: tq-energy-manager-em2xx-em3xx + brand: TQ + description: Energy Manager EM2xx/EM3xx +render: + - usage: grid + default: | + type: template + template: tq-em + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 80 # Port, optional + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 80 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/tq-energy-manager-em420.yaml b/templates/release/de/meter/tq-energy-manager-em420.yaml new file mode 100644 index 0000000000..2487758691 --- /dev/null +++ b/templates/release/de/meter/tq-energy-manager-em420.yaml @@ -0,0 +1,52 @@ +template: tq-em420 +product: + identifier: tq-energy-manager-em420 + brand: TQ + description: Energy Manager EM420 +render: + - usage: grid + default: | + type: template + template: tq-em420 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 80 # Port, optional + device: local # API Gerätepfad, JSON-Schnittstelle -> Datenendpunkt (optional) + token: ey... # Accesstoken, Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 80 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: device + example: + default: local + choice: [] + unit: + description: API Gerätepfad + help: JSON-Schnittstelle -> Datenendpunkt + advanced: false + optional: true + - name: token + example: ey... + default: + choice: [] + unit: + description: Accesstoken + help: Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/varta-element.yaml b/templates/release/de/meter/varta-element.yaml new file mode 100644 index 0000000000..db5ff58ee2 --- /dev/null +++ b/templates/release/de/meter/varta-element.yaml @@ -0,0 +1,76 @@ +template: varta +product: + identifier: varta-element + brand: VARTA + description: element +description: | + PV nur verfügbar mit PV-Sensor +render: + - usage: grid + default: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + - usage: battery + default: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/varta-pulse-neo.yaml b/templates/release/de/meter/varta-pulse-neo.yaml new file mode 100644 index 0000000000..2cfdefb491 --- /dev/null +++ b/templates/release/de/meter/varta-pulse-neo.yaml @@ -0,0 +1,76 @@ +template: varta +product: + identifier: varta-pulse-neo + brand: VARTA + description: pulse neo +description: | + PV nur verfügbar mit PV-Sensor +render: + - usage: grid + default: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + - usage: battery + default: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/varta-pulse.yaml b/templates/release/de/meter/varta-pulse.yaml new file mode 100644 index 0000000000..f3af3a7101 --- /dev/null +++ b/templates/release/de/meter/varta-pulse.yaml @@ -0,0 +1,76 @@ +template: varta +product: + identifier: varta-pulse + brand: VARTA + description: pulse +description: | + PV nur verfügbar mit PV-Sensor +render: + - usage: grid + default: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + - usage: battery + default: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/varta_0.yaml b/templates/release/de/meter/varta_0.yaml deleted file mode 100644 index 1a260fd1b0..0000000000 --- a/templates/release/de/meter/varta_0.yaml +++ /dev/null @@ -1,46 +0,0 @@ -product: - brand: VARTA - description: pulse, pulse neo, element -description: | - PV nur verfügbar mit PV-Sensor -render: - - usage: grid - default: | - type: template - template: varta - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: varta - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - - usage: pv - default: | - type: template - template: varta - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: varta - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - - usage: battery - default: | - type: template - template: varta - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: varta - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - capacity: 50 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/victron-em24.yaml b/templates/release/de/meter/victron-em24.yaml new file mode 100644 index 0000000000..9afe506784 --- /dev/null +++ b/templates/release/de/meter/victron-em24.yaml @@ -0,0 +1,64 @@ +template: cg-em24 +product: + identifier: victron-em24 + brand: Victron + description: EM24 +description: | + EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. + +render: + - usage: grid + default: | + type: template + template: cg-em24 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/victron-em24_e1.yaml b/templates/release/de/meter/victron-em24_e1.yaml new file mode 100644 index 0000000000..e4d65fa572 --- /dev/null +++ b/templates/release/de/meter/victron-em24_e1.yaml @@ -0,0 +1,48 @@ +template: cg-em24_e1 +product: + identifier: victron-em24_e1 + brand: Victron + description: EM24_E1 +description: | + EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. + Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + +render: + - usage: grid + default: | + type: template + template: cg-em24_e1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24_e1 + usage: charge + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/victron-em530-em540.yaml b/templates/release/de/meter/victron-em530-em540.yaml new file mode 100644 index 0000000000..57fc28e720 --- /dev/null +++ b/templates/release/de/meter/victron-em530-em540.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: victron-em530-em540 + brand: Victron + description: EM530/EM540 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/victron-energy.yaml b/templates/release/de/meter/victron-energy.yaml new file mode 100644 index 0000000000..ee5827d500 --- /dev/null +++ b/templates/release/de/meter/victron-energy.yaml @@ -0,0 +1,122 @@ +template: victron-energy +product: + identifier: victron-energy + brand: Victron + description: Energy +capabilities: ["battery-control"] +description: | + Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt werden soll. +render: + - usage: grid + default: | + type: template + template: victron-energy + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) + advanced: | + type: template + template: victron-energy + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: pv + default: | + type: template + template: victron-energy + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: victron-energy + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + - usage: battery + default: | + type: template + template: victron-energy + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + advanced: | + type: template + template: victron-energy + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + capacity: 50 # Akkukapazität (kWh), optional + minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: meterid + example: + default: + choice: [] + unit: + description: + help: Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximale AC Leistung des Hybrid-Wechselrichters + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximaler Ladestand + help: Oberes Limit beim Laden der Batterie aus dem Netz + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/victron-energy_0.yaml b/templates/release/de/meter/victron-energy_0.yaml deleted file mode 100644 index ab70a35b9c..0000000000 --- a/templates/release/de/meter/victron-energy_0.yaml +++ /dev/null @@ -1,56 +0,0 @@ -product: - brand: Victron - description: Energy -capabilities: ["battery-control"] -description: | - Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt werden soll. -render: - - usage: grid - default: | - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) - advanced: | - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: pv - default: | - type: template - template: victron-energy - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: victron-energy - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - - usage: battery - default: | - type: template - template: victron-energy - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - advanced: | - type: template - template: victron-energy - usage: battery - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - capacity: 50 # Akkukapazität (kWh), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) diff --git a/templates/release/de/meter/victron-et340.yaml b/templates/release/de/meter/victron-et340.yaml new file mode 100644 index 0000000000..0f3d3b8836 --- /dev/null +++ b/templates/release/de/meter/victron-et340.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: victron-et340 + brand: Victron + description: ET340 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/volkszaehler-http_0.yaml b/templates/release/de/meter/volkszaehler-http_0.yaml deleted file mode 100644 index 52564aa2de..0000000000 --- a/templates/release/de/meter/volkszaehler-http_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Volkszähler - description: HTTP API - group: Generische Unterstützung -render: - - usage: grid - default: | - type: template - template: volkszaehler-http - usage: grid - url: # URL des "data" Kontexts der Volkszähler Middleware, Beispiel: http://zaehler.network.local:8080/api/data (optional) - uuid: diff --git a/templates/release/de/meter/volkszaehler-importexport_0.yaml b/templates/release/de/meter/volkszaehler-importexport_0.yaml deleted file mode 100644 index aa893ebdee..0000000000 --- a/templates/release/de/meter/volkszaehler-importexport_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Volkszähler - description: HTTP API, Import & Export - group: Generische Unterstützung -render: - - usage: grid - default: | - type: template - template: volkszaehler-importexport - usage: grid - url: # URL des "data" Kontexts der Volkszähler Middleware, Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data (optional) - importuuid: - exportuuid: diff --git a/templates/release/de/meter/volkszaehler-ws_0.yaml b/templates/release/de/meter/volkszaehler-ws_0.yaml deleted file mode 100644 index b5d795d4a0..0000000000 --- a/templates/release/de/meter/volkszaehler-ws_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Volkszähler - description: WebSocket API - group: Generische Unterstützung -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: volkszaehler-ws - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8082 # Port, optional - uuid: diff --git a/templates/release/de/meter/volkszahler-http-api-import-and-export.yaml b/templates/release/de/meter/volkszahler-http-api-import-and-export.yaml new file mode 100644 index 0000000000..b69b2f3e26 --- /dev/null +++ b/templates/release/de/meter/volkszahler-http-api-import-and-export.yaml @@ -0,0 +1,43 @@ +template: volkszaehler-importexport +product: + identifier: volkszahler-http-api-import-and-export + brand: Volkszähler + description: HTTP API, Import & Export + group: Generische Unterstützung +render: + - usage: grid + default: | + type: template + template: volkszaehler-importexport + usage: grid + url: # URL des "data" Kontexts der Volkszähler Middleware, Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data (optional) + importuuid: + exportuuid: +params: + - name: url + example: + default: + choice: [] + unit: + description: URL des "data" Kontexts der Volkszähler Middleware + help: 'Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data' + advanced: false + optional: true + - name: importuuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: exportuuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/volkszahler-http-api.yaml b/templates/release/de/meter/volkszahler-http-api.yaml new file mode 100644 index 0000000000..5e900f8251 --- /dev/null +++ b/templates/release/de/meter/volkszahler-http-api.yaml @@ -0,0 +1,33 @@ +template: volkszaehler-http +product: + identifier: volkszahler-http-api + brand: Volkszähler + description: HTTP API + group: Generische Unterstützung +render: + - usage: grid + default: | + type: template + template: volkszaehler-http + usage: grid + url: # URL des "data" Kontexts der Volkszähler Middleware, Beispiel: http://zaehler.network.local:8080/api/data (optional) + uuid: +params: + - name: url + example: + default: + choice: [] + unit: + description: URL des "data" Kontexts der Volkszähler Middleware + help: 'Beispiel: http://zaehler.network.local:8080/api/data' + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/volkszahler-websocket-api.yaml b/templates/release/de/meter/volkszahler-websocket-api.yaml new file mode 100644 index 0000000000..0aa20aac06 --- /dev/null +++ b/templates/release/de/meter/volkszahler-websocket-api.yaml @@ -0,0 +1,44 @@ +template: volkszaehler-ws +product: + identifier: volkszahler-websocket-api + brand: Volkszähler + description: WebSocket API + group: Generische Unterstützung +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: volkszaehler-ws + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8082 # Port, optional + uuid: +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8082 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/vzlogger.yaml b/templates/release/de/meter/vzlogger.yaml new file mode 100644 index 0000000000..0052aef453 --- /dev/null +++ b/templates/release/de/meter/vzlogger.yaml @@ -0,0 +1,159 @@ +template: vzlogger +product: + identifier: vzlogger + description: vzlogger + group: Generische Unterstützung +render: + - usage: grid + default: | + type: template + template: vzlogger + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8081 # Port, optional + uuid: + advanced: | + type: template + template: vzlogger + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8081 # Port, optional + uuid: + scale: 1 # Skalierungsfaktor, Multipliziere Rohwert mit diesem Faktor (optional) + l1currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0), optional + l2currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0), optional + l3currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0), optional + l1poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0), optional + l2poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0), optional + l3poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0), optional + l1voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0), optional + l2voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0), optional + l3voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0), optional + cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8081 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: scale + example: + default: 1 + choice: [] + unit: + description: Skalierungsfaktor + help: Multipliziere Rohwert mit diesem Faktor + advanced: true + optional: true + - name: l1currentuuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0) + help: + advanced: true + optional: true + - name: l2currentuuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0) + help: + advanced: true + optional: true + - name: l3currentuuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0) + help: + advanced: true + optional: true + - name: l1poweruuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0) + help: + advanced: true + optional: true + - name: l2poweruuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0) + help: + advanced: true + optional: true + - name: l3poweruuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0) + help: + advanced: true + optional: true + - name: l1voltageuuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0) + help: + advanced: true + optional: true + - name: l2voltageuuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0) + help: + advanced: true + optional: true + - name: l3voltageuuid + example: + default: + choice: [] + unit: + description: Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0) + help: + advanced: true + optional: true + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/vzlogger_0.yaml b/templates/release/de/meter/vzlogger_0.yaml deleted file mode 100644 index 9e31137f78..0000000000 --- a/templates/release/de/meter/vzlogger_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - description: vzlogger - group: Generische Unterstützung -render: - - usage: grid - default: | - type: template - template: vzlogger - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8081 # Port, optional - uuid: - advanced: | - type: template - template: vzlogger - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 8081 # Port, optional - uuid: - scale: 1 # Skalierungsfaktor, Multipliziere Rohwert mit diesem Faktor (optional) - l1currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0), optional - l2currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0), optional - l3currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0), optional - l1poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0), optional - l2poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0), optional - l3poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0), optional - l1voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0), optional - l2voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0), optional - l3voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0), optional - cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/meter/wago-879-30xx.yaml b/templates/release/de/meter/wago-879-30xx.yaml new file mode 100644 index 0000000000..9e3a3ece70 --- /dev/null +++ b/templates/release/de/meter/wago-879-30xx.yaml @@ -0,0 +1,61 @@ +template: wago-879-30xx +product: + identifier: wago-879-30xx + brand: Wago + description: 879-30xx +render: + - usage: grid + default: | + type: template + template: wago-879-30xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: wago-879-30xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/wago-879-30xx_0.yaml b/templates/release/de/meter/wago-879-30xx_0.yaml deleted file mode 100644 index 4b3f34dd35..0000000000 --- a/templates/release/de/meter/wago-879-30xx_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Wago - description: 879-30xx -render: - - usage: grid - default: | - type: template - template: wago-879-30xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: wago-879-30xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/de/meter/wattsonic.yaml b/templates/release/de/meter/wattsonic.yaml new file mode 100644 index 0000000000..30cae19580 --- /dev/null +++ b/templates/release/de/meter/wattsonic.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: wattsonic + brand: Wattsonic +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/wattsonic_0.yaml b/templates/release/de/meter/wattsonic_0.yaml deleted file mode 100644 index bedbb12042..0000000000 --- a/templates/release/de/meter/wattsonic_0.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: Wattsonic -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional diff --git a/templates/release/de/meter/wattsonic_1.yaml b/templates/release/de/meter/wattsonic_1.yaml deleted file mode 100644 index 8327b94177..0000000000 --- a/templates/release/de/meter/wattsonic_1.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: Sunway -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional diff --git a/templates/release/de/meter/wattsonic_2.yaml b/templates/release/de/meter/wattsonic_2.yaml deleted file mode 100644 index 418d78c2fa..0000000000 --- a/templates/release/de/meter/wattsonic_2.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: Solinteng -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional diff --git a/templates/release/de/meter/wattsonic_3.yaml b/templates/release/de/meter/wattsonic_3.yaml deleted file mode 100644 index da31402d45..0000000000 --- a/templates/release/de/meter/wattsonic_3.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: A-Tronix -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional diff --git a/templates/release/de/meter/wattsonic_4.yaml b/templates/release/de/meter/wattsonic_4.yaml deleted file mode 100644 index 779a7375a0..0000000000 --- a/templates/release/de/meter/wattsonic_4.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: St-ems -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional diff --git a/templates/release/de/meter/weidmuller-em110-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em110-rtu-2p.yaml new file mode 100644 index 0000000000..e5d38d0886 --- /dev/null +++ b/templates/release/de/meter/weidmuller-em110-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm220_230 +product: + identifier: weidmuller-em110-rtu-2p + brand: Weidmüller + description: EM110-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron-sdm220_230 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm220_230 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/weidmuller-em111-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em111-rtu-2p.yaml new file mode 100644 index 0000000000..07c0b80e23 --- /dev/null +++ b/templates/release/de/meter/weidmuller-em111-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm220_230 +product: + identifier: weidmuller-em111-rtu-2p + brand: Weidmüller + description: EM111-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron-sdm220_230 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm220_230 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/weidmuller-em120-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em120-rtu-2p.yaml new file mode 100644 index 0000000000..b1cb3fc002 --- /dev/null +++ b/templates/release/de/meter/weidmuller-em120-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: weidmuller-em120-rtu-2p + brand: Weidmüller + description: EM120-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/weidmuller-em122-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em122-rtu-2p.yaml new file mode 100644 index 0000000000..415863aac2 --- /dev/null +++ b/templates/release/de/meter/weidmuller-em122-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: weidmuller-em122-rtu-2p + brand: Weidmüller + description: EM122-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/youless-energy-monitor.yaml b/templates/release/de/meter/youless-energy-monitor.yaml new file mode 100644 index 0000000000..46ea113252 --- /dev/null +++ b/templates/release/de/meter/youless-energy-monitor.yaml @@ -0,0 +1,31 @@ +template: youless +product: + identifier: youless-energy-monitor + brand: Youless + description: Energy Monitor +description: | + Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszähler benötigt. + +render: + - usage: grid + default: | + type: template + template: youless + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + - usage: pv + default: | + type: template + template: youless + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/youless_0.yaml b/templates/release/de/meter/youless_0.yaml deleted file mode 100644 index 7753a7cd15..0000000000 --- a/templates/release/de/meter/youless_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Youless - description: Energy Monitor -description: | - Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszähler benötigt. - -render: - - usage: grid - default: | - type: template - template: youless - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - - usage: pv - default: | - type: template - template: youless - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname diff --git a/templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml b/templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml new file mode 100644 index 0000000000..3afd3d3dcc --- /dev/null +++ b/templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: zcs-azzurro-hybrid-inverter + brand: ZCS Azzurro + description: Hybrid Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/zcs-azzurro-inverter.yaml b/templates/release/de/meter/zcs-azzurro-inverter.yaml new file mode 100644 index 0000000000..deb238c7c5 --- /dev/null +++ b/templates/release/de/meter/zcs-azzurro-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: zcs-azzurro-inverter + brand: ZCS Azzurro + description: Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/de/meter/zendure-hyper-2000.yaml b/templates/release/de/meter/zendure-hyper-2000.yaml new file mode 100644 index 0000000000..c950cc883f --- /dev/null +++ b/templates/release/de/meter/zendure-hyper-2000.yaml @@ -0,0 +1,88 @@ +template: zendure +product: + identifier: zendure-hyper-2000 + brand: Zendure + description: Hyper 2000 +requirements: ["skiptest"] +render: + - usage: pv + default: | + type: template + template: zendure + usage: pv + account: dev@zendure.com + serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # [EU, Global] + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: zendure + usage: pv + account: dev@zendure.com + serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # [EU, Global] + timeout: 10s # Zeitüberschreitung, optional + - usage: battery + default: | + type: template + template: zendure + usage: battery + account: dev@zendure.com + serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # [EU, Global] + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: zendure + usage: battery + account: dev@zendure.com + serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # [EU, Global] + timeout: 10s # Zeitüberschreitung, optional + capacity: 2 # Akkukapazität (kWh), optional +params: + - name: account + example: dev@zendure.com + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: serial + example: VU5D99F74021B04 + default: + choice: [] + unit: + description: + help: Zu finden in der Zendure App in den Einstellungen des Geräts + advanced: false + optional: false + - name: region + example: + default: EU + choice: ['EU', 'Global'] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: 2 + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/meter/zendure_0.yaml b/templates/release/de/meter/zendure_0.yaml deleted file mode 100644 index 7369b2ed70..0000000000 --- a/templates/release/de/meter/zendure_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Zendure - description: Hyper 2000 -requirements: ["skiptest"] -render: - - usage: pv - default: | - type: template - template: zendure - usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: zendure - usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] - timeout: 10s # Zeitüberschreitung, optional - - usage: battery - default: | - type: template - template: zendure - usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: zendure - usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] - timeout: 10s # Zeitüberschreitung, optional - capacity: 2 # Akkukapazität (kWh), optional diff --git a/templates/release/de/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml b/templates/release/de/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml new file mode 100644 index 0000000000..9f36a7b431 --- /dev/null +++ b/templates/release/de/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml @@ -0,0 +1,24 @@ +template: slimmelezer-luxembourg +product: + identifier: zuidwijk-slimmelezer-plus-in-luxembourg + brand: Zuidwijk + description: SlimmeLezer(+) in Luxembourg +description: | + Slimmelezer-Geräte in Luxemburg verwenden für verschiedene Sensoren andere Namen. +render: + - usage: grid + default: | + type: template + template: slimmelezer-luxembourg + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/zuidwijk-slimmelezer-plus-v2.yaml b/templates/release/de/meter/zuidwijk-slimmelezer-plus-v2.yaml new file mode 100644 index 0000000000..b199b9b31a --- /dev/null +++ b/templates/release/de/meter/zuidwijk-slimmelezer-plus-v2.yaml @@ -0,0 +1,24 @@ +template: slimmelezer-V2 +product: + identifier: zuidwijk-slimmelezer-plus-v2 + brand: Zuidwijk + description: SlimmeLezer(+) V2 +description: | + Neuere Slimmelezer-Geräte verwenden eine andere Konfiguration. Probieren Sie diese Vorlage aus, wenn die andere fehlschlägt. +render: + - usage: grid + default: | + type: template + template: slimmelezer-V2 + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/meter/zuidwijk-slimmelezer-plus.yaml b/templates/release/de/meter/zuidwijk-slimmelezer-plus.yaml new file mode 100644 index 0000000000..c6627cce34 --- /dev/null +++ b/templates/release/de/meter/zuidwijk-slimmelezer-plus.yaml @@ -0,0 +1,37 @@ +template: slimmelezer +product: + identifier: zuidwijk-slimmelezer-plus + brand: Zuidwijk + description: SlimmeLezer(+) +render: + - usage: grid + default: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + advanced: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + scale: 1000 # Skalierungsfaktor, Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: scale + example: 1 | 10 | 100 | 1000 + default: 1000 + choice: [] + unit: + description: Skalierungsfaktor + help: Verwenden Skala von 1000 für Zuidwijk Slimmelezer. Verwenden Skala 1 für ESPHome DSMR und mhendriks P1 Dongle + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/de/tariff/amber-electric.yaml b/templates/release/de/tariff/amber-electric.yaml new file mode 100644 index 0000000000..40b4f8c86e --- /dev/null +++ b/templates/release/de/tariff/amber-electric.yaml @@ -0,0 +1,77 @@ +template: amber +product: + identifier: amber-electric + brand: Amber Electric + group: Dynamischer Strompreis +countries: ["AU"] +render: + - default: | + type: template + template: amber + token: # optional + siteid: # optional + channel: # optional + advanced: | + type: template + template: amber + token: # optional + siteid: # optional + channel: # optional + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: siteid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: channel + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/amber_0.yaml b/templates/release/de/tariff/amber_0.yaml deleted file mode 100644 index 426aefc2f6..0000000000 --- a/templates/release/de/tariff/amber_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Amber Electric - group: Dynamischer Strompreis -countries: ["AU"] -render: - - default: | - type: template - template: amber - token: # optional - siteid: # optional - channel: # optional - advanced: | - type: template - template: amber - token: # optional - siteid: # optional - channel: # optional - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/awattar.yaml b/templates/release/de/tariff/awattar.yaml new file mode 100644 index 0000000000..b1861bcbfb --- /dev/null +++ b/templates/release/de/tariff/awattar.yaml @@ -0,0 +1,55 @@ +template: awattar +product: + identifier: awattar + brand: Awattar + group: Dynamischer Strompreis +countries: ["DE", "AT"] +render: + - default: | + type: template + template: awattar + region: AT # [DE, AT] + advanced: | + type: template + template: awattar + region: AT # [DE, AT] + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: region + example: AT + default: + choice: ['DE', 'AT'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/awattar_0.yaml b/templates/release/de/tariff/awattar_0.yaml deleted file mode 100644 index 18a940678a..0000000000 --- a/templates/release/de/tariff/awattar_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Awattar - group: Dynamischer Strompreis -countries: ["DE", "AT"] -render: - - default: | - type: template - template: awattar - region: AT # [DE, AT] - advanced: | - type: template - template: awattar - region: AT # [DE, AT] - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/electricity-maps-commercial-api.yaml b/templates/release/de/tariff/electricity-maps-commercial-api.yaml new file mode 100644 index 0000000000..12eb3a2963 --- /dev/null +++ b/templates/release/de/tariff/electricity-maps-commercial-api.yaml @@ -0,0 +1,44 @@ +template: electricitymaps +product: + identifier: electricity-maps-commercial-api + brand: Electricity Maps + description: Commercial API + group: CO₂ Vorhersage +requirements: ["skiptest"] +description: | + CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. +render: + - default: | + type: template + template: electricitymaps + uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) Adresse + token: + zone: DE # siehe https://api.electricitymap.org/v3/zones +params: + - name: uri + example: https://api-access.electricitymaps.com/2w...1g/ + default: + choice: [] + unit: + description: URI + help: HTTP(S) Adresse + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + description: + help: siehe https://api.electricitymap.org/v3/zones + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/tariff/electricity-maps-free-api.yaml b/templates/release/de/tariff/electricity-maps-free-api.yaml new file mode 100644 index 0000000000..8b258cf02b --- /dev/null +++ b/templates/release/de/tariff/electricity-maps-free-api.yaml @@ -0,0 +1,34 @@ +template: electricitymaps-free +product: + identifier: electricity-maps-free-api + brand: Electricity Maps + description: Free API + group: CO₂ Vorhersage +requirements: ["skiptest"] +description: | + CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. +render: + - default: | + type: template + template: electricitymaps-free + token: + zone: DE # siehe https://api.electricitymap.org/v3/zones +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + description: + help: siehe https://api.electricitymap.org/v3/zones + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/tariff/electricitymaps-free_0.yaml b/templates/release/de/tariff/electricitymaps-free_0.yaml deleted file mode 100644 index 141fdeec08..0000000000 --- a/templates/release/de/tariff/electricitymaps-free_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Electricity Maps - description: Free API - group: CO₂ Vorhersage -requirements: ["skiptest"] -description: | - CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. -render: - - default: | - type: template - template: electricitymaps-free - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones diff --git a/templates/release/de/tariff/electricitymaps_0.yaml b/templates/release/de/tariff/electricitymaps_0.yaml deleted file mode 100644 index c483166fe0..0000000000 --- a/templates/release/de/tariff/electricitymaps_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Electricity Maps - description: Commercial API - group: CO₂ Vorhersage -requirements: ["skiptest"] -description: | - CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. -render: - - default: | - type: template - template: electricitymaps - uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) Adresse - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones diff --git a/templates/release/de/tariff/energinet.yaml b/templates/release/de/tariff/energinet.yaml new file mode 100644 index 0000000000..50bd013c09 --- /dev/null +++ b/templates/release/de/tariff/energinet.yaml @@ -0,0 +1,56 @@ +template: energinet +product: + identifier: energinet + brand: Energinet + group: Dynamischer Strompreis +countries: ["DK"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: energinet + region: dk1 # [dk1, dk2] + advanced: | + type: template + template: energinet + region: dk1 # [dk1, dk2] + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: region + example: dk1 + default: + choice: ['dk1', 'dk2'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/energinet_0.yaml b/templates/release/de/tariff/energinet_0.yaml deleted file mode 100644 index 4f34b58118..0000000000 --- a/templates/release/de/tariff/energinet_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Energinet - group: Dynamischer Strompreis -countries: ["DK"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: energinet - region: dk1 # [dk1, dk2] - advanced: | - type: template - template: energinet - region: dk1 # [dk1, dk2] - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/energy-charts-api_0.yaml b/templates/release/de/tariff/energy-charts-api_0.yaml deleted file mode 100644 index 2b24b007d5..0000000000 --- a/templates/release/de/tariff/energy-charts-api_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Fraunhofer ISE - group: Dynamischer Strompreis -countries: ["EU"] -requirements: ["skiptest"] -description: | - Day-ahead Energiepreise (je kWh) an der Börse. Kann ohne vorherige Anmeldung auf https://api.energy-charts.info/ abgerufen werden. Nutzbar u.a. für dynamische Stromtarife, wo der Anbieter bis dato auf der Kundenschnittstelle noch kein Preis-Vorhersagen anbietet. -render: - - default: | - type: template - template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] - advanced: | - type: template - template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/enever.yaml b/templates/release/de/tariff/enever.yaml new file mode 100644 index 0000000000..8a9c836a71 --- /dev/null +++ b/templates/release/de/tariff/enever.yaml @@ -0,0 +1,77 @@ +template: enever +product: + identifier: enever + brand: Enever + group: Dynamischer Strompreis +countries: ["NL"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: enever + token: + provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + advanced: | + type: template + template: enever + token: + provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) + interval: 3h # optional +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: provider + example: + default: + choice: ['', 'AA', 'AIP', 'ANWB', 'BE', 'EE', 'EN', 'EVO', 'EZ', 'FR', 'GSL', 'MDE', 'NE', 'PE', 'TI', 'VDB', 'VON', 'WE', 'ZG', 'ZP'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true + - name: interval + example: + default: 3h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/enever_0.yaml b/templates/release/de/tariff/enever_0.yaml deleted file mode 100644 index 2cc2627043..0000000000 --- a/templates/release/de/tariff/enever_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Enever - group: Dynamischer Strompreis -countries: ["NL"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] - advanced: | - type: template - template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) - interval: 3h # optional diff --git a/templates/release/de/tariff/entso-e.yaml b/templates/release/de/tariff/entso-e.yaml new file mode 100644 index 0000000000..3fe142d5bc --- /dev/null +++ b/templates/release/de/tariff/entso-e.yaml @@ -0,0 +1,70 @@ +template: entsoe +product: + identifier: entso-e + brand: ENTSO-E + group: Dynamischer Strompreis +countries: ["EU"] +description: | + Day-ahead-Preise für den europäischen Strommarkt. Siehe https://transparency.entsoe.eu für weitere Informationen. + Basis für viele dynamische Tarife. + +render: + - default: | + type: template + template: entsoe + securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + advanced: | + type: template + template: entsoe + securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: securitytoken + example: + default: + choice: [] + unit: + description: + help: Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation + advanced: false + optional: true + - name: domain + example: BZN|DE-LU + default: + choice: [] + unit: + description: + help: siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas + advanced: false + optional: true + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/entsoe_0.yaml b/templates/release/de/tariff/entsoe_0.yaml deleted file mode 100644 index 24d1a1d5a7..0000000000 --- a/templates/release/de/tariff/entsoe_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: ENTSO-E - group: Dynamischer Strompreis -countries: ["EU"] -description: | - Day-ahead-Preise für den europäischen Strommarkt. Siehe https://transparency.entsoe.eu für weitere Informationen. - Basis für viele dynamische Tarife. - -render: - - default: | - type: template - template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) - advanced: | - type: template - template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/forecast-solar.yaml b/templates/release/de/tariff/forecast-solar.yaml new file mode 100644 index 0000000000..10ef52addf --- /dev/null +++ b/templates/release/de/tariff/forecast-solar.yaml @@ -0,0 +1,101 @@ +template: forecast-solar +product: + identifier: forecast-solar + brand: Forecast.Solar + group: PV Vorhersage +requirements: ["skiptest"] +description: | + [forecast.solar](https://forecast.solar) kann kostenlos verwendet werden. Kostenpflichtige Pläne können ebenfalls verwendet werden, indem ein API-Key angegeben wird. +render: + - default: | + type: template + template: forecast-solar + lat: 55.7351 # Breitengrad + lon: 9.1275 # Längengrad + dec: 25 # Neigung, 0 = horizontal, 90 = vertikal + kwp: 9.8 # Maximale Generatorleistung (kWp) + az: 180 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden + advanced: | + type: template + template: forecast-solar + lat: 55.7351 # Breitengrad + lon: 9.1275 # Längengrad + dec: 25 # Neigung, 0 = horizontal, 90 = vertikal + kwp: 9.8 # Maximale Generatorleistung (kWp) + az: 180 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden + horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizont, Simuliert Verschattung durch Gelände, [mehr Informationen](https://doc.forecast.solar/horizon) (optional) + apikey: # API-Key, optional + interval: 1h # optional +params: + - name: lat + example: 55.7351 + default: + choice: [] + unit: + description: Breitengrad + help: + advanced: false + optional: false + - name: lon + example: 9.1275 + default: + choice: [] + unit: + description: Längengrad + help: + advanced: false + optional: false + - name: dec + example: 25 + default: + choice: [] + unit: + description: Neigung + help: 0 = horizontal, 90 = vertikal + advanced: false + optional: false + - name: kwp + example: 9.8 + default: + choice: [] + unit: kWp + description: Maximale Generatorleistung + help: + advanced: false + optional: false + - name: az + example: 180 + default: + choice: [] + unit: + description: Azimut + help: -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden + advanced: false + optional: false + - name: horizon + example: 0,0,15,30,45,60,60,60,45,30,15,0 + default: + choice: [] + unit: + description: Horizont + help: Simuliert Verschattung durch Gelände, [mehr Informationen](https://doc.forecast.solar/horizon) + advanced: true + optional: true + - name: apikey + example: + default: + choice: [] + unit: + description: API-Key + help: + advanced: true + optional: true + - name: interval + example: + default: 1h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/forecast-solar_0.yaml b/templates/release/de/tariff/forecast-solar_0.yaml deleted file mode 100644 index b15ecb6b57..0000000000 --- a/templates/release/de/tariff/forecast-solar_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Forecast.Solar - group: PV Vorhersage -requirements: ["skiptest"] -description: | - [forecast.solar](https://forecast.solar) kann kostenlos verwendet werden. Kostenpflichtige Pläne können ebenfalls verwendet werden, indem ein API-Key angegeben wird. -render: - - default: | - type: template - template: forecast-solar - lat: 55.7351 # Breitengrad - lon: 9.1275 # Längengrad - dec: 25 # Neigung, 0 = horizontal, 90 = vertikal - kwp: 9.8 # Maximale Generatorleistung (kWp) - az: 180 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden - advanced: | - type: template - template: forecast-solar - lat: 55.7351 # Breitengrad - lon: 9.1275 # Längengrad - dec: 25 # Neigung, 0 = horizontal, 90 = vertikal - kwp: 9.8 # Maximale Generatorleistung (kWp) - az: 180 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden - horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizont, Simuliert Verschattung durch Gelände, [mehr Informationen](https://doc.forecast.solar/horizon) (optional) - apikey: # API-Key, optional - interval: 1h # optional diff --git a/templates/release/de/tariff/fraunhofer-ise.yaml b/templates/release/de/tariff/fraunhofer-ise.yaml new file mode 100644 index 0000000000..78323adc0c --- /dev/null +++ b/templates/release/de/tariff/fraunhofer-ise.yaml @@ -0,0 +1,58 @@ +template: energy-charts-api +product: + identifier: fraunhofer-ise + brand: Fraunhofer ISE + group: Dynamischer Strompreis +countries: ["EU"] +requirements: ["skiptest"] +description: | + Day-ahead Energiepreise (je kWh) an der Börse. Kann ohne vorherige Anmeldung auf https://api.energy-charts.info/ abgerufen werden. Nutzbar u.a. für dynamische Stromtarife, wo der Anbieter bis dato auf der Kundenschnittstelle noch kein Preis-Vorhersagen anbietet. +render: + - default: | + type: template + template: energy-charts-api + bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + advanced: | + type: template + template: energy-charts-api + bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: bzn + example: + default: DE-LU + choice: ['AT', 'BE', 'CH', 'CZ', 'DE-LU', 'DE-AT-LU', 'DK1', 'DK2', 'FR', 'HU', 'IT-NORTH', 'NL', 'NO2', 'PL', 'SE4', 'SI'] + unit: + description: + help: Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/green-grid-compass.yaml b/templates/release/de/tariff/green-grid-compass.yaml new file mode 100644 index 0000000000..1889c6442d --- /dev/null +++ b/templates/release/de/tariff/green-grid-compass.yaml @@ -0,0 +1,34 @@ +template: green-grid-compass +product: + identifier: green-grid-compass + brand: Green Grid Compass + group: CO₂ Vorhersage +countries: ["BE", "DE", "LU"] +requirements: ["skiptest"] +description: | + Europäische CO₂-Intensitätsdaten von [greengrid-compass.eu](https://www.greengrid-compass.eu). Liefert Vorhersagen der nächsten Stunden und ist nach Registrierung kostenlos nutzbar. +render: + - default: | + type: template + template: green-grid-compass + apiKey: # API-Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key + zone: DE_LU # Zonencode, [BE, DE_LU] +params: + - name: apiKey + example: + default: + choice: [] + unit: + description: API-Key + help: Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key + advanced: false + optional: false + - name: zone + example: + default: DE_LU + choice: ['BE', 'DE_LU'] + unit: + description: Zonencode + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/de/tariff/green-grid-compass_0.yaml b/templates/release/de/tariff/green-grid-compass_0.yaml deleted file mode 100644 index 1cd2473509..0000000000 --- a/templates/release/de/tariff/green-grid-compass_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Green Grid Compass - group: CO₂ Vorhersage -countries: ["BE", "DE", "LU"] -requirements: ["skiptest"] -description: | - Europäische CO₂-Intensitätsdaten von [greengrid-compass.eu](https://www.greengrid-compass.eu). Liefert Vorhersagen der nächsten Stunden und ist nach Registrierung kostenlos nutzbar. -render: - - default: | - type: template - template: green-grid-compass - apiKey: # API-Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key - zone: DE_LU # Zonencode, [BE, DE_LU] diff --git a/templates/release/de/tariff/groupe-e-vario-plus.yaml b/templates/release/de/tariff/groupe-e-vario-plus.yaml new file mode 100644 index 0000000000..de5a82f1bc --- /dev/null +++ b/templates/release/de/tariff/groupe-e-vario-plus.yaml @@ -0,0 +1,46 @@ +template: groupe-e +product: + identifier: groupe-e-vario-plus + brand: Groupe E + description: Vario Plus + group: Dynamischer Strompreis +countries: ["CH"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: groupe-e + advanced: | + type: template + template: groupe-e + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/groupe-e_0.yaml b/templates/release/de/tariff/groupe-e_0.yaml deleted file mode 100644 index eb503a2444..0000000000 --- a/templates/release/de/tariff/groupe-e_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Groupe E - description: Vario Plus - group: Dynamischer Strompreis -countries: ["CH"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: groupe-e - advanced: | - type: template - template: groupe-e - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/grunstromindex.yaml b/templates/release/de/tariff/grunstromindex.yaml new file mode 100644 index 0000000000..dfb34b4499 --- /dev/null +++ b/templates/release/de/tariff/grunstromindex.yaml @@ -0,0 +1,34 @@ +template: grünstromindex +product: + identifier: grunstromindex + brand: Grünstromindex + group: CO₂ Vorhersage +countries: ["DE"] +requirements: ["skiptest"] +description: | + Regionale Emissionsdaten von https://gruenstromindex.de +render: + - default: | + type: template + template: grünstromindex + zip: + token: # Token für den Zugriff auf die API von https://console.corrently.io/ (optional) +params: + - name: zip + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: Token für den Zugriff auf die API von https://console.corrently.io/ + advanced: false + optional: true \ No newline at end of file diff --git "a/templates/release/de/tariff/gr\303\274nstromindex_0.yaml" "b/templates/release/de/tariff/gr\303\274nstromindex_0.yaml" deleted file mode 100644 index 0a02c63f62..0000000000 --- "a/templates/release/de/tariff/gr\303\274nstromindex_0.yaml" +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Grünstromindex - group: CO₂ Vorhersage -countries: ["DE"] -requirements: ["skiptest"] -description: | - Regionale Emissionsdaten von https://gruenstromindex.de -render: - - default: | - type: template - template: grünstromindex - zip: - token: # Token für den Zugriff auf die API von https://console.corrently.io/ (optional) diff --git a/templates/release/de/tariff/national-grid-eso.yaml b/templates/release/de/tariff/national-grid-eso.yaml new file mode 100644 index 0000000000..ae59095492 --- /dev/null +++ b/templates/release/de/tariff/national-grid-eso.yaml @@ -0,0 +1,31 @@ +template: ngeso +product: + identifier: national-grid-eso + brand: National Grid ESO + group: CO₂ Vorhersage +countries: ["GB"] +render: + - default: | + type: template + template: ngeso + region: 1 # Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. (optional) +params: + - name: region + example: 1 + default: + choice: [] + unit: + description: + help: Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list + advanced: false + optional: true + - name: postalcode + example: SW1 + default: + choice: [] + unit: + description: + help: Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/ngeso_0.yaml b/templates/release/de/tariff/ngeso_0.yaml deleted file mode 100644 index 42c27e82d9..0000000000 --- a/templates/release/de/tariff/ngeso_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: National Grid ESO - group: CO₂ Vorhersage -countries: ["GB"] -render: - - default: | - type: template - template: ngeso - region: 1 # Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list (optional) - postalcode: SW1 # Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. (optional) diff --git a/templates/release/de/tariff/nordpool-spot-prices.yaml b/templates/release/de/tariff/nordpool-spot-prices.yaml new file mode 100644 index 0000000000..7667c3e997 --- /dev/null +++ b/templates/release/de/tariff/nordpool-spot-prices.yaml @@ -0,0 +1,69 @@ +template: nordpool +product: + identifier: nordpool-spot-prices + brand: Nordpool spot prices + group: Dynamischer Strompreis +countries: ["EU"] +requirements: ["skiptest"] +description: | + Nordpool Spot Preise im Day-Ahead-Markt für alle Märkte in der Nordpool-Region. +render: + - default: | + type: template + template: nordpool + region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + advanced: | + type: template + template: nordpool + region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: region + example: GER + default: + choice: ['EE', 'LT', 'LV', 'AT', 'BE', 'FR', 'GER', 'NL', 'PL', 'DK1', 'DK2', 'FI', 'NO1', 'NO2', 'NO3', 'NO4', 'NO5', 'SE1', 'SE2', 'SE3', 'SE4', 'TEL', 'SYS'] + unit: + description: + help: + advanced: false + optional: true + - name: currency + example: + default: EUR + choice: ['DKK', 'EUR', 'NOK', 'PLN', 'RON', 'SEK'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/nordpool_0.yaml b/templates/release/de/tariff/nordpool_0.yaml deleted file mode 100644 index c297312d47..0000000000 --- a/templates/release/de/tariff/nordpool_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - brand: Nordpool spot prices - group: Dynamischer Strompreis -countries: ["EU"] -requirements: ["skiptest"] -description: | - Nordpool Spot Preise im Day-Ahead-Markt für alle Märkte in der Nordpool-Region. -render: - - default: | - type: template - template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] - advanced: | - type: template - template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/octopus-api_0.yaml b/templates/release/de/tariff/octopus-api_0.yaml deleted file mode 100644 index dd0bb8b35c..0000000000 --- a/templates/release/de/tariff/octopus-api_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Octopus Energy - description: API - group: Dynamischer Strompreis -countries: ["GB"] -description: | - Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access -render: - - default: | - type: template - template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional) diff --git a/templates/release/de/tariff/octopus-energy-api.yaml b/templates/release/de/tariff/octopus-energy-api.yaml new file mode 100644 index 0000000000..1f5f76218d --- /dev/null +++ b/templates/release/de/tariff/octopus-energy-api.yaml @@ -0,0 +1,34 @@ +template: octopus-api +product: + identifier: octopus-energy-api + brand: Octopus Energy + description: API + group: Dynamischer Strompreis +countries: ["GB"] +description: | + Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access +render: + - default: | + type: template + template: octopus-api + apiKey: # Octopus Energy API Key. + accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional) +params: + - name: apiKey + example: + default: + choice: [] + unit: + description: + help: Octopus Energy API Key. + advanced: false + optional: false + - name: accountNumber + example: + default: + choice: [] + unit: + description: + help: Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/octopus-energy-product-code.yaml b/templates/release/de/tariff/octopus-energy-product-code.yaml new file mode 100644 index 0000000000..88f69fb77a --- /dev/null +++ b/templates/release/de/tariff/octopus-energy-product-code.yaml @@ -0,0 +1,42 @@ +template: octopus-productcode +product: + identifier: octopus-energy-product-code + brand: Octopus Energy + description: Product Code + group: Dynamischer Strompreis +countries: ["GB"] +render: + - default: | + type: template + template: octopus-productcode + productCode: AGILE-FLEX-22-11-25 # Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. + region: # Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Ich benutze den BACS-Lastschrifttarif. (optional) +params: + - name: productCode + example: AGILE-FLEX-22-11-25 + default: + choice: [] + unit: + description: + help: Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. + advanced: false + optional: false + - name: region + example: + default: + choice: ['A', 'B', 'C', 'D', 'E', 'F', 'G', 'H', 'J', 'K', 'L', 'M', 'N', 'P'] + unit: + description: + help: 'Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/' + advanced: false + optional: false + - name: directDebit + example: + default: true + choice: [] + unit: + description: + help: Ich benutze den BACS-Lastschrifttarif. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/octopus-productcode_0.yaml b/templates/release/de/tariff/octopus-productcode_0.yaml deleted file mode 100644 index 4b29cd671b..0000000000 --- a/templates/release/de/tariff/octopus-productcode_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Octopus Energy - description: Product Code - group: Dynamischer Strompreis -countries: ["GB"] -render: - - default: | - type: template - template: octopus-productcode - productCode: AGILE-FLEX-22-11-25 # Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. - region: # Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] - directDebit: true # Ich benutze den BACS-Lastschrifttarif. (optional) diff --git a/templates/release/de/tariff/open-meteo.yaml b/templates/release/de/tariff/open-meteo.yaml new file mode 100644 index 0000000000..fed0e5be2a --- /dev/null +++ b/templates/release/de/tariff/open-meteo.yaml @@ -0,0 +1,141 @@ +template: open-meteo +product: + identifier: open-meteo + brand: Open-Meteo + group: PV Vorhersage +requirements: ["skiptest"] +description: | + Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Open-Source-Wetter-API und bietet kostenlosen Zugriff für nicht-kommerzielle Nutzung. Kein API-Schlüssel erforderlich. +render: + - default: | + type: template + template: open-meteo + lat: 55.7351 # Breitengrad + lon: 9.1275 # Längengrad + dec: 25 # Neigung, 0 = horizontal, 90 = vertikal + kwp: 9.8 # Maximale Generatorleistung (kWp) + az: 0 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden + advanced: | + type: template + template: open-meteo + lat: 55.7351 # Breitengrad + lon: 9.1275 # Längengrad + dec: 25 # Neigung, 0 = horizontal, 90 = vertikal + kwp: 9.8 # Maximale Generatorleistung (kWp) + az: 0 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden + ac: 1000 # AC Leistung [kW], optional + dm: 0 # Dämpfung morgens [%], optional + de: 0 # Dämpfung abends [%], optional + efficiency: 100 # Wirkungsgrad [%], optional + alphatemp: -0.004 # Temperaturkoeffizient, optional + rossmodel: 0.0342 # Kühlung [Ross-Modell], Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) + interval: 1h # optional +params: + - name: lat + example: 55.7351 + default: + choice: [] + unit: + description: Breitengrad + help: + advanced: false + optional: false + - name: lon + example: 9.1275 + default: + choice: [] + unit: + description: Längengrad + help: + advanced: false + optional: false + - name: dec + example: 25 + default: + choice: [] + unit: + description: Neigung + help: 0 = horizontal, 90 = vertikal + advanced: false + optional: false + - name: kwp + example: 9.8 + default: + choice: [] + unit: kWp + description: Maximale Generatorleistung + help: + advanced: false + optional: false + - name: az + example: 0 + default: + choice: [] + unit: + description: Azimut + help: -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden + advanced: false + optional: false + - name: ac + example: + default: 1000 + choice: [] + unit: + description: AC Leistung [kW] + help: + advanced: true + optional: true + - name: dm + example: + default: 0 + choice: [] + unit: + description: Dämpfung morgens [%] + help: + advanced: true + optional: true + - name: de + example: + default: 0 + choice: [] + unit: + description: Dämpfung abends [%] + help: + advanced: true + optional: true + - name: efficiency + example: + default: 100 + choice: [] + unit: + description: Wirkungsgrad [%] + help: + advanced: true + optional: true + - name: alphatemp + example: + default: -0.004 + choice: [] + unit: + description: Temperaturkoeffizient + help: + advanced: true + optional: true + - name: rossmodel + example: + default: 0.0342 + choice: [] + unit: + description: Kühlung [Ross-Modell] + help: Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) + advanced: true + optional: true + - name: interval + example: + default: 1h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/open-meteo_0.yaml b/templates/release/de/tariff/open-meteo_0.yaml deleted file mode 100644 index bed9c12b2c..0000000000 --- a/templates/release/de/tariff/open-meteo_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Open-Meteo - group: PV Vorhersage -requirements: ["skiptest"] -description: | - Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Open-Source-Wetter-API und bietet kostenlosen Zugriff für nicht-kommerzielle Nutzung. Kein API-Schlüssel erforderlich. -render: - - default: | - type: template - template: open-meteo - lat: 55.7351 # Breitengrad - lon: 9.1275 # Längengrad - dec: 25 # Neigung, 0 = horizontal, 90 = vertikal - kwp: 9.8 # Maximale Generatorleistung (kWp) - az: 0 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden - advanced: | - type: template - template: open-meteo - lat: 55.7351 # Breitengrad - lon: 9.1275 # Längengrad - dec: 25 # Neigung, 0 = horizontal, 90 = vertikal - kwp: 9.8 # Maximale Generatorleistung (kWp) - az: 0 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden - ac: 1000 # AC Leistung [kW], optional - dm: 0 # Dämpfung morgens [%], optional - de: 0 # Dämpfung abends [%], optional - efficiency: 100 # Wirkungsgrad [%], optional - alphatemp: -0.004 # Temperaturkoeffizient, optional - rossmodel: 0.0342 # Kühlung [Ross-Modell], Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional diff --git a/templates/release/de/tariff/ostrom.yaml b/templates/release/de/tariff/ostrom.yaml new file mode 100644 index 0000000000..8560014056 --- /dev/null +++ b/templates/release/de/tariff/ostrom.yaml @@ -0,0 +1,44 @@ +template: ostrom +product: + identifier: ostrom + brand: Ostrom + group: Dynamischer Strompreis +countries: ["DE"] +requirements: ["skiptest"] +description: | + Erzeuge einen 'Production Client' im Ostrom-Entwicklerportal: https://developer.ostrom-api.io/ +render: + - default: | + type: template + template: ostrom + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a + contract: 100523456 # Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional) +params: + - name: clientid + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: clientsecret + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: contract + example: 100523456 + default: + choice: [] + unit: + description: + help: Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/ostrom_0.yaml b/templates/release/de/tariff/ostrom_0.yaml deleted file mode 100644 index ece29a4023..0000000000 --- a/templates/release/de/tariff/ostrom_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Ostrom - group: Dynamischer Strompreis -countries: ["DE"] -requirements: ["skiptest"] -description: | - Erzeuge einen 'Production Client' im Ostrom-Entwicklerportal: https://developer.ostrom-api.io/ -render: - - default: | - type: template - template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional) diff --git a/templates/release/de/tariff/pun-orario.yaml b/templates/release/de/tariff/pun-orario.yaml new file mode 100644 index 0000000000..68693fbf9e --- /dev/null +++ b/templates/release/de/tariff/pun-orario.yaml @@ -0,0 +1,47 @@ +template: pun +product: + identifier: pun-orario + brand: PUN Orario + group: Dynamischer Strompreis +countries: ["IT"] +requirements: ["skiptest"] +description: | + Preisdaten von https://www.mercatoelettrico.org/it/. Wird oft zur Einspeisung ins Netz verwendet. +render: + - default: | + type: template + template: pun + advanced: | + type: template + template: pun + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/pun_0.yaml b/templates/release/de/tariff/pun_0.yaml deleted file mode 100644 index fda1ea56fb..0000000000 --- a/templates/release/de/tariff/pun_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: PUN Orario - group: Dynamischer Strompreis -countries: ["IT"] -requirements: ["skiptest"] -description: | - Preisdaten von https://www.mercatoelettrico.org/it/. Wird oft zur Einspeisung ins Netz verwendet. -render: - - default: | - type: template - template: pun - advanced: | - type: template - template: pun - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/smartenergy-smartcontrol.yaml b/templates/release/de/tariff/smartenergy-smartcontrol.yaml new file mode 100644 index 0000000000..db6b4f0755 --- /dev/null +++ b/templates/release/de/tariff/smartenergy-smartcontrol.yaml @@ -0,0 +1,45 @@ +template: smartenergy +product: + identifier: smartenergy-smartcontrol + brand: SmartEnergy + description: smartCONTROL + group: Dynamischer Strompreis +countries: ["AT"] +render: + - default: | + type: template + template: smartenergy + advanced: | + type: template + template: smartenergy + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/smartenergy_0.yaml b/templates/release/de/tariff/smartenergy_0.yaml deleted file mode 100644 index e98a68ae18..0000000000 --- a/templates/release/de/tariff/smartenergy_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SmartEnergy - description: smartCONTROL - group: Dynamischer Strompreis -countries: ["AT"] -render: - - default: | - type: template - template: smartenergy - advanced: | - type: template - template: smartenergy - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/solcast.yaml b/templates/release/de/tariff/solcast.yaml new file mode 100644 index 0000000000..da9fe517c9 --- /dev/null +++ b/templates/release/de/tariff/solcast.yaml @@ -0,0 +1,68 @@ +template: solcast +product: + identifier: solcast + brand: Solcast + group: PV Vorhersage +requirements: ["skiptest"] +description: | + Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting)-Account. Der kostenlose "Home User" Tarif ist für private Anwendungen oft ausreichend. Dieser Plan hat ein API-Limit von 10 Anfragen pro Tag. +render: + - default: | + type: template + template: solcast + site: # Ressource ID deiner Anlage + token: # Solcast API Token + advanced: | + type: template + template: solcast + site: # Ressource ID deiner Anlage + token: # Solcast API Token + from: # Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) + to: # Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) + interval: 3h # optional +params: + - name: site + example: + default: + choice: [] + unit: + description: + help: Ressource ID deiner Anlage + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: Solcast API Token + advanced: false + optional: false + - name: from + example: + default: + choice: [] + unit: + description: + help: Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" + advanced: true + optional: true + - name: to + example: + default: + choice: [] + unit: + description: + help: Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" + advanced: true + optional: true + - name: interval + example: + default: 3h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/solcast_0.yaml b/templates/release/de/tariff/solcast_0.yaml deleted file mode 100644 index bc6c77802f..0000000000 --- a/templates/release/de/tariff/solcast_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Solcast - group: PV Vorhersage -requirements: ["skiptest"] -description: | - Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting)-Account. Der kostenlose "Home User" Tarif ist für private Anwendungen oft ausreichend. Dieser Plan hat ein API-Limit von 10 Anfragen pro Tag. -render: - - default: | - type: template - template: solcast - site: # Ressource ID deiner Anlage - token: # Solcast API Token - advanced: | - type: template - template: solcast - site: # Ressource ID deiner Anlage - token: # Solcast API Token - from: # Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) - to: # Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) - interval: 3h # optional diff --git a/templates/release/de/tariff/spotty-energie.yaml b/templates/release/de/tariff/spotty-energie.yaml new file mode 100644 index 0000000000..5238a12ca9 --- /dev/null +++ b/templates/release/de/tariff/spotty-energie.yaml @@ -0,0 +1,67 @@ +template: spottyenergy +product: + identifier: spotty-energie + brand: Spotty Energie + group: Dynamischer Strompreis +countries: ["AT"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: spottyenergy + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + advanced: | + type: template + template: spottyenergy + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: contractid + example: ffffffff-4444-6666-2222-aaaaaabbbbbb + default: + choice: [] + unit: + description: + help: Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ + advanced: false + optional: false + - name: pricetype + example: + default: CONSUMPTION + choice: ['MARKET', 'CONSUMPTION', 'GENERATION'] + unit: + description: + help: Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/spottyenergy_0.yaml b/templates/release/de/tariff/spottyenergy_0.yaml deleted file mode 100644 index dfb3bc0b50..0000000000 --- a/templates/release/de/tariff/spottyenergy_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Spotty Energie - group: Dynamischer Strompreis -countries: ["AT"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] - advanced: | - type: template - template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/tibber.yaml b/templates/release/de/tariff/tibber.yaml new file mode 100644 index 0000000000..390ad45c95 --- /dev/null +++ b/templates/release/de/tariff/tibber.yaml @@ -0,0 +1,69 @@ +template: tibber +product: + identifier: tibber + brand: Tibber + group: Dynamischer Strompreis +countries: ["NO", "SE", "DE", "NL"] +requirements: ["skiptest"] +description: | + Hol dir deinen API-Token aus dem Tibber-Entwicklerportal: https://developer.tibber.com/ +render: + - default: | + type: template + template: tibber + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) + advanced: | + type: template + template: tibber + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) + charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) + tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) +params: + - name: token + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: homeid + example: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c + default: + choice: [] + unit: + description: + help: Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. + advanced: false + optional: true + - name: charges + example: + default: + choice: [] + unit: + description: Aufschlag + help: Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Steuer + help: Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formel + help: Individuelle Formel zur Berechnung des Preises + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/tibber_0.yaml b/templates/release/de/tariff/tibber_0.yaml deleted file mode 100644 index de3c6130d9..0000000000 --- a/templates/release/de/tariff/tibber_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - brand: Tibber - group: Dynamischer Strompreis -countries: ["NO", "SE", "DE", "NL"] -requirements: ["skiptest"] -description: | - Hol dir deinen API-Token aus dem Tibber-Entwicklerportal: https://developer.tibber.com/ -render: - - default: | - type: template - template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) - advanced: | - type: template - template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) - charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) - tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) diff --git a/templates/release/de/tariff/victron-vrm-solar-forecast.yaml b/templates/release/de/tariff/victron-vrm-solar-forecast.yaml new file mode 100644 index 0000000000..1ded5b0719 --- /dev/null +++ b/templates/release/de/tariff/victron-vrm-solar-forecast.yaml @@ -0,0 +1,49 @@ +template: victron +product: + identifier: victron-vrm-solar-forecast + brand: Victron + description: VRM Solar Forecast + group: PV Vorhersage +requirements: ["skiptest"] +description: | + [vrm.victronenergy.com](https://vrm.victronenergy.com) abrufen der 2-Tage-Prognose einer Installation im VRM-Portal. Es wird ein kostenloses User Access Token benoetigt. +render: + - default: | + type: template + template: victron + idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt + token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen + advanced: | + type: template + template: victron + idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt + token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen + interval: 1h # optional +params: + - name: idsite + example: 123456 + default: + choice: [] + unit: + description: VRM-Installations-ID der Installation + help: Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: API Zugriffstoken + help: Token können im VRM erstellt werden unter Präferenzen->Integrationen + advanced: false + optional: false + - name: interval + example: + default: 1h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/victron_0.yaml b/templates/release/de/tariff/victron_0.yaml deleted file mode 100644 index 83fd4926bc..0000000000 --- a/templates/release/de/tariff/victron_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Victron - description: VRM Solar Forecast - group: PV Vorhersage -requirements: ["skiptest"] -description: | - [vrm.victronenergy.com](https://vrm.victronenergy.com) abrufen der 2-Tage-Prognose einer Installation im VRM-Portal. Es wird ein kostenloses User Access Token benoetigt. -render: - - default: | - type: template - template: victron - idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt - token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen - advanced: | - type: template - template: victron - idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt - token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen - interval: 1h # optional diff --git a/templates/release/de/vehicle/aiways.yaml b/templates/release/de/vehicle/aiways.yaml new file mode 100644 index 0000000000..2428df9340 --- /dev/null +++ b/templates/release/de/vehicle/aiways.yaml @@ -0,0 +1,147 @@ +template: aiways +product: + identifier: aiways + brand: Aiways +render: + - default: | + type: template + template: aiways + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: aiways + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/aiways_0.yaml b/templates/release/de/vehicle/aiways_0.yaml deleted file mode 100644 index 5e0497c25c..0000000000 --- a/templates/release/de/vehicle/aiways_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Aiways -render: - - default: | - type: template - template: aiways - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: aiways - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/audi.yaml b/templates/release/de/vehicle/audi.yaml new file mode 100644 index 0000000000..e3f21d047b --- /dev/null +++ b/templates/release/de/vehicle/audi.yaml @@ -0,0 +1,147 @@ +template: audi +product: + identifier: audi + brand: Audi +render: + - default: | + type: template + template: audi + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WAUZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: audi + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WAUZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: WAUZZZ... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/audi_0.yaml b/templates/release/de/vehicle/audi_0.yaml deleted file mode 100644 index 577105d571..0000000000 --- a/templates/release/de/vehicle/audi_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Audi -render: - - default: | - type: template - template: audi - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WAUZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: audi - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WAUZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/bmw.yaml b/templates/release/de/vehicle/bmw.yaml new file mode 100644 index 0000000000..26ea682910 --- /dev/null +++ b/templates/release/de/vehicle/bmw.yaml @@ -0,0 +1,191 @@ +template: bmw +product: + identifier: bmw + brand: BMW +description: | + Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. + +render: + - default: | + type: template + template: bmw + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + hcaptcha: + advanced: | + type: template + template: bmw + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + hcaptcha: + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + region: EU # Region, [EU, NA] + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: WBMW... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: hcaptcha + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: region + example: + default: EU + choice: ['EU', 'NA'] + unit: + description: Region + help: + advanced: true + optional: false + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/bmw_0.yaml b/templates/release/de/vehicle/bmw_0.yaml deleted file mode 100644 index fc093dab65..0000000000 --- a/templates/release/de/vehicle/bmw_0.yaml +++ /dev/null @@ -1,35 +0,0 @@ -product: - brand: BMW -description: | - Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. - -render: - - default: | - type: template - template: bmw - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: - advanced: | - type: template - template: bmw - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - region: EU # Region, [EU, NA] - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/carwings_0.yaml b/templates/release/de/vehicle/carwings_0.yaml deleted file mode 100644 index 5203423571..0000000000 --- a/templates/release/de/vehicle/carwings_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nissan - description: Leaf (pre 2019) -render: - - default: | - type: template - template: carwings - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: carwings - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/citroen.yaml b/templates/release/de/vehicle/citroen.yaml new file mode 100644 index 0000000000..b38f2a07fb --- /dev/null +++ b/templates/release/de/vehicle/citroen.yaml @@ -0,0 +1,161 @@ +template: citroen +product: + identifier: citroen + brand: Citroën +description: | + Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + +render: + - default: | + type: template + template: citroen + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: citroen + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/citroen_0.yaml b/templates/release/de/vehicle/citroen_0.yaml deleted file mode 100644 index dc4ce6ca3b..0000000000 --- a/templates/release/de/vehicle/citroen_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Citroën -description: | - Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. - -render: - - default: | - type: template - template: citroen - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: citroen - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/cupra_0.yaml b/templates/release/de/vehicle/cupra_0.yaml deleted file mode 100644 index 9e6a57b1dc..0000000000 --- a/templates/release/de/vehicle/cupra_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Seat - description: CupraConnect Gen4 (Born, Formentor, Tavascan) -render: - - default: | - type: template - template: cupra - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: cupra - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/dacia.yaml b/templates/release/de/vehicle/dacia.yaml new file mode 100644 index 0000000000..a2829a658d --- /dev/null +++ b/templates/release/de/vehicle/dacia.yaml @@ -0,0 +1,167 @@ +template: dacia +product: + identifier: dacia + brand: Dacia +render: + - default: | + type: template + template: dacia + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: dacia + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/dacia_0.yaml b/templates/release/de/vehicle/dacia_0.yaml deleted file mode 100644 index d6eb649092..0000000000 --- a/templates/release/de/vehicle/dacia_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: Dacia -render: - - default: | - type: template - template: dacia - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: dacia - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/ds.yaml b/templates/release/de/vehicle/ds.yaml new file mode 100644 index 0000000000..d3e33e9272 --- /dev/null +++ b/templates/release/de/vehicle/ds.yaml @@ -0,0 +1,161 @@ +template: ds +product: + identifier: ds + brand: DS +description: | + Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + +render: + - default: | + type: template + template: ds + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: ds + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/ds_0.yaml b/templates/release/de/vehicle/ds_0.yaml deleted file mode 100644 index d58c9674fb..0000000000 --- a/templates/release/de/vehicle/ds_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: DS -description: | - Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. - -render: - - default: | - type: template - template: ds - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: ds - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/enyaq_0.yaml b/templates/release/de/vehicle/enyaq_0.yaml deleted file mode 100644 index f02d4c5b44..0000000000 --- a/templates/release/de/vehicle/enyaq_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Skoda - description: Enyaq -render: - - default: | - type: template - template: enyaq - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: enyaq - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - timeout: 10s # Zeitüberschreitung, optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/evnotify.yaml b/templates/release/de/vehicle/evnotify.yaml new file mode 100644 index 0000000000..8488b849ee --- /dev/null +++ b/templates/release/de/vehicle/evnotify.yaml @@ -0,0 +1,127 @@ +template: evnotify +product: + identifier: evnotify + description: evNotify + group: Generische Unterstützung +render: + - default: | + type: template + template: evnotify + akey: + token: + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: evnotify + akey: + token: + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: akey + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/evnotify_0.yaml b/templates/release/de/vehicle/evnotify_0.yaml deleted file mode 100644 index 805d253324..0000000000 --- a/templates/release/de/vehicle/evnotify_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: evNotify - group: Generische Unterstützung -render: - - default: | - type: template - template: evnotify - akey: - token: - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: evnotify - akey: - token: - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/fiat.yaml b/templates/release/de/vehicle/fiat.yaml new file mode 100644 index 0000000000..6b1133c87f --- /dev/null +++ b/templates/release/de/vehicle/fiat.yaml @@ -0,0 +1,178 @@ +template: fiat +product: + identifier: fiat + brand: Fiat +render: + - default: | + type: template + template: fiat + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + advanced: | + type: template + template: fiat + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: ZFAE... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: pin + example: + default: + choice: [] + unit: + description: + help: Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/fiat_0.yaml b/templates/release/de/vehicle/fiat_0.yaml deleted file mode 100644 index f21faac875..0000000000 --- a/templates/release/de/vehicle/fiat_0.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - brand: Fiat -render: - - default: | - type: template - template: fiat - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) - advanced: | - type: template - template: fiat - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/fiat_1.yaml b/templates/release/de/vehicle/fiat_1.yaml deleted file mode 100644 index 3ab9d07926..0000000000 --- a/templates/release/de/vehicle/fiat_1.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - brand: Jeep -render: - - default: | - type: template - template: fiat - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) - advanced: | - type: template - template: fiat - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/flobz_0.yaml b/templates/release/de/vehicle/flobz_0.yaml deleted file mode 100644 index 387e97b4cb..0000000000 --- a/templates/release/de/vehicle/flobz_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - description: PSA Car Controller - group: Generische Unterstützung -description: | - Remote Control of PSA car https://github.com/flobz/psa_car_controller -render: - - default: | - type: template - template: flobz - url: http://192.0.2.2 - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: flobz - url: http://192.0.2.2 - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - wakeup_alt: false # alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. (optional) diff --git a/templates/release/de/vehicle/ford-connect_0.yaml b/templates/release/de/vehicle/ford-connect_0.yaml deleted file mode 100644 index 32d7605e37..0000000000 --- a/templates/release/de/vehicle/ford-connect_0.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - brand: Ford -render: - - default: | - type: template - template: ford-connect - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com - clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com - accessToken: - refreshToken: - vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: ford-connect - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com - clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com - accessToken: - refreshToken: - vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/ford.yaml b/templates/release/de/vehicle/ford.yaml new file mode 100644 index 0000000000..67c61b1f96 --- /dev/null +++ b/templates/release/de/vehicle/ford.yaml @@ -0,0 +1,169 @@ +template: ford-connect +product: + identifier: ford + brand: Ford +render: + - default: | + type: template + template: ford-connect + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com + clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com + accessToken: + refreshToken: + vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: ford-connect + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com + clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com + accessToken: + refreshToken: + vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: clientid + example: + default: + choice: [] + unit: + description: FordConnect API Client ID + help: Einrichtung unter https://developer.ford.com + advanced: false + optional: false + - name: clientsecret + example: + default: + choice: [] + unit: + description: FordConnect API Client Secret + help: Einrichtung unter https://developer.ford.com + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: WF0FXX... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/generic-vehicle-without-api.yaml b/templates/release/de/vehicle/generic-vehicle-without-api.yaml new file mode 100644 index 0000000000..9c05a9f976 --- /dev/null +++ b/templates/release/de/vehicle/generic-vehicle-without-api.yaml @@ -0,0 +1,105 @@ +template: offline +product: + identifier: generic-vehicle-without-api + description: Generisches Fahrzeug (ohne API) + group: Generische Unterstützung +render: + - default: | + type: template + template: offline + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: offline + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/hyundai-bluelink.yaml b/templates/release/de/vehicle/hyundai-bluelink.yaml new file mode 100644 index 0000000000..c7b4f04d26 --- /dev/null +++ b/templates/release/de/vehicle/hyundai-bluelink.yaml @@ -0,0 +1,161 @@ +template: hyundai +product: + identifier: hyundai-bluelink + brand: Hyundai + description: Bluelink +description: | + Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. +render: + - default: | + type: template + template: hyundai + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + language: en # Sprache, [en, de] (optional) + advanced: | + type: template + template: hyundai + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + language: en # Sprache, [en, de] (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: language + example: + default: en + choice: ['en', 'de'] + unit: + description: Sprache + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/hyundai_0.yaml b/templates/release/de/vehicle/hyundai_0.yaml deleted file mode 100644 index 8d6e6900ac..0000000000 --- a/templates/release/de/vehicle/hyundai_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Hyundai - description: Bluelink -description: | - Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. -render: - - default: | - type: template - template: hyundai - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - language: en # Sprache, [en, de] (optional) - advanced: | - type: template - template: hyundai - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - language: en # Sprache, [en, de] (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/ioBroker.bmw_0.yaml b/templates/release/de/vehicle/ioBroker.bmw_0.yaml deleted file mode 100644 index cdc3a16d93..0000000000 --- a/templates/release/de/vehicle/ioBroker.bmw_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - description: ioBroker.bmw - group: Generische Unterstützung -description: | - ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api -render: - - default: | - type: template - template: ioBroker.bmw - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - uri: # URI, HTTP(S) Adresse - advanced: | - type: template - template: ioBroker.bmw - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - uri: # URI, HTTP(S) Adresse - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - id: 0 # Instanz-ID (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/iobroker-bmw.yaml b/templates/release/de/vehicle/iobroker-bmw.yaml new file mode 100644 index 0000000000..5ae99e5e14 --- /dev/null +++ b/templates/release/de/vehicle/iobroker-bmw.yaml @@ -0,0 +1,159 @@ +template: ioBroker.bmw +product: + identifier: iobroker-bmw + description: ioBroker.bmw + group: Generische Unterstützung +description: | + ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api +render: + - default: | + type: template + template: ioBroker.bmw + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer + uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse + advanced: | + type: template + template: ioBroker.bmw + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer + uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + id: 0 # Instanz-ID, optional + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: vin + example: WBA8E9G50GM091234 + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: BMW Fahrzeugidentifikationsnummer + advanced: false + optional: false + - name: uri + example: + default: + choice: [] + unit: + description: ioBroker URL einschliesslich ioBroker.simple-api Port + help: HTTP(S) Adresse + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: id + example: + default: 0 + choice: [] + unit: + description: Instanz-ID + help: + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/iso15118.yaml b/templates/release/de/vehicle/iso15118.yaml new file mode 100644 index 0000000000..2f27a10dca --- /dev/null +++ b/templates/release/de/vehicle/iso15118.yaml @@ -0,0 +1,112 @@ +template: iso15118 +product: + identifier: iso15118 + description: ISO15118 + group: Generische Unterstützung +capabilities: ["iso151182"] +description: | + Nur unterstützt wenn das Fahrzeug den Ladestand (Soc) an die verbundene Wallbox übermitteln kann. + Bei Verwendung von ISO15118 mit bestimmten VW Konzernfahrzeugen, z.B. Porsche Taycan, ist zusätzliche Konfiguration + im Fahrzeug erforderlich. Dafür muss ein aktives Ortsbezogenes Ladeprofil mit der niedrigsten Minimalladung (25%) + angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht in den Schalfmodus übergeben. + +render: + - default: | + type: template + template: iso15118 + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: iso15118 + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/iso15118_0.yaml b/templates/release/de/vehicle/iso15118_0.yaml deleted file mode 100644 index 4adfbf8caa..0000000000 --- a/templates/release/de/vehicle/iso15118_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - description: ISO15118 - group: Generische Unterstützung -capabilities: ["iso151182"] -description: | - Nur unterstützt wenn das Fahrzeug den Ladestand (Soc) an die verbundene Wallbox übermitteln kann. - Bei Verwendung von ISO15118 mit bestimmten VW Konzernfahrzeugen, z.B. Porsche Taycan, ist zusätzliche Konfiguration - im Fahrzeug erforderlich. Dafür muss ein aktives Ortsbezogenes Ladeprofil mit der niedrigsten Minimalladung (25%) - angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht in den Schalfmodus übergeben. - -render: - - default: | - type: template - template: iso15118 - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: iso15118 - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/jeep.yaml b/templates/release/de/vehicle/jeep.yaml new file mode 100644 index 0000000000..6e06964dfe --- /dev/null +++ b/templates/release/de/vehicle/jeep.yaml @@ -0,0 +1,178 @@ +template: fiat +product: + identifier: jeep + brand: Jeep +render: + - default: | + type: template + template: fiat + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + advanced: | + type: template + template: fiat + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: ZFAE... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: pin + example: + default: + choice: [] + unit: + description: + help: Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/kia-bluelink.yaml b/templates/release/de/vehicle/kia-bluelink.yaml new file mode 100644 index 0000000000..ccdfe46ac3 --- /dev/null +++ b/templates/release/de/vehicle/kia-bluelink.yaml @@ -0,0 +1,161 @@ +template: kia +product: + identifier: kia-bluelink + brand: Kia + description: Bluelink +description: | + Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. +render: + - default: | + type: template + template: kia + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + language: en # Sprache, [en, de] (optional) + advanced: | + type: template + template: kia + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + language: en # Sprache, [en, de] (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: language + example: + default: en + choice: ['en', 'de'] + unit: + description: Sprache + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/kia_0.yaml b/templates/release/de/vehicle/kia_0.yaml deleted file mode 100644 index 5780583146..0000000000 --- a/templates/release/de/vehicle/kia_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Kia - description: Bluelink -description: | - Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. -render: - - default: | - type: template - template: kia - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - language: en # Sprache, [en, de] (optional) - advanced: | - type: template - template: kia - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - language: en # Sprache, [en, de] (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/mercedes-benz.yaml b/templates/release/de/vehicle/mercedes-benz.yaml new file mode 100644 index 0000000000..2418b582d2 --- /dev/null +++ b/templates/release/de/vehicle/mercedes-benz.yaml @@ -0,0 +1,172 @@ +template: mercedes +product: + identifier: mercedes-benz + brand: Mercedes-Benz +description: | + Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https://tinyurl.com/mbapi2020helptoken. + +render: + - default: | + type: template + template: mercedes + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: mercedes + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: region + example: + default: EMEA + choice: ['EMEA', 'APAC', 'NORAM'] + unit: + description: + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/mercedes_0.yaml b/templates/release/de/vehicle/mercedes_0.yaml deleted file mode 100644 index 095d737099..0000000000 --- a/templates/release/de/vehicle/mercedes_0.yaml +++ /dev/null @@ -1,34 +0,0 @@ -product: - brand: Mercedes-Benz -description: | - Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https://tinyurl.com/mbapi2020helptoken. - -render: - - default: | - type: template - template: mercedes - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: mercedes - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/mg.yaml b/templates/release/de/vehicle/mg.yaml new file mode 100644 index 0000000000..f50f56d0ab --- /dev/null +++ b/templates/release/de/vehicle/mg.yaml @@ -0,0 +1,157 @@ +template: mg +product: + identifier: mg + brand: MG +render: + - default: | + type: template + template: mg + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: mg + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + region: EU # Region, [EU, AU] +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: region + example: + default: EU + choice: ['EU', 'AU'] + unit: + description: Region + help: + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/de/vehicle/mg2mqtt.yaml b/templates/release/de/vehicle/mg2mqtt.yaml new file mode 100644 index 0000000000..74550ea3bb --- /dev/null +++ b/templates/release/de/vehicle/mg2mqtt.yaml @@ -0,0 +1,140 @@ +template: mg2mqtt +product: + identifier: mg2mqtt + description: mg2mqtt + group: Generische Unterstützung +description: | + Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway oder https://github.com/SAIC-iSmart-API/saic-java-client) +render: + - default: | + type: template + template: mg2mqtt + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + timeout: 1h # Zeitüberschreitung, optional + advanced: | + type: template + template: mg2mqtt + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + timeout: 1h # Zeitüberschreitung, optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 1h + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/mg2mqtt_0.yaml b/templates/release/de/vehicle/mg2mqtt_0.yaml deleted file mode 100644 index 4d010db657..0000000000 --- a/templates/release/de/vehicle/mg2mqtt_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: mg2mqtt - group: Generische Unterstützung -description: | - Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway oder https://github.com/SAIC-iSmart-API/saic-java-client) -render: - - default: | - type: template - template: mg2mqtt - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - timeout: 1h # Zeitüberschreitung, optional - advanced: | - type: template - template: mg2mqtt - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - timeout: 1h # Zeitüberschreitung, optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/mg_0.yaml b/templates/release/de/vehicle/mg_0.yaml deleted file mode 100644 index 801c70bb8f..0000000000 --- a/templates/release/de/vehicle/mg_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: MG -render: - - default: | - type: template - template: mg - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: mg - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - region: EU # Region, [EU, AU] diff --git a/templates/release/de/vehicle/mini.yaml b/templates/release/de/vehicle/mini.yaml new file mode 100644 index 0000000000..3381139fbf --- /dev/null +++ b/templates/release/de/vehicle/mini.yaml @@ -0,0 +1,191 @@ +template: mini +product: + identifier: mini + brand: Mini +description: | + Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. + +render: + - default: | + type: template + template: mini + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + hcaptcha: + advanced: | + type: template + template: mini + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + hcaptcha: + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + region: EU # Region, [EU, NA] + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: WBMW... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: hcaptcha + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: region + example: + default: EU + choice: ['EU', 'NA'] + unit: + description: Region + help: + advanced: true + optional: false + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/mini_0.yaml b/templates/release/de/vehicle/mini_0.yaml deleted file mode 100644 index 556ef1206f..0000000000 --- a/templates/release/de/vehicle/mini_0.yaml +++ /dev/null @@ -1,35 +0,0 @@ -product: - brand: Mini -description: | - Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. - -render: - - default: | - type: template - template: mini - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: - advanced: | - type: template - template: mini - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - region: EU # Region, [EU, NA] - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/mz2mqtt.yaml b/templates/release/de/vehicle/mz2mqtt.yaml new file mode 100644 index 0000000000..382c0e69dd --- /dev/null +++ b/templates/release/de/vehicle/mz2mqtt.yaml @@ -0,0 +1,128 @@ +template: mz2mqtt +product: + identifier: mz2mqtt + description: mz2mqtt + group: Generische Unterstützung +description: | + myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mqtt Installation https://github.com/C64Axel/mz2mqtt. +render: + - default: | + type: template + template: mz2mqtt + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: | + type: template + template: mz2mqtt + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + timeout: 720h # Zeitüberschreitung, optional +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: timeout + example: 10s + default: 720h + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/mz2mqtt_0.yaml b/templates/release/de/vehicle/mz2mqtt_0.yaml deleted file mode 100644 index 555893907d..0000000000 --- a/templates/release/de/vehicle/mz2mqtt_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - description: mz2mqtt - group: Generische Unterstützung -description: | - myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mqtt Installation https://github.com/C64Axel/mz2mqtt. -render: - - default: | - type: template - template: mz2mqtt - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - advanced: | - type: template - template: mz2mqtt - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - timeout: 720h # Zeitüberschreitung, optional diff --git a/templates/release/de/vehicle/nissan-ariya.yaml b/templates/release/de/vehicle/nissan-ariya.yaml new file mode 100644 index 0000000000..31d15a0905 --- /dev/null +++ b/templates/release/de/vehicle/nissan-ariya.yaml @@ -0,0 +1,148 @@ +template: nissan-ariya +product: + identifier: nissan-ariya + brand: Nissan + description: Ariya +render: + - default: | + type: template + template: nissan-ariya + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: nissan-ariya + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/nissan-ariya_0.yaml b/templates/release/de/vehicle/nissan-ariya_0.yaml deleted file mode 100644 index 7375f4a679..0000000000 --- a/templates/release/de/vehicle/nissan-ariya_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nissan - description: Ariya -render: - - default: | - type: template - template: nissan-ariya - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: nissan-ariya - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/nissan-leaf-pre-2019.yaml b/templates/release/de/vehicle/nissan-leaf-pre-2019.yaml new file mode 100644 index 0000000000..dd53859d64 --- /dev/null +++ b/templates/release/de/vehicle/nissan-leaf-pre-2019.yaml @@ -0,0 +1,148 @@ +template: carwings +product: + identifier: nissan-leaf-pre-2019 + brand: Nissan + description: Leaf (pre 2019) +render: + - default: | + type: template + template: carwings + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: carwings + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/nissan-leaf.yaml b/templates/release/de/vehicle/nissan-leaf.yaml new file mode 100644 index 0000000000..0c80b9b792 --- /dev/null +++ b/templates/release/de/vehicle/nissan-leaf.yaml @@ -0,0 +1,148 @@ +template: nissan +product: + identifier: nissan-leaf + brand: Nissan + description: Leaf +render: + - default: | + type: template + template: nissan + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: nissan + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/nissan_0.yaml b/templates/release/de/vehicle/nissan_0.yaml deleted file mode 100644 index 6f2817324e..0000000000 --- a/templates/release/de/vehicle/nissan_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nissan - description: Leaf -render: - - default: | - type: template - template: nissan - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: nissan - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/niu-e-scooter.yaml b/templates/release/de/vehicle/niu-e-scooter.yaml new file mode 100644 index 0000000000..6561f215e4 --- /dev/null +++ b/templates/release/de/vehicle/niu-e-scooter.yaml @@ -0,0 +1,71 @@ +template: niu-e-scooter +product: + identifier: niu-e-scooter + brand: NIU + description: E-Scooter + group: Scooter +render: + - default: | + type: template + template: niu-e-scooter + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + icon: scooter # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + serial: # Scooter Seriennummer, wie in der NIU app angegeben + capacity: 4 # Akkukapazität (kWh), optional +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: icon + example: + default: scooter + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Scooter Seriennummer, wie in der NIU app angegeben + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: 4 + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/niu-e-scooter_0.yaml b/templates/release/de/vehicle/niu-e-scooter_0.yaml deleted file mode 100644 index d4de382706..0000000000 --- a/templates/release/de/vehicle/niu-e-scooter_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: NIU - description: E-Scooter - group: Scooter -render: - - default: | - type: template - template: niu-e-scooter - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - icon: scooter # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - serial: # Scooter Seriennummer, wie in der NIU app angegeben - capacity: 4 # Akkukapazität (kWh), optional diff --git a/templates/release/de/vehicle/offline_0.yaml b/templates/release/de/vehicle/offline_0.yaml deleted file mode 100644 index 3bbe09e4ea..0000000000 --- a/templates/release/de/vehicle/offline_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - description: Generisches Fahrzeug (ohne API) - group: Generische Unterstützung -render: - - default: | - type: template - template: offline - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: offline - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/opel.yaml b/templates/release/de/vehicle/opel.yaml new file mode 100644 index 0000000000..6309f74fd8 --- /dev/null +++ b/templates/release/de/vehicle/opel.yaml @@ -0,0 +1,161 @@ +template: opel +product: + identifier: opel + brand: Opel +description: | + Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + +render: + - default: | + type: template + template: opel + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: opel + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/opel_0.yaml b/templates/release/de/vehicle/opel_0.yaml deleted file mode 100644 index b4bc929c89..0000000000 --- a/templates/release/de/vehicle/opel_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Opel -description: | - Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. - -render: - - default: | - type: template - template: opel - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: opel - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/open-vehicle-monitoring-system.yaml b/templates/release/de/vehicle/open-vehicle-monitoring-system.yaml new file mode 100644 index 0000000000..548ac255c8 --- /dev/null +++ b/templates/release/de/vehicle/open-vehicle-monitoring-system.yaml @@ -0,0 +1,160 @@ +template: ovms +product: + identifier: open-vehicle-monitoring-system + description: Open Vehicle Monitoring System + group: Generische Unterstützung +description: | + Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei [Open Vehicle Monitoring System](http://api.openvehicles.com/). +render: + - default: | + type: template + template: ovms + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vehicleid: + advanced: | + type: template + template: ovms + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vehicleid: + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + server: dexters-web.de + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vehicleid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: server + example: + default: dexters-web.de + choice: [] + unit: + description: + help: + advanced: true + optional: false + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/ovms_0.yaml b/templates/release/de/vehicle/ovms_0.yaml deleted file mode 100644 index 9e566a9596..0000000000 --- a/templates/release/de/vehicle/ovms_0.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - description: Open Vehicle Monitoring System - group: Generische Unterstützung -description: | - Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei [Open Vehicle Monitoring System](http://api.openvehicles.com/). -render: - - default: | - type: template - template: ovms - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vehicleid: - advanced: | - type: template - template: ovms - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vehicleid: - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - server: dexters-web.de - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/peugeot.yaml b/templates/release/de/vehicle/peugeot.yaml new file mode 100644 index 0000000000..ecdf2f5d34 --- /dev/null +++ b/templates/release/de/vehicle/peugeot.yaml @@ -0,0 +1,161 @@ +template: peugeot +product: + identifier: peugeot + brand: Peugeot +description: | + Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + +render: + - default: | + type: template + template: peugeot + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: peugeot + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/peugeot_0.yaml b/templates/release/de/vehicle/peugeot_0.yaml deleted file mode 100644 index d787bcc5a2..0000000000 --- a/templates/release/de/vehicle/peugeot_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Peugeot -description: | - Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. - -render: - - default: | - type: template - template: peugeot - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: peugeot - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/polestar.yaml b/templates/release/de/vehicle/polestar.yaml new file mode 100644 index 0000000000..36ecc2fea3 --- /dev/null +++ b/templates/release/de/vehicle/polestar.yaml @@ -0,0 +1,148 @@ +template: polestar +product: + identifier: polestar + brand: Polestar +requirements: ["skiptest"] +render: + - default: | + type: template + template: polestar + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: LPSVS... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: polestar + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: LPSVS... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: LPSVS... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/polestar_0.yaml b/templates/release/de/vehicle/polestar_0.yaml deleted file mode 100644 index 6263d897fe..0000000000 --- a/templates/release/de/vehicle/polestar_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Polestar -requirements: ["skiptest"] -render: - - default: | - type: template - template: polestar - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: LPSVS... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: polestar - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: LPSVS... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/psa-car-controller.yaml b/templates/release/de/vehicle/psa-car-controller.yaml new file mode 100644 index 0000000000..95851e5eca --- /dev/null +++ b/templates/release/de/vehicle/psa-car-controller.yaml @@ -0,0 +1,139 @@ +template: flobz +product: + identifier: psa-car-controller + description: PSA Car Controller + group: Generische Unterstützung +description: | + Remote Control of PSA car https://github.com/flobz/psa_car_controller +render: + - default: | + type: template + template: flobz + url: http://192.0.2.2 + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: flobz + url: http://192.0.2.2 + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + wakeup_alt: false # alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. (optional) +params: + - name: url + example: http://192.0.2.2 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: wakeup_alt + example: + default: false + choice: [] + unit: + description: + help: alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/renault.yaml b/templates/release/de/vehicle/renault.yaml new file mode 100644 index 0000000000..657ee2d145 --- /dev/null +++ b/templates/release/de/vehicle/renault.yaml @@ -0,0 +1,157 @@ +template: renault +product: + identifier: renault + brand: Renault +render: + - default: | + type: template + template: renault + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WREN... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: renault + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WREN... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + wakeupmode: default # Aufweckmechanismus, [default, alternative, MY24] (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: WREN... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: wakeupmode + example: + default: default + choice: ['default', 'alternative', 'MY24'] + unit: + description: Aufweckmechanismus + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/renault_0.yaml b/templates/release/de/vehicle/renault_0.yaml deleted file mode 100644 index 561d974716..0000000000 --- a/templates/release/de/vehicle/renault_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Renault -render: - - default: | - type: template - template: renault - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WREN... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: renault - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WREN... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - wakeupmode: default # Aufweckmechanismus, [default, alternative, MY24] (optional) diff --git a/templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml b/templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml new file mode 100644 index 0000000000..363ce018be --- /dev/null +++ b/templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml @@ -0,0 +1,148 @@ +template: seat +product: + identifier: seat-cupraconnect-gen3-ateca-leon-formentor-tarraco + brand: Seat + description: CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) +render: + - default: | + type: template + template: seat + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: seat + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml b/templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml new file mode 100644 index 0000000000..6223fe45f6 --- /dev/null +++ b/templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml @@ -0,0 +1,168 @@ +template: cupra +product: + identifier: seat-cupraconnect-gen4-born-formentor-tavascan + brand: Seat + description: CupraConnect Gen4 (Born, Formentor, Tavascan) +render: + - default: | + type: template + template: cupra + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: cupra + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/seat_0.yaml b/templates/release/de/vehicle/seat_0.yaml deleted file mode 100644 index f33ff938d5..0000000000 --- a/templates/release/de/vehicle/seat_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Seat - description: CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) -render: - - default: | - type: template - template: seat - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: seat - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/skoda-enyaq.yaml b/templates/release/de/vehicle/skoda-enyaq.yaml new file mode 100644 index 0000000000..c1caa1cf34 --- /dev/null +++ b/templates/release/de/vehicle/skoda-enyaq.yaml @@ -0,0 +1,159 @@ +template: enyaq +product: + identifier: skoda-enyaq + brand: Skoda + description: Enyaq +render: + - default: | + type: template + template: enyaq + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: enyaq + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + timeout: 10s # Zeitüberschreitung, optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 10s + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/smart-1.yaml b/templates/release/de/vehicle/smart-1.yaml new file mode 100644 index 0000000000..fa7e38303d --- /dev/null +++ b/templates/release/de/vehicle/smart-1.yaml @@ -0,0 +1,168 @@ +template: smart-hello +product: + identifier: smart-1 + brand: Smart + description: #1 +render: + - default: | + type: template + template: smart-hello + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: smart-hello + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/smart-eq.yaml b/templates/release/de/vehicle/smart-eq.yaml new file mode 100644 index 0000000000..2232c320a5 --- /dev/null +++ b/templates/release/de/vehicle/smart-eq.yaml @@ -0,0 +1,173 @@ +template: smart +product: + identifier: smart-eq + brand: Smart + description: EQ +description: | + Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. + +render: + - default: | + type: template + template: smart + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: smart + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: region + example: + default: EMEA + choice: ['EMEA', 'APAC', 'NORAM'] + unit: + description: + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/smart-hello_0.yaml b/templates/release/de/vehicle/smart-hello_0.yaml deleted file mode 100644 index db5745bf05..0000000000 --- a/templates/release/de/vehicle/smart-hello_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Smart - description: #1 -render: - - default: | - type: template - template: smart-hello - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: smart-hello - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/smart_0.yaml b/templates/release/de/vehicle/smart_0.yaml deleted file mode 100644 index 2aaeff5c22..0000000000 --- a/templates/release/de/vehicle/smart_0.yaml +++ /dev/null @@ -1,35 +0,0 @@ -product: - brand: Smart - description: EQ -description: | - Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. - -render: - - default: | - type: template - template: smart - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: smart - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/tesla-ble.yaml b/templates/release/de/vehicle/tesla-ble.yaml new file mode 100644 index 0000000000..1f6e70b1bd --- /dev/null +++ b/templates/release/de/vehicle/tesla-ble.yaml @@ -0,0 +1,140 @@ +template: tesla-ble +product: + identifier: tesla-ble + description: Tesla BLE + group: Generische Unterstützung +description: | + Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy +render: + - default: | + type: template + template: tesla-ble + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung + url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy + port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional) + advanced: | + type: template + template: tesla-ble + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung + url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy + port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Erforderlich für BLE-Verbindung + advanced: false + optional: false + - name: url + example: http://192.168.178.27 + default: + choice: [] + unit: + description: + help: URL des Tesla BLE HTTP Proxy + advanced: false + optional: false + - name: port + example: 8080 + default: 8080 + choice: [] + unit: + description: Port + help: Port des Tesla BLE HTTP Proxy + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/tesla-ble_0.yaml b/templates/release/de/vehicle/tesla-ble_0.yaml deleted file mode 100644 index 5f4093073c..0000000000 --- a/templates/release/de/vehicle/tesla-ble_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: Tesla BLE - group: Generische Unterstützung -description: | - Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy -render: - - default: | - type: template - template: tesla-ble - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung - url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy - port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional) - advanced: | - type: template - template: tesla-ble - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung - url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy - port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/tesla.yaml b/templates/release/de/vehicle/tesla.yaml new file mode 100644 index 0000000000..663ee1253d --- /dev/null +++ b/templates/release/de/vehicle/tesla.yaml @@ -0,0 +1,195 @@ +template: tesla +product: + identifier: tesla + brand: Tesla +requirements: ["skiptest"] +description: | + Tesla bietet eine offizielle, aber kostenpflichtige Fahrzeug-API an. + Für private Nutzung kannst du dir einen [Tesla Developer Account](https://developer.tesla.com/) erstellen und erhältst ein monatliches API-Guthaben von 10 €. + Das ist für die gängigen evcc-Anwendungsfälle in der Regel ausreichend. + + Die Anleitung von [myteslamate.com](https://www.myteslamate.com/tesla-api-application-registration/) erklärt den Prozess und generiert dir kostenfrei die für evcc benötigten Access- und Refresh-Token. + Mit diesem Tokenpaar und deiner im Tesla Developer Account erstellten Client ID kann evcc direkt mit der Tesla API kommunizieren. + Dein verbrauchtes Guthaben kannst du im Tesla Developer Dashboard einsehen. + + Für die Nutzung des Tesla Wall Connectors benötigst du einen öffentlichen Command-Proxy-Server. + [myteslamate.com](https://app.myteslamate.com/) stellt diesen Dienst kostenpflichtig (nutzungsbasiert) zur Verfügung. + Konfiguriere dafür bei myteslamate.com die Command-Berechtigungen und trage das Proxy-Token hier ein. + Start-, Stopp- und Stromstärken-Kommandos werden über diesen Proxy an Tesla geschickt. + + Weitere Informationen und Alternativen findest du in [unserem Blogbeitrag](https://docs.evcc.io/blog/2025/01/20/tesla-api-update). + +render: + - default: | + type: template + template: tesla + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: tesla + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + commandProxy: https://api.myteslamate.com # Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) + proxyToken: # Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: clientId + example: + default: + choice: [] + unit: + description: + help: Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: von [myteslamate.com](https://app.myteslamate.com/). + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: von [myteslamate.com](https://app.myteslamate.com/). + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: commandProxy + example: + default: https://api.myteslamate.com + choice: [] + unit: + description: + help: Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. + advanced: true + optional: true + - name: proxyToken + example: + default: + choice: [] + unit: + description: + help: Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/tesla_0.yaml b/templates/release/de/vehicle/tesla_0.yaml deleted file mode 100644 index 35fd503040..0000000000 --- a/templates/release/de/vehicle/tesla_0.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Tesla -requirements: ["skiptest"] -description: | - Tesla bietet eine offizielle, aber kostenpflichtige Fahrzeug-API an. - Für private Nutzung kannst du dir einen [Tesla Developer Account](https://developer.tesla.com/) erstellen und erhältst ein monatliches API-Guthaben von 10 €. - Das ist für die gängigen evcc-Anwendungsfälle in der Regel ausreichend. - - Die Anleitung von [myteslamate.com](https://www.myteslamate.com/tesla-api-application-registration/) erklärt den Prozess und generiert dir kostenfrei die für evcc benötigten Access- und Refresh-Token. - Mit diesem Tokenpaar und deiner im Tesla Developer Account erstellten Client ID kann evcc direkt mit der Tesla API kommunizieren. - Dein verbrauchtes Guthaben kannst du im Tesla Developer Dashboard einsehen. - - Für die Nutzung des Tesla Wall Connectors benötigst du einen öffentlichen Command-Proxy-Server. - [myteslamate.com](https://app.myteslamate.com/) stellt diesen Dienst kostenpflichtig (nutzungsbasiert) zur Verfügung. - Konfiguriere dafür bei myteslamate.com die Command-Berechtigungen und trage das Proxy-Token hier ein. - Start-, Stopp- und Stromstärken-Kommandos werden über diesen Proxy an Tesla geschickt. - - Weitere Informationen und Alternativen findest du in [unserem Blogbeitrag](https://docs.evcc.io/blog/2025/01/20/tesla-api-update). - -render: - - default: | - type: template - template: tesla - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: tesla - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - commandProxy: https://api.myteslamate.com # Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) - proxyToken: # Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/teslalogger.yaml b/templates/release/de/vehicle/teslalogger.yaml new file mode 100644 index 0000000000..de2ba86769 --- /dev/null +++ b/templates/release/de/vehicle/teslalogger.yaml @@ -0,0 +1,140 @@ +template: teslalogger +product: + identifier: teslalogger + description: TeslaLogger + group: Generische Unterstützung +description: | + Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger +render: + - default: | + type: template + template: teslalogger + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + id: 1 # TeslaLogger CarID, optional + url: http://192.0.2.2 + port: 5000 # Port, optional + advanced: | + type: template + template: teslalogger + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + id: 1 # TeslaLogger CarID, optional + url: http://192.0.2.2 + port: 5000 # Port, optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: id + example: + default: 1 + choice: [] + unit: + description: TeslaLogger CarID + help: + advanced: false + optional: true + - name: url + example: http://192.0.2.2 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: port + example: 5000 + default: 5000 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/teslalogger_0.yaml b/templates/release/de/vehicle/teslalogger_0.yaml deleted file mode 100644 index 3d9e7e1a92..0000000000 --- a/templates/release/de/vehicle/teslalogger_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: TeslaLogger - group: Generische Unterstützung -description: | - Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger -render: - - default: | - type: template - template: teslalogger - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 - port: 5000 # Port, optional - advanced: | - type: template - template: teslalogger - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 - port: 5000 # Port, optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/teslamate.yaml b/templates/release/de/vehicle/teslamate.yaml new file mode 100644 index 0000000000..3d4e07f24d --- /dev/null +++ b/templates/release/de/vehicle/teslamate.yaml @@ -0,0 +1,118 @@ +template: teslamate +product: + identifier: teslamate + description: TeslaMate + group: Generische Unterstützung +description: | + Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Voraussetzung ist konfigurierter MQTT Broker. +render: + - default: | + type: template + template: teslamate + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + id: 1 # Fahrzeug-ID, optional + advanced: | + type: template + template: teslamate + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + id: 1 # Fahrzeug-ID, optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: id + example: + default: 1 + choice: [] + unit: + description: Fahrzeug-ID + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/teslamate_0.yaml b/templates/release/de/vehicle/teslamate_0.yaml deleted file mode 100644 index a15ba084e3..0000000000 --- a/templates/release/de/vehicle/teslamate_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: TeslaMate - group: Generische Unterstützung -description: | - Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Voraussetzung ist konfigurierter MQTT Broker. -render: - - default: | - type: template - template: teslamate - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - id: 1 # Fahrzeug-ID, optional - advanced: | - type: template - template: teslamate - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - id: 1 # Fahrzeug-ID, optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/tessie.yaml b/templates/release/de/vehicle/tessie.yaml new file mode 100644 index 0000000000..b4e4566bd7 --- /dev/null +++ b/templates/release/de/vehicle/tessie.yaml @@ -0,0 +1,129 @@ +template: tessie +product: + identifier: tessie + description: Tessie + group: Generische Unterstützung +description: | + Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug niemals aufwecken; das Polling kann auf „always“ und interval „1M“ eingestellt werden. Wenn das Fahrzeug wach ist, sind die Daten normalerweise weniger als 15 Sekunden alt. Wenn das Fahrzeug schläft, stammen die Daten aus dem Zeitpunkt, zu dem es eingeschlafen ist. Holen Sie sich Ihr Token unter https://dash.tessie.com/settings/api +render: + - default: | + type: template + template: tessie + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeug-VIN, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + token: # Tessie API Token + advanced: | + type: template + template: tessie + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeug-VIN, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + token: # Tessie API Token + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeug-VIN + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Tessie API Token + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/tessie_0.yaml b/templates/release/de/vehicle/tessie_0.yaml deleted file mode 100644 index 2ad484f0b5..0000000000 --- a/templates/release/de/vehicle/tessie_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - description: Tessie - group: Generische Unterstützung -description: | - Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug niemals aufwecken; das Polling kann auf „always“ und interval „1M“ eingestellt werden. Wenn das Fahrzeug wach ist, sind die Daten normalerweise weniger als 15 Sekunden alt. Wenn das Fahrzeug schläft, stammen die Daten aus dem Zeitpunkt, zu dem es eingeschlafen ist. Holen Sie sich Ihr Token unter https://dash.tessie.com/settings/api -render: - - default: | - type: template - template: tessie - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeug-VIN, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - token: # Tessie API Token - advanced: | - type: template - template: tessie - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeug-VIN, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - token: # Tessie API Token - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/toyota.yaml b/templates/release/de/vehicle/toyota.yaml new file mode 100644 index 0000000000..3581408db7 --- /dev/null +++ b/templates/release/de/vehicle/toyota.yaml @@ -0,0 +1,150 @@ +template: toyota +product: + identifier: toyota + brand: Toyota +description: | + Benötigt Toyota Connected Services Account. + +render: + - default: | + type: template + template: toyota + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: JT... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: toyota + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: JT... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: JT... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/toyota_0.yaml b/templates/release/de/vehicle/toyota_0.yaml deleted file mode 100644 index 90c811706b..0000000000 --- a/templates/release/de/vehicle/toyota_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Toyota -description: | - Benötigt Toyota Connected Services Account. - -render: - - default: | - type: template - template: toyota - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: JT... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: toyota - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: JT... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/tronity.yaml b/templates/release/de/vehicle/tronity.yaml new file mode 100644 index 0000000000..83086466e5 --- /dev/null +++ b/templates/release/de/vehicle/tronity.yaml @@ -0,0 +1,149 @@ +template: tronity +product: + identifier: tronity + description: Tronity + group: Generische Unterstützung +requirements: ["sponsorship"] +render: + - default: | + type: template + template: tronity + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + clientid: # Tronity API Client ID, Einrichtung unter https://app.tronity.tech + clientsecret: # Tronity API Client Secret, Einrichtung unter https://app.tronity.tech + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: tronity + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + clientid: # Tronity API Client ID, Einrichtung unter https://app.tronity.tech + clientsecret: # Tronity API Client Secret, Einrichtung unter https://app.tronity.tech + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: clientid + example: + default: + choice: [] + unit: + description: Tronity API Client ID + help: Einrichtung unter https://app.tronity.tech + advanced: false + optional: false + - name: clientsecret + example: + default: + choice: [] + unit: + description: Tronity API Client Secret + help: Einrichtung unter https://app.tronity.tech + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/tronity_0.yaml b/templates/release/de/vehicle/tronity_0.yaml deleted file mode 100644 index bda3aba39c..0000000000 --- a/templates/release/de/vehicle/tronity_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: Tronity - group: Generische Unterstützung -requirements: ["sponsorship"] -render: - - default: | - type: template - template: tronity - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - clientid: # Tronity API Client ID, Einrichtung unter https://app.tronity.tech - clientsecret: # Tronity API Client Secret, Einrichtung unter https://app.tronity.tech - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: tronity - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - clientid: # Tronity API Client ID, Einrichtung unter https://app.tronity.tech - clientsecret: # Tronity API Client Secret, Einrichtung unter https://app.tronity.tech - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/de/vehicle/volkswagen-we-connect-id.yaml b/templates/release/de/vehicle/volkswagen-we-connect-id.yaml new file mode 100644 index 0000000000..5cfa81e579 --- /dev/null +++ b/templates/release/de/vehicle/volkswagen-we-connect-id.yaml @@ -0,0 +1,181 @@ +template: vw +product: + identifier: volkswagen-we-connect-id + brand: Volkswagen + description: We Connect ID +description: | + e-Golf, e-Up, ID Familie +render: + - default: | + type: template + template: vw + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WVWZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + timeout: 10s # Zeitüberschreitung, optional + advanced: | + type: template + template: vw + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: WVWZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + timeout: 10s # Zeitüberschreitung, optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) + coarsecurrent: # 1A Ladestromvorgabe, Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe (optional) + welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: WVWZZZ... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 10s + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A Ladestromvorgabe + help: Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Laden bei Verbindung + help: Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/volvo-connected_0.yaml b/templates/release/de/vehicle/volvo-connected_0.yaml deleted file mode 100644 index a6e03e48da..0000000000 --- a/templates/release/de/vehicle/volvo-connected_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Volvo -description: | - Für die Nutzung mit EVCC benötigst du einen Volvo Account und einen Volvo Connected Car API Key. - Erstelle dazu auf der [Account Seite](https://developer.volvocars.com/account/) eine neue Applikation und speichere den primären VCC API Key ab. - Veröffentliche nun deine Applikation und wähle unter "Scopes" die Berechtigungen "Connected Vehicle API -> conve:vehicle-relation" und "Energy API -> (alles)" aus. - Als Redirect URL musst du die URL deiner EVCC Instanz eintragen, zb "http://evcc.local:7070/oauth/callback". - Sobald die Applikation erstellt ist, wird sie als "Publication under Review" angezeigt. Das ist nicht weiter schlimm, es funktioniert trotzdem. - Beim Anlegen des Fahrzeugs über die UI wird ein Fehler angezeigt. - Schaue im Log nach der Meldung "registering oauth provider at /oauth/login?..." und öffne den Link "http://evcc.local:7070/oauth/login?..." in einem neuen Tab. - Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Ist die Autorisierung erfolgreich, kann das Fahrzeug hinzugefügt werden. - -render: - - default: | - type: template - template: volvo-connected - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. - vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - advanced: | - type: template - template: volvo-connected - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. - vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/volvo.yaml b/templates/release/de/vehicle/volvo.yaml new file mode 100644 index 0000000000..a226d2ca91 --- /dev/null +++ b/templates/release/de/vehicle/volvo.yaml @@ -0,0 +1,169 @@ +template: volvo-connected +product: + identifier: volvo + brand: Volvo +description: | + Für die Nutzung mit EVCC benötigst du einen Volvo Account und einen Volvo Connected Car API Key. + Erstelle dazu auf der [Account Seite](https://developer.volvocars.com/account/) eine neue Applikation und speichere den primären VCC API Key ab. + Veröffentliche nun deine Applikation und wähle unter "Scopes" die Berechtigungen "Connected Vehicle API -> conve:vehicle-relation" und "Energy API -> (alles)" aus. + Als Redirect URL musst du die URL deiner EVCC Instanz eintragen, zb "http://evcc.local:7070/oauth/callback". + Sobald die Applikation erstellt ist, wird sie als "Publication under Review" angezeigt. Das ist nicht weiter schlimm, es funktioniert trotzdem. + Beim Anlegen des Fahrzeugs über die UI wird ein Fehler angezeigt. + Schaue im Log nach der Meldung "registering oauth provider at /oauth/login?..." und öffne den Link "http://evcc.local:7070/oauth/login?..." in einem neuen Tab. + Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Ist die Autorisierung erfolgreich, kann das Fahrzeug hinzugefügt werden. + +render: + - default: | + type: template + template: volvo-connected + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + advanced: | + type: template + template: volvo-connected + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: vccapikey + example: + default: + choice: [] + unit: + description: + help: VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientId + example: + default: + choice: [] + unit: + description: + help: Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientSecret + example: + default: + choice: [] + unit: + description: + help: Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: redirectUri + example: + default: + choice: [] + unit: + description: + help: 'Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist.' + advanced: false + optional: false + - name: vin + example: WF0FXX... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/volvo2mqtt.yaml b/templates/release/de/vehicle/volvo2mqtt.yaml new file mode 100644 index 0000000000..4f8e5f526b --- /dev/null +++ b/templates/release/de/vehicle/volvo2mqtt.yaml @@ -0,0 +1,129 @@ +template: volvo2mqtt +product: + identifier: volvo2mqtt + description: volvo2mqtt + group: Generische Unterstützung +description: | + Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqtt-Installation https://github.com/Dielee/volvo2mqtt. +render: + - default: | + type: template + template: volvo2mqtt + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + timeout: 720h # Zeitüberschreitung, optional + advanced: | + type: template + template: volvo2mqtt + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + timeout: 720h # Zeitüberschreitung, optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: false + - name: timeout + example: 10s + default: 720h + choice: [] + unit: + description: Zeitüberschreitung + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/volvo2mqtt_0.yaml b/templates/release/de/vehicle/volvo2mqtt_0.yaml deleted file mode 100644 index 2a566108f3..0000000000 --- a/templates/release/de/vehicle/volvo2mqtt_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - description: volvo2mqtt - group: Generische Unterstützung -description: | - Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqtt-Installation https://github.com/Dielee/volvo2mqtt. -render: - - default: | - type: template - template: volvo2mqtt - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - timeout: 720h # Zeitüberschreitung, optional - advanced: | - type: template - template: volvo2mqtt - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind - timeout: 720h # Zeitüberschreitung, optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) diff --git a/templates/release/de/vehicle/vw_0.yaml b/templates/release/de/vehicle/vw_0.yaml deleted file mode 100644 index f44aba9860..0000000000 --- a/templates/release/de/vehicle/vw_0.yaml +++ /dev/null @@ -1,34 +0,0 @@ -product: - brand: Volkswagen - description: We Connect ID -description: | - e-Golf, e-Up, ID Familie -render: - - default: | - type: template - template: vw - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WVWZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - timeout: 10s # Zeitüberschreitung, optional - advanced: | - type: template - template: vw - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: WVWZZZ... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - timeout: 10s # Zeitüberschreitung, optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - coarsecurrent: # Fahrzeug unterstützt nur 1A Schritte der Ladestromvorgabe, 1A Ladestromvorgabe (optional) - welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional) diff --git a/templates/release/de/vehicle/zero-motorcycles.yaml b/templates/release/de/vehicle/zero-motorcycles.yaml new file mode 100644 index 0000000000..1d993229b2 --- /dev/null +++ b/templates/release/de/vehicle/zero-motorcycles.yaml @@ -0,0 +1,147 @@ +template: zero +product: + identifier: zero-motorcycles + brand: Zero Motorcycles +render: + - default: | + type: template + template: zero + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + advanced: | + type: template + template: zero + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen + vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) + title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) + capacity: 50 # Akkukapazität (kWh), optional + icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) + mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) + identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) + priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) + cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Benutzerkonto + help: bspw. E-Mail Adresse, User Id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Passwort + help: Bei führenden Nullen bitte in einfache Hochkommata setzen + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Fahrzeugidentifikationsnummer + help: Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Titel + help: Wird in der Benutzeroberfläche angezeigt + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Akkukapazität + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Wird in der Benutzeroberfläche angezeigt + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximale Phasenanzahl + help: Die maximale Anzahl der Phasen welche genutzt werden können + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist + help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimale Stromstärke + help: Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximale Stromstärke + help: Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identifikation + help: 'Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priorität + help: Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/zero_0.yaml b/templates/release/de/vehicle/zero_0.yaml deleted file mode 100644 index e13f599dbf..0000000000 --- a/templates/release/de/vehicle/zero_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Zero Motorcycles -render: - - default: | - type: template - template: zero - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - advanced: | - type: template - template: zero - user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) - title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) - capacity: 50 # Akkukapazität (kWh), optional - icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) - minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) - identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) - priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) diff --git a/templates/release/en/charger/Kathrein_0.yaml b/templates/release/en/charger/Kathrein_0.yaml deleted file mode 100644 index 3eda50aea9..0000000000 --- a/templates/release/en/charger/Kathrein_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC20 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/Kathrein_1.yaml b/templates/release/en/charger/Kathrein_1.yaml deleted file mode 100644 index c7bd4139ce..0000000000 --- a/templates/release/en/charger/Kathrein_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC35 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/Kathrein_2.yaml b/templates/release/en/charger/Kathrein_2.yaml deleted file mode 100644 index 85c342294c..0000000000 --- a/templates/release/en/charger/Kathrein_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC40 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/Kathrein_3.yaml b/templates/release/en/charger/Kathrein_3.yaml deleted file mode 100644 index 11589d88ef..0000000000 --- a/templates/release/en/charger/Kathrein_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC60 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/Kathrein_4.yaml b/templates/release/en/charger/Kathrein_4.yaml deleted file mode 100644 index e427cae71f..0000000000 --- a/templates/release/en/charger/Kathrein_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC40 E -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/Kathrein_5.yaml b/templates/release/en/charger/Kathrein_5.yaml deleted file mode 100644 index ecab3168ec..0000000000 --- a/templates/release/en/charger/Kathrein_5.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kathrein - description: KWB-AC60 E -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 -render: - - default: | - type: template - template: Kathrein - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/abb-terra-ac-ocpp.yaml b/templates/release/en/charger/abb-terra-ac-ocpp.yaml new file mode 100644 index 0000000000..505840e5b6 --- /dev/null +++ b/templates/release/en/charger/abb-terra-ac-ocpp.yaml @@ -0,0 +1,88 @@ +template: ocpp-abb-tac +product: + identifier: abb-terra-ac-ocpp + brand: ABB + description: Terra AC (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf +render: + - default: | + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-abb-tac + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abb-terra-ac.yaml b/templates/release/en/charger/abb-terra-ac.yaml new file mode 100644 index 0000000000..3ec6b2dc6d --- /dev/null +++ b/templates/release/en/charger/abb-terra-ac.yaml @@ -0,0 +1,52 @@ +template: abb +product: + identifier: abb-terra-ac + brand: ABB + description: Terra AC +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Requires firmware >= 1.6.5 +render: + - default: | + type: template + template: abb + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/abb_0.yaml b/templates/release/en/charger/abb_0.yaml deleted file mode 100644 index 537b90cf5e..0000000000 --- a/templates/release/en/charger/abb_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: ABB - description: Terra AC -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Requires firmware >= 1.6.5 -render: - - default: | - type: template - template: abb - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/abl-em4-single-ocpp.yaml b/templates/release/en/charger/abl-em4-single-ocpp.yaml new file mode 100644 index 0000000000..2a27db733b --- /dev/null +++ b/templates/release/en/charger/abl-em4-single-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-em4-single-ocpp + brand: ABL + description: eM4 Single (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-em4-single-sbcx.yaml b/templates/release/en/charger/abl-em4-single-sbcx.yaml new file mode 100644 index 0000000000..58bf11b5fc --- /dev/null +++ b/templates/release/en/charger/abl-em4-single-sbcx.yaml @@ -0,0 +1,52 @@ +template: abl-em4 +product: + identifier: abl-em4-single-sbcx + brand: ABL + description: eM4 Single (SBCx) +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-em4-twin-ocpp.yaml b/templates/release/en/charger/abl-em4-twin-ocpp.yaml new file mode 100644 index 0000000000..a39d79ae65 --- /dev/null +++ b/templates/release/en/charger/abl-em4-twin-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-em4-twin-ocpp + brand: ABL + description: eM4 Twin (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-em4-twin-sbcx.yaml b/templates/release/en/charger/abl-em4-twin-sbcx.yaml new file mode 100644 index 0000000000..1c06f607cb --- /dev/null +++ b/templates/release/en/charger/abl-em4-twin-sbcx.yaml @@ -0,0 +1,52 @@ +template: abl-em4 +product: + identifier: abl-em4-twin-sbcx + brand: ABL + description: eM4 Twin (SBCx) +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: abl-em4 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-em4_0.yaml b/templates/release/en/charger/abl-em4_0.yaml deleted file mode 100644 index 59227336be..0000000000 --- a/templates/release/en/charger/abl-em4_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: ABL - description: eM4 (SBCx) -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl-em4 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: abl-em4 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/abl-emh1.yaml b/templates/release/en/charger/abl-emh1.yaml new file mode 100644 index 0000000000..43e451e43f --- /dev/null +++ b/templates/release/en/charger/abl-emh1.yaml @@ -0,0 +1,53 @@ +template: abl +product: + identifier: abl-emh1 + brand: ABL + description: eMH1 +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true +modbus: + baudrate: 38400 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-emh2-ocpp.yaml b/templates/release/en/charger/abl-emh2-ocpp.yaml new file mode 100644 index 0000000000..cf4fde1953 --- /dev/null +++ b/templates/release/en/charger/abl-emh2-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-emh2-ocpp + brand: ABL + description: eMH2 (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-emh2.yaml b/templates/release/en/charger/abl-emh2.yaml new file mode 100644 index 0000000000..78b98d1562 --- /dev/null +++ b/templates/release/en/charger/abl-emh2.yaml @@ -0,0 +1,53 @@ +template: abl +product: + identifier: abl-emh2 + brand: ABL + description: eMH2 +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true +modbus: + baudrate: 38400 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-emh3-ocpp.yaml b/templates/release/en/charger/abl-emh3-ocpp.yaml new file mode 100644 index 0000000000..f90cd7eaf0 --- /dev/null +++ b/templates/release/en/charger/abl-emh3-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-abl +product: + identifier: abl-emh3-ocpp + brand: ABL + description: eMH3 (OCPP) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-abl + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abl_0.yaml b/templates/release/en/charger/abl_0.yaml deleted file mode 100644 index 31dd8d81e7..0000000000 --- a/templates/release/en/charger/abl_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: ABL - description: eMH1 -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional diff --git a/templates/release/en/charger/abl_1.yaml b/templates/release/en/charger/abl_1.yaml deleted file mode 100644 index 5988bc7e0f..0000000000 --- a/templates/release/en/charger/abl_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: ABL - description: eMH2 -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional diff --git a/templates/release/en/charger/abl_2.yaml b/templates/release/en/charger/abl_2.yaml deleted file mode 100644 index ab0c39bbb2..0000000000 --- a/templates/release/en/charger/abl_2.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: SENEC - description: Wallbox pro -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: abl - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional diff --git a/templates/release/en/charger/ac-elwa-2_0.yaml b/templates/release/en/charger/ac-elwa-2_0.yaml deleted file mode 100644 index 47636a7346..0000000000 --- a/templates/release/en/charger/ac-elwa-2_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: my-PV - description: AC ELWA 2 - group: Heating devices -requirements: ["sponsorship"] -render: - - default: | - type: template - template: ac-elwa-2 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - scale: 1 # Scale factor for power limit, optional diff --git a/templates/release/en/charger/ac-thor_0.yaml b/templates/release/en/charger/ac-thor_0.yaml deleted file mode 100644 index cbe0ba9ced..0000000000 --- a/templates/release/en/charger/ac-thor_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: my-PV - description: AC•THOR - group: Heating devices -requirements: ["sponsorship"] -render: - - default: | - type: template - template: ac-thor - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) - scale: 1 # Scale factor for power limit, optional diff --git a/templates/release/en/charger/ac-thor_1.yaml b/templates/release/en/charger/ac-thor_1.yaml deleted file mode 100644 index 34806ba75d..0000000000 --- a/templates/release/en/charger/ac-thor_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: my-PV - description: AC•THOR 9s - group: Heating devices -requirements: ["sponsorship"] -render: - - default: | - type: template - template: ac-thor - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) - scale: 1 # Scale factor for power limit, optional diff --git a/templates/release/en/charger/alfen-eve-ocpp.yaml b/templates/release/en/charger/alfen-eve-ocpp.yaml new file mode 100644 index 0000000000..45494e94f5 --- /dev/null +++ b/templates/release/en/charger/alfen-eve-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-alfen +product: + identifier: alfen-eve-ocpp + brand: Alfen + description: Eve (OCPP) +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-alfen + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/alfen-eve.yaml b/templates/release/en/charger/alfen-eve.yaml new file mode 100644 index 0000000000..58fa1c24e7 --- /dev/null +++ b/templates/release/en/charger/alfen-eve.yaml @@ -0,0 +1,35 @@ +template: alfen +product: + identifier: alfen-eve + brand: Alfen + description: Eve +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The "Active load balancing" license is required for external Modbus control of the charger. Enable "Active Load Balancing" and select "Energy Management System" as Data Source in the configuration. It is recommended to set "ValidityTime" ("TCP/IP EMS" menu) to 300s. When using "Double" charger both loadpoints need to be added. The the first port (or single) is accessable on ID 1, second port on ID 2. +render: + - default: | + type: template + template: alfen + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/alfen_0.yaml b/templates/release/en/charger/alfen_0.yaml deleted file mode 100644 index 66eddbbd3e..0000000000 --- a/templates/release/en/charger/alfen_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Alfen - description: Eve -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The "Active load balancing" license is required for external Modbus control of the charger. Enable "Active Load Balancing" and select "Energy Management System" as Data Source in the configuration. It is recommended to set "ValidityTime" ("TCP/IP EMS" menu) to 300s. When using "Double" charger both loadpoints need to be added. The the first port (or single) is accessable on ID 1, second port on ID 2. -render: - - default: | - type: template - template: alfen - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/alpha-innotec.yaml b/templates/release/en/charger/alpha-innotec.yaml new file mode 100644 index 0000000000..d95a0e30c0 --- /dev/null +++ b/templates/release/en/charger/alpha-innotec.yaml @@ -0,0 +1,63 @@ +template: luxtronik +product: + identifier: alpha-innotec + brand: alpha innotec + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/alphatec-ladesaule-twin.yaml b/templates/release/en/charger/alphatec-ladesaule-twin.yaml new file mode 100644 index 0000000000..c378d83016 --- /dev/null +++ b/templates/release/en/charger/alphatec-ladesaule-twin.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: alphatec-ladesaule-twin + brand: Alphatec + description: Ladesäule Twin +requirements: ["sponsorship"] +description: | + The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/alphatec-wallbox-mini.yaml b/templates/release/en/charger/alphatec-wallbox-mini.yaml new file mode 100644 index 0000000000..641654116a --- /dev/null +++ b/templates/release/en/charger/alphatec-wallbox-mini.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: alphatec-wallbox-mini + brand: Alphatec + description: Wallbox Mini +requirements: ["sponsorship"] +description: | + The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/alphatec-wallbox-power.yaml b/templates/release/en/charger/alphatec-wallbox-power.yaml new file mode 100644 index 0000000000..3abd75d11e --- /dev/null +++ b/templates/release/en/charger/alphatec-wallbox-power.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: alphatec-wallbox-power + brand: Alphatec + description: Wallbox Power +requirements: ["sponsorship"] +description: | + The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/alphatec_0.yaml b/templates/release/en/charger/alphatec_0.yaml deleted file mode 100644 index 653775617a..0000000000 --- a/templates/release/en/charger/alphatec_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Alphatec - description: Wallbox Mini -requirements: ["sponsorship"] -description: | - The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/alphatec_1.yaml b/templates/release/en/charger/alphatec_1.yaml deleted file mode 100644 index cdbf11c5fa..0000000000 --- a/templates/release/en/charger/alphatec_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Alphatec - description: Wallbox Power -requirements: ["sponsorship"] -description: | - The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/alphatec_2.yaml b/templates/release/en/charger/alphatec_2.yaml deleted file mode 100644 index cbb0599898..0000000000 --- a/templates/release/en/charger/alphatec_2.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Alphatec - description: Ladesäule Twin -requirements: ["sponsorship"] -description: | - The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/alphatec_3.yaml b/templates/release/en/charger/alphatec_3.yaml deleted file mode 100644 index b8e74f2bb9..0000000000 --- a/templates/release/en/charger/alphatec_3.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: LRT - description: HOME Essential+ -requirements: ["sponsorship"] -description: | - The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. -render: - - default: | - type: template - template: alphatec - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/amperfied-solar_0.yaml b/templates/release/en/charger/amperfied-solar_0.yaml deleted file mode 100644 index 3a2dc38062..0000000000 --- a/templates/release/en/charger/amperfied-solar_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Amperfied - description: Wallbox connect.solar -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: amperfied-solar - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/amperfied-wallbox-connect-business.yaml b/templates/release/en/charger/amperfied-wallbox-connect-business.yaml new file mode 100644 index 0000000000..9aa1661f93 --- /dev/null +++ b/templates/release/en/charger/amperfied-wallbox-connect-business.yaml @@ -0,0 +1,33 @@ +template: amperfied +product: + identifier: amperfied-wallbox-connect-business + brand: Amperfied + description: Wallbox connect.business +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: amperfied + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/amperfied-wallbox-connect-home.yaml b/templates/release/en/charger/amperfied-wallbox-connect-home.yaml new file mode 100644 index 0000000000..31f18ff3e1 --- /dev/null +++ b/templates/release/en/charger/amperfied-wallbox-connect-home.yaml @@ -0,0 +1,33 @@ +template: amperfied +product: + identifier: amperfied-wallbox-connect-home + brand: Amperfied + description: Wallbox connect.home +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: amperfied + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/amperfied-wallbox-connect-solar.yaml b/templates/release/en/charger/amperfied-wallbox-connect-solar.yaml new file mode 100644 index 0000000000..976171a73b --- /dev/null +++ b/templates/release/en/charger/amperfied-wallbox-connect-solar.yaml @@ -0,0 +1,33 @@ +template: amperfied-solar +product: + identifier: amperfied-wallbox-connect-solar + brand: Amperfied + description: Wallbox connect.solar +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: amperfied-solar + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/amperfied-wallbox-energy-control.yaml b/templates/release/en/charger/amperfied-wallbox-energy-control.yaml new file mode 100644 index 0000000000..5d6ea17fd3 --- /dev/null +++ b/templates/release/en/charger/amperfied-wallbox-energy-control.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: amperfied-wallbox-energy-control + brand: Amperfied + description: Wallbox Energy Control +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/amperfied_0.yaml b/templates/release/en/charger/amperfied_0.yaml deleted file mode 100644 index 98a6dd4e94..0000000000 --- a/templates/release/en/charger/amperfied_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Amperfied - description: Wallbox connect.home -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: amperfied - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/amperfied_1.yaml b/templates/release/en/charger/amperfied_1.yaml deleted file mode 100644 index 630984a204..0000000000 --- a/templates/release/en/charger/amperfied_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Amperfied - description: Wallbox connect.business -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: amperfied - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/ampure-next.yaml b/templates/release/en/charger/ampure-next.yaml new file mode 100644 index 0000000000..e75379d045 --- /dev/null +++ b/templates/release/en/charger/ampure-next.yaml @@ -0,0 +1,34 @@ +template: webasto-next +product: + identifier: ampure-next + brand: Ampure + description: NEXT +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. +render: + - default: | + type: template + template: webasto-next + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/ampure-unite.yaml b/templates/release/en/charger/ampure-unite.yaml new file mode 100644 index 0000000000..7fd4097f24 --- /dev/null +++ b/templates/release/en/charger/ampure-unite.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: ampure-unite + brand: Ampure + description: Unite +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/audi-wallbox-plus.yaml b/templates/release/en/charger/audi-wallbox-plus.yaml new file mode 100644 index 0000000000..2ebb7208ae --- /dev/null +++ b/templates/release/en/charger/audi-wallbox-plus.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: audi-wallbox-plus + brand: Audi + description: Wallbox plus +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/audi-wallbox-pro.yaml b/templates/release/en/charger/audi-wallbox-pro.yaml new file mode 100644 index 0000000000..2fc5f7a839 --- /dev/null +++ b/templates/release/en/charger/audi-wallbox-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: audi-wallbox-pro + brand: Audi + description: Wallbox pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +render: + - default: | + type: template + template: ellipro + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/autel-ac-compact.yaml b/templates/release/en/charger/autel-ac-compact.yaml new file mode 100644 index 0000000000..a3e29d425d --- /dev/null +++ b/templates/release/en/charger/autel-ac-compact.yaml @@ -0,0 +1,94 @@ +template: ocpp-autel +product: + identifier: autel-ac-compact + brand: AUTEL + description: AC Compact +capabilities: ["mA"] +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: + * In the Autel Charge app, click on “OCPP Server” + * In the search bar type “Custom” and select it. + * Server URL: ws://[evcc-address]:8887/ (local network connection) + * Charger ID: Leave empty (for use the serial number) or set custom value which is reused in configuration as *stationid* + * Authorisation Key: leave empty + +render: + - default: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/autel-ac-maxicharger.yaml b/templates/release/en/charger/autel-ac-maxicharger.yaml new file mode 100644 index 0000000000..988a1c35b0 --- /dev/null +++ b/templates/release/en/charger/autel-ac-maxicharger.yaml @@ -0,0 +1,94 @@ +template: ocpp-autel +product: + identifier: autel-ac-maxicharger + brand: AUTEL + description: AC MaxiCharger +capabilities: ["mA"] +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: + * In the Autel Charge app, click on “OCPP Server” + * In the search bar type “Custom” and select it. + * Server URL: ws://[evcc-address]:8887/ (local network connection) + * Charger ID: Leave empty (for use the serial number) or set custom value which is reused in configuration as *stationid* + * Authorisation Key: leave empty + +render: + - default: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-autel + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/autoaid-business-wallbox.yaml b/templates/release/en/charger/autoaid-business-wallbox.yaml new file mode 100644 index 0000000000..d88e519b42 --- /dev/null +++ b/templates/release/en/charger/autoaid-business-wallbox.yaml @@ -0,0 +1,86 @@ +template: ocpp-autoaid +product: + identifier: autoaid-business-wallbox + brand: Autoaid + description: Business Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/autoaid-intelligent-wallbox.yaml b/templates/release/en/charger/autoaid-intelligent-wallbox.yaml new file mode 100644 index 0000000000..7a8e721f02 --- /dev/null +++ b/templates/release/en/charger/autoaid-intelligent-wallbox.yaml @@ -0,0 +1,86 @@ +template: ocpp-autoaid +product: + identifier: autoaid-intelligent-wallbox + brand: Autoaid + description: Intelligent Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-autoaid + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/avm-fritzdect.yaml b/templates/release/en/charger/avm-fritzdect.yaml new file mode 100644 index 0000000000..3c8e9c68ca --- /dev/null +++ b/templates/release/en/charger/avm-fritzdect.yaml @@ -0,0 +1,99 @@ +template: fritzdect +product: + identifier: avm-fritzdect + brand: AVM + description: FritzDECT + group: Switchable sockets +render: + - default: | + type: template + template: fritzdect + uri: https://fritz.box # URI, HTTP(S) address (optional) + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: fritzdect + uri: https://fritz.box # URI, HTTP(S) address (optional) + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: uri + example: + default: https://fritz.box + choice: [] + unit: + description: URI + help: HTTP(S) address + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: ain + example: 307788992233 + default: + choice: [] + unit: + description: Actor Identification Number (AIN) + help: Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/bender-cc612.yaml b/templates/release/en/charger/bender-cc612.yaml new file mode 100644 index 0000000000..e71c6d81d6 --- /dev/null +++ b/templates/release/en/charger/bender-cc612.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: bender-cc612 + brand: Bender + description: CC612 +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/bender-cc613.yaml b/templates/release/en/charger/bender-cc613.yaml new file mode 100644 index 0000000000..e27ab70912 --- /dev/null +++ b/templates/release/en/charger/bender-cc613.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: bender-cc613 + brand: Bender + description: CC613 +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/bender-cc_0.yaml b/templates/release/en/charger/bender-cc_0.yaml deleted file mode 100644 index 2c01dcae76..0000000000 --- a/templates/release/en/charger/bender-cc_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ampure - description: Live -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_1.yaml b/templates/release/en/charger/bender-cc_1.yaml deleted file mode 100644 index bbdfa9886f..0000000000 --- a/templates/release/en/charger/bender-cc_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: CC612 -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_10.yaml b/templates/release/en/charger/bender-cc_10.yaml deleted file mode 100644 index a47eafeb64..0000000000 --- a/templates/release/en/charger/bender-cc_10.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Optec - description: Mobility One -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_11.yaml b/templates/release/en/charger/bender-cc_11.yaml deleted file mode 100644 index ccdf4e27ad..0000000000 --- a/templates/release/en/charger/bender-cc_11.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Garo - description: GLB, GLB+, LS4, LS4 compact -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_12.yaml b/templates/release/en/charger/bender-cc_12.yaml deleted file mode 100644 index 53d289046f..0000000000 --- a/templates/release/en/charger/bender-cc_12.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ensto - description: Chago Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_13.yaml b/templates/release/en/charger/bender-cc_13.yaml deleted file mode 100644 index d9f0a2e1d8..0000000000 --- a/templates/release/en/charger/bender-cc_13.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ubitricity - description: Heinz -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_14.yaml b/templates/release/en/charger/bender-cc_14.yaml deleted file mode 100644 index 57ae464d18..0000000000 --- a/templates/release/en/charger/bender-cc_14.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: CUBOS - description: C11E, C22E -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_15.yaml b/templates/release/en/charger/bender-cc_15.yaml deleted file mode 100644 index 128564141b..0000000000 --- a/templates/release/en/charger/bender-cc_15.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Spelsberg - description: Wallbox Smart Pro -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_2.yaml b/templates/release/en/charger/bender-cc_2.yaml deleted file mode 100644 index db30a4e6f9..0000000000 --- a/templates/release/en/charger/bender-cc_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: CC613 -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_3.yaml b/templates/release/en/charger/bender-cc_3.yaml deleted file mode 100644 index 74181a6273..0000000000 --- a/templates/release/en/charger/bender-cc_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Professional -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_4.yaml b/templates/release/en/charger/bender-cc_4.yaml deleted file mode 100644 index ac29abac3b..0000000000 --- a/templates/release/en/charger/bender-cc_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMEDIO Professional -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_5.yaml b/templates/release/en/charger/bender-cc_5.yaml deleted file mode 100644 index a0e96d6a6e..0000000000 --- a/templates/release/en/charger/bender-cc_5.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON ChargeControl -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_6.yaml b/templates/release/en/charger/bender-cc_6.yaml deleted file mode 100644 index 64465aaeb4..0000000000 --- a/templates/release/en/charger/bender-cc_6.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Webasto - description: Live -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_7.yaml b/templates/release/en/charger/bender-cc_7.yaml deleted file mode 100644 index d6b1df0bb7..0000000000 --- a/templates/release/en/charger/bender-cc_7.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Juice - description: Charger Me -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_8.yaml b/templates/release/en/charger/bender-cc_8.yaml deleted file mode 100644 index 8a3ad1cce0..0000000000 --- a/templates/release/en/charger/bender-cc_8.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: TechniSat - description: Technivolt -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-cc_9.yaml b/templates/release/en/charger/bender-cc_9.yaml deleted file mode 100644 index 9bf575baa6..0000000000 --- a/templates/release/en/charger/bender-cc_9.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ebee - description: Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. -render: - - default: | - type: template - template: bender-cc - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-icc1314.yaml b/templates/release/en/charger/bender-icc1314.yaml new file mode 100644 index 0000000000..ddda4ca25d --- /dev/null +++ b/templates/release/en/charger/bender-icc1314.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: bender-icc1314 + brand: Bender + description: ICC1314 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + The configuration option 'External Energy Management' must be enabled. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/bender-icc1324.yaml b/templates/release/en/charger/bender-icc1324.yaml new file mode 100644 index 0000000000..d7de6d3c99 --- /dev/null +++ b/templates/release/en/charger/bender-icc1324.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: bender-icc1324 + brand: Bender + description: ICC1324 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + The configuration option 'External Energy Management' must be enabled. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/bender-icc_0.yaml b/templates/release/en/charger/bender-icc_0.yaml deleted file mode 100644 index 0fcea4a6c3..0000000000 --- a/templates/release/en/charger/bender-icc_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: ICC1314 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - The configuration option 'External Energy Management' must be enabled. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-icc_1.yaml b/templates/release/en/charger/bender-icc_1.yaml deleted file mode 100644 index d4b1a66135..0000000000 --- a/templates/release/en/charger/bender-icc_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Bender - description: ICC1324 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - The configuration option 'External Energy Management' must be enabled. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-icc_2.yaml b/templates/release/en/charger/bender-icc_2.yaml deleted file mode 100644 index 154f62841c..0000000000 --- a/templates/release/en/charger/bender-icc_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON 4You 500 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - The configuration option 'External Energy Management' must be enabled. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bender-icc_3.yaml b/templates/release/en/charger/bender-icc_3.yaml deleted file mode 100644 index 0722cf5215..0000000000 --- a/templates/release/en/charger/bender-icc_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Mennekes - description: AMTRON 4Business 700 -capabilities: ["rfid", "mA", "1p3p"] -requirements: ["sponsorship"] -description: | - The configuration option 'External Energy Management' must be enabled. -render: - - default: | - type: template - template: bender-icc - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/bmw-i-wallbox.yaml b/templates/release/en/charger/bmw-i-wallbox.yaml new file mode 100644 index 0000000000..8326efb604 --- /dev/null +++ b/templates/release/en/charger/bmw-i-wallbox.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: bmw-i-wallbox + brand: BMW + description: i Wallbox +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/bosch-sg-ready.yaml b/templates/release/en/charger/bosch-sg-ready.yaml new file mode 100644 index 0000000000..16810941b4 --- /dev/null +++ b/templates/release/en/charger/bosch-sg-ready.yaml @@ -0,0 +1,53 @@ +template: emsesp +product: + identifier: bosch-sg-ready + brand: Bosch + description: SG Ready + group: Heating devices +description: | + Integrated via [EMSESP](https://emsesp.org/) +render: + - default: | + type: template + template: emsesp + host: 192.0.2.2 # IP address or hostname + token: # optional + powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) + tempsource: # Temperature source, [warmwater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: powersource + example: + default: hpcurrpower + choice: ['hpcurrpower', 'hppower'] + unit: + description: Power source + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperature source + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/bosch-x-change.yaml b/templates/release/en/charger/bosch-x-change.yaml new file mode 100644 index 0000000000..99d9fcde39 --- /dev/null +++ b/templates/release/en/charger/bosch-x-change.yaml @@ -0,0 +1,46 @@ +template: kermi +product: + identifier: bosch-x-change + brand: Bösch + description: x-change + group: Heating devices +render: + - default: | + type: template + template: kermi + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater, buffer] (optional) + advanced: | + type: template + template: kermi + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater, buffer] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperature source + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml b/templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml new file mode 100644 index 0000000000..324cfb12e1 --- /dev/null +++ b/templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: buderus-logamatic-hmc-20-z + brand: Buderus + description: Logamatic HMC 20 Z + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/buderus-logamatic-hmc-20.yaml b/templates/release/en/charger/buderus-logamatic-hmc-20.yaml new file mode 100644 index 0000000000..a9a1e3a5d5 --- /dev/null +++ b/templates/release/en/charger/buderus-logamatic-hmc-20.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: buderus-logamatic-hmc-20 + brand: Buderus + description: Logamatic HMC 20 + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/buderus-sg-ready.yaml b/templates/release/en/charger/buderus-sg-ready.yaml new file mode 100644 index 0000000000..40dfd311cb --- /dev/null +++ b/templates/release/en/charger/buderus-sg-ready.yaml @@ -0,0 +1,53 @@ +template: emsesp +product: + identifier: buderus-sg-ready + brand: Buderus + description: SG Ready + group: Heating devices +description: | + Integrated via [EMSESP](https://emsesp.org/) +render: + - default: | + type: template + template: emsesp + host: 192.0.2.2 # IP address or hostname + token: # optional + powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) + tempsource: # Temperature source, [warmwater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: powersource + example: + default: hpcurrpower + choice: ['hpcurrpower', 'hppower'] + unit: + description: Power source + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperature source + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/cfos-power-brain-solar.yaml b/templates/release/en/charger/cfos-power-brain-solar.yaml new file mode 100644 index 0000000000..7cbb9cb5c7 --- /dev/null +++ b/templates/release/en/charger/cfos-power-brain-solar.yaml @@ -0,0 +1,28 @@ +template: cfos +product: + identifier: cfos-power-brain-solar + brand: cFos + description: Power Brain Solar +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + S0 meters must be configured separately as charge meter. + Phase switching is only available with the Solar variant and must be enabled by the user: + 1) Home -> disable Load Balancing (Monitoring Mode) + 2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) + +render: + - default: | + type: template + template: cfos + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/cfos-power-brain.yaml b/templates/release/en/charger/cfos-power-brain.yaml new file mode 100644 index 0000000000..f75a0ee626 --- /dev/null +++ b/templates/release/en/charger/cfos-power-brain.yaml @@ -0,0 +1,28 @@ +template: cfos +product: + identifier: cfos-power-brain + brand: cFos + description: Power Brain +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + S0 meters must be configured separately as charge meter. + Phase switching is only available with the Solar variant and must be enabled by the user: + 1) Home -> disable Load Balancing (Monitoring Mode) + 2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) + +render: + - default: | + type: template + template: cfos + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/cfos_0.yaml b/templates/release/en/charger/cfos_0.yaml deleted file mode 100644 index 1321c0f642..0000000000 --- a/templates/release/en/charger/cfos_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: cFos - description: Power Brain -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - S0 meters must be configured separately as charge meter. - Phase switching is only available with the Solar variant and must be enabled by the user: - 1) Home -> disable Load Balancing (Monitoring Mode) - 2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) - -render: - - default: | - type: template - template: cfos - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/cfos_1.yaml b/templates/release/en/charger/cfos_1.yaml deleted file mode 100644 index bf6800e7c4..0000000000 --- a/templates/release/en/charger/cfos_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: cFos - description: Power Brain Solar -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - S0 meters must be configured separately as charge meter. - Phase switching is only available with the Solar variant and must be enabled by the user: - 1) Home -> disable Load Balancing (Monitoring Mode) - 2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) - -render: - - default: | - type: template - template: cfos - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/charge-amps-halo.yaml b/templates/release/en/charger/charge-amps-halo.yaml new file mode 100644 index 0000000000..15983194fe --- /dev/null +++ b/templates/release/en/charger/charge-amps-halo.yaml @@ -0,0 +1,86 @@ +template: ocpp-chargeamps +product: + identifier: charge-amps-halo + brand: Charge Amps + description: Halo +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-chargeamps + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-chargeamps + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/compleo-ebox.yaml b/templates/release/en/charger/compleo-ebox.yaml new file mode 100644 index 0000000000..7f5a029899 --- /dev/null +++ b/templates/release/en/charger/compleo-ebox.yaml @@ -0,0 +1,33 @@ +template: innogy-ebox +product: + identifier: compleo-ebox + brand: Compleo + description: eBox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: innogy-ebox + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/cta-all-in-one-aeroplus.yaml b/templates/release/en/charger/cta-all-in-one-aeroplus.yaml new file mode 100644 index 0000000000..18b2131213 --- /dev/null +++ b/templates/release/en/charger/cta-all-in-one-aeroplus.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: cta-all-in-one-aeroplus + brand: CTA All-In-One + description: Aeroplus + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/cubos-c11e.yaml b/templates/release/en/charger/cubos-c11e.yaml new file mode 100644 index 0000000000..82181dc117 --- /dev/null +++ b/templates/release/en/charger/cubos-c11e.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: cubos-c11e + brand: CUBOS + description: C11E +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/cubos-c22e.yaml b/templates/release/en/charger/cubos-c22e.yaml new file mode 100644 index 0000000000..7dc41128d5 --- /dev/null +++ b/templates/release/en/charger/cubos-c22e.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: cubos-c22e + brand: CUBOS + description: C22E +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/cupra-charger-connect-2.yaml b/templates/release/en/charger/cupra-charger-connect-2.yaml new file mode 100644 index 0000000000..300efaa1c4 --- /dev/null +++ b/templates/release/en/charger/cupra-charger-connect-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: cupra-charger-connect-2 + brand: Cupra + description: Charger Connect 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/cupra-charger-connect.yaml b/templates/release/en/charger/cupra-charger-connect.yaml new file mode 100644 index 0000000000..dda0228281 --- /dev/null +++ b/templates/release/en/charger/cupra-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: cupra-charger-connect + brand: Cupra + description: Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/cupra-charger-pro-2.yaml b/templates/release/en/charger/cupra-charger-pro-2.yaml new file mode 100644 index 0000000000..dfea74d4ab --- /dev/null +++ b/templates/release/en/charger/cupra-charger-pro-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: cupra-charger-pro-2 + brand: Cupra + description: Charger Pro 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/cupra-charger-pro-eichrecht-2.yaml b/templates/release/en/charger/cupra-charger-pro-eichrecht-2.yaml new file mode 100644 index 0000000000..22daf02fdb --- /dev/null +++ b/templates/release/en/charger/cupra-charger-pro-eichrecht-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: cupra-charger-pro-eichrecht-2 + brand: Cupra + description: Charger Pro Eichrecht 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/cupra-charger-pro.yaml b/templates/release/en/charger/cupra-charger-pro.yaml new file mode 100644 index 0000000000..b03d1921d5 --- /dev/null +++ b/templates/release/en/charger/cupra-charger-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: cupra-charger-pro + brand: Cupra + description: Charger Pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +render: + - default: | + type: template + template: ellipro + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/dadapower-premium-wallbox.yaml b/templates/release/en/charger/dadapower-premium-wallbox.yaml new file mode 100644 index 0000000000..8774b672ed --- /dev/null +++ b/templates/release/en/charger/dadapower-premium-wallbox.yaml @@ -0,0 +1,33 @@ +template: dadapower +product: + identifier: dadapower-premium-wallbox + brand: Dadapower + description: Premium Wallbox +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: dadapower + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/dadapower_0.yaml b/templates/release/en/charger/dadapower_0.yaml deleted file mode 100644 index 7a916c80ea..0000000000 --- a/templates/release/en/charger/dadapower_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Dadapower - description: Premium Wallbox -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: dadapower - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/daheimladen-mb_0.yaml b/templates/release/en/charger/daheimladen-mb_0.yaml deleted file mode 100644 index 1f3f7c2ee6..0000000000 --- a/templates/release/en/charger/daheimladen-mb_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: DaheimLaden - description: Wallbox -description: | - Wallbox must be operated with a recent firmware including Modbus support. Furthermore, “Nachladen” (Smart) or “RSDA” (Touch) must be activated in settings. -render: - - default: | - type: template - template: daheimladen-mb - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional diff --git a/templates/release/en/charger/daheimladen-wallbox.yaml b/templates/release/en/charger/daheimladen-wallbox.yaml new file mode 100644 index 0000000000..2ce0f64a48 --- /dev/null +++ b/templates/release/en/charger/daheimladen-wallbox.yaml @@ -0,0 +1,32 @@ +template: daheimladen-mb +product: + identifier: daheimladen-wallbox + brand: DaheimLaden + description: Wallbox +description: | + Wallbox must be operated with a recent firmware including Modbus support. Furthermore, “Nachladen” (Smart) or “RSDA” (Touch) must be activated in settings. +render: + - default: | + type: template + template: daheimladen-mb + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/daikin-homehub-sg-ready.yaml b/templates/release/en/charger/daikin-homehub-sg-ready.yaml new file mode 100644 index 0000000000..e853bbab96 --- /dev/null +++ b/templates/release/en/charger/daikin-homehub-sg-ready.yaml @@ -0,0 +1,42 @@ +template: daikin-homehub +product: + identifier: daikin-homehub-sg-ready + brand: Daikin + description: HomeHub (SG Ready) + group: Heating devices +render: + - default: | + type: template + template: daikin-homehub + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperature source, [warmwater, buffer] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperature source + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/daikin-homehub_0.yaml b/templates/release/en/charger/daikin-homehub_0.yaml deleted file mode 100644 index a1c5a4abe2..0000000000 --- a/templates/release/en/charger/daikin-homehub_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Daikin - description: HomeHub (SG Ready) - group: Heating devices -render: - - default: | - type: template - template: daikin-homehub - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperature source, [warmwater, buffer] (optional) diff --git a/templates/release/en/charger/delta-ac-max-basic.yaml b/templates/release/en/charger/delta-ac-max-basic.yaml new file mode 100644 index 0000000000..914ee2fadf --- /dev/null +++ b/templates/release/en/charger/delta-ac-max-basic.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-ac-max-basic + brand: Delta + description: AC Max Basic +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/delta-ac-max-smart.yaml b/templates/release/en/charger/delta-ac-max-smart.yaml new file mode 100644 index 0000000000..bff5b8e4ef --- /dev/null +++ b/templates/release/en/charger/delta-ac-max-smart.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-ac-max-smart + brand: Delta + description: AC MAX Smart +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/delta-slim-charger.yaml b/templates/release/en/charger/delta-slim-charger.yaml new file mode 100644 index 0000000000..445a3a7a10 --- /dev/null +++ b/templates/release/en/charger/delta-slim-charger.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-slim-charger + brand: Delta + description: SLIM Charger +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/delta-ultra-fast-charger.yaml b/templates/release/en/charger/delta-ultra-fast-charger.yaml new file mode 100644 index 0000000000..0fefe6ee67 --- /dev/null +++ b/templates/release/en/charger/delta-ultra-fast-charger.yaml @@ -0,0 +1,82 @@ +template: delta +product: + identifier: delta-ultra-fast-charger + brand: Delta + description: Ultra Fast Charger +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: delta + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/delta_0.yaml b/templates/release/en/charger/delta_0.yaml deleted file mode 100644 index 90af37b2c8..0000000000 --- a/templates/release/en/charger/delta_0.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: AC Max Basic -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/delta_1.yaml b/templates/release/en/charger/delta_1.yaml deleted file mode 100644 index de38935e87..0000000000 --- a/templates/release/en/charger/delta_1.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: AC MAX Smart -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/delta_2.yaml b/templates/release/en/charger/delta_2.yaml deleted file mode 100644 index df6bde5e54..0000000000 --- a/templates/release/en/charger/delta_2.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: SLIM Charger -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/delta_3.yaml b/templates/release/en/charger/delta_3.yaml deleted file mode 100644 index f85b44f55a..0000000000 --- a/templates/release/en/charger/delta_3.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Delta - description: Ultra Fast Charger -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: delta - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/demo-charger.yaml b/templates/release/en/charger/demo-charger.yaml new file mode 100644 index 0000000000..9cf0000f7a --- /dev/null +++ b/templates/release/en/charger/demo-charger.yaml @@ -0,0 +1,68 @@ +template: demo-charger +product: + identifier: demo-charger + description: Demo charger + group: Generic support +description: | + For demonstration purposes. Charger with a fixed set of values. +render: + - default: | + type: template + template: demo-charger + status: A # Charge status, [A, B, C] + power: 0 # Power, optional + enabled: true # Enabled, optional + advanced: | + type: template + template: demo-charger + status: A # Charge status, [A, B, C] + power: 0 # Power, optional + enabled: true # Enabled, optional + maxcurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + phases1p3p: false # Phase switching, optional +params: + - name: status + example: + default: A + choice: ['A', 'B', 'C'] + unit: + description: Charge status + help: + advanced: false + optional: false + - name: power + example: + default: 0 + choice: [] + unit: + description: Power + help: + advanced: false + optional: true + - name: enabled + example: + default: true + choice: [] + unit: + description: Enabled + help: + advanced: false + optional: true + - name: maxcurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: Phase switching + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/demo-charger_0.yaml b/templates/release/en/charger/demo-charger_0.yaml deleted file mode 100644 index edc88f9dab..0000000000 --- a/templates/release/en/charger/demo-charger_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - description: Demo charger - group: Generic support -description: | - For demonstration purposes. Charger with a fixed set of values. -render: - - default: | - type: template - template: demo-charger - status: A # Charge status, [A, B, C] - power: 0 # Power, optional - enabled: true # Enabled, optional - advanced: | - type: template - template: demo-charger - status: A # Charge status, [A, B, C] - power: 0 # Power, optional - enabled: true # Enabled, optional - maxcurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - phases1p3p: false # Phase switching, optional diff --git a/templates/release/en/charger/e-on-drive-ebox.yaml b/templates/release/en/charger/e-on-drive-ebox.yaml new file mode 100644 index 0000000000..932f0f1f8c --- /dev/null +++ b/templates/release/en/charger/e-on-drive-ebox.yaml @@ -0,0 +1,33 @@ +template: innogy-ebox +product: + identifier: e-on-drive-ebox + brand: E.ON Drive + description: eBox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: innogy-ebox + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/e-on-drive-vbox.yaml b/templates/release/en/charger/e-on-drive-vbox.yaml new file mode 100644 index 0000000000..f5f5f857c8 --- /dev/null +++ b/templates/release/en/charger/e-on-drive-vbox.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: e-on-drive-vbox + brand: E.ON Drive + description: vBox +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/e3-dc-easy-connect.yaml b/templates/release/en/charger/e3-dc-easy-connect.yaml new file mode 100644 index 0000000000..34f8650441 --- /dev/null +++ b/templates/release/en/charger/e3-dc-easy-connect.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: e3-dc-easy-connect + brand: E3/DC + description: Easy Connect +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/easee-charge-core.yaml b/templates/release/en/charger/easee-charge-core.yaml new file mode 100644 index 0000000000..24ebb5b7cc --- /dev/null +++ b/templates/release/en/charger/easee-charge-core.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-charge-core + brand: Easee + description: Charge Core +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Username, Email address + password: # Password, same as Easee app or the web portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) + authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: Email address + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: same as Easee app or the web portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Timeout + help: Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/easee-charge-lite.yaml b/templates/release/en/charger/easee-charge-lite.yaml new file mode 100644 index 0000000000..a59992e01c --- /dev/null +++ b/templates/release/en/charger/easee-charge-lite.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-charge-lite + brand: Easee + description: Charge Lite +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Username, Email address + password: # Password, same as Easee app or the web portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) + authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: Email address + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: same as Easee app or the web portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Timeout + help: Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/easee-charge.yaml b/templates/release/en/charger/easee-charge.yaml new file mode 100644 index 0000000000..ac65e51964 --- /dev/null +++ b/templates/release/en/charger/easee-charge.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-charge + brand: Easee + description: Charge +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Username, Email address + password: # Password, same as Easee app or the web portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) + authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: Email address + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: same as Easee app or the web portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Timeout + help: Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/easee-home.yaml b/templates/release/en/charger/easee-home.yaml new file mode 100644 index 0000000000..1b87517dcb --- /dev/null +++ b/templates/release/en/charger/easee-home.yaml @@ -0,0 +1,62 @@ +template: easee +product: + identifier: easee-home + brand: Easee + description: Home +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: easee + user: # Username, Email address + password: # Password, same as Easee app or the web portal (https://easee.cloud) + charger: EH______ + timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) + authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: Email address + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: same as Easee app or the web portal (https://easee.cloud) + advanced: false + optional: false + - name: charger + example: EH______ + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 20s + choice: [] + unit: + description: Timeout + help: Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. + advanced: false + optional: true + - name: authorize + example: + default: + choice: [] + unit: + description: + help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/easee_0.yaml b/templates/release/en/charger/easee_0.yaml deleted file mode 100644 index 069882a822..0000000000 --- a/templates/release/en/charger/easee_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Home -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Username, Email address - password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) diff --git a/templates/release/en/charger/easee_1.yaml b/templates/release/en/charger/easee_1.yaml deleted file mode 100644 index f86f3338ad..0000000000 --- a/templates/release/en/charger/easee_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Charge -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Username, Email address - password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) diff --git a/templates/release/en/charger/easee_2.yaml b/templates/release/en/charger/easee_2.yaml deleted file mode 100644 index 120490109e..0000000000 --- a/templates/release/en/charger/easee_2.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Charge Lite -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Username, Email address - password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) diff --git a/templates/release/en/charger/easee_3.yaml b/templates/release/en/charger/easee_3.yaml deleted file mode 100644 index 1d5206c7cd..0000000000 --- a/templates/release/en/charger/easee_3.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Easee - description: Charge Core -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: easee - user: # Username, Email address - password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ - timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) diff --git a/templates/release/en/charger/ebee-wallbox.yaml b/templates/release/en/charger/ebee-wallbox.yaml new file mode 100644 index 0000000000..3cf64f9b1f --- /dev/null +++ b/templates/release/en/charger/ebee-wallbox.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: ebee-wallbox + brand: Ebee + description: Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/echarge-cph1.yaml b/templates/release/en/charger/echarge-cph1.yaml new file mode 100644 index 0000000000..f7364ed64d --- /dev/null +++ b/templates/release/en/charger/echarge-cph1.yaml @@ -0,0 +1,37 @@ +template: hardybarth-ecb1 +product: + identifier: echarge-cph1 + brand: echarge + description: cPH1 +requirements: ["sponsorship"] +description: | + Charge mode must be configured as `manual` +render: + - default: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP address or hostname + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/echarge-cph2.yaml b/templates/release/en/charger/echarge-cph2.yaml new file mode 100644 index 0000000000..dd00ca68f7 --- /dev/null +++ b/templates/release/en/charger/echarge-cph2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: echarge-cph2 + brand: echarge + description: cPH2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/echarge-cpm2.yaml b/templates/release/en/charger/echarge-cpm2.yaml new file mode 100644 index 0000000000..c95ccdd498 --- /dev/null +++ b/templates/release/en/charger/echarge-cpm2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: echarge-cpm2 + brand: echarge + description: cPμ2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml b/templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml new file mode 100644 index 0000000000..d648bddcec --- /dev/null +++ b/templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml @@ -0,0 +1,48 @@ +template: obo +product: + identifier: ecoharmony-evse-epc-2-0-plus + brand: EcoHarmony + description: EVSE EPC 2.0 Plus +render: + - default: | + type: template + template: obo + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 101 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 101 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/edgetech-smart-evse.yaml b/templates/release/en/charger/edgetech-smart-evse.yaml new file mode 100644 index 0000000000..c34cb02e76 --- /dev/null +++ b/templates/release/en/charger/edgetech-smart-evse.yaml @@ -0,0 +1,42 @@ +template: smartevse +product: + identifier: edgetech-smart-evse + brand: Edgetech + description: Smart EVSE +capabilities: ["1p3p"] +render: + - default: | + type: template + template: smartevse + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/eebus-compatible.yaml b/templates/release/en/charger/eebus-compatible.yaml new file mode 100644 index 0000000000..3792c8bc40 --- /dev/null +++ b/templates/release/en/charger/eebus-compatible.yaml @@ -0,0 +1,32 @@ +template: eebus +product: + identifier: eebus-compatible + description: EEBUS compatible + group: Generic support +capabilities: ["mA"] +requirements: ["eebus"] +render: + - default: | + type: template + template: eebus + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/eebus_0.yaml b/templates/release/en/charger/eebus_0.yaml deleted file mode 100644 index acb2c68eae..0000000000 --- a/templates/release/en/charger/eebus_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - description: EEBUS compatible - group: Generic support -capabilities: ["mA"] -requirements: ["eebus"] -render: - - default: | - type: template - template: eebus - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elco.yaml b/templates/release/en/charger/elco.yaml new file mode 100644 index 0000000000..81b2395070 --- /dev/null +++ b/templates/release/en/charger/elco.yaml @@ -0,0 +1,63 @@ +template: luxtronik +product: + identifier: elco + brand: Elco + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/elecq-biz.yaml b/templates/release/en/charger/elecq-biz.yaml new file mode 100644 index 0000000000..429fda9d37 --- /dev/null +++ b/templates/release/en/charger/elecq-biz.yaml @@ -0,0 +1,85 @@ +template: ocpp-elecq +product: + identifier: elecq-biz + brand: Elecq + description: Biz +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elecq-home.yaml b/templates/release/en/charger/elecq-home.yaml new file mode 100644 index 0000000000..dad2cfd2d7 --- /dev/null +++ b/templates/release/en/charger/elecq-home.yaml @@ -0,0 +1,85 @@ +template: ocpp-elecq +product: + identifier: elecq-home + brand: Elecq + description: Home +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elecq-station.yaml b/templates/release/en/charger/elecq-station.yaml new file mode 100644 index 0000000000..0fd4eef97e --- /dev/null +++ b/templates/release/en/charger/elecq-station.yaml @@ -0,0 +1,85 @@ +template: ocpp-elecq +product: + identifier: elecq-station + brand: Elecq + description: Station +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-elecq + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/eledio-go.yaml b/templates/release/en/charger/eledio-go.yaml new file mode 100644 index 0000000000..0c24bb5cc2 --- /dev/null +++ b/templates/release/en/charger/eledio-go.yaml @@ -0,0 +1,89 @@ +template: ocpp-enercab +product: + identifier: eledio-go + brand: eledio + description: go +capabilities: ["1p3p"] +requirements: ["sponsorship", "skiptest"] +description: | + https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + +render: + - default: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elli-2_0.yaml b/templates/release/en/charger/elli-2_0.yaml deleted file mode 100644 index f78d334f03..0000000000 --- a/templates/release/en/charger/elli-2_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Connect 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_1.yaml b/templates/release/en/charger/elli-2_1.yaml deleted file mode 100644 index 5f08a8d949..0000000000 --- a/templates/release/en/charger/elli-2_1.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Pro 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_10.yaml b/templates/release/en/charger/elli-2_10.yaml deleted file mode 100644 index e9b9e67aa4..0000000000 --- a/templates/release/en/charger/elli-2_10.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Pro 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_11.yaml b/templates/release/en/charger/elli-2_11.yaml deleted file mode 100644 index 635b665fd2..0000000000 --- a/templates/release/en/charger/elli-2_11.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Pro Eichrecht 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_2.yaml b/templates/release/en/charger/elli-2_2.yaml deleted file mode 100644 index b7c67cad13..0000000000 --- a/templates/release/en/charger/elli-2_2.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Pro Eichrecht 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_3.yaml b/templates/release/en/charger/elli-2_3.yaml deleted file mode 100644 index 959332f6be..0000000000 --- a/templates/release/en/charger/elli-2_3.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: Charger Connect 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_4.yaml b/templates/release/en/charger/elli-2_4.yaml deleted file mode 100644 index dd09d5469a..0000000000 --- a/templates/release/en/charger/elli-2_4.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: Charger Pro 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_5.yaml b/templates/release/en/charger/elli-2_5.yaml deleted file mode 100644 index bab7de0f9e..0000000000 --- a/templates/release/en/charger/elli-2_5.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: Charger Pro Eichrecht 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_6.yaml b/templates/release/en/charger/elli-2_6.yaml deleted file mode 100644 index b11eaf5350..0000000000 --- a/templates/release/en/charger/elli-2_6.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: Charger Connect -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_7.yaml b/templates/release/en/charger/elli-2_7.yaml deleted file mode 100644 index 7e5120f122..0000000000 --- a/templates/release/en/charger/elli-2_7.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: Charger Pro -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_8.yaml b/templates/release/en/charger/elli-2_8.yaml deleted file mode 100644 index 47eb5ee0e3..0000000000 --- a/templates/release/en/charger/elli-2_8.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: Charger Pro Eichrecht -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-2_9.yaml b/templates/release/en/charger/elli-2_9.yaml deleted file mode 100644 index d445d4b5fc..0000000000 --- a/templates/release/en/charger/elli-2_9.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Connect 2 -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: elli-2 - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elli-charger-connect-2.yaml b/templates/release/en/charger/elli-charger-connect-2.yaml new file mode 100644 index 0000000000..7506b87451 --- /dev/null +++ b/templates/release/en/charger/elli-charger-connect-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: elli-charger-connect-2 + brand: Elli + description: Charger Connect 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elli-charger-connect.yaml b/templates/release/en/charger/elli-charger-connect.yaml new file mode 100644 index 0000000000..f131caa4f6 --- /dev/null +++ b/templates/release/en/charger/elli-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: elli-charger-connect + brand: Elli + description: Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elli-charger-pro-2.yaml b/templates/release/en/charger/elli-charger-pro-2.yaml new file mode 100644 index 0000000000..82c9aa2b88 --- /dev/null +++ b/templates/release/en/charger/elli-charger-pro-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: elli-charger-pro-2 + brand: Elli + description: Charger Pro 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elli-charger-pro-eichrecht-2.yaml b/templates/release/en/charger/elli-charger-pro-eichrecht-2.yaml new file mode 100644 index 0000000000..b8682237b8 --- /dev/null +++ b/templates/release/en/charger/elli-charger-pro-eichrecht-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: elli-charger-pro-eichrecht-2 + brand: Elli + description: Charger Pro Eichrecht 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elli-charger-pro.yaml b/templates/release/en/charger/elli-charger-pro.yaml new file mode 100644 index 0000000000..f67b55a9e7 --- /dev/null +++ b/templates/release/en/charger/elli-charger-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: elli-charger-pro + brand: Elli + description: Charger Pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +render: + - default: | + type: template + template: ellipro + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elliconnect_0.yaml b/templates/release/en/charger/elliconnect_0.yaml deleted file mode 100644 index 2f6255db43..0000000000 --- a/templates/release/en/charger/elliconnect_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Elli - description: Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - - Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elliconnect_1.yaml b/templates/release/en/charger/elliconnect_1.yaml deleted file mode 100644 index 736c7f770b..0000000000 --- a/templates/release/en/charger/elliconnect_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Volkswagen - description: ID. Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - - Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elliconnect_2.yaml b/templates/release/en/charger/elliconnect_2.yaml deleted file mode 100644 index 846d2c813c..0000000000 --- a/templates/release/en/charger/elliconnect_2.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Skoda - description: iV Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - - Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elliconnect_3.yaml b/templates/release/en/charger/elliconnect_3.yaml deleted file mode 100644 index 031ebd5a3d..0000000000 --- a/templates/release/en/charger/elliconnect_3.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Cupra - description: Charger Connect -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - - Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/elliconnect_4.yaml b/templates/release/en/charger/elliconnect_4.yaml deleted file mode 100644 index b236963701..0000000000 --- a/templates/release/en/charger/elliconnect_4.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Audi - description: Wallbox plus -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - - Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. - -render: - - default: | - type: template - template: elliconnect - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/ellipro_0.yaml b/templates/release/en/charger/ellipro_0.yaml deleted file mode 100644 index b14cd592b1..0000000000 --- a/templates/release/en/charger/ellipro_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Elli - description: Charger Pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - -render: - - default: | - type: template - template: ellipro - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/ellipro_1.yaml b/templates/release/en/charger/ellipro_1.yaml deleted file mode 100644 index 6f6a63208b..0000000000 --- a/templates/release/en/charger/ellipro_1.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Volkswagen - description: ID. Charger Pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - -render: - - default: | - type: template - template: ellipro - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/ellipro_2.yaml b/templates/release/en/charger/ellipro_2.yaml deleted file mode 100644 index 92c0fe1918..0000000000 --- a/templates/release/en/charger/ellipro_2.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Skoda - description: iV Charger Connect+ -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - -render: - - default: | - type: template - template: ellipro - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/ellipro_3.yaml b/templates/release/en/charger/ellipro_3.yaml deleted file mode 100644 index cd3f1dba89..0000000000 --- a/templates/release/en/charger/ellipro_3.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Cupra - description: Charger Pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - -render: - - default: | - type: template - template: ellipro - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/ellipro_4.yaml b/templates/release/en/charger/ellipro_4.yaml deleted file mode 100644 index 7fe6493a42..0000000000 --- a/templates/release/en/charger/ellipro_4.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Audi - description: Wallbox pro -capabilities: ["mA"] -requirements: ["eebus"] -description: | - The device has to have a fix IP address (manuall or via DHCP). - - The identification of a vehicle using the RFID card is not possible. - - Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. - -render: - - default: | - type: template - template: ellipro - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/em2go-home.yaml b/templates/release/en/charger/em2go-home.yaml new file mode 100644 index 0000000000..e7fc0ebe91 --- /dev/null +++ b/templates/release/en/charger/em2go-home.yaml @@ -0,0 +1,23 @@ +template: em2go-home +product: + identifier: em2go-home + brand: EM2GO + description: Home +capabilities: ["1p3p", "mA"] +description: | + Requires FW Version >= E3C_V1.1. mA regulation requires FW version >= E3C_V1.3. +render: + - default: | + type: template + template: em2go-home + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/em2go-home_0.yaml b/templates/release/en/charger/em2go-home_0.yaml deleted file mode 100644 index 07b28709a4..0000000000 --- a/templates/release/en/charger/em2go-home_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: EM2GO - description: Home -capabilities: ["1p3p", "mA"] -description: | - Requires FW Version >= E3C_V1.1. mA regulation requires FW version >= E3C_V1.3. -render: - - default: | - type: template - template: em2go-home - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml b/templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml new file mode 100644 index 0000000000..40c98dfd6e --- /dev/null +++ b/templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml @@ -0,0 +1,34 @@ +template: em2go +product: + identifier: em2go-pro-power-ocpp-onc + brand: EM2GO + description: Pro Power (OCPP/ONC) +capabilities: ["mA"] +description: | + Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15) +render: + - default: | + type: template + template: em2go + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/em2go_0.yaml b/templates/release/en/charger/em2go_0.yaml deleted file mode 100644 index 5735a34957..0000000000 --- a/templates/release/en/charger/em2go_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: EM2GO - description: Pro Power (OCPP/ONC) -capabilities: ["mA"] -description: | - Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15) -render: - - default: | - type: template - template: em2go - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/emsesp_0.yaml b/templates/release/en/charger/emsesp_0.yaml deleted file mode 100644 index 38ab23fcc3..0000000000 --- a/templates/release/en/charger/emsesp_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Buderus - description: SG Ready - group: Heating devices -description: | - Integrated via [EMSESP](https://emsesp.org/) -render: - - default: | - type: template - template: emsesp - host: 192.0.2.2 # IP address or hostname - token: # optional - powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) - tempsource: # Temperature source, [warmwater] (optional) diff --git a/templates/release/en/charger/emsesp_1.yaml b/templates/release/en/charger/emsesp_1.yaml deleted file mode 100644 index 9b4bc52c18..0000000000 --- a/templates/release/en/charger/emsesp_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Bosch - description: SG Ready - group: Heating devices -description: | - Integrated via [EMSESP](https://emsesp.org/) -render: - - default: | - type: template - template: emsesp - host: 192.0.2.2 # IP address or hostname - token: # optional - powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) - tempsource: # Temperature source, [warmwater] (optional) diff --git a/templates/release/en/charger/emsesp_2.yaml b/templates/release/en/charger/emsesp_2.yaml deleted file mode 100644 index 4f4a563f81..0000000000 --- a/templates/release/en/charger/emsesp_2.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Junkers - description: SG Ready - group: Heating devices -description: | - Integrated via [EMSESP](https://emsesp.org/) -render: - - default: | - type: template - template: emsesp - host: 192.0.2.2 # IP address or hostname - token: # optional - powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) - tempsource: # Temperature source, [warmwater] (optional) diff --git a/templates/release/en/charger/enercab-smart.yaml b/templates/release/en/charger/enercab-smart.yaml new file mode 100644 index 0000000000..6e38d0a6c5 --- /dev/null +++ b/templates/release/en/charger/enercab-smart.yaml @@ -0,0 +1,89 @@ +template: ocpp-enercab +product: + identifier: enercab-smart + brand: enercab + description: smart +capabilities: ["1p3p"] +requirements: ["sponsorship", "skiptest"] +description: | + https://www.enercab.at/index.php?controller=attachment&id_attachment=311 + +render: + - default: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-enercab + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/enplus-ac-ev-charger.yaml b/templates/release/en/charger/enplus-ac-ev-charger.yaml new file mode 100644 index 0000000000..8b811c9b4f --- /dev/null +++ b/templates/release/en/charger/enplus-ac-ev-charger.yaml @@ -0,0 +1,86 @@ +template: ocpp-enplus +product: + identifier: enplus-ac-ev-charger + brand: EN+ + description: AC EV Charger +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-enplus + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/ensto-chago-wallbox.yaml b/templates/release/en/charger/ensto-chago-wallbox.yaml new file mode 100644 index 0000000000..7ccf03073e --- /dev/null +++ b/templates/release/en/charger/ensto-chago-wallbox.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: ensto-chago-wallbox + brand: Ensto + description: Chago Wallbox +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/entratek-power-dot-fix.yaml b/templates/release/en/charger/entratek-power-dot-fix.yaml new file mode 100644 index 0000000000..5927676fd9 --- /dev/null +++ b/templates/release/en/charger/entratek-power-dot-fix.yaml @@ -0,0 +1,86 @@ +template: ocpp-entratek +product: + identifier: entratek-power-dot-fix + brand: EntraTek + description: Power Dot Fix +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/entratek-power-dot-pro-2.yaml b/templates/release/en/charger/entratek-power-dot-pro-2.yaml new file mode 100644 index 0000000000..cf26d709e1 --- /dev/null +++ b/templates/release/en/charger/entratek-power-dot-pro-2.yaml @@ -0,0 +1,86 @@ +template: ocpp-entratek +product: + identifier: entratek-power-dot-pro-2 + brand: EntraTek + description: Power Dot Pro 2 +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-entratek + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/eprowallbox_0.yaml b/templates/release/en/charger/eprowallbox_0.yaml deleted file mode 100644 index 9f74cf8d50..0000000000 --- a/templates/release/en/charger/eprowallbox_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: Free2Move - description: eProWallbox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: eprowallbox - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/esl-walli-light.yaml b/templates/release/en/charger/esl-walli-light.yaml new file mode 100644 index 0000000000..1dd5790664 --- /dev/null +++ b/templates/release/en/charger/esl-walli-light.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: esl-walli-light + brand: ESL + description: Walli LIGHT +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/esystems-ghostone.yaml b/templates/release/en/charger/esystems-ghostone.yaml new file mode 100644 index 0000000000..0e90d57030 --- /dev/null +++ b/templates/release/en/charger/esystems-ghostone.yaml @@ -0,0 +1,39 @@ +template: ghost +product: + identifier: esystems-ghostone + brand: eSystems + description: ghostONE +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: ghost + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/etrel-duo_0.yaml b/templates/release/en/charger/etrel-duo_0.yaml deleted file mode 100644 index 1752e022fc..0000000000 --- a/templates/release/en/charger/etrel-duo_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Etrel - description: INCH Duo -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be switched to "Power" charging mode. -render: - - default: | - type: template - template: etrel-duo - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: etrel-duo - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/etrel-inch-duo.yaml b/templates/release/en/charger/etrel-inch-duo.yaml new file mode 100644 index 0000000000..65b432fb74 --- /dev/null +++ b/templates/release/en/charger/etrel-inch-duo.yaml @@ -0,0 +1,49 @@ +template: etrel-duo +product: + identifier: etrel-inch-duo + brand: Etrel + description: INCH Duo +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be switched to "Power" charging mode. +render: + - default: | + type: template + template: etrel-duo + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: etrel-duo + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/etrel-inch.yaml b/templates/release/en/charger/etrel-inch.yaml new file mode 100644 index 0000000000..e70651458b --- /dev/null +++ b/templates/release/en/charger/etrel-inch.yaml @@ -0,0 +1,34 @@ +template: etrel +product: + identifier: etrel-inch + brand: Etrel + description: INCH +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be switched to "Power" charging mode. +render: + - default: | + type: template + template: etrel + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/etrel_0.yaml b/templates/release/en/charger/etrel_0.yaml deleted file mode 100644 index 4df177382e..0000000000 --- a/templates/release/en/charger/etrel_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Etrel - description: INCH -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be switched to "Power" charging mode. -render: - - default: | - type: template - template: etrel - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional diff --git a/templates/release/en/charger/etrel_1.yaml b/templates/release/en/charger/etrel_1.yaml deleted file mode 100644 index 9bad6e2a3e..0000000000 --- a/templates/release/en/charger/etrel_1.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Sonnen - description: sonnenCharger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be switched to "Power" charging mode. -render: - - default: | - type: template - template: etrel - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional diff --git a/templates/release/en/charger/evbox-elvi.yaml b/templates/release/en/charger/evbox-elvi.yaml new file mode 100644 index 0000000000..482c84ae1f --- /dev/null +++ b/templates/release/en/charger/evbox-elvi.yaml @@ -0,0 +1,86 @@ +template: ocpp-evbox-elvi +product: + identifier: evbox-elvi + brand: EVBox + description: Elvi +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-evbox-elvi + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + meter: true # optional + advanced: | + type: template + template: ocpp-evbox-elvi + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + meter: true # optional + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: meter + example: + default: true + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/evbox-livo.yaml b/templates/release/en/charger/evbox-livo.yaml new file mode 100644 index 0000000000..89da690d2e --- /dev/null +++ b/templates/release/en/charger/evbox-livo.yaml @@ -0,0 +1,33 @@ +template: livo +product: + identifier: evbox-livo + brand: EVBox + description: Livo +requirements: ["eebus"] +description: | + The device requires a fixed IP addres. It's important to set up EEBus first. After setting up EEBus the charger will recognize evcc as a HEMS device on the network. Please use the installer tool to select evcc as HEMS. After this has been done, copy the given SKI from the Install app and add it to your yaml. +render: + - default: | + type: template + template: livo + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/evse-din.yaml b/templates/release/en/charger/evse-din.yaml new file mode 100644 index 0000000000..782107d0b0 --- /dev/null +++ b/templates/release/en/charger/evse-din.yaml @@ -0,0 +1,40 @@ +template: evse-din +product: + identifier: evse-din + description: EVSE DIN +render: + - default: | + type: template + template: evse-din + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/evse-din_0.yaml b/templates/release/en/charger/evse-din_0.yaml deleted file mode 100644 index 4f2a93b261..0000000000 --- a/templates/release/en/charger/evse-din_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Stark in Strom - description: Easy -render: - - default: | - type: template - template: evse-din - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/evse-din_1.yaml b/templates/release/en/charger/evse-din_1.yaml deleted file mode 100644 index caf6f20729..0000000000 --- a/templates/release/en/charger/evse-din_1.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - description: EVSE DIN -render: - - default: | - type: template - template: evse-din - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/evse-wifi.yaml b/templates/release/en/charger/evse-wifi.yaml new file mode 100644 index 0000000000..e0e018060f --- /dev/null +++ b/templates/release/en/charger/evse-wifi.yaml @@ -0,0 +1,19 @@ +template: evsewifi +product: + identifier: evse-wifi + description: EVSE-WiFi +render: + - default: | + type: template + template: evsewifi + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/evsewifi_0.yaml b/templates/release/en/charger/evsewifi_0.yaml deleted file mode 100644 index 5795fa06d9..0000000000 --- a/templates/release/en/charger/evsewifi_0.yaml +++ /dev/null @@ -1,7 +0,0 @@ -product: - description: EVSE-WiFi -render: - - default: | - type: template - template: evsewifi - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/free2move-eprowallbox-move.yaml b/templates/release/en/charger/free2move-eprowallbox-move.yaml new file mode 100644 index 0000000000..1e8b314567 --- /dev/null +++ b/templates/release/en/charger/free2move-eprowallbox-move.yaml @@ -0,0 +1,43 @@ +template: eprowallbox +product: + identifier: free2move-eprowallbox-move + brand: Free2Move + description: eProWallbox Move +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: eprowallbox + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/free2move-eprowallbox.yaml b/templates/release/en/charger/free2move-eprowallbox.yaml new file mode 100644 index 0000000000..095c5fd108 --- /dev/null +++ b/templates/release/en/charger/free2move-eprowallbox.yaml @@ -0,0 +1,43 @@ +template: eprowallbox +product: + identifier: free2move-eprowallbox + brand: Free2Move + description: eProWallbox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: eprowallbox + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/free2move-esolutions-eprowallbox.yaml b/templates/release/en/charger/free2move-esolutions-eprowallbox.yaml new file mode 100644 index 0000000000..6d6a946c05 --- /dev/null +++ b/templates/release/en/charger/free2move-esolutions-eprowallbox.yaml @@ -0,0 +1,86 @@ +template: ocpp-esolutions +product: + identifier: free2move-esolutions-eprowallbox + brand: Free2move eSolutions + description: eProWallbox +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-esolutions + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-esolutions + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/fritzdect_0.yaml b/templates/release/en/charger/fritzdect_0.yaml deleted file mode 100644 index 5815b41e40..0000000000 --- a/templates/release/en/charger/fritzdect_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: AVM - description: FritzDECT - group: Switchable sockets -render: - - default: | - type: template - template: fritzdect - uri: https://fritz.box # URI, HTTP(S) address (optional) - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: fritzdect - uri: https://fritz.box # URI, HTTP(S) address (optional) - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/fronius-wattpilot-ocpp.yaml b/templates/release/en/charger/fronius-wattpilot-ocpp.yaml new file mode 100644 index 0000000000..4e78bbd58e --- /dev/null +++ b/templates/release/en/charger/fronius-wattpilot-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: fronius-wattpilot-ocpp + brand: Fronius + description: Wattpilot (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/garo-glb.yaml b/templates/release/en/charger/garo-glb.yaml new file mode 100644 index 0000000000..cdb2b7ec35 --- /dev/null +++ b/templates/release/en/charger/garo-glb.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-glb + brand: Garo + description: GLB +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/garo-glbplus.yaml b/templates/release/en/charger/garo-glbplus.yaml new file mode 100644 index 0000000000..66e57286c8 --- /dev/null +++ b/templates/release/en/charger/garo-glbplus.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-glbplus + brand: Garo + description: GLB+ +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/garo-ls4-compact.yaml b/templates/release/en/charger/garo-ls4-compact.yaml new file mode 100644 index 0000000000..99aeb05fa1 --- /dev/null +++ b/templates/release/en/charger/garo-ls4-compact.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-ls4-compact + brand: Garo + description: LS4 compact +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/garo-ls4.yaml b/templates/release/en/charger/garo-ls4.yaml new file mode 100644 index 0000000000..d299feef7d --- /dev/null +++ b/templates/release/en/charger/garo-ls4.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: garo-ls4 + brand: Garo + description: LS4 +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/ghost_0.yaml b/templates/release/en/charger/ghost_0.yaml deleted file mode 100644 index cd1329080c..0000000000 --- a/templates/release/en/charger/ghost_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: eSystems - description: ghostONE -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: ghost - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/ghost_1.yaml b/templates/release/en/charger/ghost_1.yaml deleted file mode 100644 index 1bb2714a32..0000000000 --- a/templates/release/en/charger/ghost_1.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Kontron Solar - description: Charger -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: ghost - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/go-e-charger-gemini-ocpp.yaml b/templates/release/en/charger/go-e-charger-gemini-ocpp.yaml new file mode 100644 index 0000000000..16e1e68c17 --- /dev/null +++ b/templates/release/en/charger/go-e-charger-gemini-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: go-e-charger-gemini-ocpp + brand: go-e + description: Charger Gemini (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-gemini.yaml b/templates/release/en/charger/go-e-charger-gemini.yaml new file mode 100644 index 0000000000..34d064674c --- /dev/null +++ b/templates/release/en/charger/go-e-charger-gemini.yaml @@ -0,0 +1,27 @@ +template: go-e-v3 +product: + identifier: go-e-charger-gemini + brand: go-e + description: Charger Gemini +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware 052.1 or later. + Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. + The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). + +render: + - default: | + type: template + template: go-e-v3 + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-homefix.yaml b/templates/release/en/charger/go-e-charger-homefix.yaml new file mode 100644 index 0000000000..bb120299b2 --- /dev/null +++ b/templates/release/en/charger/go-e-charger-homefix.yaml @@ -0,0 +1,24 @@ +template: go-e +product: + identifier: go-e-charger-homefix + brand: go-e + description: Charger HOMEfix +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. +render: + - default: | + type: template + template: go-e + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-homeplus.yaml b/templates/release/en/charger/go-e-charger-homeplus.yaml new file mode 100644 index 0000000000..b1c443844b --- /dev/null +++ b/templates/release/en/charger/go-e-charger-homeplus.yaml @@ -0,0 +1,27 @@ +template: go-e-v3 +product: + identifier: go-e-charger-homeplus + brand: go-e + description: Charger HOME+ +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware 052.1 or later. + Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. + The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). + +render: + - default: | + type: template + template: go-e-v3 + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-pro-ocpp.yaml b/templates/release/en/charger/go-e-charger-pro-ocpp.yaml new file mode 100644 index 0000000000..0ed39bb987 --- /dev/null +++ b/templates/release/en/charger/go-e-charger-pro-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: go-e-charger-pro-ocpp + brand: go-e + description: Charger PRO (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-pro.yaml b/templates/release/en/charger/go-e-charger-pro.yaml new file mode 100644 index 0000000000..ddabf61e41 --- /dev/null +++ b/templates/release/en/charger/go-e-charger-pro.yaml @@ -0,0 +1,24 @@ +template: go-e +product: + identifier: go-e-charger-pro + brand: go-e + description: Charger PRO +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. +render: + - default: | + type: template + template: go-e + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-v3-ocpp.yaml b/templates/release/en/charger/go-e-charger-v3-ocpp.yaml new file mode 100644 index 0000000000..d24b717b59 --- /dev/null +++ b/templates/release/en/charger/go-e-charger-v3-ocpp.yaml @@ -0,0 +1,86 @@ +template: ocpp-goe +product: + identifier: go-e-charger-v3-ocpp + brand: go-e + description: Charger V3 (OCPP) +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-goe + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-v3.yaml b/templates/release/en/charger/go-e-charger-v3.yaml new file mode 100644 index 0000000000..537e188ef6 --- /dev/null +++ b/templates/release/en/charger/go-e-charger-v3.yaml @@ -0,0 +1,27 @@ +template: go-e-v3 +product: + identifier: go-e-charger-v3 + brand: go-e + description: Charger V3 +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware 052.1 or later. + Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. + The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). + +render: + - default: | + type: template + template: go-e-v3 + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/go-e-v3_0.yaml b/templates/release/en/charger/go-e-v3_0.yaml deleted file mode 100644 index 2368290fc7..0000000000 --- a/templates/release/en/charger/go-e-v3_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: go-e - description: Charger Gemini -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware 052.1 or later. - Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. - The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). - -render: - - default: | - type: template - template: go-e-v3 - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/go-e-v3_1.yaml b/templates/release/en/charger/go-e-v3_1.yaml deleted file mode 100644 index 7ab41af351..0000000000 --- a/templates/release/en/charger/go-e-v3_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: go-e - description: Charger HOME+ -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware 052.1 or later. - Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. - The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). - -render: - - default: | - type: template - template: go-e-v3 - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/go-e-v3_2.yaml b/templates/release/en/charger/go-e-v3_2.yaml deleted file mode 100644 index 52adab157c..0000000000 --- a/templates/release/en/charger/go-e-v3_2.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: go-e - description: Charger V3 -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware 052.1 or later. - Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. - The “simulate unplugging” option should be activated in the Go-E app ("Car" menu item). - -render: - - default: | - type: template - template: go-e-v3 - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/go-e_0.yaml b/templates/release/en/charger/go-e_0.yaml deleted file mode 100644 index fe0499ca05..0000000000 --- a/templates/release/en/charger/go-e_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: go-e - description: Charger HOMEfix -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. -render: - - default: | - type: template - template: go-e - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/go-e_1.yaml b/templates/release/en/charger/go-e_1.yaml deleted file mode 100644 index 3806244bc6..0000000000 --- a/templates/release/en/charger/go-e_1.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: go-e - description: Charger PRO -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. -render: - - default: | - type: template - template: go-e - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/hardy-barth-cph1.yaml b/templates/release/en/charger/hardy-barth-cph1.yaml new file mode 100644 index 0000000000..6bd15a728b --- /dev/null +++ b/templates/release/en/charger/hardy-barth-cph1.yaml @@ -0,0 +1,37 @@ +template: hardybarth-ecb1 +product: + identifier: hardy-barth-cph1 + brand: Hardy Barth + description: cPH1 +requirements: ["sponsorship"] +description: | + Charge mode must be configured as `manual` +render: + - default: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: hardybarth-ecb1 + host: 192.0.2.2 # IP address or hostname + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/hardy-barth-cph2.yaml b/templates/release/en/charger/hardy-barth-cph2.yaml new file mode 100644 index 0000000000..a3a08a750d --- /dev/null +++ b/templates/release/en/charger/hardy-barth-cph2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: hardy-barth-cph2 + brand: Hardy Barth + description: cPH2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/hardy-barth-cpm2.yaml b/templates/release/en/charger/hardy-barth-cpm2.yaml new file mode 100644 index 0000000000..82d12254b8 --- /dev/null +++ b/templates/release/en/charger/hardy-barth-cpm2.yaml @@ -0,0 +1,21 @@ +template: hardybarth-salia +product: + identifier: hardy-barth-cpm2 + brand: Hardy Barth + description: cPμ2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hardybarth-salia + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/hardybarth-ecb1_0.yaml b/templates/release/en/charger/hardybarth-ecb1_0.yaml deleted file mode 100644 index 386a0bf0bf..0000000000 --- a/templates/release/en/charger/hardybarth-ecb1_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: HardyBarth - description: cPH1 -requirements: ["sponsorship"] -description: | - Charge mode must be configured as `manual` -render: - - default: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP address or hostname - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/hardybarth-ecb1_1.yaml b/templates/release/en/charger/hardybarth-ecb1_1.yaml deleted file mode 100644 index aaf632a2e2..0000000000 --- a/templates/release/en/charger/hardybarth-ecb1_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: echarge - description: cPH1 -requirements: ["sponsorship"] -description: | - Charge mode must be configured as `manual` -render: - - default: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: hardybarth-ecb1 - host: 192.0.2.2 # IP address or hostname - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/hardybarth-salia_0.yaml b/templates/release/en/charger/hardybarth-salia_0.yaml deleted file mode 100644 index 811cd84108..0000000000 --- a/templates/release/en/charger/hardybarth-salia_0.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: Hardy Barth - description: cPH2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/hardybarth-salia_1.yaml b/templates/release/en/charger/hardybarth-salia_1.yaml deleted file mode 100644 index a316c5dfdc..0000000000 --- a/templates/release/en/charger/hardybarth-salia_1.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: Hardy Barth - description: cPμ2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/hardybarth-salia_2.yaml b/templates/release/en/charger/hardybarth-salia_2.yaml deleted file mode 100644 index d567cef271..0000000000 --- a/templates/release/en/charger/hardybarth-salia_2.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: echarge - description: cPH2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/hardybarth-salia_3.yaml b/templates/release/en/charger/hardybarth-salia_3.yaml deleted file mode 100644 index 244481cd21..0000000000 --- a/templates/release/en/charger/hardybarth-salia_3.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: echarge - description: cPμ2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hardybarth-salia - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/heidelberg-energy-control.yaml b/templates/release/en/charger/heidelberg-energy-control.yaml new file mode 100644 index 0000000000..c298a4b722 --- /dev/null +++ b/templates/release/en/charger/heidelberg-energy-control.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: heidelberg-energy-control + brand: Heidelberg + description: Energy Control +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/heidelberg_0.yaml b/templates/release/en/charger/heidelberg_0.yaml deleted file mode 100644 index 04e1da686f..0000000000 --- a/templates/release/en/charger/heidelberg_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Heidelberg - description: Energy Control -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/heidelberg_1.yaml b/templates/release/en/charger/heidelberg_1.yaml deleted file mode 100644 index 5f910f2d2f..0000000000 --- a/templates/release/en/charger/heidelberg_1.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: SENEC - description: Wallbox pro s -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/heidelberg_2.yaml b/templates/release/en/charger/heidelberg_2.yaml deleted file mode 100644 index 360a58cf42..0000000000 --- a/templates/release/en/charger/heidelberg_2.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Walther Werke - description: Basic Evo Pro -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/heidelberg_3.yaml b/templates/release/en/charger/heidelberg_3.yaml deleted file mode 100644 index 863e1833eb..0000000000 --- a/templates/release/en/charger/heidelberg_3.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Amperfied - description: Wallbox Energy Control -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). -render: - - default: | - type: template - template: heidelberg - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/hesotec-ebox.yaml b/templates/release/en/charger/hesotec-ebox.yaml new file mode 100644 index 0000000000..5c80164d4a --- /dev/null +++ b/templates/release/en/charger/hesotec-ebox.yaml @@ -0,0 +1,32 @@ +template: hesotec +product: + identifier: hesotec-ebox + brand: Hesotec + description: eBox +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hesotec + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/hesotec-esat.yaml b/templates/release/en/charger/hesotec-esat.yaml new file mode 100644 index 0000000000..4c93f63fa0 --- /dev/null +++ b/templates/release/en/charger/hesotec-esat.yaml @@ -0,0 +1,32 @@ +template: hesotec +product: + identifier: hesotec-esat + brand: Hesotec + description: eSat +requirements: ["sponsorship"] +render: + - default: | + type: template + template: hesotec + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/hesotec_0.yaml b/templates/release/en/charger/hesotec_0.yaml deleted file mode 100644 index f709745da2..0000000000 --- a/templates/release/en/charger/hesotec_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Hesotec - description: eSat -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hesotec - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/hesotec_1.yaml b/templates/release/en/charger/hesotec_1.yaml deleted file mode 100644 index 387c70b2fa..0000000000 --- a/templates/release/en/charger/hesotec_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Hesotec - description: eBox -requirements: ["sponsorship"] -render: - - default: | - type: template - template: hesotec - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/home-assistant-switch.yaml b/templates/release/en/charger/home-assistant-switch.yaml new file mode 100644 index 0000000000..b0f58c8c82 --- /dev/null +++ b/templates/release/en/charger/home-assistant-switch.yaml @@ -0,0 +1,100 @@ +template: homeassistant-switch +product: + identifier: home-assistant-switch + brand: Home Assistant + description: Switch + group: Switchable sockets +requirements: ["skiptest"] +render: + - default: | + type: template + template: homeassistant-switch + baseurl: http://homeassistant.local:8123 # Base URL of the Home Assistant instance + token: # Long-Lived Access Token, from Home Assistant profile + switchentity: switch.smartsocket # Entity ID of the switch device + powerentity: sensor.smartsocket_power # Entity ID for power measurement, optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: homeassistant-switch + baseurl: http://homeassistant.local:8123 # Base URL of the Home Assistant instance + token: # Long-Lived Access Token, from Home Assistant profile + switchentity: switch.smartsocket # Entity ID of the switch device + powerentity: sensor.smartsocket_power # Entity ID for power measurement, optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: baseurl + example: http://homeassistant.local:8123 + default: + choice: [] + unit: + description: Base URL of the Home Assistant instance + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Long-Lived Access Token + help: from Home Assistant profile + advanced: false + optional: false + - name: switchentity + example: switch.smartsocket + default: + choice: [] + unit: + description: Entity ID of the switch device + help: + advanced: false + optional: false + - name: powerentity + example: sensor.smartsocket_power + default: + choice: [] + unit: + description: Entity ID for power measurement + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/homeassistant-switch_0.yaml b/templates/release/en/charger/homeassistant-switch_0.yaml deleted file mode 100644 index 960aee862d..0000000000 --- a/templates/release/en/charger/homeassistant-switch_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Home Assistant - description: Switch - group: Switchable sockets -requirements: ["skiptest"] -render: - - default: | - type: template - template: homeassistant-switch - baseurl: http://homeassistant.local:8123 # Base URL of the Home Assistant instance - token: # Long-Lived Access Token, from Home Assistant profile - switchentity: switch.smartsocket # Entity ID of the switch device - powerentity: sensor.smartsocket_power # Entity ID for power measurement, optional - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: homeassistant-switch - baseurl: http://homeassistant.local:8123 # Base URL of the Home Assistant instance - token: # Long-Lived Access Token, from Home Assistant profile - switchentity: switch.smartsocket # Entity ID of the switch device - powerentity: sensor.smartsocket_power # Entity ID for power measurement, optional - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/homecharge-homecharger.yaml b/templates/release/en/charger/homecharge-homecharger.yaml new file mode 100644 index 0000000000..acb7086b89 --- /dev/null +++ b/templates/release/en/charger/homecharge-homecharger.yaml @@ -0,0 +1,90 @@ +template: ocpp-homecharge +product: + identifier: homecharge-homecharger + brand: Homecharge + description: Homecharger +requirements: ["sponsorship", "skiptest"] +description: | + The charger must be equipped with a built-in meter (models HC11L/HC22L Energy or Profi). + For the OCPP configuration, you need to access the EFR-SECC charge controller at http://host/secc. + For login credentials, ask your dealer or the vendor EFR (www.efr.de). + +render: + - default: | + type: template + template: ocpp-homecharge + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-homecharge + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/homematic-ip.yaml b/templates/release/en/charger/homematic-ip.yaml new file mode 100644 index 0000000000..38325c66b2 --- /dev/null +++ b/templates/release/en/charger/homematic-ip.yaml @@ -0,0 +1,139 @@ +template: homematic +product: + identifier: homematic-ip + brand: Homematic IP + group: Switchable sockets +render: + - default: | + type: template + template: homematic + host: 192.0.2.2 # IP address or hostname + port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: homematic + host: 192.0.2.2 # IP address or hostname + port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Homematic meter channel number like shown in the CCU web user interface. + switchchannel: 3 # Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Homematic switch actor channel number like shown in the CCU web user interface. + cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 2010 + choice: [] + unit: + description: XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010) + help: + advanced: false + optional: true + - name: device + example: 0001EE89AAD848 + default: + choice: [] + unit: + description: Device address/Serial number + help: Homematic device id like shown in the CCU web user interface. + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: meterchannel + example: + default: 6 + choice: [] + unit: + description: Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2) + help: Homematic meter channel number like shown in the CCU web user interface. + advanced: true + optional: false + - name: switchchannel + example: + default: 3 + choice: [] + unit: + description: Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1) + help: Homematic switch actor channel number like shown in the CCU web user interface. + advanced: true + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: XML-RPC api cache duration - Default 1s. (valid units are s,m,h) + help: In case of duty cycle problems try a cache setting of 30s. + advanced: true + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/homematic_0.yaml b/templates/release/en/charger/homematic_0.yaml deleted file mode 100644 index 2b9e3c3105..0000000000 --- a/templates/release/en/charger/homematic_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Homematic IP - group: Switchable sockets -render: - - default: | - type: template - template: homematic - host: 192.0.2.2 # IP address or hostname - port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: homematic - host: 192.0.2.2 # IP address or hostname - port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Homematic meter channel number like shown in the CCU web user interface. - switchchannel: 3 # Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Homematic switch actor channel number like shown in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/homewizard.yaml b/templates/release/en/charger/homewizard.yaml new file mode 100644 index 0000000000..569127140b --- /dev/null +++ b/templates/release/en/charger/homewizard.yaml @@ -0,0 +1,65 @@ +template: homewizard +product: + identifier: homewizard + brand: HomeWizard + group: Switchable sockets +render: + - default: | + type: template + template: homewizard + host: 192.0.2.2 # IP address or hostname + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: homewizard + host: 192.0.2.2 # IP address or hostname + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/homewizard_0.yaml b/templates/release/en/charger/homewizard_0.yaml deleted file mode 100644 index 9f251ecda3..0000000000 --- a/templates/release/en/charger/homewizard_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: HomeWizard - group: Switchable sockets -render: - - default: | - type: template - template: homewizard - host: 192.0.2.2 # IP address or hostname - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: homewizard - host: 192.0.2.2 # IP address or hostname - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/huawei-scharger-22kt-s0.yaml b/templates/release/en/charger/huawei-scharger-22kt-s0.yaml new file mode 100644 index 0000000000..4596d621f3 --- /dev/null +++ b/templates/release/en/charger/huawei-scharger-22kt-s0.yaml @@ -0,0 +1,85 @@ +template: ocpp-huawei +product: + identifier: huawei-scharger-22kt-s0 + brand: Huawei + description: SCharger-22KT-S0 +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/huawei-scharger-7ks-s0.yaml b/templates/release/en/charger/huawei-scharger-7ks-s0.yaml new file mode 100644 index 0000000000..b147a22584 --- /dev/null +++ b/templates/release/en/charger/huawei-scharger-7ks-s0.yaml @@ -0,0 +1,85 @@ +template: ocpp-huawei +product: + identifier: huawei-scharger-7ks-s0 + brand: Huawei + description: SCharger-7KS-S0 +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-huawei + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/ichargecion_0.yaml b/templates/release/en/charger/ichargecion_0.yaml deleted file mode 100644 index b17e5e89dd..0000000000 --- a/templates/release/en/charger/ichargecion_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Schrack - description: i-CHARGE CION -render: - - default: | - type: template - template: ichargecion - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/ichargecion_1.yaml b/templates/release/en/charger/ichargecion_1.yaml deleted file mode 100644 index 2e266ef1bc..0000000000 --- a/templates/release/en/charger/ichargecion_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Smartfox - description: Pro Charger -render: - - default: | - type: template - template: ichargecion - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/idm.yaml b/templates/release/en/charger/idm.yaml new file mode 100644 index 0000000000..1c94b7a8cc --- /dev/null +++ b/templates/release/en/charger/idm.yaml @@ -0,0 +1,41 @@ +template: idm +product: + identifier: idm + brand: IDM + group: Heating devices +render: + - default: | + type: template + template: idm + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater_top', 'warmwater_bottom', 'buffer'] + unit: + description: Temperature source + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/idm_0.yaml b/templates/release/en/charger/idm_0.yaml deleted file mode 100644 index 690f1b5779..0000000000 --- a/templates/release/en/charger/idm_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: IDM - group: Heating devices -render: - - default: | - type: template - template: idm - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer] (optional) diff --git a/templates/release/en/charger/innogy-ebox.yaml b/templates/release/en/charger/innogy-ebox.yaml new file mode 100644 index 0000000000..4d8616ac7e --- /dev/null +++ b/templates/release/en/charger/innogy-ebox.yaml @@ -0,0 +1,33 @@ +template: innogy-ebox +product: + identifier: innogy-ebox + brand: Innogy + description: eBox +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: innogy-ebox + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/innogy-ebox_0.yaml b/templates/release/en/charger/innogy-ebox_0.yaml deleted file mode 100644 index 805ac61c0d..0000000000 --- a/templates/release/en/charger/innogy-ebox_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Innogy - description: eBox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: innogy-ebox - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/innogy-ebox_1.yaml b/templates/release/en/charger/innogy-ebox_1.yaml deleted file mode 100644 index 628cd32186..0000000000 --- a/templates/release/en/charger/innogy-ebox_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: E.ON Drive - description: eBox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: innogy-ebox - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/innogy-ebox_2.yaml b/templates/release/en/charger/innogy-ebox_2.yaml deleted file mode 100644 index a35d5b1986..0000000000 --- a/templates/release/en/charger/innogy-ebox_2.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Compleo - description: eBox -capabilities: ["mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: innogy-ebox - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/inro-pantabox.yaml b/templates/release/en/charger/inro-pantabox.yaml new file mode 100644 index 0000000000..c483687e57 --- /dev/null +++ b/templates/release/en/charger/inro-pantabox.yaml @@ -0,0 +1,20 @@ +template: pantabox +product: + identifier: inro-pantabox + brand: INRO + description: Pantabox +render: + - default: | + type: template + template: pantabox + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/juice-charger-me.yaml b/templates/release/en/charger/juice-charger-me.yaml new file mode 100644 index 0000000000..51a7b93f7f --- /dev/null +++ b/templates/release/en/charger/juice-charger-me.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: juice-charger-me + brand: Juice + description: Charger Me +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/junkers-sg-ready.yaml b/templates/release/en/charger/junkers-sg-ready.yaml new file mode 100644 index 0000000000..6b0049bb08 --- /dev/null +++ b/templates/release/en/charger/junkers-sg-ready.yaml @@ -0,0 +1,53 @@ +template: emsesp +product: + identifier: junkers-sg-ready + brand: Junkers + description: SG Ready + group: Heating devices +description: | + Integrated via [EMSESP](https://emsesp.org/) +render: + - default: | + type: template + template: emsesp + host: 192.0.2.2 # IP address or hostname + token: # optional + powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) + tempsource: # Temperature source, [warmwater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: powersource + example: + default: hpcurrpower + choice: ['hpcurrpower', 'hppower'] + unit: + description: Power source + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperature source + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/kathrein-kwb-ac20.yaml b/templates/release/en/charger/kathrein-kwb-ac20.yaml new file mode 100644 index 0000000000..5028dd5e05 --- /dev/null +++ b/templates/release/en/charger/kathrein-kwb-ac20.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac20 + brand: Kathrein + description: KWB-AC20 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/kathrein-kwb-ac35.yaml b/templates/release/en/charger/kathrein-kwb-ac35.yaml new file mode 100644 index 0000000000..bd31023595 --- /dev/null +++ b/templates/release/en/charger/kathrein-kwb-ac35.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac35 + brand: Kathrein + description: KWB-AC35 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/kathrein-kwb-ac40-e.yaml b/templates/release/en/charger/kathrein-kwb-ac40-e.yaml new file mode 100644 index 0000000000..0b795f3734 --- /dev/null +++ b/templates/release/en/charger/kathrein-kwb-ac40-e.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac40-e + brand: Kathrein + description: KWB-AC40 E +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/kathrein-kwb-ac40.yaml b/templates/release/en/charger/kathrein-kwb-ac40.yaml new file mode 100644 index 0000000000..07a252b7c4 --- /dev/null +++ b/templates/release/en/charger/kathrein-kwb-ac40.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac40 + brand: Kathrein + description: KWB-AC40 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/kathrein-kwb-ac60-e.yaml b/templates/release/en/charger/kathrein-kwb-ac60-e.yaml new file mode 100644 index 0000000000..d226dc0204 --- /dev/null +++ b/templates/release/en/charger/kathrein-kwb-ac60-e.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac60-e + brand: Kathrein + description: KWB-AC60 E +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/kathrein-kwb-ac60.yaml b/templates/release/en/charger/kathrein-kwb-ac60.yaml new file mode 100644 index 0000000000..e36ff55fe7 --- /dev/null +++ b/templates/release/en/charger/kathrein-kwb-ac60.yaml @@ -0,0 +1,35 @@ +template: Kathrein +product: + identifier: kathrein-kwb-ac60 + brand: Kathrein + description: KWB-AC60 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 +render: + - default: | + type: template + template: Kathrein + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/keba-kecontact-p20.yaml b/templates/release/en/charger/keba-kecontact-p20.yaml new file mode 100644 index 0000000000..b26307061d --- /dev/null +++ b/templates/release/en/charger/keba-kecontact-p20.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p20 + brand: KEBA + description: KeContact P20 +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/keba-kecontact-p30-c-series.yaml b/templates/release/en/charger/keba-kecontact-p30-c-series.yaml new file mode 100644 index 0000000000..498bad6c24 --- /dev/null +++ b/templates/release/en/charger/keba-kecontact-p30-c-series.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p30-c-series + brand: KEBA + description: KeContact P30 C-Series +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/keba-kecontact-p30-x-series.yaml b/templates/release/en/charger/keba-kecontact-p30-x-series.yaml new file mode 100644 index 0000000000..1bb21b4672 --- /dev/null +++ b/templates/release/en/charger/keba-kecontact-p30-x-series.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p30-x-series + brand: KEBA + description: KeContact P30 X-Series +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/keba-kecontact-p40-pro.yaml b/templates/release/en/charger/keba-kecontact-p40-pro.yaml new file mode 100644 index 0000000000..a632a837ea --- /dev/null +++ b/templates/release/en/charger/keba-kecontact-p40-pro.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p40-pro + brand: KEBA + description: KeContact P40 Pro +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/keba-kecontact-p40.yaml b/templates/release/en/charger/keba-kecontact-p40.yaml new file mode 100644 index 0000000000..1ba138f981 --- /dev/null +++ b/templates/release/en/charger/keba-kecontact-p40.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: keba-kecontact-p40 + brand: KEBA + description: KeContact P40 +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/keba-modbus_0.yaml b/templates/release/en/charger/keba-modbus_0.yaml deleted file mode 100644 index b84fbdf3a4..0000000000 --- a/templates/release/en/charger/keba-modbus_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P20 -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/charger/keba-modbus_1.yaml b/templates/release/en/charger/keba-modbus_1.yaml deleted file mode 100644 index db52e7541f..0000000000 --- a/templates/release/en/charger/keba-modbus_1.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P30 C-Series -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/charger/keba-modbus_2.yaml b/templates/release/en/charger/keba-modbus_2.yaml deleted file mode 100644 index fe52ef144d..0000000000 --- a/templates/release/en/charger/keba-modbus_2.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P30 X-Series -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/charger/keba-modbus_3.yaml b/templates/release/en/charger/keba-modbus_3.yaml deleted file mode 100644 index c6b9f3a2b8..0000000000 --- a/templates/release/en/charger/keba-modbus_3.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P40 -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/charger/keba-modbus_4.yaml b/templates/release/en/charger/keba-modbus_4.yaml deleted file mode 100644 index fba8368ca7..0000000000 --- a/templates/release/en/charger/keba-modbus_4.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: KEBA - description: KeContact P40 Pro -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/charger/keba-modbus_5.yaml b/templates/release/en/charger/keba-modbus_5.yaml deleted file mode 100644 index 11b25ed691..0000000000 --- a/templates/release/en/charger/keba-modbus_5.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: BMW - description: i Wallbox -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/charger/keba-modbus_6.yaml b/templates/release/en/charger/keba-modbus_6.yaml deleted file mode 100644 index 6f88b5d7a1..0000000000 --- a/templates/release/en/charger/keba-modbus_6.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: SolarEdge - description: Home EV Charger -capabilities: ["1p3p", "mA", "rfid"] -requirements: ["sponsorship"] -description: | - Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. -render: - - default: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: keba-modbus - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/charger/kermi-x-center-pro.yaml b/templates/release/en/charger/kermi-x-center-pro.yaml new file mode 100644 index 0000000000..c9c86a94ed --- /dev/null +++ b/templates/release/en/charger/kermi-x-center-pro.yaml @@ -0,0 +1,46 @@ +template: kermi +product: + identifier: kermi-x-center-pro + brand: Kermi + description: x-center pro + group: Heating devices +render: + - default: | + type: template + template: kermi + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater, buffer] (optional) + advanced: | + type: template + template: kermi + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater, buffer] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperature source + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/kermi_0.yaml b/templates/release/en/charger/kermi_0.yaml deleted file mode 100644 index 9dc3f046da..0000000000 --- a/templates/release/en/charger/kermi_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Bösch - description: x-change - group: Heating devices -render: - - default: | - type: template - template: kermi - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater, buffer] (optional) - advanced: | - type: template - template: kermi - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional diff --git a/templates/release/en/charger/kermi_1.yaml b/templates/release/en/charger/kermi_1.yaml deleted file mode 100644 index 8612a402fb..0000000000 --- a/templates/release/en/charger/kermi_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Kermi - description: x-center pro - group: Heating devices -render: - - default: | - type: template - template: kermi - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater, buffer] (optional) - advanced: | - type: template - template: kermi - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional diff --git a/templates/release/en/charger/kontron-solar-charger.yaml b/templates/release/en/charger/kontron-solar-charger.yaml new file mode 100644 index 0000000000..64d2128683 --- /dev/null +++ b/templates/release/en/charger/kontron-solar-charger.yaml @@ -0,0 +1,39 @@ +template: ghost +product: + identifier: kontron-solar-charger + brand: Kontron Solar + description: Charger +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: ghost + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/kostal-enector.yaml b/templates/release/en/charger/kostal-enector.yaml new file mode 100644 index 0000000000..6ec447a413 --- /dev/null +++ b/templates/release/en/charger/kostal-enector.yaml @@ -0,0 +1,48 @@ +template: mennekes-compact +product: + identifier: kostal-enector + brand: Kostal + description: Enector +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). + No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. + For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. + +render: + - default: | + type: template + template: mennekes-compact + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 50 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N2" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 50 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 57600 + comset: 8N2 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 50 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/kse-wbx16.yaml b/templates/release/en/charger/kse-wbx16.yaml new file mode 100644 index 0000000000..c562f20efd --- /dev/null +++ b/templates/release/en/charger/kse-wbx16.yaml @@ -0,0 +1,43 @@ +template: kse +product: + identifier: kse-wbx16 + brand: KSE + description: wBX16 +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: kse + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 100 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 100 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 100 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/kse_0.yaml b/templates/release/en/charger/kse_0.yaml deleted file mode 100644 index eb69e1c9fe..0000000000 --- a/templates/release/en/charger/kse_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: KSE - description: wBX16 -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: kse - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 100 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 100 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/ladefoxx-evload.yaml b/templates/release/en/charger/ladefoxx-evload.yaml new file mode 100644 index 0000000000..2b3d505acb --- /dev/null +++ b/templates/release/en/charger/ladefoxx-evload.yaml @@ -0,0 +1,50 @@ +template: phoenix-charx +product: + identifier: ladefoxx-evload + brand: LadeFoxx + description: EvLoad +render: + - default: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/ladefoxx-mikro-2-0.yaml b/templates/release/en/charger/ladefoxx-mikro-2-0.yaml new file mode 100644 index 0000000000..bb15c9c9e8 --- /dev/null +++ b/templates/release/en/charger/ladefoxx-mikro-2-0.yaml @@ -0,0 +1,50 @@ +template: phoenix-charx +product: + identifier: ladefoxx-mikro-2-0 + brand: LadeFoxx + description: Mikro 2.0 +render: + - default: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/lambda-eu-l-series.yaml b/templates/release/en/charger/lambda-eu-l-series.yaml new file mode 100644 index 0000000000..d90d02721f --- /dev/null +++ b/templates/release/en/charger/lambda-eu-l-series.yaml @@ -0,0 +1,52 @@ +template: lambda-zewotherm +product: + identifier: lambda-eu-l-series + brand: Lambda + description: EU-L Series + group: Heating devices +description: | + Energy management settings of the device: + + - E-Meter communication type: "ModBus Client" + - E-Meter measuring point: "Pos. E-Überschuss" + +render: + - default: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + advanced: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater_top', 'warmwater_bottom', 'buffer_top', 'buffer_bottom'] + unit: + description: Temperature source + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/lambda-zewotherm_0.yaml b/templates/release/en/charger/lambda-zewotherm_0.yaml deleted file mode 100644 index ecdbe28173..0000000000 --- a/templates/release/en/charger/lambda-zewotherm_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: Lambda - description: EU-L Series - group: Heating devices -description: | - Energy management settings of the device: - - - E-Meter communication type: "ModBus Client" - - E-Meter measuring point: "Pos. E-Überschuss" - -render: - - default: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - advanced: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional diff --git a/templates/release/en/charger/lambda-zewotherm_1.yaml b/templates/release/en/charger/lambda-zewotherm_1.yaml deleted file mode 100644 index d99dcf6524..0000000000 --- a/templates/release/en/charger/lambda-zewotherm_1.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: Zewotherm - description: EU-L Series - group: Heating devices -description: | - Energy management settings of the device: - - - E-Meter communication type: "ModBus Client" - - E-Meter measuring point: "Pos. E-Überschuss" - -render: - - default: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - advanced: | - type: template - template: lambda-zewotherm - host: 192.0.2.2 # IP address or hostname - tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional diff --git a/templates/release/en/charger/livo_0.yaml b/templates/release/en/charger/livo_0.yaml deleted file mode 100644 index 958b3a0754..0000000000 --- a/templates/release/en/charger/livo_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: EVBox - description: Livo -requirements: ["eebus"] -description: | - The device requires a fixed IP addres. It's important to set up EEBus first. After setting up EEBus the charger will recognize evcc as a HEMS device on the network. Please use the installer tool to select evcc as HEMS. After this has been done, copy the given SKI from the Install app and add it to your yaml. -render: - - default: | - type: template - template: livo - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/lrt-home-essentialplus.yaml b/templates/release/en/charger/lrt-home-essentialplus.yaml new file mode 100644 index 0000000000..e772fa61d8 --- /dev/null +++ b/templates/release/en/charger/lrt-home-essentialplus.yaml @@ -0,0 +1,44 @@ +template: alphatec +product: + identifier: lrt-home-essentialplus + brand: LRT + description: HOME Essential+ +requirements: ["sponsorship"] +description: | + The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. +render: + - default: | + type: template + template: alphatec + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/luxtronik_0.yaml b/templates/release/en/charger/luxtronik_0.yaml deleted file mode 100644 index 7b4d9a3c86..0000000000 --- a/templates/release/en/charger/luxtronik_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Buderus - description: Logamatic HMC 20 - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_1.yaml b/templates/release/en/charger/luxtronik_1.yaml deleted file mode 100644 index 9a3e13a730..0000000000 --- a/templates/release/en/charger/luxtronik_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Buderus - description: Logamatic HMC 20 Z - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_10.yaml b/templates/release/en/charger/luxtronik_10.yaml deleted file mode 100644 index ee3c4312a7..0000000000 --- a/templates/release/en/charger/luxtronik_10.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Wolf - description: BWS - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_2.yaml b/templates/release/en/charger/luxtronik_2.yaml deleted file mode 100644 index 1ae8eb3f6d..0000000000 --- a/templates/release/en/charger/luxtronik_2.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: alpha innotec - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_3.yaml b/templates/release/en/charger/luxtronik_3.yaml deleted file mode 100644 index 3285d2c7ff..0000000000 --- a/templates/release/en/charger/luxtronik_3.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: CTA All-In-One - description: Aeroplus - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_4.yaml b/templates/release/en/charger/luxtronik_4.yaml deleted file mode 100644 index a69f1eeffe..0000000000 --- a/templates/release/en/charger/luxtronik_4.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Elco - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_5.yaml b/templates/release/en/charger/luxtronik_5.yaml deleted file mode 100644 index 5a1ed904ae..0000000000 --- a/templates/release/en/charger/luxtronik_5.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nibe - description: AP-AW10 - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_6.yaml b/templates/release/en/charger/luxtronik_6.yaml deleted file mode 100644 index 37360d2c3f..0000000000 --- a/templates/release/en/charger/luxtronik_6.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Roth - description: ThermoAura - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_7.yaml b/templates/release/en/charger/luxtronik_7.yaml deleted file mode 100644 index 60723f68a5..0000000000 --- a/templates/release/en/charger/luxtronik_7.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Roth - description: ThermoTerra - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_8.yaml b/templates/release/en/charger/luxtronik_8.yaml deleted file mode 100644 index b798ad00bb..0000000000 --- a/templates/release/en/charger/luxtronik_8.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Novelan - description: WPR NET - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/luxtronik_9.yaml b/templates/release/en/charger/luxtronik_9.yaml deleted file mode 100644 index 586a745b89..0000000000 --- a/templates/release/en/charger/luxtronik_9.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Wolf - description: BWL - group: Heating devices -description: | - For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. -render: - - default: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - advanced: | - type: template - template: luxtronik - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) diff --git a/templates/release/en/charger/mennekes-amedio-professional.yaml b/templates/release/en/charger/mennekes-amedio-professional.yaml new file mode 100644 index 0000000000..36add13db9 --- /dev/null +++ b/templates/release/en/charger/mennekes-amedio-professional.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: mennekes-amedio-professional + brand: Mennekes + description: AMEDIO Professional +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-4business-700.yaml b/templates/release/en/charger/mennekes-amtron-4business-700.yaml new file mode 100644 index 0000000000..2e89144629 --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-4business-700.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: mennekes-amtron-4business-700 + brand: Mennekes + description: AMTRON 4Business 700 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + The configuration option 'External Energy Management' must be enabled. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-4you-300.yaml b/templates/release/en/charger/mennekes-amtron-4you-300.yaml new file mode 100644 index 0000000000..3a8cc64988 --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-4you-300.yaml @@ -0,0 +1,48 @@ +template: mennekes-compact +product: + identifier: mennekes-amtron-4you-300 + brand: Mennekes + description: AMTRON 4You 300 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). + No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. + For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. + +render: + - default: | + type: template + template: mennekes-compact + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 50 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N2" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 50 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 57600 + comset: 8N2 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 50 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-4you-500.yaml b/templates/release/en/charger/mennekes-amtron-4you-500.yaml new file mode 100644 index 0000000000..d61ecc493b --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-4you-500.yaml @@ -0,0 +1,35 @@ +template: bender-icc +product: + identifier: mennekes-amtron-4you-500 + brand: Mennekes + description: AMTRON 4You 500 +capabilities: ["rfid", "mA", "1p3p"] +requirements: ["sponsorship"] +description: | + The configuration option 'External Energy Management' must be enabled. +render: + - default: | + type: template + template: bender-icc + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-chargecontrol.yaml b/templates/release/en/charger/mennekes-amtron-chargecontrol.yaml new file mode 100644 index 0000000000..f9551c603c --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-chargecontrol.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: mennekes-amtron-chargecontrol + brand: Mennekes + description: AMTRON ChargeControl +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml b/templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml new file mode 100644 index 0000000000..9ec9376da4 --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml @@ -0,0 +1,48 @@ +template: mennekes-compact +product: + identifier: mennekes-amtron-compact-2-0s + brand: Mennekes + description: AMTRON Compact 2.0s +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). + No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. + For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. + +render: + - default: | + type: template + template: mennekes-compact + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 50 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N2" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 50 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 57600 + comset: 8N2 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 50 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-premium.yaml b/templates/release/en/charger/mennekes-amtron-premium.yaml new file mode 100644 index 0000000000..4d919d93dc --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-premium.yaml @@ -0,0 +1,32 @@ +template: mennekes-hcc3 +product: + identifier: mennekes-amtron-premium + brand: Mennekes + description: AMTRON Premium +requirements: ["sponsorship"] +render: + - default: | + type: template + template: mennekes-hcc3 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-professional.yaml b/templates/release/en/charger/mennekes-amtron-professional.yaml new file mode 100644 index 0000000000..32802f436d --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-professional.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: mennekes-amtron-professional + brand: Mennekes + description: AMTRON Professional +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-amtron-xtra.yaml b/templates/release/en/charger/mennekes-amtron-xtra.yaml new file mode 100644 index 0000000000..1669a80f46 --- /dev/null +++ b/templates/release/en/charger/mennekes-amtron-xtra.yaml @@ -0,0 +1,32 @@ +template: mennekes-hcc3 +product: + identifier: mennekes-amtron-xtra + brand: Mennekes + description: AMTRON Xtra +requirements: ["sponsorship"] +render: + - default: | + type: template + template: mennekes-hcc3 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-compact_0.yaml b/templates/release/en/charger/mennekes-compact_0.yaml deleted file mode 100644 index 9caa15c414..0000000000 --- a/templates/release/en/charger/mennekes-compact_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Compact 2.0s -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). - No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. - For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. - -render: - - default: | - type: template - template: mennekes-compact - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 50 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N2" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 50 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/mennekes-compact_1.yaml b/templates/release/en/charger/mennekes-compact_1.yaml deleted file mode 100644 index 8f0a6638b7..0000000000 --- a/templates/release/en/charger/mennekes-compact_1.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Mennekes - description: AMTRON 4You 300 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). - No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. - For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. - -render: - - default: | - type: template - template: mennekes-compact - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 50 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N2" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 50 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/mennekes-compact_2.yaml b/templates/release/en/charger/mennekes-compact_2.yaml deleted file mode 100644 index 2d1a4ff2b8..0000000000 --- a/templates/release/en/charger/mennekes-compact_2.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Kostal - description: Enector -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). - No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. - For Kostal systems with Smart Energy Meter (KSEM), the additional activation code (Solar Pure Mode / Solar Plus Mode) for the KSEM is *not* required. - -render: - - default: | - type: template - template: mennekes-compact - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 50 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 57600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N2" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 50 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/mennekes-emobility-gateway-acu.yaml b/templates/release/en/charger/mennekes-emobility-gateway-acu.yaml new file mode 100644 index 0000000000..8c86d3d8ef --- /dev/null +++ b/templates/release/en/charger/mennekes-emobility-gateway-acu.yaml @@ -0,0 +1,91 @@ +template: ocpp-mennekes-acu +product: + identifier: mennekes-emobility-gateway-acu + brand: Mennekes + description: eMobility Gateway (ACU) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + To configure, open the web interface of the ACU. + Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J + Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. + +render: + - default: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-hcc3_0.yaml b/templates/release/en/charger/mennekes-hcc3_0.yaml deleted file mode 100644 index 327f8b99ed..0000000000 --- a/templates/release/en/charger/mennekes-hcc3_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Xtra -requirements: ["sponsorship"] -render: - - default: | - type: template - template: mennekes-hcc3 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/mennekes-hcc3_1.yaml b/templates/release/en/charger/mennekes-hcc3_1.yaml deleted file mode 100644 index dbcb5fe2d6..0000000000 --- a/templates/release/en/charger/mennekes-hcc3_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Mennekes - description: AMTRON Premium -requirements: ["sponsorship"] -render: - - default: | - type: template - template: mennekes-hcc3 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/mennekes-smart-acu.yaml b/templates/release/en/charger/mennekes-smart-acu.yaml new file mode 100644 index 0000000000..ee8c14ea55 --- /dev/null +++ b/templates/release/en/charger/mennekes-smart-acu.yaml @@ -0,0 +1,91 @@ +template: ocpp-mennekes-acu +product: + identifier: mennekes-smart-acu + brand: Mennekes + description: Smart (ACU) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + To configure, open the web interface of the ACU. + Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J + Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. + +render: + - default: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-smart-t-acu.yaml b/templates/release/en/charger/mennekes-smart-t-acu.yaml new file mode 100644 index 0000000000..0881909243 --- /dev/null +++ b/templates/release/en/charger/mennekes-smart-t-acu.yaml @@ -0,0 +1,91 @@ +template: ocpp-mennekes-acu +product: + identifier: mennekes-smart-t-acu + brand: Mennekes + description: Smart T (ACU) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + To configure, open the web interface of the ACU. + Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J + Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. + +render: + - default: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-mennekes-acu + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/my-pv-ac-elwa-2.yaml b/templates/release/en/charger/my-pv-ac-elwa-2.yaml new file mode 100644 index 0000000000..4a97e43e27 --- /dev/null +++ b/templates/release/en/charger/my-pv-ac-elwa-2.yaml @@ -0,0 +1,43 @@ +template: ac-elwa-2 +product: + identifier: my-pv-ac-elwa-2 + brand: my-PV + description: AC ELWA 2 + group: Heating devices +requirements: ["sponsorship"] +render: + - default: | + type: template + template: ac-elwa-2 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + scale: 1 # Scale factor for power limit, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: scale + example: + default: 1 + choice: [] + unit: + description: Scale factor for power limit + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/my-pv-ac-thor-9s.yaml b/templates/release/en/charger/my-pv-ac-thor-9s.yaml new file mode 100644 index 0000000000..27e4da3e20 --- /dev/null +++ b/templates/release/en/charger/my-pv-ac-thor-9s.yaml @@ -0,0 +1,53 @@ +template: ac-thor +product: + identifier: my-pv-ac-thor-9s + brand: my-PV + description: AC•THOR 9s + group: Heating devices +requirements: ["sponsorship"] +render: + - default: | + type: template + template: ac-thor + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + scale: 1 # Scale factor for power limit, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperature sensor + help: + advanced: false + optional: true + - name: scale + example: + default: 1 + choice: [] + unit: + description: Scale factor for power limit + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/my-pv-ac-thor.yaml b/templates/release/en/charger/my-pv-ac-thor.yaml new file mode 100644 index 0000000000..7a240c5ef2 --- /dev/null +++ b/templates/release/en/charger/my-pv-ac-thor.yaml @@ -0,0 +1,53 @@ +template: ac-thor +product: + identifier: my-pv-ac-thor + brand: my-PV + description: AC•THOR + group: Heating devices +requirements: ["sponsorship"] +render: + - default: | + type: template + template: ac-thor + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + scale: 1 # Scale factor for power limit, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperature sensor + help: + advanced: false + optional: true + - name: scale + example: + default: 1 + choice: [] + unit: + description: Scale factor for power limit + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/mystrom-switch.yaml b/templates/release/en/charger/mystrom-switch.yaml new file mode 100644 index 0000000000..fb021fd3f9 --- /dev/null +++ b/templates/release/en/charger/mystrom-switch.yaml @@ -0,0 +1,66 @@ +template: mystrom +product: + identifier: mystrom-switch + brand: myStrom + description: Switch + group: Switchable sockets +render: + - default: | + type: template + template: mystrom + host: 192.0.2.2 # IP address or hostname + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: mystrom + host: 192.0.2.2 # IP address or hostname + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/mystrom_0.yaml b/templates/release/en/charger/mystrom_0.yaml deleted file mode 100644 index 3dc677c7ac..0000000000 --- a/templates/release/en/charger/mystrom_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: myStrom - description: Switch - group: Switchable sockets -render: - - default: | - type: template - template: mystrom - host: 192.0.2.2 # IP address or hostname - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: mystrom - host: 192.0.2.2 # IP address or hostname - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/nibe-ap-aw10.yaml b/templates/release/en/charger/nibe-ap-aw10.yaml new file mode 100644 index 0000000000..867b468dce --- /dev/null +++ b/templates/release/en/charger/nibe-ap-aw10.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: nibe-ap-aw10 + brand: Nibe + description: AP-AW10 + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/novelan-wpr-net.yaml b/templates/release/en/charger/novelan-wpr-net.yaml new file mode 100644 index 0000000000..9aca44539d --- /dev/null +++ b/templates/release/en/charger/novelan-wpr-net.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: novelan-wpr-net + brand: Novelan + description: WPR NET + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/nrggen2_0.yaml b/templates/release/en/charger/nrggen2_0.yaml deleted file mode 100644 index 9e415a9ef3..0000000000 --- a/templates/release/en/charger/nrggen2_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: NRGkick - description: Gen2 -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: nrggen2 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: nrggen2 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - phases1p3p: false # Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. (optional) diff --git a/templates/release/en/charger/nrgkick-connect.yaml b/templates/release/en/charger/nrgkick-connect.yaml new file mode 100644 index 0000000000..4c0e2d7bce --- /dev/null +++ b/templates/release/en/charger/nrgkick-connect.yaml @@ -0,0 +1,42 @@ +template: nrgkick-connect +product: + identifier: nrgkick-connect + brand: NRGkick + description: Connect +description: | + NRGkick charging unit via HTTP (older than 2022/2023) +render: + - default: | + type: template + template: nrgkick-connect + host: 192.0.2.2 # IP address or hostname + mac: + password: # Password, Use single quotes in case of leading zeros +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: mac + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/nrgkick-connect_0.yaml b/templates/release/en/charger/nrgkick-connect_0.yaml deleted file mode 100644 index 5a4d0e7275..0000000000 --- a/templates/release/en/charger/nrgkick-connect_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: NRGkick - description: Connect -description: | - NRGkick charging unit via HTTP (older than 2022/2023) -render: - - default: | - type: template - template: nrgkick-connect - host: 192.0.2.2 # IP address or hostname - mac: - password: # Password, Use single quotes in case of leading zeros diff --git a/templates/release/en/charger/nrgkick-gen2.yaml b/templates/release/en/charger/nrgkick-gen2.yaml new file mode 100644 index 0000000000..4a807075d6 --- /dev/null +++ b/templates/release/en/charger/nrgkick-gen2.yaml @@ -0,0 +1,52 @@ +template: nrggen2 +product: + identifier: nrgkick-gen2 + brand: NRGkick + description: Gen2 +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: nrggen2 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: nrggen2 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + phases1p3p: false # Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: + help: Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/obo-bettermann-ion.yaml b/templates/release/en/charger/obo-bettermann-ion.yaml new file mode 100644 index 0000000000..f0eb202144 --- /dev/null +++ b/templates/release/en/charger/obo-bettermann-ion.yaml @@ -0,0 +1,48 @@ +template: obo +product: + identifier: obo-bettermann-ion + brand: OBO Bettermann + description: Ion +render: + - default: | + type: template + template: obo + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 101 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 101 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/obo_0.yaml b/templates/release/en/charger/obo_0.yaml deleted file mode 100644 index bf4300498c..0000000000 --- a/templates/release/en/charger/obo_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: EcoHarmony - description: EVSE EPC 2.0 Plus -render: - - default: | - type: template - template: obo - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 101 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/obo_1.yaml b/templates/release/en/charger/obo_1.yaml deleted file mode 100644 index b47bf8b176..0000000000 --- a/templates/release/en/charger/obo_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: OBO Bettermann - description: Ion -render: - - default: | - type: template - template: obo - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 101 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/obo_2.yaml b/templates/release/en/charger/obo_2.yaml deleted file mode 100644 index 920581ce88..0000000000 --- a/templates/release/en/charger/obo_2.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Viridian EV - description: EVSE EPC 2.0 Plus -render: - - default: | - type: template - template: obo - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 101 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 101 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml b/templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml new file mode 100644 index 0000000000..406f9c4a3b --- /dev/null +++ b/templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml @@ -0,0 +1,107 @@ +template: ocpp +product: + identifier: ocpp-1-6j-compatible-smart-charging + description: OCPP 1.6J compatible (Smart Charging) + group: Generic support +capabilities: ["mA", "rfid", "1p3p"] +requirements: ["sponsorship", "skiptest"] +description: | + With OCPP the connection will be established from charger (client) to evcc (server). + The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. + By default, the first incoming connection with any station identifier is used. + In order to be able to clearly assign several charging points, the respective station identifier (`stationid: `) and connector number (`connector: `) must be configured. + Many wallboxes automatically add the `station id` to the backend URL, some have to do this manually `ws://:8887/`. + If the charger supports sending metering values, try to adjust the interval to a short time span (< 10s) . + Use your RFID tags (this allows e.g. vehicle identification) or set your charger to "free charging" or "autostart" to generate the transaction required for charging release. + + If the charger does not offer any option to start transactions locally, the `remotestart` advanced option can be used to automatically start a transaction as soon as a vehicle is connected. + This should only be necessary in exceptional cases. + + Requirements: + * If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration + * Backend URL (Central System) in the charger configuration: `ws://[evcc-adresse]:8887/` (possibly add `stationid`) + * Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar + * No encryption, no authentication, no password + * Local network connection + + The specific configuration and the actual usable functionality depend on the charger model and its software. + +render: + - default: | + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/ocpp-abb-tac_0.yaml b/templates/release/en/charger/ocpp-abb-tac_0.yaml deleted file mode 100644 index 2571c9f715..0000000000 --- a/templates/release/en/charger/ocpp-abb-tac_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: ABB - description: Terra AC -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf -render: - - default: | - type: template - template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-abl_0.yaml b/templates/release/en/charger/ocpp-abl_0.yaml deleted file mode 100644 index 873a13c83e..0000000000 --- a/templates/release/en/charger/ocpp-abl_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ABL Sursum - description: eMH2 -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-abl_1.yaml b/templates/release/en/charger/ocpp-abl_1.yaml deleted file mode 100644 index 48a737e753..0000000000 --- a/templates/release/en/charger/ocpp-abl_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ABL Sursum - description: eMH3 -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-abl_2.yaml b/templates/release/en/charger/ocpp-abl_2.yaml deleted file mode 100644 index f9650e62ba..0000000000 --- a/templates/release/en/charger/ocpp-abl_2.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ABL Sursum - description: eMH4 -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-alfen_0.yaml b/templates/release/en/charger/ocpp-alfen_0.yaml deleted file mode 100644 index 989176a199..0000000000 --- a/templates/release/en/charger/ocpp-alfen_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Alfen - description: Eve -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-autel_0.yaml b/templates/release/en/charger/ocpp-autel_0.yaml deleted file mode 100644 index 0883320b17..0000000000 --- a/templates/release/en/charger/ocpp-autel_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: AUTEL - description: AC MaxiCharger -capabilities: ["mA"] -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: - * In the Autel Charge app, click on “OCPP Server” - * In the search bar type “Custom” and select it. - * Server URL: ws://[evcc-address]:8887/ (local network connection) - * Charger ID: Leave empty (for use the serial number) or set custom value which is reused in configuration as *stationid* - * Authorisation Key: leave empty - -render: - - default: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-autel_1.yaml b/templates/release/en/charger/ocpp-autel_1.yaml deleted file mode 100644 index 6a545ff074..0000000000 --- a/templates/release/en/charger/ocpp-autel_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: AUTEL - description: AC Compact -capabilities: ["mA"] -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: - * In the Autel Charge app, click on “OCPP Server” - * In the search bar type “Custom” and select it. - * Server URL: ws://[evcc-address]:8887/ (local network connection) - * Charger ID: Leave empty (for use the serial number) or set custom value which is reused in configuration as *stationid* - * Authorisation Key: leave empty - -render: - - default: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-autoaid_0.yaml b/templates/release/en/charger/ocpp-autoaid_0.yaml deleted file mode 100644 index c68ca7e43f..0000000000 --- a/templates/release/en/charger/ocpp-autoaid_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Autoaid - description: Intelligent Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-autoaid_1.yaml b/templates/release/en/charger/ocpp-autoaid_1.yaml deleted file mode 100644 index c0240ecde7..0000000000 --- a/templates/release/en/charger/ocpp-autoaid_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Autoaid - description: Business Wallbox -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-beny_0.yaml b/templates/release/en/charger/ocpp-beny_0.yaml deleted file mode 100644 index e86a3af3ce..0000000000 --- a/templates/release/en/charger/ocpp-beny_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ZJ Beny - description: BCP EV charger -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-chargeamps_0.yaml b/templates/release/en/charger/ocpp-chargeamps_0.yaml deleted file mode 100644 index e8184d6426..0000000000 --- a/templates/release/en/charger/ocpp-chargeamps_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Charge Amps - description: Halo -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-elecq_0.yaml b/templates/release/en/charger/ocpp-elecq_0.yaml deleted file mode 100644 index 73b72693b7..0000000000 --- a/templates/release/en/charger/ocpp-elecq_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Elecq - description: Home -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-elecq_1.yaml b/templates/release/en/charger/ocpp-elecq_1.yaml deleted file mode 100644 index c0a3563bc8..0000000000 --- a/templates/release/en/charger/ocpp-elecq_1.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Elecq - description: Biz -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-elecq_2.yaml b/templates/release/en/charger/ocpp-elecq_2.yaml deleted file mode 100644 index 97e94949e4..0000000000 --- a/templates/release/en/charger/ocpp-elecq_2.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Elecq - description: Station -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-enercab_0.yaml b/templates/release/en/charger/ocpp-enercab_0.yaml deleted file mode 100644 index 655a212efc..0000000000 --- a/templates/release/en/charger/ocpp-enercab_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: enercab - description: smart -capabilities: ["1p3p"] -requirements: ["sponsorship", "skiptest"] -description: | - https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - -render: - - default: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-enercab_1.yaml b/templates/release/en/charger/ocpp-enercab_1.yaml deleted file mode 100644 index fd69e0665e..0000000000 --- a/templates/release/en/charger/ocpp-enercab_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: eledio - description: go -capabilities: ["1p3p"] -requirements: ["sponsorship", "skiptest"] -description: | - https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - -render: - - default: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-enplus_0.yaml b/templates/release/en/charger/ocpp-enplus_0.yaml deleted file mode 100644 index 891cc1b2d6..0000000000 --- a/templates/release/en/charger/ocpp-enplus_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EN+ - description: AC EV Charger -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-entratek_0.yaml b/templates/release/en/charger/ocpp-entratek_0.yaml deleted file mode 100644 index 0806f056e6..0000000000 --- a/templates/release/en/charger/ocpp-entratek_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EntraTek - description: Power Dot Fix -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-entratek_1.yaml b/templates/release/en/charger/ocpp-entratek_1.yaml deleted file mode 100644 index c37df2d328..0000000000 --- a/templates/release/en/charger/ocpp-entratek_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EntraTek - description: Power Dot Pro 2 -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-esolutions_0.yaml b/templates/release/en/charger/ocpp-esolutions_0.yaml deleted file mode 100644 index 2e8f02d6a5..0000000000 --- a/templates/release/en/charger/ocpp-esolutions_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Free2move eSolutions - description: eProWallbox -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-evbox-elvi_0.yaml b/templates/release/en/charger/ocpp-evbox-elvi_0.yaml deleted file mode 100644 index bfd7917b30..0000000000 --- a/templates/release/en/charger/ocpp-evbox-elvi_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: EVBox - description: Elvi -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional - advanced: | - type: template - template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-goe_0.yaml b/templates/release/en/charger/ocpp-goe_0.yaml deleted file mode 100644 index 3fa3cec78a..0000000000 --- a/templates/release/en/charger/ocpp-goe_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: go-e - description: Charger V3 -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-goe_1.yaml b/templates/release/en/charger/ocpp-goe_1.yaml deleted file mode 100644 index b76ac80dce..0000000000 --- a/templates/release/en/charger/ocpp-goe_1.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: go-e - description: Charger Gemini -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-goe_2.yaml b/templates/release/en/charger/ocpp-goe_2.yaml deleted file mode 100644 index 166693cde4..0000000000 --- a/templates/release/en/charger/ocpp-goe_2.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: go-e - description: Charger PRO -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-goe_3.yaml b/templates/release/en/charger/ocpp-goe_3.yaml deleted file mode 100644 index 4b206edb2d..0000000000 --- a/templates/release/en/charger/ocpp-goe_3.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Fronius - description: Wattpilot -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-homecharge_0.yaml b/templates/release/en/charger/ocpp-homecharge_0.yaml deleted file mode 100644 index 8bf16e858f..0000000000 --- a/templates/release/en/charger/ocpp-homecharge_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Homecharge - description: Homecharger -requirements: ["sponsorship", "skiptest"] -description: | - The charger must be equipped with a built-in meter (models HC11L/HC22L Energy or Profi). - For the OCPP configuration, you need to access the EFR-SECC charge controller at http://host/secc. - For login credentials, ask your dealer or the vendor EFR (www.efr.de). - -render: - - default: | - type: template - template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-huawei_0.yaml b/templates/release/en/charger/ocpp-huawei_0.yaml deleted file mode 100644 index b561592251..0000000000 --- a/templates/release/en/charger/ocpp-huawei_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Huawei - description: SCharger-7KS-S0 -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-huawei_1.yaml b/templates/release/en/charger/ocpp-huawei_1.yaml deleted file mode 100644 index 0796066754..0000000000 --- a/templates/release/en/charger/ocpp-huawei_1.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Huawei - description: SCharger-22KT-S0 -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-mennekes-acu_0.yaml b/templates/release/en/charger/ocpp-mennekes-acu_0.yaml deleted file mode 100644 index d8e731b409..0000000000 --- a/templates/release/en/charger/ocpp-mennekes-acu_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Mennekes - description: eMobility Gateway (ACU) -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - To configure, open the web interface of the ACU. - Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J - Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. - -render: - - default: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-mennekes-acu_1.yaml b/templates/release/en/charger/ocpp-mennekes-acu_1.yaml deleted file mode 100644 index 218405b290..0000000000 --- a/templates/release/en/charger/ocpp-mennekes-acu_1.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Mennekes - description: Smart (ACU) -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - To configure, open the web interface of the ACU. - Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J - Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. - -render: - - default: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-mennekes-acu_2.yaml b/templates/release/en/charger/ocpp-mennekes-acu_2.yaml deleted file mode 100644 index d569eefddd..0000000000 --- a/templates/release/en/charger/ocpp-mennekes-acu_2.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Mennekes - description: Smart T (ACU) -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - To configure, open the web interface of the ACU. - Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J - Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be entered here. Basic Authentication: Disabled. OCPP 1.6 Settings: Enable all options. - -render: - - default: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-orbis_0.yaml b/templates/release/en/charger/ocpp-orbis_0.yaml deleted file mode 100644 index 1350e23155..0000000000 --- a/templates/release/en/charger/ocpp-orbis_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Orbis - description: Viaris -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-sungrow_0.yaml b/templates/release/en/charger/ocpp-sungrow_0.yaml deleted file mode 100644 index 6aac284904..0000000000 --- a/templates/release/en/charger/ocpp-sungrow_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Sungrow - description: AC011E -capabilities: ["mA", "rfid"] -requirements: ["sponsorship", "skiptest"] -render: - - default: | - type: template - template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-wallbox_0.yaml b/templates/release/en/charger/ocpp-wallbox_0.yaml deleted file mode 100644 index 79286e348d..0000000000 --- a/templates/release/en/charger/ocpp-wallbox_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Plus -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-wallbox_1.yaml b/templates/release/en/charger/ocpp-wallbox_1.yaml deleted file mode 100644 index 2cfe10fc01..0000000000 --- a/templates/release/en/charger/ocpp-wallbox_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Max -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-wallbox_2.yaml b/templates/release/en/charger/ocpp-wallbox_2.yaml deleted file mode 100644 index 86d044dcdb..0000000000 --- a/templates/release/en/charger/ocpp-wallbox_2.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Commander 2 -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-wallbox_3.yaml b/templates/release/en/charger/ocpp-wallbox_3.yaml deleted file mode 100644 index 30ff13d052..0000000000 --- a/templates/release/en/charger/ocpp-wallbox_3.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Copper SB -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp-zaptec_0.yaml b/templates/release/en/charger/ocpp-zaptec_0.yaml deleted file mode 100644 index 711a95e839..0000000000 --- a/templates/release/en/charger/ocpp-zaptec_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Zaptec - description: Go -capabilities: ["rfid"] -requirements: ["sponsorship", "skiptest"] -description: | - OCPP Native mode - - https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ - -render: - - default: | - type: template - template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/ocpp_0.yaml b/templates/release/en/charger/ocpp_0.yaml deleted file mode 100644 index 2c7cbd4654..0000000000 --- a/templates/release/en/charger/ocpp_0.yaml +++ /dev/null @@ -1,41 +0,0 @@ -product: - description: OCPP 1.6J compatible (Smart Charging) - group: Generic support -capabilities: ["mA", "rfid", "1p3p"] -requirements: ["sponsorship", "skiptest"] -description: | - With OCPP the connection will be established from charger (client) to evcc (server). - The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. - By default, the first incoming connection with any station identifier is used. - In order to be able to clearly assign several charging points, the respective station identifier (`stationid: `) and connector number (`connector: `) must be configured. - Many wallboxes automatically add the `station id` to the backend URL, some have to do this manually `ws://:8887/`. - If the charger supports sending metering values, try to adjust the interval to a short time span (< 10s) . - Use your RFID tags (this allows e.g. vehicle identification) or set your charger to "free charging" or "autostart" to generate the transaction required for charging release. - - If the charger does not offer any option to start transactions locally, the `remotestart` advanced option can be used to automatically start a transaction as soon as a vehicle is connected. - This should only be necessary in exceptional cases. - - Requirements: - * If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration - * Backend URL (Central System) in the charger configuration: `ws://[evcc-adresse]:8887/` (possibly add `stationid`) - * Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar - * No encryption, no authentication, no password - * Local network connection - - The specific configuration and the actual usable functionality depend on the charger model and its software. - -render: - - default: | - type: template - template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/openevse.yaml b/templates/release/en/charger/openevse.yaml new file mode 100644 index 0000000000..16a5e08cbd --- /dev/null +++ b/templates/release/en/charger/openevse.yaml @@ -0,0 +1,41 @@ +template: openevse +product: + identifier: openevse + brand: OpenEVSE +description: | + Requires firmware 7.0 or later. +render: + - default: | + type: template + template: openevse + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/openevse_0.yaml b/templates/release/en/charger/openevse_0.yaml deleted file mode 100644 index 4cd324e5f9..0000000000 --- a/templates/release/en/charger/openevse_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: OpenEVSE -description: | - Requires firmware 7.0 or later. -render: - - default: | - type: template - template: openevse - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/openwb-2.0_0.yaml b/templates/release/en/charger/openwb-2.0_0.yaml deleted file mode 100644 index c9af74d9c1..0000000000 --- a/templates/release/en/charger/openwb-2.0_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: openWB - description: Software 2.x -capabilities: ["1p3p", "mA", "rfid"] -description: | - Requires [`Software 2.x`](https://github.com/openWB/core). - The following changes are necessary under the 'Einstellungen' tab: - - * Steuerungsmodus: `secondary` - * Steuerung über Modbus als secondary: `An` - -render: - - default: | - type: template - template: openwb-2.0 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: openwb-2.0 - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional - phases1p3p: true # Charger is equipped with phase switching feature, optional diff --git a/templates/release/en/charger/openwb-pro.yaml b/templates/release/en/charger/openwb-pro.yaml new file mode 100644 index 0000000000..9430b28082 --- /dev/null +++ b/templates/release/en/charger/openwb-pro.yaml @@ -0,0 +1,21 @@ +template: openwb-pro +product: + identifier: openwb-pro + brand: openWB + description: Pro +capabilities: ["1p3p", "mA", "iso151182"] +render: + - default: | + type: template + template: openwb-pro + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/openwb-pro_0.yaml b/templates/release/en/charger/openwb-pro_0.yaml deleted file mode 100644 index 3bc89ce0bd..0000000000 --- a/templates/release/en/charger/openwb-pro_0.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: openWB - description: Pro -capabilities: ["1p3p", "mA", "iso151182"] -render: - - default: | - type: template - template: openwb-pro - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/openwb-series2.yaml b/templates/release/en/charger/openwb-series2.yaml new file mode 100644 index 0000000000..bc3d7d67eb --- /dev/null +++ b/templates/release/en/charger/openwb-series2.yaml @@ -0,0 +1,46 @@ +template: openwb +product: + identifier: openwb-series2 + brand: openWB + description: series2 +description: | + The wallbox has to be configured as loadpoint. +render: + - default: | + type: template + template: openwb + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: openwb + host: 192.0.2.2 # IP address or hostname + connector: 1 # Loadpoint (if >1 loadpoint), optional + phases1p3p: false # Charger is equipped with phase switching feature, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: Charger is equipped with phase switching feature + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/openwb-software-2-x.yaml b/templates/release/en/charger/openwb-software-2-x.yaml new file mode 100644 index 0000000000..67481d919f --- /dev/null +++ b/templates/release/en/charger/openwb-software-2-x.yaml @@ -0,0 +1,68 @@ +template: openwb-2.0 +product: + identifier: openwb-software-2-x + brand: openWB + description: Software 2.x +capabilities: ["1p3p", "mA", "rfid"] +description: | + Requires [`Software 2.x`](https://github.com/openWB/core). + The following changes are necessary under the 'Einstellungen' tab: + + * Steuerungsmodus: `secondary` + * Steuerung über Modbus als secondary: `An` + +render: + - default: | + type: template + template: openwb-2.0 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: openwb-2.0 + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional + phases1p3p: true # Charger is equipped with phase switching feature, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true + - name: phases1p3p + example: + default: true + choice: [] + unit: + description: Charger is equipped with phase switching feature + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/openwb_0.yaml b/templates/release/en/charger/openwb_0.yaml deleted file mode 100644 index c998e58f52..0000000000 --- a/templates/release/en/charger/openwb_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: openWB - description: series2 -description: | - The wallbox has to be configured as loadpoint. -render: - - default: | - type: template - template: openwb - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: openwb - host: 192.0.2.2 # IP address or hostname - connector: 1 # Loadpoint (if >1 loadpoint), optional - phases1p3p: false # Charger is equipped with phase switching feature, optional diff --git a/templates/release/en/charger/optec-mobility-one.yaml b/templates/release/en/charger/optec-mobility-one.yaml new file mode 100644 index 0000000000..9ebb1648ad --- /dev/null +++ b/templates/release/en/charger/optec-mobility-one.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: optec-mobility-one + brand: Optec + description: Mobility One +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/orbis-viaris.yaml b/templates/release/en/charger/orbis-viaris.yaml new file mode 100644 index 0000000000..16e797ffa5 --- /dev/null +++ b/templates/release/en/charger/orbis-viaris.yaml @@ -0,0 +1,85 @@ +template: ocpp-orbis +product: + identifier: orbis-viaris + brand: Orbis + description: Viaris +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-orbis + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-orbis + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/pantabox_0.yaml b/templates/release/en/charger/pantabox_0.yaml deleted file mode 100644 index 1607b7c68d..0000000000 --- a/templates/release/en/charger/pantabox_0.yaml +++ /dev/null @@ -1,8 +0,0 @@ -product: - brand: INRO - description: Pantabox -render: - - default: | - type: template - template: pantabox - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/pc-electric-garo.yaml b/templates/release/en/charger/pc-electric-garo.yaml new file mode 100644 index 0000000000..c02f24095d --- /dev/null +++ b/templates/release/en/charger/pc-electric-garo.yaml @@ -0,0 +1,33 @@ +template: pcelectric-garo +product: + identifier: pc-electric-garo + brand: PC Electric + description: Garo +requirements: ["sponsorship"] +description: | + Only devices configured as master can be used right now! +render: + - default: | + type: template + template: pcelectric-garo + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8080 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/pcelectric-garo_0.yaml b/templates/release/en/charger/pcelectric-garo_0.yaml deleted file mode 100644 index ad8becdfcc..0000000000 --- a/templates/release/en/charger/pcelectric-garo_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: PC Electric - description: Garo -requirements: ["sponsorship"] -description: | - Only devices configured as master can be used right now! -render: - - default: | - type: template - template: pcelectric-garo - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional diff --git a/templates/release/en/charger/peblar-business.yaml b/templates/release/en/charger/peblar-business.yaml new file mode 100644 index 0000000000..4e05b5a4df --- /dev/null +++ b/templates/release/en/charger/peblar-business.yaml @@ -0,0 +1,35 @@ +template: peblar +product: + identifier: peblar-business + brand: Peblar + description: Business +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. +render: + - default: | + type: template + template: peblar + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/peblar-home-plus.yaml b/templates/release/en/charger/peblar-home-plus.yaml new file mode 100644 index 0000000000..a289474e50 --- /dev/null +++ b/templates/release/en/charger/peblar-home-plus.yaml @@ -0,0 +1,35 @@ +template: peblar +product: + identifier: peblar-home-plus + brand: Peblar + description: Home Plus +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. +render: + - default: | + type: template + template: peblar + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/peblar-home.yaml b/templates/release/en/charger/peblar-home.yaml new file mode 100644 index 0000000000..4d94c82455 --- /dev/null +++ b/templates/release/en/charger/peblar-home.yaml @@ -0,0 +1,35 @@ +template: peblar +product: + identifier: peblar-home + brand: Peblar + description: Home +capabilities: ["1p3p", "mA"] +requirements: ["sponsorship"] +description: | + Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. +render: + - default: | + type: template + template: peblar + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/peblar_0.yaml b/templates/release/en/charger/peblar_0.yaml deleted file mode 100644 index 9f40acc89d..0000000000 --- a/templates/release/en/charger/peblar_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Peblar - description: Home -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. -render: - - default: | - type: template - template: peblar - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/peblar_1.yaml b/templates/release/en/charger/peblar_1.yaml deleted file mode 100644 index 36fef832ad..0000000000 --- a/templates/release/en/charger/peblar_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Peblar - description: Home Plus -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. -render: - - default: | - type: template - template: peblar - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/peblar_2.yaml b/templates/release/en/charger/peblar_2.yaml deleted file mode 100644 index 2a2d62886a..0000000000 --- a/templates/release/en/charger/peblar_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Peblar - description: Business -capabilities: ["1p3p", "mA"] -requirements: ["sponsorship"] -description: | - Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. -render: - - default: | - type: template - template: peblar - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-charx_0.yaml b/templates/release/en/charger/phoenix-charx_0.yaml deleted file mode 100644 index b260dee1a2..0000000000 --- a/templates/release/en/charger/phoenix-charx_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Phoenix Contact - description: CHARX -render: - - default: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/phoenix-charx_1.yaml b/templates/release/en/charger/phoenix-charx_1.yaml deleted file mode 100644 index 211884ab42..0000000000 --- a/templates/release/en/charger/phoenix-charx_1.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: LadeFoxx - description: EvLoad -render: - - default: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/phoenix-charx_2.yaml b/templates/release/en/charger/phoenix-charx_2.yaml deleted file mode 100644 index 8723fb07a6..0000000000 --- a/templates/release/en/charger/phoenix-charx_2.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: LadeFoxx - description: Mikro 2.0 -render: - - default: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: phoenix-charx - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/phoenix-contact-charx.yaml b/templates/release/en/charger/phoenix-contact-charx.yaml new file mode 100644 index 0000000000..ddd15513c8 --- /dev/null +++ b/templates/release/en/charger/phoenix-contact-charx.yaml @@ -0,0 +1,50 @@ +template: phoenix-charx +product: + identifier: phoenix-contact-charx + brand: Phoenix Contact + description: CHARX +render: + - default: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: phoenix-charx + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml b/templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml new file mode 100644 index 0000000000..61f1ab493f --- /dev/null +++ b/templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml @@ -0,0 +1,31 @@ +template: phoenix-em-eth +product: + identifier: phoenix-contact-em-cp-pp-eth + brand: Phoenix Contact + description: EM-CP-PP-ETH +render: + - default: | + type: template + template: phoenix-em-eth + + # Modbus TCP + modbus: tcpip + id: 180 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 180 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml new file mode 100644 index 0000000000..f649ef2acb --- /dev/null +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g + brand: Phoenix Contact + description: EV-CC-AC1-M3-CBC-RCM-ETH-3G +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml new file mode 100644 index 0000000000..99b79a1724 --- /dev/null +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth + brand: Phoenix Contact + description: EV-CC-AC1-M3-CBC-RCM-ETH +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml new file mode 100644 index 0000000000..5d18695bda --- /dev/null +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp + brand: Phoenix Contact + description: EV-CC-AC1-M3-RCM-ETH-3G-XP +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml new file mode 100644 index 0000000000..2d7353b28a --- /dev/null +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp + brand: Phoenix Contact + description: EV-CC-AC1-M3-RCM-ETH-XP +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/phoenix-contact-ev-ser.yaml b/templates/release/en/charger/phoenix-contact-ev-ser.yaml new file mode 100644 index 0000000000..ff1e20eb68 --- /dev/null +++ b/templates/release/en/charger/phoenix-contact-ev-ser.yaml @@ -0,0 +1,41 @@ +template: phoenix-ev-ser +product: + identifier: phoenix-contact-ev-ser + brand: Phoenix Contact + description: EV-SER +render: + - default: | + type: template + template: phoenix-ev-ser + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/phoenix-em-eth_0.yaml b/templates/release/en/charger/phoenix-em-eth_0.yaml deleted file mode 100644 index 761efe9d6d..0000000000 --- a/templates/release/en/charger/phoenix-em-eth_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Phoenix Contact - description: EM-CP-PP-ETH -render: - - default: | - type: template - template: phoenix-em-eth - - # Modbus TCP - modbus: tcpip - id: 180 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_0.yaml b/templates/release/en/charger/phoenix-ev-eth_0.yaml deleted file mode 100644 index e47b91f6d3..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-CBC-RCM-ETH -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_1.yaml b/templates/release/en/charger/phoenix-ev-eth_1.yaml deleted file mode 100644 index 4bad74acba..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-CBC-RCM-ETH-3G -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_2.yaml b/templates/release/en/charger/phoenix-ev-eth_2.yaml deleted file mode 100644 index 848da21357..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-RCM-ETH-XP -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_3.yaml b/templates/release/en/charger/phoenix-ev-eth_3.yaml deleted file mode 100644 index 0492909392..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-CC-AC1-M3-RCM-ETH-3G-XP -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_4.yaml b/templates/release/en/charger/phoenix-ev-eth_4.yaml deleted file mode 100644 index 9129df7521..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Wallbe - description: Eco -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_5.yaml b/templates/release/en/charger/phoenix-ev-eth_5.yaml deleted file mode 100644 index 0d95d417e4..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_5.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Wallbe - description: Eco 2.0(s) -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_6.yaml b/templates/release/en/charger/phoenix-ev-eth_6.yaml deleted file mode 100644 index e1ccc8be99..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_6.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Wallbe - description: Pro -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_7.yaml b/templates/release/en/charger/phoenix-ev-eth_7.yaml deleted file mode 100644 index dfd172c24c..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_7.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: ESL - description: Walli LIGHT -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-eth_8.yaml b/templates/release/en/charger/phoenix-ev-eth_8.yaml deleted file mode 100644 index a1f93d4917..0000000000 --- a/templates/release/en/charger/phoenix-ev-eth_8.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: E3/DC - description: Easy Connect -capabilities: ["mA", "rfid"] -requirements: ["sponsorship"] -description: | - DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. -render: - - default: | - type: template - template: phoenix-ev-eth - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/phoenix-ev-ser_0.yaml b/templates/release/en/charger/phoenix-ev-ser_0.yaml deleted file mode 100644 index 63128dfb43..0000000000 --- a/templates/release/en/charger/phoenix-ev-ser_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Phoenix Contact - description: EV-SER -render: - - default: | - type: template - template: phoenix-ev-ser - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/plugchoice.yaml b/templates/release/en/charger/plugchoice.yaml new file mode 100644 index 0000000000..2288c51f42 --- /dev/null +++ b/templates/release/en/charger/plugchoice.yaml @@ -0,0 +1,56 @@ +template: plugchoice +product: + identifier: plugchoice + brand: Plugchoice + group: Generic support +requirements: ["sponsorship"] +description: | + Chargers connected through Plugchoice can leverage its OCPP proxy functionality to establish a connection to other backoffices while maintaining full control through EVCC. This allows seamless management of Plugchoice-registered chargers directly from EVCC. + + For improved meter readings, it is recommended to configure the following settings in the Plugchoice portal under the configuration tab: + + - Set `MeterValueSampleInterval` to 10 seconds (or another interval according to your preference). + - Set `MeterValuesSampledData` to `Energy.Active.Import.Register,Current.Offered,Current.Import,Voltage`. + + These adjustments enable more frequent and detailed reporting of charging data to EVCC. + +render: + - default: | + type: template + template: plugchoice + token: # API Token + identity: # Charger identity (e.g. AA123456) + advanced: | + type: template + template: plugchoice + token: # API Token + identity: # Charger identity (e.g. AA123456) + connector: 1 # Loadpoint (if >1 loadpoint), Connector ID (usually 1) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token + advanced: false + optional: false + - name: identity + example: + default: + choice: [] + unit: + description: + help: Charger identity (e.g. AA123456) + advanced: false + optional: false + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: Connector ID (usually 1) + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/plugchoice_0.yaml b/templates/release/en/charger/plugchoice_0.yaml deleted file mode 100644 index 4a13f6125e..0000000000 --- a/templates/release/en/charger/plugchoice_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Plugchoice - group: Generic support -requirements: ["sponsorship"] -description: | - Chargers connected through Plugchoice can leverage its OCPP proxy functionality to establish a connection to other backoffices while maintaining full control through EVCC. This allows seamless management of Plugchoice-registered chargers directly from EVCC. - - For improved meter readings, it is recommended to configure the following settings in the Plugchoice portal under the configuration tab: - - - Set `MeterValueSampleInterval` to 10 seconds (or another interval according to your preference). - - Set `MeterValuesSampledData` to `Energy.Active.Import.Register,Current.Offered,Current.Import,Voltage`. - - These adjustments enable more frequent and detailed reporting of charging data to EVCC. - -render: - - default: | - type: template - template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456) - advanced: | - type: template - template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456) - connector: 1 # Loadpoint (if >1 loadpoint), Connector ID (usually 1) diff --git a/templates/release/en/charger/pmcc_0.yaml b/templates/release/en/charger/pmcc_0.yaml deleted file mode 100644 index 694b97a243..0000000000 --- a/templates/release/en/charger/pmcc_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: Porsche - description: Mobile Charger Connect -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -render: - - default: | - type: template - template: pmcc - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/pmcp_0.yaml b/templates/release/en/charger/pmcp_0.yaml deleted file mode 100644 index e1d7dadb66..0000000000 --- a/templates/release/en/charger/pmcp_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Porsche - description: Mobile Charger Plus -requirements: ["eebus"] -render: - - default: | - type: template - template: pmcp - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/porsche-mobile-charger-connect.yaml b/templates/release/en/charger/porsche-mobile-charger-connect.yaml new file mode 100644 index 0000000000..6af404458a --- /dev/null +++ b/templates/release/en/charger/porsche-mobile-charger-connect.yaml @@ -0,0 +1,32 @@ +template: pmcc +product: + identifier: porsche-mobile-charger-connect + brand: Porsche + description: Mobile Charger Connect +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +render: + - default: | + type: template + template: pmcc + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/porsche-mobile-charger-plus.yaml b/templates/release/en/charger/porsche-mobile-charger-plus.yaml new file mode 100644 index 0000000000..0fd67cdd1b --- /dev/null +++ b/templates/release/en/charger/porsche-mobile-charger-plus.yaml @@ -0,0 +1,31 @@ +template: pmcp +product: + identifier: porsche-mobile-charger-plus + brand: Porsche + description: Mobile Charger Plus +requirements: ["eebus"] +render: + - default: | + type: template + template: pmcp + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/porsche-wallbox.yaml b/templates/release/en/charger/porsche-wallbox.yaml new file mode 100644 index 0000000000..695ea88a51 --- /dev/null +++ b/templates/release/en/charger/porsche-wallbox.yaml @@ -0,0 +1,39 @@ +template: porsche-wallbox +product: + identifier: porsche-wallbox + brand: Porsche + description: Wallbox +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: porsche-wallbox + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/porsche-wallbox_0.yaml b/templates/release/en/charger/porsche-wallbox_0.yaml deleted file mode 100644 index 9b9e7327a3..0000000000 --- a/templates/release/en/charger/porsche-wallbox_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: Porsche - description: Wallbox -capabilities: ["iso151182", "mA"] -requirements: ["eebus"] -description: | - The device has to be used in the normal charging mode. - - The usage of phase switching is currently not possible in evcc. - - The identification of a vehicle using the RFID card is not possible. - -render: - - default: | - type: template - template: porsche-wallbox - ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox - ip: 192.0.2.2 # IP address, optional diff --git a/templates/release/en/charger/pracht-alpha-xt.yaml b/templates/release/en/charger/pracht-alpha-xt.yaml new file mode 100644 index 0000000000..691bd21ded --- /dev/null +++ b/templates/release/en/charger/pracht-alpha-xt.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-alpha-xt + brand: Pracht + description: Alpha XT +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/pracht-alpha_0.yaml b/templates/release/en/charger/pracht-alpha_0.yaml deleted file mode 100644 index b663d3b0ec..0000000000 --- a/templates/release/en/charger/pracht-alpha_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: Alpha XT -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/pracht-alpha_1.yaml b/templates/release/en/charger/pracht-alpha_1.yaml deleted file mode 100644 index a302f13f83..0000000000 --- a/templates/release/en/charger/pracht-alpha_1.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: XT+ -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/pracht-alpha_2.yaml b/templates/release/en/charger/pracht-alpha_2.yaml deleted file mode 100644 index 4bcd02ce8e..0000000000 --- a/templates/release/en/charger/pracht-alpha_2.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: Mono XT -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/pracht-alpha_3.yaml b/templates/release/en/charger/pracht-alpha_3.yaml deleted file mode 100644 index 44d13e9930..0000000000 --- a/templates/release/en/charger/pracht-alpha_3.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Pracht - description: PNI -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: pracht-alpha - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - connector: 1 # Loadpoint (if >1 loadpoint), optional diff --git a/templates/release/en/charger/pracht-mono-xt.yaml b/templates/release/en/charger/pracht-mono-xt.yaml new file mode 100644 index 0000000000..28323f4f86 --- /dev/null +++ b/templates/release/en/charger/pracht-mono-xt.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-mono-xt + brand: Pracht + description: Mono XT +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/pracht-pni.yaml b/templates/release/en/charger/pracht-pni.yaml new file mode 100644 index 0000000000..cb145e826c --- /dev/null +++ b/templates/release/en/charger/pracht-pni.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-pni + brand: Pracht + description: PNI +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/pracht-xtplus.yaml b/templates/release/en/charger/pracht-xtplus.yaml new file mode 100644 index 0000000000..3e44cdb035 --- /dev/null +++ b/templates/release/en/charger/pracht-xtplus.yaml @@ -0,0 +1,92 @@ +template: pracht-alpha +product: + identifier: pracht-xtplus + brand: Pracht + description: XT+ +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: pracht-alpha + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + connector: 1 # Loadpoint (if >1 loadpoint), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Loadpoint (if >1 loadpoint) + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/pulsares-simplebox.yaml b/templates/release/en/charger/pulsares-simplebox.yaml new file mode 100644 index 0000000000..089c80a4d5 --- /dev/null +++ b/templates/release/en/charger/pulsares-simplebox.yaml @@ -0,0 +1,41 @@ +template: pulsares +product: + identifier: pulsares-simplebox + brand: Pulsares + description: SimpleBox +render: + - default: | + type: template + template: pulsares + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/pulsares_0.yaml b/templates/release/en/charger/pulsares_0.yaml deleted file mode 100644 index 3b68b02181..0000000000 --- a/templates/release/en/charger/pulsares_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Pulsares - description: SimpleBox -render: - - default: | - type: template - template: pulsares - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/pulsatrix.yaml b/templates/release/en/charger/pulsatrix.yaml new file mode 100644 index 0000000000..b2edd2796a --- /dev/null +++ b/templates/release/en/charger/pulsatrix.yaml @@ -0,0 +1,20 @@ +template: pulsatrix +product: + identifier: pulsatrix + brand: Pulsatrix +requirements: ["sponsorship"] +render: + - default: | + type: template + template: pulsatrix + host: 192.0.2.2 # IP address or hostname, Shown on 3rd page of SECC display +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: Shown on 3rd page of SECC display + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/pulsatrix_0.yaml b/templates/release/en/charger/pulsatrix_0.yaml deleted file mode 100644 index d9836d7330..0000000000 --- a/templates/release/en/charger/pulsatrix_0.yaml +++ /dev/null @@ -1,8 +0,0 @@ -product: - brand: Pulsatrix -requirements: ["sponsorship"] -render: - - default: | - type: template - template: pulsatrix - host: 192.0.2.2 # IP address or hostname, Shown on 3rd page of SECC display diff --git a/templates/release/en/charger/qcells-q-home-edrive-a.yaml b/templates/release/en/charger/qcells-q-home-edrive-a.yaml new file mode 100644 index 0000000000..0292ea895a --- /dev/null +++ b/templates/release/en/charger/qcells-q-home-edrive-a.yaml @@ -0,0 +1,45 @@ +template: solax +product: + identifier: qcells-q-home-edrive-a + brand: Qcells + description: Q.HOME EDRIVE A +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be in “Fast” mode and decoupled from the inverter system. +render: + - default: | + type: template + template: solax + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 70 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 70 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 70 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/roth-thermoaura.yaml b/templates/release/en/charger/roth-thermoaura.yaml new file mode 100644 index 0000000000..0fae90c9fd --- /dev/null +++ b/templates/release/en/charger/roth-thermoaura.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: roth-thermoaura + brand: Roth + description: ThermoAura + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/roth-thermoterra.yaml b/templates/release/en/charger/roth-thermoterra.yaml new file mode 100644 index 0000000000..62cc89cb8a --- /dev/null +++ b/templates/release/en/charger/roth-thermoterra.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: roth-thermoterra + brand: Roth + description: ThermoTerra + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/schneider-evlink-pro.yaml b/templates/release/en/charger/schneider-evlink-pro.yaml new file mode 100644 index 0000000000..2204af38ba --- /dev/null +++ b/templates/release/en/charger/schneider-evlink-pro.yaml @@ -0,0 +1,32 @@ +template: schneider-evlink-v3 +product: + identifier: schneider-evlink-pro + brand: Schneider + description: EVlink Pro +requirements: ["sponsorship"] +render: + - default: | + type: template + template: schneider-evlink-v3 + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/schneider-evlink-v3_0.yaml b/templates/release/en/charger/schneider-evlink-v3_0.yaml deleted file mode 100644 index 080654a253..0000000000 --- a/templates/release/en/charger/schneider-evlink-v3_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Schneider - description: EVlink Pro -requirements: ["sponsorship"] -render: - - default: | - type: template - template: schneider-evlink-v3 - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/schrack-i-charge-cion.yaml b/templates/release/en/charger/schrack-i-charge-cion.yaml new file mode 100644 index 0000000000..921cd93531 --- /dev/null +++ b/templates/release/en/charger/schrack-i-charge-cion.yaml @@ -0,0 +1,41 @@ +template: ichargecion +product: + identifier: schrack-i-charge-cion + brand: Schrack + description: i-CHARGE CION +render: + - default: | + type: template + template: ichargecion + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/senec-wallbox-pro-s.yaml b/templates/release/en/charger/senec-wallbox-pro-s.yaml new file mode 100644 index 0000000000..4db76c3745 --- /dev/null +++ b/templates/release/en/charger/senec-wallbox-pro-s.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: senec-wallbox-pro-s + brand: SENEC + description: Wallbox pro s +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/senec-wallbox-pro.yaml b/templates/release/en/charger/senec-wallbox-pro.yaml new file mode 100644 index 0000000000..8dd32cad59 --- /dev/null +++ b/templates/release/en/charger/senec-wallbox-pro.yaml @@ -0,0 +1,53 @@ +template: abl +product: + identifier: senec-wallbox-pro + brand: SENEC + description: Wallbox pro +capabilities: ["mA"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: abl + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 38400 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true +modbus: + baudrate: 38400 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/shelly-1.yaml b/templates/release/en/charger/shelly-1.yaml new file mode 100644 index 0000000000..2725ecee02 --- /dev/null +++ b/templates/release/en/charger/shelly-1.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-1 + brand: Shelly + description: 1 + group: Switchable sockets +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/shelly-plug-s.yaml b/templates/release/en/charger/shelly-plug-s.yaml new file mode 100644 index 0000000000..4450095afd --- /dev/null +++ b/templates/release/en/charger/shelly-plug-s.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-plug-s + brand: Shelly + description: Plug S + group: Switchable sockets +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/shelly-plus-1.yaml b/templates/release/en/charger/shelly-plus-1.yaml new file mode 100644 index 0000000000..baf2926e51 --- /dev/null +++ b/templates/release/en/charger/shelly-plus-1.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-plus-1 + brand: Shelly + description: Plus 1 + group: Switchable sockets +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/shelly-pro-1.yaml b/templates/release/en/charger/shelly-pro-1.yaml new file mode 100644 index 0000000000..b7d6bcba1f --- /dev/null +++ b/templates/release/en/charger/shelly-pro-1.yaml @@ -0,0 +1,99 @@ +template: shelly +product: + identifier: shelly-pro-1 + brand: Shelly + description: Pro 1 + group: Switchable sockets +render: + - default: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: shelly + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/shelly_0.yaml b/templates/release/en/charger/shelly_0.yaml deleted file mode 100644 index ab11ba5244..0000000000 --- a/templates/release/en/charger/shelly_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: Shelly - group: Switchable sockets -render: - - default: | - type: template - template: shelly - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: shelly - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/siemens-versicharge-gen3.yaml b/templates/release/en/charger/siemens-versicharge-gen3.yaml new file mode 100644 index 0000000000..c52fe42c88 --- /dev/null +++ b/templates/release/en/charger/siemens-versicharge-gen3.yaml @@ -0,0 +1,34 @@ +template: versicharge +product: + identifier: siemens-versicharge-gen3 + brand: Siemens + description: Versicharge GEN3 +requirements: ["sponsorship"] +description: | + Requires firmware >= 2.135 +render: + - default: | + type: template + template: versicharge + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/skoda-charger-connect.yaml b/templates/release/en/charger/skoda-charger-connect.yaml new file mode 100644 index 0000000000..de595b2a8a --- /dev/null +++ b/templates/release/en/charger/skoda-charger-connect.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: skoda-charger-connect + brand: Skoda + description: Charger Connect +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/skoda-charger-pro-eichrecht.yaml b/templates/release/en/charger/skoda-charger-pro-eichrecht.yaml new file mode 100644 index 0000000000..7d3173f522 --- /dev/null +++ b/templates/release/en/charger/skoda-charger-pro-eichrecht.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: skoda-charger-pro-eichrecht + brand: Skoda + description: Charger Pro Eichrecht +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/skoda-charger-pro.yaml b/templates/release/en/charger/skoda-charger-pro.yaml new file mode 100644 index 0000000000..d653e94f40 --- /dev/null +++ b/templates/release/en/charger/skoda-charger-pro.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: skoda-charger-pro + brand: Skoda + description: Charger Pro +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/skoda-iv-charger-connect.yaml b/templates/release/en/charger/skoda-iv-charger-connect.yaml new file mode 100644 index 0000000000..64ba65c000 --- /dev/null +++ b/templates/release/en/charger/skoda-iv-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: skoda-iv-charger-connect + brand: Skoda + description: iV Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/skoda-iv-charger-connectplus.yaml b/templates/release/en/charger/skoda-iv-charger-connectplus.yaml new file mode 100644 index 0000000000..4ed650dada --- /dev/null +++ b/templates/release/en/charger/skoda-iv-charger-connectplus.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: skoda-iv-charger-connectplus + brand: Skoda + description: iV Charger Connect+ +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +render: + - default: | + type: template + template: ellipro + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/sma-echarger.yaml b/templates/release/en/charger/sma-echarger.yaml new file mode 100644 index 0000000000..5593307269 --- /dev/null +++ b/templates/release/en/charger/sma-echarger.yaml @@ -0,0 +1,44 @@ +template: smaevcharger +product: + identifier: sma-echarger + brand: SMA + description: eCharger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. +render: + - default: | + type: template + template: smaevcharger + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/sma-ev-charger.yaml b/templates/release/en/charger/sma-ev-charger.yaml new file mode 100644 index 0000000000..cb4092d4d3 --- /dev/null +++ b/templates/release/en/charger/sma-ev-charger.yaml @@ -0,0 +1,44 @@ +template: smaevcharger +product: + identifier: sma-ev-charger + brand: SMA + description: EV Charger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. +render: + - default: | + type: template + template: smaevcharger + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/smaevcharger_0.yaml b/templates/release/en/charger/smaevcharger_0.yaml deleted file mode 100644 index a93e45eb92..0000000000 --- a/templates/release/en/charger/smaevcharger_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: SMA - description: EV Charger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. -render: - - default: | - type: template - template: smaevcharger - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros diff --git a/templates/release/en/charger/smaevcharger_1.yaml b/templates/release/en/charger/smaevcharger_1.yaml deleted file mode 100644 index 589cbc8047..0000000000 --- a/templates/release/en/charger/smaevcharger_1.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: SMA - description: eCharger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. -render: - - default: | - type: template - template: smaevcharger - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros diff --git a/templates/release/en/charger/smartevse_0.yaml b/templates/release/en/charger/smartevse_0.yaml deleted file mode 100644 index 4ef89c2ede..0000000000 --- a/templates/release/en/charger/smartevse_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - brand: Edgetech - description: Smart EVSE -capabilities: ["1p3p"] -render: - - default: | - type: template - template: smartevse - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/smartfox-pro-charger.yaml b/templates/release/en/charger/smartfox-pro-charger.yaml new file mode 100644 index 0000000000..488e3de539 --- /dev/null +++ b/templates/release/en/charger/smartfox-pro-charger.yaml @@ -0,0 +1,41 @@ +template: ichargecion +product: + identifier: smartfox-pro-charger + brand: Smartfox + description: Pro Charger +render: + - default: | + type: template + template: ichargecion + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/smartwb.yaml b/templates/release/en/charger/smartwb.yaml new file mode 100644 index 0000000000..98717b891e --- /dev/null +++ b/templates/release/en/charger/smartwb.yaml @@ -0,0 +1,19 @@ +template: smartwb +product: + identifier: smartwb + description: smartWB +render: + - default: | + type: template + template: smartwb + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/smartwb_0.yaml b/templates/release/en/charger/smartwb_0.yaml deleted file mode 100644 index b8c3cce0b8..0000000000 --- a/templates/release/en/charger/smartwb_0.yaml +++ /dev/null @@ -1,7 +0,0 @@ -product: - description: smartWB -render: - - default: | - type: template - template: smartwb - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/solaredge-home-ev-charger.yaml b/templates/release/en/charger/solaredge-home-ev-charger.yaml new file mode 100644 index 0000000000..d554fb8398 --- /dev/null +++ b/templates/release/en/charger/solaredge-home-ev-charger.yaml @@ -0,0 +1,54 @@ +template: keba-modbus +product: + identifier: solaredge-home-ev-charger + brand: SolarEdge + description: Home EV Charger +capabilities: ["1p3p", "mA", "rfid"] +requirements: ["sponsorship"] +description: | + Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. +render: + - default: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: keba-modbus + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/solax-x3-evc.yaml b/templates/release/en/charger/solax-x3-evc.yaml new file mode 100644 index 0000000000..8887f4b2e0 --- /dev/null +++ b/templates/release/en/charger/solax-x3-evc.yaml @@ -0,0 +1,45 @@ +template: solax +product: + identifier: solax-x3-evc + brand: Solax + description: X3-EVC +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be in “Fast” mode and decoupled from the inverter system. +render: + - default: | + type: template + template: solax + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 70 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 70 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 70 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/solax_0.yaml b/templates/release/en/charger/solax_0.yaml deleted file mode 100644 index dfb8f568e4..0000000000 --- a/templates/release/en/charger/solax_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Solax - description: X3-EVC -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be in “Fast” mode and decoupled from the inverter system. -render: - - default: | - type: template - template: solax - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 70 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 70 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/solax_1.yaml b/templates/release/en/charger/solax_1.yaml deleted file mode 100644 index 98a778749a..0000000000 --- a/templates/release/en/charger/solax_1.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Tigo - description: GO EV Charger -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be in “Fast” mode and decoupled from the inverter system. -render: - - default: | - type: template - template: solax - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 70 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 70 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/solax_2.yaml b/templates/release/en/charger/solax_2.yaml deleted file mode 100644 index 20940b0c12..0000000000 --- a/templates/release/en/charger/solax_2.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Qcells - description: Q.HOME EDRIVE A -capabilities: ["mA"] -requirements: ["sponsorship"] -description: | - The charger must be in “Fast” mode and decoupled from the inverter system. -render: - - default: | - type: template - template: solax - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 70 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 70 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/sonnen-sonnencharger.yaml b/templates/release/en/charger/sonnen-sonnencharger.yaml new file mode 100644 index 0000000000..3e9988e3e8 --- /dev/null +++ b/templates/release/en/charger/sonnen-sonnencharger.yaml @@ -0,0 +1,34 @@ +template: etrel +product: + identifier: sonnen-sonnencharger + brand: Sonnen + description: sonnenCharger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be switched to "Power" charging mode. +render: + - default: | + type: template + template: etrel + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml b/templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml new file mode 100644 index 0000000000..abc08a8588 --- /dev/null +++ b/templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: spelsberg-wallbox-smart-pro + brand: Spelsberg + description: Wallbox Smart Pro +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/stark-in-strom-easy.yaml b/templates/release/en/charger/stark-in-strom-easy.yaml new file mode 100644 index 0000000000..34909a8afe --- /dev/null +++ b/templates/release/en/charger/stark-in-strom-easy.yaml @@ -0,0 +1,41 @@ +template: evse-din +product: + identifier: stark-in-strom-easy + brand: Stark in Strom + description: Easy +render: + - default: | + type: template + template: evse-din + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml b/templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml new file mode 100644 index 0000000000..ee82bee39f --- /dev/null +++ b/templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml @@ -0,0 +1,42 @@ +template: stiebel-lwa +product: + identifier: stiebel-eltron-lwa-lwz-sg-ready + brand: Stiebel Eltron + description: LWA/LWZ (SG Ready) + group: Heating devices +render: + - default: | + type: template + template: stiebel-lwa + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperature source, [warmwater] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperature source + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml b/templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml new file mode 100644 index 0000000000..1f6a7d687e --- /dev/null +++ b/templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml @@ -0,0 +1,42 @@ +template: stiebel-wpm +product: + identifier: stiebel-eltron-wpm-sg-ready + brand: Stiebel Eltron + description: WPM (SG Ready) + group: Heating devices +render: + - default: | + type: template + template: stiebel-wpm + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperature source, [warmwater, buffer] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater', 'buffer'] + unit: + description: Temperature source + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/stiebel-lwa_0.yaml b/templates/release/en/charger/stiebel-lwa_0.yaml deleted file mode 100644 index 4e86a084b0..0000000000 --- a/templates/release/en/charger/stiebel-lwa_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Stiebel Eltron - description: LWA/LWZ (SG Ready) - group: Heating devices -render: - - default: | - type: template - template: stiebel-lwa - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperature source, [warmwater] (optional) diff --git a/templates/release/en/charger/stiebel-lwa_1.yaml b/templates/release/en/charger/stiebel-lwa_1.yaml deleted file mode 100644 index f8193b85d3..0000000000 --- a/templates/release/en/charger/stiebel-lwa_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Tecalor - description: THZ (SG Ready) - group: Heating devices -render: - - default: | - type: template - template: stiebel-lwa - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperature source, [warmwater] (optional) diff --git a/templates/release/en/charger/stiebel-wpm_0.yaml b/templates/release/en/charger/stiebel-wpm_0.yaml deleted file mode 100644 index fed9fa3350..0000000000 --- a/templates/release/en/charger/stiebel-wpm_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Stiebel Eltron - description: WPM (SG Ready) - group: Heating devices -render: - - default: | - type: template - template: stiebel-wpm - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - tempsource: # Temperature source, [warmwater, buffer] (optional) diff --git a/templates/release/en/charger/sungrow-ac011e-01.yaml b/templates/release/en/charger/sungrow-ac011e-01.yaml new file mode 100644 index 0000000000..5b3e3e81ce --- /dev/null +++ b/templates/release/en/charger/sungrow-ac011e-01.yaml @@ -0,0 +1,50 @@ +template: sungrow +product: + identifier: sungrow-ac011e-01 + brand: Sungrow + description: AC011E-01 +capabilities: ["mA", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: sungrow + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 248 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 248 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/sungrow-ac011e.yaml b/templates/release/en/charger/sungrow-ac011e.yaml new file mode 100644 index 0000000000..fdfd054a4d --- /dev/null +++ b/templates/release/en/charger/sungrow-ac011e.yaml @@ -0,0 +1,86 @@ +template: ocpp-sungrow +product: + identifier: sungrow-ac011e + brand: Sungrow + description: AC011E +capabilities: ["mA", "rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-sungrow + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-sungrow + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/sungrow-ac22e-01.yaml b/templates/release/en/charger/sungrow-ac22e-01.yaml new file mode 100644 index 0000000000..64254227f2 --- /dev/null +++ b/templates/release/en/charger/sungrow-ac22e-01.yaml @@ -0,0 +1,50 @@ +template: sungrow +product: + identifier: sungrow-ac22e-01 + brand: Sungrow + description: AC22E-01 +capabilities: ["mA", "1p3p"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: sungrow + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 248 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 248 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 248 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/sungrow_0.yaml b/templates/release/en/charger/sungrow_0.yaml deleted file mode 100644 index 84322afc67..0000000000 --- a/templates/release/en/charger/sungrow_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Sungrow - description: AC011E-01 -capabilities: ["mA", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: sungrow - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 248 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/sungrow_1.yaml b/templates/release/en/charger/sungrow_1.yaml deleted file mode 100644 index 13687bf675..0000000000 --- a/templates/release/en/charger/sungrow_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Sungrow - description: AC22E-01 -capabilities: ["mA", "1p3p"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: sungrow - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 248 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 248 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/tapo_0.yaml b/templates/release/en/charger/tapo_0.yaml deleted file mode 100644 index 5b40e65ca8..0000000000 --- a/templates/release/en/charger/tapo_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: TP-Link - description: Tapo P-Series Smart Plug - group: Switchable sockets -render: - - default: | - type: template - template: tapo - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: tapo - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/tasmota-single-phase.yaml b/templates/release/en/charger/tasmota-single-phase.yaml new file mode 100644 index 0000000000..daf5faba09 --- /dev/null +++ b/templates/release/en/charger/tasmota-single-phase.yaml @@ -0,0 +1,99 @@ +template: tasmota +product: + identifier: tasmota-single-phase + brand: Tasmota + description: single phase + group: Switchable sockets +render: + - default: | + type: template + template: tasmota + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 1 # Relaychannel number, Relaychannel number (1-8) + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: tasmota + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 1 # Relaychannel number, Relaychannel number (1-8) + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: admin is default + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 1 + choice: [] + unit: + description: Relaychannel number + help: Relaychannel number (1-8) + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/tasmota_0.yaml b/templates/release/en/charger/tasmota_0.yaml deleted file mode 100644 index a3526d90bb..0000000000 --- a/templates/release/en/charger/tasmota_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: Tasmota - description: single phase - group: Switchable sockets -render: - - default: | - type: template - template: tasmota - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 1 # Relaychannel number, Relaychannel number (1-8) - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: tasmota - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 1 # Relaychannel number, Relaychannel number (1-8) - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/tecalor-thz-sg-ready.yaml b/templates/release/en/charger/tecalor-thz-sg-ready.yaml new file mode 100644 index 0000000000..511f40d926 --- /dev/null +++ b/templates/release/en/charger/tecalor-thz-sg-ready.yaml @@ -0,0 +1,42 @@ +template: stiebel-lwa +product: + identifier: tecalor-thz-sg-ready + brand: Tecalor + description: THZ (SG Ready) + group: Heating devices +render: + - default: | + type: template + template: stiebel-lwa + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + tempsource: # Temperature source, [warmwater] (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: tempsource + example: + default: + choice: ['warmwater'] + unit: + description: Temperature source + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/technisat-technivolt.yaml b/templates/release/en/charger/technisat-technivolt.yaml new file mode 100644 index 0000000000..a9a31fa574 --- /dev/null +++ b/templates/release/en/charger/technisat-technivolt.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: technisat-technivolt + brand: TechniSat + description: Technivolt +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/tesla-wall-connector-gen-3.yaml b/templates/release/en/charger/tesla-wall-connector-gen-3.yaml new file mode 100644 index 0000000000..807a61245d --- /dev/null +++ b/templates/release/en/charger/tesla-wall-connector-gen-3.yaml @@ -0,0 +1,22 @@ +template: twc3 +product: + identifier: tesla-wall-connector-gen-3 + brand: Tesla + description: Wall Connector (Gen 3) +description: | + The TWC wallbox cannot be controlled directly. Control is via the vehicle. The vehicle must be selected at the TWC3 loadpoint. At this time only [Tesla vehicles](https://docs.evcc.io/en/docs/devices/vehicles#tesla) are supported. +render: + - default: | + type: template + template: twc3 + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/tessie.yaml b/templates/release/en/charger/tessie.yaml new file mode 100644 index 0000000000..136d61a5cb --- /dev/null +++ b/templates/release/en/charger/tessie.yaml @@ -0,0 +1,41 @@ +template: tessie +product: + identifier: tessie + description: Tessie +description: | + Charger connected via the Tessie API. Allows control of charging state and configuration of maximum current. +render: + - default: | + type: template + template: tessie + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + token: # Tessie API Token + location: tessiehome # Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) +params: + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Tessie API Token + help: + advanced: false + optional: false + - name: location + example: tessiehome + default: + choice: [] + unit: + description: Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/tessie_0.yaml b/templates/release/en/charger/tessie_0.yaml deleted file mode 100644 index d2cb6b952a..0000000000 --- a/templates/release/en/charger/tessie_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - description: Tessie -description: | - Charger connected via the Tessie API. Allows control of charging state and configuration of maximum current. -render: - - default: | - type: template - template: tessie - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - token: # Tessie API Token - location: tessiehome # Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) diff --git a/templates/release/en/charger/tigo-go-ev-charger.yaml b/templates/release/en/charger/tigo-go-ev-charger.yaml new file mode 100644 index 0000000000..c1f1f2d9c4 --- /dev/null +++ b/templates/release/en/charger/tigo-go-ev-charger.yaml @@ -0,0 +1,45 @@ +template: solax +product: + identifier: tigo-go-ev-charger + brand: Tigo + description: GO EV Charger +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + The charger must be in “Fast” mode and decoupled from the inverter system. +render: + - default: | + type: template + template: solax + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 70 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 70 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 70 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/tinkerforge-warp-charger-pro.yaml b/templates/release/en/charger/tinkerforge-warp-charger-pro.yaml new file mode 100644 index 0000000000..b915054b81 --- /dev/null +++ b/templates/release/en/charger/tinkerforge-warp-charger-pro.yaml @@ -0,0 +1,92 @@ +template: tinkerforge-warp +product: + identifier: tinkerforge-warp-charger-pro + brand: TinkerForge + description: WARP Charger Pro +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +description: | + WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. +render: + - default: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + advanced: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: IP address or hostname of the MQTT broker + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT broker port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (omit leading /) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Timeout + help: Don't accept values older than this value + advanced: false + optional: true + - name: energymanager + example: + default: + choice: [] + unit: + description: + help: WEM Firmware v2 required. EnergyManager MQTT topic (if installed) + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/tinkerforge-warp-charger-smart.yaml b/templates/release/en/charger/tinkerforge-warp-charger-smart.yaml new file mode 100644 index 0000000000..b61bb6c102 --- /dev/null +++ b/templates/release/en/charger/tinkerforge-warp-charger-smart.yaml @@ -0,0 +1,92 @@ +template: tinkerforge-warp +product: + identifier: tinkerforge-warp-charger-smart + brand: TinkerForge + description: WARP Charger Smart +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +description: | + WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. +render: + - default: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + advanced: | + type: template + template: tinkerforge-warp + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: IP address or hostname of the MQTT broker + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT broker port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (omit leading /) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Timeout + help: Don't accept values older than this value + advanced: false + optional: true + - name: energymanager + example: + default: + choice: [] + unit: + description: + help: WEM Firmware v2 required. EnergyManager MQTT topic (if installed) + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/tinkerforge-warp3-charger-pro.yaml b/templates/release/en/charger/tinkerforge-warp3-charger-pro.yaml new file mode 100644 index 0000000000..a05145462a --- /dev/null +++ b/templates/release/en/charger/tinkerforge-warp3-charger-pro.yaml @@ -0,0 +1,81 @@ +template: tinkerforge-warp3 +product: + identifier: tinkerforge-warp3-charger-pro + brand: TinkerForge + description: WARP3 Charger Pro +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +description: | + The automatic phase switching for 1p vehicles must be deactivated. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. +render: + - default: | + type: template + template: tinkerforge-warp3 + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + advanced: | + type: template + template: tinkerforge-warp3 + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: IP address or hostname of the MQTT broker + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT broker port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (omit leading /) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Timeout + help: Don't accept values older than this value + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/tinkerforge-warp3-charger-smart.yaml b/templates/release/en/charger/tinkerforge-warp3-charger-smart.yaml new file mode 100644 index 0000000000..4703dafd31 --- /dev/null +++ b/templates/release/en/charger/tinkerforge-warp3-charger-smart.yaml @@ -0,0 +1,79 @@ +template: tinkerforge-warp3-smart +product: + identifier: tinkerforge-warp3-charger-smart + brand: TinkerForge + description: WARP3 Charger Smart +capabilities: ["mA", "1p3p", "rfid"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: tinkerforge-warp3-smart + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + advanced: | + type: template + template: tinkerforge-warp3-smart + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: warp # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: IP address or hostname of the MQTT broker + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT broker port + advanced: false + optional: true + - name: topic + example: + default: warp + choice: [] + unit: + description: Topic + help: Topic (omit leading /) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Timeout + help: Don't accept values older than this value + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/tinkerforge-warp3-smart_0.yaml b/templates/release/en/charger/tinkerforge-warp3-smart_0.yaml deleted file mode 100644 index 368aaab1d8..0000000000 --- a/templates/release/en/charger/tinkerforge-warp3-smart_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: TinkerForge - description: WARP3 Charger Smart -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: tinkerforge-warp3-smart - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - advanced: | - type: template - template: tinkerforge-warp3-smart - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/tinkerforge-warp3_0.yaml b/templates/release/en/charger/tinkerforge-warp3_0.yaml deleted file mode 100644 index 4ff2ba96c7..0000000000 --- a/templates/release/en/charger/tinkerforge-warp3_0.yaml +++ /dev/null @@ -1,24 +0,0 @@ -product: - brand: TinkerForge - description: WARP3 Charger Pro -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -description: | - The automatic phase switching for 1p vehicles must be deactivated. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. -render: - - default: | - type: template - template: tinkerforge-warp3 - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - advanced: | - type: template - template: tinkerforge-warp3 - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/tinkerforge-warp_0.yaml b/templates/release/en/charger/tinkerforge-warp_0.yaml deleted file mode 100644 index 72d17458a9..0000000000 --- a/templates/release/en/charger/tinkerforge-warp_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: TinkerForge - description: WARP Charger Smart -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -description: | - WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. -render: - - default: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) - advanced: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/tinkerforge-warp_1.yaml b/templates/release/en/charger/tinkerforge-warp_1.yaml deleted file mode 100644 index b1809f339c..0000000000 --- a/templates/release/en/charger/tinkerforge-warp_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: TinkerForge - description: WARP Charger Pro -capabilities: ["mA", "1p3p", "rfid"] -requirements: ["skiptest"] -description: | - WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. -render: - - default: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) - advanced: | - type: template - template: tinkerforge-warp - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: warp # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/tp-link-h-series-smart-plug.yaml b/templates/release/en/charger/tp-link-h-series-smart-plug.yaml new file mode 100644 index 0000000000..210a80b2da --- /dev/null +++ b/templates/release/en/charger/tp-link-h-series-smart-plug.yaml @@ -0,0 +1,66 @@ +template: tplink +product: + identifier: tp-link-h-series-smart-plug + brand: TP-Link + description: H-Series Smart Plug + group: Switchable sockets +render: + - default: | + type: template + template: tplink + host: 192.0.2.2 # IP address or hostname + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: tplink + host: 192.0.2.2 # IP address or hostname + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/tp-link-tapo-p-series-smart-plug.yaml b/templates/release/en/charger/tp-link-tapo-p-series-smart-plug.yaml new file mode 100644 index 0000000000..e0626f612e --- /dev/null +++ b/templates/release/en/charger/tp-link-tapo-p-series-smart-plug.yaml @@ -0,0 +1,88 @@ +template: tapo +product: + identifier: tp-link-tapo-p-series-smart-plug + brand: TP-Link + description: Tapo P-Series Smart Plug + group: Switchable sockets +render: + - default: | + type: template + template: tapo + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + advanced: | + type: template + template: tapo + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) + integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) + heating: # Heating device, Shows °C instead of % (optional) + icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: standbypower + example: + default: 15 + choice: [] + unit: W + description: Standby power + help: Power values above this value will be considered as charging power + advanced: false + optional: true + - name: integrateddevice + example: + default: + choice: [] + unit: + description: Integrated device + help: Integrated device. No charging sessions + advanced: true + optional: true + - name: heating + example: + default: + choice: [] + unit: + description: Heating device + help: Shows °C instead of % + advanced: true + optional: true + - name: icon + example: + default: + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/tplink_0.yaml b/templates/release/en/charger/tplink_0.yaml deleted file mode 100644 index 97097a9d05..0000000000 --- a/templates/release/en/charger/tplink_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: TP-Link - description: H-Series Smart Plug - group: Switchable sockets -render: - - default: | - type: template - template: tplink - host: 192.0.2.2 # IP address or hostname - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - advanced: | - type: template - template: tplink - host: 192.0.2.2 # IP address or hostname - standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) - heating: # Heating device, Shows °C instead of % (optional) - icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) diff --git a/templates/release/en/charger/trydan_0.yaml b/templates/release/en/charger/trydan_0.yaml deleted file mode 100644 index 1518c57a4f..0000000000 --- a/templates/release/en/charger/trydan_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: V2C Trydan -requirements: ["sponsorship"] -description: | - V2C trydan -render: - - default: | - type: template - template: trydan - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/twc3_0.yaml b/templates/release/en/charger/twc3_0.yaml deleted file mode 100644 index f7ad76713f..0000000000 --- a/templates/release/en/charger/twc3_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Tesla - description: Wall Connector (Gen 3) -description: | - The TWC wallbox cannot be controlled directly. Control is via the vehicle. The vehicle must be selected at the TWC3 loadpoint. At this time only [Tesla vehicles](https://docs.evcc.io/en/docs/devices/vehicles#tesla) are supported. -render: - - default: | - type: template - template: twc3 - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/ubitricity-heinz.yaml b/templates/release/en/charger/ubitricity-heinz.yaml new file mode 100644 index 0000000000..90db352a18 --- /dev/null +++ b/templates/release/en/charger/ubitricity-heinz.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: ubitricity-heinz + brand: Ubitricity + description: Heinz +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/v2c-trydan.yaml b/templates/release/en/charger/v2c-trydan.yaml new file mode 100644 index 0000000000..2c58969810 --- /dev/null +++ b/templates/release/en/charger/v2c-trydan.yaml @@ -0,0 +1,22 @@ +template: trydan +product: + identifier: v2c-trydan + brand: V2C Trydan +requirements: ["sponsorship"] +description: | + V2C trydan +render: + - default: | + type: template + template: trydan + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/vaillant-sensonet-sg-ready.yaml b/templates/release/en/charger/vaillant-sensonet-sg-ready.yaml new file mode 100644 index 0000000000..833f97a34d --- /dev/null +++ b/templates/release/en/charger/vaillant-sensonet-sg-ready.yaml @@ -0,0 +1,63 @@ +template: vaillant +product: + identifier: vaillant-sensonet-sg-ready + brand: Vaillant + description: SensoNET (SG Ready) + group: Heating devices +description: | + The boost function heats hot water or a boost zone. The boost zone is identified by the ID. The boost temperature is specified in degrees Celsius. If boost temperature is specified, the boost zone is activated, otherwise hot water. +render: + - default: | + type: template + template: vaillant + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + realm: DE # [DE, AT] (optional) + zone: # Boost zone id (optional) + setpoint: # Boost temperature setpoint (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: realm + example: + default: DE + choice: ['DE', 'AT'] + unit: + description: + help: + advanced: false + optional: true + - name: zone + example: + default: + choice: [] + unit: + description: + help: Boost zone id + advanced: false + optional: true + - name: setpoint + example: + default: + choice: [] + unit: + description: + help: Boost temperature setpoint + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/vaillant_0.yaml b/templates/release/en/charger/vaillant_0.yaml deleted file mode 100644 index 40e7150b18..0000000000 --- a/templates/release/en/charger/vaillant_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Vaillant - description: SensoNET (SG Ready) - group: Heating devices -description: | - The boost function heats hot water or a boost zone. The boost zone is identified by the ID. The boost temperature is specified in degrees Celsius. If boost temperature is specified, the boost zone is activated, otherwise hot water. -render: - - default: | - type: template - template: vaillant - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - realm: DE # [DE, AT] (optional) - zone: # Boost zone id (optional) - setpoint: # Boost temperature setpoint (optional) diff --git a/templates/release/en/charger/versicharge_0.yaml b/templates/release/en/charger/versicharge_0.yaml deleted file mode 100644 index 348a24a052..0000000000 --- a/templates/release/en/charger/versicharge_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Siemens - description: Versicharge GEN3 -requirements: ["sponsorship"] -description: | - Requires firmware >= 2.135 -render: - - default: | - type: template - template: versicharge - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/vestel-connect-plus.yaml b/templates/release/en/charger/vestel-connect-plus.yaml new file mode 100644 index 0000000000..be8156c353 --- /dev/null +++ b/templates/release/en/charger/vestel-connect-plus.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: vestel-connect-plus + brand: Vestel + description: Connect Plus +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/vestel-evc04-home-smart.yaml b/templates/release/en/charger/vestel-evc04-home-smart.yaml new file mode 100644 index 0000000000..760817a31e --- /dev/null +++ b/templates/release/en/charger/vestel-evc04-home-smart.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: vestel-evc04-home-smart + brand: Vestel + description: EVC04 Home Smart +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/vestel_0.yaml b/templates/release/en/charger/vestel_0.yaml deleted file mode 100644 index 710dda58f6..0000000000 --- a/templates/release/en/charger/vestel_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Ampure - description: Unite -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/vestel_1.yaml b/templates/release/en/charger/vestel_1.yaml deleted file mode 100644 index bd463fd75b..0000000000 --- a/templates/release/en/charger/vestel_1.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Vestel - description: EVC04 Home Smart -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/vestel_2.yaml b/templates/release/en/charger/vestel_2.yaml deleted file mode 100644 index 0d3b82ca83..0000000000 --- a/templates/release/en/charger/vestel_2.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Vestel - description: Connect Plus -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/vestel_3.yaml b/templates/release/en/charger/vestel_3.yaml deleted file mode 100644 index 0d31d81d33..0000000000 --- a/templates/release/en/charger/vestel_3.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Webasto - description: Unite -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/vestel_4.yaml b/templates/release/en/charger/vestel_4.yaml deleted file mode 100644 index d80fb51d9d..0000000000 --- a/templates/release/en/charger/vestel_4.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: E.ON Drive - description: vBox -capabilities: ["rfid", "1p3p"] -requirements: ["sponsorship"] -description: | - 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. -render: - - default: | - type: template - template: vestel - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/victron-ev-charging-station-via-gx.yaml b/templates/release/en/charger/victron-ev-charging-station-via-gx.yaml new file mode 100644 index 0000000000..eb034f66f4 --- /dev/null +++ b/templates/release/en/charger/victron-ev-charging-station-via-gx.yaml @@ -0,0 +1,33 @@ +template: victron +product: + identifier: victron-ev-charging-station-via-gx + brand: Victron + description: EV Charging Station (via GX) +description: | + Enter the host of the GX device (not the charger). The charger has to be in manual mode and Modbus has to be configured for ID 100. +render: + - default: | + type: template + template: victron + + # Modbus TCP + modbus: tcpip + id: 100 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 100 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/victron-ev-charging-station.yaml b/templates/release/en/charger/victron-ev-charging-station.yaml new file mode 100644 index 0000000000..ae75ee2247 --- /dev/null +++ b/templates/release/en/charger/victron-ev-charging-station.yaml @@ -0,0 +1,33 @@ +template: victron-evcs +product: + identifier: victron-ev-charging-station + brand: Victron + description: EV Charging Station +description: | + Enter the host of the charger (not the GX device) and ensure that the charger is in manual mode. +render: + - default: | + type: template + template: victron-evcs + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/victron-evcs_0.yaml b/templates/release/en/charger/victron-evcs_0.yaml deleted file mode 100644 index 2ec17a214f..0000000000 --- a/templates/release/en/charger/victron-evcs_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Victron - description: EV Charging Station -description: | - Enter the host of the charger (not the GX device) and ensure that the charger is in manual mode. -render: - - default: | - type: template - template: victron-evcs - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/victron_0.yaml b/templates/release/en/charger/victron_0.yaml deleted file mode 100644 index 7f7b7ea5b0..0000000000 --- a/templates/release/en/charger/victron_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Victron - description: EV Charging Station (via GX) -description: | - Enter the host of the GX device (not the charger). The charger has to be in manual mode and Modbus has to be configured for ID 100. -render: - - default: | - type: template - template: victron - - # Modbus TCP - modbus: tcpip - id: 100 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/charger/viessmann-heatpump-sg-ready.yaml b/templates/release/en/charger/viessmann-heatpump-sg-ready.yaml new file mode 100644 index 0000000000..b501aa35c7 --- /dev/null +++ b/templates/release/en/charger/viessmann-heatpump-sg-ready.yaml @@ -0,0 +1,85 @@ +template: viessmann +product: + identifier: viessmann-heatpump-sg-ready + brand: Viessmann + description: Heatpump (SG Ready) + group: Heating devices +requirements: ["skiptest"] +description: | + One-time hot water preparation to a configurable target temperature. The device automatically decides whether to use the heat pump or the auxiliary electric heater (if available). + +render: + - default: | + type: template + template: viessmann + user: # Username, Register at [app.developer.viessmann.com](https://app.developer.viessmann.com) + password: # Password, For the configured Viessmann account. + clientid: # Client ID, Configure at [app.developer.viessmann.com](https://app.developer.viessmann.com) + gateway_serial: # Gateway Serial, VitoConnect serial number (VitoCare App -> Settings -> Communication module -> Serial number) + installation_id: # Installation ID, Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...
Prerequisites: curl, jq, and the following parameters: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Then execute the following to get an oauth token (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\?code=\(.*\).*/\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) ``` Finally, get the installation id: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' ``` + device_id: 0 # Device ID, typically `0` + target_temperature: 45 # Target temperature for one-time charge (°C), max. 60°C +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: Register at [app.developer.viessmann.com](https://app.developer.viessmann.com) + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: For the configured Viessmann account. + advanced: false + optional: false + - name: clientid + example: + default: + choice: [] + unit: + description: Client ID + help: Configure at [app.developer.viessmann.com](https://app.developer.viessmann.com) + advanced: false + optional: false + - name: gateway_serial + example: + default: + choice: [] + unit: + description: Gateway Serial + help: VitoConnect serial number (VitoCare App -> Settings -> Communication module -> Serial number) + advanced: false + optional: false + - name: installation_id + example: + default: + choice: [] + unit: + description: Installation ID + help: 'Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we''re aware this is not for every user, but currently we don''t have a better workflow...
Prerequisites: curl, jq, and the following parameters: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Then execute the following to get an oauth token (n.b. it''s best to paste the entire block as-is, since the intermediate ''CODE'' is only valid for 20 seconds): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed ''s/.*\?code=\(.*\).*/\1/'' \ | tr -d ''[:space:]'') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) ``` Finally, get the installation id: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq ''.data[].id'' ```' + advanced: false + optional: false + - name: device_id + example: + default: 0 + choice: [] + unit: + description: Device ID + help: typically `0` + advanced: false + optional: false + - name: target_temperature + example: + default: 45 + choice: [] + unit: °C + description: Target temperature for one-time charge + help: max. 60°C + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/viessmann_0.yaml b/templates/release/en/charger/viessmann_0.yaml deleted file mode 100644 index d89be0f225..0000000000 --- a/templates/release/en/charger/viessmann_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Viessmann - description: Heatpump (SG Ready) - group: Heating devices -requirements: ["skiptest"] -description: | - One-time hot water preparation to a configurable target temperature. The device automatically decides whether to use the heat pump or the auxiliary electric heater (if available). - -render: - - default: | - type: template - template: viessmann - user: # Username, Register at [app.developer.viessmann.com](https://app.developer.viessmann.com) - password: # Password, For the configured Viessmann account. - clientid: # Client ID, Configure at [app.developer.viessmann.com](https://app.developer.viessmann.com) - gateway_serial: # Gateway Serial, VitoConnect serial number (VitoCare App -> Settings -> Communication module -> Serial number) - installation_id: # Installation ID, Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...
Prerequisites: curl, jq, and the following parameters: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Then execute the following to get an oauth token (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\?code=\(.*\).*/\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) ``` Finally, get the installation id: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' ``` - device_id: 0 # Device ID, typically `0` - target_temperature: 45 # Target temperature for one-time charge (°C), max. 60°C diff --git a/templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml b/templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml new file mode 100644 index 0000000000..53ecd1be96 --- /dev/null +++ b/templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml @@ -0,0 +1,48 @@ +template: obo +product: + identifier: viridian-ev-evse-epc-2-0-plus + brand: Viridian EV + description: EVSE EPC 2.0 Plus +render: + - default: | + type: template + template: obo + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 101 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 101 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 101 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/volkswagen-charger-connect-2.yaml b/templates/release/en/charger/volkswagen-charger-connect-2.yaml new file mode 100644 index 0000000000..816f5858e4 --- /dev/null +++ b/templates/release/en/charger/volkswagen-charger-connect-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: volkswagen-charger-connect-2 + brand: Volkswagen + description: Charger Connect 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/volkswagen-charger-pro-2.yaml b/templates/release/en/charger/volkswagen-charger-pro-2.yaml new file mode 100644 index 0000000000..c4b8c5ae97 --- /dev/null +++ b/templates/release/en/charger/volkswagen-charger-pro-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: volkswagen-charger-pro-2 + brand: Volkswagen + description: Charger Pro 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/volkswagen-charger-pro-eichrecht-2.yaml b/templates/release/en/charger/volkswagen-charger-pro-eichrecht-2.yaml new file mode 100644 index 0000000000..e4d74d159e --- /dev/null +++ b/templates/release/en/charger/volkswagen-charger-pro-eichrecht-2.yaml @@ -0,0 +1,39 @@ +template: elli-2 +product: + identifier: volkswagen-charger-pro-eichrecht-2 + brand: Volkswagen + description: Charger Pro Eichrecht 2 +capabilities: ["iso151182", "mA"] +requirements: ["eebus"] +description: | + The device has to be used in the normal charging mode. + + The usage of phase switching is currently not possible in evcc. + + The identification of a vehicle using the RFID card is not possible. + +render: + - default: | + type: template + template: elli-2 + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/volkswagen-id-charger-connect.yaml b/templates/release/en/charger/volkswagen-id-charger-connect.yaml new file mode 100644 index 0000000000..cb40c0ecc3 --- /dev/null +++ b/templates/release/en/charger/volkswagen-id-charger-connect.yaml @@ -0,0 +1,41 @@ +template: elliconnect +product: + identifier: volkswagen-id-charger-connect + brand: Volkswagen + description: ID. Charger Connect +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + + Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration. + +render: + - default: | + type: template + template: elliconnect + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/volkswagen-id-charger-pro.yaml b/templates/release/en/charger/volkswagen-id-charger-pro.yaml new file mode 100644 index 0000000000..2d31b64679 --- /dev/null +++ b/templates/release/en/charger/volkswagen-id-charger-pro.yaml @@ -0,0 +1,39 @@ +template: ellipro +product: + identifier: volkswagen-id-charger-pro + brand: Volkswagen + description: ID. Charger Pro +capabilities: ["mA"] +requirements: ["eebus"] +description: | + The device has to have a fix IP address (manuall or via DHCP). + + The identification of a vehicle using the RFID card is not possible. + + Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended. + +render: + - default: | + type: template + template: ellipro + ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox + ip: 192.0.2.2 # IP address, optional +params: + - name: ski + example: + default: + choice: [] + unit: + description: Subject Key Identifier (SKI) + help: Usually found on the web interface of the wallbox + advanced: false + optional: false + - name: ip + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/volt-time-one.yaml b/templates/release/en/charger/volt-time-one.yaml new file mode 100644 index 0000000000..8aecc3c621 --- /dev/null +++ b/templates/release/en/charger/volt-time-one.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-one + brand: Volt Time + description: One +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial number (e.g. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Serial number (e.g. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/volt-time-source-2.yaml b/templates/release/en/charger/volt-time-source-2.yaml new file mode 100644 index 0000000000..04f687ad64 --- /dev/null +++ b/templates/release/en/charger/volt-time-source-2.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-source-2 + brand: Volt Time + description: Source 2 +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial number (e.g. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Serial number (e.g. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/volt-time-source-2s.yaml b/templates/release/en/charger/volt-time-source-2s.yaml new file mode 100644 index 0000000000..61f89cfd7c --- /dev/null +++ b/templates/release/en/charger/volt-time-source-2s.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-source-2s + brand: Volt Time + description: Source 2s +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial number (e.g. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Serial number (e.g. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/volt-time-source.yaml b/templates/release/en/charger/volt-time-source.yaml new file mode 100644 index 0000000000..de310e8817 --- /dev/null +++ b/templates/release/en/charger/volt-time-source.yaml @@ -0,0 +1,31 @@ +template: volttime +product: + identifier: volt-time-source + brand: Volt Time + description: Source +requirements: ["sponsorship"] +render: + - default: | + type: template + template: volttime + token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial number (e.g. 1008621) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + advanced: false + optional: false + - name: serial_number + example: + default: + choice: [] + unit: + description: + help: Serial number (e.g. 1008621) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/charger/volttime_0.yaml b/templates/release/en/charger/volttime_0.yaml deleted file mode 100644 index b653c5d3bf..0000000000 --- a/templates/release/en/charger/volttime_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: Source -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) diff --git a/templates/release/en/charger/volttime_1.yaml b/templates/release/en/charger/volttime_1.yaml deleted file mode 100644 index b53f2b2cf0..0000000000 --- a/templates/release/en/charger/volttime_1.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: Source 2 -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) diff --git a/templates/release/en/charger/volttime_2.yaml b/templates/release/en/charger/volttime_2.yaml deleted file mode 100644 index 407a9e3893..0000000000 --- a/templates/release/en/charger/volttime_2.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: Source 2s -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) diff --git a/templates/release/en/charger/volttime_3.yaml b/templates/release/en/charger/volttime_3.yaml deleted file mode 100644 index cf4e8fe61b..0000000000 --- a/templates/release/en/charger/volttime_3.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Volt Time - description: One -requirements: ["sponsorship"] -render: - - default: | - type: template - template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) diff --git a/templates/release/en/charger/wallbe-eco-2-0-s.yaml b/templates/release/en/charger/wallbe-eco-2-0-s.yaml new file mode 100644 index 0000000000..8ffe2e48e5 --- /dev/null +++ b/templates/release/en/charger/wallbe-eco-2-0-s.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: wallbe-eco-2-0-s + brand: Wallbe + description: Eco 2.0(s) +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbe-eco.yaml b/templates/release/en/charger/wallbe-eco.yaml new file mode 100644 index 0000000000..61e02c6596 --- /dev/null +++ b/templates/release/en/charger/wallbe-eco.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: wallbe-eco + brand: Wallbe + description: Eco +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbe-pro.yaml b/templates/release/en/charger/wallbe-pro.yaml new file mode 100644 index 0000000000..d1eb089d38 --- /dev/null +++ b/templates/release/en/charger/wallbe-pro.yaml @@ -0,0 +1,35 @@ +template: phoenix-ev-eth +product: + identifier: wallbe-pro + brand: Wallbe + description: Pro +capabilities: ["mA", "rfid"] +requirements: ["sponsorship"] +description: | + DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. +render: + - default: | + type: template + template: phoenix-ev-eth + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml b/templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml new file mode 100644 index 0000000000..64b0edd567 --- /dev/null +++ b/templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-commander-2-fw-5-x + brand: wallbox + description: Commander 2 (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-commander-2.yaml b/templates/release/en/charger/wallbox-commander-2.yaml new file mode 100644 index 0000000000..c08f1d2efb --- /dev/null +++ b/templates/release/en/charger/wallbox-commander-2.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-commander-2 + brand: wallbox + description: Commander 2 +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml b/templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml new file mode 100644 index 0000000000..19ec95449a --- /dev/null +++ b/templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-copper-sb-fw-5-x + brand: wallbox + description: Copper SB (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-copper-sb.yaml b/templates/release/en/charger/wallbox-copper-sb.yaml new file mode 100644 index 0000000000..86add4d82e --- /dev/null +++ b/templates/release/en/charger/wallbox-copper-sb.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-copper-sb + brand: wallbox + description: Copper SB +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-fw5_0.yaml b/templates/release/en/charger/wallbox-fw5_0.yaml deleted file mode 100644 index d0e207fcad..0000000000 --- a/templates/release/en/charger/wallbox-fw5_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Plus (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/wallbox-fw5_1.yaml b/templates/release/en/charger/wallbox-fw5_1.yaml deleted file mode 100644 index 66520f7a1e..0000000000 --- a/templates/release/en/charger/wallbox-fw5_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Pulsar Max (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/wallbox-fw5_2.yaml b/templates/release/en/charger/wallbox-fw5_2.yaml deleted file mode 100644 index a71b771c86..0000000000 --- a/templates/release/en/charger/wallbox-fw5_2.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Commander 2 (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/wallbox-fw5_3.yaml b/templates/release/en/charger/wallbox-fw5_3.yaml deleted file mode 100644 index ca05a8dfd9..0000000000 --- a/templates/release/en/charger/wallbox-fw5_3.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: wallbox - description: Copper SB (FW 5.x) -requirements: ["sponsorship", "skiptest"] -description: | - Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ - - * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) - * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) - * URL: ws://[evcc-adresse]:8887/ (local network connection) - * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* - * Password: leave empty - -render: - - default: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - advanced: | - type: template - template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional diff --git a/templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml b/templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml new file mode 100644 index 0000000000..ebcb93e080 --- /dev/null +++ b/templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-pulsar-max-fw-5-x + brand: wallbox + description: Pulsar Max (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-pulsar-max.yaml b/templates/release/en/charger/wallbox-pulsar-max.yaml new file mode 100644 index 0000000000..15ca5c98f4 --- /dev/null +++ b/templates/release/en/charger/wallbox-pulsar-max.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-pulsar-max + brand: wallbox + description: Pulsar Max +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml b/templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml new file mode 100644 index 0000000000..00f8478604 --- /dev/null +++ b/templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml @@ -0,0 +1,94 @@ +template: wallbox-fw5 +product: + identifier: wallbox-pulsar-plus-fw-5-x + brand: wallbox + description: Pulsar Plus (FW 5.x) +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: wallbox-fw5 + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: -Current.Offered,Power.Offered + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-pulsar-plus.yaml b/templates/release/en/charger/wallbox-pulsar-plus.yaml new file mode 100644 index 0000000000..cf8d4ec7b8 --- /dev/null +++ b/templates/release/en/charger/wallbox-pulsar-plus.yaml @@ -0,0 +1,94 @@ +template: ocpp-wallbox +product: + identifier: wallbox-pulsar-plus + brand: wallbox + description: Pulsar Plus +requirements: ["sponsorship", "skiptest"] +description: | + Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ + + * Switch on “Enable OCPP” (myWallbox app) or enable the “OCPP WebSocket connection” switch (myWallbox Portal) + * Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app) + * URL: ws://[evcc-adresse]:8887/ (local network connection) + * Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as *stationid* + * Password: leave empty + +render: + - default: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-wallbox + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/walther-werke-basic-evo-pro.yaml b/templates/release/en/charger/walther-werke-basic-evo-pro.yaml new file mode 100644 index 0000000000..8ffbf630b9 --- /dev/null +++ b/templates/release/en/charger/walther-werke-basic-evo-pro.yaml @@ -0,0 +1,45 @@ +template: heidelberg +product: + identifier: walther-werke-basic-evo-pro + brand: Walther Werke + description: Basic Evo Pro +capabilities: ["mA"] +requirements: ["sponsorship"] +description: | + Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). +render: + - default: | + type: template + template: heidelberg + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 19200 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/webasto-live.yaml b/templates/release/en/charger/webasto-live.yaml new file mode 100644 index 0000000000..e52353bc38 --- /dev/null +++ b/templates/release/en/charger/webasto-live.yaml @@ -0,0 +1,35 @@ +template: bender-cc +product: + identifier: webasto-live + brand: Webasto + description: Live +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. +render: + - default: | + type: template + template: bender-cc + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/webasto-next.yaml b/templates/release/en/charger/webasto-next.yaml new file mode 100644 index 0000000000..96cc913a36 --- /dev/null +++ b/templates/release/en/charger/webasto-next.yaml @@ -0,0 +1,34 @@ +template: webasto-next +product: + identifier: webasto-next + brand: Webasto + description: NEXT +capabilities: ["rfid"] +requirements: ["sponsorship"] +description: | + Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. +render: + - default: | + type: template + template: webasto-next + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/webasto-next_0.yaml b/templates/release/en/charger/webasto-next_0.yaml deleted file mode 100644 index c4e8ea0023..0000000000 --- a/templates/release/en/charger/webasto-next_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Ampure - description: NEXT -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. -render: - - default: | - type: template - template: webasto-next - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional diff --git a/templates/release/en/charger/webasto-next_1.yaml b/templates/release/en/charger/webasto-next_1.yaml deleted file mode 100644 index c547964af8..0000000000 --- a/templates/release/en/charger/webasto-next_1.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Webasto - description: NEXT -capabilities: ["rfid"] -requirements: ["sponsorship"] -description: | - Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. -render: - - default: | - type: template - template: webasto-next - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional diff --git a/templates/release/en/charger/webasto-unite.yaml b/templates/release/en/charger/webasto-unite.yaml new file mode 100644 index 0000000000..7814e557be --- /dev/null +++ b/templates/release/en/charger/webasto-unite.yaml @@ -0,0 +1,35 @@ +template: vestel +product: + identifier: webasto-unite + brand: Webasto + description: Unite +capabilities: ["rfid", "1p3p"] +requirements: ["sponsorship"] +description: | + 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. +render: + - default: | + type: template + template: vestel + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 255 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/weidmuller-ac-smart.yaml b/templates/release/en/charger/weidmuller-ac-smart.yaml new file mode 100644 index 0000000000..208a9f860c --- /dev/null +++ b/templates/release/en/charger/weidmuller-ac-smart.yaml @@ -0,0 +1,22 @@ +template: weidmüller +product: + identifier: weidmuller-ac-smart + brand: Weidmüller + description: AC Smart +capabilities: ["1p3p", "rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: weidmüller + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git "a/templates/release/en/charger/weidm\303\274ller_0.yaml" "b/templates/release/en/charger/weidm\303\274ller_0.yaml" deleted file mode 100644 index 086e4ad63e..0000000000 --- "a/templates/release/en/charger/weidm\303\274ller_0.yaml" +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Weidmüller - description: AC Smart -capabilities: ["1p3p", "rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: weidmüller - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/charger/wolf-bwl.yaml b/templates/release/en/charger/wolf-bwl.yaml new file mode 100644 index 0000000000..e83fb23818 --- /dev/null +++ b/templates/release/en/charger/wolf-bwl.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: wolf-bwl + brand: Wolf + description: BWL + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/wolf-bws.yaml b/templates/release/en/charger/wolf-bws.yaml new file mode 100644 index 0000000000..221c1a7d08 --- /dev/null +++ b/templates/release/en/charger/wolf-bws.yaml @@ -0,0 +1,64 @@ +template: luxtronik +product: + identifier: wolf-bws + brand: Wolf + description: BWS + group: Heating devices +description: | + For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. +render: + - default: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + heatoffset: 0.0 # Temperature boost offset for heating. (optional) + wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for heating. + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: + help: Temperature boost offset for hot water. Possibly increases wear on compressor. + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/charger/zaptec-go-2.yaml b/templates/release/en/charger/zaptec-go-2.yaml new file mode 100644 index 0000000000..850df29718 --- /dev/null +++ b/templates/release/en/charger/zaptec-go-2.yaml @@ -0,0 +1,42 @@ +template: zaptec +product: + identifier: zaptec-go-2 + brand: Zaptec + description: Go 2 +capabilities: ["rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: zaptec + id: # Charger ID (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: id + example: + default: + choice: [] + unit: + description: + help: Charger ID + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/zaptec-go-ocpp.yaml b/templates/release/en/charger/zaptec-go-ocpp.yaml new file mode 100644 index 0000000000..ca2c300b30 --- /dev/null +++ b/templates/release/en/charger/zaptec-go-ocpp.yaml @@ -0,0 +1,91 @@ +template: ocpp-zaptec +product: + identifier: zaptec-go-ocpp + brand: Zaptec + description: Go (OCPP) +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +description: | + OCPP Native mode + + https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ + +render: + - default: | + type: template + template: ocpp-zaptec + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-zaptec + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/zaptec-go.yaml b/templates/release/en/charger/zaptec-go.yaml new file mode 100644 index 0000000000..e5681a3d88 --- /dev/null +++ b/templates/release/en/charger/zaptec-go.yaml @@ -0,0 +1,42 @@ +template: zaptec +product: + identifier: zaptec-go + brand: Zaptec + description: Go +capabilities: ["rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: zaptec + id: # Charger ID (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: id + example: + default: + choice: [] + unit: + description: + help: Charger ID + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/zaptec-pro.yaml b/templates/release/en/charger/zaptec-pro.yaml new file mode 100644 index 0000000000..c17b01a024 --- /dev/null +++ b/templates/release/en/charger/zaptec-pro.yaml @@ -0,0 +1,42 @@ +template: zaptec +product: + identifier: zaptec-pro + brand: Zaptec + description: Pro +capabilities: ["rfid"] +requirements: ["sponsorship"] +render: + - default: | + type: template + template: zaptec + id: # Charger ID (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: id + example: + default: + choice: [] + unit: + description: + help: Charger ID + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/zaptec_0.yaml b/templates/release/en/charger/zaptec_0.yaml deleted file mode 100644 index 6051509256..0000000000 --- a/templates/release/en/charger/zaptec_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zaptec - description: Go -capabilities: ["rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: zaptec - id: # Charger ID (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/zaptec_1.yaml b/templates/release/en/charger/zaptec_1.yaml deleted file mode 100644 index a53e2bdea2..0000000000 --- a/templates/release/en/charger/zaptec_1.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zaptec - description: Go 2 -capabilities: ["rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: zaptec - id: # Charger ID (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/zaptec_2.yaml b/templates/release/en/charger/zaptec_2.yaml deleted file mode 100644 index 89ad730089..0000000000 --- a/templates/release/en/charger/zaptec_2.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zaptec - description: Pro -capabilities: ["rfid"] -requirements: ["sponsorship"] -render: - - default: | - type: template - template: zaptec - id: # Charger ID (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/charger/zewotherm-eu-l-series.yaml b/templates/release/en/charger/zewotherm-eu-l-series.yaml new file mode 100644 index 0000000000..5d8b273aef --- /dev/null +++ b/templates/release/en/charger/zewotherm-eu-l-series.yaml @@ -0,0 +1,52 @@ +template: lambda-zewotherm +product: + identifier: zewotherm-eu-l-series + brand: Zewotherm + description: EU-L Series + group: Heating devices +description: | + Energy management settings of the device: + + - E-Meter communication type: "ModBus Client" + - E-Meter measuring point: "Pos. E-Überschuss" + +render: + - default: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + advanced: | + type: template + template: lambda-zewotherm + host: 192.0.2.2 # IP address or hostname + tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) + watchdog: 60s # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: tempsource + example: + default: + choice: ['warmwater_top', 'warmwater_bottom', 'buffer_top', 'buffer_bottom'] + unit: + description: Temperature source + help: + advanced: false + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/charger/zj-beny-bcp-ev-charger.yaml b/templates/release/en/charger/zj-beny-bcp-ev-charger.yaml new file mode 100644 index 0000000000..d36a5375db --- /dev/null +++ b/templates/release/en/charger/zj-beny-bcp-ev-charger.yaml @@ -0,0 +1,86 @@ +template: ocpp-beny +product: + identifier: zj-beny-bcp-ev-charger + brand: ZJ Beny + description: BCP EV charger +capabilities: ["rfid"] +requirements: ["sponsorship", "skiptest"] +render: + - default: | + type: template + template: ocpp-beny + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + advanced: | + type: template + template: ocpp-beny + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) + remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) + idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) + connecttimeout: 5m # Timeout for the registration of the charging point, optional + meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional +params: + - name: stationid + example: EVB-P12354 + default: + choice: [] + unit: + description: Station ID + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + advanced: false + optional: true + - name: connector + example: + default: 1 + choice: [] + unit: + description: Connector number + help: For charging stations with multiple connectors. Counting starts at 1 for the first connector. + advanced: true + optional: true + - name: remotestart + example: + default: + choice: [] + unit: + description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + advanced: true + optional: true + - name: idtag + example: evcc + default: + choice: [] + unit: + description: Identifier used for authentication of external transactions (RemoteStartTransaction) + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + advanced: true + optional: true + - name: connecttimeout + example: + default: 5m + choice: [] + unit: + description: Timeout for the registration of the charging point + help: + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval of meter values (MeterValueSampleInterval) + help: + advanced: true + optional: true + - name: metervalues + example: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage + default: + choice: [] + unit: + description: Manual specification of the meter values to be configured (MeterValuesSampledData) + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/a-tronix.yaml b/templates/release/en/meter/a-tronix.yaml new file mode 100644 index 0000000000..1e00b96fce --- /dev/null +++ b/templates/release/en/meter/a-tronix.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: a-tronix + brand: A-Tronix +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/abb-a43.yaml b/templates/release/en/meter/abb-a43.yaml new file mode 100644 index 0000000000..b8f9cde212 --- /dev/null +++ b/templates/release/en/meter/abb-a43.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-a43 + brand: ABB + description: A43 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/abb-a44.yaml b/templates/release/en/meter/abb-a44.yaml new file mode 100644 index 0000000000..73a54d0f01 --- /dev/null +++ b/templates/release/en/meter/abb-a44.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-a44 + brand: ABB + description: A44 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/abb-ab_0.yaml b/templates/release/en/meter/abb-ab_0.yaml deleted file mode 100644 index 8555cd10ce..0000000000 --- a/templates/release/en/meter/abb-ab_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: ABB - description: A43, A44, B23, B24 -render: - - usage: grid - default: | - type: template - template: abb-ab - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: abb-ab - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/abb-b23.yaml b/templates/release/en/meter/abb-b23.yaml new file mode 100644 index 0000000000..064db6b31f --- /dev/null +++ b/templates/release/en/meter/abb-b23.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-b23 + brand: ABB + description: B23 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/abb-b24.yaml b/templates/release/en/meter/abb-b24.yaml new file mode 100644 index 0000000000..b82fd16671 --- /dev/null +++ b/templates/release/en/meter/abb-b24.yaml @@ -0,0 +1,61 @@ +template: abb-ab +product: + identifier: abb-b24 + brand: ABB + description: B24 +render: + - usage: grid + default: | + type: template + template: abb-ab + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: abb-ab + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/ac-elwa-2_0.yaml b/templates/release/en/meter/ac-elwa-2_0.yaml deleted file mode 100644 index 8b79787bc0..0000000000 --- a/templates/release/en/meter/ac-elwa-2_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: my-PV - description: AC ELWA 2 -render: - - usage: aux - default: | - type: template - template: ac-elwa-2 - usage: aux - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/ac-elwa-e_0.yaml b/templates/release/en/meter/ac-elwa-e_0.yaml deleted file mode 100644 index b876a4a357..0000000000 --- a/templates/release/en/meter/ac-elwa-e_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: my-PV - description: AC ELWA-E -render: - - usage: aux - default: | - type: template - template: ac-elwa-e - usage: aux - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/acrel-adw300.yaml b/templates/release/en/meter/acrel-adw300.yaml new file mode 100644 index 0000000000..ed0f7ea506 --- /dev/null +++ b/templates/release/en/meter/acrel-adw300.yaml @@ -0,0 +1,98 @@ +template: acrel-adw300 +product: + identifier: acrel-adw300 + brand: Acrel + description: ADW300 +render: + - usage: grid + default: | + type: template + template: acrel-adw300 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: acrel-adw300 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: acrel-adw300 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 1200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/acrel-adw300_0.yaml b/templates/release/en/meter/acrel-adw300_0.yaml deleted file mode 100644 index 158d7b0051..0000000000 --- a/templates/release/en/meter/acrel-adw300_0.yaml +++ /dev/null @@ -1,76 +0,0 @@ -product: - brand: Acrel - description: ADW300 Wireless Metering Meter -render: - - usage: grid - default: | - type: template - template: acrel-adw300 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: acrel-adw300 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: acrel-adw300 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/ads-tec-storaxe.yaml b/templates/release/en/meter/ads-tec-storaxe.yaml new file mode 100644 index 0000000000..f7afea8d69 --- /dev/null +++ b/templates/release/en/meter/ads-tec-storaxe.yaml @@ -0,0 +1,53 @@ +template: storaxe +product: + identifier: ads-tec-storaxe + brand: Ads-tec + description: StoraXe +render: + - usage: battery + default: | + type: template + template: storaxe + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: storaxe + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/alpha-ess-smile_0.yaml b/templates/release/en/meter/alpha-ess-smile_0.yaml deleted file mode 100644 index 2d290b8d12..0000000000 --- a/templates/release/en/meter/alpha-ess-smile_0.yaml +++ /dev/null @@ -1,157 +0,0 @@ -product: - brand: Alpha ESS - description: Storion SMILE -capabilities: ["battery-control"] -description: | - To use active battery control, times for grid charging must be defined once via the web interface or app. (Settings->Function settings->Grid charging/discharging) A continuous time period should be entered here (e.g.: Charging time 1 00:00-23:00, Charging time 2 23:00-00:00). However, deactivate the "Grid charging" switch. The actual control takes place via evcc. Discharge stop is realized via a scheduled grid charge with a target SoC of 10%. Alternatively, it can also be configured via Modbus. To do this, set the registers `2134,2142,2135,2136,2144,2137,2175` to the values `0,0,23,0,23,0,0,0,0`. - -render: - - usage: grid - default: | - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: alpha-ess-smile - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: alpha-ess-smile - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: alpha-ess-smile - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: alpha-ess-smile - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/alpha-ess-storion-smile.yaml b/templates/release/en/meter/alpha-ess-storion-smile.yaml new file mode 100644 index 0000000000..f474beffca --- /dev/null +++ b/templates/release/en/meter/alpha-ess-storion-smile.yaml @@ -0,0 +1,215 @@ +template: alpha-ess-smile +product: + identifier: alpha-ess-storion-smile + brand: Alpha ESS + description: Storion SMILE +capabilities: ["battery-control"] +description: | + To use active battery control, times for grid charging must be defined once via the web interface or app. (Settings->Function settings->Grid charging/discharging) A continuous time period should be entered here (e.g.: Charging time 1 00:00-23:00, Charging time 2 23:00-00:00). However, deactivate the "Grid charging" switch. The actual control takes place via evcc. Discharge stop is realized via a scheduled grid charge with a target SoC of 10%. Alternatively, it can also be configured via Modbus. To do this, set the registers `2134,2142,2135,2136,2144,2137,2175` to the values `0,0,23,0,23,0,0,0,0`. + +render: + - usage: grid + default: | + type: template + template: alpha-ess-smile + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: alpha-ess-smile + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: alpha-ess-smile + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: alpha-ess-smile + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: alpha-ess-smile + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: alpha-ess-smile + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 85 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 85 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 85 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/ampere-ampere-storagepro.yaml b/templates/release/en/meter/ampere-ampere-storagepro.yaml new file mode 100644 index 0000000000..94721883fe --- /dev/null +++ b/templates/release/en/meter/ampere-ampere-storagepro.yaml @@ -0,0 +1,211 @@ +template: saj-h2 +product: + identifier: ampere-ampere-storagepro + brand: Ampere + description: Ampere.StoragePro +render: + - usage: grid + default: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: battery + default: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 2 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 2 + choice: [] + unit: + description: Default mode for battery control + help: Inverter falls back to this mode after charging the battery or after stopping discharge. + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/anker-micro-inverter.yaml b/templates/release/en/meter/anker-micro-inverter.yaml new file mode 100644 index 0000000000..c2b07840a3 --- /dev/null +++ b/templates/release/en/meter/anker-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: anker-micro-inverter + brand: Anker + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/apsystems-ez1.yaml b/templates/release/en/meter/apsystems-ez1.yaml new file mode 100644 index 0000000000..ff96f1a79d --- /dev/null +++ b/templates/release/en/meter/apsystems-ez1.yaml @@ -0,0 +1,22 @@ +template: apsystems-ez1 +product: + identifier: apsystems-ez1 + brand: APsystems + description: EZ1 +render: + - usage: pv + default: | + type: template + template: apsystems-ez1 + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/apsystems-ez1_0.yaml b/templates/release/en/meter/apsystems-ez1_0.yaml deleted file mode 100644 index 270fae6e88..0000000000 --- a/templates/release/en/meter/apsystems-ez1_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: APsystems - description: EZ1 -render: - - usage: pv - default: | - type: template - template: apsystems-ez1 - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/avm-fritzdect.yaml b/templates/release/en/meter/avm-fritzdect.yaml new file mode 100644 index 0000000000..3a00454390 --- /dev/null +++ b/templates/release/en/meter/avm-fritzdect.yaml @@ -0,0 +1,62 @@ +template: fritzdect +product: + identifier: avm-fritzdect + brand: AVM + description: FritzDECT + group: Switchable sockets +render: + - usage: pv + default: | + type: template + template: fritzdect + usage: pv + uri: https://fritz.box # URI, HTTP(S) address (optional) + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. + - usage: charge + default: | + type: template + template: fritzdect + usage: charge + uri: https://fritz.box # URI, HTTP(S) address (optional) + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. +params: + - name: uri + example: + default: https://fritz.box + choice: [] + unit: + description: URI + help: HTTP(S) address + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: ain + example: 307788992233 + default: + choice: [] + unit: + description: Actor Identification Number (AIN) + help: Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/axitec-axihycon-12-15h.yaml b/templates/release/en/meter/axitec-axihycon-12-15h.yaml new file mode 100644 index 0000000000..86ff1a7b81 --- /dev/null +++ b/templates/release/en/meter/axitec-axihycon-12-15h.yaml @@ -0,0 +1,150 @@ +template: solis-hybrid-s +product: + identifier: axitec-axihycon-12-15h + brand: Axitec + description: AXIhycon 12-15H +render: + - usage: grid + default: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/bernecker-engineering-mpm3pm.yaml b/templates/release/en/meter/bernecker-engineering-mpm3pm.yaml new file mode 100644 index 0000000000..7d3910399f --- /dev/null +++ b/templates/release/en/meter/bernecker-engineering-mpm3pm.yaml @@ -0,0 +1,61 @@ +template: mpm3pm +product: + identifier: bernecker-engineering-mpm3pm + brand: Bernecker Engineering + description: MPM3PM +render: + - usage: grid + default: | + type: template + template: mpm3pm + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: mpm3pm + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/bge_tech_ds100_0.yaml b/templates/release/en/meter/bge_tech_ds100_0.yaml deleted file mode 100644 index 14bc06d873..0000000000 --- a/templates/release/en/meter/bge_tech_ds100_0.yaml +++ /dev/null @@ -1,100 +0,0 @@ -product: - brand: BGEtech - description: DS100 -render: - - usage: grid - default: | - type: template - template: bge_tech_ds100 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: bge_tech_ds100 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: bge_tech_ds100 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: aux - default: | - type: template - template: bge_tech_ds100 - usage: aux - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/bge_tech_ws100_0.yaml b/templates/release/en/meter/bge_tech_ws100_0.yaml deleted file mode 100644 index 13119038a7..0000000000 --- a/templates/release/en/meter/bge_tech_ws100_0.yaml +++ /dev/null @@ -1,100 +0,0 @@ -product: - brand: BGEtech - description: WS100 -render: - - usage: grid - default: | - type: template - template: bge_tech_ws100 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: bge_tech_ws100 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: bge_tech_ws100 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: aux - default: | - type: template - template: bge_tech_ws100 - usage: aux - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/bgetech-ds100.yaml b/templates/release/en/meter/bgetech-ds100.yaml new file mode 100644 index 0000000000..c4718cb5cc --- /dev/null +++ b/templates/release/en/meter/bgetech-ds100.yaml @@ -0,0 +1,122 @@ +template: bge_tech_ds100 +product: + identifier: bgetech-ds100 + brand: BGEtech + description: DS100 +render: + - usage: grid + default: | + type: template + template: bge_tech_ds100 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: bge_tech_ds100 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: bge_tech_ds100 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: aux + default: | + type: template + template: bge_tech_ds100 + usage: aux + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 1200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/bgetech-ws100.yaml b/templates/release/en/meter/bgetech-ws100.yaml new file mode 100644 index 0000000000..b1f7bbd153 --- /dev/null +++ b/templates/release/en/meter/bgetech-ws100.yaml @@ -0,0 +1,122 @@ +template: bge_tech_ws100 +product: + identifier: bgetech-ws100 + brand: BGEtech + description: WS100 +render: + - usage: grid + default: | + type: template + template: bge_tech_ws100 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: bge_tech_ws100 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: bge_tech_ws100 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: aux + default: | + type: template + template: bge_tech_ws100 + usage: aux + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 1200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 1200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/bosch-bpt-s-5-hybrid.yaml b/templates/release/en/meter/bosch-bpt-s-5-hybrid.yaml new file mode 100644 index 0000000000..8bd0c6b98d --- /dev/null +++ b/templates/release/en/meter/bosch-bpt-s-5-hybrid.yaml @@ -0,0 +1,60 @@ +template: bosch-bpt +product: + identifier: bosch-bpt-s-5-hybrid + brand: Bosch + description: BPT-S 5 Hybrid +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: bosch-bpt + usage: grid + uri: # URI, HTTP(S) address (optional) + advanced: | + type: template + template: bosch-bpt + usage: grid + uri: # URI, HTTP(S) address (optional) + - usage: pv + default: | + type: template + template: bosch-bpt + usage: pv + uri: # URI, HTTP(S) address (optional) + advanced: | + type: template + template: bosch-bpt + usage: pv + uri: # URI, HTTP(S) address (optional) + - usage: battery + default: | + type: template + template: bosch-bpt + usage: battery + uri: # URI, HTTP(S) address (optional) + advanced: | + type: template + template: bosch-bpt + usage: battery + uri: # URI, HTTP(S) address (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: uri + example: + default: + choice: [] + unit: + description: URI + help: HTTP(S) address + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/bosch-bpt_0.yaml b/templates/release/en/meter/bosch-bpt_0.yaml deleted file mode 100644 index addeb3d601..0000000000 --- a/templates/release/en/meter/bosch-bpt_0.yaml +++ /dev/null @@ -1,39 +0,0 @@ -product: - brand: Bosch - description: BPT-S 5 Hybrid -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: bosch-bpt - usage: grid - uri: # URI, HTTP(S) address (optional) - advanced: | - type: template - template: bosch-bpt - usage: grid - uri: # URI, HTTP(S) address (optional) - - usage: pv - default: | - type: template - template: bosch-bpt - usage: pv - uri: # URI, HTTP(S) address (optional) - advanced: | - type: template - template: bosch-bpt - usage: pv - uri: # URI, HTTP(S) address (optional) - - usage: battery - default: | - type: template - template: bosch-bpt - usage: battery - uri: # URI, HTTP(S) address (optional) - advanced: | - type: template - template: bosch-bpt - usage: battery - uri: # URI, HTTP(S) address (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/bosswerk-micro-inverter.yaml b/templates/release/en/meter/bosswerk-micro-inverter.yaml new file mode 100644 index 0000000000..0434da45af --- /dev/null +++ b/templates/release/en/meter/bosswerk-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: bosswerk-micro-inverter + brand: Bosswerk + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml b/templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml new file mode 100644 index 0000000000..b75d465d27 --- /dev/null +++ b/templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml @@ -0,0 +1,61 @@ +template: cg-emt1xx +product: + identifier: carlo-gavazzi-em110-111-112 + brand: Carlo Gavazzi + description: EM110/111/112 +render: + - usage: pv + default: | + type: template + template: cg-emt1xx + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt1xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/carlo-gavazzi-em24.yaml b/templates/release/en/meter/carlo-gavazzi-em24.yaml new file mode 100644 index 0000000000..4d1ac3ffcb --- /dev/null +++ b/templates/release/en/meter/carlo-gavazzi-em24.yaml @@ -0,0 +1,64 @@ +template: cg-em24 +product: + identifier: carlo-gavazzi-em24 + brand: Carlo Gavazzi + description: EM24 +description: | + EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. + +render: + - usage: grid + default: | + type: template + template: cg-em24 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/carlo-gavazzi-em24_e1.yaml b/templates/release/en/meter/carlo-gavazzi-em24_e1.yaml new file mode 100644 index 0000000000..8dae3ab2d9 --- /dev/null +++ b/templates/release/en/meter/carlo-gavazzi-em24_e1.yaml @@ -0,0 +1,48 @@ +template: cg-em24_e1 +product: + identifier: carlo-gavazzi-em24_e1 + brand: Carlo Gavazzi + description: EM24_E1 +description: | + EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. + The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + +render: + - usage: grid + default: | + type: template + template: cg-em24_e1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24_e1 + usage: charge + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/carlo-gavazzi-em330-em340.yaml b/templates/release/en/meter/carlo-gavazzi-em330-em340.yaml new file mode 100644 index 0000000000..71771d9771 --- /dev/null +++ b/templates/release/en/meter/carlo-gavazzi-em330-em340.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: carlo-gavazzi-em330-em340 + brand: Carlo Gavazzi + description: EM330/EM340 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/carlo-gavazzi-em530-em540.yaml b/templates/release/en/meter/carlo-gavazzi-em530-em540.yaml new file mode 100644 index 0000000000..d0f5a82c17 --- /dev/null +++ b/templates/release/en/meter/carlo-gavazzi-em530-em540.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: carlo-gavazzi-em530-em540 + brand: Carlo Gavazzi + description: EM530/EM540 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/carlo-gavazzi-et112.yaml b/templates/release/en/meter/carlo-gavazzi-et112.yaml new file mode 100644 index 0000000000..16680813b5 --- /dev/null +++ b/templates/release/en/meter/carlo-gavazzi-et112.yaml @@ -0,0 +1,61 @@ +template: cg-emt1xx +product: + identifier: carlo-gavazzi-et112 + brand: Carlo Gavazzi + description: ET112 +render: + - usage: pv + default: | + type: template + template: cg-emt1xx + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt1xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/carlo-gavazzi-et330-et340.yaml b/templates/release/en/meter/carlo-gavazzi-et330-et340.yaml new file mode 100644 index 0000000000..da396ac6cc --- /dev/null +++ b/templates/release/en/meter/carlo-gavazzi-et330-et340.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: carlo-gavazzi-et330-et340 + brand: Carlo Gavazzi + description: ET330/ET340 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/cfos-powerbrain-meter.yaml b/templates/release/en/meter/cfos-powerbrain-meter.yaml new file mode 100644 index 0000000000..3eb38abc45 --- /dev/null +++ b/templates/release/en/meter/cfos-powerbrain-meter.yaml @@ -0,0 +1,34 @@ +template: cfos +product: + identifier: cfos-powerbrain-meter + brand: cFos + description: PowerBrain Meter +requirements: ["sponsorship"] +render: + - usage: charge + default: | + type: template + template: cfos + usage: charge + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 4702 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 4702 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/cfos_0.yaml b/templates/release/en/meter/cfos_0.yaml deleted file mode 100644 index c7b87e0fcf..0000000000 --- a/templates/release/en/meter/cfos_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: cFos - description: PowerBrain Meter -requirements: ["sponsorship"] -render: - - usage: charge - default: | - type: template - template: cfos - usage: charge - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 4702 # Port diff --git a/templates/release/en/meter/cg-em24_0.yaml b/templates/release/en/meter/cg-em24_0.yaml deleted file mode 100644 index 25b895e0bc..0000000000 --- a/templates/release/en/meter/cg-em24_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM24 -description: | - EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. - -render: - - usage: grid - default: | - type: template - template: cg-em24 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-em24_1.yaml b/templates/release/en/meter/cg-em24_1.yaml deleted file mode 100644 index ae345cf0b1..0000000000 --- a/templates/release/en/meter/cg-em24_1.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Victron - description: EM24 -description: | - EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. - -render: - - usage: grid - default: | - type: template - template: cg-em24 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-em24_e1_0.yaml b/templates/release/en/meter/cg-em24_e1_0.yaml deleted file mode 100644 index bfa3faf840..0000000000 --- a/templates/release/en/meter/cg-em24_e1_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM24_E1 -description: | - EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. - The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - -render: - - usage: grid - default: | - type: template - template: cg-em24_e1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24_e1 - usage: charge - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-em24_e1_1.yaml b/templates/release/en/meter/cg-em24_e1_1.yaml deleted file mode 100644 index 41616d459f..0000000000 --- a/templates/release/en/meter/cg-em24_e1_1.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Victron - description: EM24_E1 -description: | - EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. - The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) - -render: - - usage: grid - default: | - type: template - template: cg-em24_e1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-em24_e1 - usage: charge - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt1xx_0.yaml b/templates/release/en/meter/cg-emt1xx_0.yaml deleted file mode 100644 index f888b1d08a..0000000000 --- a/templates/release/en/meter/cg-emt1xx_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM110/111/112 -render: - - usage: pv - default: | - type: template - template: cg-emt1xx - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt1xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt1xx_1.yaml b/templates/release/en/meter/cg-emt1xx_1.yaml deleted file mode 100644 index 2e307a267d..0000000000 --- a/templates/release/en/meter/cg-emt1xx_1.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Carlo Gavazzi - description: ET112 -render: - - usage: pv - default: | - type: template - template: cg-emt1xx - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt1xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt3xx_0.yaml b/templates/release/en/meter/cg-emt3xx_0.yaml deleted file mode 100644 index c9e82d203f..0000000000 --- a/templates/release/en/meter/cg-emt3xx_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Carlo Gavazzi - description: ET330/ET340 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt3xx_1.yaml b/templates/release/en/meter/cg-emt3xx_1.yaml deleted file mode 100644 index 20f08771e4..0000000000 --- a/templates/release/en/meter/cg-emt3xx_1.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM330/EM340 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt3xx_2.yaml b/templates/release/en/meter/cg-emt3xx_2.yaml deleted file mode 100644 index 5d4dad42c1..0000000000 --- a/templates/release/en/meter/cg-emt3xx_2.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Carlo Gavazzi - description: EM530/EM540 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt3xx_3.yaml b/templates/release/en/meter/cg-emt3xx_3.yaml deleted file mode 100644 index c2d1600b67..0000000000 --- a/templates/release/en/meter/cg-emt3xx_3.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Victron - description: ET340 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt3xx_4.yaml b/templates/release/en/meter/cg-emt3xx_4.yaml deleted file mode 100644 index 7235030cd2..0000000000 --- a/templates/release/en/meter/cg-emt3xx_4.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Victron - description: EM530/EM540 -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/cg-emt3xx_5.yaml b/templates/release/en/meter/cg-emt3xx_5.yaml deleted file mode 100644 index 335ed59fe7..0000000000 --- a/templates/release/en/meter/cg-emt3xx_5.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Kostal - description: Energy Meter C (KEM-C) -render: - - usage: grid - default: | - type: template - template: cg-emt3xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: cg-emt3xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/demo-battery.yaml b/templates/release/en/meter/demo-battery.yaml new file mode 100644 index 0000000000..7ef7b0ef96 --- /dev/null +++ b/templates/release/en/meter/demo-battery.yaml @@ -0,0 +1,91 @@ +template: demo-battery +product: + identifier: demo-battery + description: Demo battery + group: Generic support +description: | + For demonstration purposes. Battery with a fixed set of values. +render: + - usage: battery + default: | + type: template + template: demo-battery + usage: battery + power: # Power (W), optional + soc: # Charge (%), optional + controllable: # Controllable, Supports active battery control (optional) + advanced: | + type: template + template: demo-battery + usage: battery + power: # Power (W), optional + soc: # Charge (%), optional + controllable: # Controllable, Supports active battery control (optional) + energy: # Meter reading (kWh), optional + currentL1: # L1 current (A), optional + currentL2: # L2 current (A), optional + currentL3: # L3 current (A), optional +params: + - name: power + example: + default: + choice: [] + unit: W + description: Power + help: + advanced: false + optional: true + - name: soc + example: + default: + choice: [] + unit: '%' + description: Charge + help: + advanced: false + optional: true + - name: controllable + example: + default: + choice: [] + unit: + description: Controllable + help: Supports active battery control + advanced: false + optional: true + - name: energy + example: + default: + choice: [] + unit: kWh + description: Meter reading + help: + advanced: true + optional: true + - name: currentL1 + example: + default: + choice: [] + unit: A + description: L1 current + help: + advanced: true + optional: true + - name: currentL2 + example: + default: + choice: [] + unit: A + description: L2 current + help: + advanced: true + optional: true + - name: currentL3 + example: + default: + choice: [] + unit: A + description: L3 current + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/demo-battery_0.yaml b/templates/release/en/meter/demo-battery_0.yaml deleted file mode 100644 index d371cb0259..0000000000 --- a/templates/release/en/meter/demo-battery_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: Demo battery - group: Generic support -description: | - For demonstration purposes. Battery with a fixed set of values. -render: - - usage: battery - default: | - type: template - template: demo-battery - usage: battery - power: # Power (W), optional - soc: # Charge (%), optional - controllable: # Controllable, Supports active battery control (optional) - advanced: | - type: template - template: demo-battery - usage: battery - power: # Power (W), optional - soc: # Charge (%), optional - controllable: # Controllable, Supports active battery control (optional) - energy: # Meter reading (kWh), optional - currentL1: # L1 current (A), optional - currentL2: # L2 current (A), optional - currentL3: # L3 current (A), optional diff --git a/templates/release/en/meter/demo-meter.yaml b/templates/release/en/meter/demo-meter.yaml new file mode 100644 index 0000000000..f687b96084 --- /dev/null +++ b/templates/release/en/meter/demo-meter.yaml @@ -0,0 +1,114 @@ +template: demo-meter +product: + identifier: demo-meter + description: Demo meter + group: Generic support +description: | + For demonstration purposes. Meter with a fixed set of values. +render: + - usage: grid + default: | + type: template + template: demo-meter + usage: grid + power: # Power (W), optional + advanced: | + type: template + template: demo-meter + usage: grid + power: # Power (W), optional + energy: # Meter reading (kWh), optional + currentL1: # L1 current (A), optional + currentL2: # L2 current (A), optional + currentL3: # L3 current (A), optional + - usage: pv + default: | + type: template + template: demo-meter + usage: pv + power: # Power (W), optional + advanced: | + type: template + template: demo-meter + usage: pv + power: # Power (W), optional + energy: # Meter reading (kWh), optional + currentL1: # L1 current (A), optional + currentL2: # L2 current (A), optional + currentL3: # L3 current (A), optional + - usage: aux + default: | + type: template + template: demo-meter + usage: aux + power: # Power (W), optional + advanced: | + type: template + template: demo-meter + usage: aux + power: # Power (W), optional + energy: # Meter reading (kWh), optional + currentL1: # L1 current (A), optional + currentL2: # L2 current (A), optional + currentL3: # L3 current (A), optional + - usage: charge + default: | + type: template + template: demo-meter + usage: charge + power: # Power (W), optional + advanced: | + type: template + template: demo-meter + usage: charge + power: # Power (W), optional + energy: # Meter reading (kWh), optional + currentL1: # L1 current (A), optional + currentL2: # L2 current (A), optional + currentL3: # L3 current (A), optional +params: + - name: power + example: + default: + choice: [] + unit: W + description: Power + help: + advanced: false + optional: true + - name: energy + example: + default: + choice: [] + unit: kWh + description: Meter reading + help: + advanced: true + optional: true + - name: currentL1 + example: + default: + choice: [] + unit: A + description: L1 current + help: + advanced: true + optional: true + - name: currentL2 + example: + default: + choice: [] + unit: A + description: L2 current + help: + advanced: true + optional: true + - name: currentL3 + example: + default: + choice: [] + unit: A + description: L3 current + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/demo-meter_0.yaml b/templates/release/en/meter/demo-meter_0.yaml deleted file mode 100644 index ba6a661a7b..0000000000 --- a/templates/release/en/meter/demo-meter_0.yaml +++ /dev/null @@ -1,66 +0,0 @@ -product: - description: Demo meter - group: Generic support -description: | - For demonstration purposes. Meter with a fixed set of values. -render: - - usage: grid - default: | - type: template - template: demo-meter - usage: grid - power: # Power (W), optional - advanced: | - type: template - template: demo-meter - usage: grid - power: # Power (W), optional - energy: # Meter reading (kWh), optional - currentL1: # L1 current (A), optional - currentL2: # L2 current (A), optional - currentL3: # L3 current (A), optional - - usage: pv - default: | - type: template - template: demo-meter - usage: pv - power: # Power (W), optional - advanced: | - type: template - template: demo-meter - usage: pv - power: # Power (W), optional - energy: # Meter reading (kWh), optional - currentL1: # L1 current (A), optional - currentL2: # L2 current (A), optional - currentL3: # L3 current (A), optional - - usage: aux - default: | - type: template - template: demo-meter - usage: aux - power: # Power (W), optional - advanced: | - type: template - template: demo-meter - usage: aux - power: # Power (W), optional - energy: # Meter reading (kWh), optional - currentL1: # L1 current (A), optional - currentL2: # L2 current (A), optional - currentL3: # L3 current (A), optional - - usage: charge - default: | - type: template - template: demo-meter - usage: charge - power: # Power (W), optional - advanced: | - type: template - template: demo-meter - usage: charge - power: # Power (W), optional - energy: # Meter reading (kWh), optional - currentL1: # L1 current (A), optional - currentL2: # L2 current (A), optional - currentL3: # L3 current (A), optional diff --git a/templates/release/en/meter/deye-3p-hybrid-inverter.yaml b/templates/release/en/meter/deye-3p-hybrid-inverter.yaml new file mode 100644 index 0000000000..2bd7dc2adc --- /dev/null +++ b/templates/release/en/meter/deye-3p-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: deye-hybrid-3p +product: + identifier: deye-3p-hybrid-inverter + brand: Deye + description: 3p hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml b/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml new file mode 100644 index 0000000000..921e126e6f --- /dev/null +++ b/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml @@ -0,0 +1,236 @@ +template: deye-hybrid-hp3 +product: + identifier: deye-hp3-hybrid-inverter + brand: Deye + description: hp3 hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + includegenport: # Treat GEN port as solar input, optional + - usage: pv + default: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + includegenport: # Treat GEN port as solar input, optional + - usage: battery + default: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + capacity: 50 # Battery capacity (kWh), optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + includegenport: # Treat GEN port as solar input, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: includegenport + example: + default: + choice: [] + unit: + description: Treat GEN port as solar input + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/deye-hybrid-3p_0.yaml b/templates/release/en/meter/deye-hybrid-3p_0.yaml deleted file mode 100644 index d99d1696c1..0000000000 --- a/templates/release/en/meter/deye-hybrid-3p_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: Deye - description: 3p hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/deye-hybrid-3p_1.yaml b/templates/release/en/meter/deye-hybrid-3p_1.yaml deleted file mode 100644 index 71ed1480d3..0000000000 --- a/templates/release/en/meter/deye-hybrid-3p_1.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: Sunsynk - description: 3p hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-3p - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/deye-hybrid-hp3_0.yaml b/templates/release/en/meter/deye-hybrid-hp3_0.yaml deleted file mode 100644 index 295a5506ab..0000000000 --- a/templates/release/en/meter/deye-hybrid-hp3_0.yaml +++ /dev/null @@ -1,160 +0,0 @@ -product: - brand: Deye - description: hp3 hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - includegenport: # Treat GEN port as solar input, optional - - usage: pv - default: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - includegenport: # Treat GEN port as solar input, optional - - usage: battery - default: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - capacity: 50 # Battery capacity (kWh), optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - includegenport: # Treat GEN port as solar input, optional diff --git a/templates/release/en/meter/deye-hybrid-hp3_1.yaml b/templates/release/en/meter/deye-hybrid-hp3_1.yaml deleted file mode 100644 index b51d2fc8e9..0000000000 --- a/templates/release/en/meter/deye-hybrid-hp3_1.yaml +++ /dev/null @@ -1,160 +0,0 @@ -product: - brand: Sunsynk - description: hp3 hybrid inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - includegenport: # Treat GEN port as solar input, optional - - usage: pv - default: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - includegenport: # Treat GEN port as solar input, optional - - usage: battery - default: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-hybrid-hp3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - storageunit: 1 # optional - capacity: 50 # Battery capacity (kWh), optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - includegenport: # Treat GEN port as solar input, optional diff --git a/templates/release/en/meter/deye-mi_0.yaml b/templates/release/en/meter/deye-mi_0.yaml deleted file mode 100644 index 330b3dd9a3..0000000000 --- a/templates/release/en/meter/deye-mi_0.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Deye - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/deye-mi_1.yaml b/templates/release/en/meter/deye-mi_1.yaml deleted file mode 100644 index aef8b45064..0000000000 --- a/templates/release/en/meter/deye-mi_1.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Bosswerk - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/deye-mi_2.yaml b/templates/release/en/meter/deye-mi_2.yaml deleted file mode 100644 index 02fbe72af3..0000000000 --- a/templates/release/en/meter/deye-mi_2.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Anker - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/deye-mi_3.yaml b/templates/release/en/meter/deye-mi_3.yaml deleted file mode 100644 index 8a119828bd..0000000000 --- a/templates/release/en/meter/deye-mi_3.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: Sunsynk - description: Micro inverter -render: - - usage: pv - default: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-mi - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/deye-micro-inverter.yaml b/templates/release/en/meter/deye-micro-inverter.yaml new file mode 100644 index 0000000000..b8ec8bd1dc --- /dev/null +++ b/templates/release/en/meter/deye-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: deye-micro-inverter + brand: Deye + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/deye-storage-hybrid-inverter.yaml b/templates/release/en/meter/deye-storage-hybrid-inverter.yaml new file mode 100644 index 0000000000..0d650decbf --- /dev/null +++ b/templates/release/en/meter/deye-storage-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: deye-storage +product: + identifier: deye-storage-hybrid-inverter + brand: Deye + description: Storage (hybrid) inverter +render: + - usage: pv + default: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + - usage: grid + default: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/deye-storage_0.yaml b/templates/release/en/meter/deye-storage_0.yaml deleted file mode 100644 index 7364fc1207..0000000000 --- a/templates/release/en/meter/deye-storage_0.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: Deye - description: Storage (hybrid) inverter -render: - - usage: pv - default: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - - usage: grid - default: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/deye-storage_1.yaml b/templates/release/en/meter/deye-storage_1.yaml deleted file mode 100644 index 9983191dab..0000000000 --- a/templates/release/en/meter/deye-storage_1.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: Sunsynk - description: Storage (hybrid) inverter -render: - - usage: pv - default: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - - usage: grid - default: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: deye-storage - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/deye-string-inverter.yaml b/templates/release/en/meter/deye-string-inverter.yaml new file mode 100644 index 0000000000..5c65be54c8 --- /dev/null +++ b/templates/release/en/meter/deye-string-inverter.yaml @@ -0,0 +1,50 @@ +template: deye-string +product: + identifier: deye-string-inverter + brand: Deye + description: String inverter +render: + - usage: pv + default: | + type: template + template: deye-string + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/deye-string_0.yaml b/templates/release/en/meter/deye-string_0.yaml deleted file mode 100644 index b584ebb31a..0000000000 --- a/templates/release/en/meter/deye-string_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Deye - description: String inverter -render: - - usage: pv - default: | - type: template - template: deye-string - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/deye-string_1.yaml b/templates/release/en/meter/deye-string_1.yaml deleted file mode 100644 index b1959c2963..0000000000 --- a/templates/release/en/meter/deye-string_1.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Sunsynk - description: String inverter -render: - - usage: pv - default: | - type: template - template: deye-string - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/discovergy.yaml b/templates/release/en/meter/discovergy.yaml new file mode 100644 index 0000000000..517fc0be1b --- /dev/null +++ b/templates/release/en/meter/discovergy.yaml @@ -0,0 +1,49 @@ +template: discovergy +product: + identifier: discovergy + description: Discovergy +render: + - usage: grid + default: | + type: template + template: discovergy + usage: grid + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + meter: 1ESY1161229886 + - usage: pv + default: | + type: template + template: discovergy + usage: pv + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + meter: 1ESY1161229886 +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: meter + example: 1ESY1161229886 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/discovergy_0.yaml b/templates/release/en/meter/discovergy_0.yaml deleted file mode 100644 index 1c3433ab4a..0000000000 --- a/templates/release/en/meter/discovergy_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - description: Discovergy -render: - - usage: grid - default: | - type: template - template: discovergy - usage: grid - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886 - - usage: pv - default: | - type: template - template: discovergy - usage: pv - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886 diff --git a/templates/release/en/meter/dsmr.yaml b/templates/release/en/meter/dsmr.yaml new file mode 100644 index 0000000000..7785f404b1 --- /dev/null +++ b/templates/release/en/meter/dsmr.yaml @@ -0,0 +1,47 @@ +template: dsmr +product: + identifier: dsmr + brand: DSMR +render: + - usage: grid + default: | + type: template + template: dsmr + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 1502 # Port, optional + advanced: | + type: template + template: dsmr + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 1502 # Port, optional + energy: # OBIS code for energy consumption, Typically 1-0:1.8.0 or 1-0:1.8.1/1-0:1.8.2 with multiple tariffs (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 1502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: energy + example: + default: + choice: [] + unit: + description: OBIS code for energy consumption + help: Typically 1-0:1.8.0 or 1-0:1.8.1/1-0:1.8.2 with multiple tariffs + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/dsmr_0.yaml b/templates/release/en/meter/dsmr_0.yaml deleted file mode 100644 index d446e15f9c..0000000000 --- a/templates/release/en/meter/dsmr_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: DSMR -render: - - usage: grid - default: | - type: template - template: dsmr - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 1502 # Port, optional - advanced: | - type: template - template: dsmr - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 1502 # Port, optional - energy: # OBIS code for energy consumption, Typically 1-0:1.8.0 or 1-0:1.8.1/1-0:1.8.2 with multiple tariffs (optional) diff --git a/templates/release/en/meter/dzg-dvh4013.yaml b/templates/release/en/meter/dzg-dvh4013.yaml new file mode 100644 index 0000000000..8a56066ec7 --- /dev/null +++ b/templates/release/en/meter/dzg-dvh4013.yaml @@ -0,0 +1,43 @@ +template: dzg +product: + identifier: dzg-dvh4013 + brand: DZG + description: DVH4013 +render: + - usage: charge + default: | + type: template + template: dzg + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/dzg_0.yaml b/templates/release/en/meter/dzg_0.yaml deleted file mode 100644 index 944659a798..0000000000 --- a/templates/release/en/meter/dzg_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: DZG - description: DVH4013 -render: - - usage: charge - default: | - type: template - template: dzg - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/e3-dc.yaml b/templates/release/en/meter/e3-dc.yaml new file mode 100644 index 0000000000..2fa2918a06 --- /dev/null +++ b/templates/release/en/meter/e3-dc.yaml @@ -0,0 +1,146 @@ +template: e3dc-rscp +product: + identifier: e3-dc + brand: E3/DC +capabilities: ["battery-control"] +description: | + Username and password are identical to Web Portal or My E3/DC App access. Key (=RSCP-Password) must be set in the E3/DC system at Personalize/User Profile. The IP adresses of evcc and E3/DC system must be in the same subnet. + + **Note**: Active battery control will override Smart-Power/Operating Range settings. + +render: + - usage: grid + default: | + type: template + template: e3dc-rscp + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 5033 # Port, optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + key: + advanced: | + type: template + template: e3dc-rscp + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 5033 # Port, optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + key: + dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) + - usage: pv + default: | + type: template + template: e3dc-rscp + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 5033 # Port, optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + key: + advanced: | + type: template + template: e3dc-rscp + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 5033 # Port, optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + key: + dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: e3dc-rscp + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 5033 # Port, optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + key: + advanced: | + type: template + template: e3dc-rscp + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 5033 # Port, optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + key: + dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 5033 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: key + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: dischargelimit + example: + default: + choice: [] + unit: + description: Discharge limit in W + help: Limits discharge power in 'Hold' battery mode + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/e3dc-rscp_0.yaml b/templates/release/en/meter/e3dc-rscp_0.yaml deleted file mode 100644 index 46c1417c33..0000000000 --- a/templates/release/en/meter/e3dc-rscp_0.yaml +++ /dev/null @@ -1,71 +0,0 @@ -product: - brand: E3/DC -capabilities: ["battery-control"] -description: | - Username and password are identical to Web Portal or My E3/DC App access. Key (=RSCP-Password) must be set in the E3/DC system at Personalize/User Profile. The IP adresses of evcc and E3/DC system must be in the same subnet. - - **Note**: Active battery control will override Smart-Power/Operating Range settings. - -render: - - usage: grid - default: | - type: template - template: e3dc-rscp - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 5033 # Port, optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - key: - advanced: | - type: template - template: e3dc-rscp - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 5033 # Port, optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - key: - dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) - - usage: pv - default: | - type: template - template: e3dc-rscp - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 5033 # Port, optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - key: - advanced: | - type: template - template: e3dc-rscp - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 5033 # Port, optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - key: - dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: e3dc-rscp - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 5033 # Port, optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - key: - advanced: | - type: template - template: e3dc-rscp - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 5033 # Port, optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - key: - dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/eastron-sdm120-modbus.yaml b/templates/release/en/meter/eastron-sdm120-modbus.yaml new file mode 100644 index 0000000000..73b2709021 --- /dev/null +++ b/templates/release/en/meter/eastron-sdm120-modbus.yaml @@ -0,0 +1,79 @@ +template: eastron-sdm120 +product: + identifier: eastron-sdm120-modbus + brand: Eastron + description: SDM120-Modbus +render: + - usage: grid + default: | + type: template + template: eastron-sdm120 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm120 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: eastron-sdm120 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/eastron-sdm120_0.yaml b/templates/release/en/meter/eastron-sdm120_0.yaml deleted file mode 100644 index c523f27872..0000000000 --- a/templates/release/en/meter/eastron-sdm120_0.yaml +++ /dev/null @@ -1,58 +0,0 @@ -product: - brand: Eastron - description: SDM120-Modbus -render: - - usage: grid - default: | - type: template - template: eastron-sdm120 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm120 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: eastron-sdm120 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron-sdm220-230.yaml b/templates/release/en/meter/eastron-sdm220-230.yaml new file mode 100644 index 0000000000..c6cf09acf7 --- /dev/null +++ b/templates/release/en/meter/eastron-sdm220-230.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm220_230 +product: + identifier: eastron-sdm220-230 + brand: Eastron + description: SDM220/230 +render: + - usage: grid + default: | + type: template + template: eastron-sdm220_230 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm220_230 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/eastron-sdm220_230_0.yaml b/templates/release/en/meter/eastron-sdm220_230_0.yaml deleted file mode 100644 index 52e4d9b147..0000000000 --- a/templates/release/en/meter/eastron-sdm220_230_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM220/230 -render: - - usage: grid - default: | - type: template - template: eastron-sdm220_230 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm220_230 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron-sdm220_230_1.yaml b/templates/release/en/meter/eastron-sdm220_230_1.yaml deleted file mode 100644 index 17900c48e0..0000000000 --- a/templates/release/en/meter/eastron-sdm220_230_1.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM110-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron-sdm220_230 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm220_230 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron-sdm220_230_2.yaml b/templates/release/en/meter/eastron-sdm220_230_2.yaml deleted file mode 100644 index dc9eab47b9..0000000000 --- a/templates/release/en/meter/eastron-sdm220_230_2.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM111-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron-sdm220_230 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm220_230 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron-sdm630-modbus.yaml b/templates/release/en/meter/eastron-sdm630-modbus.yaml new file mode 100644 index 0000000000..bb5ee3cccb --- /dev/null +++ b/templates/release/en/meter/eastron-sdm630-modbus.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: eastron-sdm630-modbus + brand: Eastron + description: SDM630-Modbus +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/eastron-sdm72_0.yaml b/templates/release/en/meter/eastron-sdm72_0.yaml deleted file mode 100644 index bbc7de94e2..0000000000 --- a/templates/release/en/meter/eastron-sdm72_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM72D-M -render: - - usage: grid - default: | - type: template - template: eastron-sdm72 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron-sdm72 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron-sdm72d-m.yaml b/templates/release/en/meter/eastron-sdm72d-m.yaml new file mode 100644 index 0000000000..9ebaf66503 --- /dev/null +++ b/templates/release/en/meter/eastron-sdm72d-m.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm72 +product: + identifier: eastron-sdm72d-m + brand: Eastron + description: SDM72D-M +render: + - usage: grid + default: | + type: template + template: eastron-sdm72 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm72 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/eastron-sdm72dm-v2.yaml b/templates/release/en/meter/eastron-sdm72dm-v2.yaml new file mode 100644 index 0000000000..552313a71d --- /dev/null +++ b/templates/release/en/meter/eastron-sdm72dm-v2.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: eastron-sdm72dm-v2 + brand: Eastron + description: SDM72DM-V2 +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/eastron_0.yaml b/templates/release/en/meter/eastron_0.yaml deleted file mode 100644 index c15d696c08..0000000000 --- a/templates/release/en/meter/eastron_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM630-Modbus -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron_1.yaml b/templates/release/en/meter/eastron_1.yaml deleted file mode 100644 index dbc823ff78..0000000000 --- a/templates/release/en/meter/eastron_1.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Eastron - description: SDM72DM-V2 -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron_2.yaml b/templates/release/en/meter/eastron_2.yaml deleted file mode 100644 index 02e5115691..0000000000 --- a/templates/release/en/meter/eastron_2.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM120-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron_3.yaml b/templates/release/en/meter/eastron_3.yaml deleted file mode 100644 index 3086ab92f7..0000000000 --- a/templates/release/en/meter/eastron_3.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Weidmüller - description: EM122-RTU-2P -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/eastron_4.yaml b/templates/release/en/meter/eastron_4.yaml deleted file mode 100644 index 407eedce68..0000000000 --- a/templates/release/en/meter/eastron_4.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Kostal - description: Energy Meter P (KEM-P) -render: - - usage: grid - default: | - type: template - template: eastron - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: eastron - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/enphase-iq-envoy.yaml b/templates/release/en/meter/enphase-iq-envoy.yaml new file mode 100644 index 0000000000..49ffc4000a --- /dev/null +++ b/templates/release/en/meter/enphase-iq-envoy.yaml @@ -0,0 +1,88 @@ +template: enphase +product: + identifier: enphase-iq-envoy + brand: Enphase + description: IQ Envoy +description: | + Only batteries of type "AC Battery" are currently supported by Enphase-API. +render: + - usage: grid + default: | + type: template + template: enphase + usage: grid + host: 192.0.2.2 # IP address or hostname + token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + advanced: | + type: template + template: enphase + usage: grid + host: 192.0.2.2 # IP address or hostname + token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: enphase + usage: pv + host: 192.0.2.2 # IP address or hostname + token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + advanced: | + type: template + template: enphase + usage: pv + host: 192.0.2.2 # IP address or hostname + token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: battery + default: | + type: template + template: enphase + usage: battery + host: 192.0.2.2 # IP address or hostname + token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + advanced: | + type: template + template: enphase + usage: battery + host: 192.0.2.2 # IP address or hostname + token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + capacity: 50 # Battery capacity (kWh), optional + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: 'Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication' + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/enphase_0.yaml b/templates/release/en/meter/enphase_0.yaml deleted file mode 100644 index 80d13c73f5..0000000000 --- a/templates/release/en/meter/enphase_0.yaml +++ /dev/null @@ -1,49 +0,0 @@ -product: - brand: Enphase - description: IQ Envoy -description: | - Only batteries of type "AC Battery" are currently supported by Enphase-API. -render: - - usage: grid - default: | - type: template - template: enphase - usage: grid - host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - advanced: | - type: template - template: enphase - usage: grid - host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - - usage: pv - default: | - type: template - template: enphase - usage: pv - host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - advanced: | - type: template - template: enphase - usage: pv - host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - - usage: battery - default: | - type: template - template: enphase - usage: battery - host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - advanced: | - type: template - template: enphase - usage: battery - host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) - capacity: 50 # Battery capacity (kWh), optional - cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/meter/esphome-dlms-austria_0.yaml b/templates/release/en/meter/esphome-dlms-austria_0.yaml deleted file mode 100644 index 4add4696f6..0000000000 --- a/templates/release/en/meter/esphome-dlms-austria_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: ESPHome - description: DLMS Meter Austria -description: | - Requires an ESPHome node running the `dlms_meter` component (e.g., from `github://SimonFischer04/esphome@dlms-meter`), - configured for Austrian DLMS meters. - -render: - - usage: grid - default: | - type: template - template: esphome-dlms-austria - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: esphome-dlms-austria - usage: grid - host: 192.0.2.2 # IP address or hostname - timeout: 10s # Timeout, optional diff --git a/templates/release/en/meter/esphome-dlms-meter-austria.yaml b/templates/release/en/meter/esphome-dlms-meter-austria.yaml new file mode 100644 index 0000000000..0092818ac7 --- /dev/null +++ b/templates/release/en/meter/esphome-dlms-meter-austria.yaml @@ -0,0 +1,41 @@ +template: esphome-dlms-austria +product: + identifier: esphome-dlms-meter-austria + brand: ESPHome + description: DLMS Meter Austria +description: | + Requires an ESPHome node running the `dlms_meter` component (e.g., from `github://SimonFischer04/esphome@dlms-meter`), + configured for Austrian DLMS meters. + +render: + - usage: grid + default: | + type: template + template: esphome-dlms-austria + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: esphome-dlms-austria + usage: grid + host: 192.0.2.2 # IP address or hostname + timeout: 10s # Timeout, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: 10s + choice: [] + unit: + description: Timeout + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/esphome-dsmr.yaml b/templates/release/en/meter/esphome-dsmr.yaml new file mode 100644 index 0000000000..0902751e9b --- /dev/null +++ b/templates/release/en/meter/esphome-dsmr.yaml @@ -0,0 +1,37 @@ +template: slimmelezer +product: + identifier: esphome-dsmr + brand: ESPHome + description: DSMR +render: + - usage: grid + default: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP address or hostname + scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: scale + example: 1 | 10 | 100 | 1000 + default: 1000 + choice: [] + unit: + description: Scale factor + help: Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/fenecon.yaml b/templates/release/en/meter/fenecon.yaml new file mode 100644 index 0000000000..f3b1a45f63 --- /dev/null +++ b/templates/release/en/meter/fenecon.yaml @@ -0,0 +1,104 @@ +template: openems +product: + identifier: fenecon + brand: FENECON +capabilities: ["battery-control"] +description: | + A commercial license is required for FEMS FENECON systems for active battery control. + +render: + - usage: grid + default: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP address or hostname + password: user # Password, Use single quotes in case of leading zeros (optional) + - usage: pv + default: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP address or hostname + password: user # Password, Use single quotes in case of leading zeros (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP address or hostname + password: user # Password, Use single quotes in case of leading zeros (optional) + battery: ess0 # controllable battery component (optional) + watchdog: 60s # adjusted to the API timeout (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: password + example: + default: user + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true + - name: battery + example: ess0 + default: + choice: [] + unit: + description: + help: controllable battery component + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: adjusted to the API timeout + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/fox-ess-h1_0.yaml b/templates/release/en/meter/fox-ess-h1_0.yaml deleted file mode 100644 index 5e59afc060..0000000000 --- a/templates/release/en/meter/fox-ess-h1_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: FoxESS - description: H1 Series Hybrid Inverter -render: - - usage: pv - default: | - type: template - template: fox-ess-h1 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: fox-ess-h1 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/fox-ess-h3-smart_0.yaml b/templates/release/en/meter/fox-ess-h3-smart_0.yaml deleted file mode 100644 index de82de19ad..0000000000 --- a/templates/release/en/meter/fox-ess-h3-smart_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: FoxESS - description: H3-Smart Series Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: fox-ess-h3-smart - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3-smart - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: fox-ess-h3-smart - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3-smart - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/fox-ess-h3_0.yaml b/templates/release/en/meter/fox-ess-h3_0.yaml deleted file mode 100644 index f6b88aa5ed..0000000000 --- a/templates/release/en/meter/fox-ess-h3_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: FoxESS - description: H3 Series Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: fox-ess-h3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: fox-ess-h3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: fox-ess-h3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml b/templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..d696651368 --- /dev/null +++ b/templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml @@ -0,0 +1,74 @@ +template: fox-ess-h1 +product: + identifier: foxess-h1-series-hybrid-inverter + brand: FoxESS + description: H1 Series Hybrid Inverter +render: + - usage: pv + default: | + type: template + template: fox-ess-h1 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: fox-ess-h1 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml b/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..a57f0bb0fa --- /dev/null +++ b/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: fox-ess-h3 +product: + identifier: foxess-h3-series-hybrid-inverter + brand: FoxESS + description: H3 Series Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fox-ess-h3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: fox-ess-h3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: fox-ess-h3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml b/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..a0f8fa93d1 --- /dev/null +++ b/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: fox-ess-h3-smart +product: + identifier: foxess-h3-smart-series-hybrid-inverter + brand: FoxESS + description: H3-Smart Series Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fox-ess-h3-smart + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3-smart + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: fox-ess-h3-smart + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3-smart + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: fox-ess-h3-smart + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: fox-ess-h3-smart + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/fritzdect_0.yaml b/templates/release/en/meter/fritzdect_0.yaml deleted file mode 100644 index 5882189e5f..0000000000 --- a/templates/release/en/meter/fritzdect_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: AVM - description: FritzDECT - group: Switchable sockets -render: - - usage: pv - default: | - type: template - template: fritzdect - usage: pv - uri: https://fritz.box # URI, HTTP(S) address (optional) - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. - - usage: charge - default: | - type: template - template: fritzdect - usage: charge - uri: https://fritz.box # URI, HTTP(S) address (optional) - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - ain: 307788992233 # Actor Identification Number (AIN), Printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes. diff --git a/templates/release/en/meter/fronius-gen24_0.yaml b/templates/release/en/meter/fronius-gen24_0.yaml deleted file mode 100644 index f48056ee45..0000000000 --- a/templates/release/en/meter/fronius-gen24_0.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Fronius - description: Symo GEN24 Plus -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) - - usage: pv - default: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/fronius-gen24_1.yaml b/templates/release/en/meter/fronius-gen24_1.yaml deleted file mode 100644 index b80de12f23..0000000000 --- a/templates/release/en/meter/fronius-gen24_1.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Fronius - description: Primo GEN24 Plus -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) - - usage: pv - default: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: fronius-gen24 - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/fronius-ohmpilot.yaml b/templates/release/en/meter/fronius-ohmpilot.yaml new file mode 100644 index 0000000000..db198241b9 --- /dev/null +++ b/templates/release/en/meter/fronius-ohmpilot.yaml @@ -0,0 +1,37 @@ +template: fronius-ohmpilot +product: + identifier: fronius-ohmpilot + brand: Fronius + description: Ohmpilot +render: + - usage: aux + default: | + type: template + template: fronius-ohmpilot + usage: aux + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: fronius-ohmpilot + usage: aux + host: 192.0.2.2 # IP address or hostname + key: 0 # ID of the Ohmpilot in SolarAPI, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: key + example: + default: 0 + choice: [] + unit: + description: ID of the Ohmpilot in SolarAPI + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/fronius-ohmpilot_0.yaml b/templates/release/en/meter/fronius-ohmpilot_0.yaml deleted file mode 100644 index 47a0293b9a..0000000000 --- a/templates/release/en/meter/fronius-ohmpilot_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Fronius - description: Ohmpilot -render: - - usage: aux - default: | - type: template - template: fronius-ohmpilot - usage: aux - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: fronius-ohmpilot - usage: aux - host: 192.0.2.2 # IP address or hostname - key: 0 # ID of the Ohmpilot in SolarAPI, optional diff --git a/templates/release/en/meter/fronius-primo-gen24-plus.yaml b/templates/release/en/meter/fronius-primo-gen24-plus.yaml new file mode 100644 index 0000000000..b37dd4decf --- /dev/null +++ b/templates/release/en/meter/fronius-primo-gen24-plus.yaml @@ -0,0 +1,105 @@ +template: fronius-gen24 +product: + identifier: fronius-primo-gen24-plus + brand: Fronius + description: Primo GEN24 Plus +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) + - usage: pv + default: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: id + example: + default: 200 + choice: [] + unit: + description: + help: Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximum charge power + help: For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/fronius-smartmeter-via-inverter.yaml b/templates/release/en/meter/fronius-smartmeter-via-inverter.yaml new file mode 100644 index 0000000000..4c5d51fd7b --- /dev/null +++ b/templates/release/en/meter/fronius-smartmeter-via-inverter.yaml @@ -0,0 +1,44 @@ +template: sunspec-meter +product: + identifier: fronius-smartmeter-via-inverter + brand: Fronius + description: Smartmeter (via Inverter) +render: + - usage: grid + default: | + type: template + template: sunspec-meter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-meter + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/fronius-solar-api-v1.yaml b/templates/release/en/meter/fronius-solar-api-v1.yaml new file mode 100644 index 0000000000..6b9ed47cfa --- /dev/null +++ b/templates/release/en/meter/fronius-solar-api-v1.yaml @@ -0,0 +1,109 @@ +template: fronius-solarapi-v1 +product: + identifier: fronius-solar-api-v1 + brand: Fronius + description: Solar API V1 +capabilities: ["battery-control"] +description: | + Solar API should only be used as fallback. Integration via Modbus is preferred. + + Username and password are only required for active battery control. + + **Attention**: Active battery control should only be used if no other settings for time-dependent battery control were made in the inverter configuration under "Energy Management" - "Battery Management", as existing settings will be overwritten. Choose corresponding configuration URI! + +render: + - usage: grid + default: | + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + advanced: | + type: template + template: fronius-solarapi-v1 + usage: grid + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional) + - usage: pv + default: | + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + advanced: | + type: template + template: fronius-solarapi-v1 + usage: pv + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional) + - usage: battery + default: | + type: template + template: fronius-solarapi-v1 + usage: battery + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + advanced: | + type: template + template: fronius-solarapi-v1 + usage: battery + host: 192.0.2.2 # IP address or hostname + user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) + password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) + capacity: 50 # Battery capacity (kWh), optional + batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: customer + choice: [] + unit: + description: Username (for active battery control) + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password (for active battery control) + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: batteryconfiguri + example: + default: /config + choice: ['/config', '/api/config'] + unit: + description: Firmware starting with 1.36.5-1 require /api/config. + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/fronius-solarapi-v1_0.yaml b/templates/release/en/meter/fronius-solarapi-v1_0.yaml deleted file mode 100644 index 5dc2666748..0000000000 --- a/templates/release/en/meter/fronius-solarapi-v1_0.yaml +++ /dev/null @@ -1,58 +0,0 @@ -product: - brand: Fronius - description: Solar API V1 -capabilities: ["battery-control"] -description: | - Solar API should only be used as fallback. Integration via Modbus is preferred. - - Username and password are only required for active battery control. - - **Attention**: Active battery control should only be used if no other settings for time-dependent battery control were made in the inverter configuration under "Energy Management" - "Battery Management", as existing settings will be overwritten. - -render: - - usage: grid - default: | - type: template - template: fronius-solarapi-v1 - usage: grid - host: 192.0.2.2 # IP address or hostname - user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - advanced: | - type: template - template: fronius-solarapi-v1 - usage: grid - host: 192.0.2.2 # IP address or hostname - user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: fronius-solarapi-v1 - usage: pv - host: 192.0.2.2 # IP address or hostname - user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - advanced: | - type: template - template: fronius-solarapi-v1 - usage: pv - host: 192.0.2.2 # IP address or hostname - user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - - usage: battery - default: | - type: template - template: fronius-solarapi-v1 - usage: battery - host: 192.0.2.2 # IP address or hostname - user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - advanced: | - type: template - template: fronius-solarapi-v1 - usage: battery - host: 192.0.2.2 # IP address or hostname - user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) - password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/fronius-symo-gen24-plus.yaml b/templates/release/en/meter/fronius-symo-gen24-plus.yaml new file mode 100644 index 0000000000..9a31470159 --- /dev/null +++ b/templates/release/en/meter/fronius-symo-gen24-plus.yaml @@ -0,0 +1,105 @@ +template: fronius-gen24 +product: + identifier: fronius-symo-gen24-plus + brand: Fronius + description: Symo GEN24 Plus +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) + - usage: pv + default: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: fronius-gen24 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: id + example: + default: 200 + choice: [] + unit: + description: + help: Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximum charge power + help: For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml b/templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml new file mode 100644 index 0000000000..5083c97a71 --- /dev/null +++ b/templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml @@ -0,0 +1,150 @@ +template: solis-hybrid +product: + identifier: ginlong-solis-hybrid-inverter-rhi-series + brand: Ginlong + description: Solis Hybrid Inverter (RHI series) +render: + - usage: grid + default: | + type: template + template: solis-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: solis-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml b/templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml new file mode 100644 index 0000000000..09352aef15 --- /dev/null +++ b/templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml @@ -0,0 +1,150 @@ +template: solis-hybrid-s +product: + identifier: ginlong-solis-hybrid-inverter-s-series + brand: Ginlong + description: Solis Hybrid Inverter (S Series) +render: + - usage: grid + default: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solis-hybrid-s + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/ginlong-solis-inverter.yaml b/templates/release/en/meter/ginlong-solis-inverter.yaml new file mode 100644 index 0000000000..92f207ca67 --- /dev/null +++ b/templates/release/en/meter/ginlong-solis-inverter.yaml @@ -0,0 +1,61 @@ +template: solis +product: + identifier: ginlong-solis-inverter + brand: Ginlong + description: Solis Inverter +render: + - usage: grid + default: | + type: template + template: solis + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: solis + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/go-e-controller.yaml b/templates/release/en/meter/go-e-controller.yaml new file mode 100644 index 0000000000..f84a818660 --- /dev/null +++ b/templates/release/en/meter/go-e-controller.yaml @@ -0,0 +1,28 @@ +template: go-e-controller +product: + identifier: go-e-controller + brand: go-e + description: Controller +render: + - usage: grid + default: | + type: template + template: go-e-controller + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: go-e-controller + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/go-e-controller_0.yaml b/templates/release/en/meter/go-e-controller_0.yaml deleted file mode 100644 index 675e63f6d4..0000000000 --- a/templates/release/en/meter/go-e-controller_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: go-e - description: Controller -render: - - usage: grid - default: | - type: template - template: go-e-controller - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: go-e-controller - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/goodwe-dt_0.yaml b/templates/release/en/meter/goodwe-dt_0.yaml deleted file mode 100644 index f4a2cd4b5e..0000000000 --- a/templates/release/en/meter/goodwe-dt_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: GoodWe - description: SDT/DT Inverter -render: - - usage: pv - default: | - type: template - template: goodwe-dt - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml b/templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml new file mode 100644 index 0000000000..773793b710 --- /dev/null +++ b/templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml @@ -0,0 +1,204 @@ +template: goodwe-hybrid +product: + identifier: goodwe-et-eh-bh-bt-hybrid-inverter + brand: GoodWe + description: ET/EH/BH/BT Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: goodwe-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + advanced: | + type: template + template: goodwe-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + - usage: pv + default: | + type: template + template: goodwe-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + advanced: | + type: template + template: goodwe-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: goodwe-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + advanced: | + type: template + template: goodwe-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + battery: 1 # [1, 2] (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip', 'udp'] + unit: + description: + help: + advanced: false + optional: true + - name: battery + example: + default: 1 + choice: ['1', '2'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true + udp: true \ No newline at end of file diff --git a/templates/release/en/meter/goodwe-goodwe-over-wifi.yaml b/templates/release/en/meter/goodwe-goodwe-over-wifi.yaml new file mode 100644 index 0000000000..34fb7ade44 --- /dev/null +++ b/templates/release/en/meter/goodwe-goodwe-over-wifi.yaml @@ -0,0 +1,35 @@ +template: goodwe-wifi +product: + identifier: goodwe-goodwe-over-wifi + brand: GoodWe + description: GoodWe over Wifi +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: goodwe-wifi + usage: grid + uri: # IP address or hostname, HTTP(S) address (optional) + - usage: pv + default: | + type: template + template: goodwe-wifi + usage: pv + uri: # IP address or hostname, HTTP(S) address (optional) + - usage: battery + default: | + type: template + template: goodwe-wifi + usage: battery + uri: # IP address or hostname, HTTP(S) address (optional) +params: + - name: uri + example: + default: + choice: [] + unit: + description: IP address or hostname + help: HTTP(S) address + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/goodwe-hybrid_0.yaml b/templates/release/en/meter/goodwe-hybrid_0.yaml deleted file mode 100644 index 3b2c762ed3..0000000000 --- a/templates/release/en/meter/goodwe-hybrid_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: GoodWe - description: ET/EH/BH/BT Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: goodwe-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - advanced: | - type: template - template: goodwe-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - - usage: pv - default: | - type: template - template: goodwe-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - advanced: | - type: template - template: goodwe-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: goodwe-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - advanced: | - type: template - template: goodwe-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - battery: 1 # [1, 2] (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/goodwe-sdt-dt-inverter.yaml b/templates/release/en/meter/goodwe-sdt-dt-inverter.yaml new file mode 100644 index 0000000000..9780442ace --- /dev/null +++ b/templates/release/en/meter/goodwe-sdt-dt-inverter.yaml @@ -0,0 +1,50 @@ +template: goodwe-dt +product: + identifier: goodwe-sdt-dt-inverter + brand: GoodWe + description: SDT/DT Inverter +render: + - usage: pv + default: | + type: template + template: goodwe-dt + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/goodwe-wifi_0.yaml b/templates/release/en/meter/goodwe-wifi_0.yaml deleted file mode 100644 index 274712a35d..0000000000 --- a/templates/release/en/meter/goodwe-wifi_0.yaml +++ /dev/null @@ -1,23 +0,0 @@ -product: - brand: GoodWe - description: GoodWe over Wifi -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: goodwe-wifi - usage: grid - uri: # IP address or hostname, HTTP(S) address (optional) - - usage: pv - default: | - type: template - template: goodwe-wifi - usage: pv - uri: # IP address or hostname, HTTP(S) address (optional) - - usage: battery - default: | - type: template - template: goodwe-wifi - usage: battery - uri: # IP address or hostname, HTTP(S) address (optional) diff --git a/templates/release/en/meter/growatt-hybrid-inverter.yaml b/templates/release/en/meter/growatt-hybrid-inverter.yaml new file mode 100644 index 0000000000..60bc5252a7 --- /dev/null +++ b/templates/release/en/meter/growatt-hybrid-inverter.yaml @@ -0,0 +1,194 @@ +template: growatt-hybrid +product: + identifier: growatt-hybrid-inverter + brand: Growatt + description: Hybrid Inverter +capabilities: ["battery-control"] +description: | + To use the active battery control, a one-time manual setup is necessary. + The modbus registers `1100, 1101, 1102` need to be set to the values `0, 5947, 0` at the same time (via "write multiple", FC 16). + This can be done by e.g. using the [Modbus CLI](https://github.com/favalex/modbus-cli): `modbus [...] H@1100=0 H@1101=5947 H@1102=0`. + The active battery control uses the first "Battery first" timeslot, so it cannot be used otherwise. + +render: + - usage: grid + default: | + type: template + template: growatt-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: growatt-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: growatt-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/growatt-hybrid-tlxh_0.yaml b/templates/release/en/meter/growatt-hybrid-tlxh_0.yaml deleted file mode 100644 index c380d6c510..0000000000 --- a/templates/release/en/meter/growatt-hybrid-tlxh_0.yaml +++ /dev/null @@ -1,148 +0,0 @@ -product: - brand: Growatt - description: TL-X(H) Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: growatt-hybrid-tlxh - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid-tlxh - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: growatt-hybrid-tlxh - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid-tlxh - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: growatt-hybrid-tlxh - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid-tlxh - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/growatt-hybrid_0.yaml b/templates/release/en/meter/growatt-hybrid_0.yaml deleted file mode 100644 index 07502d8a5a..0000000000 --- a/templates/release/en/meter/growatt-hybrid_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: Growatt - description: Hybrid Inverter -capabilities: ["battery-control"] -description: | - To use the active battery control, a one-time manual setup is necessary. - The modbus registers `1100, 1101, 1102` need to be set to the values `0, 5947, 0` at the same time (via "write multiple", FC 16). - This can be done by e.g. using the [Modbus CLI](https://github.com/favalex/modbus-cli): `modbus [...] H@1100=0 H@1101=5947 H@1102=0`. - The active battery control uses the first "Battery first" timeslot, so it cannot be used otherwise. - -render: - - usage: grid - default: | - type: template - template: growatt-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: growatt-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: growatt-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: growatt-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml b/templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml new file mode 100644 index 0000000000..8ab8d64824 --- /dev/null +++ b/templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml @@ -0,0 +1,188 @@ +template: growatt-hybrid-tlxh +product: + identifier: growatt-tl-x-h-hybrid-inverter + brand: Growatt + description: TL-X(H) Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: growatt-hybrid-tlxh + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid-tlxh + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: growatt-hybrid-tlxh + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid-tlxh + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: growatt-hybrid-tlxh + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: growatt-hybrid-tlxh + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/homematic-ip.yaml b/templates/release/en/meter/homematic-ip.yaml new file mode 100644 index 0000000000..9d382eaff5 --- /dev/null +++ b/templates/release/en/meter/homematic-ip.yaml @@ -0,0 +1,121 @@ +template: homematic +product: + identifier: homematic-ip + brand: Homematic IP + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: homematic + usage: grid + host: 192.0.2.2 # IP address or hostname + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + advanced: | + type: template + template: homematic + usage: grid + host: 192.0.2.2 # IP address or hostname + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + - usage: pv + default: | + type: template + template: homematic + usage: pv + host: 192.0.2.2 # IP address or hostname + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + advanced: | + type: template + template: homematic + usage: pv + host: 192.0.2.2 # IP address or hostname + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + - usage: charge + default: | + type: template + template: homematic + usage: charge + host: 192.0.2.2 # IP address or hostname + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + advanced: | + type: template + template: homematic + usage: charge + host: 192.0.2.2 # IP address or hostname + device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: device + example: 0001EE89AAD848 + default: + choice: [] + unit: + description: Device address/Serial number + help: Homematic device id like shown in the CCU web user interface. + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: meterchannel + example: + default: 6 + choice: [] + unit: + description: Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1) + help: Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: XML-RPC api cache duration - Default 1s. (valid units are s,m,h) + help: In case of duty cycle problems try a cache setting of 30s. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/homematic_0.yaml b/templates/release/en/meter/homematic_0.yaml deleted file mode 100644 index 812c5e1223..0000000000 --- a/templates/release/en/meter/homematic_0.yaml +++ /dev/null @@ -1,64 +0,0 @@ -product: - brand: Homematic IP - group: Switchable sockets -render: - - usage: grid - default: | - type: template - template: homematic - usage: grid - host: 192.0.2.2 # IP address or hostname - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - advanced: | - type: template - template: homematic - usage: grid - host: 192.0.2.2 # IP address or hostname - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) - - usage: pv - default: | - type: template - template: homematic - usage: pv - host: 192.0.2.2 # IP address or hostname - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - advanced: | - type: template - template: homematic - usage: pv - host: 192.0.2.2 # IP address or hostname - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) - - usage: charge - default: | - type: template - template: homematic - usage: charge - host: 192.0.2.2 # IP address or hostname - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - advanced: | - type: template - template: homematic - usage: charge - host: 192.0.2.2 # IP address or hostname - device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) diff --git a/templates/release/en/meter/homewizard-kwh-meter.yaml b/templates/release/en/meter/homewizard-kwh-meter.yaml new file mode 100644 index 0000000000..79f94ccfab --- /dev/null +++ b/templates/release/en/meter/homewizard-kwh-meter.yaml @@ -0,0 +1,28 @@ +template: homewizard-kwh +product: + identifier: homewizard-kwh-meter + brand: HomeWizard + description: kWh Meter +render: + - usage: pv + default: | + type: template + template: homewizard-kwh + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: charge + default: | + type: template + template: homewizard-kwh + usage: charge + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/homewizard-kwh_0.yaml b/templates/release/en/meter/homewizard-kwh_0.yaml deleted file mode 100644 index 8836bf7823..0000000000 --- a/templates/release/en/meter/homewizard-kwh_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: HomeWizard - description: kWh Meter -render: - - usage: pv - default: | - type: template - template: homewizard-kwh - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: charge - default: | - type: template - template: homewizard-kwh - usage: charge - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/homewizard-wi-fi-p1-meter.yaml b/templates/release/en/meter/homewizard-wi-fi-p1-meter.yaml new file mode 100644 index 0000000000..8dd5d424d5 --- /dev/null +++ b/templates/release/en/meter/homewizard-wi-fi-p1-meter.yaml @@ -0,0 +1,22 @@ +template: homewizard +product: + identifier: homewizard-wi-fi-p1-meter + brand: HomeWizard + description: Wi-Fi P1 Meter +render: + - usage: grid + default: | + type: template + template: homewizard + usage: grid + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/homewizard_0.yaml b/templates/release/en/meter/homewizard_0.yaml deleted file mode 100644 index 90e207dbd5..0000000000 --- a/templates/release/en/meter/homewizard_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: HomeWizard - description: Wi-Fi P1 Meter -render: - - usage: grid - default: | - type: template - template: homewizard - usage: grid - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/hoymiles-ahoydtu_0.yaml b/templates/release/en/meter/hoymiles-ahoydtu_0.yaml deleted file mode 100644 index e2f3bfff59..0000000000 --- a/templates/release/en/meter/hoymiles-ahoydtu_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: Hoymiles - description: HM & HMS Series (via AhoyDTU) -render: - - usage: pv - default: | - type: template - template: hoymiles-ahoydtu - usage: pv - host: 192.0.2.2 # IP address or hostname - id: 0 # Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID], optional diff --git a/templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml b/templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml new file mode 100644 index 0000000000..15971602c5 --- /dev/null +++ b/templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml @@ -0,0 +1,32 @@ +template: hoymiles-ahoydtu +product: + identifier: hoymiles-hm-and-hms-series-via-ahoydtu + brand: Hoymiles + description: HM & HMS Series (via AhoyDTU) +render: + - usage: pv + default: | + type: template + template: hoymiles-ahoydtu + usage: pv + host: 192.0.2.2 # IP address or hostname + id: 0 # Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID], optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: id + example: + default: 0 + choice: [] + unit: + description: 'Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID]' + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml b/templates/release/en/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml new file mode 100644 index 0000000000..317cc1bc10 --- /dev/null +++ b/templates/release/en/meter/hoymiles-hm-and-hms-series-via-opendtu.yaml @@ -0,0 +1,22 @@ +template: hoymiles-opendtu +product: + identifier: hoymiles-hm-and-hms-series-via-opendtu + brand: Hoymiles + description: HM & HMS Series (via OpenDTU) +render: + - usage: pv + default: | + type: template + template: hoymiles-opendtu + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/hoymiles-opendtu_0.yaml b/templates/release/en/meter/hoymiles-opendtu_0.yaml deleted file mode 100644 index 5626635079..0000000000 --- a/templates/release/en/meter/hoymiles-opendtu_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Hoymiles - description: HM & HMS Series (via OpenDTU) -render: - - usage: pv - default: | - type: template - template: hoymiles-opendtu - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/huawei-dongle_0.yaml b/templates/release/en/meter/huawei-dongle_0.yaml deleted file mode 100644 index 6d8dcf604d..0000000000 --- a/templates/release/en/meter/huawei-dongle_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Huawei - description: SUN2000 (SDongle) -description: | - Needs "Modbus/TCP". Activation using "maintenance access" within the communication settings of the inverter. - See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 - -render: - - usage: pv - default: | - type: template - template: huawei-dongle - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional diff --git a/templates/release/en/meter/huawei-emma.yaml b/templates/release/en/meter/huawei-emma.yaml new file mode 100644 index 0000000000..d6cd38e178 --- /dev/null +++ b/templates/release/en/meter/huawei-emma.yaml @@ -0,0 +1,95 @@ +template: huawei-emma +product: + identifier: huawei-emma + brand: Huawei + description: EMMA +render: + - usage: grid + default: | + type: template + template: huawei-emma + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: huawei-emma + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: huawei-emma + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: huawei-emma + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: huawei-emma + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: huawei-emma + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/huawei-emma_0.yaml b/templates/release/en/meter/huawei-emma_0.yaml deleted file mode 100644 index a609847eb2..0000000000 --- a/templates/release/en/meter/huawei-emma_0.yaml +++ /dev/null @@ -1,68 +0,0 @@ -product: - brand: Huawei - description: EMMA -render: - - usage: grid - default: | - type: template - template: huawei-emma - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: huawei-emma - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: huawei-emma - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: huawei-emma - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: huawei-emma - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: huawei-emma - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/huawei-smartlogger.yaml b/templates/release/en/meter/huawei-smartlogger.yaml new file mode 100644 index 0000000000..4c2ebff76e --- /dev/null +++ b/templates/release/en/meter/huawei-smartlogger.yaml @@ -0,0 +1,133 @@ +template: huawei-smartlogger +product: + identifier: huawei-smartlogger + brand: Huawei + description: SmartLogger +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: huawei-smartlogger + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + advanced: | + type: template + template: huawei-smartlogger + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: huawei-smartlogger + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + advanced: | + type: template + template: huawei-smartlogger + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + storageunit: 1 # optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: huawei-smartlogger + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + advanced: | + type: template + template: huawei-smartlogger + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + storageunit: 1 # optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 15s + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/huawei-smartlogger_0.yaml b/templates/release/en/meter/huawei-smartlogger_0.yaml deleted file mode 100644 index 210607213e..0000000000 --- a/templates/release/en/meter/huawei-smartlogger_0.yaml +++ /dev/null @@ -1,79 +0,0 @@ -product: - brand: Huawei - description: SmartLogger -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: huawei-smartlogger - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - advanced: | - type: template - template: huawei-smartlogger - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: huawei-smartlogger - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - advanced: | - type: template - template: huawei-smartlogger - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - storageunit: 1 # optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: huawei-smartlogger - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - advanced: | - type: template - template: huawei-smartlogger - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - storageunit: 1 # optional - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/huawei-sun2000-sdongle.yaml b/templates/release/en/meter/huawei-sun2000-sdongle.yaml new file mode 100644 index 0000000000..2a58eed667 --- /dev/null +++ b/templates/release/en/meter/huawei-sun2000-sdongle.yaml @@ -0,0 +1,47 @@ +template: huawei-dongle +product: + identifier: huawei-sun2000-sdongle + brand: Huawei + description: SUN2000 (SDongle) +description: | + Needs "Modbus/TCP". Activation using "maintenance access" within the communication settings of the inverter. + See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + +render: + - usage: pv + default: | + type: template + template: huawei-dongle + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 15s + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/huawei-sun2000.yaml b/templates/release/en/meter/huawei-sun2000.yaml new file mode 100644 index 0000000000..d7924aaf23 --- /dev/null +++ b/templates/release/en/meter/huawei-sun2000.yaml @@ -0,0 +1,240 @@ +template: huawei-sun2000 +product: + identifier: huawei-sun2000 + brand: Huawei + description: SUN2000 +capabilities: ["battery-control"] +description: | + Grid and Battery require the PowerSensor. + Modbus/TCP requires activation using "maintenance access" within the communication settings of the inverter. + See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + +render: + - usage: grid + default: | + type: template + template: huawei-sun2000 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + advanced: | + type: template + template: huawei-sun2000 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: huawei-sun2000 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + advanced: | + type: template + template: huawei-sun2000 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + storageunit: 1 # optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: huawei-sun2000 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + advanced: | + type: template + template: huawei-sun2000 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 15s # Timeout, optional + storageunit: 1 # optional + maxchargepower: 10000 # Maximum charge power (W), For forced charging of the battery. (optional) + capacity: 50 # Battery capacity (kWh), optional + forceaccharging: false # Inverter cascade, Keep AC charging active to charge the storage from other inverters via AC. Prevents stand-by. (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 15s + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 10000 + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: forceaccharging + example: + default: false + choice: [] + unit: + description: Inverter cascade + help: Keep AC charging active to charge the storage from other inverters via AC. Prevents stand-by. + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/huawei-sun2000_0.yaml b/templates/release/en/meter/huawei-sun2000_0.yaml deleted file mode 100644 index cae3953e4b..0000000000 --- a/templates/release/en/meter/huawei-sun2000_0.yaml +++ /dev/null @@ -1,164 +0,0 @@ -product: - brand: Huawei - description: SUN2000 -capabilities: ["battery-control"] -description: | - Grid and Battery require the PowerSensor. - Modbus/TCP requires activation using "maintenance access" within the communication settings of the inverter. - See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 - -render: - - usage: grid - default: | - type: template - template: huawei-sun2000 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - advanced: | - type: template - template: huawei-sun2000 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: huawei-sun2000 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - advanced: | - type: template - template: huawei-sun2000 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - storageunit: 1 # optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: huawei-sun2000 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - advanced: | - type: template - template: huawei-sun2000 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 15s # Timeout, optional - storageunit: 1 # optional - maxchargepower: 10000 # Maximum charge power (W), For forced charging of the battery. (optional) - capacity: 50 # Battery capacity (kWh), optional - forceaccharging: false # Inverter cascade, Keep AC charging active to charge the storage from other inverters via AC. Prevents stand-by. (optional) diff --git a/templates/release/en/meter/iammeter-wem3080.yaml b/templates/release/en/meter/iammeter-wem3080.yaml new file mode 100644 index 0000000000..fe39602cc3 --- /dev/null +++ b/templates/release/en/meter/iammeter-wem3080.yaml @@ -0,0 +1,38 @@ +template: iammeter +product: + identifier: iammeter-wem3080 + brand: IAMMETER + description: WEM3080 +description: | + 3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. + See https://www.iammeter.com/newsshow/net-energy-metering + +render: + - usage: grid + default: | + type: template + template: iammeter + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: iammeter + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: charge + default: | + type: template + template: iammeter + usage: charge + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml b/templates/release/en/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml new file mode 100644 index 0000000000..60cfc0dcbc --- /dev/null +++ b/templates/release/en/meter/iammeter-wem3080t-wem3046t-wem3050t.yaml @@ -0,0 +1,38 @@ +template: iammeter +product: + identifier: iammeter-wem3080t-wem3046t-wem3050t + brand: IAMMETER + description: WEM3080T/WEM3046T/WEM3050T +description: | + 3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. + See https://www.iammeter.com/newsshow/net-energy-metering + +render: + - usage: grid + default: | + type: template + template: iammeter + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: iammeter + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: charge + default: | + type: template + template: iammeter + usage: charge + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/iammeter_0.yaml b/templates/release/en/meter/iammeter_0.yaml deleted file mode 100644 index e3c36326c9..0000000000 --- a/templates/release/en/meter/iammeter_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: IAMMETER - description: WEM3080T/WEM3046T/WEM3050T -description: | - 3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. - See https://www.iammeter.com/newsshow/net-energy-metering - -render: - - usage: grid - default: | - type: template - template: iammeter - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: iammeter - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: charge - default: | - type: template - template: iammeter - usage: charge - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/iammeter_1.yaml b/templates/release/en/meter/iammeter_1.yaml deleted file mode 100644 index 2a7b54c2a6..0000000000 --- a/templates/release/en/meter/iammeter_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: IAMMETER - description: WEM3080 -description: | - 3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. - See https://www.iammeter.com/newsshow/net-energy-metering - -render: - - usage: grid - default: | - type: template - template: iammeter - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: iammeter - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: charge - default: | - type: template - template: iammeter - usage: charge - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/igen-tech-solarman-logger.yaml b/templates/release/en/meter/igen-tech-solarman-logger.yaml new file mode 100644 index 0000000000..0c1644d82c --- /dev/null +++ b/templates/release/en/meter/igen-tech-solarman-logger.yaml @@ -0,0 +1,42 @@ +template: solarman +product: + identifier: igen-tech-solarman-logger + brand: IGEN Tech + description: Solarman Logger +render: + - usage: pv + default: | + type: template + template: solarman + usage: pv + host: 192.0.2.2 # IP address or hostname + user: admin # Username, e.g. email address, user id, etc. (optional) + password: admin # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: admin + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: admin + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/inepro-pro380-mod.yaml b/templates/release/en/meter/inepro-pro380-mod.yaml new file mode 100644 index 0000000000..66c63aefae --- /dev/null +++ b/templates/release/en/meter/inepro-pro380-mod.yaml @@ -0,0 +1,61 @@ +template: inepro +product: + identifier: inepro-pro380-mod + brand: inepro + description: PRO380-MOD +render: + - usage: grid + default: | + type: template + template: inepro + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: inepro + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/inepro_0.yaml b/templates/release/en/meter/inepro_0.yaml deleted file mode 100644 index a72a94dd1b..0000000000 --- a/templates/release/en/meter/inepro_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: inepro - description: PRO380-MOD -render: - - usage: grid - default: | - type: template - template: inepro - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: inepro - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/iometer.yaml b/templates/release/en/meter/iometer.yaml new file mode 100644 index 0000000000..8d6d1c8b89 --- /dev/null +++ b/templates/release/en/meter/iometer.yaml @@ -0,0 +1,21 @@ +template: iometer +product: + identifier: iometer + brand: IOmeter +render: + - usage: grid + default: | + type: template + template: iometer + usage: grid + host: 192.0.2.2 # IP of your IOmeter +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP of your IOmeter + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/iometer_0.yaml b/templates/release/en/meter/iometer_0.yaml deleted file mode 100644 index ab4bc35581..0000000000 --- a/templates/release/en/meter/iometer_0.yaml +++ /dev/null @@ -1,9 +0,0 @@ -product: - brand: IOmeter -render: - - usage: grid - default: | - type: template - template: iometer - usage: grid - host: 192.0.2.2 # IP of your IOmeter diff --git a/templates/release/en/meter/janitza-b-series.yaml b/templates/release/en/meter/janitza-b-series.yaml new file mode 100644 index 0000000000..471cd33ce3 --- /dev/null +++ b/templates/release/en/meter/janitza-b-series.yaml @@ -0,0 +1,74 @@ +template: janitza +product: + identifier: janitza-b-series + brand: Janitza + description: B series +render: + - usage: grid + default: | + type: template + template: janitza + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: janitza + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/janitza-umg-series.yaml b/templates/release/en/meter/janitza-umg-series.yaml new file mode 100644 index 0000000000..c6c3c47f25 --- /dev/null +++ b/templates/release/en/meter/janitza-umg-series.yaml @@ -0,0 +1,74 @@ +template: janitza +product: + identifier: janitza-umg-series + brand: Janitza + description: UMG series +render: + - usage: grid + default: | + type: template + template: janitza + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: janitza + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/janitza_0.yaml b/templates/release/en/meter/janitza_0.yaml deleted file mode 100644 index 1c8d9b69ff..0000000000 --- a/templates/release/en/meter/janitza_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Janitza - description: B series, UMG series -render: - - usage: grid - default: | - type: template - template: janitza - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: janitza - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/keba-kecontact-e10.yaml b/templates/release/en/meter/keba-kecontact-e10.yaml new file mode 100644 index 0000000000..432af7879f --- /dev/null +++ b/templates/release/en/meter/keba-kecontact-e10.yaml @@ -0,0 +1,33 @@ +template: keba-kecontact +product: + identifier: keba-kecontact-e10 + brand: KEBA + description: KeContact E10 +render: + - usage: grid + default: | + type: template + template: keba-kecontact + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/keba-kecontact_0.yaml b/templates/release/en/meter/keba-kecontact_0.yaml deleted file mode 100644 index 8ac8658939..0000000000 --- a/templates/release/en/meter/keba-kecontact_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: KEBA - description: KeContact E10 -render: - - usage: grid - default: | - type: template - template: keba-kecontact - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml b/templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml new file mode 100644 index 0000000000..fdaed4b63f --- /dev/null +++ b/templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: kostal-energy-meter-c-kem-c + brand: Kostal + description: Energy Meter C (KEM-C) +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml b/templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml new file mode 100644 index 0000000000..a4f8d0cb8f --- /dev/null +++ b/templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: kostal-energy-meter-p-kem-p + brand: Kostal + description: Energy Meter P (KEM-P) +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/kostal-ksem-inverter_0.yaml b/templates/release/en/meter/kostal-ksem-inverter_0.yaml deleted file mode 100644 index 94e1f00784..0000000000 --- a/templates/release/en/meter/kostal-ksem-inverter_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Kostal - description: Smart Energy Meter (via inverter) -description: | - The energy meter must be installed in sensor position 2 (grid connection). Sensor position 1 (House consumption) is not supported. -render: - - usage: grid - default: | - type: template - template: kostal-ksem-inverter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port diff --git a/templates/release/en/meter/kostal-ksem_0.yaml b/templates/release/en/meter/kostal-ksem_0.yaml deleted file mode 100644 index a2d146cf9c..0000000000 --- a/templates/release/en/meter/kostal-ksem_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Kostal - description: Smart Energy Meter -render: - - usage: grid - default: | - type: template - template: kostal-ksem - usage: grid - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/kostal-piko-ba.yaml b/templates/release/en/meter/kostal-piko-ba.yaml new file mode 100644 index 0000000000..b858ce2e50 --- /dev/null +++ b/templates/release/en/meter/kostal-piko-ba.yaml @@ -0,0 +1,28 @@ +template: kostal-piko-pv +product: + identifier: kostal-piko-ba + brand: Kostal + description: Piko BA +render: + - usage: grid + default: | + type: template + template: kostal-piko-pv + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: kostal-piko-pv + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/kostal-piko-hybrid.yaml b/templates/release/en/meter/kostal-piko-hybrid.yaml new file mode 100644 index 0000000000..6afda4ee67 --- /dev/null +++ b/templates/release/en/meter/kostal-piko-hybrid.yaml @@ -0,0 +1,59 @@ +template: kostal-piko-hybrid +product: + identifier: kostal-piko-hybrid + brand: Kostal + description: Piko Hybrid +render: + - usage: grid + default: | + type: template + template: kostal-piko-hybrid + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: kostal-piko-hybrid + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: kostal-piko-hybrid + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: kostal-piko-hybrid + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: battery + default: | + type: template + template: kostal-piko-hybrid + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: kostal-piko-hybrid + usage: battery + host: 192.0.2.2 # IP address or hostname + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/kostal-piko-hybrid_0.yaml b/templates/release/en/meter/kostal-piko-hybrid_0.yaml deleted file mode 100644 index 5966a3f24c..0000000000 --- a/templates/release/en/meter/kostal-piko-hybrid_0.yaml +++ /dev/null @@ -1,38 +0,0 @@ -product: - brand: Kostal - description: Piko Hybrid -render: - - usage: grid - default: | - type: template - template: kostal-piko-hybrid - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: kostal-piko-hybrid - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: kostal-piko-hybrid - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: kostal-piko-hybrid - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: battery - default: | - type: template - template: kostal-piko-hybrid - usage: battery - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: kostal-piko-hybrid - usage: battery - host: 192.0.2.2 # IP address or hostname - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/kostal-piko-legacy.yaml b/templates/release/en/meter/kostal-piko-legacy.yaml new file mode 100644 index 0000000000..280f85e0e7 --- /dev/null +++ b/templates/release/en/meter/kostal-piko-legacy.yaml @@ -0,0 +1,42 @@ +template: kostal-piko-legacy +product: + identifier: kostal-piko-legacy + brand: Kostal + description: Piko (legacy) +render: + - usage: pv + default: | + type: template + template: kostal-piko-legacy + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/kostal-piko-legacy_0.yaml b/templates/release/en/meter/kostal-piko-legacy_0.yaml deleted file mode 100644 index 20cdddb4b3..0000000000 --- a/templates/release/en/meter/kostal-piko-legacy_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Kostal - description: Piko (legacy) -render: - - usage: pv - default: | - type: template - template: kostal-piko-legacy - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros diff --git a/templates/release/en/meter/kostal-piko-mp-plus.yaml b/templates/release/en/meter/kostal-piko-mp-plus.yaml new file mode 100644 index 0000000000..61e2452f79 --- /dev/null +++ b/templates/release/en/meter/kostal-piko-mp-plus.yaml @@ -0,0 +1,22 @@ +template: kostal-piko-mp-plus +product: + identifier: kostal-piko-mp-plus + brand: Kostal + description: Piko MP Plus +render: + - usage: pv + default: | + type: template + template: kostal-piko-mp-plus + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/kostal-piko-mp-plus_0.yaml b/templates/release/en/meter/kostal-piko-mp-plus_0.yaml deleted file mode 100644 index 74ff42473f..0000000000 --- a/templates/release/en/meter/kostal-piko-mp-plus_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Kostal - description: Piko MP Plus -render: - - usage: pv - default: | - type: template - template: kostal-piko-mp-plus - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/kostal-piko-mp-plus_1.yaml b/templates/release/en/meter/kostal-piko-mp-plus_1.yaml deleted file mode 100644 index c609239b45..0000000000 --- a/templates/release/en/meter/kostal-piko-mp-plus_1.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: Steca - description: coolcept fleX -render: - - usage: pv - default: | - type: template - template: kostal-piko-mp-plus - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/kostal-piko-pv_0.yaml b/templates/release/en/meter/kostal-piko-pv_0.yaml deleted file mode 100644 index e8f3051863..0000000000 --- a/templates/release/en/meter/kostal-piko-pv_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Kostal - description: Piko, Piko BA -render: - - usage: grid - default: | - type: template - template: kostal-piko-pv - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: kostal-piko-pv - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/kostal-piko.yaml b/templates/release/en/meter/kostal-piko.yaml new file mode 100644 index 0000000000..b7a8f91dce --- /dev/null +++ b/templates/release/en/meter/kostal-piko.yaml @@ -0,0 +1,28 @@ +template: kostal-piko-pv +product: + identifier: kostal-piko + brand: Kostal + description: Piko +render: + - usage: grid + default: | + type: template + template: kostal-piko-pv + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: kostal-piko-pv + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/kostal-plenticore-gen2_0.yaml b/templates/release/en/meter/kostal-plenticore-gen2_0.yaml deleted file mode 100644 index a30b9e2d4b..0000000000 --- a/templates/release/en/meter/kostal-plenticore-gen2_0.yaml +++ /dev/null @@ -1,59 +0,0 @@ -product: - brand: Kostal - description: Plenticore Hybrid, incl. grid charging of the house battery -capabilities: ["battery-control"] -description: | - Only a single system may access the inverter! For active battery control, the feature external battery control via modbus must be activated using installer access. **_Can basically be used for various inverter generations (G1/G2/G3)._** - **The function for grid charging the battery is available using this template, but is currently incompatible with some older inverters - _test carefully_!** - _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ - -render: - - usage: pv - default: | - type: template - template: kostal-plenticore-gen2 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore-gen2 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Endianness (Little/Big), [little, big] (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: kostal-plenticore-gen2 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore-gen2 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Endianness (Little/Big), [little, big] (optional) - capacity: 50 # Battery capacity (kWh), optional - maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) - watchdog: 60s # optional diff --git a/templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml b/templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml new file mode 100644 index 0000000000..7a44f32845 --- /dev/null +++ b/templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml @@ -0,0 +1,122 @@ +template: kostal-plenticore-gen2 +product: + identifier: kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery + brand: Kostal + description: Plenticore Hybrid, incl. grid charging of the house battery +capabilities: ["battery-control"] +description: | + Only a single system may access the inverter! For active battery control, the feature external battery control via modbus must be activated using installer access. **_Can basically be used for various inverter generations (G1/G2/G3)._** + **The function for grid charging the battery is available using this template, but is currently incompatible with some older inverters - _test carefully_!** + _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + +render: + - usage: pv + default: | + type: template + template: kostal-plenticore-gen2 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore-gen2 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Endianness (Little/Big), [little, big] (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: kostal-plenticore-gen2 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore-gen2 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Endianness (Little/Big), [little, big] (optional) + capacity: 50 # Battery capacity (kWh), optional + maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: endianness + example: + default: little + choice: ['little', 'big'] + unit: + description: Endianness (Little/Big) + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximum charge power + help: For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/kostal-plenticore-hybrid.yaml b/templates/release/en/meter/kostal-plenticore-hybrid.yaml new file mode 100644 index 0000000000..0e3776852c --- /dev/null +++ b/templates/release/en/meter/kostal-plenticore-hybrid.yaml @@ -0,0 +1,133 @@ +template: kostal-plenticore +product: + identifier: kostal-plenticore-hybrid + brand: Kostal + description: Plenticore Hybrid +capabilities: ["battery-control"] +description: | + Only a single system may access the inverter! For active battery control the function external battery control via Modbus must be activated using installer access. + **Grid charging is not available!** _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + +render: + - usage: pv + default: | + type: template + template: kostal-plenticore + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore + usage: pv + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Endianness (Little/Big), [little, big] (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: kostal-plenticore + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + advanced: | + type: template + template: kostal-plenticore + usage: battery + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port + endianness: little # Endianness (Little/Big), [little, big] (optional) + capacity: 50 # Battery capacity (kWh), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: endianness + example: + default: little + choice: ['little', 'big'] + unit: + description: Endianness (Little/Big) + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/kostal-plenticore_0.yaml b/templates/release/en/meter/kostal-plenticore_0.yaml deleted file mode 100644 index 498bea5138..0000000000 --- a/templates/release/en/meter/kostal-plenticore_0.yaml +++ /dev/null @@ -1,61 +0,0 @@ -product: - brand: Kostal - description: Plenticore Hybrid -capabilities: ["battery-control"] -description: | - Only a single system may access the inverter! For active battery control the function external battery control via Modbus must be activated using installer access. - **Grid charging is not available!** _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ - -render: - - usage: pv - default: | - type: template - template: kostal-plenticore - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore - usage: pv - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Endianness (Little/Big), [little, big] (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: kostal-plenticore - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - advanced: | - type: template - template: kostal-plenticore - usage: battery - - # Modbus TCP - modbus: tcpip - id: 71 - host: 192.0.2.2 # Hostname - port: 1502 # Port - endianness: little # Endianness (Little/Big), [little, big] (optional) - capacity: 50 # Battery capacity (kWh), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional diff --git a/templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml b/templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml new file mode 100644 index 0000000000..8edeae7571 --- /dev/null +++ b/templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml @@ -0,0 +1,35 @@ +template: kostal-ksem-inverter +product: + identifier: kostal-smart-energy-meter-via-inverter + brand: Kostal + description: Smart Energy Meter (via inverter) +description: | + The energy meter must be installed in sensor position 2 (grid connection). Sensor position 1 (House consumption) is not supported. +render: + - usage: grid + default: | + type: template + template: kostal-ksem-inverter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 1502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 1502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/kostal-smart-energy-meter.yaml b/templates/release/en/meter/kostal-smart-energy-meter.yaml new file mode 100644 index 0000000000..63cad3375d --- /dev/null +++ b/templates/release/en/meter/kostal-smart-energy-meter.yaml @@ -0,0 +1,33 @@ +template: kostal-ksem +product: + identifier: kostal-smart-energy-meter + brand: Kostal + description: Smart Energy Meter +render: + - usage: grid + default: | + type: template + template: kostal-ksem + usage: grid + + # Modbus TCP + modbus: tcpip + id: 71 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 71 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/lg-ess-home-15.yaml b/templates/release/en/meter/lg-ess-home-15.yaml new file mode 100644 index 0000000000..2be099f596 --- /dev/null +++ b/templates/release/en/meter/lg-ess-home-15.yaml @@ -0,0 +1,111 @@ +template: lg-ess-home-15 +product: + identifier: lg-ess-home-15 + brand: LG + description: ESS Home 15 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: lg-ess-home-15 + usage: grid + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + advanced: | + type: template + template: lg-ess-home-15 + usage: grid + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: lg-ess-home-15 + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + advanced: | + type: template + template: lg-ess-home-15 + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: battery + default: | + type: template + template: lg-ess-home-15 + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + advanced: | + type: template + template: lg-ess-home-15 + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + capacity: 50 # Battery capacity (kWh), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. + advanced: false + optional: true + - name: registration + example: DE200... + default: + choice: [] + unit: + description: + help: Registration id of the LG ESS HOME inverter. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/lg-ess-home-15_0.yaml b/templates/release/en/meter/lg-ess-home-15_0.yaml deleted file mode 100644 index b7ad9634b0..0000000000 --- a/templates/release/en/meter/lg-ess-home-15_0.yaml +++ /dev/null @@ -1,54 +0,0 @@ -product: - brand: LG - description: ESS Home 15 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: lg-ess-home-15 - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - advanced: | - type: template - template: lg-ess-home-15 - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: lg-ess-home-15 - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - advanced: | - type: template - template: lg-ess-home-15 - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: battery - default: | - type: template - template: lg-ess-home-15 - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - advanced: | - type: template - template: lg-ess-home-15 - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - capacity: 50 # Battery capacity (kWh), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/lg-ess-home-8-10.yaml b/templates/release/en/meter/lg-ess-home-8-10.yaml new file mode 100644 index 0000000000..77ffb0ea9e --- /dev/null +++ b/templates/release/en/meter/lg-ess-home-8-10.yaml @@ -0,0 +1,114 @@ +template: lg-ess-home-8-10 +product: + identifier: lg-ess-home-8-10 + brand: LG + description: ESS Home 8/10 +capabilities: ["battery-control"] +description: | + To use the battery control, a firmware version greater than or equal to 10.05.7433 / R2155 is required + +render: + - usage: grid + default: | + type: template + template: lg-ess-home-8-10 + usage: grid + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + advanced: | + type: template + template: lg-ess-home-8-10 + usage: grid + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: lg-ess-home-8-10 + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + advanced: | + type: template + template: lg-ess-home-8-10 + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: battery + default: | + type: template + template: lg-ess-home-8-10 + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + advanced: | + type: template + template: lg-ess-home-8-10 + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) + registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + capacity: 50 # Battery capacity (kWh), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. + advanced: false + optional: true + - name: registration + example: DE200... + default: + choice: [] + unit: + description: + help: Registration id of the LG ESS HOME inverter. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/lg-ess-home-8-10_0.yaml b/templates/release/en/meter/lg-ess-home-8-10_0.yaml deleted file mode 100644 index 91bad08985..0000000000 --- a/templates/release/en/meter/lg-ess-home-8-10_0.yaml +++ /dev/null @@ -1,57 +0,0 @@ -product: - brand: LG - description: ESS Home 8/10 -capabilities: ["battery-control"] -description: | - To use the battery control, a firmware version greater than or equal to 10.05.7433 / R2155 is required - -render: - - usage: grid - default: | - type: template - template: lg-ess-home-8-10 - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - advanced: | - type: template - template: lg-ess-home-8-10 - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: lg-ess-home-8-10 - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - advanced: | - type: template - template: lg-ess-home-8-10 - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: battery - default: | - type: template - template: lg-ess-home-8-10 - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - advanced: | - type: template - template: lg-ess-home-8-10 - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - capacity: 50 # Battery capacity (kWh), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/loxone-miniserver.yaml b/templates/release/en/meter/loxone-miniserver.yaml new file mode 100644 index 0000000000..43db43732b --- /dev/null +++ b/templates/release/en/meter/loxone-miniserver.yaml @@ -0,0 +1,92 @@ +template: loxone +product: + identifier: loxone-miniserver + brand: Loxone + description: Miniserver +render: + - usage: grid + default: | + type: template + template: loxone + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterblock: # Meter block, Name from Loxone Config + socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) + - usage: pv + default: | + type: template + template: loxone + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterblock: # Meter block, Name from Loxone Config + socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) + - usage: battery + default: | + type: template + template: loxone + usage: battery + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterblock: # Meter block, Name from Loxone Config + socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) + - usage: charge + default: | + type: template + template: loxone + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + meterblock: # Meter block, Name from Loxone Config + socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: meterblock + example: + default: + choice: [] + unit: + description: Meter block + help: Name from Loxone Config + advanced: false + optional: false + - name: socblock + example: + default: + choice: [] + unit: + description: Function block name for state of charge + help: Name from Loxone Config, only for battery + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/loxone_0.yaml b/templates/release/en/meter/loxone_0.yaml deleted file mode 100644 index 1f06e42555..0000000000 --- a/templates/release/en/meter/loxone_0.yaml +++ /dev/null @@ -1,44 +0,0 @@ -product: - brand: Loxone - description: Miniserver -render: - - usage: grid - default: | - type: template - template: loxone - usage: grid - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterblock: # Meter block, Name from Loxone Config - socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) - - usage: pv - default: | - type: template - template: loxone - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterblock: # Meter block, Name from Loxone Config - socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) - - usage: battery - default: | - type: template - template: loxone - usage: battery - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterblock: # Meter block, Name from Loxone Config - socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) - - usage: charge - default: | - type: template - template: loxone - usage: charge - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - meterblock: # Meter block, Name from Loxone Config - socblock: # Function block name for state of charge, Name from Loxone Config, only for battery (optional) diff --git a/templates/release/en/meter/m-tec-energy-butler-gen2.yaml b/templates/release/en/meter/m-tec-energy-butler-gen2.yaml new file mode 100644 index 0000000000..d4e337c9b1 --- /dev/null +++ b/templates/release/en/meter/m-tec-energy-butler-gen2.yaml @@ -0,0 +1,79 @@ +template: mtec-eb-gen2 +product: + identifier: m-tec-energy-butler-gen2 + brand: M-TEC + description: Energy Butler GEN2 +render: + - usage: grid + default: | + type: template + template: mtec-eb-gen2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: mtec-eb-gen2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: mtec-eb-gen2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/m-tec-energy-butler-gen3.yaml b/templates/release/en/meter/m-tec-energy-butler-gen3.yaml new file mode 100644 index 0000000000..0d3280a1ff --- /dev/null +++ b/templates/release/en/meter/m-tec-energy-butler-gen3.yaml @@ -0,0 +1,178 @@ +template: mtec-eb-gen3 +product: + identifier: m-tec-energy-butler-gen3 + brand: M-TEC + description: Energy Butler GEN3 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: mtec-eb-gen3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: mtec-eb-gen3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: mtec-eb-gen3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: mtec-eb-gen3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: mtec-eb-gen3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: mtec-eb-gen3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 255 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 255 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 255 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/marstek-venus-battery-storage.yaml b/templates/release/en/meter/marstek-venus-battery-storage.yaml new file mode 100644 index 0000000000..a15f840331 --- /dev/null +++ b/templates/release/en/meter/marstek-venus-battery-storage.yaml @@ -0,0 +1,112 @@ +template: marstek-venus +product: + identifier: marstek-venus-battery-storage + brand: Marstek + description: Venus Battery Storage +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: marstek-venus + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 5.12 # Battery capacity (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) + advanced: | + type: template + template: marstek-venus + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 5.12 # Battery capacity (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) + minsoc: 11 # Venus can only be discharged down to 11%. (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 100 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxchargepower: 2500 # Charge power in watts for Charge mode. 2500W is the maximum for Venus. (W), For forced charging of the battery. (optional) + work_mode_normal: 1 # Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode., optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: 5.12 + choice: [] + unit: kWh + description: Battery capacity + help: Venus-E 5.12 kWh, Venus-C 2.56 kWh + advanced: false + optional: true + - name: minsoc + example: 25 + default: 11 + choice: [] + unit: '%' + description: Venus can only be discharged down to 11%. + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 100 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxchargepower + example: + default: 2500 + choice: [] + unit: W + description: Charge power in watts for Charge mode. 2500W is the maximum for Venus. + help: For forced charging of the battery. + advanced: true + optional: true + - name: work_mode_normal + example: + default: 1 + choice: [] + unit: + description: Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode. + help: + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/marstek-venus_0.yaml b/templates/release/en/meter/marstek-venus_0.yaml deleted file mode 100644 index 62b9727b72..0000000000 --- a/templates/release/en/meter/marstek-venus_0.yaml +++ /dev/null @@ -1,46 +0,0 @@ -product: - brand: Marstek - description: Venus Battery Storage -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: marstek-venus - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 5.12 # Battery capacity (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - advanced: | - type: template - template: marstek-venus - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 5.12 # Battery capacity (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - minsoc: 11 # Venus can only be discharged down to 11%. (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 100 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxchargepower: 2500 # Charge power in watts for Charge mode. 2500W is the maximum for Venus. (W), For forced charging of the battery. (optional) - work_mode_normal: 1 # Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode., optional diff --git a/templates/release/en/meter/mhendriks-p1-dongle.yaml b/templates/release/en/meter/mhendriks-p1-dongle.yaml new file mode 100644 index 0000000000..51eb98792e --- /dev/null +++ b/templates/release/en/meter/mhendriks-p1-dongle.yaml @@ -0,0 +1,37 @@ +template: slimmelezer +product: + identifier: mhendriks-p1-dongle + brand: mhendriks + description: P1 dongle +render: + - usage: grid + default: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP address or hostname + scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: scale + example: 1 | 10 | 100 | 1000 + default: 1000 + choice: [] + unit: + description: Scale factor + help: Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/mpm3pm_0.yaml b/templates/release/en/meter/mpm3pm_0.yaml deleted file mode 100644 index e3d65077f7..0000000000 --- a/templates/release/en/meter/mpm3pm_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Bernecker Engineering - description: MPM3PM -render: - - usage: grid - default: | - type: template - template: mpm3pm - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: mpm3pm - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/mtec-eb-gen2_0.yaml b/templates/release/en/meter/mtec-eb-gen2_0.yaml deleted file mode 100644 index de33af6124..0000000000 --- a/templates/release/en/meter/mtec-eb-gen2_0.yaml +++ /dev/null @@ -1,58 +0,0 @@ -product: - brand: M-TEC - description: Energy Butler GEN2 -render: - - usage: grid - default: | - type: template - template: mtec-eb-gen2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: mtec-eb-gen2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: mtec-eb-gen2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/mtec-eb-gen3_0.yaml b/templates/release/en/meter/mtec-eb-gen3_0.yaml deleted file mode 100644 index 30c5bf1470..0000000000 --- a/templates/release/en/meter/mtec-eb-gen3_0.yaml +++ /dev/null @@ -1,147 +0,0 @@ -product: - brand: M-TEC - description: Energy Butler GEN3 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: mtec-eb-gen3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: mtec-eb-gen3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: mtec-eb-gen3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: mtec-eb-gen3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: mtec-eb-gen3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: mtec-eb-gen3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 255 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 255 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/my-pv-ac-elwa-2.yaml b/templates/release/en/meter/my-pv-ac-elwa-2.yaml new file mode 100644 index 0000000000..661ac9bd83 --- /dev/null +++ b/templates/release/en/meter/my-pv-ac-elwa-2.yaml @@ -0,0 +1,22 @@ +template: ac-elwa-2 +product: + identifier: my-pv-ac-elwa-2 + brand: my-PV + description: AC ELWA 2 +render: + - usage: aux + default: | + type: template + template: ac-elwa-2 + usage: aux + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/my-pv-ac-elwa-e.yaml b/templates/release/en/meter/my-pv-ac-elwa-e.yaml new file mode 100644 index 0000000000..105444b95d --- /dev/null +++ b/templates/release/en/meter/my-pv-ac-elwa-e.yaml @@ -0,0 +1,22 @@ +template: ac-elwa-e +product: + identifier: my-pv-ac-elwa-e + brand: my-PV + description: AC ELWA-E +render: + - usage: aux + default: | + type: template + template: ac-elwa-e + usage: aux + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/my-pv-ac-thor.yaml b/templates/release/en/meter/my-pv-ac-thor.yaml new file mode 100644 index 0000000000..7b831c3963 --- /dev/null +++ b/templates/release/en/meter/my-pv-ac-thor.yaml @@ -0,0 +1,22 @@ +template: thor +product: + identifier: my-pv-ac-thor + brand: my-PV + description: AC•THOR +render: + - usage: aux + default: | + type: template + template: thor + usage: aux + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/my-pv-wifi-meter.yaml b/templates/release/en/meter/my-pv-wifi-meter.yaml new file mode 100644 index 0000000000..01129aa7e8 --- /dev/null +++ b/templates/release/en/meter/my-pv-wifi-meter.yaml @@ -0,0 +1,33 @@ +template: mypv-wifi-meter +product: + identifier: my-pv-wifi-meter + brand: my-PV + description: WiFi Meter +render: + - usage: grid + default: | + type: template + template: mypv-wifi-meter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/mypv-wifi-meter_0.yaml b/templates/release/en/meter/mypv-wifi-meter_0.yaml deleted file mode 100644 index f8d60b48a0..0000000000 --- a/templates/release/en/meter/mypv-wifi-meter_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: my-PV - description: WiFi Meter -render: - - usage: grid - default: | - type: template - template: mypv-wifi-meter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/mystrom-switch.yaml b/templates/release/en/meter/mystrom-switch.yaml new file mode 100644 index 0000000000..b150de8560 --- /dev/null +++ b/templates/release/en/meter/mystrom-switch.yaml @@ -0,0 +1,29 @@ +template: mystrom +product: + identifier: mystrom-switch + brand: myStrom + description: Switch + group: Switchable sockets +render: + - usage: pv + default: | + type: template + template: mystrom + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: charge + default: | + type: template + template: mystrom + usage: charge + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/mystrom_0.yaml b/templates/release/en/meter/mystrom_0.yaml deleted file mode 100644 index 3e146f8e1f..0000000000 --- a/templates/release/en/meter/mystrom_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: myStrom - description: Switch - group: Switchable sockets -render: - - usage: pv - default: | - type: template - template: mystrom - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: charge - default: | - type: template - template: mystrom - usage: charge - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/openems.yaml b/templates/release/en/meter/openems.yaml new file mode 100644 index 0000000000..806081d47f --- /dev/null +++ b/templates/release/en/meter/openems.yaml @@ -0,0 +1,104 @@ +template: openems +product: + identifier: openems + brand: OpenEMS +capabilities: ["battery-control"] +description: | + A commercial license is required for FEMS FENECON systems for active battery control. + +render: + - usage: grid + default: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: openems + usage: grid + host: 192.0.2.2 # IP address or hostname + password: user # Password, Use single quotes in case of leading zeros (optional) + - usage: pv + default: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: openems + usage: pv + host: 192.0.2.2 # IP address or hostname + password: user # Password, Use single quotes in case of leading zeros (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: openems + usage: battery + host: 192.0.2.2 # IP address or hostname + password: user # Password, Use single quotes in case of leading zeros (optional) + battery: ess0 # controllable battery component (optional) + watchdog: 60s # adjusted to the API timeout (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: password + example: + default: user + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true + - name: battery + example: ess0 + default: + choice: [] + unit: + description: + help: controllable battery component + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: adjusted to the API timeout + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/openems_0.yaml b/templates/release/en/meter/openems_0.yaml deleted file mode 100644 index 643f372ad8..0000000000 --- a/templates/release/en/meter/openems_0.yaml +++ /dev/null @@ -1,47 +0,0 @@ -product: - brand: OpenEMS -capabilities: ["battery-control"] -description: | - A commercial license is required for FEMS FENECON systems for active battery control. - -render: - - usage: grid - default: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP address or hostname - password: user # Password, Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP address or hostname - password: user # Password, Use single quotes in case of leading zeros (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP address or hostname - password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/openems_1.yaml b/templates/release/en/meter/openems_1.yaml deleted file mode 100644 index fc02fd8c4a..0000000000 --- a/templates/release/en/meter/openems_1.yaml +++ /dev/null @@ -1,47 +0,0 @@ -product: - brand: FENECON -capabilities: ["battery-control"] -description: | - A commercial license is required for FEMS FENECON systems for active battery control. - -render: - - usage: grid - default: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: openems - usage: grid - host: 192.0.2.2 # IP address or hostname - password: user # Password, Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: openems - usage: pv - host: 192.0.2.2 # IP address or hostname - password: user # Password, Use single quotes in case of leading zeros (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: openems - usage: battery - host: 192.0.2.2 # IP address or hostname - password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/orno-or-we-516.yaml b/templates/release/en/meter/orno-or-we-516.yaml new file mode 100644 index 0000000000..e5828f01eb --- /dev/null +++ b/templates/release/en/meter/orno-or-we-516.yaml @@ -0,0 +1,61 @@ +template: orno +product: + identifier: orno-or-we-516 + brand: ORNO + description: OR-WE-516 +render: + - usage: grid + default: | + type: template + template: orno + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: orno + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/orno-or-we-517.yaml b/templates/release/en/meter/orno-or-we-517.yaml new file mode 100644 index 0000000000..84efc46ba1 --- /dev/null +++ b/templates/release/en/meter/orno-or-we-517.yaml @@ -0,0 +1,61 @@ +template: orno +product: + identifier: orno-or-we-517 + brand: ORNO + description: OR-WE-517 +render: + - usage: grid + default: | + type: template + template: orno + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: orno + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8E1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8E1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/orno_0.yaml b/templates/release/en/meter/orno_0.yaml deleted file mode 100644 index 775ad5c2db..0000000000 --- a/templates/release/en/meter/orno_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Orno - description: OR-WE-516, OR-WE-517 -render: - - usage: grid - default: | - type: template - template: orno - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: orno - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8E1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/p1monitor-p1-monitor.yaml b/templates/release/en/meter/p1monitor-p1-monitor.yaml new file mode 100644 index 0000000000..734a4d8f71 --- /dev/null +++ b/templates/release/en/meter/p1monitor-p1-monitor.yaml @@ -0,0 +1,22 @@ +template: p1monitor +product: + identifier: p1monitor-p1-monitor + brand: P1Monitor + description: P1 Monitor +render: + - usage: grid + default: | + type: template + template: p1monitor + usage: grid + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/p1monitor_0.yaml b/templates/release/en/meter/p1monitor_0.yaml deleted file mode 100644 index 0d3c458f30..0000000000 --- a/templates/release/en/meter/p1monitor_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: P1Monitor - description: P1 Monitor -render: - - usage: grid - default: | - type: template - template: p1monitor - usage: grid - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/plexlog.yaml b/templates/release/en/meter/plexlog.yaml new file mode 100644 index 0000000000..cf9e287fb5 --- /dev/null +++ b/templates/release/en/meter/plexlog.yaml @@ -0,0 +1,97 @@ +template: plexlog +product: + identifier: plexlog + description: Plexlog +description: | + The values are updated approximately every 15 seconds, hence the evcc `interval` should not be less than 30 seconds. + +render: + - usage: grid + default: | + type: template + template: plexlog + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + advanced: | + type: template + template: plexlog + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + - usage: pv + default: | + type: template + template: plexlog + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + advanced: | + type: template + template: plexlog + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + - usage: battery + default: | + type: template + template: plexlog + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + advanced: | + type: template + template: plexlog + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 503 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 503 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/plexlog_0.yaml b/templates/release/en/meter/plexlog_0.yaml deleted file mode 100644 index 981283f065..0000000000 --- a/templates/release/en/meter/plexlog_0.yaml +++ /dev/null @@ -1,70 +0,0 @@ -product: - description: Plexlog -description: | - The values are updated approximately every 15 seconds, hence the evcc `interval` should not be less than 30 seconds. - -render: - - usage: grid - default: | - type: template - template: plexlog - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - advanced: | - type: template - template: plexlog - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - - usage: pv - default: | - type: template - template: plexlog - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - advanced: | - type: template - template: plexlog - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - - usage: battery - default: | - type: template - template: plexlog - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - advanced: | - type: template - template: plexlog - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 503 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/powerdog.yaml b/templates/release/en/meter/powerdog.yaml new file mode 100644 index 0000000000..5ec0e5a171 --- /dev/null +++ b/templates/release/en/meter/powerdog.yaml @@ -0,0 +1,43 @@ +template: powerdog +product: + identifier: powerdog + description: Powerdog +render: + - usage: grid + default: | + type: template + template: powerdog + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: powerdog + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/powerdog_0.yaml b/templates/release/en/meter/powerdog_0.yaml deleted file mode 100644 index e8ffec3dde..0000000000 --- a/templates/release/en/meter/powerdog_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: Powerdog -render: - - usage: grid - default: | - type: template - template: powerdog - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: powerdog - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/powerfox-poweropti.yaml b/templates/release/en/meter/powerfox-poweropti.yaml new file mode 100644 index 0000000000..0aa760537a --- /dev/null +++ b/templates/release/en/meter/powerfox-poweropti.yaml @@ -0,0 +1,62 @@ +template: powerfox-poweropti +product: + identifier: powerfox-poweropti + brand: Powerfox + description: Poweropti +render: + - usage: grid + default: | + type: template + template: powerfox-poweropti + usage: grid + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + advanced: | + type: template + template: powerfox-poweropti + usage: grid + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + id: main # Id in case of multiple PowerOpti + - usage: pv + default: | + type: template + template: powerfox-poweropti + usage: pv + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + advanced: | + type: template + template: powerfox-poweropti + usage: pv + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + id: main # Id in case of multiple PowerOpti +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: id + example: + default: main + choice: [] + unit: + description: + help: Id in case of multiple PowerOpti + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/powerfox-poweropti_0.yaml b/templates/release/en/meter/powerfox-poweropti_0.yaml deleted file mode 100644 index 414ced22db..0000000000 --- a/templates/release/en/meter/powerfox-poweropti_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Powerfox - description: Poweropti -render: - - usage: grid - default: | - type: template - template: powerfox-poweropti - usage: grid - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - advanced: | - type: template - template: powerfox-poweropti - usage: grid - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti - - usage: pv - default: | - type: template - template: powerfox-poweropti - usage: pv - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - advanced: | - type: template - template: powerfox-poweropti - usage: pv - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti diff --git a/templates/release/en/meter/qcells-hybrid-cloud_0.yaml b/templates/release/en/meter/qcells-hybrid-cloud_0.yaml deleted file mode 100644 index d92342d9e0..0000000000 --- a/templates/release/en/meter/qcells-hybrid-cloud_0.yaml +++ /dev/null @@ -1,49 +0,0 @@ -product: - brand: QCells - description: Hybrid-Inverter (Cloud) -description: | - The QCells hybrid inverter has to be registered in the QCellsCloud. - - **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. - -render: - - usage: grid - default: | - type: template - template: qcells-hybrid-cloud - usage: grid - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". - serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. - advanced: | - type: template - template: qcells-hybrid-cloud - usage: grid - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". - serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. - - usage: pv - default: | - type: template - template: qcells-hybrid-cloud - usage: pv - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". - serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. - advanced: | - type: template - template: qcells-hybrid-cloud - usage: pv - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". - serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. - - usage: battery - default: | - type: template - template: qcells-hybrid-cloud - usage: battery - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". - serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. - advanced: | - type: template - template: qcells-hybrid-cloud - usage: battery - tokenid: # QCellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". - serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/qcells-hybrid-inverter-cloud.yaml b/templates/release/en/meter/qcells-hybrid-inverter-cloud.yaml new file mode 100644 index 0000000000..d31377a8ba --- /dev/null +++ b/templates/release/en/meter/qcells-hybrid-inverter-cloud.yaml @@ -0,0 +1,79 @@ +template: qcells-hybrid-cloud +product: + identifier: qcells-hybrid-inverter-cloud + brand: Qcells + description: Hybrid-Inverter (Cloud) +description: | + The Qcells hybrid inverter has to be registered in the QcellsCloud. + + **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. + +render: + - usage: grid + default: | + type: template + template: qcells-hybrid-cloud + usage: grid + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. + advanced: | + type: template + template: qcells-hybrid-cloud + usage: grid + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. + - usage: pv + default: | + type: template + template: qcells-hybrid-cloud + usage: pv + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. + advanced: | + type: template + template: qcells-hybrid-cloud + usage: pv + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. + - usage: battery + default: | + type: template + template: qcells-hybrid-cloud + usage: battery + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. + advanced: | + type: template + template: qcells-hybrid-cloud + usage: battery + tokenid: # QcellsCloud TokenID, Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + serial: # Serial number, Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. + capacity: 50 # Battery capacity (kWh), optional +params: + - name: tokenid + example: + default: + choice: [] + unit: + description: QcellsCloud TokenID + help: Go to https://qhome-ess-g3.q-cells.eu/#/api/ and take the value of "ObtaintokenID". + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Serial number + help: Go to https://qhome-ess-g3.q-cells.eu/blue/#/inverter and take the value of registration number. + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml b/templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml new file mode 100644 index 0000000000..4a6599a88a --- /dev/null +++ b/templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml @@ -0,0 +1,225 @@ +template: solax +product: + identifier: qcells-q-home-ess-hyb-g3 + brand: Qcells + description: Q.HOME ESS HYB-G3 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + advanced: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + advanced: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + storageunit: 1 # optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + advanced: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + storageunit: 1 # optional + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: The inverter has a third PV input (MPPT3) + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Default mode for battery control + help: Inverter falls back to this mode after charging the battery or after stopping discharge. + advanced: true + optional: true +modbus: + baudrate: 19200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/rct-power.yaml b/templates/release/en/meter/rct-power.yaml new file mode 100644 index 0000000000..422faadc48 --- /dev/null +++ b/templates/release/en/meter/rct-power.yaml @@ -0,0 +1,118 @@ +template: rct-power +product: + identifier: rct-power + brand: RCT + description: Power +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: rct-power + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: rct-power + usage: grid + host: 192.0.2.2 # IP address or hostname + minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + externalpower: # External power, Query external power of all devices connected to S0 (optional) + - usage: pv + default: | + type: template + template: rct-power + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: rct-power + usage: pv + host: 192.0.2.2 # IP address or hostname + minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + externalpower: # External power, Query external power of all devices connected to S0 (optional) + - usage: battery + default: | + type: template + template: rct-power + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: rct-power + usage: battery + host: 192.0.2.2 # IP address or hostname + capacity: 50 # Battery capacity (kWh), optional + minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) + externalpower: # External power, Query external power of all devices connected to S0 (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 7 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 97 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: cache + example: 5m + default: 30s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: externalpower + example: + default: + choice: [] + unit: + description: External power + help: Query external power of all devices connected to S0 + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/rct-power_0.yaml b/templates/release/en/meter/rct-power_0.yaml deleted file mode 100644 index 28d75ab20b..0000000000 --- a/templates/release/en/meter/rct-power_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: RCT - description: Power -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: rct-power - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: rct-power - usage: grid - host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional) - - usage: pv - default: | - type: template - template: rct-power - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: rct-power - usage: pv - host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional) - - usage: battery - default: | - type: template - template: rct-power - usage: battery - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: rct-power - usage: battery - host: 192.0.2.2 # IP address or hostname - capacity: 50 # Battery capacity (kWh), optional - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional) diff --git a/templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml b/templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml new file mode 100644 index 0000000000..7a300b29b2 --- /dev/null +++ b/templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml @@ -0,0 +1,61 @@ +template: sbc-axx3 +product: + identifier: saia-burgess-controls-sbc-ale3 + brand: Saia-Burgess Controls (SBC) + description: ALE3 +render: + - usage: grid + default: | + type: template + template: sbc-axx3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: sbc-axx3 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml b/templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml new file mode 100644 index 0000000000..5d50d6befe --- /dev/null +++ b/templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml @@ -0,0 +1,61 @@ +template: sbc-axx3 +product: + identifier: saia-burgess-controls-sbc-awd3 + brand: Saia-Burgess Controls (SBC) + description: AWD3 +render: + - usage: grid + default: | + type: template + template: sbc-axx3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: sbc-axx3 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml b/templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml new file mode 100644 index 0000000000..6366c2c44d --- /dev/null +++ b/templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml @@ -0,0 +1,110 @@ +template: saj-h1 +product: + identifier: saj-h1-series-hybrid-solar-inverter + brand: SAJ + description: H1 Series Hybrid Solar Inverter +render: + - usage: grid + default: | + type: template + template: saj-h1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Timeout, optional + advanced: | + type: template + template: saj-h1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Timeout, optional + - usage: pv + default: | + type: template + template: saj-h1 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Timeout, optional + advanced: | + type: template + template: saj-h1 + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Timeout, optional + - usage: battery + default: | + type: template + template: saj-h1 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Timeout, optional + advanced: | + type: template + template: saj-h1 + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 5s # Timeout, optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 5s + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/saj-h1_0.yaml b/templates/release/en/meter/saj-h1_0.yaml deleted file mode 100644 index 5c112c0783..0000000000 --- a/templates/release/en/meter/saj-h1_0.yaml +++ /dev/null @@ -1,74 +0,0 @@ -product: - brand: SAJ - description: H1 Series Hybrid Solar Inverter -render: - - usage: grid - default: | - type: template - template: saj-h1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Timeout, optional - advanced: | - type: template - template: saj-h1 - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Timeout, optional - - usage: pv - default: | - type: template - template: saj-h1 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Timeout, optional - advanced: | - type: template - template: saj-h1 - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Timeout, optional - - usage: battery - default: | - type: template - template: saj-h1 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Timeout, optional - advanced: | - type: template - template: saj-h1 - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 5s # Timeout, optional - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml b/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml new file mode 100644 index 0000000000..660d3368d5 --- /dev/null +++ b/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml @@ -0,0 +1,211 @@ +template: saj-h2 +product: + identifier: saj-h2-series-hybrid-solar-inverter + brand: SAJ + description: H2 Series Hybrid Solar Inverter +render: + - usage: grid + default: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: battery + default: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: saj-h2 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 2 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 2 + choice: [] + unit: + description: Default mode for battery control + help: Inverter falls back to this mode after charging the battery or after stopping discharge. + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true +modbus: + baudrate: 115200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/saj-h2_0.yaml b/templates/release/en/meter/saj-h2_0.yaml deleted file mode 100644 index 8708616902..0000000000 --- a/templates/release/en/meter/saj-h2_0.yaml +++ /dev/null @@ -1,153 +0,0 @@ -product: - brand: SAJ - description: H2 Series Hybrid Solar Inverter -render: - - usage: grid - default: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: battery - default: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 2 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/saj-h2_1.yaml b/templates/release/en/meter/saj-h2_1.yaml deleted file mode 100644 index e8c51a7422..0000000000 --- a/templates/release/en/meter/saj-h2_1.yaml +++ /dev/null @@ -1,153 +0,0 @@ -product: - brand: Ampere - description: Ampere.StoragePro -render: - - usage: grid - default: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: battery - default: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: saj-h2 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 2 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/saj-r5-series-solar-inverter.yaml b/templates/release/en/meter/saj-r5-series-solar-inverter.yaml new file mode 100644 index 0000000000..7ebc2899e9 --- /dev/null +++ b/templates/release/en/meter/saj-r5-series-solar-inverter.yaml @@ -0,0 +1,43 @@ +template: saj-r5 +product: + identifier: saj-r5-series-solar-inverter + brand: SAJ + description: R5 Series Solar Inverter +render: + - usage: pv + default: | + type: template + template: saj-r5 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/saj-r5_0.yaml b/templates/release/en/meter/saj-r5_0.yaml deleted file mode 100644 index dcf6d62b72..0000000000 --- a/templates/release/en/meter/saj-r5_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: SAJ - description: R5 Series Solar Inverter -render: - - usage: pv - default: | - type: template - template: saj-r5 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sax-homespeicher.yaml b/templates/release/en/meter/sax-homespeicher.yaml new file mode 100644 index 0000000000..b81b514f91 --- /dev/null +++ b/templates/release/en/meter/sax-homespeicher.yaml @@ -0,0 +1,44 @@ +template: sax +product: + identifier: sax-homespeicher + brand: SAX + description: Homespeicher +render: + - usage: grid + default: | + type: template + template: sax + usage: grid + + # Modbus TCP + modbus: tcpip + id: 64 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sax + usage: battery + + # Modbus TCP + modbus: tcpip + id: 64 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 64 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sax_0.yaml b/templates/release/en/meter/sax_0.yaml deleted file mode 100644 index 6b87e7b5ff..0000000000 --- a/templates/release/en/meter/sax_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: SAX - description: Homespeicher -render: - - usage: grid - default: | - type: template - template: sax - usage: grid - - # Modbus TCP - modbus: tcpip - id: 64 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sax - usage: battery - - # Modbus TCP - modbus: tcpip - id: 64 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sbc-axx3_0.yaml b/templates/release/en/meter/sbc-axx3_0.yaml deleted file mode 100644 index 0932eb8d3b..0000000000 --- a/templates/release/en/meter/sbc-axx3_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Saia-Burgess Controls - description: ALE3, AWD3 -render: - - usage: grid - default: | - type: template - template: sbc-axx3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: sbc-axx3 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml b/templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml new file mode 100644 index 0000000000..c57a0d25eb --- /dev/null +++ b/templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml @@ -0,0 +1,61 @@ +template: schneider-iem3000 +product: + identifier: schneider-electric-iem3xxx-modbus + brand: Schneider Electric + description: iEM3xxx Modbus +render: + - usage: grid + default: | + type: template + template: schneider-iem3000 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: schneider-iem3000 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/schneider-iem3000_0.yaml b/templates/release/en/meter/schneider-iem3000_0.yaml deleted file mode 100644 index c766da31fc..0000000000 --- a/templates/release/en/meter/schneider-iem3000_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Schneider Electric - description: iEM3xxx Modbus -render: - - usage: grid - default: | - type: template - template: schneider-iem3000 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: schneider-iem3000 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/senec-home.yaml b/templates/release/en/meter/senec-home.yaml new file mode 100644 index 0000000000..3ba4623572 --- /dev/null +++ b/templates/release/en/meter/senec-home.yaml @@ -0,0 +1,75 @@ +template: senec-home +product: + identifier: senec-home + brand: SENEC + description: .Home +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: senec-home + usage: grid + host: 192.0.2.2 # IP address or hostname + schema: https # [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: grid + host: 192.0.2.2 # IP address or hostname + schema: https # [https, http] (optional) + - usage: pv + default: | + type: template + template: senec-home + usage: pv + host: 192.0.2.2 # IP address or hostname + schema: https # [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: pv + host: 192.0.2.2 # IP address or hostname + schema: https # [https, http] (optional) + - usage: battery + default: | + type: template + template: senec-home + usage: battery + host: 192.0.2.2 # IP address or hostname + schema: https # [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: battery + host: 192.0.2.2 # IP address or hostname + schema: https # [https, http] (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: schema + example: + default: https + choice: ['https', 'http'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/senec-home_0.yaml b/templates/release/en/meter/senec-home_0.yaml deleted file mode 100644 index faafe6214d..0000000000 --- a/templates/release/en/meter/senec-home_0.yaml +++ /dev/null @@ -1,45 +0,0 @@ -product: - brand: SENEC - description: .Home -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: senec-home - usage: grid - host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) - advanced: | - type: template - template: senec-home - usage: grid - host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) - - usage: pv - default: | - type: template - template: senec-home - usage: pv - host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) - advanced: | - type: template - template: senec-home - usage: pv - host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) - - usage: battery - default: | - type: template - template: senec-home - usage: battery - host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) - advanced: | - type: template - template: senec-home - usage: battery - host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml b/templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml new file mode 100644 index 0000000000..f54338773c --- /dev/null +++ b/templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml @@ -0,0 +1,33 @@ +template: senergy +product: + identifier: senergy-se-4-5-6ktl-s1-g2-inverter + brand: Senergy + description: SE 4/5/6KTL-S1/G2 Inverter +render: + - usage: pv + default: | + type: template + template: senergy + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/senergy_0.yaml b/templates/release/en/meter/senergy_0.yaml deleted file mode 100644 index 9a544572ac..0000000000 --- a/templates/release/en/meter/senergy_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: Senergy - description: SE 4/5/6KTL-S1/G2 Inverter -render: - - usage: pv - default: | - type: template - template: senergy - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/senergy_1.yaml b/templates/release/en/meter/senergy_1.yaml deleted file mode 100644 index 1d9c00fb45..0000000000 --- a/templates/release/en/meter/senergy_1.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SolarMax - description: SP Series Inverter -render: - - usage: pv - default: | - type: template - template: senergy - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/shelly-1pm-mini.yaml b/templates/release/en/meter/shelly-1pm-mini.yaml new file mode 100644 index 0000000000..23085f2b03 --- /dev/null +++ b/templates/release/en/meter/shelly-1pm-mini.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-1pm-mini + brand: Shelly + description: 1PM mini + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-1pm.yaml b/templates/release/en/meter/shelly-1pm.yaml new file mode 100644 index 0000000000..be2bbbcef0 --- /dev/null +++ b/templates/release/en/meter/shelly-1pm.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-1pm + brand: Shelly + description: 1PM + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-1pm_0.yaml b/templates/release/en/meter/shelly-1pm_0.yaml deleted file mode 100644 index 1388f91961..0000000000 --- a/templates/release/en/meter/shelly-1pm_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Shelly - description: 1PM, EM, Plug S, Pro 3EM in monophase mode - group: Switchable sockets -render: - - usage: grid - default: | - type: template - template: shelly-1pm - usage: grid - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional - - usage: pv - default: | - type: template - template: shelly-1pm - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional - - usage: charge - default: | - type: template - template: shelly-1pm - usage: charge - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional diff --git a/templates/release/en/meter/shelly-3em.yaml b/templates/release/en/meter/shelly-3em.yaml new file mode 100644 index 0000000000..15b9de40fd --- /dev/null +++ b/templates/release/en/meter/shelly-3em.yaml @@ -0,0 +1,73 @@ +template: shelly-3em +product: + identifier: shelly-3em + brand: Shelly + description: 3EM +render: + - usage: grid + default: | + type: template + template: shelly-3em + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: shelly-3em + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: pv + default: | + type: template + template: shelly-3em + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: shelly-3em + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: charge + default: | + type: template + template: shelly-3em + usage: charge + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: shelly-3em + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-3em_0.yaml b/templates/release/en/meter/shelly-3em_0.yaml deleted file mode 100644 index 7ee5fbfb3f..0000000000 --- a/templates/release/en/meter/shelly-3em_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Shelly - description: 3EM -render: - - usage: grid - default: | - type: template - template: shelly-3em - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: shelly-3em - usage: grid - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: shelly-3em - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: shelly-3em - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: charge - default: | - type: template - template: shelly-3em - usage: charge - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: shelly-3em - usage: charge - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/meter/shelly-em.yaml b/templates/release/en/meter/shelly-em.yaml new file mode 100644 index 0000000000..d23ce01b7d --- /dev/null +++ b/templates/release/en/meter/shelly-em.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-em + brand: Shelly + description: EM + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-plug-s.yaml b/templates/release/en/meter/shelly-plug-s.yaml new file mode 100644 index 0000000000..854e29da5c --- /dev/null +++ b/templates/release/en/meter/shelly-plug-s.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-plug-s + brand: Shelly + description: Plug S + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pm-mini.yaml b/templates/release/en/meter/shelly-pm-mini.yaml new file mode 100644 index 0000000000..820ffb553a --- /dev/null +++ b/templates/release/en/meter/shelly-pm-mini.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pm-mini + brand: Shelly + description: PM mini + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pro-1pm.yaml b/templates/release/en/meter/shelly-pro-1pm.yaml new file mode 100644 index 0000000000..94f2bfc9dc --- /dev/null +++ b/templates/release/en/meter/shelly-pro-1pm.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pro-1pm + brand: Shelly + description: Pro 1PM + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pro-3-em.yaml b/templates/release/en/meter/shelly-pro-3-em.yaml new file mode 100644 index 0000000000..21144ec53e --- /dev/null +++ b/templates/release/en/meter/shelly-pro-3-em.yaml @@ -0,0 +1,58 @@ +template: shelly-pro-3em +product: + identifier: shelly-pro-3-em + brand: Shelly + description: Pro 3 EM +render: + - usage: grid + default: | + type: template + template: shelly-pro-3em + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: pv + default: | + type: template + template: shelly-pro-3em + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: charge + default: | + type: template + template: shelly-pro-3em + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml b/templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml new file mode 100644 index 0000000000..601becd01f --- /dev/null +++ b/templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pro-3em-monophase-mode + brand: Shelly + description: Pro 3EM (monophase mode) + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pro-3em_0.yaml b/templates/release/en/meter/shelly-pro-3em_0.yaml deleted file mode 100644 index f30ffb99ed..0000000000 --- a/templates/release/en/meter/shelly-pro-3em_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Shelly - description: Pro 3 EM -render: - - usage: grid - default: | - type: template - template: shelly-pro-3em - usage: grid - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: shelly-pro-3em - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: charge - default: | - type: template - template: shelly-pro-3em - usage: charge - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/meter/shelly-pro-em.yaml b/templates/release/en/meter/shelly-pro-em.yaml new file mode 100644 index 0000000000..caf1c024b6 --- /dev/null +++ b/templates/release/en/meter/shelly-pro-em.yaml @@ -0,0 +1,71 @@ +template: shelly-1pm +product: + identifier: shelly-pro-em + brand: Shelly + description: Pro EM + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: shelly-1pm + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: pv + default: | + type: template + template: shelly-1pm + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional + - usage: charge + default: | + type: template + template: shelly-1pm + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 0 + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/siemens-7kt1665.yaml b/templates/release/en/meter/siemens-7kt1665.yaml new file mode 100644 index 0000000000..f5dbf9221f --- /dev/null +++ b/templates/release/en/meter/siemens-7kt1665.yaml @@ -0,0 +1,74 @@ +template: siemens-7kt1665 +product: + identifier: siemens-7kt1665 + brand: Siemens + description: 7KT1665 +render: + - usage: grid + default: | + type: template + template: siemens-7kt1665 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: siemens-7kt1665 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/siemens-7kt1665_0.yaml b/templates/release/en/meter/siemens-7kt1665_0.yaml deleted file mode 100644 index 938c0727f0..0000000000 --- a/templates/release/en/meter/siemens-7kt1665_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Siemens - description: 7KT1665 -render: - - usage: grid - default: | - type: template - template: siemens-7kt1665 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: siemens-7kt1665 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/siemens-junelight-smart-battery.yaml b/templates/release/en/meter/siemens-junelight-smart-battery.yaml new file mode 100644 index 0000000000..4e4e61bdee --- /dev/null +++ b/templates/release/en/meter/siemens-junelight-smart-battery.yaml @@ -0,0 +1,98 @@ +template: siemens-junelight +product: + identifier: siemens-junelight-smart-battery + brand: Siemens + description: Junelight Smart Battery +description: | + The battery has to be set to Loxone with the installer account. + +render: + - usage: grid + default: | + type: template + template: siemens-junelight + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: siemens-junelight + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: siemens-junelight + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: siemens-junelight + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: siemens-junelight + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: siemens-junelight + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/siemens-junelight_0.yaml b/templates/release/en/meter/siemens-junelight_0.yaml deleted file mode 100644 index f5b3e946c4..0000000000 --- a/templates/release/en/meter/siemens-junelight_0.yaml +++ /dev/null @@ -1,71 +0,0 @@ -product: - brand: Siemens - description: Junelight Smart Battery -description: | - The battery has to be set to Loxone with the installer account. - -render: - - usage: grid - default: | - type: template - template: siemens-junelight - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: siemens-junelight - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: siemens-junelight - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: siemens-junelight - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: siemens-junelight - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: siemens-junelight - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/siemens-pac-2200.yaml b/templates/release/en/meter/siemens-pac-2200.yaml new file mode 100644 index 0000000000..d508896cb5 --- /dev/null +++ b/templates/release/en/meter/siemens-pac-2200.yaml @@ -0,0 +1,74 @@ +template: siemens-pac2200 +product: + identifier: siemens-pac-2200 + brand: Siemens + description: PAC 2200 +render: + - usage: grid + default: | + type: template + template: siemens-pac2200 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: siemens-pac2200 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/siemens-pac2200_0.yaml b/templates/release/en/meter/siemens-pac2200_0.yaml deleted file mode 100644 index f4a8b1239f..0000000000 --- a/templates/release/en/meter/siemens-pac2200_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Siemens - description: PAC 2200 -render: - - usage: grid - default: | - type: template - template: siemens-pac2200 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: siemens-pac2200 - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml b/templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml new file mode 100644 index 0000000000..b408d4ecc9 --- /dev/null +++ b/templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml @@ -0,0 +1,91 @@ +template: sigenergy +product: + identifier: sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec + brand: Sigenergy + description: Sigen Hybrid/Sigen PV Max/SigenStore EC +description: | + The electrician needs to enable the Modbus via TCP/IP in their service app before the setup is functional. This is not available in the customers mySigen app. +render: + - usage: grid + default: | + type: template + template: sigenergy + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # optional + advanced: | + type: template + template: sigenergy + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # optional + - usage: pv + default: | + type: template + template: sigenergy + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # optional + advanced: | + type: template + template: sigenergy + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # optional + - usage: battery + default: | + type: template + template: sigenergy + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # optional + advanced: | + type: template + template: sigenergy + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: id + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sigenergy_0.yaml b/templates/release/en/meter/sigenergy_0.yaml deleted file mode 100644 index 5a38408be4..0000000000 --- a/templates/release/en/meter/sigenergy_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Sigenergy - description: Sigen Hybrid/Sigen PV Max/SigenStore EC -description: | - The electrician needs to enable the Modbus via TCP/IP in their service app before the setup is functional. This is not available in the customers mySigen app. -render: - - usage: grid - default: | - type: template - template: sigenergy - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 1 # optional - advanced: | - type: template - template: sigenergy - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 1 # optional - - usage: pv - default: | - type: template - template: sigenergy - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 1 # optional - advanced: | - type: template - template: sigenergy - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 1 # optional - - usage: battery - default: | - type: template - template: sigenergy - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 1 # optional - advanced: | - type: template - template: sigenergy - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - id: 1 # optional - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/slimmelezer-V2_0.yaml b/templates/release/en/meter/slimmelezer-V2_0.yaml deleted file mode 100644 index c92e825721..0000000000 --- a/templates/release/en/meter/slimmelezer-V2_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zuidwijk - description: SlimmeLezer(+) V2 -description: | - More recent slimmelezer devices use a different configuration. Try this template if the other one fails. -render: - - usage: grid - default: | - type: template - template: slimmelezer-V2 - usage: grid - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/slimmelezer-luxembourg_0.yaml b/templates/release/en/meter/slimmelezer-luxembourg_0.yaml deleted file mode 100644 index f8fc9e139c..0000000000 --- a/templates/release/en/meter/slimmelezer-luxembourg_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Zuidwijk - description: SlimmeLezer(+) in Luxembourg -description: | - Slimmelezer devices use different sensor names in Luxembourg. -render: - - usage: grid - default: | - type: template - template: slimmelezer-luxembourg - usage: grid - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/slimmelezer_0.yaml b/templates/release/en/meter/slimmelezer_0.yaml deleted file mode 100644 index 5464082c24..0000000000 --- a/templates/release/en/meter/slimmelezer_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Zuidwijk - description: SlimmeLezer(+) -render: - - usage: grid - default: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP address or hostname - scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle diff --git a/templates/release/en/meter/slimmelezer_1.yaml b/templates/release/en/meter/slimmelezer_1.yaml deleted file mode 100644 index 905cf4247e..0000000000 --- a/templates/release/en/meter/slimmelezer_1.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: ESPHome - description: DSMR -render: - - usage: grid - default: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP address or hostname - scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle diff --git a/templates/release/en/meter/slimmelezer_2.yaml b/templates/release/en/meter/slimmelezer_2.yaml deleted file mode 100644 index 1fbd43906a..0000000000 --- a/templates/release/en/meter/slimmelezer_2.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: mhendriks - description: P1 dongle -render: - - usage: grid - default: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: slimmelezer - usage: grid - host: 192.0.2.2 # IP address or hostname - scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle diff --git a/templates/release/en/meter/sma-data-manager.yaml b/templates/release/en/meter/sma-data-manager.yaml new file mode 100644 index 0000000000..3e2d66bbb6 --- /dev/null +++ b/templates/release/en/meter/sma-data-manager.yaml @@ -0,0 +1,97 @@ +template: sma-data-manager +product: + identifier: sma-data-manager + brand: SMA + description: Data Manager +description: | + In the web interface of the SMA Data Manager you need to activate "Modbus Server activated" in the section "External communication". +render: + - usage: grid + default: | + type: template + template: sma-data-manager + usage: grid + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-data-manager + usage: grid + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sma-data-manager + usage: pv + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-data-manager + usage: pv + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sma-data-manager + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-data-manager + usage: battery + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-data-manager_0.yaml b/templates/release/en/meter/sma-data-manager_0.yaml deleted file mode 100644 index 1f805c0ff8..0000000000 --- a/templates/release/en/meter/sma-data-manager_0.yaml +++ /dev/null @@ -1,70 +0,0 @@ -product: - brand: SMA - description: Data Manager -description: | - In the web interface of the SMA Data Manager you need to activate "Modbus Server activated" in the section "External communication". -render: - - usage: grid - default: | - type: template - template: sma-data-manager - usage: grid - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-data-manager - usage: grid - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sma-data-manager - usage: pv - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-data-manager - usage: pv - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sma-data-manager - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-data-manager - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/sma-energy-meter.yaml b/templates/release/en/meter/sma-energy-meter.yaml new file mode 100644 index 0000000000..d491804575 --- /dev/null +++ b/templates/release/en/meter/sma-energy-meter.yaml @@ -0,0 +1,49 @@ +template: sma-energy-meter +product: + identifier: sma-energy-meter + brand: SMA + description: Energy Meter +render: + - usage: grid + default: | + type: template + template: sma-energy-meter + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: sma-energy-meter + usage: grid + host: 192.0.2.2 # IP address or hostname + interface: eth0 # Network interface, optional + - usage: pv + default: | + type: template + template: sma-energy-meter + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: sma-energy-meter + usage: pv + host: 192.0.2.2 # IP address or hostname + interface: eth0 # Network interface, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: interface + example: eth0 + default: + choice: [] + unit: + description: Network interface + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-energy-meter_0.yaml b/templates/release/en/meter/sma-energy-meter_0.yaml deleted file mode 100644 index f3aca25200..0000000000 --- a/templates/release/en/meter/sma-energy-meter_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: SMA - description: Energy Meter -render: - - usage: grid - default: | - type: template - template: sma-energy-meter - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: sma-energy-meter - usage: grid - host: 192.0.2.2 # IP address or hostname - interface: eth0 # Network interface, optional - - usage: pv - default: | - type: template - template: sma-energy-meter - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: sma-energy-meter - usage: pv - host: 192.0.2.2 # IP address or hostname - interface: eth0 # Network interface, optional diff --git a/templates/release/en/meter/sma-home-manager_0.yaml b/templates/release/en/meter/sma-home-manager_0.yaml deleted file mode 100644 index 2ed42b04b8..0000000000 --- a/templates/release/en/meter/sma-home-manager_0.yaml +++ /dev/null @@ -1,18 +0,0 @@ -product: - brand: SMA - description: Sunny Home Manager 2.0 -capabilities: ["smahems"] -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: sma-home-manager - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: sma-home-manager - usage: grid - host: 192.0.2.2 # IP address or hostname - interface: eth0 # Network interface, optional diff --git a/templates/release/en/meter/sma-hybrid_0.yaml b/templates/release/en/meter/sma-hybrid_0.yaml deleted file mode 100644 index 20a1d12187..0000000000 --- a/templates/release/en/meter/sma-hybrid_0.yaml +++ /dev/null @@ -1,51 +0,0 @@ -product: - brand: SMA - description: Smart Energy Hybrid Inverter -capabilities: ["battery-control"] -render: - - usage: pv - default: | - type: template - template: sma-hybrid - usage: pv - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-hybrid - usage: pv - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: sma-hybrid - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-hybrid - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional diff --git a/templates/release/en/meter/sma-inverter-modbus_0.yaml b/templates/release/en/meter/sma-inverter-modbus_0.yaml deleted file mode 100644 index cda83af755..0000000000 --- a/templates/release/en/meter/sma-inverter-modbus_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SMA - description: Wechselrichter (Modbus) -render: - - usage: pv - default: | - type: template - template: sma-inverter-modbus - usage: pv - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sma-inverter-speedwire.yaml b/templates/release/en/meter/sma-inverter-speedwire.yaml new file mode 100644 index 0000000000..8b8bb33c3b --- /dev/null +++ b/templates/release/en/meter/sma-inverter-speedwire.yaml @@ -0,0 +1,62 @@ +template: sma-inverter-speedwire +product: + identifier: sma-inverter-speedwire + brand: SMA + description: Inverter (Speedwire) +requirements: ["skiptest"] +render: + - usage: pv + default: | + type: template + template: sma-inverter-speedwire + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, Password for user group Standard (optional) + advanced: | + type: template + template: sma-inverter-speedwire + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, Password for user group Standard (optional) + - usage: battery + default: | + type: template + template: sma-inverter-speedwire + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, Password for user group Standard (optional) + advanced: | + type: template + template: sma-inverter-speedwire + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, Password for user group Standard (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Password for user group Standard + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-inverter-speedwire_0.yaml b/templates/release/en/meter/sma-inverter-speedwire_0.yaml deleted file mode 100644 index 332bf304a5..0000000000 --- a/templates/release/en/meter/sma-inverter-speedwire_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: SMA - description: Inverter (Speedwire) -requirements: ["skiptest"] -render: - - usage: pv - default: | - type: template - template: sma-inverter-speedwire - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, Password for user group Standard (optional) - advanced: | - type: template - template: sma-inverter-speedwire - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, Password for user group Standard (optional) - - usage: battery - default: | - type: template - template: sma-inverter-speedwire - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, Password for user group Standard (optional) - advanced: | - type: template - template: sma-inverter-speedwire - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, Password for user group Standard (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/sma-sbs-15-25-modbus_0.yaml b/templates/release/en/meter/sma-sbs-15-25-modbus_0.yaml deleted file mode 100644 index bfe5994b45..0000000000 --- a/templates/release/en/meter/sma-sbs-15-25-modbus_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: SMA - description: Sunny Boy Storage 1.5/2.0/2.5 (Modbus) -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sma-sbs-15-25-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-sbs-15-25-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional diff --git a/templates/release/en/meter/sma-sbs-modbus_0.yaml b/templates/release/en/meter/sma-sbs-modbus_0.yaml deleted file mode 100644 index 746c98829b..0000000000 --- a/templates/release/en/meter/sma-sbs-modbus_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: SMA - description: Sunny Boy Storage 3.7/5.0/6.0 (Modbus) -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sma-sbs-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-sbs-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional diff --git a/templates/release/en/meter/sma-si-modbus_0.yaml b/templates/release/en/meter/sma-si-modbus_0.yaml deleted file mode 100644 index 18cda0ff71..0000000000 --- a/templates/release/en/meter/sma-si-modbus_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: SMA - description: Sunny Island (Modbus) -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sma-si-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sma-si-modbus - usage: battery - - # Modbus TCP - modbus: tcpip - id: 3 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional diff --git a/templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml b/templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml new file mode 100644 index 0000000000..f7c2040de9 --- /dev/null +++ b/templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml @@ -0,0 +1,105 @@ +template: sma-hybrid +product: + identifier: sma-smart-energy-hybrid-inverter + brand: SMA + description: Smart Energy Hybrid Inverter +capabilities: ["battery-control"] +render: + - usage: pv + default: | + type: template + template: sma-hybrid + usage: pv + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-hybrid + usage: pv + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: sma-hybrid + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-hybrid + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: ModbusTCP server needs to be enabled. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml b/templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml new file mode 100644 index 0000000000..850e600582 --- /dev/null +++ b/templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml @@ -0,0 +1,74 @@ +template: sma-sbs-15-25-modbus +product: + identifier: sma-sunny-boy-storage-1-5-2-0-2-5-modbus + brand: SMA + description: Sunny Boy Storage 1.5/2.0/2.5 (Modbus) +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sma-sbs-15-25-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-sbs-15-25-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: ModbusTCP server needs to be enabled. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml b/templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml new file mode 100644 index 0000000000..8d1d1531f4 --- /dev/null +++ b/templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml @@ -0,0 +1,74 @@ +template: sma-sbs-modbus +product: + identifier: sma-sunny-boy-storage-3-7-5-0-6-0-modbus + brand: SMA + description: Sunny Boy Storage 3.7/5.0/6.0 (Modbus) +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sma-sbs-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-sbs-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: ModbusTCP server needs to be enabled. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-sunny-home-manager-2-0.yaml b/templates/release/en/meter/sma-sunny-home-manager-2-0.yaml new file mode 100644 index 0000000000..fea114ced9 --- /dev/null +++ b/templates/release/en/meter/sma-sunny-home-manager-2-0.yaml @@ -0,0 +1,39 @@ +template: sma-home-manager +product: + identifier: sma-sunny-home-manager-2-0 + brand: SMA + description: Sunny Home Manager 2.0 +capabilities: ["smahems"] +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: sma-home-manager + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: sma-home-manager + usage: grid + host: 192.0.2.2 # IP address or hostname + interface: eth0 # Network interface, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: interface + example: eth0 + default: + choice: [] + unit: + description: Network interface + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-sunny-island-modbus.yaml b/templates/release/en/meter/sma-sunny-island-modbus.yaml new file mode 100644 index 0000000000..59a9def741 --- /dev/null +++ b/templates/release/en/meter/sma-sunny-island-modbus.yaml @@ -0,0 +1,74 @@ +template: sma-si-modbus +product: + identifier: sma-sunny-island-modbus + brand: SMA + description: Sunny Island (Modbus) +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sma-si-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sma-si-modbus + usage: battery + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: ModbusTCP server needs to be enabled. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 4200 + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-webbox.yaml b/templates/release/en/meter/sma-webbox.yaml new file mode 100644 index 0000000000..41feca330a --- /dev/null +++ b/templates/release/en/meter/sma-webbox.yaml @@ -0,0 +1,33 @@ +template: sma-webbox +product: + identifier: sma-webbox + brand: SMA + description: WebBox +render: + - usage: pv + default: | + type: template + template: sma-webbox + usage: pv + + # Modbus TCP + modbus: tcpip + id: 2 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: ModbusTCP server needs to be enabled. + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 2 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sma-webbox_0.yaml b/templates/release/en/meter/sma-webbox_0.yaml deleted file mode 100644 index 2d6962964d..0000000000 --- a/templates/release/en/meter/sma-webbox_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SMA - description: WebBox -render: - - usage: pv - default: | - type: template - template: sma-webbox - usage: pv - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sma-wechselrichter-modbus.yaml b/templates/release/en/meter/sma-wechselrichter-modbus.yaml new file mode 100644 index 0000000000..2350570aa1 --- /dev/null +++ b/templates/release/en/meter/sma-wechselrichter-modbus.yaml @@ -0,0 +1,33 @@ +template: sma-inverter-modbus +product: + identifier: sma-wechselrichter-modbus + brand: SMA + description: Wechselrichter (Modbus) +render: + - usage: pv + default: | + type: template + template: sma-inverter-modbus + usage: pv + + # Modbus TCP + modbus: tcpip + id: 3 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: ModbusTCP server needs to be enabled. + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 3 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-box.yaml b/templates/release/en/meter/smartfox-box.yaml new file mode 100644 index 0000000000..be4fbbd2e8 --- /dev/null +++ b/templates/release/en/meter/smartfox-box.yaml @@ -0,0 +1,37 @@ +template: smartfox +product: + identifier: smartfox-box + brand: Smartfox + description: Box +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: smartfox + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: aux + default: | + type: template + template: smartfox + usage: aux + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-em2_0.yaml b/templates/release/en/meter/smartfox-em2_0.yaml deleted file mode 100644 index 95ab02e968..0000000000 --- a/templates/release/en/meter/smartfox-em2_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Smartfox - description: Pro, Pro 2, Pro Light, Pro Light 2, Light (EM2 firmware) -description: | - `aux` can be used for water heating power. - -render: - - usage: grid - default: | - type: template - template: smartfox-em2 - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: smartfox-em2 - usage: grid - host: 192.0.2.2 # IP address or hostname - cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - - usage: pv - default: | - type: template - template: smartfox-em2 - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: smartfox-em2 - usage: pv - host: 192.0.2.2 # IP address or hostname - cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - - usage: aux - default: | - type: template - template: smartfox-em2 - usage: aux - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: smartfox-em2 - usage: aux - host: 192.0.2.2 # IP address or hostname - cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/meter/smartfox-light-em2-firmware.yaml b/templates/release/en/meter/smartfox-light-em2-firmware.yaml new file mode 100644 index 0000000000..28fec810be --- /dev/null +++ b/templates/release/en/meter/smartfox-light-em2-firmware.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-light-em2-firmware + brand: Smartfox + description: Light (EM2 firmware) +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-pro-2.yaml b/templates/release/en/meter/smartfox-pro-2.yaml new file mode 100644 index 0000000000..75ba8eb909 --- /dev/null +++ b/templates/release/en/meter/smartfox-pro-2.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro-2 + brand: Smartfox + description: Pro 2 +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-pro-light-2.yaml b/templates/release/en/meter/smartfox-pro-light-2.yaml new file mode 100644 index 0000000000..6b1c00a126 --- /dev/null +++ b/templates/release/en/meter/smartfox-pro-light-2.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro-light-2 + brand: Smartfox + description: Pro Light 2 +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-pro-light.yaml b/templates/release/en/meter/smartfox-pro-light.yaml new file mode 100644 index 0000000000..e73f1656c6 --- /dev/null +++ b/templates/release/en/meter/smartfox-pro-light.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro-light + brand: Smartfox + description: Pro Light +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-pro.yaml b/templates/release/en/meter/smartfox-pro.yaml new file mode 100644 index 0000000000..f3d6833e27 --- /dev/null +++ b/templates/release/en/meter/smartfox-pro.yaml @@ -0,0 +1,64 @@ +template: smartfox-em2 +product: + identifier: smartfox-pro + brand: Smartfox + description: Pro +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: grid + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: pv + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: aux + default: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: smartfox-em2 + usage: aux + host: 192.0.2.2 # IP address or hostname + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-reg-extended.yaml b/templates/release/en/meter/smartfox-reg-extended.yaml new file mode 100644 index 0000000000..b512e7a2ee --- /dev/null +++ b/templates/release/en/meter/smartfox-reg-extended.yaml @@ -0,0 +1,37 @@ +template: smartfox +product: + identifier: smartfox-reg-extended + brand: Smartfox + description: Reg extended +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: smartfox + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: aux + default: | + type: template + template: smartfox + usage: aux + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/smartfox-reg.yaml b/templates/release/en/meter/smartfox-reg.yaml new file mode 100644 index 0000000000..651ceef586 --- /dev/null +++ b/templates/release/en/meter/smartfox-reg.yaml @@ -0,0 +1,37 @@ +template: smartfox +product: + identifier: smartfox-reg + brand: Smartfox + description: Reg +description: | + `aux` can be used for water heating power. + +render: + - usage: grid + default: | + type: template + template: smartfox + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: smartfox + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: aux + default: | + type: template + template: smartfox + usage: aux + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/smartfox_0.yaml b/templates/release/en/meter/smartfox_0.yaml deleted file mode 100644 index 9786730bc4..0000000000 --- a/templates/release/en/meter/smartfox_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - brand: Smartfox - description: Box, Reg, Reg extended -description: | - `aux` can be used for water heating power. - -render: - - usage: grid - default: | - type: template - template: smartfox - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: smartfox - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: aux - default: | - type: template - template: smartfox - usage: aux - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/sofarsolar-g3_0.yaml b/templates/release/en/meter/sofarsolar-g3_0.yaml deleted file mode 100644 index 59c03efc61..0000000000 --- a/templates/release/en/meter/sofarsolar-g3_0.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: HYD 5…20K-3PH -capabilities: ["battery-control"] -description: | - LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) diff --git a/templates/release/en/meter/sofarsolar-g3_1.yaml b/templates/release/en/meter/sofarsolar-g3_1.yaml deleted file mode 100644 index 332133f756..0000000000 --- a/templates/release/en/meter/sofarsolar-g3_1.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: HYD 3…6K-EP -capabilities: ["battery-control"] -description: | - LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) diff --git a/templates/release/en/meter/sofarsolar-g3_2.yaml b/templates/release/en/meter/sofarsolar-g3_2.yaml deleted file mode 100644 index 135fe8a133..0000000000 --- a/templates/release/en/meter/sofarsolar-g3_2.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: SOFAR 80…136KTL -capabilities: ["battery-control"] -description: | - LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) diff --git a/templates/release/en/meter/sofarsolar-g3_3.yaml b/templates/release/en/meter/sofarsolar-g3_3.yaml deleted file mode 100644 index 43ae1f59df..0000000000 --- a/templates/release/en/meter/sofarsolar-g3_3.yaml +++ /dev/null @@ -1,154 +0,0 @@ -product: - brand: SofarSolar - description: SOFAR 5…24KTL-G3 -capabilities: ["battery-control"] -description: | - LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. -render: - - usage: grid - default: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - - usage: pv - default: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - advanced: | - type: template - template: sofarsolar-g3 - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) diff --git a/templates/release/en/meter/sofarsolar-hybrid-inverter.yaml b/templates/release/en/meter/sofarsolar-hybrid-inverter.yaml new file mode 100644 index 0000000000..b0ba5822ac --- /dev/null +++ b/templates/release/en/meter/sofarsolar-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: sofarsolar-hybrid-inverter + brand: SofarSolar + description: Hybrid Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml b/templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml new file mode 100644 index 0000000000..af34a7f69a --- /dev/null +++ b/templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-hyd-3-6k-ep + brand: SofarSolar + description: HYD 3…6K-EP +capabilities: ["battery-control"] +description: | + LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Default mode for battery control + help: Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml b/templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml new file mode 100644 index 0000000000..d800827cfb --- /dev/null +++ b/templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-hyd-5-20k-3ph + brand: SofarSolar + description: HYD 5…20K-3PH +capabilities: ["battery-control"] +description: | + LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Default mode for battery control + help: Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sofarsolar-inverter.yaml b/templates/release/en/meter/sofarsolar-inverter.yaml new file mode 100644 index 0000000000..bdfba5d50a --- /dev/null +++ b/templates/release/en/meter/sofarsolar-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: sofarsolar-inverter + brand: SofarSolar + description: Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml b/templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml new file mode 100644 index 0000000000..604ab347fc --- /dev/null +++ b/templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-sofar-5-24ktl-g3 + brand: SofarSolar + description: SOFAR 5…24KTL-G3 +capabilities: ["battery-control"] +description: | + LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Default mode for battery control + help: Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml b/templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml new file mode 100644 index 0000000000..1a1862c701 --- /dev/null +++ b/templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml @@ -0,0 +1,212 @@ +template: sofarsolar-g3 +product: + identifier: sofarsolar-sofar-80-136ktl + brand: SofarSolar + description: SOFAR 80…136KTL +capabilities: ["battery-control"] +description: | + LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. +render: + - usage: grid + default: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + - usage: pv + default: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + advanced: | + type: template + template: sofarsolar-g3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 8899 # Port + storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Default mode for battery control + help: Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 8899 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sofarsolar_0.yaml b/templates/release/en/meter/sofarsolar_0.yaml deleted file mode 100644 index 7b1bd8a22f..0000000000 --- a/templates/release/en/meter/sofarsolar_0.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: SofarSolar - description: Inverter, Hybrid Inverter -render: - - usage: grid - default: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/sofarsolar_1.yaml b/templates/release/en/meter/sofarsolar_1.yaml deleted file mode 100644 index dee96b1423..0000000000 --- a/templates/release/en/meter/sofarsolar_1.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - brand: ZCS Azzurro - description: Inverter, Hybrid Inverter -render: - - usage: grid - default: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sofarsolar - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solaranzeige-solaranzeige.yaml b/templates/release/en/meter/solaranzeige-solaranzeige.yaml new file mode 100644 index 0000000000..be8201b903 --- /dev/null +++ b/templates/release/en/meter/solaranzeige-solaranzeige.yaml @@ -0,0 +1,100 @@ +template: solaranzeige +product: + identifier: solaranzeige-solaranzeige + brand: Solaranzeige + description: Solaranzeige +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: solaranzeige + usage: grid + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + advanced: | + type: template + template: solaranzeige + usage: grid + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: pv + default: | + type: template + template: solaranzeige + usage: pv + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + advanced: | + type: template + template: solaranzeige + usage: pv + host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker + port: 1883 # Port, MQTT broker port (optional) + topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) + timeout: 30s # Timeout, Don't accept values older than this value (optional) + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: IP address or hostname of the MQTT broker + advanced: false + optional: false + - name: port + example: + default: 1883 + choice: [] + unit: + description: Port + help: MQTT broker port + advanced: false + optional: true + - name: topic + example: + default: solaranzeige/box1 + choice: [] + unit: + description: Topic + help: Topic (omit leading /) + advanced: false + optional: true + - name: timeout + example: 10s + default: 30s + choice: [] + unit: + description: Timeout + help: Don't accept values older than this value + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: true + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solaranzeige_0.yaml b/templates/release/en/meter/solaranzeige_0.yaml deleted file mode 100644 index ff3f41deeb..0000000000 --- a/templates/release/en/meter/solaranzeige_0.yaml +++ /dev/null @@ -1,43 +0,0 @@ -product: - brand: Solaranzeige - description: Solaranzeige -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: solaranzeige - usage: grid - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - advanced: | - type: template - template: solaranzeige - usage: grid - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: solaranzeige - usage: pv - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - advanced: | - type: template - template: solaranzeige - usage: pv - host: 192.0.2.2 # IP address or hostname, IP address or hostname of the MQTT broker - port: 1883 # Port, MQTT broker port (optional) - topic: solaranzeige/box1 # Topic, Topic (omit leading /) (optional) - timeout: 30s # Timeout, Don't accept values older than this value (optional) - user: # Username, e.g. email address, user id, etc. (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/meter/solaredge-hybrid-inverter.yaml b/templates/release/en/meter/solaredge-hybrid-inverter.yaml new file mode 100644 index 0000000000..47e8484b7f --- /dev/null +++ b/templates/release/en/meter/solaredge-hybrid-inverter.yaml @@ -0,0 +1,219 @@ +template: solaredge-hybrid +product: + identifier: solaredge-hybrid-inverter + brand: SolarEdge + description: Hybrid Inverter +capabilities: ["battery-control"] +description: | + Only one system can and may have a Modbus TCP connection to the inverter at the same time! + For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Remote". + +render: + - usage: grid + default: | + type: template + template: solaredge-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: solaredge-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional + watchdog: 60s # optional + - usage: pv + default: | + type: template + template: solaredge-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: solaredge-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: solaredge-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: solaredge-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional + capacity: 50 # Battery capacity (kWh), optional + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 1502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/solaredge-hybrid_0.yaml b/templates/release/en/meter/solaredge-hybrid_0.yaml deleted file mode 100644 index ee5bada3ac..0000000000 --- a/templates/release/en/meter/solaredge-hybrid_0.yaml +++ /dev/null @@ -1,161 +0,0 @@ -product: - brand: SolarEdge - description: Hybrid Inverter -capabilities: ["battery-control"] -description: | - Only one system can and may have a Modbus TCP connection to the inverter at the same time! - For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Remote". - -render: - - usage: grid - default: | - type: template - template: solaredge-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: solaredge-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional - watchdog: 60s # optional - - usage: pv - default: | - type: template - template: solaredge-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: solaredge-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: solaredge-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: solaredge-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional - capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional diff --git a/templates/release/en/meter/solaredge-inverter.yaml b/templates/release/en/meter/solaredge-inverter.yaml new file mode 100644 index 0000000000..6a3df4d161 --- /dev/null +++ b/templates/release/en/meter/solaredge-inverter.yaml @@ -0,0 +1,87 @@ +template: solaredge-inverter +product: + identifier: solaredge-inverter + brand: SolarEdge + description: Inverter +description: | + Only one system may access the inverter! +render: + - usage: grid + default: | + type: template + template: solaredge-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional + - usage: pv + default: | + type: template + template: solaredge-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 1502 # Port + timeout: 10s # Timeout, optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 1502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/solaredge-inverter_0.yaml b/templates/release/en/meter/solaredge-inverter_0.yaml deleted file mode 100644 index fee71b0b18..0000000000 --- a/templates/release/en/meter/solaredge-inverter_0.yaml +++ /dev/null @@ -1,56 +0,0 @@ -product: - brand: SolarEdge - description: Inverter -description: | - Only one system may access the inverter! -render: - - usage: grid - default: | - type: template - template: solaredge-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional - - usage: pv - default: | - type: template - template: solaredge-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 1502 # Port - timeout: 10s # Timeout, optional diff --git a/templates/release/en/meter/solarlog.yaml b/templates/release/en/meter/solarlog.yaml new file mode 100644 index 0000000000..74cd440bb1 --- /dev/null +++ b/templates/release/en/meter/solarlog.yaml @@ -0,0 +1,42 @@ +template: solarlog +product: + identifier: solarlog + description: Solarlog +description: | + We recommend to use this device for grid power values only, if no other device is available providing this data. + If you have a home battery installed, please do not use this device at all for grid power values. + +render: + - usage: grid + default: | + type: template + template: solarlog + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: solarlog + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solarlog_0.yaml b/templates/release/en/meter/solarlog_0.yaml deleted file mode 100644 index 698d7af565..0000000000 --- a/templates/release/en/meter/solarlog_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - description: Solarlog -description: | - We recommend to use this device for grid power values only, if no other device is available providing this data. - If you have a home battery installed, please do not use this device at all for grid power values. - -render: - - usage: grid - default: | - type: template - template: solarlog - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - - usage: pv - default: | - type: template - template: solarlog - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional diff --git a/templates/release/en/meter/solarman_0.yaml b/templates/release/en/meter/solarman_0.yaml deleted file mode 100644 index e8f58cb7c7..0000000000 --- a/templates/release/en/meter/solarman_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: IGEN Tech - description: Solarman Logger -render: - - usage: pv - default: | - type: template - template: solarman - usage: pv - host: 192.0.2.2 # IP address or hostname - user: admin # Username, e.g. email address, user id, etc. (optional) - password: admin # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml b/templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml new file mode 100644 index 0000000000..357d3ff7f7 --- /dev/null +++ b/templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml @@ -0,0 +1,120 @@ +template: solarmax-maxstorage +product: + identifier: solarmax-max-storage-max-storage-ultimate + brand: SolarMax + description: MAX.STORAGE / MAX.STORAGE Ultimate +capabilities: ["battery-control"] +description: | + For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. +render: + - usage: grid + default: | + type: template + template: solarmax-maxstorage + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solarmax-maxstorage + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + watchdog: 60s # optional + - usage: pv + default: | + type: template + template: solarmax-maxstorage + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solarmax-maxstorage + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + watchdog: 60s # optional + - usage: battery + default: | + type: template + template: solarmax-maxstorage + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: solarmax-maxstorage + usage: battery + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + watchdog: 60s # optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/solarmax-maxstorage_0.yaml b/templates/release/en/meter/solarmax-maxstorage_0.yaml deleted file mode 100644 index be7f036a9c..0000000000 --- a/templates/release/en/meter/solarmax-maxstorage_0.yaml +++ /dev/null @@ -1,75 +0,0 @@ -product: - brand: SolarMax - description: MAX.STORAGE / MAX.STORAGE Ultimate -capabilities: ["battery-control"] -description: | - For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. -render: - - usage: grid - default: | - type: template - template: solarmax-maxstorage - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solarmax-maxstorage - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - watchdog: 60s # optional - - usage: pv - default: | - type: template - template: solarmax-maxstorage - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solarmax-maxstorage - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional - - usage: battery - default: | - type: template - template: solarmax-maxstorage - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solarmax-maxstorage - usage: battery - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional diff --git a/templates/release/en/meter/solarmax-smt_0.yaml b/templates/release/en/meter/solarmax-smt_0.yaml deleted file mode 100644 index 177b29e4e3..0000000000 --- a/templates/release/en/meter/solarmax-smt_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SolarMax - description: SolarMax SMT -render: - - usage: pv - default: | - type: template - template: solarmax-smt - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/solarmax-solarmax-smt.yaml b/templates/release/en/meter/solarmax-solarmax-smt.yaml new file mode 100644 index 0000000000..f28a6b03f5 --- /dev/null +++ b/templates/release/en/meter/solarmax-solarmax-smt.yaml @@ -0,0 +1,33 @@ +template: solarmax-smt +product: + identifier: solarmax-solarmax-smt + brand: SolarMax + description: SolarMax SMT +render: + - usage: pv + default: | + type: template + template: solarmax-smt + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/solarmax-sp-series-inverter.yaml b/templates/release/en/meter/solarmax-sp-series-inverter.yaml new file mode 100644 index 0000000000..430c460089 --- /dev/null +++ b/templates/release/en/meter/solarmax-sp-series-inverter.yaml @@ -0,0 +1,33 @@ +template: senergy +product: + identifier: solarmax-sp-series-inverter + brand: SolarMax + description: SP Series Inverter +render: + - usage: pv + default: | + type: template + template: senergy + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/solarwatt-energymanager-pro.yaml b/templates/release/en/meter/solarwatt-energymanager-pro.yaml new file mode 100644 index 0000000000..c149af876c --- /dev/null +++ b/templates/release/en/meter/solarwatt-energymanager-pro.yaml @@ -0,0 +1,59 @@ +template: solarwatt +product: + identifier: solarwatt-energymanager-pro + brand: Solarwatt + description: EnergyManager Pro +render: + - usage: grid + default: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: battery + default: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP address or hostname + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solarwatt-energymanager.yaml b/templates/release/en/meter/solarwatt-energymanager.yaml new file mode 100644 index 0000000000..1ffad05d97 --- /dev/null +++ b/templates/release/en/meter/solarwatt-energymanager.yaml @@ -0,0 +1,59 @@ +template: solarwatt +product: + identifier: solarwatt-energymanager + brand: Solarwatt + description: EnergyManager +render: + - usage: grid + default: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: battery + default: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP address or hostname + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solarwatt-flex_0.yaml b/templates/release/en/meter/solarwatt-flex_0.yaml deleted file mode 100644 index 2971f54261..0000000000 --- a/templates/release/en/meter/solarwatt-flex_0.yaml +++ /dev/null @@ -1,41 +0,0 @@ -product: - brand: Solarwatt - description: Manager flex -description: | - Combines data of all connected PV inverters or batteries. - -render: - - usage: grid - default: | - type: template - template: solarwatt-flex - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt-flex - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: solarwatt-flex - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt-flex - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: battery - default: | - type: template - template: solarwatt-flex - usage: battery - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt-flex - usage: battery - host: 192.0.2.2 # IP address or hostname - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solarwatt-manager-flex.yaml b/templates/release/en/meter/solarwatt-manager-flex.yaml new file mode 100644 index 0000000000..2b511aa618 --- /dev/null +++ b/templates/release/en/meter/solarwatt-manager-flex.yaml @@ -0,0 +1,62 @@ +template: solarwatt-flex +product: + identifier: solarwatt-manager-flex + brand: Solarwatt + description: Manager flex +description: | + Combines data of all connected PV inverters or batteries. + +render: + - usage: grid + default: | + type: template + template: solarwatt-flex + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt-flex + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: solarwatt-flex + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt-flex + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: battery + default: | + type: template + template: solarwatt-flex + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt-flex + usage: battery + host: 192.0.2.2 # IP address or hostname + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml b/templates/release/en/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml new file mode 100644 index 0000000000..5bdc806f7f --- /dev/null +++ b/templates/release/en/meter/solarwatt-myreserve-matrix-lan-oder-powergateway.yaml @@ -0,0 +1,74 @@ +template: solarwatt-myreserve-matrix +product: + identifier: solarwatt-myreserve-matrix-lan-oder-powergateway + brand: Solarwatt + description: MyReserve Matrix (LAN oder PowerGateway) +render: + - usage: grid + default: | + type: template + template: solarwatt-myreserve-matrix + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + advanced: | + type: template + template: solarwatt-myreserve-matrix + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + - usage: pv + default: | + type: template + template: solarwatt-myreserve-matrix + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + advanced: | + type: template + template: solarwatt-myreserve-matrix + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + - usage: battery + default: | + type: template + template: solarwatt-myreserve-matrix + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + advanced: | + type: template + template: solarwatt-myreserve-matrix + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8080 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solarwatt-myreserve-matrix_0.yaml b/templates/release/en/meter/solarwatt-myreserve-matrix_0.yaml deleted file mode 100644 index 66aeb6cf01..0000000000 --- a/templates/release/en/meter/solarwatt-myreserve-matrix_0.yaml +++ /dev/null @@ -1,44 +0,0 @@ -product: - brand: Solarwatt - description: MyReserve Matrix (LAN oder PowerGateway) -render: - - usage: grid - default: | - type: template - template: solarwatt-myreserve-matrix - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - advanced: | - type: template - template: solarwatt-myreserve-matrix - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - - usage: pv - default: | - type: template - template: solarwatt-myreserve-matrix - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - advanced: | - type: template - template: solarwatt-myreserve-matrix - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - - usage: battery - default: | - type: template - template: solarwatt-myreserve-matrix - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - advanced: | - type: template - template: solarwatt-myreserve-matrix - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solarwatt-myreserve.yaml b/templates/release/en/meter/solarwatt-myreserve.yaml new file mode 100644 index 0000000000..12c6d813c4 --- /dev/null +++ b/templates/release/en/meter/solarwatt-myreserve.yaml @@ -0,0 +1,59 @@ +template: solarwatt +product: + identifier: solarwatt-myreserve + brand: Solarwatt + description: MyReserve +render: + - usage: grid + default: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: pv + host: 192.0.2.2 # IP address or hostname + - usage: battery + default: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: solarwatt + usage: battery + host: 192.0.2.2 # IP address or hostname + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solarwatt_0.yaml b/templates/release/en/meter/solarwatt_0.yaml deleted file mode 100644 index 50634a9b38..0000000000 --- a/templates/release/en/meter/solarwatt_0.yaml +++ /dev/null @@ -1,38 +0,0 @@ -product: - brand: Solarwatt - description: MyReserve -render: - - usage: grid - default: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: battery - default: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP address or hostname - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solarwatt_1.yaml b/templates/release/en/meter/solarwatt_1.yaml deleted file mode 100644 index bf7afd541f..0000000000 --- a/templates/release/en/meter/solarwatt_1.yaml +++ /dev/null @@ -1,38 +0,0 @@ -product: - brand: Solarwatt - description: EnergyManager, EnergyManager Pro -render: - - usage: grid - default: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt - usage: pv - host: 192.0.2.2 # IP address or hostname - - usage: battery - default: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP address or hostname - advanced: | - type: template - template: solarwatt - usage: battery - host: 192.0.2.2 # IP address or hostname - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solax-hybrid-cloud_0.yaml b/templates/release/en/meter/solax-hybrid-cloud_0.yaml deleted file mode 100644 index 7d86501701..0000000000 --- a/templates/release/en/meter/solax-hybrid-cloud_0.yaml +++ /dev/null @@ -1,49 +0,0 @@ -product: - brand: Solax - description: Hybrid-Inverter (Cloud) -description: | - The Solax hybrid inverter has to be registered in the SolaxCloud. - - **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. - -render: - - usage: grid - default: | - type: template - template: solax-hybrid-cloud - usage: grid - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') - serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number - advanced: | - type: template - template: solax-hybrid-cloud - usage: grid - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') - serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number - - usage: pv - default: | - type: template - template: solax-hybrid-cloud - usage: pv - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') - serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number - advanced: | - type: template - template: solax-hybrid-cloud - usage: pv - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') - serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number - - usage: battery - default: | - type: template - template: solax-hybrid-cloud - usage: battery - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') - serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number - advanced: | - type: template - template: solax-hybrid-cloud - usage: battery - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') - serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solax-hybrid-inverter-cloud.yaml b/templates/release/en/meter/solax-hybrid-inverter-cloud.yaml new file mode 100644 index 0000000000..a20c1b6030 --- /dev/null +++ b/templates/release/en/meter/solax-hybrid-inverter-cloud.yaml @@ -0,0 +1,79 @@ +template: solax-hybrid-cloud +product: + identifier: solax-hybrid-inverter-cloud + brand: Solax + description: Hybrid-Inverter (Cloud) +description: | + The Solax hybrid inverter has to be registered in the SolaxCloud. + + **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. + +render: + - usage: grid + default: | + type: template + template: solax-hybrid-cloud + usage: grid + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + advanced: | + type: template + template: solax-hybrid-cloud + usage: grid + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + - usage: pv + default: | + type: template + template: solax-hybrid-cloud + usage: pv + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + advanced: | + type: template + template: solax-hybrid-cloud + usage: pv + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + - usage: battery + default: | + type: template + template: solax-hybrid-cloud + usage: battery + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + advanced: | + type: template + template: solax-hybrid-cloud + usage: battery + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + capacity: 50 # Battery capacity (kWh), optional +params: + - name: tokenid + example: + default: + choice: [] + unit: + description: SolaxCloud TokenID + help: 'https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: ''20241028488283838'')' + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Serial number + help: https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + advanced: false + optional: false + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml b/templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml new file mode 100644 index 0000000000..e4abf0bc5f --- /dev/null +++ b/templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml @@ -0,0 +1,225 @@ +template: solax +product: + identifier: solax-hybrid-x1-x3-g3-g4 + brand: Solax + description: Hybrid X1/X3 G3/G4 +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + advanced: | + type: template + template: solax + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + storageunit: 1 # optional + - usage: pv + default: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + advanced: | + type: template + template: solax + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + storageunit: 1 # optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + advanced: | + type: template + template: solax + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + mppt3: false # The inverter has a third PV input (MPPT3), optional + storageunit: 1 # optional + capacity: 50 # Battery capacity (kWh), optional + defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: The inverter has a third PV input (MPPT3) + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: defaultmode + example: + default: 0 + choice: [] + unit: + description: Default mode for battery control + help: Inverter falls back to this mode after charging the battery or after stopping discharge. + advanced: true + optional: true +modbus: + baudrate: 19200 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/solax-inverter-cloud.yaml b/templates/release/en/meter/solax-inverter-cloud.yaml new file mode 100644 index 0000000000..195c81bec1 --- /dev/null +++ b/templates/release/en/meter/solax-inverter-cloud.yaml @@ -0,0 +1,37 @@ +template: solax-inverter-cloud +product: + identifier: solax-inverter-cloud + brand: Solax + description: Inverter (Cloud) +description: | + The Solax inverter has to be registered in the SolaxCloud. + + **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. + +render: + - usage: pv + default: | + type: template + template: solax-inverter-cloud + usage: pv + tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') + serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number +params: + - name: tokenid + example: + default: + choice: [] + unit: + description: SolaxCloud TokenID + help: 'https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: ''20241028488283838'')' + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Serial number + help: https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/solax-inverter-cloud_0.yaml b/templates/release/en/meter/solax-inverter-cloud_0.yaml deleted file mode 100644 index cc392d9a7e..0000000000 --- a/templates/release/en/meter/solax-inverter-cloud_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Solax - description: Inverter (Cloud) -description: | - The Solax inverter has to be registered in the SolaxCloud. - - **Attention**: Values can only be fetched every 150s and then also can be 5 minutes old. Charging by PV will not be optimal because of this! Only use as fallback if no local access is available. - -render: - - usage: pv - default: | - type: template - template: solax-inverter-cloud - usage: pv - tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') - serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number diff --git a/templates/release/en/meter/solax_0.yaml b/templates/release/en/meter/solax_0.yaml deleted file mode 100644 index b376dc5bdb..0000000000 --- a/templates/release/en/meter/solax_0.yaml +++ /dev/null @@ -1,158 +0,0 @@ -product: - brand: Solax - description: Hybrid X1/X3 G3/G4 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - advanced: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - advanced: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - advanced: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) diff --git a/templates/release/en/meter/solax_1.yaml b/templates/release/en/meter/solax_1.yaml deleted file mode 100644 index afa38d5a6d..0000000000 --- a/templates/release/en/meter/solax_1.yaml +++ /dev/null @@ -1,158 +0,0 @@ -product: - brand: Qcells - description: Q.HOME ESS HYB-G3 -capabilities: ["battery-control"] -render: - - usage: grid - default: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - advanced: | - type: template - template: solax - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional - - usage: pv - default: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - advanced: | - type: template - template: solax - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - advanced: | - type: template - template: solax - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional - capacity: 50 # Battery capacity (kWh), optional - defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) diff --git a/templates/release/en/meter/solinteng.yaml b/templates/release/en/meter/solinteng.yaml new file mode 100644 index 0000000000..9aca1cfd8e --- /dev/null +++ b/templates/release/en/meter/solinteng.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: solinteng + brand: Solinteng +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/solis-hybrid-s_0.yaml b/templates/release/en/meter/solis-hybrid-s_0.yaml deleted file mode 100644 index e698d3ec94..0000000000 --- a/templates/release/en/meter/solis-hybrid-s_0.yaml +++ /dev/null @@ -1,111 +0,0 @@ -product: - brand: Ginlong - description: Solis Hybrid Inverter (S Series) -render: - - usage: grid - default: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solis-hybrid-s_1.yaml b/templates/release/en/meter/solis-hybrid-s_1.yaml deleted file mode 100644 index 94b6330bbe..0000000000 --- a/templates/release/en/meter/solis-hybrid-s_1.yaml +++ /dev/null @@ -1,111 +0,0 @@ -product: - brand: Axitec - description: AXIhycon 12-15H -render: - - usage: grid - default: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid-s - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solis-hybrid_0.yaml b/templates/release/en/meter/solis-hybrid_0.yaml deleted file mode 100644 index c2dc055071..0000000000 --- a/templates/release/en/meter/solis-hybrid_0.yaml +++ /dev/null @@ -1,111 +0,0 @@ -product: - brand: Ginlong - description: Solis Hybrid Inverter (RHI series) -render: - - usage: grid - default: | - type: template - template: solis-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: solis-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: solis-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/solis_0.yaml b/templates/release/en/meter/solis_0.yaml deleted file mode 100644 index 060c4546dc..0000000000 --- a/templates/release/en/meter/solis_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Ginlong - description: Solis Inverter -render: - - usage: grid - default: | - type: template - template: solis - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: solis - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sonnen-comfort.yaml b/templates/release/en/meter/sonnen-comfort.yaml new file mode 100644 index 0000000000..e8997210d0 --- /dev/null +++ b/templates/release/en/meter/sonnen-comfort.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-comfort + brand: Sonnen + description: comfort +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sonnen-eco-5.yaml b/templates/release/en/meter/sonnen-eco-5.yaml new file mode 100644 index 0000000000..325a1185d1 --- /dev/null +++ b/templates/release/en/meter/sonnen-eco-5.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-eco-5 + brand: Sonnen + description: eco 5 +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sonnen-eco-6.yaml b/templates/release/en/meter/sonnen-eco-6.yaml new file mode 100644 index 0000000000..0dc8a04dc0 --- /dev/null +++ b/templates/release/en/meter/sonnen-eco-6.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-eco-6 + brand: Sonnen + description: eco 6 +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sonnen-oem-6-5.yaml b/templates/release/en/meter/sonnen-oem-6-5.yaml new file mode 100644 index 0000000000..1e7a3f38f9 --- /dev/null +++ b/templates/release/en/meter/sonnen-oem-6-5.yaml @@ -0,0 +1,96 @@ +template: sonnenbatterie-eco56 +product: + identifier: sonnen-oem-6-5 + brand: Sonnen + description: oem 6.5 +render: + - usage: grid + default: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: pv + default: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) + - usage: battery + default: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + advanced: | + type: template + template: sonnenbatterie-eco56 + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 7979 # Port, optional + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) + cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 7979 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: cache + example: 5m + default: 5s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/sonnen-sonnenbatterie.yaml b/templates/release/en/meter/sonnen-sonnenbatterie.yaml new file mode 100644 index 0000000000..e12e323998 --- /dev/null +++ b/templates/release/en/meter/sonnen-sonnenbatterie.yaml @@ -0,0 +1,111 @@ +template: sonnenbatterie +product: + identifier: sonnen-sonnenbatterie + brand: Sonnen + description: sonnenBatterie +capabilities: ["battery-control"] +description: | + For active battery control, the "JSON Write API" must be activated via the sonnenBatterie web interface (under Software-Integration) and the API token generated there must be entered in the battery configuration under `token`. + The two operating modes supported for the sonnenBatterie are “self-consumption” (default) and “time-of-use”. The mode can be adapted to the configuration of the sonnenBatterie via the 'defaultmode' parameter. + The power for grid charging can be adapted to the inverter power of the sonnenBatterie via the `maxchargepower` parameter. + +render: + - usage: grid + default: | + type: template + template: sonnenbatterie + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + advanced: | + type: template + template: sonnenbatterie + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + - usage: pv + default: | + type: template + template: sonnenbatterie + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + advanced: | + type: template + template: sonnenbatterie + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + - usage: battery + default: | + type: template + template: sonnenbatterie + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + token: # API Token (required for active battery control) (optional) + advanced: | + type: template + template: sonnenbatterie + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 8080 # Port, optional + token: # API Token (required for active battery control) (optional) + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: 3300 # Maximum charge power (W), For forced charging of the battery. (optional) + defaultmode: self-consumption # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. [self-consumption, time-of-use] +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8080 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: token + example: + default: + choice: [] + unit: + description: + help: API Token (required for active battery control) + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: 3300 + choice: [] + unit: W + description: Maximum charge power + help: For forced charging of the battery. + advanced: true + optional: true + - name: defaultmode + example: + default: self-consumption + choice: ['self-consumption', 'time-of-use'] + unit: + description: Default mode for battery control + help: Inverter falls back to this mode after charging the battery or after stopping discharge. + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/sonnenbatterie-eco56_0.yaml b/templates/release/en/meter/sonnenbatterie-eco56_0.yaml deleted file mode 100644 index a7b18d6e3e..0000000000 --- a/templates/release/en/meter/sonnenbatterie-eco56_0.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Sonnen - description: comfort, eco 5, eco 6, oem 6.5 -render: - - usage: grid - default: | - type: template - template: sonnenbatterie-eco56 - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 7979 # Port, optional - advanced: | - type: template - template: sonnenbatterie-eco56 - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 7979 # Port, optional - cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - - usage: pv - default: | - type: template - template: sonnenbatterie-eco56 - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 7979 # Port, optional - advanced: | - type: template - template: sonnenbatterie-eco56 - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 7979 # Port, optional - cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - - usage: battery - default: | - type: template - template: sonnenbatterie-eco56 - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 7979 # Port, optional - advanced: | - type: template - template: sonnenbatterie-eco56 - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 7979 # Port, optional - capacity: 50 # Battery capacity (kWh), optional - maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) - cache: 5s # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/meter/sonnenbatterie_0.yaml b/templates/release/en/meter/sonnenbatterie_0.yaml deleted file mode 100644 index 191daa0c38..0000000000 --- a/templates/release/en/meter/sonnenbatterie_0.yaml +++ /dev/null @@ -1,54 +0,0 @@ -product: - brand: Sonnen - description: sonnenBatterie -capabilities: ["battery-control"] -description: | - For active battery control, the "JSON Write API" must be activated via the sonnenBatterie web interface (under Software-Integration) and the API token generated there must be entered in the battery configuration under `token`. - The two operating modes supported for the sonnenBatterie are “self-consumption” (default) and “time-of-use”. The mode can be adapted to the configuration of the sonnenBatterie via the 'defaultmode' parameter. - The power for grid charging can be adapted to the inverter power of the sonnenBatterie via the `maxchargepower` parameter. - -render: - - usage: grid - default: | - type: template - template: sonnenbatterie - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - advanced: | - type: template - template: sonnenbatterie - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - - usage: pv - default: | - type: template - template: sonnenbatterie - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - advanced: | - type: template - template: sonnenbatterie - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - - usage: battery - default: | - type: template - template: sonnenbatterie - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional) - advanced: | - type: template - template: sonnenbatterie - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional) - capacity: 50 # Battery capacity (kWh), optional - maxchargepower: 3300 # Maximum charge power (W), For forced charging of the battery. (optional) - defaultmode: self-consumption # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. [self-consumption, time-of-use] diff --git a/templates/release/en/meter/st-ems.yaml b/templates/release/en/meter/st-ems.yaml new file mode 100644 index 0000000000..9bb492504b --- /dev/null +++ b/templates/release/en/meter/st-ems.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: st-ems + brand: St-ems +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/steca-coolcept-flex.yaml b/templates/release/en/meter/steca-coolcept-flex.yaml new file mode 100644 index 0000000000..7bed96e98d --- /dev/null +++ b/templates/release/en/meter/steca-coolcept-flex.yaml @@ -0,0 +1,22 @@ +template: kostal-piko-mp-plus +product: + identifier: steca-coolcept-flex + brand: Steca + description: coolcept fleX +render: + - usage: pv + default: | + type: template + template: kostal-piko-mp-plus + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/storaxe_0.yaml b/templates/release/en/meter/storaxe_0.yaml deleted file mode 100644 index 6534c984f8..0000000000 --- a/templates/release/en/meter/storaxe_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Ads-tec - description: StoraXe -render: - - usage: battery - default: | - type: template - template: storaxe - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: storaxe - usage: battery - - # Modbus TCP - modbus: tcpip - id: 2 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/sungrow-hybrid_0.yaml b/templates/release/en/meter/sungrow-hybrid_0.yaml deleted file mode 100644 index 5e90620af8..0000000000 --- a/templates/release/en/meter/sungrow-hybrid_0.yaml +++ /dev/null @@ -1,157 +0,0 @@ -product: - brand: Sungrow - description: SH Series Hybrid Inverter -capabilities: ["battery-control"] -description: | - Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmware. Older versions do not provide all required data (power, state of charge). -render: - - usage: grid - default: | - type: template - template: sungrow-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: sungrow-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - - usage: pv - default: | - type: template - template: sungrow-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: sungrow-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: sungrow-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - advanced: | - type: template - template: sungrow-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - timeout: 10s # Timeout, optional - capacity: 50 # Battery capacity (kWh), optional - maxchargepower: # Maximum charge power (W), Maximum charge power for forced charging of the battery in watts. (0 to automatically set the value of the maximum BDC rated power) (optional) diff --git a/templates/release/en/meter/sungrow-inverter_0.yaml b/templates/release/en/meter/sungrow-inverter_0.yaml deleted file mode 100644 index 3bc755a5b5..0000000000 --- a/templates/release/en/meter/sungrow-inverter_0.yaml +++ /dev/null @@ -1,52 +0,0 @@ -product: - brand: Sungrow - description: SG Series Inverter -render: - - usage: grid - default: | - type: template - template: sungrow-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sungrow-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sungrow-sg-series-inverter.yaml b/templates/release/en/meter/sungrow-sg-series-inverter.yaml new file mode 100644 index 0000000000..5616956caf --- /dev/null +++ b/templates/release/en/meter/sungrow-sg-series-inverter.yaml @@ -0,0 +1,74 @@ +template: sungrow-inverter +product: + identifier: sungrow-sg-series-inverter + brand: Sungrow + description: SG Series Inverter +render: + - usage: grid + default: | + type: template + template: sungrow-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sungrow-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml b/templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml new file mode 100644 index 0000000000..2cd4be840b --- /dev/null +++ b/templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml @@ -0,0 +1,215 @@ +template: sungrow-hybrid +product: + identifier: sungrow-sh-series-hybrid-inverter + brand: Sungrow + description: SH Series Hybrid Inverter +capabilities: ["battery-control"] +description: | + Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmware. Older versions do not provide all required data (power, state of charge). +render: + - usage: grid + default: | + type: template + template: sungrow-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: sungrow-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + - usage: pv + default: | + type: template + template: sungrow-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: sungrow-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: sungrow-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + advanced: | + type: template + template: sungrow-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + timeout: 10s # Timeout, optional + capacity: 50 # Battery capacity (kWh), optional + maxchargepower: # Maximum charge power (W), Maximum charge power for forced charging of the battery in watts. (0 to automatically set the value of the maximum BDC rated power) (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: maxchargepower + example: + default: + choice: [] + unit: W + description: Maximum charge power + help: Maximum charge power for forced charging of the battery in watts. (0 to automatically set the value of the maximum BDC rated power) + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunspec-battery-control_0.yaml b/templates/release/en/meter/sunspec-battery-control_0.yaml deleted file mode 100644 index 77e9733a09..0000000000 --- a/templates/release/en/meter/sunspec-battery-control_0.yaml +++ /dev/null @@ -1,55 +0,0 @@ -product: - description: SunSpec Battery (Model 802) - group: Generic support -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sunspec-battery-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-battery-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/sunspec-battery-model-124.yaml b/templates/release/en/meter/sunspec-battery-model-124.yaml new file mode 100644 index 0000000000..cbfedd7b32 --- /dev/null +++ b/templates/release/en/meter/sunspec-battery-model-124.yaml @@ -0,0 +1,94 @@ +template: sunspec-inverter-control +product: + identifier: sunspec-battery-model-124 + description: SunSpec Battery (Model 124) + group: Generic support +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sunspec-inverter-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: maxchargerate + example: + default: 100 + choice: [] + unit: '%' + description: Maximum charge power + help: For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunspec-battery-model-802.yaml b/templates/release/en/meter/sunspec-battery-model-802.yaml new file mode 100644 index 0000000000..f45126a893 --- /dev/null +++ b/templates/release/en/meter/sunspec-battery-model-802.yaml @@ -0,0 +1,104 @@ +template: sunspec-battery-control +product: + identifier: sunspec-battery-model-802 + description: SunSpec Battery (Model 802) + group: Generic support +capabilities: ["battery-control"] +render: + - usage: battery + default: | + type: template + template: sunspec-battery-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-battery-control + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunspec-hybrid-inverter.yaml b/templates/release/en/meter/sunspec-hybrid-inverter.yaml new file mode 100644 index 0000000000..99374f041d --- /dev/null +++ b/templates/release/en/meter/sunspec-hybrid-inverter.yaml @@ -0,0 +1,187 @@ +template: sunspec-hybrid +product: + identifier: sunspec-hybrid-inverter + description: SunSpec Hybrid Inverter + group: Generic support +render: + - usage: grid + default: | + type: template + template: sunspec-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-hybrid + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-hybrid + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: sunspec-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-hybrid + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunspec-hybrid_0.yaml b/templates/release/en/meter/sunspec-hybrid_0.yaml deleted file mode 100644 index 86e1699f16..0000000000 --- a/templates/release/en/meter/sunspec-hybrid_0.yaml +++ /dev/null @@ -1,147 +0,0 @@ -product: - description: SunSpec Hybrid Inverter - group: Generic support -render: - - usage: grid - default: | - type: template - template: sunspec-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-hybrid - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-hybrid - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - - usage: battery - default: | - type: template - template: sunspec-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-hybrid - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/sunspec-inverter-control_0.yaml b/templates/release/en/meter/sunspec-inverter-control_0.yaml deleted file mode 100644 index a5f309d951..0000000000 --- a/templates/release/en/meter/sunspec-inverter-control_0.yaml +++ /dev/null @@ -1,54 +0,0 @@ -product: - description: SunSpec Battery (Model 124) - group: Generic support -capabilities: ["battery-control"] -render: - - usage: battery - default: | - type: template - template: sunspec-inverter-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter-control - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/sunspec-inverter.yaml b/templates/release/en/meter/sunspec-inverter.yaml new file mode 100644 index 0000000000..b75479d342 --- /dev/null +++ b/templates/release/en/meter/sunspec-inverter.yaml @@ -0,0 +1,177 @@ +template: sunspec-inverter +product: + identifier: sunspec-inverter + description: SunSpec Inverter + group: Generic support +render: + - usage: grid + default: | + type: template + template: sunspec-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sunspec-inverter + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sunspec-inverter + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunspec-inverter_0.yaml b/templates/release/en/meter/sunspec-inverter_0.yaml deleted file mode 100644 index 10ff704939..0000000000 --- a/templates/release/en/meter/sunspec-inverter_0.yaml +++ /dev/null @@ -1,146 +0,0 @@ -product: - description: SunSpec Inverter - group: Generic support -render: - - usage: grid - default: | - type: template - template: sunspec-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: battery - default: | - type: template - template: sunspec-inverter - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: sunspec-inverter - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/sunspec-meter.yaml b/templates/release/en/meter/sunspec-meter.yaml new file mode 100644 index 0000000000..7e626429cd --- /dev/null +++ b/templates/release/en/meter/sunspec-meter.yaml @@ -0,0 +1,43 @@ +template: sunspec-meter +product: + identifier: sunspec-meter + description: SunSpec Meter +render: + - usage: grid + default: | + type: template + template: sunspec-meter + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sunspec-meter + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunspec-meter_0.yaml b/templates/release/en/meter/sunspec-meter_0.yaml deleted file mode 100644 index a37a482b6d..0000000000 --- a/templates/release/en/meter/sunspec-meter_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: SunSpec Meter -render: - - usage: grid - default: | - type: template - template: sunspec-meter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-meter - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sunspec-meter_1.yaml b/templates/release/en/meter/sunspec-meter_1.yaml deleted file mode 100644 index 676b669491..0000000000 --- a/templates/release/en/meter/sunspec-meter_1.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Fronius - description: Smartmeter (via Inverter) -render: - - usage: grid - default: | - type: template - template: sunspec-meter - usage: grid - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: pv - default: | - type: template - template: sunspec-meter - usage: pv - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml b/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml new file mode 100644 index 0000000000..ab07bd15e0 --- /dev/null +++ b/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml @@ -0,0 +1,212 @@ +template: deye-hybrid-3p +product: + identifier: sunsynk-3p-hybrid-inverter + brand: Sunsynk + description: 3p hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + - usage: battery + default: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-3p + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml b/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml new file mode 100644 index 0000000000..5c15e7c1ff --- /dev/null +++ b/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml @@ -0,0 +1,236 @@ +template: deye-hybrid-hp3 +product: + identifier: sunsynk-hp3-hybrid-inverter + brand: Sunsynk + description: hp3 hybrid inverter +capabilities: ["battery-control"] +render: + - usage: grid + default: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + includegenport: # Treat GEN port as solar input, optional + - usage: pv + default: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + includegenport: # Treat GEN port as solar input, optional + - usage: battery + default: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-hybrid-hp3 + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + storageunit: 1 # optional + capacity: 50 # Battery capacity (kWh), optional + minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + includegenport: # Treat GEN port as solar input, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: + help: + advanced: true + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: 20 + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: 95 + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: includegenport + example: + default: + choice: [] + unit: + description: Treat GEN port as solar input + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunsynk-micro-inverter.yaml b/templates/release/en/meter/sunsynk-micro-inverter.yaml new file mode 100644 index 0000000000..69b8cde633 --- /dev/null +++ b/templates/release/en/meter/sunsynk-micro-inverter.yaml @@ -0,0 +1,73 @@ +template: deye-mi +product: + identifier: sunsynk-micro-inverter + brand: Sunsynk + description: Micro inverter +render: + - usage: pv + default: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-mi + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml b/templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml new file mode 100644 index 0000000000..77cc7a0a8a --- /dev/null +++ b/templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: deye-storage +product: + identifier: sunsynk-storage-hybrid-inverter + brand: Sunsynk + description: Storage (hybrid) inverter +render: + - usage: pv + default: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + - usage: grid + default: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: deye-storage + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunsynk-string-inverter.yaml b/templates/release/en/meter/sunsynk-string-inverter.yaml new file mode 100644 index 0000000000..ed15c76121 --- /dev/null +++ b/templates/release/en/meter/sunsynk-string-inverter.yaml @@ -0,0 +1,50 @@ +template: deye-string +product: + identifier: sunsynk-string-inverter + brand: Sunsynk + description: String inverter +render: + - usage: pv + default: | + type: template + template: deye-string + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/sunway.yaml b/templates/release/en/meter/sunway.yaml new file mode 100644 index 0000000000..be374737ea --- /dev/null +++ b/templates/release/en/meter/sunway.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: sunway + brand: Sunway +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/tapo_0.yaml b/templates/release/en/meter/tapo_0.yaml deleted file mode 100644 index 8aa3aa63fc..0000000000 --- a/templates/release/en/meter/tapo_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: TP-Link - description: Tapo P-Series Smart Plug - group: Switchable sockets -render: - - usage: pv - default: | - type: template - template: tapo - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros diff --git a/templates/release/en/meter/tasmota-3p_0.yaml b/templates/release/en/meter/tasmota-3p_0.yaml deleted file mode 100644 index ff3d6e34ee..0000000000 --- a/templates/release/en/meter/tasmota-3p_0.yaml +++ /dev/null @@ -1,39 +0,0 @@ -product: - brand: Tasmota - description: three phase - group: Switchable sockets -description: | - Meter channels 1,2,3 must be used. -render: - - usage: grid - default: | - type: template - template: tasmota-3p - usage: grid - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: tasmota-3p - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: battery - default: | - type: template - template: tasmota-3p - usage: battery - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: charge - default: | - type: template - template: tasmota-3p - usage: charge - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml b/templates/release/en/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml new file mode 100644 index 0000000000..15175bbf0b --- /dev/null +++ b/templates/release/en/meter/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.yaml @@ -0,0 +1,91 @@ +template: tasmota-sml +product: + identifier: tasmota-sml-ir-reader-for-smartmeters-e-g-hichi + brand: Tasmota + description: SML IR-reader for smartmeters e.g. Hichi +description: | + To be able to read the values of the smart meter for evcc correctly, the IR reader script must be changed so that the following JSON tags are generated: + - **SML** as the group name of the read parameters + - **Total_in** for the total consumption in KWh (4 decimal places) + - **Total_out** for the total feed-in in KWh (4 decimal places) + - **Power_curr** for the current consumption or the current feed-in in W (0 decimal places) + + A corresponding IR reader script looks like this: + ``` + >D + >B + =>sensor53 r + >M 1 + // highlight-next-line + +1,3,s,16,9600,SML + // highlight-next-line + 1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 + // highlight-next-line + 1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 + // highlight-next-line + 1,77070100100700ff@1,Verbrauch,W,Power_curr,0 + 1,77070100600100ff@#,Zählernummer,,Meter_Id,0 + # + ``` + +render: + - usage: grid + default: | + type: template + template: tasmota-sml + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: pv + default: | + type: template + template: tasmota-sml + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: battery + default: | + type: template + template: tasmota-sml + usage: battery + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: charge + default: | + type: template + template: tasmota-sml + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: admin is default + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/tasmota-sml_0.yaml b/templates/release/en/meter/tasmota-sml_0.yaml deleted file mode 100644 index 8f0b4b0614..0000000000 --- a/templates/release/en/meter/tasmota-sml_0.yaml +++ /dev/null @@ -1,61 +0,0 @@ -product: - brand: Tasmota - description: SML IR-reader for smartmeters e.g. Hichi -description: | - To be able to read the values of the smart meter for evcc correctly, the IR reader script must be changed so that the following JSON tags are generated: - - **SML** as the group name of the read parameters - - **Total_in** for the total consumption in KWh (4 decimal places) - - **Total_out** for the total feed-in in KWh (4 decimal places) - - **Power_curr** for the current consumption or the current feed-in in W (0 decimal places) - - A corresponding IR reader script looks like this: - ``` - >D - >B - =>sensor53 r - >M 1 - // highlight-next-line - +1,3,s,16,9600,SML - // highlight-next-line - 1,77070100010800ff@1000,Gesamtverbrauch,KWh,Total_in,4 - // highlight-next-line - 1,77070100020800ff@1000,Gesamteinspeisung,KWh,Total_out,4 - // highlight-next-line - 1,77070100100700ff@1,Verbrauch,W,Power_curr,0 - 1,77070100600100ff@#,Zählernummer,,Meter_Id,0 - # - ``` - -render: - - usage: grid - default: | - type: template - template: tasmota-sml - usage: grid - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: pv - default: | - type: template - template: tasmota-sml - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: battery - default: | - type: template - template: tasmota-sml - usage: battery - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - - usage: charge - default: | - type: template - template: tasmota-sml - usage: charge - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml b/templates/release/en/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml new file mode 100644 index 0000000000..9a93f1c7f2 --- /dev/null +++ b/templates/release/en/meter/tasmota-tasmota-1-phase-plus-sml-meter.yaml @@ -0,0 +1,80 @@ +template: tasmota +product: + identifier: tasmota-tasmota-1-phase-plus-sml-meter + brand: Tasmota + description: Tasmota (1 Phase + SML Meter) + group: Switchable sockets +render: + - usage: grid + default: | + type: template + template: tasmota + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 1 # Channel number, Meterchannel number (1-8) + - usage: pv + default: | + type: template + template: tasmota + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 1 # Channel number, Meterchannel number (1-8) + - usage: battery + default: | + type: template + template: tasmota + usage: battery + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 1 # Channel number, Meterchannel number (1-8) + - usage: charge + default: | + type: template + template: tasmota + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 1 # Channel number, Meterchannel number (1-8) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: admin is default + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true + - name: channel + example: + default: 1 + choice: [] + unit: + description: Channel number + help: Meterchannel number (1-8) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/tasmota-three-phase.yaml b/templates/release/en/meter/tasmota-three-phase.yaml new file mode 100644 index 0000000000..4edf7dc339 --- /dev/null +++ b/templates/release/en/meter/tasmota-three-phase.yaml @@ -0,0 +1,69 @@ +template: tasmota-3p +product: + identifier: tasmota-three-phase + brand: Tasmota + description: three phase + group: Switchable sockets +description: | + Meter channels 1,2,3 must be used. +render: + - usage: grid + default: | + type: template + template: tasmota-3p + usage: grid + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: pv + default: | + type: template + template: tasmota-3p + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: battery + default: | + type: template + template: tasmota-3p + usage: battery + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + - usage: charge + default: | + type: template + template: tasmota-3p + usage: charge + host: 192.0.2.2 # IP address or hostname + user: # Username, admin is default (optional) + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: admin is default + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/tasmota_0.yaml b/templates/release/en/meter/tasmota_0.yaml deleted file mode 100644 index ffc7aa02df..0000000000 --- a/templates/release/en/meter/tasmota_0.yaml +++ /dev/null @@ -1,41 +0,0 @@ -product: - brand: Tasmota - description: Tasmota (1 Phase + SML Meter) - group: Switchable sockets -render: - - usage: grid - default: | - type: template - template: tasmota - usage: grid - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 1 # Channel number, Meterchannel number (1-8) - - usage: pv - default: | - type: template - template: tasmota - usage: pv - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 1 # Channel number, Meterchannel number (1-8) - - usage: battery - default: | - type: template - template: tasmota - usage: battery - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 1 # Channel number, Meterchannel number (1-8) - - usage: charge - default: | - type: template - template: tasmota - usage: charge - host: 192.0.2.2 # IP address or hostname - user: # Username, admin is default (optional) - password: # Password, Use single quotes in case of leading zeros (optional) - channel: 1 # Channel number, Meterchannel number (1-8) diff --git a/templates/release/en/meter/tesla-powerwall.yaml b/templates/release/en/meter/tesla-powerwall.yaml new file mode 100644 index 0000000000..9d19d7b9b4 --- /dev/null +++ b/templates/release/en/meter/tesla-powerwall.yaml @@ -0,0 +1,127 @@ +template: tesla-powerwall +product: + identifier: tesla-powerwall + brand: Tesla + description: Powerwall +capabilities: ["battery-control"] +description: | + To use the optional battery control you need to generate a `refresh` token for communicating with the Tesla API. + + The following apps allow to create the token: + - [Auth app for Tesla (iOS)](https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613#?platform=iphone) + - [Tesla Tokens (Android)](https://play.google.com/store/apps/details?id=net.leveugle.teslatokens) + - [Tesla Auth (macOS, Linux)](https://github.com/adriankumpf/tesla_auth) + +render: + - usage: grid + default: | + type: template + template: tesla-powerwall + usage: grid + host: 192.0.2.2 # IP address or hostname + password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. + refreshToken: # optional + siteId: # optional product identifier of the energy site, use to override autodectction (optional) + advanced: | + type: template + template: tesla-powerwall + usage: grid + host: 192.0.2.2 # IP address or hostname + password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. + refreshToken: # optional + siteId: # optional product identifier of the energy site, use to override autodectction (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: tesla-powerwall + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. + refreshToken: # optional + siteId: # optional product identifier of the energy site, use to override autodectction (optional) + advanced: | + type: template + template: tesla-powerwall + usage: pv + host: 192.0.2.2 # IP address or hostname + password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. + refreshToken: # optional + siteId: # optional product identifier of the energy site, use to override autodectction (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: battery + default: | + type: template + template: tesla-powerwall + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. + refreshToken: # optional + siteId: # optional product identifier of the energy site, use to override autodectction (optional) + advanced: | + type: template + template: tesla-powerwall + usage: battery + host: 192.0.2.2 # IP address or hostname + password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. + refreshToken: # optional + siteId: # optional product identifier of the energy site, use to override autodectction (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: siteId + example: + default: + choice: [] + unit: + description: + help: optional product identifier of the energy site, use to override autodectction + advanced: false + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/tesla-powerwall_0.yaml b/templates/release/en/meter/tesla-powerwall_0.yaml deleted file mode 100644 index c2595a9d0a..0000000000 --- a/templates/release/en/meter/tesla-powerwall_0.yaml +++ /dev/null @@ -1,70 +0,0 @@ -product: - brand: Tesla - description: Powerwall -capabilities: ["battery-control"] -description: | - To use the optional battery control you need to generate a `refresh` token for communicating with the Tesla API. - - The following apps allow to create the token: - - [Auth app for Tesla (iOS)](https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613#?platform=iphone) - - [Tesla Tokens (Android)](https://play.google.com/store/apps/details?id=net.leveugle.teslatokens) - - [Tesla Auth (macOS, Linux)](https://github.com/adriankumpf/tesla_auth) - -render: - - usage: grid - default: | - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - advanced: | - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - advanced: | - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: battery - default: | - type: template - template: tesla-powerwall - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - advanced: | - type: template - template: tesla-powerwall - usage: battery - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/thor_0.yaml b/templates/release/en/meter/thor_0.yaml deleted file mode 100644 index 8c2453302e..0000000000 --- a/templates/release/en/meter/thor_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: my-PV - description: AC•THOR -render: - - usage: aux - default: | - type: template - template: thor - usage: aux - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/tibber-pulse.yaml b/templates/release/en/meter/tibber-pulse.yaml new file mode 100644 index 0000000000..a81ed20044 --- /dev/null +++ b/templates/release/en/meter/tibber-pulse.yaml @@ -0,0 +1,33 @@ +template: tibber-pulse +product: + identifier: tibber-pulse + brand: Tibber + description: Pulse +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: tibber-pulse + usage: grid + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional +params: + - name: token + example: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: homeid + example: 96a14971-525a-4420-aae9-e5aedaa129ff + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/tibber-pulse_0.yaml b/templates/release/en/meter/tibber-pulse_0.yaml deleted file mode 100644 index 6da33b3f35..0000000000 --- a/templates/release/en/meter/tibber-pulse_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Tibber - description: Pulse -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: tibber-pulse - usage: grid - token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE - homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional diff --git a/templates/release/en/meter/tp-link-h-series-smart-plug.yaml b/templates/release/en/meter/tp-link-h-series-smart-plug.yaml new file mode 100644 index 0000000000..82419a06a3 --- /dev/null +++ b/templates/release/en/meter/tp-link-h-series-smart-plug.yaml @@ -0,0 +1,23 @@ +template: tplink +product: + identifier: tp-link-h-series-smart-plug + brand: TP-Link + description: H-Series Smart Plug + group: Switchable sockets +render: + - usage: pv + default: | + type: template + template: tplink + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/tp-link-tapo-p-series-smart-plug.yaml b/templates/release/en/meter/tp-link-tapo-p-series-smart-plug.yaml new file mode 100644 index 0000000000..aec8e0d438 --- /dev/null +++ b/templates/release/en/meter/tp-link-tapo-p-series-smart-plug.yaml @@ -0,0 +1,43 @@ +template: tapo +product: + identifier: tp-link-tapo-p-series-smart-plug + brand: TP-Link + description: Tapo P-Series Smart Plug + group: Switchable sockets +render: + - usage: pv + default: | + type: template + template: tapo + usage: pv + host: 192.0.2.2 # IP address or hostname + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/tplink_0.yaml b/templates/release/en/meter/tplink_0.yaml deleted file mode 100644 index b20e61dbee..0000000000 --- a/templates/release/en/meter/tplink_0.yaml +++ /dev/null @@ -1,11 +0,0 @@ -product: - brand: TP-Link - description: H-Series Smart Plug - group: Switchable sockets -render: - - usage: pv - default: | - type: template - template: tplink - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/tq-em420_0.yaml b/templates/release/en/meter/tq-em420_0.yaml deleted file mode 100644 index b6a2d77db2..0000000000 --- a/templates/release/en/meter/tq-em420_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: TQ - description: Energy Manager EM420 -render: - - usage: grid - default: | - type: template - template: tq-em420 - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 80 # Port, optional - device: local # API Device Path, JSON-API -> Data Endpoint (optional) - token: ey... # Access token, Access token for EM420 (Create in Profile -> Access tokens) diff --git a/templates/release/en/meter/tq-em_0.yaml b/templates/release/en/meter/tq-em_0.yaml deleted file mode 100644 index 8ab8314c67..0000000000 --- a/templates/release/en/meter/tq-em_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: TQ - description: Energy Manager EM2xx/EM3xx -render: - - usage: grid - default: | - type: template - template: tq-em - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 80 # Port, optional - password: # Password, Use single quotes in case of leading zeros (optional) diff --git a/templates/release/en/meter/tq-energy-manager-em2xx-em3xx.yaml b/templates/release/en/meter/tq-energy-manager-em2xx-em3xx.yaml new file mode 100644 index 0000000000..a30afc18f4 --- /dev/null +++ b/templates/release/en/meter/tq-energy-manager-em2xx-em3xx.yaml @@ -0,0 +1,42 @@ +template: tq-em +product: + identifier: tq-energy-manager-em2xx-em3xx + brand: TQ + description: Energy Manager EM2xx/EM3xx +render: + - usage: grid + default: | + type: template + template: tq-em + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 80 # Port, optional + password: # Password, Use single quotes in case of leading zeros (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 80 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/tq-energy-manager-em420.yaml b/templates/release/en/meter/tq-energy-manager-em420.yaml new file mode 100644 index 0000000000..2ecbbcba30 --- /dev/null +++ b/templates/release/en/meter/tq-energy-manager-em420.yaml @@ -0,0 +1,52 @@ +template: tq-em420 +product: + identifier: tq-energy-manager-em420 + brand: TQ + description: Energy Manager EM420 +render: + - usage: grid + default: | + type: template + template: tq-em420 + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 80 # Port, optional + device: local # API Device Path, JSON-API -> Data Endpoint (optional) + token: ey... # Access token, Access token for EM420 (Create in Profile -> Access tokens) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 80 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: device + example: + default: local + choice: [] + unit: + description: API Device Path + help: JSON-API -> Data Endpoint + advanced: false + optional: true + - name: token + example: ey... + default: + choice: [] + unit: + description: Access token + help: Access token for EM420 (Create in Profile -> Access tokens) + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/varta-element.yaml b/templates/release/en/meter/varta-element.yaml new file mode 100644 index 0000000000..eac635c831 --- /dev/null +++ b/templates/release/en/meter/varta-element.yaml @@ -0,0 +1,76 @@ +template: varta +product: + identifier: varta-element + brand: VARTA + description: element +description: | + PV only available with PV sensor +render: + - usage: grid + default: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + - usage: battery + default: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/varta-pulse-neo.yaml b/templates/release/en/meter/varta-pulse-neo.yaml new file mode 100644 index 0000000000..1782087058 --- /dev/null +++ b/templates/release/en/meter/varta-pulse-neo.yaml @@ -0,0 +1,76 @@ +template: varta +product: + identifier: varta-pulse-neo + brand: VARTA + description: pulse neo +description: | + PV only available with PV sensor +render: + - usage: grid + default: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + - usage: battery + default: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/varta-pulse.yaml b/templates/release/en/meter/varta-pulse.yaml new file mode 100644 index 0000000000..32111518e5 --- /dev/null +++ b/templates/release/en/meter/varta-pulse.yaml @@ -0,0 +1,76 @@ +template: varta +product: + identifier: varta-pulse + brand: VARTA + description: pulse +description: | + PV only available with PV sensor +render: + - usage: grid + default: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + - usage: pv + default: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + - usage: battery + default: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: varta + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/varta_0.yaml b/templates/release/en/meter/varta_0.yaml deleted file mode 100644 index 2b1fffb1ba..0000000000 --- a/templates/release/en/meter/varta_0.yaml +++ /dev/null @@ -1,46 +0,0 @@ -product: - brand: VARTA - description: pulse, pulse neo, element -description: | - PV only available with PV sensor -render: - - usage: grid - default: | - type: template - template: varta - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: varta - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - - usage: pv - default: | - type: template - template: varta - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: varta - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - - usage: battery - default: | - type: template - template: varta - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: varta - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - capacity: 50 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/victron-em24.yaml b/templates/release/en/meter/victron-em24.yaml new file mode 100644 index 0000000000..7bc995f01d --- /dev/null +++ b/templates/release/en/meter/victron-em24.yaml @@ -0,0 +1,64 @@ +template: cg-em24 +product: + identifier: victron-em24 + brand: Victron + description: EM24 +description: | + EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. + +render: + - usage: grid + default: | + type: template + template: cg-em24 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/victron-em24_e1.yaml b/templates/release/en/meter/victron-em24_e1.yaml new file mode 100644 index 0000000000..ce3ea0b240 --- /dev/null +++ b/templates/release/en/meter/victron-em24_e1.yaml @@ -0,0 +1,48 @@ +template: cg-em24_e1 +product: + identifier: victron-em24_e1 + brand: Victron + description: EM24_E1 +description: | + EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. + The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) + +render: + - usage: grid + default: | + type: template + template: cg-em24_e1 + usage: grid + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-em24_e1 + usage: charge + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + host: 192.0.2.2 + id: 1 + modbus: tcpip + port: 502 + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/victron-em530-em540.yaml b/templates/release/en/meter/victron-em530-em540.yaml new file mode 100644 index 0000000000..57fc28e720 --- /dev/null +++ b/templates/release/en/meter/victron-em530-em540.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: victron-em530-em540 + brand: Victron + description: EM530/EM540 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/victron-energy.yaml b/templates/release/en/meter/victron-energy.yaml new file mode 100644 index 0000000000..8008ced095 --- /dev/null +++ b/templates/release/en/meter/victron-energy.yaml @@ -0,0 +1,122 @@ +template: victron-energy +product: + identifier: victron-energy + brand: Victron + description: Energy +capabilities: ["battery-control"] +description: | + For grid usage, a grid meter VRM instance is require to enabled load management. +render: + - usage: grid + default: | + type: template + template: victron-energy + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) + advanced: | + type: template + template: victron-energy + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: pv + default: | + type: template + template: victron-energy + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: victron-energy + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + - usage: battery + default: | + type: template + template: victron-energy + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + advanced: | + type: template + template: victron-energy + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + capacity: 50 # Battery capacity (kWh), optional + minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) + maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 502 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: meterid + example: + default: + choice: [] + unit: + description: + help: Grid meter VRM instance- can be read out in VRM portal or via remoteUI. + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: maxacpower + example: 5000 + default: 0 + choice: [] + unit: W + description: Maximum AC power of the hybrid inverter + help: + advanced: true + optional: true + - name: minsoc + example: 25 + default: + choice: [] + unit: '%' + description: Minimum charge + help: Lower limit when discharging the battery in normal operation + advanced: true + optional: true + - name: maxsoc + example: 95 + default: + choice: [] + unit: '%' + description: Maximum charge + help: Upper limit when charging the battery from the grid + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/victron-energy_0.yaml b/templates/release/en/meter/victron-energy_0.yaml deleted file mode 100644 index c505657b10..0000000000 --- a/templates/release/en/meter/victron-energy_0.yaml +++ /dev/null @@ -1,56 +0,0 @@ -product: - brand: Victron - description: Energy -capabilities: ["battery-control"] -description: | - For grid usage, a grid meter VRM instance is require to enabled load management. -render: - - usage: grid - default: | - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) - advanced: | - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: pv - default: | - type: template - template: victron-energy - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: victron-energy - usage: pv - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - - usage: battery - default: | - type: template - template: victron-energy - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - advanced: | - type: template - template: victron-energy - usage: battery - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - capacity: 50 # Battery capacity (kWh), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) diff --git a/templates/release/en/meter/victron-et340.yaml b/templates/release/en/meter/victron-et340.yaml new file mode 100644 index 0000000000..0f3d3b8836 --- /dev/null +++ b/templates/release/en/meter/victron-et340.yaml @@ -0,0 +1,74 @@ +template: cg-emt3xx +product: + identifier: victron-et340 + brand: Victron + description: ET340 +render: + - usage: grid + default: | + type: template + template: cg-emt3xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: cg-emt3xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/volkszaehler-http_0.yaml b/templates/release/en/meter/volkszaehler-http_0.yaml deleted file mode 100644 index 629855051e..0000000000 --- a/templates/release/en/meter/volkszaehler-http_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Volkszähler - description: HTTP API - group: Generic support -render: - - usage: grid - default: | - type: template - template: volkszaehler-http - usage: grid - url: # URL of the middleware's "data" context, Example: http://zaehler.network.local:8080/api/data (optional) - uuid: diff --git a/templates/release/en/meter/volkszaehler-importexport_0.yaml b/templates/release/en/meter/volkszaehler-importexport_0.yaml deleted file mode 100644 index afd01bc3ad..0000000000 --- a/templates/release/en/meter/volkszaehler-importexport_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Volkszähler - description: HTTP API, Import & Export - group: Generic support -render: - - usage: grid - default: | - type: template - template: volkszaehler-importexport - usage: grid - url: # URL of the middleware's "data" context, The URL is for example: http://zaehler.network.local:8080/api/data (optional) - importuuid: - exportuuid: diff --git a/templates/release/en/meter/volkszaehler-ws_0.yaml b/templates/release/en/meter/volkszaehler-ws_0.yaml deleted file mode 100644 index 01609205c6..0000000000 --- a/templates/release/en/meter/volkszaehler-ws_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Volkszähler - description: WebSocket API - group: Generic support -requirements: ["skiptest"] -render: - - usage: grid - default: | - type: template - template: volkszaehler-ws - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 8082 # Port, optional - uuid: diff --git a/templates/release/en/meter/volkszahler-http-api-import-and-export.yaml b/templates/release/en/meter/volkszahler-http-api-import-and-export.yaml new file mode 100644 index 0000000000..a479cab3c2 --- /dev/null +++ b/templates/release/en/meter/volkszahler-http-api-import-and-export.yaml @@ -0,0 +1,43 @@ +template: volkszaehler-importexport +product: + identifier: volkszahler-http-api-import-and-export + brand: Volkszähler + description: HTTP API, Import & Export + group: Generic support +render: + - usage: grid + default: | + type: template + template: volkszaehler-importexport + usage: grid + url: # URL of the middleware's "data" context, The URL is for example: http://zaehler.network.local:8080/api/data (optional) + importuuid: + exportuuid: +params: + - name: url + example: + default: + choice: [] + unit: + description: URL of the middleware's "data" context + help: 'The URL is for example: http://zaehler.network.local:8080/api/data' + advanced: false + optional: true + - name: importuuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: exportuuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/volkszahler-http-api.yaml b/templates/release/en/meter/volkszahler-http-api.yaml new file mode 100644 index 0000000000..99c37ef933 --- /dev/null +++ b/templates/release/en/meter/volkszahler-http-api.yaml @@ -0,0 +1,33 @@ +template: volkszaehler-http +product: + identifier: volkszahler-http-api + brand: Volkszähler + description: HTTP API + group: Generic support +render: + - usage: grid + default: | + type: template + template: volkszaehler-http + usage: grid + url: # URL of the middleware's "data" context, Example: http://zaehler.network.local:8080/api/data (optional) + uuid: +params: + - name: url + example: + default: + choice: [] + unit: + description: URL of the middleware's "data" context + help: 'Example: http://zaehler.network.local:8080/api/data' + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/volkszahler-websocket-api.yaml b/templates/release/en/meter/volkszahler-websocket-api.yaml new file mode 100644 index 0000000000..8b7127e2ab --- /dev/null +++ b/templates/release/en/meter/volkszahler-websocket-api.yaml @@ -0,0 +1,44 @@ +template: volkszaehler-ws +product: + identifier: volkszahler-websocket-api + brand: Volkszähler + description: WebSocket API + group: Generic support +requirements: ["skiptest"] +render: + - usage: grid + default: | + type: template + template: volkszaehler-ws + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8082 # Port, optional + uuid: +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8082 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/vzlogger.yaml b/templates/release/en/meter/vzlogger.yaml new file mode 100644 index 0000000000..f561382def --- /dev/null +++ b/templates/release/en/meter/vzlogger.yaml @@ -0,0 +1,159 @@ +template: vzlogger +product: + identifier: vzlogger + description: vzlogger + group: Generic support +render: + - usage: grid + default: | + type: template + template: vzlogger + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8081 # Port, optional + uuid: + advanced: | + type: template + template: vzlogger + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8081 # Port, optional + uuid: + scale: 1 # Scale factor, Multiply by this value (optional) + l1currentuuid: # The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0), optional + l2currentuuid: # The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0), optional + l3currentuuid: # The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0), optional + l1poweruuid: # The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0), optional + l2poweruuid: # The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0), optional + l3poweruuid: # The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0), optional + l1voltageuuid: # The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0), optional + l2voltageuuid: # The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0), optional + l3voltageuuid: # The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0), optional + cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: + default: 8081 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: scale + example: + default: 1 + choice: [] + unit: + description: Scale factor + help: Multiply by this value + advanced: true + optional: true + - name: l1currentuuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0) + help: + advanced: true + optional: true + - name: l2currentuuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0) + help: + advanced: true + optional: true + - name: l3currentuuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0) + help: + advanced: true + optional: true + - name: l1poweruuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0) + help: + advanced: true + optional: true + - name: l2poweruuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0) + help: + advanced: true + optional: true + - name: l3poweruuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0) + help: + advanced: true + optional: true + - name: l1voltageuuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0) + help: + advanced: true + optional: true + - name: l2voltageuuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0) + help: + advanced: true + optional: true + - name: l3voltageuuid + example: + default: + choice: [] + unit: + description: The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0) + help: + advanced: true + optional: true + - name: cache + example: 5m + default: 1s + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/vzlogger_0.yaml b/templates/release/en/meter/vzlogger_0.yaml deleted file mode 100644 index 647ea0d5d5..0000000000 --- a/templates/release/en/meter/vzlogger_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - description: vzlogger - group: Generic support -render: - - usage: grid - default: | - type: template - template: vzlogger - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 8081 # Port, optional - uuid: - advanced: | - type: template - template: vzlogger - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 8081 # Port, optional - uuid: - scale: 1 # Scale factor, Multiply by this value (optional) - l1currentuuid: # The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0), optional - l2currentuuid: # The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0), optional - l3currentuuid: # The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0), optional - l1poweruuid: # The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0), optional - l2poweruuid: # The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0), optional - l3poweruuid: # The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0), optional - l1voltageuuid: # The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0), optional - l2voltageuuid: # The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0), optional - l3voltageuuid: # The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0), optional - cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/meter/wago-879-30xx.yaml b/templates/release/en/meter/wago-879-30xx.yaml new file mode 100644 index 0000000000..9e3a3ece70 --- /dev/null +++ b/templates/release/en/meter/wago-879-30xx.yaml @@ -0,0 +1,61 @@ +template: wago-879-30xx +product: + identifier: wago-879-30xx + brand: Wago + description: 879-30xx +render: + - usage: grid + default: | + type: template + template: wago-879-30xx + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: wago-879-30xx + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/wago-879-30xx_0.yaml b/templates/release/en/meter/wago-879-30xx_0.yaml deleted file mode 100644 index 4b3f34dd35..0000000000 --- a/templates/release/en/meter/wago-879-30xx_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Wago - description: 879-30xx -render: - - usage: grid - default: | - type: template - template: wago-879-30xx - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - usage: charge - default: | - type: template - template: wago-879-30xx - usage: charge - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port diff --git a/templates/release/en/meter/wattsonic.yaml b/templates/release/en/meter/wattsonic.yaml new file mode 100644 index 0000000000..9aae7f95f2 --- /dev/null +++ b/templates/release/en/meter/wattsonic.yaml @@ -0,0 +1,151 @@ +template: wattsonic +product: + identifier: wattsonic + brand: Wattsonic +render: + - usage: grid + default: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: pv + default: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + delay: 100ms # optional + - usage: battery + default: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: wattsonic + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 247 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 247 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional + delay: 100ms # optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true + - name: delay + example: + default: 100ms + choice: [] + unit: + description: + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 247 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/wattsonic_0.yaml b/templates/release/en/meter/wattsonic_0.yaml deleted file mode 100644 index ce4ad627ac..0000000000 --- a/templates/release/en/meter/wattsonic_0.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: Wattsonic -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional diff --git a/templates/release/en/meter/wattsonic_1.yaml b/templates/release/en/meter/wattsonic_1.yaml deleted file mode 100644 index eab7143b0e..0000000000 --- a/templates/release/en/meter/wattsonic_1.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: Sunway -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional diff --git a/templates/release/en/meter/wattsonic_2.yaml b/templates/release/en/meter/wattsonic_2.yaml deleted file mode 100644 index 9c26d16676..0000000000 --- a/templates/release/en/meter/wattsonic_2.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: Solinteng -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional diff --git a/templates/release/en/meter/wattsonic_3.yaml b/templates/release/en/meter/wattsonic_3.yaml deleted file mode 100644 index ee4278c707..0000000000 --- a/templates/release/en/meter/wattsonic_3.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: A-Tronix -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional diff --git a/templates/release/en/meter/wattsonic_4.yaml b/templates/release/en/meter/wattsonic_4.yaml deleted file mode 100644 index 44bd73bc2a..0000000000 --- a/templates/release/en/meter/wattsonic_4.yaml +++ /dev/null @@ -1,112 +0,0 @@ -product: - brand: St-ems -render: - - usage: grid - default: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: pv - default: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - delay: 100ms # optional - - usage: battery - default: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - advanced: | - type: template - template: wattsonic - usage: battery - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional diff --git a/templates/release/en/meter/weidmuller-em110-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em110-rtu-2p.yaml new file mode 100644 index 0000000000..e5d38d0886 --- /dev/null +++ b/templates/release/en/meter/weidmuller-em110-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm220_230 +product: + identifier: weidmuller-em110-rtu-2p + brand: Weidmüller + description: EM110-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron-sdm220_230 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm220_230 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/weidmuller-em111-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em111-rtu-2p.yaml new file mode 100644 index 0000000000..07c0b80e23 --- /dev/null +++ b/templates/release/en/meter/weidmuller-em111-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron-sdm220_230 +product: + identifier: weidmuller-em111-rtu-2p + brand: Weidmüller + description: EM111-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron-sdm220_230 + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron-sdm220_230 + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/weidmuller-em120-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em120-rtu-2p.yaml new file mode 100644 index 0000000000..b1cb3fc002 --- /dev/null +++ b/templates/release/en/meter/weidmuller-em120-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: weidmuller-em120-rtu-2p + brand: Weidmüller + description: EM120-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/weidmuller-em122-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em122-rtu-2p.yaml new file mode 100644 index 0000000000..415863aac2 --- /dev/null +++ b/templates/release/en/meter/weidmuller-em122-rtu-2p.yaml @@ -0,0 +1,61 @@ +template: eastron +product: + identifier: weidmuller-em122-rtu-2p + brand: Weidmüller + description: EM122-RTU-2P +render: + - usage: grid + default: | + type: template + template: eastron + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: charge + default: | + type: template + template: eastron + usage: charge + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: + help: + advanced: false + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/youless-energy-monitor.yaml b/templates/release/en/meter/youless-energy-monitor.yaml new file mode 100644 index 0000000000..bca068a502 --- /dev/null +++ b/templates/release/en/meter/youless-energy-monitor.yaml @@ -0,0 +1,31 @@ +template: youless +product: + identifier: youless-energy-monitor + brand: Youless + description: Energy Monitor +description: | + An externally connected S0 generation meter is required to record the solar production. + +render: + - usage: grid + default: | + type: template + template: youless + usage: grid + host: 192.0.2.2 # IP address or hostname + - usage: pv + default: | + type: template + template: youless + usage: pv + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/youless_0.yaml b/templates/release/en/meter/youless_0.yaml deleted file mode 100644 index 3d4b310f3d..0000000000 --- a/templates/release/en/meter/youless_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Youless - description: Energy Monitor -description: | - An externally connected S0 generation meter is required to record the solar production. - -render: - - usage: grid - default: | - type: template - template: youless - usage: grid - host: 192.0.2.2 # IP address or hostname - - usage: pv - default: | - type: template - template: youless - usage: pv - host: 192.0.2.2 # IP address or hostname diff --git a/templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml b/templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml new file mode 100644 index 0000000000..8755b73e99 --- /dev/null +++ b/templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: zcs-azzurro-hybrid-inverter + brand: ZCS Azzurro + description: Hybrid Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/zcs-azzurro-inverter.yaml b/templates/release/en/meter/zcs-azzurro-inverter.yaml new file mode 100644 index 0000000000..c4df9aa401 --- /dev/null +++ b/templates/release/en/meter/zcs-azzurro-inverter.yaml @@ -0,0 +1,177 @@ +template: sofarsolar +product: + identifier: zcs-azzurro-inverter + brand: ZCS Azzurro + description: Inverter +render: + - usage: grid + default: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: grid + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: pv + default: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: pv + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + - usage: battery + default: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + advanced: | + type: template + template: sofarsolar + usage: battery + + # RS485 via adapter (Modbus RTU) + modbus: rs485serial + id: 1 + device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse + baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 + comset: "8N1" # Kommunikationsparameter für den Adapter + + # RS485 via TCP/IP (Modbus RTU) + modbus: rs485tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true +modbus: + baudrate: 9600 + comset: 8N1 + device: /dev/ttyUSB0 + host: 192.0.2.2 + id: 1 + port: 502 + rs485serial: true + rs485tcpip: true + tcpip: true \ No newline at end of file diff --git a/templates/release/en/meter/zendure-hyper-2000.yaml b/templates/release/en/meter/zendure-hyper-2000.yaml new file mode 100644 index 0000000000..c4ac734274 --- /dev/null +++ b/templates/release/en/meter/zendure-hyper-2000.yaml @@ -0,0 +1,88 @@ +template: zendure +product: + identifier: zendure-hyper-2000 + brand: Zendure + description: Hyper 2000 +requirements: ["skiptest"] +render: + - usage: pv + default: | + type: template + template: zendure + usage: pv + account: dev@zendure.com + serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device + region: EU # [EU, Global] + timeout: 10s # Timeout, optional + advanced: | + type: template + template: zendure + usage: pv + account: dev@zendure.com + serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device + region: EU # [EU, Global] + timeout: 10s # Timeout, optional + - usage: battery + default: | + type: template + template: zendure + usage: battery + account: dev@zendure.com + serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device + region: EU # [EU, Global] + timeout: 10s # Timeout, optional + advanced: | + type: template + template: zendure + usage: battery + account: dev@zendure.com + serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device + region: EU # [EU, Global] + timeout: 10s # Timeout, optional + capacity: 2 # Battery capacity (kWh), optional +params: + - name: account + example: dev@zendure.com + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: serial + example: VU5D99F74021B04 + default: + choice: [] + unit: + description: + help: You can find this in the Zendure App in the settings of the device + advanced: false + optional: false + - name: region + example: + default: EU + choice: ['EU', 'Global'] + unit: + description: + help: + advanced: false + optional: false + - name: timeout + example: 10s + default: + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: capacity + example: 50 + default: 2 + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/meter/zendure_0.yaml b/templates/release/en/meter/zendure_0.yaml deleted file mode 100644 index a0dec95e1f..0000000000 --- a/templates/release/en/meter/zendure_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Zendure - description: Hyper 2000 -requirements: ["skiptest"] -render: - - usage: pv - default: | - type: template - template: zendure - usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] - timeout: 10s # Timeout, optional - advanced: | - type: template - template: zendure - usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] - timeout: 10s # Timeout, optional - - usage: battery - default: | - type: template - template: zendure - usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] - timeout: 10s # Timeout, optional - advanced: | - type: template - template: zendure - usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] - timeout: 10s # Timeout, optional - capacity: 2 # Battery capacity (kWh), optional diff --git a/templates/release/en/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml b/templates/release/en/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml new file mode 100644 index 0000000000..c16e4c51d5 --- /dev/null +++ b/templates/release/en/meter/zuidwijk-slimmelezer-plus-in-luxembourg.yaml @@ -0,0 +1,24 @@ +template: slimmelezer-luxembourg +product: + identifier: zuidwijk-slimmelezer-plus-in-luxembourg + brand: Zuidwijk + description: SlimmeLezer(+) in Luxembourg +description: | + Slimmelezer devices use different sensor names in Luxembourg. +render: + - usage: grid + default: | + type: template + template: slimmelezer-luxembourg + usage: grid + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/zuidwijk-slimmelezer-plus-v2.yaml b/templates/release/en/meter/zuidwijk-slimmelezer-plus-v2.yaml new file mode 100644 index 0000000000..69caa52974 --- /dev/null +++ b/templates/release/en/meter/zuidwijk-slimmelezer-plus-v2.yaml @@ -0,0 +1,24 @@ +template: slimmelezer-V2 +product: + identifier: zuidwijk-slimmelezer-plus-v2 + brand: Zuidwijk + description: SlimmeLezer(+) V2 +description: | + More recent slimmelezer devices use a different configuration. Try this template if the other one fails. +render: + - usage: grid + default: | + type: template + template: slimmelezer-V2 + usage: grid + host: 192.0.2.2 # IP address or hostname +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/meter/zuidwijk-slimmelezer-plus.yaml b/templates/release/en/meter/zuidwijk-slimmelezer-plus.yaml new file mode 100644 index 0000000000..16fa4bf451 --- /dev/null +++ b/templates/release/en/meter/zuidwijk-slimmelezer-plus.yaml @@ -0,0 +1,37 @@ +template: slimmelezer +product: + identifier: zuidwijk-slimmelezer-plus + brand: Zuidwijk + description: SlimmeLezer(+) +render: + - usage: grid + default: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP address or hostname + advanced: | + type: template + template: slimmelezer + usage: grid + host: 192.0.2.2 # IP address or hostname + scale: 1000 # Scale factor, Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: scale + example: 1 | 10 | 100 | 1000 + default: 1000 + choice: [] + unit: + description: Scale factor + help: Use scale of 1000 for Zuidwijk Slimmelezer. Use scale 1 for ESPHome DSMR and mhendriks P1 Dongle + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/en/tariff/amber-electric.yaml b/templates/release/en/tariff/amber-electric.yaml new file mode 100644 index 0000000000..73847d9b8b --- /dev/null +++ b/templates/release/en/tariff/amber-electric.yaml @@ -0,0 +1,77 @@ +template: amber +product: + identifier: amber-electric + brand: Amber Electric + group: Dynamic electricity price +countries: ["AU"] +render: + - default: | + type: template + template: amber + token: # optional + siteid: # optional + channel: # optional + advanced: | + type: template + template: amber + token: # optional + siteid: # optional + channel: # optional + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: siteid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: channel + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: true + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/amber_0.yaml b/templates/release/en/tariff/amber_0.yaml deleted file mode 100644 index 75fc5db1e1..0000000000 --- a/templates/release/en/tariff/amber_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Amber Electric - group: Dynamic electricity price -countries: ["AU"] -render: - - default: | - type: template - template: amber - token: # optional - siteid: # optional - channel: # optional - advanced: | - type: template - template: amber - token: # optional - siteid: # optional - channel: # optional - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/awattar.yaml b/templates/release/en/tariff/awattar.yaml new file mode 100644 index 0000000000..625ef55c35 --- /dev/null +++ b/templates/release/en/tariff/awattar.yaml @@ -0,0 +1,55 @@ +template: awattar +product: + identifier: awattar + brand: Awattar + group: Dynamic electricity price +countries: ["DE", "AT"] +render: + - default: | + type: template + template: awattar + region: AT # [DE, AT] + advanced: | + type: template + template: awattar + region: AT # [DE, AT] + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: region + example: AT + default: + choice: ['DE', 'AT'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/awattar_0.yaml b/templates/release/en/tariff/awattar_0.yaml deleted file mode 100644 index 13219b380b..0000000000 --- a/templates/release/en/tariff/awattar_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Awattar - group: Dynamic electricity price -countries: ["DE", "AT"] -render: - - default: | - type: template - template: awattar - region: AT # [DE, AT] - advanced: | - type: template - template: awattar - region: AT # [DE, AT] - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/electricity-maps-commercial-api.yaml b/templates/release/en/tariff/electricity-maps-commercial-api.yaml new file mode 100644 index 0000000000..fe9a867ea9 --- /dev/null +++ b/templates/release/en/tariff/electricity-maps-commercial-api.yaml @@ -0,0 +1,44 @@ +template: electricitymaps +product: + identifier: electricity-maps-commercial-api + brand: Electricity Maps + description: Commercial API + group: CO₂ forecast +requirements: ["skiptest"] +description: | + CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. +render: + - default: | + type: template + template: electricitymaps + uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) address + token: + zone: DE # see https://api.electricitymap.org/v3/zones +params: + - name: uri + example: https://api-access.electricitymaps.com/2w...1g/ + default: + choice: [] + unit: + description: URI + help: HTTP(S) address + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + description: + help: see https://api.electricitymap.org/v3/zones + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/tariff/electricity-maps-free-api.yaml b/templates/release/en/tariff/electricity-maps-free-api.yaml new file mode 100644 index 0000000000..1baf6253c0 --- /dev/null +++ b/templates/release/en/tariff/electricity-maps-free-api.yaml @@ -0,0 +1,34 @@ +template: electricitymaps-free +product: + identifier: electricity-maps-free-api + brand: Electricity Maps + description: Free API + group: CO₂ forecast +requirements: ["skiptest"] +description: | + CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. +render: + - default: | + type: template + template: electricitymaps-free + token: + zone: DE # see https://api.electricitymap.org/v3/zones +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + description: + help: see https://api.electricitymap.org/v3/zones + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/tariff/electricitymaps-free_0.yaml b/templates/release/en/tariff/electricitymaps-free_0.yaml deleted file mode 100644 index 2724053163..0000000000 --- a/templates/release/en/tariff/electricitymaps-free_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Electricity Maps - description: Free API - group: CO₂ forecast -requirements: ["skiptest"] -description: | - CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. -render: - - default: | - type: template - template: electricitymaps-free - token: - zone: DE # see https://api.electricitymap.org/v3/zones diff --git a/templates/release/en/tariff/electricitymaps_0.yaml b/templates/release/en/tariff/electricitymaps_0.yaml deleted file mode 100644 index 141d236a5a..0000000000 --- a/templates/release/en/tariff/electricitymaps_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Electricity Maps - description: Commercial API - group: CO₂ forecast -requirements: ["skiptest"] -description: | - CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. -render: - - default: | - type: template - template: electricitymaps - uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) address - token: - zone: DE # see https://api.electricitymap.org/v3/zones diff --git a/templates/release/en/tariff/energinet.yaml b/templates/release/en/tariff/energinet.yaml new file mode 100644 index 0000000000..bf3d80f1b3 --- /dev/null +++ b/templates/release/en/tariff/energinet.yaml @@ -0,0 +1,56 @@ +template: energinet +product: + identifier: energinet + brand: Energinet + group: Dynamic electricity price +countries: ["DK"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: energinet + region: dk1 # [dk1, dk2] + advanced: | + type: template + template: energinet + region: dk1 # [dk1, dk2] + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: region + example: dk1 + default: + choice: ['dk1', 'dk2'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/energinet_0.yaml b/templates/release/en/tariff/energinet_0.yaml deleted file mode 100644 index 2a27ee410f..0000000000 --- a/templates/release/en/tariff/energinet_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: Energinet - group: Dynamic electricity price -countries: ["DK"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: energinet - region: dk1 # [dk1, dk2] - advanced: | - type: template - template: energinet - region: dk1 # [dk1, dk2] - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/energy-charts-api_0.yaml b/templates/release/en/tariff/energy-charts-api_0.yaml deleted file mode 100644 index f846ebb79b..0000000000 --- a/templates/release/en/tariff/energy-charts-api_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Fraunhofer ISE - group: Dynamic electricity price -countries: ["EU"] -requirements: ["skiptest"] -description: | - Day-ahead forecast of energy prices (per kWh) on the exchange. No prior registration for https://api.energy-charts.info/ necessary. Can be used for dynamic electricity tariffs, for example, where the supplier does not yet offer a price forecast on the customer interface. -render: - - default: | - type: template - template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] - advanced: | - type: template - template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/enever.yaml b/templates/release/en/tariff/enever.yaml new file mode 100644 index 0000000000..130da727b6 --- /dev/null +++ b/templates/release/en/tariff/enever.yaml @@ -0,0 +1,77 @@ +template: enever +product: + identifier: enever + brand: Enever + group: Dynamic electricity price +countries: ["NL"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: enever + token: + provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + advanced: | + type: template + template: enever + token: + provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) + interval: 3h # optional +params: + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: provider + example: + default: + choice: ['', 'AA', 'AIP', 'ANWB', 'BE', 'EE', 'EN', 'EVO', 'EZ', 'FR', 'GSL', 'MDE', 'NE', 'PE', 'TI', 'VDB', 'VON', 'WE', 'ZG', 'ZP'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true + - name: interval + example: + default: 3h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/enever_0.yaml b/templates/release/en/tariff/enever_0.yaml deleted file mode 100644 index 494b84df7c..0000000000 --- a/templates/release/en/tariff/enever_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Enever - group: Dynamic electricity price -countries: ["NL"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] - advanced: | - type: template - template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) - interval: 3h # optional diff --git a/templates/release/en/tariff/entso-e.yaml b/templates/release/en/tariff/entso-e.yaml new file mode 100644 index 0000000000..b17690125a --- /dev/null +++ b/templates/release/en/tariff/entso-e.yaml @@ -0,0 +1,70 @@ +template: entsoe +product: + identifier: entso-e + brand: ENTSO-E + group: Dynamic electricity price +countries: ["EU"] +description: | + Day-ahead prices for the European electricity market. See https://transparency.entsoe.eu for more information. + Basis for many dynamic tariffs. + +render: + - default: | + type: template + template: entsoe + securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + advanced: | + type: template + template: entsoe + securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: securitytoken + example: + default: + choice: [] + unit: + description: + help: Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation + advanced: false + optional: true + - name: domain + example: BZN|DE-LU + default: + choice: [] + unit: + description: + help: see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas + advanced: false + optional: true + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/entsoe_0.yaml b/templates/release/en/tariff/entsoe_0.yaml deleted file mode 100644 index c050019d08..0000000000 --- a/templates/release/en/tariff/entsoe_0.yaml +++ /dev/null @@ -1,22 +0,0 @@ -product: - brand: ENTSO-E - group: Dynamic electricity price -countries: ["EU"] -description: | - Day-ahead prices for the European electricity market. See https://transparency.entsoe.eu for more information. - Basis for many dynamic tariffs. - -render: - - default: | - type: template - template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) - advanced: | - type: template - template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/forecast-solar.yaml b/templates/release/en/tariff/forecast-solar.yaml new file mode 100644 index 0000000000..e5adec0c06 --- /dev/null +++ b/templates/release/en/tariff/forecast-solar.yaml @@ -0,0 +1,101 @@ +template: forecast-solar +product: + identifier: forecast-solar + brand: Forecast.Solar + group: PV forecast +requirements: ["skiptest"] +description: | + [forecast.solar](https://forecast.solar) can be used for free. Paid plans can also be used by specifying an API key. +render: + - default: | + type: template + template: forecast-solar + lat: 55.7351 # Latitude + lon: 9.1275 # Longitude + dec: 25 # Decline, 0 = horizontal, 90 = vertical + kwp: 9.8 # Maximum generator power (kWp) + az: 180 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north + advanced: | + type: template + template: forecast-solar + lat: 55.7351 # Latitude + lon: 9.1275 # Longitude + dec: 25 # Decline, 0 = horizontal, 90 = vertical + kwp: 9.8 # Maximum generator power (kWp) + az: 180 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north + horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizon, Simulates terrain shadows, [more information](https://doc.forecast.solar/horizon) (optional) + apikey: # API key, optional + interval: 1h # optional +params: + - name: lat + example: 55.7351 + default: + choice: [] + unit: + description: Latitude + help: + advanced: false + optional: false + - name: lon + example: 9.1275 + default: + choice: [] + unit: + description: Longitude + help: + advanced: false + optional: false + - name: dec + example: 25 + default: + choice: [] + unit: + description: Decline + help: 0 = horizontal, 90 = vertical + advanced: false + optional: false + - name: kwp + example: 9.8 + default: + choice: [] + unit: kWp + description: Maximum generator power + help: + advanced: false + optional: false + - name: az + example: 180 + default: + choice: [] + unit: + description: Azimuth + help: -180 = north, -90 = east, 0 = south, 90 = west, 180 = north + advanced: false + optional: false + - name: horizon + example: 0,0,15,30,45,60,60,60,45,30,15,0 + default: + choice: [] + unit: + description: Horizon + help: Simulates terrain shadows, [more information](https://doc.forecast.solar/horizon) + advanced: true + optional: true + - name: apikey + example: + default: + choice: [] + unit: + description: API key + help: + advanced: true + optional: true + - name: interval + example: + default: 1h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/forecast-solar_0.yaml b/templates/release/en/tariff/forecast-solar_0.yaml deleted file mode 100644 index 9a9f7e8568..0000000000 --- a/templates/release/en/tariff/forecast-solar_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - brand: Forecast.Solar - group: PV forecast -requirements: ["skiptest"] -description: | - [forecast.solar](https://forecast.solar) can be used for free. Paid plans can also be used by specifying an API key. -render: - - default: | - type: template - template: forecast-solar - lat: 55.7351 # Latitude - lon: 9.1275 # Longitude - dec: 25 # Decline, 0 = horizontal, 90 = vertical - kwp: 9.8 # Maximum generator power (kWp) - az: 180 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north - advanced: | - type: template - template: forecast-solar - lat: 55.7351 # Latitude - lon: 9.1275 # Longitude - dec: 25 # Decline, 0 = horizontal, 90 = vertical - kwp: 9.8 # Maximum generator power (kWp) - az: 180 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north - horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizon, Simulates terrain shadows, [more information](https://doc.forecast.solar/horizon) (optional) - apikey: # API key, optional - interval: 1h # optional diff --git a/templates/release/en/tariff/fraunhofer-ise.yaml b/templates/release/en/tariff/fraunhofer-ise.yaml new file mode 100644 index 0000000000..643fd3b6f5 --- /dev/null +++ b/templates/release/en/tariff/fraunhofer-ise.yaml @@ -0,0 +1,58 @@ +template: energy-charts-api +product: + identifier: fraunhofer-ise + brand: Fraunhofer ISE + group: Dynamic electricity price +countries: ["EU"] +requirements: ["skiptest"] +description: | + Day-ahead forecast of energy prices (per kWh) on the exchange. No prior registration for https://api.energy-charts.info/ necessary. Can be used for dynamic electricity tariffs, for example, where the supplier does not yet offer a price forecast on the customer interface. +render: + - default: | + type: template + template: energy-charts-api + bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + advanced: | + type: template + template: energy-charts-api + bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: bzn + example: + default: DE-LU + choice: ['AT', 'BE', 'CH', 'CZ', 'DE-LU', 'DE-AT-LU', 'DK1', 'DK2', 'FR', 'HU', 'IT-NORTH', 'NL', 'NO2', 'PL', 'SE4', 'SI'] + unit: + description: + help: Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/green-grid-compass.yaml b/templates/release/en/tariff/green-grid-compass.yaml new file mode 100644 index 0000000000..03111e9411 --- /dev/null +++ b/templates/release/en/tariff/green-grid-compass.yaml @@ -0,0 +1,34 @@ +template: green-grid-compass +product: + identifier: green-grid-compass + brand: Green Grid Compass + group: CO₂ forecast +countries: ["BE", "DE", "LU"] +requirements: ["skiptest"] +description: | + European CO₂ intensity data from [greengrid-compass.eu](https://www.greengrid-compass.eu). Provides forecasts for the next hours and is free of charge after registration. +render: + - default: | + type: template + template: green-grid-compass + apiKey: # API Key, Create an app in https://api-portal.eco2grid.com and copy the key + zone: DE_LU # Zone code, [BE, DE_LU] +params: + - name: apiKey + example: + default: + choice: [] + unit: + description: API Key + help: Create an app in https://api-portal.eco2grid.com and copy the key + advanced: false + optional: false + - name: zone + example: + default: DE_LU + choice: ['BE', 'DE_LU'] + unit: + description: Zone code + help: + advanced: false + optional: false \ No newline at end of file diff --git a/templates/release/en/tariff/green-grid-compass_0.yaml b/templates/release/en/tariff/green-grid-compass_0.yaml deleted file mode 100644 index f36277e032..0000000000 --- a/templates/release/en/tariff/green-grid-compass_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Green Grid Compass - group: CO₂ forecast -countries: ["BE", "DE", "LU"] -requirements: ["skiptest"] -description: | - European CO₂ intensity data from [greengrid-compass.eu](https://www.greengrid-compass.eu). Provides forecasts for the next hours and is free of charge after registration. -render: - - default: | - type: template - template: green-grid-compass - apiKey: # API Key, Create an app in https://api-portal.eco2grid.com and copy the key - zone: DE_LU # Zone code, [BE, DE_LU] diff --git a/templates/release/en/tariff/groupe-e-vario-plus.yaml b/templates/release/en/tariff/groupe-e-vario-plus.yaml new file mode 100644 index 0000000000..ac7ea7b10e --- /dev/null +++ b/templates/release/en/tariff/groupe-e-vario-plus.yaml @@ -0,0 +1,46 @@ +template: groupe-e +product: + identifier: groupe-e-vario-plus + brand: Groupe E + description: Vario Plus + group: Dynamic electricity price +countries: ["CH"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: groupe-e + advanced: | + type: template + template: groupe-e + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/groupe-e_0.yaml b/templates/release/en/tariff/groupe-e_0.yaml deleted file mode 100644 index 56bc8fd34a..0000000000 --- a/templates/release/en/tariff/groupe-e_0.yaml +++ /dev/null @@ -1,16 +0,0 @@ -product: - brand: Groupe E - description: Vario Plus - group: Dynamic electricity price -countries: ["CH"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: groupe-e - advanced: | - type: template - template: groupe-e - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/grunstromindex.yaml b/templates/release/en/tariff/grunstromindex.yaml new file mode 100644 index 0000000000..890a2a7656 --- /dev/null +++ b/templates/release/en/tariff/grunstromindex.yaml @@ -0,0 +1,34 @@ +template: grünstromindex +product: + identifier: grunstromindex + brand: Grünstromindex + group: CO₂ forecast +countries: ["DE"] +requirements: ["skiptest"] +description: | + Regional emission data from https://gruenstromindex.de +render: + - default: | + type: template + template: grünstromindex + zip: + token: # Token for accessing the API from https://console.corrently.io (optional) +params: + - name: zip + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: Token for accessing the API from https://console.corrently.io + advanced: false + optional: true \ No newline at end of file diff --git "a/templates/release/en/tariff/gr\303\274nstromindex_0.yaml" "b/templates/release/en/tariff/gr\303\274nstromindex_0.yaml" deleted file mode 100644 index 05b927e46c..0000000000 --- "a/templates/release/en/tariff/gr\303\274nstromindex_0.yaml" +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Grünstromindex - group: CO₂ forecast -countries: ["DE"] -requirements: ["skiptest"] -description: | - Regional emission data from https://gruenstromindex.de -render: - - default: | - type: template - template: grünstromindex - zip: - token: # Token for accessing the API from https://console.corrently.io (optional) diff --git a/templates/release/en/tariff/national-grid-eso.yaml b/templates/release/en/tariff/national-grid-eso.yaml new file mode 100644 index 0000000000..be12f4b89a --- /dev/null +++ b/templates/release/en/tariff/national-grid-eso.yaml @@ -0,0 +1,31 @@ +template: ngeso +product: + identifier: national-grid-eso + brand: National Grid ESO + group: CO₂ forecast +countries: ["GB"] +render: + - default: | + type: template + template: ngeso + region: 1 # Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. (optional) +params: + - name: region + example: 1 + default: + choice: [] + unit: + description: + help: Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list + advanced: false + optional: true + - name: postalcode + example: SW1 + default: + choice: [] + unit: + description: + help: Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/ngeso_0.yaml b/templates/release/en/tariff/ngeso_0.yaml deleted file mode 100644 index ce118924a9..0000000000 --- a/templates/release/en/tariff/ngeso_0.yaml +++ /dev/null @@ -1,10 +0,0 @@ -product: - brand: National Grid ESO - group: CO₂ forecast -countries: ["GB"] -render: - - default: | - type: template - template: ngeso - region: 1 # Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list (optional) - postalcode: SW1 # Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. (optional) diff --git a/templates/release/en/tariff/nordpool-spot-prices.yaml b/templates/release/en/tariff/nordpool-spot-prices.yaml new file mode 100644 index 0000000000..a304828912 --- /dev/null +++ b/templates/release/en/tariff/nordpool-spot-prices.yaml @@ -0,0 +1,69 @@ +template: nordpool +product: + identifier: nordpool-spot-prices + brand: Nordpool spot prices + group: Dynamic electricity price +countries: ["EU"] +requirements: ["skiptest"] +description: | + Nordpool spot prices in day-ahead market for all markets in the Nordpool region. +render: + - default: | + type: template + template: nordpool + region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + advanced: | + type: template + template: nordpool + region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: region + example: GER + default: + choice: ['EE', 'LT', 'LV', 'AT', 'BE', 'FR', 'GER', 'NL', 'PL', 'DK1', 'DK2', 'FI', 'NO1', 'NO2', 'NO3', 'NO4', 'NO5', 'SE1', 'SE2', 'SE3', 'SE4', 'TEL', 'SYS'] + unit: + description: + help: + advanced: false + optional: true + - name: currency + example: + default: EUR + choice: ['DKK', 'EUR', 'NOK', 'PLN', 'RON', 'SEK'] + unit: + description: + help: + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/nordpool_0.yaml b/templates/release/en/tariff/nordpool_0.yaml deleted file mode 100644 index 0196acdc2f..0000000000 --- a/templates/release/en/tariff/nordpool_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - brand: Nordpool spot prices - group: Dynamic electricity price -countries: ["EU"] -requirements: ["skiptest"] -description: | - Nordpool spot prices in day-ahead market for all markets in the Nordpool region. -render: - - default: | - type: template - template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] - advanced: | - type: template - template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/octopus-api_0.yaml b/templates/release/en/tariff/octopus-api_0.yaml deleted file mode 100644 index 84078e9cb2..0000000000 --- a/templates/release/en/tariff/octopus-api_0.yaml +++ /dev/null @@ -1,13 +0,0 @@ -product: - brand: Octopus Energy - description: API - group: Dynamic electricity price -countries: ["GB"] -description: | - You can get the API key in the Octopus portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access -render: - - default: | - type: template - template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional) diff --git a/templates/release/en/tariff/octopus-energy-api.yaml b/templates/release/en/tariff/octopus-energy-api.yaml new file mode 100644 index 0000000000..ed9f3801c6 --- /dev/null +++ b/templates/release/en/tariff/octopus-energy-api.yaml @@ -0,0 +1,34 @@ +template: octopus-api +product: + identifier: octopus-energy-api + brand: Octopus Energy + description: API + group: Dynamic electricity price +countries: ["GB"] +description: | + You can get the API key in the Octopus portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access +render: + - default: | + type: template + template: octopus-api + apiKey: # Octopus Energy API Key. + accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional) +params: + - name: apiKey + example: + default: + choice: [] + unit: + description: + help: Octopus Energy API Key. + advanced: false + optional: false + - name: accountNumber + example: + default: + choice: [] + unit: + description: + help: Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/octopus-energy-product-code.yaml b/templates/release/en/tariff/octopus-energy-product-code.yaml new file mode 100644 index 0000000000..353df8d8b0 --- /dev/null +++ b/templates/release/en/tariff/octopus-energy-product-code.yaml @@ -0,0 +1,42 @@ +template: octopus-productcode +product: + identifier: octopus-energy-product-code + brand: Octopus Energy + description: Product Code + group: Dynamic electricity price +countries: ["GB"] +render: + - default: | + type: template + template: octopus-productcode + productCode: AGILE-FLEX-22-11-25 # The tariff code for your energy contract. Make sure this is set to your import tariff code. + region: # The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Use Direct Debit tariff rates. (optional) +params: + - name: productCode + example: AGILE-FLEX-22-11-25 + default: + choice: [] + unit: + description: + help: The tariff code for your energy contract. Make sure this is set to your import tariff code. + advanced: false + optional: false + - name: region + example: + default: + choice: ['A', 'B', 'C', 'D', 'E', 'F', 'G', 'H', 'J', 'K', 'L', 'M', 'N', 'P'] + unit: + description: + help: 'The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/' + advanced: false + optional: false + - name: directDebit + example: + default: true + choice: [] + unit: + description: + help: Use Direct Debit tariff rates. + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/octopus-productcode_0.yaml b/templates/release/en/tariff/octopus-productcode_0.yaml deleted file mode 100644 index 2e8bd67f9f..0000000000 --- a/templates/release/en/tariff/octopus-productcode_0.yaml +++ /dev/null @@ -1,12 +0,0 @@ -product: - brand: Octopus Energy - description: Product Code - group: Dynamic electricity price -countries: ["GB"] -render: - - default: | - type: template - template: octopus-productcode - productCode: AGILE-FLEX-22-11-25 # The tariff code for your energy contract. Make sure this is set to your import tariff code. - region: # The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] - directDebit: true # Use Direct Debit tariff rates. (optional) diff --git a/templates/release/en/tariff/open-meteo.yaml b/templates/release/en/tariff/open-meteo.yaml new file mode 100644 index 0000000000..d5c0eeea1b --- /dev/null +++ b/templates/release/en/tariff/open-meteo.yaml @@ -0,0 +1,141 @@ +template: open-meteo +product: + identifier: open-meteo + brand: Open-Meteo + group: PV forecast +requirements: ["skiptest"] +description: | + Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open-source weather API and offers free access for non-commercial use. No API key required. +render: + - default: | + type: template + template: open-meteo + lat: 55.7351 # Latitude + lon: 9.1275 # Longitude + dec: 25 # Decline, 0 = horizontal, 90 = vertical + kwp: 9.8 # Maximum generator power (kWp) + az: 0 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north + advanced: | + type: template + template: open-meteo + lat: 55.7351 # Latitude + lon: 9.1275 # Longitude + dec: 25 # Decline, 0 = horizontal, 90 = vertical + kwp: 9.8 # Maximum generator power (kWp) + az: 0 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north + ac: 1000 # AC Power [kW], optional + dm: 0 # Damping morning [%], optional + de: 0 # Damping evening [%], optional + efficiency: 100 # Efficiency [%], optional + alphatemp: -0.004 # Temperature coefficient, optional + rossmodel: 0.0342 # Cooling type [Ross Model], Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) + interval: 1h # optional +params: + - name: lat + example: 55.7351 + default: + choice: [] + unit: + description: Latitude + help: + advanced: false + optional: false + - name: lon + example: 9.1275 + default: + choice: [] + unit: + description: Longitude + help: + advanced: false + optional: false + - name: dec + example: 25 + default: + choice: [] + unit: + description: Decline + help: 0 = horizontal, 90 = vertical + advanced: false + optional: false + - name: kwp + example: 9.8 + default: + choice: [] + unit: kWp + description: Maximum generator power + help: + advanced: false + optional: false + - name: az + example: 0 + default: + choice: [] + unit: + description: Azimuth + help: -180 = north, -90 = east, 0 = south, 90 = west, 180 = north + advanced: false + optional: false + - name: ac + example: + default: 1000 + choice: [] + unit: + description: AC Power [kW] + help: + advanced: true + optional: true + - name: dm + example: + default: 0 + choice: [] + unit: + description: Damping morning [%] + help: + advanced: true + optional: true + - name: de + example: + default: 0 + choice: [] + unit: + description: Damping evening [%] + help: + advanced: true + optional: true + - name: efficiency + example: + default: 100 + choice: [] + unit: + description: Efficiency [%] + help: + advanced: true + optional: true + - name: alphatemp + example: + default: -0.004 + choice: [] + unit: + description: Temperature coefficient + help: + advanced: true + optional: true + - name: rossmodel + example: + default: 0.0342 + choice: [] + unit: + description: Cooling type [Ross Model] + help: Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) + advanced: true + optional: true + - name: interval + example: + default: 1h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/open-meteo_0.yaml b/templates/release/en/tariff/open-meteo_0.yaml deleted file mode 100644 index 34129af032..0000000000 --- a/templates/release/en/tariff/open-meteo_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Open-Meteo - group: PV forecast -requirements: ["skiptest"] -description: | - Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open-source weather API and offers free access for non-commercial use. No API key required. -render: - - default: | - type: template - template: open-meteo - lat: 55.7351 # Latitude - lon: 9.1275 # Longitude - dec: 25 # Decline, 0 = horizontal, 90 = vertical - kwp: 9.8 # Maximum generator power (kWp) - az: 0 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north - advanced: | - type: template - template: open-meteo - lat: 55.7351 # Latitude - lon: 9.1275 # Longitude - dec: 25 # Decline, 0 = horizontal, 90 = vertical - kwp: 9.8 # Maximum generator power (kWp) - az: 0 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north - ac: 1000 # AC Power [kW], optional - dm: 0 # Damping morning [%], optional - de: 0 # Damping evening [%], optional - efficiency: 100 # Efficiency [%], optional - alphatemp: -0.004 # Temperature coefficient, optional - rossmodel: 0.0342 # Cooling type [Ross Model], Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional diff --git a/templates/release/en/tariff/ostrom.yaml b/templates/release/en/tariff/ostrom.yaml new file mode 100644 index 0000000000..15626ba8fa --- /dev/null +++ b/templates/release/en/tariff/ostrom.yaml @@ -0,0 +1,44 @@ +template: ostrom +product: + identifier: ostrom + brand: Ostrom + group: Dynamic electricity price +countries: ["DE"] +requirements: ["skiptest"] +description: | + Create a 'Production Client' in the Ostrom developer portal: https://developer.ostrom-api.io/ +render: + - default: | + type: template + template: ostrom + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a + contract: 100523456 # Only required if multiple contracts belong to the same user (optional) +params: + - name: clientid + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: clientsecret + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: contract + example: 100523456 + default: + choice: [] + unit: + description: + help: Only required if multiple contracts belong to the same user + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/ostrom_0.yaml b/templates/release/en/tariff/ostrom_0.yaml deleted file mode 100644 index c7750b8ebe..0000000000 --- a/templates/release/en/tariff/ostrom_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: Ostrom - group: Dynamic electricity price -countries: ["DE"] -requirements: ["skiptest"] -description: | - Create a 'Production Client' in the Ostrom developer portal: https://developer.ostrom-api.io/ -render: - - default: | - type: template - template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Only required if multiple contracts belong to the same user (optional) diff --git a/templates/release/en/tariff/pun-orario.yaml b/templates/release/en/tariff/pun-orario.yaml new file mode 100644 index 0000000000..3f03771970 --- /dev/null +++ b/templates/release/en/tariff/pun-orario.yaml @@ -0,0 +1,47 @@ +template: pun +product: + identifier: pun-orario + brand: PUN Orario + group: Dynamic electricity price +countries: ["IT"] +requirements: ["skiptest"] +description: | + Price data from https://www.mercatoelettrico.org/it/. Often used for feeding into the grid. +render: + - default: | + type: template + template: pun + advanced: | + type: template + template: pun + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/pun_0.yaml b/templates/release/en/tariff/pun_0.yaml deleted file mode 100644 index 88607b684d..0000000000 --- a/templates/release/en/tariff/pun_0.yaml +++ /dev/null @@ -1,17 +0,0 @@ -product: - brand: PUN Orario - group: Dynamic electricity price -countries: ["IT"] -requirements: ["skiptest"] -description: | - Price data from https://www.mercatoelettrico.org/it/. Often used for feeding into the grid. -render: - - default: | - type: template - template: pun - advanced: | - type: template - template: pun - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/smartenergy-smartcontrol.yaml b/templates/release/en/tariff/smartenergy-smartcontrol.yaml new file mode 100644 index 0000000000..916d1de694 --- /dev/null +++ b/templates/release/en/tariff/smartenergy-smartcontrol.yaml @@ -0,0 +1,45 @@ +template: smartenergy +product: + identifier: smartenergy-smartcontrol + brand: SmartEnergy + description: smartCONTROL + group: Dynamic electricity price +countries: ["AT"] +render: + - default: | + type: template + template: smartenergy + advanced: | + type: template + template: smartenergy + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/smartenergy_0.yaml b/templates/release/en/tariff/smartenergy_0.yaml deleted file mode 100644 index 2ebaa0c84d..0000000000 --- a/templates/release/en/tariff/smartenergy_0.yaml +++ /dev/null @@ -1,15 +0,0 @@ -product: - brand: SmartEnergy - description: smartCONTROL - group: Dynamic electricity price -countries: ["AT"] -render: - - default: | - type: template - template: smartenergy - advanced: | - type: template - template: smartenergy - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/solcast.yaml b/templates/release/en/tariff/solcast.yaml new file mode 100644 index 0000000000..bfa625b557 --- /dev/null +++ b/templates/release/en/tariff/solcast.yaml @@ -0,0 +1,68 @@ +template: solcast +product: + identifier: solcast + brand: Solcast + group: PV forecast +requirements: ["skiptest"] +description: | + Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) account. The free "Home User" tier is often sufficient for private use. This plan has an API limit of 10 requests per day. +render: + - default: | + type: template + template: solcast + site: # ressource ID of your site + token: # Solcast API Token + advanced: | + type: template + template: solcast + site: # ressource ID of your site + token: # Solcast API Token + from: # Start time of data retrieval, specified in full hours, e.g. "6" (optional) + to: # End time of data retrieval, specified in full hours, e.g. "20" (optional) + interval: 3h # optional +params: + - name: site + example: + default: + choice: [] + unit: + description: + help: ressource ID of your site + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: Solcast API Token + advanced: false + optional: false + - name: from + example: + default: + choice: [] + unit: + description: + help: Start time of data retrieval, specified in full hours, e.g. "6" + advanced: true + optional: true + - name: to + example: + default: + choice: [] + unit: + description: + help: End time of data retrieval, specified in full hours, e.g. "20" + advanced: true + optional: true + - name: interval + example: + default: 3h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/solcast_0.yaml b/templates/release/en/tariff/solcast_0.yaml deleted file mode 100644 index 3ca5b561e5..0000000000 --- a/templates/release/en/tariff/solcast_0.yaml +++ /dev/null @@ -1,20 +0,0 @@ -product: - brand: Solcast - group: PV forecast -requirements: ["skiptest"] -description: | - Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) account. The free "Home User" tier is often sufficient for private use. This plan has an API limit of 10 requests per day. -render: - - default: | - type: template - template: solcast - site: # ressource ID of your site - token: # Solcast API Token - advanced: | - type: template - template: solcast - site: # ressource ID of your site - token: # Solcast API Token - from: # Start time of data retrieval, specified in full hours, e.g. "6" (optional) - to: # End time of data retrieval, specified in full hours, e.g. "20" (optional) - interval: 3h # optional diff --git a/templates/release/en/tariff/spotty-energie.yaml b/templates/release/en/tariff/spotty-energie.yaml new file mode 100644 index 0000000000..ef4a03dcda --- /dev/null +++ b/templates/release/en/tariff/spotty-energie.yaml @@ -0,0 +1,67 @@ +template: spottyenergy +product: + identifier: spotty-energie + brand: Spotty Energie + group: Dynamic electricity price +countries: ["AT"] +requirements: ["skiptest"] +render: + - default: | + type: template + template: spottyenergy + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + advanced: | + type: template + template: spottyenergy + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: contractid + example: ffffffff-4444-6666-2222-aaaaaabbbbbb + default: + choice: [] + unit: + description: + help: You can get your contract id from the customer portal https://i.spottyenergie.at/ + advanced: false + optional: false + - name: pricetype + example: + default: CONSUMPTION + choice: ['MARKET', 'CONSUMPTION', 'GENERATION'] + unit: + description: + help: Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren + advanced: false + optional: false + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/spottyenergy_0.yaml b/templates/release/en/tariff/spottyenergy_0.yaml deleted file mode 100644 index b2a630fee9..0000000000 --- a/templates/release/en/tariff/spottyenergy_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Spotty Energie - group: Dynamic electricity price -countries: ["AT"] -requirements: ["skiptest"] -render: - - default: | - type: template - template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] - advanced: | - type: template - template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/tibber.yaml b/templates/release/en/tariff/tibber.yaml new file mode 100644 index 0000000000..ef2f5fa520 --- /dev/null +++ b/templates/release/en/tariff/tibber.yaml @@ -0,0 +1,69 @@ +template: tibber +product: + identifier: tibber + brand: Tibber + group: Dynamic electricity price +countries: ["NO", "SE", "DE", "NL"] +requirements: ["skiptest"] +description: | + Get your API token from the Tibber developer portal: https://developer.tibber.com/ +render: + - default: | + type: template + template: tibber + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) + advanced: | + type: template + template: tibber + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) + charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) + tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) + formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) +params: + - name: token + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: homeid + example: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c + default: + choice: [] + unit: + description: + help: Only required if you have multiple homes in your Tibber account. + advanced: false + optional: true + - name: charges + example: + default: + choice: [] + unit: + description: Charge + help: Additional fixed charge per kWh (e.g. 0.05 for 5 cents) + advanced: true + optional: true + - name: tax + example: + default: + choice: [] + unit: + description: Tax + help: Additional percentage charge (e.g. 0.2 for 20%) + advanced: true + optional: true + - name: formula + example: math.Max((price + charges) * (1 + tax), 0.0) + default: + choice: [] + unit: + description: Formula + help: Individual formula for calculating the price + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/tibber_0.yaml b/templates/release/en/tariff/tibber_0.yaml deleted file mode 100644 index 218af3caa3..0000000000 --- a/templates/release/en/tariff/tibber_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - brand: Tibber - group: Dynamic electricity price -countries: ["NO", "SE", "DE", "NL"] -requirements: ["skiptest"] -description: | - Get your API token from the Tibber developer portal: https://developer.tibber.com/ -render: - - default: | - type: template - template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) - advanced: | - type: template - template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) - charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) - tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) - formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) diff --git a/templates/release/en/tariff/victron-vrm-solar-forecast.yaml b/templates/release/en/tariff/victron-vrm-solar-forecast.yaml new file mode 100644 index 0000000000..24e32e57de --- /dev/null +++ b/templates/release/en/tariff/victron-vrm-solar-forecast.yaml @@ -0,0 +1,49 @@ +template: victron +product: + identifier: victron-vrm-solar-forecast + brand: Victron + description: VRM Solar Forecast + group: PV forecast +requirements: ["skiptest"] +description: | + [vrm.victronenergy.com](https://vrm.victronenergy.com) get the 2-days-forecast from your installation in VRM portal. You need a free user access token. +render: + - default: | + type: template + template: victron + idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" + token: # API access token, Tokens can be created in VRM in Preferences->Integrations + advanced: | + type: template + template: victron + idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" + token: # API access token, Tokens can be created in VRM in Preferences->Integrations + interval: 1h # optional +params: + - name: idsite + example: 123456 + default: + choice: [] + unit: + description: VRM Site ID of the installation + help: The VRM Site ID is displayed in the installation settings under "General" + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: API access token + help: Tokens can be created in VRM in Preferences->Integrations + advanced: false + optional: false + - name: interval + example: + default: 1h + choice: [] + unit: + description: + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/victron_0.yaml b/templates/release/en/tariff/victron_0.yaml deleted file mode 100644 index c53a8a9998..0000000000 --- a/templates/release/en/tariff/victron_0.yaml +++ /dev/null @@ -1,19 +0,0 @@ -product: - brand: Victron - description: VRM Solar Forecast - group: PV forecast -requirements: ["skiptest"] -description: | - [vrm.victronenergy.com](https://vrm.victronenergy.com) get the 2-days-forecast from your installation in VRM portal. You need a free user access token. -render: - - default: | - type: template - template: victron - idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" - token: # API access token, Tokens can be created in VRM in Preferences->Integrations - advanced: | - type: template - template: victron - idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" - token: # API access token, Tokens can be created in VRM in Preferences->Integrations - interval: 1h # optional diff --git a/templates/release/en/vehicle/aiways.yaml b/templates/release/en/vehicle/aiways.yaml new file mode 100644 index 0000000000..6011abd9bc --- /dev/null +++ b/templates/release/en/vehicle/aiways.yaml @@ -0,0 +1,147 @@ +template: aiways +product: + identifier: aiways + brand: Aiways +render: + - default: | + type: template + template: aiways + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: aiways + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/aiways_0.yaml b/templates/release/en/vehicle/aiways_0.yaml deleted file mode 100644 index 41b779693b..0000000000 --- a/templates/release/en/vehicle/aiways_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Aiways -render: - - default: | - type: template - template: aiways - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: aiways - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/audi.yaml b/templates/release/en/vehicle/audi.yaml new file mode 100644 index 0000000000..e00ee032e6 --- /dev/null +++ b/templates/release/en/vehicle/audi.yaml @@ -0,0 +1,147 @@ +template: audi +product: + identifier: audi + brand: Audi +render: + - default: | + type: template + template: audi + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WAUZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: audi + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WAUZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: WAUZZZ... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/audi_0.yaml b/templates/release/en/vehicle/audi_0.yaml deleted file mode 100644 index b160ad8867..0000000000 --- a/templates/release/en/vehicle/audi_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Audi -render: - - default: | - type: template - template: audi - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WAUZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: audi - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WAUZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/bmw.yaml b/templates/release/en/vehicle/bmw.yaml new file mode 100644 index 0000000000..faa2414262 --- /dev/null +++ b/templates/release/en/vehicle/bmw.yaml @@ -0,0 +1,191 @@ +template: bmw +product: + identifier: bmw + brand: BMW +description: | + Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. + +render: + - default: | + type: template + template: bmw + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + hcaptcha: + advanced: | + type: template + template: bmw + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + hcaptcha: + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + region: EU # Region, [EU, NA] + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: WBMW... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: hcaptcha + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: region + example: + default: EU + choice: ['EU', 'NA'] + unit: + description: Region + help: + advanced: true + optional: false + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/bmw_0.yaml b/templates/release/en/vehicle/bmw_0.yaml deleted file mode 100644 index 893d766bf3..0000000000 --- a/templates/release/en/vehicle/bmw_0.yaml +++ /dev/null @@ -1,35 +0,0 @@ -product: - brand: BMW -description: | - Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. - -render: - - default: | - type: template - template: bmw - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - hcaptcha: - advanced: | - type: template - template: bmw - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - hcaptcha: - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - region: EU # Region, [EU, NA] - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/carwings_0.yaml b/templates/release/en/vehicle/carwings_0.yaml deleted file mode 100644 index a6431a96d4..0000000000 --- a/templates/release/en/vehicle/carwings_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nissan - description: Leaf (pre 2019) -render: - - default: | - type: template - template: carwings - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: carwings - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/citroen.yaml b/templates/release/en/vehicle/citroen.yaml new file mode 100644 index 0000000000..bc67559ae4 --- /dev/null +++ b/templates/release/en/vehicle/citroen.yaml @@ -0,0 +1,161 @@ +template: citroen +product: + identifier: citroen + brand: Citroën +description: | + Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + +render: + - default: | + type: template + template: citroen + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: citroen + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/citroen_0.yaml b/templates/release/en/vehicle/citroen_0.yaml deleted file mode 100644 index 80a90a75a4..0000000000 --- a/templates/release/en/vehicle/citroen_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Citroën -description: | - Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. - -render: - - default: | - type: template - template: citroen - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: citroen - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/cupra_0.yaml b/templates/release/en/vehicle/cupra_0.yaml deleted file mode 100644 index c964a5aa9a..0000000000 --- a/templates/release/en/vehicle/cupra_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Seat - description: CupraConnect Gen4 (Born, Formentor, Tavascan) -render: - - default: | - type: template - template: cupra - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: cupra - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/dacia.yaml b/templates/release/en/vehicle/dacia.yaml new file mode 100644 index 0000000000..57810bdcd3 --- /dev/null +++ b/templates/release/en/vehicle/dacia.yaml @@ -0,0 +1,167 @@ +template: dacia +product: + identifier: dacia + brand: Dacia +render: + - default: | + type: template + template: dacia + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: dacia + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/dacia_0.yaml b/templates/release/en/vehicle/dacia_0.yaml deleted file mode 100644 index 15a799dd53..0000000000 --- a/templates/release/en/vehicle/dacia_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - brand: Dacia -render: - - default: | - type: template - template: dacia - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: dacia - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/ds.yaml b/templates/release/en/vehicle/ds.yaml new file mode 100644 index 0000000000..9781f34f42 --- /dev/null +++ b/templates/release/en/vehicle/ds.yaml @@ -0,0 +1,161 @@ +template: ds +product: + identifier: ds + brand: DS +description: | + Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + +render: + - default: | + type: template + template: ds + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: ds + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/ds_0.yaml b/templates/release/en/vehicle/ds_0.yaml deleted file mode 100644 index dbdac3414f..0000000000 --- a/templates/release/en/vehicle/ds_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: DS -description: | - Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. - -render: - - default: | - type: template - template: ds - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: ds - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/enyaq_0.yaml b/templates/release/en/vehicle/enyaq_0.yaml deleted file mode 100644 index 1f6c4b7170..0000000000 --- a/templates/release/en/vehicle/enyaq_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Skoda - description: Enyaq -render: - - default: | - type: template - template: enyaq - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - timeout: 10s # Timeout, optional - advanced: | - type: template - template: enyaq - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - timeout: 10s # Timeout, optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/evnotify.yaml b/templates/release/en/vehicle/evnotify.yaml new file mode 100644 index 0000000000..8b712a999b --- /dev/null +++ b/templates/release/en/vehicle/evnotify.yaml @@ -0,0 +1,127 @@ +template: evnotify +product: + identifier: evnotify + description: evNotify + group: Generic support +render: + - default: | + type: template + template: evnotify + akey: + token: + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: evnotify + akey: + token: + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: akey + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/evnotify_0.yaml b/templates/release/en/vehicle/evnotify_0.yaml deleted file mode 100644 index 25089ee73e..0000000000 --- a/templates/release/en/vehicle/evnotify_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: evNotify - group: Generic support -render: - - default: | - type: template - template: evnotify - akey: - token: - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: evnotify - akey: - token: - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/fiat.yaml b/templates/release/en/vehicle/fiat.yaml new file mode 100644 index 0000000000..0de8fa06a2 --- /dev/null +++ b/templates/release/en/vehicle/fiat.yaml @@ -0,0 +1,178 @@ +template: fiat +product: + identifier: fiat + brand: Fiat +render: + - default: | + type: template + template: fiat + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + advanced: | + type: template + template: fiat + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: ZFAE... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: pin + example: + default: + choice: [] + unit: + description: + help: Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/fiat_0.yaml b/templates/release/en/vehicle/fiat_0.yaml deleted file mode 100644 index 4cf94368d8..0000000000 --- a/templates/release/en/vehicle/fiat_0.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - brand: Fiat -render: - - default: | - type: template - template: fiat - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) - advanced: | - type: template - template: fiat - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/fiat_1.yaml b/templates/release/en/vehicle/fiat_1.yaml deleted file mode 100644 index 599820a9d5..0000000000 --- a/templates/release/en/vehicle/fiat_1.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - brand: Jeep -render: - - default: | - type: template - template: fiat - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) - advanced: | - type: template - template: fiat - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/flobz_0.yaml b/templates/release/en/vehicle/flobz_0.yaml deleted file mode 100644 index d3298dedda..0000000000 --- a/templates/release/en/vehicle/flobz_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - description: PSA Car Controller - group: Generic support -description: | - Remote Control of PSA car https://github.com/flobz/psa_car_controller -render: - - default: | - type: template - template: flobz - url: http://192.0.2.2 - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: flobz - url: http://192.0.2.2 - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - wakeup_alt: false # alternative wakeup-code; could lead to increased discharge of the 12V battery. (optional) diff --git a/templates/release/en/vehicle/ford-connect_0.yaml b/templates/release/en/vehicle/ford-connect_0.yaml deleted file mode 100644 index d4aa6aec96..0000000000 --- a/templates/release/en/vehicle/ford-connect_0.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - brand: Ford -render: - - default: | - type: template - template: ford-connect - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - clientid: # FordConnect API Client ID, Setup at https://developer.ford.com - clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com - accessToken: - refreshToken: - vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: ford-connect - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - clientid: # FordConnect API Client ID, Setup at https://developer.ford.com - clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com - accessToken: - refreshToken: - vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/ford.yaml b/templates/release/en/vehicle/ford.yaml new file mode 100644 index 0000000000..714e7caafc --- /dev/null +++ b/templates/release/en/vehicle/ford.yaml @@ -0,0 +1,169 @@ +template: ford-connect +product: + identifier: ford + brand: Ford +render: + - default: | + type: template + template: ford-connect + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + clientid: # FordConnect API Client ID, Setup at https://developer.ford.com + clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com + accessToken: + refreshToken: + vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: ford-connect + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + clientid: # FordConnect API Client ID, Setup at https://developer.ford.com + clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com + accessToken: + refreshToken: + vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: clientid + example: + default: + choice: [] + unit: + description: FordConnect API Client ID + help: Setup at https://developer.ford.com + advanced: false + optional: false + - name: clientsecret + example: + default: + choice: [] + unit: + description: FordConnect API Client Secret + help: Setup at https://developer.ford.com + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: WF0FXX... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/generic-vehicle-without-api.yaml b/templates/release/en/vehicle/generic-vehicle-without-api.yaml new file mode 100644 index 0000000000..94705d2660 --- /dev/null +++ b/templates/release/en/vehicle/generic-vehicle-without-api.yaml @@ -0,0 +1,105 @@ +template: offline +product: + identifier: generic-vehicle-without-api + description: Generic vehicle (without API) + group: Generic support +render: + - default: | + type: template + template: offline + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: offline + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/hyundai-bluelink.yaml b/templates/release/en/vehicle/hyundai-bluelink.yaml new file mode 100644 index 0000000000..0a140715bf --- /dev/null +++ b/templates/release/en/vehicle/hyundai-bluelink.yaml @@ -0,0 +1,161 @@ +template: hyundai +product: + identifier: hyundai-bluelink + brand: Hyundai + description: Bluelink +description: | + Some models (e.g. Kona) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. +render: + - default: | + type: template + template: hyundai + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + language: en # Language, [en, de] (optional) + advanced: | + type: template + template: hyundai + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + language: en # Language, [en, de] (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: language + example: + default: en + choice: ['en', 'de'] + unit: + description: Language + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/hyundai_0.yaml b/templates/release/en/vehicle/hyundai_0.yaml deleted file mode 100644 index 7ca677a2ec..0000000000 --- a/templates/release/en/vehicle/hyundai_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Hyundai - description: Bluelink -description: | - Some models (e.g. Kona) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. -render: - - default: | - type: template - template: hyundai - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - language: en # Language, [en, de] (optional) - advanced: | - type: template - template: hyundai - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - language: en # Language, [en, de] (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/ioBroker.bmw_0.yaml b/templates/release/en/vehicle/ioBroker.bmw_0.yaml deleted file mode 100644 index 9d34e5beeb..0000000000 --- a/templates/release/en/vehicle/ioBroker.bmw_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - description: ioBroker.bmw - group: Generic support -description: | - ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api -render: - - default: | - type: template - template: ioBroker.bmw - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - uri: # URI, HTTP(S) address - advanced: | - type: template - template: ioBroker.bmw - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - uri: # URI, HTTP(S) address - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - id: 0 # Instance ID (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/iobroker-bmw.yaml b/templates/release/en/vehicle/iobroker-bmw.yaml new file mode 100644 index 0000000000..b8b5041571 --- /dev/null +++ b/templates/release/en/vehicle/iobroker-bmw.yaml @@ -0,0 +1,159 @@ +template: ioBroker.bmw +product: + identifier: iobroker-bmw + description: ioBroker.bmw + group: Generic support +description: | + ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api +render: + - default: | + type: template + template: ioBroker.bmw + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber + uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address + advanced: | + type: template + template: ioBroker.bmw + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber + uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + id: 0 # Instance ID, optional + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: vin + example: WBA8E9G50GM091234 + default: + choice: [] + unit: + description: Vehicle Identification Number + help: BMW VehicleIdentificationNumber + advanced: false + optional: false + - name: uri + example: + default: + choice: [] + unit: + description: ioBroker URL inlcuding ioBroker.simple-api Port + help: HTTP(S) address + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: id + example: + default: 0 + choice: [] + unit: + description: Instance ID + help: + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/iso15118.yaml b/templates/release/en/vehicle/iso15118.yaml new file mode 100644 index 0000000000..4ecf1d1a5d --- /dev/null +++ b/templates/release/en/vehicle/iso15118.yaml @@ -0,0 +1,112 @@ +template: iso15118 +product: + identifier: iso15118 + description: ISO15118 + group: Generic support +capabilities: ["iso151182"] +description: | + Only supported if the vehicle can provide the state of charge (Soc) to the connected charger. + Using ISO15118 with some VW group vehicles, e.g. Porsche Taycan, requires additional configuration in the vehicle. + This requires an active location-based charging profile with the lowest minimum charge (25%) and direct charging disabled. + Otherwise the vehicle cannot be put into sleep mode. + +render: + - default: | + type: template + template: iso15118 + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: iso15118 + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/iso15118_0.yaml b/templates/release/en/vehicle/iso15118_0.yaml deleted file mode 100644 index f818e4ff49..0000000000 --- a/templates/release/en/vehicle/iso15118_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - description: ISO15118 - group: Generic support -capabilities: ["iso151182"] -description: | - Only supported if the vehicle can provide the state of charge (Soc) to the connected charger. - Using ISO15118 with some VW group vehicles, e.g. Porsche Taycan, requires additional configuration in the vehicle. - This requires an active location-based charging profile with the lowest minimum charge (25%) and direct charging disabled. - Otherwise the vehicle cannot be put into sleep mode. - -render: - - default: | - type: template - template: iso15118 - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: iso15118 - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/jeep.yaml b/templates/release/en/vehicle/jeep.yaml new file mode 100644 index 0000000000..9f71e55cd2 --- /dev/null +++ b/templates/release/en/vehicle/jeep.yaml @@ -0,0 +1,178 @@ +template: fiat +product: + identifier: jeep + brand: Jeep +render: + - default: | + type: template + template: fiat + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + advanced: | + type: template + template: fiat + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: ZFAE... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: pin + example: + default: + choice: [] + unit: + description: + help: Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/kia-bluelink.yaml b/templates/release/en/vehicle/kia-bluelink.yaml new file mode 100644 index 0000000000..aaf74064cf --- /dev/null +++ b/templates/release/en/vehicle/kia-bluelink.yaml @@ -0,0 +1,161 @@ +template: kia +product: + identifier: kia-bluelink + brand: Kia + description: Bluelink +description: | + Some models (e.g. Niro EV) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. +render: + - default: | + type: template + template: kia + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + language: en # Language, [en, de] (optional) + advanced: | + type: template + template: kia + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + language: en # Language, [en, de] (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: language + example: + default: en + choice: ['en', 'de'] + unit: + description: Language + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/kia_0.yaml b/templates/release/en/vehicle/kia_0.yaml deleted file mode 100644 index 377fd3476b..0000000000 --- a/templates/release/en/vehicle/kia_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Kia - description: Bluelink -description: | - Some models (e.g. Niro EV) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. -render: - - default: | - type: template - template: kia - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - language: en # Language, [en, de] (optional) - advanced: | - type: template - template: kia - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - language: en # Language, [en, de] (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/mercedes-benz.yaml b/templates/release/en/vehicle/mercedes-benz.yaml new file mode 100644 index 0000000000..9bdecd8e82 --- /dev/null +++ b/templates/release/en/vehicle/mercedes-benz.yaml @@ -0,0 +1,172 @@ +template: mercedes +product: + identifier: mercedes-benz + brand: Mercedes-Benz +description: | + Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/mbapi2020helptoken. + +render: + - default: | + type: template + template: mercedes + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: mercedes + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: region + example: + default: EMEA + choice: ['EMEA', 'APAC', 'NORAM'] + unit: + description: + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/mercedes_0.yaml b/templates/release/en/vehicle/mercedes_0.yaml deleted file mode 100644 index 907cd189d6..0000000000 --- a/templates/release/en/vehicle/mercedes_0.yaml +++ /dev/null @@ -1,34 +0,0 @@ -product: - brand: Mercedes-Benz -description: | - Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/mbapi2020helptoken. - -render: - - default: | - type: template - template: mercedes - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: mercedes - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/mg.yaml b/templates/release/en/vehicle/mg.yaml new file mode 100644 index 0000000000..5e0c7dcb7e --- /dev/null +++ b/templates/release/en/vehicle/mg.yaml @@ -0,0 +1,157 @@ +template: mg +product: + identifier: mg + brand: MG +render: + - default: | + type: template + template: mg + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: mg + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + region: EU # Region, [EU, AU] +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: region + example: + default: EU + choice: ['EU', 'AU'] + unit: + description: Region + help: + advanced: true + optional: false \ No newline at end of file diff --git a/templates/release/en/vehicle/mg2mqtt.yaml b/templates/release/en/vehicle/mg2mqtt.yaml new file mode 100644 index 0000000000..193bf3c45d --- /dev/null +++ b/templates/release/en/vehicle/mg2mqtt.yaml @@ -0,0 +1,140 @@ +template: mg2mqtt +product: + identifier: mg2mqtt + description: mg2mqtt + group: Generic support +description: | + Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway or https://github.com/SAIC-iSmart-API/saic-java-client) +render: + - default: | + type: template + template: mg2mqtt + user: # Username, e.g. email address, user id, etc. + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + timeout: 1h # Timeout, optional + advanced: | + type: template + template: mg2mqtt + user: # Username, e.g. email address, user id, etc. + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + timeout: 1h # Timeout, optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 1h + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/mg2mqtt_0.yaml b/templates/release/en/vehicle/mg2mqtt_0.yaml deleted file mode 100644 index 50a0ee682e..0000000000 --- a/templates/release/en/vehicle/mg2mqtt_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: mg2mqtt - group: Generic support -description: | - Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway or https://github.com/SAIC-iSmart-API/saic-java-client) -render: - - default: | - type: template - template: mg2mqtt - user: # Username, e.g. email address, user id, etc. - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - timeout: 1h # Timeout, optional - advanced: | - type: template - template: mg2mqtt - user: # Username, e.g. email address, user id, etc. - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - timeout: 1h # Timeout, optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/mg_0.yaml b/templates/release/en/vehicle/mg_0.yaml deleted file mode 100644 index 7f155403e5..0000000000 --- a/templates/release/en/vehicle/mg_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: MG -render: - - default: | - type: template - template: mg - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: mg - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - region: EU # Region, [EU, AU] diff --git a/templates/release/en/vehicle/mini.yaml b/templates/release/en/vehicle/mini.yaml new file mode 100644 index 0000000000..e5cf44b35a --- /dev/null +++ b/templates/release/en/vehicle/mini.yaml @@ -0,0 +1,191 @@ +template: mini +product: + identifier: mini + brand: Mini +description: | + Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. + +render: + - default: | + type: template + template: mini + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + hcaptcha: + advanced: | + type: template + template: mini + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + hcaptcha: + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + region: EU # Region, [EU, NA] + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: WBMW... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: hcaptcha + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: region + example: + default: EU + choice: ['EU', 'NA'] + unit: + description: Region + help: + advanced: true + optional: false + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/mini_0.yaml b/templates/release/en/vehicle/mini_0.yaml deleted file mode 100644 index a70fdf8cd5..0000000000 --- a/templates/release/en/vehicle/mini_0.yaml +++ /dev/null @@ -1,35 +0,0 @@ -product: - brand: Mini -description: | - Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. - -render: - - default: | - type: template - template: mini - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - hcaptcha: - advanced: | - type: template - template: mini - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - hcaptcha: - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - region: EU # Region, [EU, NA] - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/mz2mqtt.yaml b/templates/release/en/vehicle/mz2mqtt.yaml new file mode 100644 index 0000000000..a8c49a69ba --- /dev/null +++ b/templates/release/en/vehicle/mz2mqtt.yaml @@ -0,0 +1,128 @@ +template: mz2mqtt +product: + identifier: mz2mqtt + description: mz2mqtt + group: Generic support +description: | + myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation https://github.com/C64Axel/mz2mqtt. +render: + - default: | + type: template + template: mz2mqtt + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + advanced: | + type: template + template: mz2mqtt + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + timeout: 720h # Timeout, optional +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: timeout + example: 10s + default: 720h + choice: [] + unit: + description: Timeout + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/mz2mqtt_0.yaml b/templates/release/en/vehicle/mz2mqtt_0.yaml deleted file mode 100644 index 98cb225edf..0000000000 --- a/templates/release/en/vehicle/mz2mqtt_0.yaml +++ /dev/null @@ -1,26 +0,0 @@ -product: - description: mz2mqtt - group: Generic support -description: | - myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation https://github.com/C64Axel/mz2mqtt. -render: - - default: | - type: template - template: mz2mqtt - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - advanced: | - type: template - template: mz2mqtt - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - timeout: 720h # Timeout, optional diff --git a/templates/release/en/vehicle/nissan-ariya.yaml b/templates/release/en/vehicle/nissan-ariya.yaml new file mode 100644 index 0000000000..bc93ff337c --- /dev/null +++ b/templates/release/en/vehicle/nissan-ariya.yaml @@ -0,0 +1,148 @@ +template: nissan-ariya +product: + identifier: nissan-ariya + brand: Nissan + description: Ariya +render: + - default: | + type: template + template: nissan-ariya + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: nissan-ariya + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/nissan-ariya_0.yaml b/templates/release/en/vehicle/nissan-ariya_0.yaml deleted file mode 100644 index 88da497a92..0000000000 --- a/templates/release/en/vehicle/nissan-ariya_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nissan - description: Ariya -render: - - default: | - type: template - template: nissan-ariya - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: nissan-ariya - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/nissan-leaf-pre-2019.yaml b/templates/release/en/vehicle/nissan-leaf-pre-2019.yaml new file mode 100644 index 0000000000..0d850e95ac --- /dev/null +++ b/templates/release/en/vehicle/nissan-leaf-pre-2019.yaml @@ -0,0 +1,148 @@ +template: carwings +product: + identifier: nissan-leaf-pre-2019 + brand: Nissan + description: Leaf (pre 2019) +render: + - default: | + type: template + template: carwings + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: carwings + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/nissan-leaf.yaml b/templates/release/en/vehicle/nissan-leaf.yaml new file mode 100644 index 0000000000..5de281e9d2 --- /dev/null +++ b/templates/release/en/vehicle/nissan-leaf.yaml @@ -0,0 +1,148 @@ +template: nissan +product: + identifier: nissan-leaf + brand: Nissan + description: Leaf +render: + - default: | + type: template + template: nissan + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: nissan + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/nissan_0.yaml b/templates/release/en/vehicle/nissan_0.yaml deleted file mode 100644 index 2e3121a596..0000000000 --- a/templates/release/en/vehicle/nissan_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Nissan - description: Leaf -render: - - default: | - type: template - template: nissan - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: nissan - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/niu-e-scooter.yaml b/templates/release/en/vehicle/niu-e-scooter.yaml new file mode 100644 index 0000000000..086dd89080 --- /dev/null +++ b/templates/release/en/vehicle/niu-e-scooter.yaml @@ -0,0 +1,71 @@ +template: niu-e-scooter +product: + identifier: niu-e-scooter + brand: NIU + description: E-Scooter + group: Scooter +render: + - default: | + type: template + template: niu-e-scooter + title: # Title, Will be displayed in the user interface (optional) + icon: scooter # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + serial: # Scooter serial number like shown in NIU app + capacity: 4 # Battery capacity (kWh), optional +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: icon + example: + default: scooter + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: serial + example: + default: + choice: [] + unit: + description: Scooter serial number like shown in NIU app + help: + advanced: false + optional: false + - name: capacity + example: 50 + default: 4 + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/niu-e-scooter_0.yaml b/templates/release/en/vehicle/niu-e-scooter_0.yaml deleted file mode 100644 index 7c39fa5672..0000000000 --- a/templates/release/en/vehicle/niu-e-scooter_0.yaml +++ /dev/null @@ -1,14 +0,0 @@ -product: - brand: NIU - description: E-Scooter - group: Scooter -render: - - default: | - type: template - template: niu-e-scooter - title: # Title, Will be displayed in the user interface (optional) - icon: scooter # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - serial: # Scooter serial number like shown in NIU app - capacity: 4 # Battery capacity (kWh), optional diff --git a/templates/release/en/vehicle/offline_0.yaml b/templates/release/en/vehicle/offline_0.yaml deleted file mode 100644 index f9be0e2b9c..0000000000 --- a/templates/release/en/vehicle/offline_0.yaml +++ /dev/null @@ -1,21 +0,0 @@ -product: - description: Generic vehicle (without API) - group: Generic support -render: - - default: | - type: template - template: offline - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: offline - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/opel.yaml b/templates/release/en/vehicle/opel.yaml new file mode 100644 index 0000000000..6d8a4f306e --- /dev/null +++ b/templates/release/en/vehicle/opel.yaml @@ -0,0 +1,161 @@ +template: opel +product: + identifier: opel + brand: Opel +description: | + Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + +render: + - default: | + type: template + template: opel + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: opel + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/opel_0.yaml b/templates/release/en/vehicle/opel_0.yaml deleted file mode 100644 index c85598d2f7..0000000000 --- a/templates/release/en/vehicle/opel_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Opel -description: | - Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. - -render: - - default: | - type: template - template: opel - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: opel - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/open-vehicle-monitoring-system.yaml b/templates/release/en/vehicle/open-vehicle-monitoring-system.yaml new file mode 100644 index 0000000000..86d9085d80 --- /dev/null +++ b/templates/release/en/vehicle/open-vehicle-monitoring-system.yaml @@ -0,0 +1,160 @@ +template: ovms +product: + identifier: open-vehicle-monitoring-system + description: Open Vehicle Monitoring System + group: Generic support +description: | + Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Vehicle Monitoring System](http://api.openvehicles.com/). +render: + - default: | + type: template + template: ovms + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vehicleid: + advanced: | + type: template + template: ovms + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vehicleid: + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + server: dexters-web.de + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vehicleid + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: server + example: + default: dexters-web.de + choice: [] + unit: + description: + help: + advanced: true + optional: false + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/ovms_0.yaml b/templates/release/en/vehicle/ovms_0.yaml deleted file mode 100644 index f1b2c938f8..0000000000 --- a/templates/release/en/vehicle/ovms_0.yaml +++ /dev/null @@ -1,31 +0,0 @@ -product: - description: Open Vehicle Monitoring System - group: Generic support -description: | - Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Vehicle Monitoring System](http://api.openvehicles.com/). -render: - - default: | - type: template - template: ovms - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vehicleid: - advanced: | - type: template - template: ovms - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vehicleid: - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - server: dexters-web.de - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/peugeot.yaml b/templates/release/en/vehicle/peugeot.yaml new file mode 100644 index 0000000000..f2622de083 --- /dev/null +++ b/templates/release/en/vehicle/peugeot.yaml @@ -0,0 +1,161 @@ +template: peugeot +product: + identifier: peugeot + brand: Peugeot +description: | + Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + +render: + - default: | + type: template + template: peugeot + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: peugeot + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/peugeot_0.yaml b/templates/release/en/vehicle/peugeot_0.yaml deleted file mode 100644 index b5c713d653..0000000000 --- a/templates/release/en/vehicle/peugeot_0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -product: - brand: Peugeot -description: | - Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. - -render: - - default: | - type: template - template: peugeot - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: peugeot - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/polestar.yaml b/templates/release/en/vehicle/polestar.yaml new file mode 100644 index 0000000000..1244dd845e --- /dev/null +++ b/templates/release/en/vehicle/polestar.yaml @@ -0,0 +1,148 @@ +template: polestar +product: + identifier: polestar + brand: Polestar +requirements: ["skiptest"] +render: + - default: | + type: template + template: polestar + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: LPSVS... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: polestar + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: LPSVS... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: LPSVS... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/polestar_0.yaml b/templates/release/en/vehicle/polestar_0.yaml deleted file mode 100644 index 9b9422c13b..0000000000 --- a/templates/release/en/vehicle/polestar_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Polestar -requirements: ["skiptest"] -render: - - default: | - type: template - template: polestar - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: LPSVS... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: polestar - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: LPSVS... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/psa-car-controller.yaml b/templates/release/en/vehicle/psa-car-controller.yaml new file mode 100644 index 0000000000..7992d4b0f3 --- /dev/null +++ b/templates/release/en/vehicle/psa-car-controller.yaml @@ -0,0 +1,139 @@ +template: flobz +product: + identifier: psa-car-controller + description: PSA Car Controller + group: Generic support +description: | + Remote Control of PSA car https://github.com/flobz/psa_car_controller +render: + - default: | + type: template + template: flobz + url: http://192.0.2.2 + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: flobz + url: http://192.0.2.2 + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + wakeup_alt: false # alternative wakeup-code; could lead to increased discharge of the 12V battery. (optional) +params: + - name: url + example: http://192.0.2.2 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: wakeup_alt + example: + default: false + choice: [] + unit: + description: + help: alternative wakeup-code; could lead to increased discharge of the 12V battery. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/renault.yaml b/templates/release/en/vehicle/renault.yaml new file mode 100644 index 0000000000..81aa25d38f --- /dev/null +++ b/templates/release/en/vehicle/renault.yaml @@ -0,0 +1,157 @@ +template: renault +product: + identifier: renault + brand: Renault +render: + - default: | + type: template + template: renault + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WREN... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: renault + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WREN... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + wakeupmode: default # Wakeup mechanism, [default, alternative, MY24] (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: WREN... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: wakeupmode + example: + default: default + choice: ['default', 'alternative', 'MY24'] + unit: + description: Wakeup mechanism + help: + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/renault_0.yaml b/templates/release/en/vehicle/renault_0.yaml deleted file mode 100644 index 514bbde560..0000000000 --- a/templates/release/en/vehicle/renault_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Renault -render: - - default: | - type: template - template: renault - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WREN... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: renault - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WREN... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - wakeupmode: default # Wakeup mechanism, [default, alternative, MY24] (optional) diff --git a/templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml b/templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml new file mode 100644 index 0000000000..19202486c1 --- /dev/null +++ b/templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml @@ -0,0 +1,148 @@ +template: seat +product: + identifier: seat-cupraconnect-gen3-ateca-leon-formentor-tarraco + brand: Seat + description: CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) +render: + - default: | + type: template + template: seat + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: seat + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml b/templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml new file mode 100644 index 0000000000..a4e6c170cb --- /dev/null +++ b/templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml @@ -0,0 +1,168 @@ +template: cupra +product: + identifier: seat-cupraconnect-gen4-born-formentor-tavascan + brand: Seat + description: CupraConnect Gen4 (Born, Formentor, Tavascan) +render: + - default: | + type: template + template: cupra + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: cupra + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/seat_0.yaml b/templates/release/en/vehicle/seat_0.yaml deleted file mode 100644 index 396e5f01cd..0000000000 --- a/templates/release/en/vehicle/seat_0.yaml +++ /dev/null @@ -1,28 +0,0 @@ -product: - brand: Seat - description: CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) -render: - - default: | - type: template - template: seat - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: seat - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/skoda-enyaq.yaml b/templates/release/en/vehicle/skoda-enyaq.yaml new file mode 100644 index 0000000000..86029b5336 --- /dev/null +++ b/templates/release/en/vehicle/skoda-enyaq.yaml @@ -0,0 +1,159 @@ +template: enyaq +product: + identifier: skoda-enyaq + brand: Skoda + description: Enyaq +render: + - default: | + type: template + template: enyaq + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + timeout: 10s # Timeout, optional + advanced: | + type: template + template: enyaq + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + timeout: 10s # Timeout, optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 10s + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/smart-1.yaml b/templates/release/en/vehicle/smart-1.yaml new file mode 100644 index 0000000000..ae72f16b08 --- /dev/null +++ b/templates/release/en/vehicle/smart-1.yaml @@ -0,0 +1,168 @@ +template: smart-hello +product: + identifier: smart-1 + brand: Smart + description: #1 +render: + - default: | + type: template + template: smart-hello + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: smart-hello + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/smart-eq.yaml b/templates/release/en/vehicle/smart-eq.yaml new file mode 100644 index 0000000000..b7c25837eb --- /dev/null +++ b/templates/release/en/vehicle/smart-eq.yaml @@ -0,0 +1,173 @@ +template: smart +product: + identifier: smart-eq + brand: Smart + description: EQ +description: | + Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. + +render: + - default: | + type: template + template: smart + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: smart + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + region: EMEA # [EMEA, APAC, NORAM] + accessToken: + refreshToken: + vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: region + example: + default: EMEA + choice: ['EMEA', 'APAC', 'NORAM'] + unit: + description: + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: vin + example: V... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/smart-hello_0.yaml b/templates/release/en/vehicle/smart-hello_0.yaml deleted file mode 100644 index a8b2821f54..0000000000 --- a/templates/release/en/vehicle/smart-hello_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Smart - description: #1 -render: - - default: | - type: template - template: smart-hello - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: smart-hello - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/smart_0.yaml b/templates/release/en/vehicle/smart_0.yaml deleted file mode 100644 index 235fd76919..0000000000 --- a/templates/release/en/vehicle/smart_0.yaml +++ /dev/null @@ -1,35 +0,0 @@ -product: - brand: Smart - description: EQ -description: | - Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. - -render: - - default: | - type: template - template: smart - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: smart - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: - vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/tesla-ble.yaml b/templates/release/en/vehicle/tesla-ble.yaml new file mode 100644 index 0000000000..d769cb2b5b --- /dev/null +++ b/templates/release/en/vehicle/tesla-ble.yaml @@ -0,0 +1,140 @@ +template: tesla-ble +product: + identifier: tesla-ble + description: Tesla BLE + group: Generic support +description: | + Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy +render: + - default: | + type: template + template: tesla-ble + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle Identification Number, Required for BLE connection + url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy + port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional) + advanced: | + type: template + template: tesla-ble + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle Identification Number, Required for BLE connection + url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy + port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: Required for BLE connection + advanced: false + optional: false + - name: url + example: http://192.168.178.27 + default: + choice: [] + unit: + description: + help: URL of the Tesla BLE HTTP Proxy + advanced: false + optional: false + - name: port + example: 8080 + default: 8080 + choice: [] + unit: + description: Port + help: Port of the Tesla BLE HTTP Proxy + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/tesla-ble_0.yaml b/templates/release/en/vehicle/tesla-ble_0.yaml deleted file mode 100644 index 735508690a..0000000000 --- a/templates/release/en/vehicle/tesla-ble_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: Tesla BLE - group: Generic support -description: | - Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy -render: - - default: | - type: template - template: tesla-ble - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle Identification Number, Required for BLE connection - url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy - port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional) - advanced: | - type: template - template: tesla-ble - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle Identification Number, Required for BLE connection - url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy - port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/tesla.yaml b/templates/release/en/vehicle/tesla.yaml new file mode 100644 index 0000000000..a1e3eff967 --- /dev/null +++ b/templates/release/en/vehicle/tesla.yaml @@ -0,0 +1,195 @@ +template: tesla +product: + identifier: tesla + brand: Tesla +requirements: ["skiptest"] +description: | + Tesla offers an official, but paid vehicle API. + For private use, you can create a [Tesla Developer Account](https://developer.tesla.com/) and receive a monthly API credit of $10. + This is usually sufficient for the common evcc use cases. + + The [myteslamate.com](https://www.myteslamate.com/tesla-api-application-registration/) guide explains the process and generates a free Access and Refresh Token. + With this token pair and your Client ID created in the Tesla Developer Account, evcc can directly communicate with the Tesla API. + You can see your used credit in the Tesla Developer Dashboard. + + To use a Tesla Wall Connector, you need a public Command Proxy Server. + [myteslamate.com](https://app.myteslamate.com/) provides such a service with per-use pricing. + Configure the Command permissions at myteslamate.com and enter the Proxy Token here. + Start, stopp and current commands are sent to Tesla via this proxy. + + More information and alternatives can be found in [our blog post](https://docs.evcc.io/en/blog/2025/01/20/tesla-api-update). + +render: + - default: | + type: template + template: tesla + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: tesla + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + commandProxy: https://api.myteslamate.com # When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) + proxyToken: # Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: clientId + example: + default: + choice: [] + unit: + description: + help: Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: + help: from [myteslamate.com](https://app.myteslamate.com/). + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: + help: from [myteslamate.com](https://app.myteslamate.com/). + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: commandProxy + example: + default: https://api.myteslamate.com + choice: [] + unit: + description: + help: When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. + advanced: true + optional: true + - name: proxyToken + example: + default: + choice: [] + unit: + description: + help: Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/tesla_0.yaml b/templates/release/en/vehicle/tesla_0.yaml deleted file mode 100644 index 24e6b4cf3d..0000000000 --- a/templates/release/en/vehicle/tesla_0.yaml +++ /dev/null @@ -1,48 +0,0 @@ -product: - brand: Tesla -requirements: ["skiptest"] -description: | - Tesla offers an official, but paid vehicle API. - For private use, you can create a [Tesla Developer Account](https://developer.tesla.com/) and receive a monthly API credit of $10. - This is usually sufficient for the common evcc use cases. - - The [myteslamate.com](https://www.myteslamate.com/tesla-api-application-registration/) guide explains the process and generates a free Access and Refresh Token. - With this token pair and your Client ID created in the Tesla Developer Account, evcc can directly communicate with the Tesla API. - You can see your used credit in the Tesla Developer Dashboard. - - To use a Tesla Wall Connector, you need a public Command Proxy Server. - [myteslamate.com](https://app.myteslamate.com/) provides such a service with per-use pricing. - Configure the Command permissions at myteslamate.com and enter the Proxy Token here. - Start, stopp and current commands are sent to Tesla via this proxy. - - More information and alternatives can be found in [our blog post](https://docs.evcc.io/en/blog/2025/01/20/tesla-api-update). - -render: - - default: | - type: template - template: tesla - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: tesla - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - commandProxy: https://api.myteslamate.com # When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) - proxyToken: # Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/teslalogger.yaml b/templates/release/en/vehicle/teslalogger.yaml new file mode 100644 index 0000000000..dec22ff5b9 --- /dev/null +++ b/templates/release/en/vehicle/teslalogger.yaml @@ -0,0 +1,140 @@ +template: teslalogger +product: + identifier: teslalogger + description: TeslaLogger + group: Generic support +description: | + Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger +render: + - default: | + type: template + template: teslalogger + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + id: 1 # TeslaLogger CarID, optional + url: http://192.0.2.2 + port: 5000 # Port, optional + advanced: | + type: template + template: teslalogger + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + id: 1 # TeslaLogger CarID, optional + url: http://192.0.2.2 + port: 5000 # Port, optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: id + example: + default: 1 + choice: [] + unit: + description: TeslaLogger CarID + help: + advanced: false + optional: true + - name: url + example: http://192.0.2.2 + default: + choice: [] + unit: + description: + help: + advanced: false + optional: false + - name: port + example: 5000 + default: 5000 + choice: [] + unit: + description: Port + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/teslalogger_0.yaml b/templates/release/en/vehicle/teslalogger_0.yaml deleted file mode 100644 index 73c9e7859c..0000000000 --- a/templates/release/en/vehicle/teslalogger_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: TeslaLogger - group: Generic support -description: | - Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger -render: - - default: | - type: template - template: teslalogger - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 - port: 5000 # Port, optional - advanced: | - type: template - template: teslalogger - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 - port: 5000 # Port, optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/teslamate.yaml b/templates/release/en/vehicle/teslamate.yaml new file mode 100644 index 0000000000..7bcbb792a0 --- /dev/null +++ b/templates/release/en/vehicle/teslamate.yaml @@ -0,0 +1,118 @@ +template: teslamate +product: + identifier: teslamate + description: TeslaMate + group: Generic support +description: | + Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT broker required. +render: + - default: | + type: template + template: teslamate + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + id: 1 # Vehicle ID, optional + advanced: | + type: template + template: teslamate + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + id: 1 # Vehicle ID, optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: id + example: + default: 1 + choice: [] + unit: + description: Vehicle ID + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/teslamate_0.yaml b/templates/release/en/vehicle/teslamate_0.yaml deleted file mode 100644 index 1d9f0a6a88..0000000000 --- a/templates/release/en/vehicle/teslamate_0.yaml +++ /dev/null @@ -1,25 +0,0 @@ -product: - description: TeslaMate - group: Generic support -description: | - Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT broker required. -render: - - default: | - type: template - template: teslamate - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - id: 1 # Vehicle ID, optional - advanced: | - type: template - template: teslamate - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - id: 1 # Vehicle ID, optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/tessie.yaml b/templates/release/en/vehicle/tessie.yaml new file mode 100644 index 0000000000..2537768787 --- /dev/null +++ b/templates/release/en/vehicle/tessie.yaml @@ -0,0 +1,129 @@ +template: tessie +product: + identifier: tessie + description: Tessie + group: Generic support +description: | + Connect your Tesla using the Tessie API. This will never wake up the car, polling can be set to "always" and interval "1M". If the vehicle is awake, the data is usually less than 15 seconds old. If the vehicle is asleep, the data is from the time the vehicle went to sleep. Get your token at https://dash.tessie.com/settings/api +render: + - default: | + type: template + template: tessie + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle VIN, If you own multiple vehicles from the same manufacturer + token: # Tessie API Token + advanced: | + type: template + template: tessie + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle VIN, If you own multiple vehicles from the same manufacturer + token: # Tessie API Token + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle VIN + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Tessie API Token + help: + advanced: false + optional: false + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/tessie_0.yaml b/templates/release/en/vehicle/tessie_0.yaml deleted file mode 100644 index 77bf181aa7..0000000000 --- a/templates/release/en/vehicle/tessie_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - description: Tessie - group: Generic support -description: | - Connect your Tesla using the Tessie API. This will never wake up the car, polling can be set to "always" and interval "1M". If the vehicle is awake, the data is usually less than 15 seconds old. If the vehicle is asleep, the data is from the time the vehicle went to sleep. Get your token at https://dash.tessie.com/settings/api -render: - - default: | - type: template - template: tessie - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle VIN, If you own multiple vehicles from the same manufacturer - token: # Tessie API Token - advanced: | - type: template - template: tessie - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle VIN, If you own multiple vehicles from the same manufacturer - token: # Tessie API Token - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/toyota.yaml b/templates/release/en/vehicle/toyota.yaml new file mode 100644 index 0000000000..894885f7a4 --- /dev/null +++ b/templates/release/en/vehicle/toyota.yaml @@ -0,0 +1,150 @@ +template: toyota +product: + identifier: toyota + brand: Toyota +description: | + Requires Toyota Connected Services Account. + +render: + - default: | + type: template + template: toyota + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: JT... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: toyota + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: JT... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: JT... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/toyota_0.yaml b/templates/release/en/vehicle/toyota_0.yaml deleted file mode 100644 index 072dfea031..0000000000 --- a/templates/release/en/vehicle/toyota_0.yaml +++ /dev/null @@ -1,30 +0,0 @@ -product: - brand: Toyota -description: | - Requires Toyota Connected Services Account. - -render: - - default: | - type: template - template: toyota - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: JT... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: toyota - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: JT... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/tronity.yaml b/templates/release/en/vehicle/tronity.yaml new file mode 100644 index 0000000000..3496a1588f --- /dev/null +++ b/templates/release/en/vehicle/tronity.yaml @@ -0,0 +1,149 @@ +template: tronity +product: + identifier: tronity + description: Tronity + group: Generic support +requirements: ["sponsorship"] +render: + - default: | + type: template + template: tronity + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + clientid: # Tronity API Client ID, Setup at https://app.tronity.tech + clientsecret: # Tronity API Client Secret, Setup at https://app.tronity.tech + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: tronity + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + clientid: # Tronity API Client ID, Setup at https://app.tronity.tech + clientsecret: # Tronity API Client Secret, Setup at https://app.tronity.tech + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: clientid + example: + default: + choice: [] + unit: + description: Tronity API Client ID + help: Setup at https://app.tronity.tech + advanced: false + optional: false + - name: clientsecret + example: + default: + choice: [] + unit: + description: Tronity API Client Secret + help: Setup at https://app.tronity.tech + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/tronity_0.yaml b/templates/release/en/vehicle/tronity_0.yaml deleted file mode 100644 index 36a8565501..0000000000 --- a/templates/release/en/vehicle/tronity_0.yaml +++ /dev/null @@ -1,29 +0,0 @@ -product: - description: Tronity - group: Generic support -requirements: ["sponsorship"] -render: - - default: | - type: template - template: tronity - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - clientid: # Tronity API Client ID, Setup at https://app.tronity.tech - clientsecret: # Tronity API Client Secret, Setup at https://app.tronity.tech - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: tronity - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - clientid: # Tronity API Client ID, Setup at https://app.tronity.tech - clientsecret: # Tronity API Client Secret, Setup at https://app.tronity.tech - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) diff --git a/templates/release/en/vehicle/volkswagen-we-connect-id.yaml b/templates/release/en/vehicle/volkswagen-we-connect-id.yaml new file mode 100644 index 0000000000..666a370180 --- /dev/null +++ b/templates/release/en/vehicle/volkswagen-we-connect-id.yaml @@ -0,0 +1,181 @@ +template: vw +product: + identifier: volkswagen-we-connect-id + brand: Volkswagen + description: We Connect ID +description: | + e-Golf, e-Up, ID family +render: + - default: | + type: template + template: vw + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WVWZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + timeout: 10s # Timeout, optional + advanced: | + type: template + template: vw + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: WVWZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + timeout: 10s # Timeout, optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) + coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional) + welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: WVWZZZ... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: timeout + example: 10s + default: 10s + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true + - name: coarsecurrent + example: + default: + choice: [] + unit: + description: 1A current control + help: Vehicle supports 1A current steps only + advanced: true + optional: true + - name: welcomecharge + example: + default: + choice: [] + unit: + description: Charge on connection + help: Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/volvo-connected_0.yaml b/templates/release/en/vehicle/volvo-connected_0.yaml deleted file mode 100644 index 3ecde57c13..0000000000 --- a/templates/release/en/vehicle/volvo-connected_0.yaml +++ /dev/null @@ -1,40 +0,0 @@ -product: - brand: Volvo -description: | - To use with EVCC, you need a Volvo account and a Volvo Connected Car API Key. - To do this, create a new application on the [Account page](https://developer.volvocars.com/account/) and save the primary VCC API key. - Now publish your application and select the permissions "Connected Vehicle API -> conve:vehicle-relation" and "Energy API -> (everything)" under "Scopes". - You must enter the URL of your EVCC instance as the redirect URL, e.g. "http://evcc.local:7070/oauth/callback". - Once the application is created, it will be displayed as "Publication under Review". This is not a problem, it still works. - When adding the vehicle via the UI, an error message is displayed. - Check the log for the message "registering oauth provider at /oauth/login?..." and open the link "http://evcc.local:7070/oauth/login?..." in a new tab. - Log in with your Volvo account and allow access to the data. If the authorization is successful, the vehicle can be added. - -render: - - default: | - type: template - template: volvo-connected - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. - vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - advanced: | - type: template - template: volvo-connected - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. - vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/volvo.yaml b/templates/release/en/vehicle/volvo.yaml new file mode 100644 index 0000000000..547f65c537 --- /dev/null +++ b/templates/release/en/vehicle/volvo.yaml @@ -0,0 +1,169 @@ +template: volvo-connected +product: + identifier: volvo + brand: Volvo +description: | + To use with EVCC, you need a Volvo account and a Volvo Connected Car API Key. + To do this, create a new application on the [Account page](https://developer.volvocars.com/account/) and save the primary VCC API key. + Now publish your application and select the permissions "Connected Vehicle API -> conve:vehicle-relation" and "Energy API -> (everything)" under "Scopes". + You must enter the URL of your EVCC instance as the redirect URL, e.g. "http://evcc.local:7070/oauth/callback". + Once the application is created, it will be displayed as "Publication under Review". This is not a problem, it still works. + When adding the vehicle via the UI, an error message is displayed. + Check the log for the message "registering oauth provider at /oauth/login?..." and open the link "http://evcc.local:7070/oauth/login?..." in a new tab. + Log in with your Volvo account and allow access to the data. If the authorization is successful, the vehicle can be added. + +render: + - default: | + type: template + template: volvo-connected + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. + vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + advanced: | + type: template + template: volvo-connected + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. + vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: vccapikey + example: + default: + choice: [] + unit: + description: + help: VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientId + example: + default: + choice: [] + unit: + description: + help: Client ID of your [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientSecret + example: + default: + choice: [] + unit: + description: + help: Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: redirectUri + example: + default: + choice: [] + unit: + description: + help: 'Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App.' + advanced: false + optional: false + - name: vin + example: WF0FXX... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/volvo2mqtt.yaml b/templates/release/en/vehicle/volvo2mqtt.yaml new file mode 100644 index 0000000000..df37953874 --- /dev/null +++ b/templates/release/en/vehicle/volvo2mqtt.yaml @@ -0,0 +1,129 @@ +template: volvo2mqtt +product: + identifier: volvo2mqtt + description: volvo2mqtt + group: Generic support +description: | + Requires MQTT broker configuration and a volvo2mqtt installation https://github.com/Dielee/volvo2mqtt +render: + - default: | + type: template + template: volvo2mqtt + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + timeout: 720h # Timeout, optional + advanced: | + type: template + template: volvo2mqtt + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer + timeout: 720h # Timeout, optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) +params: + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: false + - name: timeout + example: 10s + default: 720h + choice: [] + unit: + description: Timeout + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/volvo2mqtt_0.yaml b/templates/release/en/vehicle/volvo2mqtt_0.yaml deleted file mode 100644 index ccb0e75b83..0000000000 --- a/templates/release/en/vehicle/volvo2mqtt_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - description: volvo2mqtt - group: Generic support -description: | - Requires MQTT broker configuration and a volvo2mqtt installation https://github.com/Dielee/volvo2mqtt -render: - - default: | - type: template - template: volvo2mqtt - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - timeout: 720h # Timeout, optional - advanced: | - type: template - template: volvo2mqtt - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer - timeout: 720h # Timeout, optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) diff --git a/templates/release/en/vehicle/vw_0.yaml b/templates/release/en/vehicle/vw_0.yaml deleted file mode 100644 index 99fe3110e0..0000000000 --- a/templates/release/en/vehicle/vw_0.yaml +++ /dev/null @@ -1,34 +0,0 @@ -product: - brand: Volkswagen - description: We Connect ID -description: | - e-Golf, e-Up, ID family -render: - - default: | - type: template - template: vw - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WVWZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - timeout: 10s # Timeout, optional - advanced: | - type: template - template: vw - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: WVWZZZ... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - timeout: 10s # Timeout, optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) - coarsecurrent: # Vehicle supports 1A current steps only, 1A current control (optional) - welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional) diff --git a/templates/release/en/vehicle/zero-motorcycles.yaml b/templates/release/en/vehicle/zero-motorcycles.yaml new file mode 100644 index 0000000000..6ea42caee5 --- /dev/null +++ b/templates/release/en/vehicle/zero-motorcycles.yaml @@ -0,0 +1,147 @@ +template: zero +product: + identifier: zero-motorcycles + brand: Zero Motorcycles +render: + - default: | + type: template + template: zero + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + advanced: | + type: template + template: zero + user: # Username, e.g. email address, user id, etc. + password: # Password, Use single quotes in case of leading zeros + vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) + title: # Title, Will be displayed in the user interface (optional) + capacity: 50 # Battery capacity (kWh), optional + icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) + phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) + mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) + maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) + identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) + priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) + cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) +params: + - name: user + example: + default: + choice: [] + unit: + description: Username + help: e.g. email address, user id, etc. + advanced: false + optional: false + - name: password + example: + default: + choice: [] + unit: + description: Password + help: Use single quotes in case of leading zeros + advanced: false + optional: false + - name: vin + example: W... + default: + choice: [] + unit: + description: Vehicle Identification Number + help: If you own multiple vehicles from the same manufacturer + advanced: false + optional: true + - name: title + example: + default: + choice: [] + unit: + description: Title + help: Will be displayed in the user interface + advanced: false + optional: true + - name: capacity + example: 50 + default: + choice: [] + unit: kWh + description: Battery capacity + help: + advanced: false + optional: true + - name: icon + example: + default: car + choice: ['car', 'bike', 'bus', 'moped', 'motorcycle', 'rocket', 'scooter', 'taxi', 'tractor', 'rickshaw', 'shuttle', 'van', 'airpurifier', 'battery', 'bulb', 'climate', 'coffeemaker', 'compute', 'cooking', 'cooler', 'desktop', 'device', 'dishwasher', 'dryer', 'floorlamp', 'generic', 'heater', 'heatexchange', 'heatpump', 'kettle', 'laundry', 'laundry2', 'machine', 'meter', 'microwave', 'pump', 'smartconsumer', 'tool', 'waterheater'] + unit: + description: Icon + help: Will be displayed in the user interface + advanced: true + optional: true + - name: phases + example: 3 + default: + choice: [] + unit: + description: Maximum number of phases + help: The maximum number of phases which can be used + advanced: true + optional: true + - name: mode + example: + default: + choice: [] + unit: + description: Default charging mode when a vehicle is connected + help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + advanced: true + optional: true + - name: minCurrent + example: 6 + default: + choice: [] + unit: A + description: Minimum amperage + help: The minimum amperage per connected phase with which the car should be charged + advanced: true + optional: true + - name: maxCurrent + example: 16 + default: + choice: [] + unit: A + description: Maximum amperage + help: The maximum amperage per connected phase with which the car shuold be charged + advanced: true + optional: true + - name: identifiers + example: + default: + choice: [] + unit: + description: Identification + help: 'Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle' + advanced: true + optional: true + - name: priority + example: + default: + choice: [] + unit: + description: Priority + help: Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy + advanced: true + optional: true + - name: cache + example: 5m + default: 15m + choice: [] + unit: + description: Cache + help: Time interval with when data should be reloaded from the vehicle + advanced: true + optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/zero_0.yaml b/templates/release/en/vehicle/zero_0.yaml deleted file mode 100644 index 79052fe3a3..0000000000 --- a/templates/release/en/vehicle/zero_0.yaml +++ /dev/null @@ -1,27 +0,0 @@ -product: - brand: Zero Motorcycles -render: - - default: | - type: template - template: zero - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - advanced: | - type: template - template: zero - user: # Username, e.g. email address, user id, etc. - password: # Password, Use single quotes in case of leading zeros - vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) - title: # Title, Will be displayed in the user interface (optional) - capacity: 50 # Battery capacity (kWh), optional - icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) - phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) - minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) - maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) - identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) - priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) From e976c54982599a1f370059da871222152753fd3e Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Fri, 13 Jun 2025 11:54:15 +0200 Subject: [PATCH 08/10] icons --- package-lock.json | 8 ++++---- package.json | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package-lock.json b/package-lock.json index d941dd488c..1d4f7bdc8d 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,7 +13,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.8", + "@evcc/icons": "^0.5.9", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -4523,9 +4523,9 @@ } }, "node_modules/@evcc/icons": { - "version": "0.5.8", - "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.8.tgz", - "integrity": "sha512-RbnX/4HEOgNzdiEs4Du11usuoD7KtzBtTxL57GObELc8SFg1RoE9rlR1RbnNbj8bAnCcrnr7+4CgJmUXkF+Scg==", + "version": "0.5.9", + "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.9.tgz", + "integrity": "sha512-c9Hof95fxDo/QaygRhpnZURw1l2E7GeD8thKvf7mKW6goDZSubIP6sb7WeSY1Uq5I4AW0XbYH6LTZej66PSd3w==", "license": "CC-BY-NC-SA-4.0", "dependencies": { "fuse.js": "^7.1.0" diff --git a/package.json b/package.json index cd5763db85..c848da67d9 100644 --- a/package.json +++ b/package.json @@ -26,7 +26,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.8", + "@evcc/icons": "^0.5.9", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", From 4d76b82c920678ba0c3e34e077dcd10c0d9cc2f6 Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Fri, 13 Jun 2025 17:00:19 +0200 Subject: [PATCH 09/10] add icon to detail --- .../chargers/abb-terra-ac-ocpp.mdx | 42 +- docs/devices-next/chargers/abb-terra-ac.mdx | 18 +- .../chargers/abl-em4-single-ocpp.mdx | 42 +- .../chargers/abl-em4-single-sbcx.mdx | 20 +- .../chargers/abl-em4-twin-ocpp.mdx | 42 +- .../chargers/abl-em4-twin-sbcx.mdx | 20 +- docs/devices-next/chargers/abl-emh1.mdx | 18 +- docs/devices-next/chargers/abl-emh2-ocpp.mdx | 42 +- docs/devices-next/chargers/abl-emh2.mdx | 18 +- docs/devices-next/chargers/abl-emh3-ocpp.mdx | 42 +- docs/devices-next/chargers/alfen-eve-ocpp.mdx | 42 +- docs/devices-next/chargers/alfen-eve.mdx | 18 +- docs/devices-next/chargers/alpha-innotec.mdx | 28 +- .../chargers/alphatec-ladesaule-twin.mdx | 18 +- .../chargers/alphatec-wallbox-mini.mdx | 18 +- .../chargers/alphatec-wallbox-power.mdx | 18 +- .../amperfied-wallbox-connect-business.mdx | 18 +- .../amperfied-wallbox-connect-home.mdx | 18 +- .../amperfied-wallbox-connect-solar.mdx | 18 +- .../amperfied-wallbox-energy-control.mdx | 18 +- docs/devices-next/chargers/ampure-next.mdx | 16 +- docs/devices-next/chargers/ampure-unite.mdx | 18 +- .../chargers/audi-wallbox-plus.mdx | 16 +- .../chargers/audi-wallbox-pro.mdx | 16 +- .../chargers/autel-ac-compact.mdx | 42 +- .../chargers/autel-ac-maxicharger.mdx | 42 +- .../chargers/autoaid-business-wallbox.mdx | 42 +- .../chargers/autoaid-intelligent-wallbox.mdx | 42 +- docs/devices-next/chargers/avm-fritzdect.mdx | 16 +- docs/devices-next/chargers/bender-cc612.mdx | 18 +- docs/devices-next/chargers/bender-cc613.mdx | 18 +- docs/devices-next/chargers/bender-icc1314.mdx | 18 +- docs/devices-next/chargers/bender-icc1324.mdx | 18 +- docs/devices-next/chargers/bmw-i-wallbox.mdx | 18 +- docs/devices-next/chargers/bosch-sg-ready.mdx | 20 +- docs/devices-next/chargers/bosch-x-change.mdx | 20 +- .../chargers/buderus-logamatic-hmc-20-z.mdx | 28 +- .../chargers/buderus-logamatic-hmc-20.mdx | 28 +- .../chargers/buderus-sg-ready.mdx | 20 +- .../chargers/cfos-power-brain-solar.mdx | 16 +- .../chargers/cfos-power-brain.mdx | 16 +- .../chargers/charge-amps-halo.mdx | 42 +- docs/devices-next/chargers/compleo-ebox.mdx | 18 +- .../chargers/cta-all-in-one-aeroplus.mdx | 28 +- docs/devices-next/chargers/cubos-c11e.mdx | 18 +- docs/devices-next/chargers/cubos-c22e.mdx | 18 +- .../chargers/cupra-charger-connect-2.mdx | 16 +- .../chargers/cupra-charger-connect.mdx | 16 +- .../chargers/cupra-charger-pro-2.mdx | 16 +- .../cupra-charger-pro-eichrecht-2.mdx | 16 +- .../chargers/cupra-charger-pro.mdx | 16 +- .../chargers/dadapower-premium-wallbox.mdx | 18 +- .../chargers/daheimladen-wallbox.mdx | 16 +- .../chargers/daikin-homehub-sg-ready.mdx | 18 +- .../chargers/delta-ac-max-basic.mdx | 20 +- .../chargers/delta-ac-max-smart.mdx | 20 +- .../chargers/delta-slim-charger.mdx | 20 +- .../chargers/delta-ultra-fast-charger.mdx | 20 +- docs/devices-next/chargers/demo-charger.mdx | 16 +- .../devices-next/chargers/e-on-drive-ebox.mdx | 18 +- .../devices-next/chargers/e-on-drive-vbox.mdx | 18 +- .../chargers/e3-dc-easy-connect.mdx | 18 +- .../chargers/easee-charge-core.mdx | 24 +- .../chargers/easee-charge-lite.mdx | 24 +- docs/devices-next/chargers/easee-charge.mdx | 24 +- docs/devices-next/chargers/easee-home.mdx | 24 +- docs/devices-next/chargers/ebee-wallbox.mdx | 18 +- docs/devices-next/chargers/echarge-cph1.mdx | 18 +- docs/devices-next/chargers/echarge-cph2.mdx | 16 +- docs/devices-next/chargers/echarge-cpm2.mdx | 16 +- .../chargers/ecoharmony-evse-epc-2-0-plus.mdx | 18 +- .../chargers/edgetech-smart-evse.mdx | 18 +- .../chargers/eebus-compatible.mdx | 16 +- docs/devices-next/chargers/elco.mdx | 28 +- docs/devices-next/chargers/elecq-biz.mdx | 42 +- docs/devices-next/chargers/elecq-home.mdx | 42 +- docs/devices-next/chargers/elecq-station.mdx | 42 +- docs/devices-next/chargers/eledio-go.mdx | 42 +- .../chargers/elli-charger-connect-2.mdx | 16 +- .../chargers/elli-charger-connect.mdx | 16 +- .../chargers/elli-charger-pro-2.mdx | 16 +- .../chargers/elli-charger-pro-eichrecht-2.mdx | 16 +- .../chargers/elli-charger-pro.mdx | 16 +- docs/devices-next/chargers/em2go-home.mdx | 16 +- .../chargers/em2go-pro-power-ocpp-onc.mdx | 18 +- docs/devices-next/chargers/enercab-smart.mdx | 42 +- .../chargers/enplus-ac-ev-charger.mdx | 42 +- .../chargers/ensto-chago-wallbox.mdx | 18 +- .../chargers/entratek-power-dot-fix.mdx | 42 +- .../chargers/entratek-power-dot-pro-2.mdx | 42 +- .../devices-next/chargers/esl-walli-light.mdx | 18 +- .../chargers/esystems-ghostone.mdx | 16 +- docs/devices-next/chargers/etrel-inch-duo.mdx | 18 +- docs/devices-next/chargers/etrel-inch.mdx | 16 +- docs/devices-next/chargers/evbox-elvi.mdx | 44 +- docs/devices-next/chargers/evbox-livo.mdx | 16 +- docs/devices-next/chargers/evse-din.mdx | 18 +- docs/devices-next/chargers/evse-wifi.mdx | 16 +- .../chargers/free2move-eprowallbox-move.mdx | 18 +- .../chargers/free2move-eprowallbox.mdx | 18 +- .../free2move-esolutions-eprowallbox.mdx | 42 +- .../chargers/fronius-wattpilot-ocpp.mdx | 42 +- docs/devices-next/chargers/garo-glb.mdx | 18 +- docs/devices-next/chargers/garo-glbplus.mdx | 18 +- .../chargers/garo-ls4-compact.mdx | 18 +- docs/devices-next/chargers/garo-ls4.mdx | 18 +- .../chargers/go-e-charger-gemini-ocpp.mdx | 42 +- .../chargers/go-e-charger-gemini.mdx | 16 +- .../chargers/go-e-charger-homefix.mdx | 16 +- .../chargers/go-e-charger-homeplus.mdx | 16 +- .../chargers/go-e-charger-pro-ocpp.mdx | 42 +- .../chargers/go-e-charger-pro.mdx | 16 +- .../chargers/go-e-charger-v3-ocpp.mdx | 42 +- .../devices-next/chargers/go-e-charger-v3.mdx | 16 +- .../chargers/hardy-barth-cph1.mdx | 18 +- .../chargers/hardy-barth-cph2.mdx | 16 +- .../chargers/hardy-barth-cpm2.mdx | 16 +- .../chargers/heidelberg-energy-control.mdx | 18 +- docs/devices-next/chargers/hesotec-ebox.mdx | 18 +- docs/devices-next/chargers/hesotec-esat.mdx | 18 +- .../chargers/home-assistant-switch.mdx | 16 +- .../chargers/homecharge-homecharger.mdx | 42 +- docs/devices-next/chargers/homematic-ip.mdx | 34 +- docs/devices-next/chargers/homewizard.mdx | 16 +- .../chargers/huawei-scharger-22kt-s0.mdx | 42 +- .../chargers/huawei-scharger-7ks-s0.mdx | 42 +- docs/devices-next/chargers/idm.mdx | 18 +- docs/devices-next/chargers/innogy-ebox.mdx | 18 +- docs/devices-next/chargers/inro-pantabox.mdx | 16 +- .../chargers/juice-charger-me.mdx | 18 +- .../chargers/junkers-sg-ready.mdx | 20 +- .../chargers/kathrein-kwb-ac20.mdx | 18 +- .../chargers/kathrein-kwb-ac35.mdx | 18 +- .../chargers/kathrein-kwb-ac40-e.mdx | 18 +- .../chargers/kathrein-kwb-ac40.mdx | 18 +- .../chargers/kathrein-kwb-ac60-e.mdx | 18 +- .../chargers/kathrein-kwb-ac60.mdx | 18 +- .../chargers/keba-kecontact-p20.mdx | 18 +- .../chargers/keba-kecontact-p30-c-series.mdx | 18 +- .../chargers/keba-kecontact-p30-x-series.mdx | 18 +- .../chargers/keba-kecontact-p40-pro.mdx | 18 +- .../chargers/keba-kecontact-p40.mdx | 18 +- .../chargers/kermi-x-center-pro.mdx | 20 +- .../chargers/kontron-solar-charger.mdx | 16 +- docs/devices-next/chargers/kostal-enector.mdx | 18 +- docs/devices-next/chargers/kse-wbx16.mdx | 18 +- .../devices-next/chargers/ladefoxx-evload.mdx | 20 +- .../chargers/ladefoxx-mikro-2-0.mdx | 20 +- .../chargers/lambda-eu-l-series.mdx | 20 +- .../chargers/lrt-home-essentialplus.mdx | 18 +- .../chargers/mennekes-amedio-professional.mdx | 18 +- .../mennekes-amtron-4business-700.mdx | 18 +- .../chargers/mennekes-amtron-4you-300.mdx | 18 +- .../chargers/mennekes-amtron-4you-500.mdx | 18 +- .../mennekes-amtron-chargecontrol.mdx | 18 +- .../chargers/mennekes-amtron-compact-2-0s.mdx | 18 +- .../chargers/mennekes-amtron-premium.mdx | 18 +- .../chargers/mennekes-amtron-professional.mdx | 18 +- .../chargers/mennekes-amtron-xtra.mdx | 18 +- .../mennekes-emobility-gateway-acu.mdx | 42 +- .../chargers/mennekes-smart-acu.mdx | 42 +- .../chargers/mennekes-smart-t-acu.mdx | 42 +- .../devices-next/chargers/my-pv-ac-elwa-2.mdx | 18 +- .../chargers/my-pv-ac-thor-9s.mdx | 22 +- docs/devices-next/chargers/my-pv-ac-thor.mdx | 22 +- docs/devices-next/chargers/mystrom-switch.mdx | 16 +- docs/devices-next/chargers/nibe-ap-aw10.mdx | 28 +- .../devices-next/chargers/novelan-wpr-net.mdx | 28 +- .../devices-next/chargers/nrgkick-connect.mdx | 20 +- docs/devices-next/chargers/nrgkick-gen2.mdx | 22 +- .../chargers/obo-bettermann-ion.mdx | 18 +- .../ocpp-1-6j-compatible-smart-charging.mdx | 42 +- docs/devices-next/chargers/openevse.mdx | 16 +- docs/devices-next/chargers/openwb-pro.mdx | 16 +- docs/devices-next/chargers/openwb-series2.mdx | 18 +- .../chargers/openwb-software-2-x.mdx | 20 +- .../chargers/optec-mobility-one.mdx | 18 +- docs/devices-next/chargers/orbis-viaris.mdx | 42 +- .../chargers/pc-electric-garo.mdx | 16 +- .../devices-next/chargers/peblar-business.mdx | 18 +- .../chargers/peblar-home-plus.mdx | 18 +- docs/devices-next/chargers/peblar-home.mdx | 18 +- .../chargers/phoenix-contact-charx.mdx | 20 +- .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 18 +- ...ix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 18 +- ...oenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 18 +- ...nix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 18 +- ...hoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 18 +- .../chargers/phoenix-contact-ev-ser.mdx | 18 +- docs/devices-next/chargers/plugchoice.mdx | 32 +- .../porsche-mobile-charger-connect.mdx | 16 +- .../chargers/porsche-mobile-charger-plus.mdx | 16 +- .../devices-next/chargers/porsche-wallbox.mdx | 16 +- .../devices-next/chargers/pracht-alpha-xt.mdx | 20 +- docs/devices-next/chargers/pracht-mono-xt.mdx | 20 +- docs/devices-next/chargers/pracht-pni.mdx | 20 +- docs/devices-next/chargers/pracht-xtplus.mdx | 20 +- .../chargers/pulsares-simplebox.mdx | 18 +- docs/devices-next/chargers/pulsatrix.mdx | 16 +- .../chargers/qcells-q-home-edrive-a.mdx | 18 +- .../devices-next/chargers/roth-thermoaura.mdx | 28 +- .../chargers/roth-thermoterra.mdx | 28 +- .../chargers/schneider-evlink-pro.mdx | 18 +- .../chargers/schrack-i-charge-cion.mdx | 18 +- .../chargers/senec-wallbox-pro-s.mdx | 18 +- .../chargers/senec-wallbox-pro.mdx | 18 +- docs/devices-next/chargers/shelly-1.mdx | 22 +- docs/devices-next/chargers/shelly-plug-s.mdx | 22 +- docs/devices-next/chargers/shelly-plus-1.mdx | 22 +- docs/devices-next/chargers/shelly-pro-1.mdx | 22 +- .../chargers/siemens-versicharge-gen3.mdx | 18 +- .../chargers/skoda-charger-connect.mdx | 16 +- .../chargers/skoda-charger-pro-eichrecht.mdx | 16 +- .../chargers/skoda-charger-pro.mdx | 16 +- .../chargers/skoda-iv-charger-connect.mdx | 16 +- .../chargers/skoda-iv-charger-connectplus.mdx | 16 +- docs/devices-next/chargers/sma-echarger.mdx | 16 +- docs/devices-next/chargers/sma-ev-charger.mdx | 16 +- .../chargers/smartfox-pro-charger.mdx | 18 +- docs/devices-next/chargers/smartwb.mdx | 16 +- .../chargers/solaredge-home-ev-charger.mdx | 18 +- docs/devices-next/chargers/solax-x3-evc.mdx | 18 +- .../chargers/sonnen-sonnencharger.mdx | 16 +- .../chargers/spelsberg-wallbox-smart-pro.mdx | 18 +- .../chargers/stark-in-strom-easy.mdx | 18 +- .../stiebel-eltron-lwa-lwz-sg-ready.mdx | 18 +- .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 18 +- .../chargers/sungrow-ac011e-01.mdx | 18 +- docs/devices-next/chargers/sungrow-ac011e.mdx | 42 +- .../chargers/sungrow-ac22e-01.mdx | 18 +- .../chargers/tasmota-single-phase.mdx | 16 +- .../chargers/tecalor-thz-sg-ready.mdx | 18 +- .../chargers/technisat-technivolt.mdx | 18 +- .../chargers/tesla-wall-connector-gen-3.mdx | 16 +- docs/devices-next/chargers/tessie.mdx | 20 +- .../chargers/tigo-go-ev-charger.mdx | 18 +- .../chargers/tinkerforge-warp-charger-pro.mdx | 22 +- .../tinkerforge-warp-charger-smart.mdx | 22 +- .../tinkerforge-warp3-charger-pro.mdx | 16 +- .../tinkerforge-warp3-charger-smart.mdx | 16 +- .../chargers/tp-link-h-series-smart-plug.mdx | 16 +- .../tp-link-tapo-p-series-smart-plug.mdx | 16 +- .../chargers/ubitricity-heinz.mdx | 18 +- docs/devices-next/chargers/v2c-trydan.mdx | 16 +- .../chargers/vaillant-sensonet-sg-ready.mdx | 28 +- .../chargers/vestel-connect-plus.mdx | 18 +- .../chargers/vestel-evc04-home-smart.mdx | 18 +- .../victron-ev-charging-station-via-gx.mdx | 18 +- .../chargers/victron-ev-charging-station.mdx | 18 +- .../chargers/viessmann-heatpump-sg-ready.mdx | 20 +- .../viridian-ev-evse-epc-2-0-plus.mdx | 18 +- .../chargers/volkswagen-charger-connect-2.mdx | 16 +- .../chargers/volkswagen-charger-pro-2.mdx | 16 +- .../volkswagen-charger-pro-eichrecht-2.mdx | 16 +- .../volkswagen-id-charger-connect.mdx | 16 +- .../chargers/volkswagen-id-charger-pro.mdx | 16 +- docs/devices-next/chargers/volt-time-one.mdx | 24 +- .../chargers/volt-time-source-2.mdx | 24 +- .../chargers/volt-time-source-2s.mdx | 24 +- .../chargers/volt-time-source.mdx | 24 +- .../chargers/wallbe-eco-2-0-s.mdx | 18 +- docs/devices-next/chargers/wallbe-eco.mdx | 18 +- docs/devices-next/chargers/wallbe-pro.mdx | 18 +- .../chargers/wallbox-commander-2-fw-5-x.mdx | 42 +- .../chargers/wallbox-commander-2.mdx | 42 +- .../chargers/wallbox-copper-sb-fw-5-x.mdx | 42 +- .../chargers/wallbox-copper-sb.mdx | 42 +- .../chargers/wallbox-pulsar-max-fw-5-x.mdx | 42 +- .../chargers/wallbox-pulsar-max.mdx | 42 +- .../chargers/wallbox-pulsar-plus-fw-5-x.mdx | 42 +- .../chargers/wallbox-pulsar-plus.mdx | 42 +- .../chargers/walther-werke-basic-evo-pro.mdx | 18 +- docs/devices-next/chargers/webasto-live.mdx | 18 +- docs/devices-next/chargers/webasto-next.mdx | 16 +- docs/devices-next/chargers/webasto-unite.mdx | 18 +- .../chargers/weidmuller-ac-smart.mdx | 16 +- docs/devices-next/chargers/wolf-bwl.mdx | 28 +- docs/devices-next/chargers/wolf-bws.mdx | 28 +- docs/devices-next/chargers/zaptec-go-2.mdx | 20 +- docs/devices-next/chargers/zaptec-go-ocpp.mdx | 42 +- docs/devices-next/chargers/zaptec-go.mdx | 20 +- docs/devices-next/chargers/zaptec-pro.mdx | 20 +- .../chargers/zewotherm-eu-l-series.mdx | 20 +- .../chargers/zj-beny-bcp-ev-charger.mdx | 42 +- docs/devices-next/meters/a-tronix.mdx | 26 +- docs/devices-next/meters/abb-a43.mdx | 18 +- docs/devices-next/meters/abb-a44.mdx | 18 +- docs/devices-next/meters/abb-b23.mdx | 18 +- docs/devices-next/meters/abb-b24.mdx | 18 +- docs/devices-next/meters/acrel-adw300.mdx | 18 +- docs/devices-next/meters/ads-tec-storaxe.mdx | 18 +- .../meters/alpha-ess-storion-smile.mdx | 47 +- .../meters/ampere-ampere-storagepro.mdx | 72 +- .../meters/anker-micro-inverter.mdx | 18 +- docs/devices-next/meters/apsystems-ez1.mdx | 16 +- docs/devices-next/meters/avm-fritzdect.mdx | 16 +- .../meters/axitec-axihycon-12-15h.mdx | 18 +- .../meters/bernecker-engineering-mpm3pm.mdx | 18 +- docs/devices-next/meters/bgetech-ds100.mdx | 18 +- docs/devices-next/meters/bgetech-ws100.mdx | 18 +- .../meters/bosch-bpt-s-5-hybrid.mdx | 16 +- .../meters/bosswerk-micro-inverter.mdx | 18 +- .../meters/carlo-gavazzi-em110-111-112.mdx | 18 +- .../meters/carlo-gavazzi-em24.mdx | 18 +- .../meters/carlo-gavazzi-em24_e1.mdx | 18 +- .../meters/carlo-gavazzi-em330-em340.mdx | 18 +- .../meters/carlo-gavazzi-em530-em540.mdx | 18 +- .../meters/carlo-gavazzi-et112.mdx | 18 +- .../meters/carlo-gavazzi-et330-et340.mdx | 18 +- .../meters/cfos-powerbrain-meter.mdx | 18 +- docs/devices-next/meters/demo-battery.mdx | 16 +- docs/devices-next/meters/demo-meter.mdx | 16 +- .../meters/deye-3p-hybrid-inverter.mdx | 47 +- .../meters/deye-hp3-hybrid-inverter.mdx | 30 +- .../meters/deye-micro-inverter.mdx | 18 +- .../meters/deye-storage-hybrid-inverter.mdx | 18 +- .../meters/deye-string-inverter.mdx | 18 +- docs/devices-next/meters/discovergy.mdx | 22 +- docs/devices-next/meters/dsmr.mdx | 16 +- docs/devices-next/meters/dzg-dvh4013.mdx | 18 +- docs/devices-next/meters/e3-dc.mdx | 30 +- .../meters/eastron-sdm120-modbus.mdx | 18 +- .../meters/eastron-sdm220-230.mdx | 18 +- .../meters/eastron-sdm630-modbus.mdx | 18 +- docs/devices-next/meters/eastron-sdm72d-m.mdx | 18 +- .../meters/eastron-sdm72dm-v2.mdx | 18 +- docs/devices-next/meters/enphase-iq-envoy.mdx | 30 +- .../meters/esphome-dlms-meter-austria.mdx | 16 +- docs/devices-next/meters/esphome-dsmr.mdx | 16 +- docs/devices-next/meters/fenecon.mdx | 24 +- .../foxess-h1-series-hybrid-inverter.mdx | 18 +- .../foxess-h3-series-hybrid-inverter.mdx | 47 +- ...foxess-h3-smart-series-hybrid-inverter.mdx | 47 +- docs/devices-next/meters/fronius-ohmpilot.mdx | 16 +- .../meters/fronius-primo-gen24-plus.mdx | 20 +- .../fronius-smartmeter-via-inverter.mdx | 18 +- .../meters/fronius-solar-api-v1.mdx | 24 +- .../meters/fronius-symo-gen24-plus.mdx | 20 +- ...nlong-solis-hybrid-inverter-rhi-series.mdx | 18 +- ...ginlong-solis-hybrid-inverter-s-series.mdx | 18 +- .../meters/ginlong-solis-inverter.mdx | 18 +- docs/devices-next/meters/go-e-controller.mdx | 16 +- .../goodwe-et-eh-bh-bt-hybrid-inverter.mdx | 30 +- .../meters/goodwe-goodwe-over-wifi.mdx | 16 +- .../meters/goodwe-sdt-dt-inverter.mdx | 18 +- .../meters/growatt-hybrid-inverter.mdx | 18 +- .../meters/growatt-tl-x-h-hybrid-inverter.mdx | 18 +- docs/devices-next/meters/homematic-ip.mdx | 38 +- .../meters/homewizard-kwh-meter.mdx | 16 +- .../meters/homewizard-wi-fi-p1-meter.mdx | 16 +- ...hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 20 +- ...hoymiles-hm-and-hms-series-via-opendtu.mdx | 16 +- docs/devices-next/meters/huawei-emma.mdx | 18 +- .../meters/huawei-smartlogger.mdx | 26 +- .../meters/huawei-sun2000-sdongle.mdx | 18 +- docs/devices-next/meters/huawei-sun2000.mdx | 26 +- docs/devices-next/meters/iammeter-wem3080.mdx | 16 +- .../iammeter-wem3080t-wem3046t-wem3050t.mdx | 16 +- .../meters/igen-tech-solarman-logger.mdx | 16 +- .../devices-next/meters/inepro-pro380-mod.mdx | 18 +- docs/devices-next/meters/iometer.mdx | 16 +- docs/devices-next/meters/janitza-b-series.mdx | 18 +- .../meters/janitza-umg-series.mdx | 18 +- .../meters/keba-kecontact-e10.mdx | 18 +- .../meters/kostal-energy-meter-c-kem-c.mdx | 18 +- .../meters/kostal-energy-meter-p-kem-p.mdx | 18 +- docs/devices-next/meters/kostal-piko-ba.mdx | 16 +- .../meters/kostal-piko-hybrid.mdx | 16 +- .../meters/kostal-piko-legacy.mdx | 16 +- .../meters/kostal-piko-mp-plus.mdx | 16 +- docs/devices-next/meters/kostal-piko.mdx | 16 +- ...ncl-grid-charging-of-the-house-battery.mdx | 24 +- .../meters/kostal-plenticore-hybrid.mdx | 26 +- ...kostal-smart-energy-meter-via-inverter.mdx | 18 +- .../meters/kostal-smart-energy-meter.mdx | 18 +- docs/devices-next/meters/lg-ess-home-15.mdx | 28 +- docs/devices-next/meters/lg-ess-home-8-10.mdx | 28 +- .../devices-next/meters/loxone-miniserver.mdx | 16 +- .../meters/m-tec-energy-butler-gen2.mdx | 18 +- .../meters/m-tec-energy-butler-gen3.mdx | 18 +- .../meters/marstek-venus-battery-storage.mdx | 30 +- .../meters/mhendriks-p1-dongle.mdx | 16 +- docs/devices-next/meters/my-pv-ac-elwa-2.mdx | 16 +- docs/devices-next/meters/my-pv-ac-elwa-e.mdx | 16 +- docs/devices-next/meters/my-pv-ac-thor.mdx | 16 +- docs/devices-next/meters/my-pv-wifi-meter.mdx | 18 +- docs/devices-next/meters/mystrom-switch.mdx | 16 +- docs/devices-next/meters/openems.mdx | 24 +- docs/devices-next/meters/orno-or-we-516.mdx | 18 +- docs/devices-next/meters/orno-or-we-517.mdx | 18 +- .../meters/p1monitor-p1-monitor.mdx | 16 +- docs/devices-next/meters/plexlog.mdx | 18 +- docs/devices-next/meters/powerdog.mdx | 18 +- .../meters/powerfox-poweropti.mdx | 22 +- .../meters/qcells-hybrid-inverter-cloud.mdx | 16 +- .../meters/qcells-q-home-ess-hyb-g3.mdx | 40 +- docs/devices-next/meters/rct-power.mdx | 26 +- .../meters/saia-burgess-controls-sbc-ale3.mdx | 18 +- .../meters/saia-burgess-controls-sbc-awd3.mdx | 18 +- .../saj-h1-series-hybrid-solar-inverter.mdx | 18 +- .../saj-h2-series-hybrid-solar-inverter.mdx | 72 +- .../meters/saj-r5-series-solar-inverter.mdx | 18 +- docs/devices-next/meters/sax-homespeicher.mdx | 18 +- .../schneider-electric-iem3xxx-modbus.mdx | 18 +- docs/devices-next/meters/senec-home.mdx | 26 +- .../senergy-se-4-5-6ktl-s1-g2-inverter.mdx | 18 +- docs/devices-next/meters/shelly-1pm-mini.mdx | 24 +- docs/devices-next/meters/shelly-1pm.mdx | 24 +- docs/devices-next/meters/shelly-3em.mdx | 16 +- docs/devices-next/meters/shelly-em.mdx | 24 +- docs/devices-next/meters/shelly-plug-s.mdx | 24 +- docs/devices-next/meters/shelly-pm-mini.mdx | 24 +- docs/devices-next/meters/shelly-pro-1pm.mdx | 24 +- docs/devices-next/meters/shelly-pro-3-em.mdx | 16 +- .../meters/shelly-pro-3em-monophase-mode.mdx | 24 +- docs/devices-next/meters/shelly-pro-em.mdx | 24 +- docs/devices-next/meters/siemens-7kt1665.mdx | 18 +- .../siemens-junelight-smart-battery.mdx | 18 +- docs/devices-next/meters/siemens-pac-2200.mdx | 18 +- ...igen-hybrid-sigen-pv-max-sigenstore-ec.mdx | 26 +- docs/devices-next/meters/sma-data-manager.mdx | 18 +- docs/devices-next/meters/sma-energy-meter.mdx | 16 +- .../meters/sma-inverter-speedwire.mdx | 16 +- .../sma-smart-energy-hybrid-inverter.mdx | 22 +- ...a-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx | 22 +- ...a-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx | 22 +- .../meters/sma-sunny-home-manager-2-0.mdx | 16 +- .../meters/sma-sunny-island-modbus.mdx | 22 +- docs/devices-next/meters/sma-webbox.mdx | 18 +- .../meters/sma-wechselrichter-modbus.mdx | 18 +- docs/devices-next/meters/smartfox-box.mdx | 16 +- .../meters/smartfox-light-em2-firmware.mdx | 16 +- docs/devices-next/meters/smartfox-pro-2.mdx | 16 +- .../meters/smartfox-pro-light-2.mdx | 16 +- .../meters/smartfox-pro-light.mdx | 16 +- docs/devices-next/meters/smartfox-pro.mdx | 16 +- .../meters/smartfox-reg-extended.mdx | 16 +- docs/devices-next/meters/smartfox-reg.mdx | 16 +- .../meters/sofarsolar-hybrid-inverter.mdx | 18 +- .../meters/sofarsolar-hyd-3-6k-ep.mdx | 26 +- .../meters/sofarsolar-hyd-5-20k-3ph.mdx | 26 +- .../meters/sofarsolar-inverter.mdx | 18 +- .../meters/sofarsolar-sofar-5-24ktl-g3.mdx | 26 +- .../meters/sofarsolar-sofar-80-136ktl.mdx | 26 +- .../meters/solaranzeige-solaranzeige.mdx | 16 +- .../meters/solaredge-hybrid-inverter.mdx | 26 +- .../meters/solaredge-inverter.mdx | 18 +- docs/devices-next/meters/solarlog.mdx | 16 +- ...armax-max-storage-max-storage-ultimate.mdx | 26 +- .../meters/solarmax-solarmax-smt.mdx | 18 +- .../meters/solarmax-sp-series-inverter.mdx | 18 +- .../meters/solarwatt-energymanager-pro.mdx | 16 +- .../meters/solarwatt-energymanager.mdx | 16 +- .../meters/solarwatt-manager-flex.mdx | 16 +- ...myreserve-matrix-lan-oder-powergateway.mdx | 16 +- .../meters/solarwatt-myreserve.mdx | 16 +- .../meters/solax-hybrid-inverter-cloud.mdx | 20 +- .../meters/solax-hybrid-x1-x3-g3-g4.mdx | 40 +- .../meters/solax-inverter-cloud.mdx | 20 +- docs/devices-next/meters/solinteng.mdx | 26 +- docs/devices-next/meters/sonnen-comfort.mdx | 16 +- docs/devices-next/meters/sonnen-eco-5.mdx | 16 +- docs/devices-next/meters/sonnen-eco-6.mdx | 16 +- docs/devices-next/meters/sonnen-oem-6-5.mdx | 16 +- .../meters/sonnen-sonnenbatterie.mdx | 22 +- docs/devices-next/meters/st-ems.mdx | 26 +- .../meters/steca-coolcept-flex.mdx | 16 +- .../meters/sungrow-sg-series-inverter.mdx | 18 +- .../sungrow-sh-series-hybrid-inverter.mdx | 18 +- .../meters/sunspec-battery-model-124.mdx | 18 +- .../meters/sunspec-battery-model-802.mdx | 18 +- .../meters/sunspec-hybrid-inverter.mdx | 18 +- docs/devices-next/meters/sunspec-inverter.mdx | 18 +- docs/devices-next/meters/sunspec-meter.mdx | 18 +- .../meters/sunsynk-3p-hybrid-inverter.mdx | 47 +- .../meters/sunsynk-hp3-hybrid-inverter.mdx | 30 +- .../meters/sunsynk-micro-inverter.mdx | 18 +- .../sunsynk-storage-hybrid-inverter.mdx | 18 +- .../meters/sunsynk-string-inverter.mdx | 18 +- docs/devices-next/meters/sunway.mdx | 26 +- ...ml-ir-reader-for-smartmeters-e-g-hichi.mdx | 16 +- ...tasmota-tasmota-1-phase-plus-sml-meter.mdx | 16 +- .../meters/tasmota-three-phase.mdx | 16 +- docs/devices-next/meters/tesla-powerwall.mdx | 56 +- docs/devices-next/meters/tibber-pulse.mdx | 24 +- .../meters/tp-link-h-series-smart-plug.mdx | 16 +- .../tp-link-tapo-p-series-smart-plug.mdx | 16 +- .../meters/tq-energy-manager-em2xx-em3xx.mdx | 16 +- .../meters/tq-energy-manager-em420.mdx | 20 +- docs/devices-next/meters/varta-element.mdx | 16 +- docs/devices-next/meters/varta-pulse-neo.mdx | 16 +- docs/devices-next/meters/varta-pulse.mdx | 16 +- docs/devices-next/meters/victron-em24.mdx | 18 +- docs/devices-next/meters/victron-em24_e1.mdx | 18 +- .../meters/victron-em530-em540.mdx | 18 +- docs/devices-next/meters/victron-energy.mdx | 33 +- docs/devices-next/meters/victron-et340.mdx | 18 +- ...volkszahler-http-api-import-and-export.mdx | 28 +- .../meters/volkszahler-http-api.mdx | 24 +- .../meters/volkszahler-websocket-api.mdx | 20 +- docs/devices-next/meters/vzlogger.mdx | 58 +- docs/devices-next/meters/wago-879-30xx.mdx | 18 +- docs/devices-next/meters/wattsonic.mdx | 26 +- .../meters/weidmuller-em110-rtu-2p.mdx | 18 +- .../meters/weidmuller-em111-rtu-2p.mdx | 18 +- .../meters/weidmuller-em120-rtu-2p.mdx | 18 +- .../meters/weidmuller-em122-rtu-2p.mdx | 18 +- .../meters/youless-energy-monitor.mdx | 16 +- .../meters/zcs-azzurro-hybrid-inverter.mdx | 18 +- .../meters/zcs-azzurro-inverter.mdx | 18 +- .../meters/zendure-hyper-2000.mdx | 40 +- ...uidwijk-slimmelezer-plus-in-luxembourg.mdx | 16 +- .../meters/zuidwijk-slimmelezer-plus-v2.mdx | 16 +- .../meters/zuidwijk-slimmelezer-plus.mdx | 16 +- docs/devices-next/tariffs/amber-electric.mdx | 34 +- docs/devices-next/tariffs/awattar.mdx | 22 +- .../electricity-maps-commercial-api.mdx | 24 +- .../tariffs/electricity-maps-free-api.mdx | 24 +- docs/devices-next/tariffs/energinet.mdx | 22 +- docs/devices-next/tariffs/enever.mdx | 32 +- docs/devices-next/tariffs/entso-e.mdx | 28 +- docs/devices-next/tariffs/forecast-solar.mdx | 24 +- docs/devices-next/tariffs/fraunhofer-ise.mdx | 22 +- .../tariffs/green-grid-compass.mdx | 16 +- .../tariffs/groupe-e-vario-plus.mdx | 16 +- docs/devices-next/tariffs/grunstromindex.mdx | 24 +- .../tariffs/national-grid-eso.mdx | 24 +- .../tariffs/nordpool-spot-prices.mdx | 28 +- .../tariffs/octopus-energy-api.mdx | 24 +- .../tariffs/octopus-energy-product-code.mdx | 28 +- docs/devices-next/tariffs/open-meteo.mdx | 20 +- docs/devices-next/tariffs/ostrom.mdx | 28 +- docs/devices-next/tariffs/pun-orario.mdx | 16 +- .../tariffs/smartenergy-smartcontrol.mdx | 16 +- docs/devices-next/tariffs/solcast.mdx | 40 +- docs/devices-next/tariffs/spotty-energie.mdx | 28 +- docs/devices-next/tariffs/tibber.mdx | 28 +- .../tariffs/victron-vrm-solar-forecast.mdx | 22 +- docs/devices-next/vehicles/aiways.mdx | 20 +- docs/devices-next/vehicles/audi.mdx | 20 +- docs/devices-next/vehicles/bmw.mdx | 26 +- docs/devices-next/vehicles/citroen.mdx | 32 +- docs/devices-next/vehicles/dacia.mdx | 20 +- docs/devices-next/vehicles/ds.mdx | 32 +- docs/devices-next/vehicles/evnotify.mdx | 32 +- docs/devices-next/vehicles/fiat.mdx | 26 +- docs/devices-next/vehicles/ford.mdx | 32 +- .../vehicles/generic-vehicle-without-api.mdx | 20 +- .../vehicles/hyundai-bluelink.mdx | 20 +- docs/devices-next/vehicles/iobroker-bmw.mdx | 26 +- docs/devices-next/vehicles/iso15118.mdx | 20 +- docs/devices-next/vehicles/jeep.mdx | 26 +- docs/devices-next/vehicles/kia-bluelink.mdx | 20 +- docs/devices-next/vehicles/mercedes-benz.mdx | 38 +- docs/devices-next/vehicles/mg.mdx | 20 +- docs/devices-next/vehicles/mg2mqtt.mdx | 20 +- docs/devices-next/vehicles/mini.mdx | 26 +- docs/devices-next/vehicles/mz2mqtt.mdx | 20 +- docs/devices-next/vehicles/nissan-ariya.mdx | 20 +- .../vehicles/nissan-leaf-pre-2019.mdx | 20 +- docs/devices-next/vehicles/nissan-leaf.mdx | 20 +- docs/devices-next/vehicles/niu-e-scooter.mdx | 16 +- docs/devices-next/vehicles/opel.mdx | 32 +- .../open-vehicle-monitoring-system.mdx | 30 +- docs/devices-next/vehicles/peugeot.mdx | 32 +- docs/devices-next/vehicles/polestar.mdx | 20 +- .../vehicles/psa-car-controller.mdx | 30 +- docs/devices-next/vehicles/renault.mdx | 20 +- ...nect-gen3-ateca-leon-formentor-tarraco.mdx | 20 +- ...raconnect-gen4-born-formentor-tavascan.mdx | 20 +- docs/devices-next/vehicles/skoda-enyaq.mdx | 20 +- docs/devices-next/vehicles/smart-1.mdx | 20 +- docs/devices-next/vehicles/smart-eq.mdx | 38 +- docs/devices-next/vehicles/tesla-ble.mdx | 26 +- docs/devices-next/vehicles/tesla.mdx | 46 +- docs/devices-next/vehicles/teslalogger.mdx | 26 +- docs/devices-next/vehicles/teslamate.mdx | 20 +- docs/devices-next/vehicles/tessie.mdx | 20 +- docs/devices-next/vehicles/toyota.mdx | 20 +- docs/devices-next/vehicles/tronity.mdx | 20 +- .../vehicles/volkswagen-we-connect-id.mdx | 20 +- docs/devices-next/vehicles/volvo.mdx | 44 +- docs/devices-next/vehicles/volvo2mqtt.mdx | 20 +- .../vehicles/zero-motorcycles.mdx | 20 +- docs/devices/chargers.mdx | 770 +++++++++--------- docs/devices/heating.mdx | 90 +- docs/devices/meters.mdx | 696 +++++----------- docs/devices/smartswitches.mdx | 26 +- docs/devices/vehicles.mdx | 234 +++--- docs/tariffs.mdx | 118 +-- .../chargers/abb-terra-ac-ocpp.mdx | 42 +- .../devices-next/chargers/abb-terra-ac.mdx | 18 +- .../chargers/abl-em4-single-ocpp.mdx | 42 +- .../chargers/abl-em4-single-sbcx.mdx | 20 +- .../chargers/abl-em4-twin-ocpp.mdx | 42 +- .../chargers/abl-em4-twin-sbcx.mdx | 20 +- .../devices-next/chargers/abl-emh1.mdx | 18 +- .../devices-next/chargers/abl-emh2-ocpp.mdx | 42 +- .../devices-next/chargers/abl-emh2.mdx | 18 +- .../devices-next/chargers/abl-emh3-ocpp.mdx | 42 +- .../devices-next/chargers/alfen-eve-ocpp.mdx | 42 +- .../devices-next/chargers/alfen-eve.mdx | 18 +- .../devices-next/chargers/alpha-innotec.mdx | 28 +- .../chargers/alphatec-ladesaule-twin.mdx | 18 +- .../chargers/alphatec-wallbox-mini.mdx | 18 +- .../chargers/alphatec-wallbox-power.mdx | 18 +- .../amperfied-wallbox-connect-business.mdx | 18 +- .../amperfied-wallbox-connect-home.mdx | 18 +- .../amperfied-wallbox-connect-solar.mdx | 18 +- .../amperfied-wallbox-energy-control.mdx | 18 +- .../devices-next/chargers/ampure-next.mdx | 16 +- .../devices-next/chargers/ampure-unite.mdx | 18 +- .../chargers/audi-wallbox-plus.mdx | 16 +- .../chargers/audi-wallbox-pro.mdx | 16 +- .../chargers/autel-ac-compact.mdx | 42 +- .../chargers/autel-ac-maxicharger.mdx | 42 +- .../chargers/autoaid-business-wallbox.mdx | 42 +- .../chargers/autoaid-intelligent-wallbox.mdx | 42 +- .../devices-next/chargers/avm-fritzdect.mdx | 16 +- .../devices-next/chargers/bender-cc612.mdx | 18 +- .../devices-next/chargers/bender-cc613.mdx | 18 +- .../devices-next/chargers/bender-icc1314.mdx | 18 +- .../devices-next/chargers/bender-icc1324.mdx | 18 +- .../devices-next/chargers/bmw-i-wallbox.mdx | 18 +- .../devices-next/chargers/bosch-sg-ready.mdx | 20 +- .../devices-next/chargers/bosch-x-change.mdx | 20 +- .../chargers/buderus-logamatic-hmc-20-z.mdx | 28 +- .../chargers/buderus-logamatic-hmc-20.mdx | 28 +- .../chargers/buderus-sg-ready.mdx | 20 +- .../chargers/cfos-power-brain-solar.mdx | 16 +- .../chargers/cfos-power-brain.mdx | 16 +- .../chargers/charge-amps-halo.mdx | 42 +- .../devices-next/chargers/compleo-ebox.mdx | 18 +- .../chargers/cta-all-in-one-aeroplus.mdx | 28 +- .../devices-next/chargers/cubos-c11e.mdx | 18 +- .../devices-next/chargers/cubos-c22e.mdx | 18 +- .../chargers/cupra-charger-connect-2.mdx | 16 +- .../chargers/cupra-charger-connect.mdx | 16 +- .../chargers/cupra-charger-pro-2.mdx | 16 +- .../cupra-charger-pro-eichrecht-2.mdx | 16 +- .../chargers/cupra-charger-pro.mdx | 16 +- .../chargers/dadapower-premium-wallbox.mdx | 18 +- .../chargers/daheimladen-wallbox.mdx | 16 +- .../chargers/daikin-homehub-sg-ready.mdx | 18 +- .../chargers/delta-ac-max-basic.mdx | 20 +- .../chargers/delta-ac-max-smart.mdx | 20 +- .../chargers/delta-slim-charger.mdx | 20 +- .../chargers/delta-ultra-fast-charger.mdx | 20 +- .../devices-next/chargers/demo-charger.mdx | 16 +- .../devices-next/chargers/e-on-drive-ebox.mdx | 18 +- .../devices-next/chargers/e-on-drive-vbox.mdx | 18 +- .../chargers/e3-dc-easy-connect.mdx | 18 +- .../chargers/easee-charge-core.mdx | 24 +- .../chargers/easee-charge-lite.mdx | 24 +- .../devices-next/chargers/easee-charge.mdx | 24 +- .../devices-next/chargers/easee-home.mdx | 24 +- .../devices-next/chargers/ebee-wallbox.mdx | 18 +- .../devices-next/chargers/echarge-cph1.mdx | 18 +- .../devices-next/chargers/echarge-cph2.mdx | 16 +- .../devices-next/chargers/echarge-cpm2.mdx | 16 +- .../chargers/ecoharmony-evse-epc-2-0-plus.mdx | 18 +- .../chargers/edgetech-smart-evse.mdx | 18 +- .../chargers/eebus-compatible.mdx | 16 +- .../current/devices-next/chargers/elco.mdx | 28 +- .../devices-next/chargers/elecq-biz.mdx | 42 +- .../devices-next/chargers/elecq-home.mdx | 42 +- .../devices-next/chargers/elecq-station.mdx | 42 +- .../devices-next/chargers/eledio-go.mdx | 42 +- .../chargers/elli-charger-connect-2.mdx | 16 +- .../chargers/elli-charger-connect.mdx | 16 +- .../chargers/elli-charger-pro-2.mdx | 16 +- .../chargers/elli-charger-pro-eichrecht-2.mdx | 16 +- .../chargers/elli-charger-pro.mdx | 16 +- .../devices-next/chargers/em2go-home.mdx | 16 +- .../chargers/em2go-pro-power-ocpp-onc.mdx | 18 +- .../devices-next/chargers/enercab-smart.mdx | 42 +- .../chargers/enplus-ac-ev-charger.mdx | 42 +- .../chargers/ensto-chago-wallbox.mdx | 18 +- .../chargers/entratek-power-dot-fix.mdx | 42 +- .../chargers/entratek-power-dot-pro-2.mdx | 42 +- .../devices-next/chargers/esl-walli-light.mdx | 18 +- .../chargers/esystems-ghostone.mdx | 16 +- .../devices-next/chargers/etrel-inch-duo.mdx | 18 +- .../devices-next/chargers/etrel-inch.mdx | 16 +- .../devices-next/chargers/evbox-elvi.mdx | 44 +- .../devices-next/chargers/evbox-livo.mdx | 16 +- .../devices-next/chargers/evse-din.mdx | 18 +- .../devices-next/chargers/evse-wifi.mdx | 16 +- .../chargers/free2move-eprowallbox-move.mdx | 18 +- .../chargers/free2move-eprowallbox.mdx | 18 +- .../free2move-esolutions-eprowallbox.mdx | 42 +- .../chargers/fronius-wattpilot-ocpp.mdx | 42 +- .../devices-next/chargers/garo-glb.mdx | 18 +- .../devices-next/chargers/garo-glbplus.mdx | 18 +- .../chargers/garo-ls4-compact.mdx | 18 +- .../devices-next/chargers/garo-ls4.mdx | 18 +- .../chargers/go-e-charger-gemini-ocpp.mdx | 42 +- .../chargers/go-e-charger-gemini.mdx | 16 +- .../chargers/go-e-charger-homefix.mdx | 16 +- .../chargers/go-e-charger-homeplus.mdx | 16 +- .../chargers/go-e-charger-pro-ocpp.mdx | 42 +- .../chargers/go-e-charger-pro.mdx | 16 +- .../chargers/go-e-charger-v3-ocpp.mdx | 42 +- .../devices-next/chargers/go-e-charger-v3.mdx | 16 +- .../chargers/hardy-barth-cph1.mdx | 18 +- .../chargers/hardy-barth-cph2.mdx | 16 +- .../chargers/hardy-barth-cpm2.mdx | 16 +- .../chargers/heidelberg-energy-control.mdx | 18 +- .../devices-next/chargers/hesotec-ebox.mdx | 18 +- .../devices-next/chargers/hesotec-esat.mdx | 18 +- .../chargers/home-assistant-switch.mdx | 16 +- .../chargers/homecharge-homecharger.mdx | 42 +- .../devices-next/chargers/homematic-ip.mdx | 34 +- .../devices-next/chargers/homewizard.mdx | 16 +- .../chargers/huawei-scharger-22kt-s0.mdx | 42 +- .../chargers/huawei-scharger-7ks-s0.mdx | 42 +- .../current/devices-next/chargers/idm.mdx | 18 +- .../devices-next/chargers/innogy-ebox.mdx | 18 +- .../devices-next/chargers/inro-pantabox.mdx | 16 +- .../chargers/juice-charger-me.mdx | 18 +- .../chargers/junkers-sg-ready.mdx | 20 +- .../chargers/kathrein-kwb-ac20.mdx | 18 +- .../chargers/kathrein-kwb-ac35.mdx | 18 +- .../chargers/kathrein-kwb-ac40-e.mdx | 18 +- .../chargers/kathrein-kwb-ac40.mdx | 18 +- .../chargers/kathrein-kwb-ac60-e.mdx | 18 +- .../chargers/kathrein-kwb-ac60.mdx | 18 +- .../chargers/keba-kecontact-p20.mdx | 18 +- .../chargers/keba-kecontact-p30-c-series.mdx | 18 +- .../chargers/keba-kecontact-p30-x-series.mdx | 18 +- .../chargers/keba-kecontact-p40-pro.mdx | 18 +- .../chargers/keba-kecontact-p40.mdx | 18 +- .../chargers/kermi-x-center-pro.mdx | 20 +- .../chargers/kontron-solar-charger.mdx | 16 +- .../devices-next/chargers/kostal-enector.mdx | 18 +- .../devices-next/chargers/kse-wbx16.mdx | 18 +- .../devices-next/chargers/ladefoxx-evload.mdx | 20 +- .../chargers/ladefoxx-mikro-2-0.mdx | 20 +- .../chargers/lambda-eu-l-series.mdx | 20 +- .../chargers/lrt-home-essentialplus.mdx | 18 +- .../chargers/mennekes-amedio-professional.mdx | 18 +- .../mennekes-amtron-4business-700.mdx | 18 +- .../chargers/mennekes-amtron-4you-300.mdx | 18 +- .../chargers/mennekes-amtron-4you-500.mdx | 18 +- .../mennekes-amtron-chargecontrol.mdx | 18 +- .../chargers/mennekes-amtron-compact-2-0s.mdx | 18 +- .../chargers/mennekes-amtron-premium.mdx | 18 +- .../chargers/mennekes-amtron-professional.mdx | 18 +- .../chargers/mennekes-amtron-xtra.mdx | 18 +- .../mennekes-emobility-gateway-acu.mdx | 42 +- .../chargers/mennekes-smart-acu.mdx | 42 +- .../chargers/mennekes-smart-t-acu.mdx | 42 +- .../devices-next/chargers/my-pv-ac-elwa-2.mdx | 18 +- .../chargers/my-pv-ac-thor-9s.mdx | 22 +- .../devices-next/chargers/my-pv-ac-thor.mdx | 22 +- .../devices-next/chargers/mystrom-switch.mdx | 16 +- .../devices-next/chargers/nibe-ap-aw10.mdx | 28 +- .../devices-next/chargers/novelan-wpr-net.mdx | 28 +- .../devices-next/chargers/nrgkick-connect.mdx | 20 +- .../devices-next/chargers/nrgkick-gen2.mdx | 22 +- .../chargers/obo-bettermann-ion.mdx | 18 +- .../ocpp-1-6j-compatible-smart-charging.mdx | 42 +- .../devices-next/chargers/openevse.mdx | 16 +- .../devices-next/chargers/openwb-pro.mdx | 16 +- .../devices-next/chargers/openwb-series2.mdx | 18 +- .../chargers/openwb-software-2-x.mdx | 20 +- .../chargers/optec-mobility-one.mdx | 18 +- .../devices-next/chargers/orbis-viaris.mdx | 42 +- .../chargers/pc-electric-garo.mdx | 16 +- .../devices-next/chargers/peblar-business.mdx | 18 +- .../chargers/peblar-home-plus.mdx | 18 +- .../devices-next/chargers/peblar-home.mdx | 18 +- .../chargers/phoenix-contact-charx.mdx | 20 +- .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 18 +- ...ix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 18 +- ...oenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 18 +- ...nix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 18 +- ...hoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 18 +- .../chargers/phoenix-contact-ev-ser.mdx | 18 +- .../devices-next/chargers/plugchoice.mdx | 32 +- .../porsche-mobile-charger-connect.mdx | 16 +- .../chargers/porsche-mobile-charger-plus.mdx | 16 +- .../devices-next/chargers/porsche-wallbox.mdx | 16 +- .../devices-next/chargers/pracht-alpha-xt.mdx | 20 +- .../devices-next/chargers/pracht-mono-xt.mdx | 20 +- .../devices-next/chargers/pracht-pni.mdx | 20 +- .../devices-next/chargers/pracht-xtplus.mdx | 20 +- .../chargers/pulsares-simplebox.mdx | 18 +- .../devices-next/chargers/pulsatrix.mdx | 16 +- .../chargers/qcells-q-home-edrive-a.mdx | 18 +- .../devices-next/chargers/roth-thermoaura.mdx | 28 +- .../chargers/roth-thermoterra.mdx | 28 +- .../chargers/schneider-evlink-pro.mdx | 18 +- .../chargers/schrack-i-charge-cion.mdx | 18 +- .../chargers/senec-wallbox-pro-s.mdx | 18 +- .../chargers/senec-wallbox-pro.mdx | 18 +- .../devices-next/chargers/shelly-1.mdx | 22 +- .../devices-next/chargers/shelly-plug-s.mdx | 22 +- .../devices-next/chargers/shelly-plus-1.mdx | 22 +- .../devices-next/chargers/shelly-pro-1.mdx | 22 +- .../chargers/siemens-versicharge-gen3.mdx | 18 +- .../chargers/skoda-charger-connect.mdx | 16 +- .../chargers/skoda-charger-pro-eichrecht.mdx | 16 +- .../chargers/skoda-charger-pro.mdx | 16 +- .../chargers/skoda-iv-charger-connect.mdx | 16 +- .../chargers/skoda-iv-charger-connectplus.mdx | 16 +- .../devices-next/chargers/sma-echarger.mdx | 16 +- .../devices-next/chargers/sma-ev-charger.mdx | 16 +- .../chargers/smartfox-pro-charger.mdx | 18 +- .../current/devices-next/chargers/smartwb.mdx | 16 +- .../chargers/solaredge-home-ev-charger.mdx | 18 +- .../devices-next/chargers/solax-x3-evc.mdx | 18 +- .../chargers/sonnen-sonnencharger.mdx | 16 +- .../chargers/spelsberg-wallbox-smart-pro.mdx | 18 +- .../chargers/stark-in-strom-easy.mdx | 18 +- .../stiebel-eltron-lwa-lwz-sg-ready.mdx | 18 +- .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 18 +- .../chargers/sungrow-ac011e-01.mdx | 18 +- .../devices-next/chargers/sungrow-ac011e.mdx | 42 +- .../chargers/sungrow-ac22e-01.mdx | 18 +- .../chargers/tasmota-single-phase.mdx | 16 +- .../chargers/tecalor-thz-sg-ready.mdx | 18 +- .../chargers/technisat-technivolt.mdx | 18 +- .../chargers/tesla-wall-connector-gen-3.mdx | 16 +- .../current/devices-next/chargers/tessie.mdx | 20 +- .../chargers/tigo-go-ev-charger.mdx | 18 +- .../chargers/tinkerforge-warp-charger-pro.mdx | 22 +- .../tinkerforge-warp-charger-smart.mdx | 22 +- .../tinkerforge-warp3-charger-pro.mdx | 16 +- .../tinkerforge-warp3-charger-smart.mdx | 16 +- .../chargers/tp-link-h-series-smart-plug.mdx | 16 +- .../tp-link-tapo-p-series-smart-plug.mdx | 16 +- .../chargers/ubitricity-heinz.mdx | 18 +- .../devices-next/chargers/v2c-trydan.mdx | 16 +- .../chargers/vaillant-sensonet-sg-ready.mdx | 28 +- .../chargers/vestel-connect-plus.mdx | 18 +- .../chargers/vestel-evc04-home-smart.mdx | 18 +- .../victron-ev-charging-station-via-gx.mdx | 18 +- .../chargers/victron-ev-charging-station.mdx | 18 +- .../chargers/viessmann-heatpump-sg-ready.mdx | 20 +- .../viridian-ev-evse-epc-2-0-plus.mdx | 18 +- .../chargers/volkswagen-charger-connect-2.mdx | 16 +- .../chargers/volkswagen-charger-pro-2.mdx | 16 +- .../volkswagen-charger-pro-eichrecht-2.mdx | 16 +- .../volkswagen-id-charger-connect.mdx | 16 +- .../chargers/volkswagen-id-charger-pro.mdx | 16 +- .../devices-next/chargers/volt-time-one.mdx | 24 +- .../chargers/volt-time-source-2.mdx | 24 +- .../chargers/volt-time-source-2s.mdx | 24 +- .../chargers/volt-time-source.mdx | 24 +- .../chargers/wallbe-eco-2-0-s.mdx | 18 +- .../devices-next/chargers/wallbe-eco.mdx | 18 +- .../devices-next/chargers/wallbe-pro.mdx | 18 +- .../chargers/wallbox-commander-2-fw-5-x.mdx | 42 +- .../chargers/wallbox-commander-2.mdx | 42 +- .../chargers/wallbox-copper-sb-fw-5-x.mdx | 42 +- .../chargers/wallbox-copper-sb.mdx | 42 +- .../chargers/wallbox-pulsar-max-fw-5-x.mdx | 42 +- .../chargers/wallbox-pulsar-max.mdx | 42 +- .../chargers/wallbox-pulsar-plus-fw-5-x.mdx | 42 +- .../chargers/wallbox-pulsar-plus.mdx | 42 +- .../chargers/walther-werke-basic-evo-pro.mdx | 18 +- .../devices-next/chargers/webasto-live.mdx | 18 +- .../devices-next/chargers/webasto-next.mdx | 16 +- .../devices-next/chargers/webasto-unite.mdx | 18 +- .../chargers/weidmuller-ac-smart.mdx | 16 +- .../devices-next/chargers/wolf-bwl.mdx | 28 +- .../devices-next/chargers/wolf-bws.mdx | 28 +- .../devices-next/chargers/zaptec-go-2.mdx | 20 +- .../devices-next/chargers/zaptec-go-ocpp.mdx | 42 +- .../devices-next/chargers/zaptec-go.mdx | 20 +- .../devices-next/chargers/zaptec-pro.mdx | 20 +- .../chargers/zewotherm-eu-l-series.mdx | 20 +- .../chargers/zj-beny-bcp-ev-charger.mdx | 42 +- .../current/devices-next/meters/a-tronix.mdx | 26 +- .../current/devices-next/meters/abb-a43.mdx | 18 +- .../current/devices-next/meters/abb-a44.mdx | 18 +- .../current/devices-next/meters/abb-b23.mdx | 18 +- .../current/devices-next/meters/abb-b24.mdx | 18 +- .../devices-next/meters/acrel-adw300.mdx | 18 +- .../devices-next/meters/ads-tec-storaxe.mdx | 18 +- .../meters/alpha-ess-storion-smile.mdx | 47 +- .../meters/ampere-ampere-storagepro.mdx | 72 +- .../meters/anker-micro-inverter.mdx | 18 +- .../devices-next/meters/apsystems-ez1.mdx | 16 +- .../devices-next/meters/avm-fritzdect.mdx | 16 +- .../meters/axitec-axihycon-12-15h.mdx | 18 +- .../meters/bernecker-engineering-mpm3pm.mdx | 18 +- .../devices-next/meters/bgetech-ds100.mdx | 18 +- .../devices-next/meters/bgetech-ws100.mdx | 18 +- .../meters/bosch-bpt-s-5-hybrid.mdx | 16 +- .../meters/bosswerk-micro-inverter.mdx | 18 +- .../meters/carlo-gavazzi-em110-111-112.mdx | 18 +- .../meters/carlo-gavazzi-em24.mdx | 18 +- .../meters/carlo-gavazzi-em24_e1.mdx | 18 +- .../meters/carlo-gavazzi-em330-em340.mdx | 18 +- .../meters/carlo-gavazzi-em530-em540.mdx | 18 +- .../meters/carlo-gavazzi-et112.mdx | 18 +- .../meters/carlo-gavazzi-et330-et340.mdx | 18 +- .../meters/cfos-powerbrain-meter.mdx | 18 +- .../devices-next/meters/demo-battery.mdx | 16 +- .../devices-next/meters/demo-meter.mdx | 16 +- .../meters/deye-3p-hybrid-inverter.mdx | 47 +- .../meters/deye-hp3-hybrid-inverter.mdx | 30 +- .../meters/deye-micro-inverter.mdx | 18 +- .../meters/deye-storage-hybrid-inverter.mdx | 18 +- .../meters/deye-string-inverter.mdx | 18 +- .../devices-next/meters/discovergy.mdx | 22 +- .../current/devices-next/meters/dsmr.mdx | 16 +- .../devices-next/meters/dzg-dvh4013.mdx | 18 +- .../current/devices-next/meters/e3-dc.mdx | 30 +- .../meters/eastron-sdm120-modbus.mdx | 18 +- .../meters/eastron-sdm220-230.mdx | 18 +- .../meters/eastron-sdm630-modbus.mdx | 18 +- .../devices-next/meters/eastron-sdm72d-m.mdx | 18 +- .../meters/eastron-sdm72dm-v2.mdx | 18 +- .../devices-next/meters/enphase-iq-envoy.mdx | 30 +- .../meters/esphome-dlms-meter-austria.mdx | 16 +- .../devices-next/meters/esphome-dsmr.mdx | 16 +- .../current/devices-next/meters/fenecon.mdx | 24 +- .../foxess-h1-series-hybrid-inverter.mdx | 18 +- .../foxess-h3-series-hybrid-inverter.mdx | 47 +- ...foxess-h3-smart-series-hybrid-inverter.mdx | 47 +- .../devices-next/meters/fronius-ohmpilot.mdx | 16 +- .../meters/fronius-primo-gen24-plus.mdx | 20 +- .../fronius-smartmeter-via-inverter.mdx | 18 +- .../meters/fronius-solar-api-v1.mdx | 24 +- .../meters/fronius-symo-gen24-plus.mdx | 20 +- ...nlong-solis-hybrid-inverter-rhi-series.mdx | 18 +- ...ginlong-solis-hybrid-inverter-s-series.mdx | 18 +- .../meters/ginlong-solis-inverter.mdx | 18 +- .../devices-next/meters/go-e-controller.mdx | 16 +- .../goodwe-et-eh-bh-bt-hybrid-inverter.mdx | 30 +- .../meters/goodwe-goodwe-over-wifi.mdx | 16 +- .../meters/goodwe-sdt-dt-inverter.mdx | 18 +- .../meters/growatt-hybrid-inverter.mdx | 18 +- .../meters/growatt-tl-x-h-hybrid-inverter.mdx | 18 +- .../devices-next/meters/homematic-ip.mdx | 38 +- .../meters/homewizard-kwh-meter.mdx | 16 +- .../meters/homewizard-wi-fi-p1-meter.mdx | 16 +- ...hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 20 +- ...hoymiles-hm-and-hms-series-via-opendtu.mdx | 16 +- .../devices-next/meters/huawei-emma.mdx | 18 +- .../meters/huawei-smartlogger.mdx | 26 +- .../meters/huawei-sun2000-sdongle.mdx | 18 +- .../devices-next/meters/huawei-sun2000.mdx | 26 +- .../devices-next/meters/iammeter-wem3080.mdx | 16 +- .../iammeter-wem3080t-wem3046t-wem3050t.mdx | 16 +- .../meters/igen-tech-solarman-logger.mdx | 16 +- .../devices-next/meters/inepro-pro380-mod.mdx | 18 +- .../current/devices-next/meters/iometer.mdx | 16 +- .../devices-next/meters/janitza-b-series.mdx | 18 +- .../meters/janitza-umg-series.mdx | 18 +- .../meters/keba-kecontact-e10.mdx | 18 +- .../meters/kostal-energy-meter-c-kem-c.mdx | 18 +- .../meters/kostal-energy-meter-p-kem-p.mdx | 18 +- .../devices-next/meters/kostal-piko-ba.mdx | 16 +- .../meters/kostal-piko-hybrid.mdx | 16 +- .../meters/kostal-piko-legacy.mdx | 16 +- .../meters/kostal-piko-mp-plus.mdx | 16 +- .../devices-next/meters/kostal-piko.mdx | 16 +- ...ncl-grid-charging-of-the-house-battery.mdx | 24 +- .../meters/kostal-plenticore-hybrid.mdx | 26 +- ...kostal-smart-energy-meter-via-inverter.mdx | 18 +- .../meters/kostal-smart-energy-meter.mdx | 18 +- .../devices-next/meters/lg-ess-home-15.mdx | 28 +- .../devices-next/meters/lg-ess-home-8-10.mdx | 28 +- .../devices-next/meters/loxone-miniserver.mdx | 16 +- .../meters/m-tec-energy-butler-gen2.mdx | 18 +- .../meters/m-tec-energy-butler-gen3.mdx | 18 +- .../meters/marstek-venus-battery-storage.mdx | 30 +- .../meters/mhendriks-p1-dongle.mdx | 16 +- .../devices-next/meters/my-pv-ac-elwa-2.mdx | 16 +- .../devices-next/meters/my-pv-ac-elwa-e.mdx | 16 +- .../devices-next/meters/my-pv-ac-thor.mdx | 16 +- .../devices-next/meters/my-pv-wifi-meter.mdx | 18 +- .../devices-next/meters/mystrom-switch.mdx | 16 +- .../current/devices-next/meters/openems.mdx | 24 +- .../devices-next/meters/orno-or-we-516.mdx | 18 +- .../devices-next/meters/orno-or-we-517.mdx | 18 +- .../meters/p1monitor-p1-monitor.mdx | 16 +- .../current/devices-next/meters/plexlog.mdx | 18 +- .../current/devices-next/meters/powerdog.mdx | 18 +- .../meters/powerfox-poweropti.mdx | 22 +- .../meters/qcells-hybrid-inverter-cloud.mdx | 16 +- .../meters/qcells-q-home-ess-hyb-g3.mdx | 40 +- .../current/devices-next/meters/rct-power.mdx | 26 +- .../meters/saia-burgess-controls-sbc-ale3.mdx | 18 +- .../meters/saia-burgess-controls-sbc-awd3.mdx | 18 +- .../saj-h1-series-hybrid-solar-inverter.mdx | 18 +- .../saj-h2-series-hybrid-solar-inverter.mdx | 72 +- .../meters/saj-r5-series-solar-inverter.mdx | 18 +- .../devices-next/meters/sax-homespeicher.mdx | 18 +- .../schneider-electric-iem3xxx-modbus.mdx | 18 +- .../devices-next/meters/senec-home.mdx | 26 +- .../senergy-se-4-5-6ktl-s1-g2-inverter.mdx | 18 +- .../devices-next/meters/shelly-1pm-mini.mdx | 24 +- .../devices-next/meters/shelly-1pm.mdx | 24 +- .../devices-next/meters/shelly-3em.mdx | 16 +- .../current/devices-next/meters/shelly-em.mdx | 24 +- .../devices-next/meters/shelly-plug-s.mdx | 24 +- .../devices-next/meters/shelly-pm-mini.mdx | 24 +- .../devices-next/meters/shelly-pro-1pm.mdx | 24 +- .../devices-next/meters/shelly-pro-3-em.mdx | 16 +- .../meters/shelly-pro-3em-monophase-mode.mdx | 24 +- .../devices-next/meters/shelly-pro-em.mdx | 24 +- .../devices-next/meters/siemens-7kt1665.mdx | 18 +- .../siemens-junelight-smart-battery.mdx | 18 +- .../devices-next/meters/siemens-pac-2200.mdx | 18 +- ...igen-hybrid-sigen-pv-max-sigenstore-ec.mdx | 26 +- .../devices-next/meters/sma-data-manager.mdx | 18 +- .../devices-next/meters/sma-energy-meter.mdx | 16 +- .../meters/sma-inverter-speedwire.mdx | 16 +- .../sma-smart-energy-hybrid-inverter.mdx | 22 +- ...a-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx | 22 +- ...a-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx | 22 +- .../meters/sma-sunny-home-manager-2-0.mdx | 16 +- .../meters/sma-sunny-island-modbus.mdx | 22 +- .../devices-next/meters/sma-webbox.mdx | 18 +- .../meters/sma-wechselrichter-modbus.mdx | 18 +- .../devices-next/meters/smartfox-box.mdx | 16 +- .../meters/smartfox-light-em2-firmware.mdx | 16 +- .../devices-next/meters/smartfox-pro-2.mdx | 16 +- .../meters/smartfox-pro-light-2.mdx | 16 +- .../meters/smartfox-pro-light.mdx | 16 +- .../devices-next/meters/smartfox-pro.mdx | 16 +- .../meters/smartfox-reg-extended.mdx | 16 +- .../devices-next/meters/smartfox-reg.mdx | 16 +- .../meters/sofarsolar-hybrid-inverter.mdx | 18 +- .../meters/sofarsolar-hyd-3-6k-ep.mdx | 26 +- .../meters/sofarsolar-hyd-5-20k-3ph.mdx | 26 +- .../meters/sofarsolar-inverter.mdx | 18 +- .../meters/sofarsolar-sofar-5-24ktl-g3.mdx | 26 +- .../meters/sofarsolar-sofar-80-136ktl.mdx | 26 +- .../meters/solaranzeige-solaranzeige.mdx | 16 +- .../meters/solaredge-hybrid-inverter.mdx | 26 +- .../meters/solaredge-inverter.mdx | 18 +- .../current/devices-next/meters/solarlog.mdx | 16 +- ...armax-max-storage-max-storage-ultimate.mdx | 26 +- .../meters/solarmax-solarmax-smt.mdx | 18 +- .../meters/solarmax-sp-series-inverter.mdx | 18 +- .../meters/solarwatt-energymanager-pro.mdx | 16 +- .../meters/solarwatt-energymanager.mdx | 16 +- .../meters/solarwatt-manager-flex.mdx | 16 +- ...myreserve-matrix-lan-oder-powergateway.mdx | 16 +- .../meters/solarwatt-myreserve.mdx | 16 +- .../meters/solax-hybrid-inverter-cloud.mdx | 20 +- .../meters/solax-hybrid-x1-x3-g3-g4.mdx | 40 +- .../meters/solax-inverter-cloud.mdx | 20 +- .../current/devices-next/meters/solinteng.mdx | 26 +- .../devices-next/meters/sonnen-comfort.mdx | 16 +- .../devices-next/meters/sonnen-eco-5.mdx | 16 +- .../devices-next/meters/sonnen-eco-6.mdx | 16 +- .../devices-next/meters/sonnen-oem-6-5.mdx | 16 +- .../meters/sonnen-sonnenbatterie.mdx | 22 +- .../current/devices-next/meters/st-ems.mdx | 26 +- .../meters/steca-coolcept-flex.mdx | 16 +- .../meters/sungrow-sg-series-inverter.mdx | 18 +- .../sungrow-sh-series-hybrid-inverter.mdx | 18 +- .../meters/sunspec-battery-model-124.mdx | 18 +- .../meters/sunspec-battery-model-802.mdx | 18 +- .../meters/sunspec-hybrid-inverter.mdx | 18 +- .../devices-next/meters/sunspec-inverter.mdx | 18 +- .../devices-next/meters/sunspec-meter.mdx | 18 +- .../meters/sunsynk-3p-hybrid-inverter.mdx | 47 +- .../meters/sunsynk-hp3-hybrid-inverter.mdx | 30 +- .../meters/sunsynk-micro-inverter.mdx | 18 +- .../sunsynk-storage-hybrid-inverter.mdx | 18 +- .../meters/sunsynk-string-inverter.mdx | 18 +- .../current/devices-next/meters/sunway.mdx | 26 +- ...ml-ir-reader-for-smartmeters-e-g-hichi.mdx | 16 +- ...tasmota-tasmota-1-phase-plus-sml-meter.mdx | 16 +- .../meters/tasmota-three-phase.mdx | 16 +- .../devices-next/meters/tesla-powerwall.mdx | 56 +- .../devices-next/meters/tibber-pulse.mdx | 24 +- .../meters/tp-link-h-series-smart-plug.mdx | 16 +- .../tp-link-tapo-p-series-smart-plug.mdx | 16 +- .../meters/tq-energy-manager-em2xx-em3xx.mdx | 16 +- .../meters/tq-energy-manager-em420.mdx | 20 +- .../devices-next/meters/varta-element.mdx | 16 +- .../devices-next/meters/varta-pulse-neo.mdx | 16 +- .../devices-next/meters/varta-pulse.mdx | 16 +- .../devices-next/meters/victron-em24.mdx | 18 +- .../devices-next/meters/victron-em24_e1.mdx | 18 +- .../meters/victron-em530-em540.mdx | 18 +- .../devices-next/meters/victron-energy.mdx | 33 +- .../devices-next/meters/victron-et340.mdx | 18 +- ...volkszahler-http-api-import-and-export.mdx | 28 +- .../meters/volkszahler-http-api.mdx | 24 +- .../meters/volkszahler-websocket-api.mdx | 20 +- .../current/devices-next/meters/vzlogger.mdx | 58 +- .../devices-next/meters/wago-879-30xx.mdx | 18 +- .../current/devices-next/meters/wattsonic.mdx | 26 +- .../meters/weidmuller-em110-rtu-2p.mdx | 18 +- .../meters/weidmuller-em111-rtu-2p.mdx | 18 +- .../meters/weidmuller-em120-rtu-2p.mdx | 18 +- .../meters/weidmuller-em122-rtu-2p.mdx | 18 +- .../meters/youless-energy-monitor.mdx | 16 +- .../meters/zcs-azzurro-hybrid-inverter.mdx | 18 +- .../meters/zcs-azzurro-inverter.mdx | 18 +- .../meters/zendure-hyper-2000.mdx | 40 +- ...uidwijk-slimmelezer-plus-in-luxembourg.mdx | 16 +- .../meters/zuidwijk-slimmelezer-plus-v2.mdx | 16 +- .../meters/zuidwijk-slimmelezer-plus.mdx | 16 +- .../devices-next/tariffs/amber-electric.mdx | 34 +- .../current/devices-next/tariffs/awattar.mdx | 22 +- .../electricity-maps-commercial-api.mdx | 24 +- .../tariffs/electricity-maps-free-api.mdx | 24 +- .../devices-next/tariffs/energinet.mdx | 22 +- .../current/devices-next/tariffs/enever.mdx | 32 +- .../current/devices-next/tariffs/entso-e.mdx | 28 +- .../devices-next/tariffs/forecast-solar.mdx | 24 +- .../devices-next/tariffs/fraunhofer-ise.mdx | 22 +- .../tariffs/green-grid-compass.mdx | 20 +- .../tariffs/groupe-e-vario-plus.mdx | 16 +- .../devices-next/tariffs/grunstromindex.mdx | 24 +- .../tariffs/national-grid-eso.mdx | 24 +- .../tariffs/nordpool-spot-prices.mdx | 28 +- .../tariffs/octopus-energy-api.mdx | 24 +- .../tariffs/octopus-energy-product-code.mdx | 28 +- .../devices-next/tariffs/open-meteo.mdx | 20 +- .../current/devices-next/tariffs/ostrom.mdx | 28 +- .../devices-next/tariffs/pun-orario.mdx | 16 +- .../tariffs/smartenergy-smartcontrol.mdx | 16 +- .../current/devices-next/tariffs/solcast.mdx | 36 +- .../devices-next/tariffs/spotty-energie.mdx | 28 +- .../current/devices-next/tariffs/tibber.mdx | 28 +- .../tariffs/victron-vrm-solar-forecast.mdx | 22 +- .../current/devices-next/vehicles/aiways.mdx | 20 +- .../current/devices-next/vehicles/audi.mdx | 20 +- .../current/devices-next/vehicles/bmw.mdx | 26 +- .../current/devices-next/vehicles/citroen.mdx | 32 +- .../current/devices-next/vehicles/dacia.mdx | 20 +- .../current/devices-next/vehicles/ds.mdx | 32 +- .../devices-next/vehicles/evnotify.mdx | 32 +- .../current/devices-next/vehicles/fiat.mdx | 26 +- .../current/devices-next/vehicles/ford.mdx | 32 +- .../vehicles/generic-vehicle-without-api.mdx | 20 +- .../vehicles/hyundai-bluelink.mdx | 20 +- .../devices-next/vehicles/iobroker-bmw.mdx | 26 +- .../devices-next/vehicles/iso15118.mdx | 20 +- .../current/devices-next/vehicles/jeep.mdx | 26 +- .../devices-next/vehicles/kia-bluelink.mdx | 20 +- .../devices-next/vehicles/mercedes-benz.mdx | 38 +- .../current/devices-next/vehicles/mg.mdx | 20 +- .../current/devices-next/vehicles/mg2mqtt.mdx | 20 +- .../current/devices-next/vehicles/mini.mdx | 26 +- .../current/devices-next/vehicles/mz2mqtt.mdx | 20 +- .../devices-next/vehicles/nissan-ariya.mdx | 20 +- .../vehicles/nissan-leaf-pre-2019.mdx | 20 +- .../devices-next/vehicles/nissan-leaf.mdx | 20 +- .../devices-next/vehicles/niu-e-scooter.mdx | 16 +- .../current/devices-next/vehicles/opel.mdx | 32 +- .../open-vehicle-monitoring-system.mdx | 30 +- .../current/devices-next/vehicles/peugeot.mdx | 32 +- .../devices-next/vehicles/polestar.mdx | 20 +- .../vehicles/psa-car-controller.mdx | 30 +- .../current/devices-next/vehicles/renault.mdx | 20 +- ...nect-gen3-ateca-leon-formentor-tarraco.mdx | 20 +- ...raconnect-gen4-born-formentor-tavascan.mdx | 20 +- .../devices-next/vehicles/skoda-enyaq.mdx | 20 +- .../current/devices-next/vehicles/smart-1.mdx | 20 +- .../devices-next/vehicles/smart-eq.mdx | 38 +- .../devices-next/vehicles/tesla-ble.mdx | 26 +- .../current/devices-next/vehicles/tesla.mdx | 46 +- .../devices-next/vehicles/teslalogger.mdx | 26 +- .../devices-next/vehicles/teslamate.mdx | 20 +- .../current/devices-next/vehicles/tessie.mdx | 20 +- .../current/devices-next/vehicles/toyota.mdx | 20 +- .../current/devices-next/vehicles/tronity.mdx | 20 +- .../vehicles/volkswagen-we-connect-id.mdx | 20 +- .../current/devices-next/vehicles/volvo.mdx | 44 +- .../devices-next/vehicles/volvo2mqtt.mdx | 20 +- .../vehicles/zero-motorcycles.mdx | 20 +- .../current/devices/chargers.mdx | 770 +++++++++--------- .../current/devices/heating.mdx | 90 +- .../current/devices/meters.mdx | 696 +++++----------- .../current/devices/smartswitches.mdx | 26 +- .../current/devices/vehicles.mdx | 234 +++--- .../current/tariffs.mdx | 120 +-- package-lock.json | 8 +- package.json | 2 +- src/css/custom.css | 42 + src/generateDevicesNext.ts | 23 +- .../release/de/charger/abb-terra-ac-ocpp.yaml | 36 +- .../release/de/charger/abb-terra-ac.yaml | 2 +- .../de/charger/abl-em4-single-ocpp.yaml | 36 +- .../de/charger/abl-em4-single-sbcx.yaml | 2 +- .../release/de/charger/abl-em4-twin-ocpp.yaml | 36 +- .../release/de/charger/abl-em4-twin-sbcx.yaml | 2 +- templates/release/de/charger/abl-emh1.yaml | 2 +- .../release/de/charger/abl-emh2-ocpp.yaml | 36 +- templates/release/de/charger/abl-emh2.yaml | 2 +- .../release/de/charger/abl-emh3-ocpp.yaml | 36 +- .../release/de/charger/alfen-eve-ocpp.yaml | 36 +- templates/release/de/charger/alfen-eve.yaml | 2 +- .../release/de/charger/alpha-innotec.yaml | 16 +- .../de/charger/alphatec-ladesaule-twin.yaml | 2 +- .../de/charger/alphatec-wallbox-mini.yaml | 2 +- .../de/charger/alphatec-wallbox-power.yaml | 2 +- .../amperfied-wallbox-connect-business.yaml | 2 +- .../amperfied-wallbox-connect-home.yaml | 2 +- .../amperfied-wallbox-connect-solar.yaml | 2 +- .../amperfied-wallbox-energy-control.yaml | 2 +- .../release/de/charger/ampure-unite.yaml | 2 +- .../release/de/charger/autel-ac-compact.yaml | 36 +- .../de/charger/autel-ac-maxicharger.yaml | 36 +- .../de/charger/autoaid-business-wallbox.yaml | 36 +- .../charger/autoaid-intelligent-wallbox.yaml | 36 +- .../release/de/charger/bender-cc612.yaml | 2 +- .../release/de/charger/bender-cc613.yaml | 2 +- .../release/de/charger/bender-icc1314.yaml | 2 +- .../release/de/charger/bender-icc1324.yaml | 2 +- .../release/de/charger/bmw-i-wallbox.yaml | 2 +- .../release/de/charger/bosch-sg-ready.yaml | 4 +- .../release/de/charger/bosch-x-change.yaml | 4 +- .../charger/buderus-logamatic-hmc-20-z.yaml | 16 +- .../de/charger/buderus-logamatic-hmc-20.yaml | 16 +- .../release/de/charger/buderus-sg-ready.yaml | 4 +- .../release/de/charger/charge-amps-halo.yaml | 36 +- .../release/de/charger/compleo-ebox.yaml | 2 +- .../de/charger/cta-all-in-one-aeroplus.yaml | 16 +- templates/release/de/charger/cubos-c11e.yaml | 2 +- templates/release/de/charger/cubos-c22e.yaml | 2 +- .../de/charger/dadapower-premium-wallbox.yaml | 2 +- .../de/charger/daikin-homehub-sg-ready.yaml | 2 +- .../de/charger/delta-ac-max-basic.yaml | 2 +- .../de/charger/delta-ac-max-smart.yaml | 2 +- .../de/charger/delta-slim-charger.yaml | 2 +- .../de/charger/delta-ultra-fast-charger.yaml | 2 +- .../release/de/charger/e-on-drive-ebox.yaml | 2 +- .../release/de/charger/e-on-drive-vbox.yaml | 2 +- .../de/charger/e3-dc-easy-connect.yaml | 2 +- .../release/de/charger/easee-charge-core.yaml | 8 +- .../release/de/charger/easee-charge-lite.yaml | 8 +- .../release/de/charger/easee-charge.yaml | 8 +- templates/release/de/charger/easee-home.yaml | 8 +- .../release/de/charger/ebee-wallbox.yaml | 2 +- .../charger/ecoharmony-evse-epc-2-0-plus.yaml | 2 +- .../de/charger/edgetech-smart-evse.yaml | 2 +- templates/release/de/charger/elco.yaml | 16 +- templates/release/de/charger/elecq-biz.yaml | 36 +- templates/release/de/charger/elecq-home.yaml | 36 +- .../release/de/charger/elecq-station.yaml | 36 +- templates/release/de/charger/eledio-go.yaml | 36 +- .../de/charger/em2go-pro-power-ocpp-onc.yaml | 2 +- .../release/de/charger/enercab-smart.yaml | 36 +- .../de/charger/enplus-ac-ev-charger.yaml | 36 +- .../de/charger/ensto-chago-wallbox.yaml | 2 +- .../de/charger/entratek-power-dot-fix.yaml | 36 +- .../de/charger/entratek-power-dot-pro-2.yaml | 36 +- .../release/de/charger/esl-walli-light.yaml | 2 +- templates/release/de/charger/evbox-elvi.yaml | 36 +- templates/release/de/charger/evse-din.yaml | 2 +- .../charger/free2move-eprowallbox-move.yaml | 2 +- .../de/charger/free2move-eprowallbox.yaml | 2 +- .../free2move-esolutions-eprowallbox.yaml | 36 +- .../de/charger/fronius-wattpilot-ocpp.yaml | 36 +- templates/release/de/charger/garo-glb.yaml | 2 +- .../release/de/charger/garo-glbplus.yaml | 2 +- .../release/de/charger/garo-ls4-compact.yaml | 2 +- templates/release/de/charger/garo-ls4.yaml | 2 +- .../de/charger/go-e-charger-gemini-ocpp.yaml | 36 +- .../de/charger/go-e-charger-pro-ocpp.yaml | 36 +- .../de/charger/go-e-charger-v3-ocpp.yaml | 36 +- .../de/charger/heidelberg-energy-control.yaml | 2 +- .../release/de/charger/hesotec-ebox.yaml | 2 +- .../release/de/charger/hesotec-esat.yaml | 2 +- .../de/charger/homecharge-homecharger.yaml | 36 +- .../release/de/charger/homematic-ip.yaml | 24 +- .../de/charger/huawei-scharger-22kt-s0.yaml | 36 +- .../de/charger/huawei-scharger-7ks-s0.yaml | 36 +- templates/release/de/charger/idm.yaml | 2 +- templates/release/de/charger/innogy-ebox.yaml | 2 +- .../release/de/charger/juice-charger-me.yaml | 2 +- .../release/de/charger/junkers-sg-ready.yaml | 4 +- .../release/de/charger/kathrein-kwb-ac20.yaml | 2 +- .../release/de/charger/kathrein-kwb-ac35.yaml | 2 +- .../de/charger/kathrein-kwb-ac40-e.yaml | 2 +- .../release/de/charger/kathrein-kwb-ac40.yaml | 2 +- .../de/charger/kathrein-kwb-ac60-e.yaml | 2 +- .../release/de/charger/kathrein-kwb-ac60.yaml | 2 +- .../de/charger/keba-kecontact-p20.yaml | 2 +- .../charger/keba-kecontact-p30-c-series.yaml | 2 +- .../charger/keba-kecontact-p30-x-series.yaml | 2 +- .../de/charger/keba-kecontact-p40-pro.yaml | 2 +- .../de/charger/keba-kecontact-p40.yaml | 2 +- .../de/charger/kermi-x-center-pro.yaml | 4 +- .../release/de/charger/kostal-enector.yaml | 2 +- templates/release/de/charger/kse-wbx16.yaml | 2 +- .../release/de/charger/ladefoxx-evload.yaml | 2 +- .../de/charger/ladefoxx-mikro-2-0.yaml | 2 +- .../de/charger/lambda-eu-l-series.yaml | 4 +- .../de/charger/lrt-home-essentialplus.yaml | 2 +- .../charger/mennekes-amedio-professional.yaml | 2 +- .../mennekes-amtron-4business-700.yaml | 2 +- .../de/charger/mennekes-amtron-4you-300.yaml | 2 +- .../de/charger/mennekes-amtron-4you-500.yaml | 2 +- .../mennekes-amtron-chargecontrol.yaml | 2 +- .../charger/mennekes-amtron-compact-2-0s.yaml | 2 +- .../de/charger/mennekes-amtron-premium.yaml | 2 +- .../charger/mennekes-amtron-professional.yaml | 2 +- .../de/charger/mennekes-amtron-xtra.yaml | 2 +- .../mennekes-emobility-gateway-acu.yaml | 36 +- .../de/charger/mennekes-smart-acu.yaml | 36 +- .../de/charger/mennekes-smart-t-acu.yaml | 36 +- .../release/de/charger/my-pv-ac-elwa-2.yaml | 2 +- .../release/de/charger/my-pv-ac-thor-9s.yaml | 6 +- .../release/de/charger/my-pv-ac-thor.yaml | 6 +- .../release/de/charger/nibe-ap-aw10.yaml | 16 +- .../release/de/charger/novelan-wpr-net.yaml | 16 +- .../release/de/charger/nrgkick-connect.yaml | 4 +- .../release/de/charger/nrgkick-gen2.yaml | 8 +- .../de/charger/obo-bettermann-ion.yaml | 2 +- .../ocpp-1-6j-compatible-smart-charging.yaml | 36 +- .../de/charger/openwb-software-2-x.yaml | 2 +- .../de/charger/optec-mobility-one.yaml | 2 +- .../release/de/charger/orbis-viaris.yaml | 36 +- .../release/de/charger/peblar-business.yaml | 2 +- .../release/de/charger/peblar-home-plus.yaml | 2 +- templates/release/de/charger/peblar-home.yaml | 2 +- .../de/charger/phoenix-contact-charx.yaml | 2 +- .../charger/phoenix-contact-em-cp-pp-eth.yaml | 2 +- ...x-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml | 2 +- ...enix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml | 2 +- ...ix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml | 2 +- ...oenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml | 2 +- .../de/charger/phoenix-contact-ev-ser.yaml | 2 +- templates/release/de/charger/plugchoice.yaml | 24 +- .../release/de/charger/pracht-alpha-xt.yaml | 2 +- .../release/de/charger/pracht-mono-xt.yaml | 2 +- templates/release/de/charger/pracht-pni.yaml | 2 +- .../release/de/charger/pracht-xtplus.yaml | 2 +- .../de/charger/pulsares-simplebox.yaml | 2 +- .../de/charger/qcells-q-home-edrive-a.yaml | 2 +- .../release/de/charger/roth-thermoaura.yaml | 16 +- .../release/de/charger/roth-thermoterra.yaml | 16 +- .../de/charger/schneider-evlink-pro.yaml | 2 +- .../de/charger/schrack-i-charge-cion.yaml | 2 +- .../de/charger/senec-wallbox-pro-s.yaml | 2 +- .../release/de/charger/senec-wallbox-pro.yaml | 2 +- templates/release/de/charger/shelly-1.yaml | 6 +- .../release/de/charger/shelly-plug-s.yaml | 6 +- .../release/de/charger/shelly-plus-1.yaml | 6 +- .../release/de/charger/shelly-pro-1.yaml | 6 +- .../de/charger/siemens-versicharge-gen3.yaml | 2 +- .../de/charger/smartfox-pro-charger.yaml | 2 +- .../de/charger/solaredge-home-ev-charger.yaml | 2 +- .../release/de/charger/solax-x3-evc.yaml | 2 +- .../charger/spelsberg-wallbox-smart-pro.yaml | 2 +- .../de/charger/stark-in-strom-easy.yaml | 2 +- .../stiebel-eltron-lwa-lwz-sg-ready.yaml | 2 +- .../charger/stiebel-eltron-wpm-sg-ready.yaml | 2 +- .../release/de/charger/sungrow-ac011e-01.yaml | 2 +- .../release/de/charger/sungrow-ac011e.yaml | 36 +- .../release/de/charger/sungrow-ac22e-01.yaml | 2 +- .../de/charger/tecalor-thz-sg-ready.yaml | 2 +- .../de/charger/technisat-technivolt.yaml | 2 +- templates/release/de/charger/tessie.yaml | 6 +- .../de/charger/tigo-go-ev-charger.yaml | 2 +- .../charger/tinkerforge-warp-charger-pro.yaml | 8 +- .../tinkerforge-warp-charger-smart.yaml | 8 +- .../release/de/charger/ubitricity-heinz.yaml | 2 +- .../charger/vaillant-sensonet-sg-ready.yaml | 16 +- .../de/charger/vestel-connect-plus.yaml | 2 +- .../de/charger/vestel-evc04-home-smart.yaml | 2 +- .../victron-ev-charging-station-via-gx.yaml | 2 +- .../charger/victron-ev-charging-station.yaml | 2 +- .../viridian-ev-evse-epc-2-0-plus.yaml | 2 +- .../release/de/charger/volt-time-one.yaml | 8 +- .../de/charger/volt-time-source-2.yaml | 8 +- .../de/charger/volt-time-source-2s.yaml | 8 +- .../release/de/charger/volt-time-source.yaml | 8 +- .../release/de/charger/wallbe-eco-2-0-s.yaml | 2 +- templates/release/de/charger/wallbe-eco.yaml | 2 +- templates/release/de/charger/wallbe-pro.yaml | 2 +- .../charger/wallbox-commander-2-fw-5-x.yaml | 36 +- .../de/charger/wallbox-commander-2.yaml | 36 +- .../de/charger/wallbox-copper-sb-fw-5-x.yaml | 36 +- .../release/de/charger/wallbox-copper-sb.yaml | 36 +- .../de/charger/wallbox-pulsar-max-fw-5-x.yaml | 36 +- .../de/charger/wallbox-pulsar-max.yaml | 36 +- .../charger/wallbox-pulsar-plus-fw-5-x.yaml | 36 +- .../de/charger/wallbox-pulsar-plus.yaml | 36 +- .../charger/walther-werke-basic-evo-pro.yaml | 2 +- .../release/de/charger/webasto-live.yaml | 2 +- .../release/de/charger/webasto-unite.yaml | 2 +- templates/release/de/charger/wolf-bwl.yaml | 16 +- templates/release/de/charger/wolf-bws.yaml | 16 +- templates/release/de/charger/zaptec-go-2.yaml | 4 +- .../release/de/charger/zaptec-go-ocpp.yaml | 36 +- templates/release/de/charger/zaptec-go.yaml | 4 +- templates/release/de/charger/zaptec-pro.yaml | 4 +- .../de/charger/zewotherm-eu-l-series.yaml | 4 +- .../de/charger/zj-beny-bcp-ev-charger.yaml | 36 +- templates/release/de/meter/a-tronix.yaml | 10 +- templates/release/de/meter/abb-a43.yaml | 2 +- templates/release/de/meter/abb-a44.yaml | 2 +- templates/release/de/meter/abb-b23.yaml | 2 +- templates/release/de/meter/abb-b24.yaml | 2 +- templates/release/de/meter/acrel-adw300.yaml | 2 +- .../release/de/meter/ads-tec-storaxe.yaml | 2 +- .../de/meter/alpha-ess-storion-smile.yaml | 6 +- .../de/meter/ampere-ampere-storagepro.yaml | 6 +- .../de/meter/anker-micro-inverter.yaml | 2 +- .../de/meter/axitec-axihycon-12-15h.yaml | 2 +- .../meter/bernecker-engineering-mpm3pm.yaml | 2 +- templates/release/de/meter/bgetech-ds100.yaml | 2 +- templates/release/de/meter/bgetech-ws100.yaml | 2 +- .../de/meter/bosswerk-micro-inverter.yaml | 2 +- .../de/meter/carlo-gavazzi-em110-111-112.yaml | 2 +- .../release/de/meter/carlo-gavazzi-em24.yaml | 2 +- .../de/meter/carlo-gavazzi-em24_e1.yaml | 2 +- .../de/meter/carlo-gavazzi-em330-em340.yaml | 2 +- .../de/meter/carlo-gavazzi-em530-em540.yaml | 2 +- .../release/de/meter/carlo-gavazzi-et112.yaml | 2 +- .../de/meter/carlo-gavazzi-et330-et340.yaml | 2 +- .../de/meter/cfos-powerbrain-meter.yaml | 2 +- .../de/meter/deye-3p-hybrid-inverter.yaml | 6 +- .../de/meter/deye-hp3-hybrid-inverter.yaml | 14 +- .../release/de/meter/deye-micro-inverter.yaml | 2 +- .../meter/deye-storage-hybrid-inverter.yaml | 2 +- .../de/meter/deye-string-inverter.yaml | 2 +- templates/release/de/meter/discovergy.yaml | 6 +- templates/release/de/meter/dzg-dvh4013.yaml | 2 +- templates/release/de/meter/e3-dc.yaml | 14 +- .../de/meter/eastron-sdm120-modbus.yaml | 2 +- .../release/de/meter/eastron-sdm220-230.yaml | 2 +- .../de/meter/eastron-sdm630-modbus.yaml | 2 +- .../release/de/meter/eastron-sdm72d-m.yaml | 2 +- .../release/de/meter/eastron-sdm72dm-v2.yaml | 2 +- .../release/de/meter/enphase-iq-envoy.yaml | 14 +- templates/release/de/meter/fenecon.yaml | 10 +- .../foxess-h1-series-hybrid-inverter.yaml | 2 +- .../foxess-h3-series-hybrid-inverter.yaml | 6 +- ...oxess-h3-smart-series-hybrid-inverter.yaml | 6 +- .../de/meter/fronius-primo-gen24-plus.yaml | 4 +- .../fronius-smartmeter-via-inverter.yaml | 2 +- .../de/meter/fronius-solar-api-v1.yaml | 10 +- .../de/meter/fronius-symo-gen24-plus.yaml | 4 +- ...long-solis-hybrid-inverter-rhi-series.yaml | 2 +- ...inlong-solis-hybrid-inverter-s-series.yaml | 2 +- .../de/meter/ginlong-solis-inverter.yaml | 2 +- .../goodwe-et-eh-bh-bt-hybrid-inverter.yaml | 16 +- .../de/meter/goodwe-sdt-dt-inverter.yaml | 2 +- .../de/meter/growatt-hybrid-inverter.yaml | 2 +- .../meter/growatt-tl-x-h-hybrid-inverter.yaml | 2 +- templates/release/de/meter/homematic-ip.yaml | 24 +- ...oymiles-hm-and-hms-series-via-ahoydtu.yaml | 6 +- templates/release/de/meter/huawei-emma.yaml | 2 +- .../release/de/meter/huawei-smartlogger.yaml | 10 +- .../de/meter/huawei-sun2000-sdongle.yaml | 2 +- .../release/de/meter/huawei-sun2000.yaml | 10 +- .../release/de/meter/inepro-pro380-mod.yaml | 2 +- .../release/de/meter/janitza-b-series.yaml | 2 +- .../release/de/meter/janitza-umg-series.yaml | 2 +- .../release/de/meter/keba-kecontact-e10.yaml | 2 +- .../de/meter/kostal-energy-meter-c-kem-c.yaml | 2 +- .../de/meter/kostal-energy-meter-p-kem-p.yaml | 2 +- ...cl-grid-charging-of-the-house-battery.yaml | 8 +- .../de/meter/kostal-plenticore-hybrid.yaml | 10 +- ...ostal-smart-energy-meter-via-inverter.yaml | 2 +- .../de/meter/kostal-smart-energy-meter.yaml | 2 +- .../release/de/meter/lg-ess-home-15.yaml | 14 +- .../release/de/meter/lg-ess-home-8-10.yaml | 14 +- .../de/meter/m-tec-energy-butler-gen2.yaml | 2 +- .../de/meter/m-tec-energy-butler-gen3.yaml | 2 +- .../meter/marstek-venus-battery-storage.yaml | 22 +- .../release/de/meter/my-pv-wifi-meter.yaml | 2 +- templates/release/de/meter/openems.yaml | 10 +- .../release/de/meter/orno-or-we-516.yaml | 2 +- .../release/de/meter/orno-or-we-517.yaml | 2 +- templates/release/de/meter/plexlog.yaml | 2 +- templates/release/de/meter/powerdog.yaml | 2 +- .../release/de/meter/powerfox-poweropti.yaml | 6 +- .../de/meter/qcells-q-home-ess-hyb-g3.yaml | 26 +- templates/release/de/meter/rct-power.yaml | 6 - .../meter/saia-burgess-controls-sbc-ale3.yaml | 2 +- .../meter/saia-burgess-controls-sbc-awd3.yaml | 2 +- .../saj-h1-series-hybrid-solar-inverter.yaml | 2 +- .../saj-h2-series-hybrid-solar-inverter.yaml | 6 +- .../meter/saj-r5-series-solar-inverter.yaml | 2 +- .../release/de/meter/sax-homespeicher.yaml | 2 +- .../schneider-electric-iem3xxx-modbus.yaml | 2 +- templates/release/de/meter/senec-home.yaml | 14 +- .../senergy-se-4-5-6ktl-s1-g2-inverter.yaml | 2 +- .../release/de/meter/shelly-1pm-mini.yaml | 8 +- templates/release/de/meter/shelly-1pm.yaml | 8 +- templates/release/de/meter/shelly-em.yaml | 8 +- templates/release/de/meter/shelly-plug-s.yaml | 8 +- .../release/de/meter/shelly-pm-mini.yaml | 8 +- .../release/de/meter/shelly-pro-1pm.yaml | 8 +- .../meter/shelly-pro-3em-monophase-mode.yaml | 8 +- templates/release/de/meter/shelly-pro-em.yaml | 8 +- .../release/de/meter/siemens-7kt1665.yaml | 2 +- .../siemens-junelight-smart-battery.yaml | 2 +- .../release/de/meter/siemens-pac-2200.yaml | 2 +- ...gen-hybrid-sigen-pv-max-sigenstore-ec.yaml | 14 +- .../release/de/meter/sma-data-manager.yaml | 2 +- .../sma-smart-energy-hybrid-inverter.yaml | 6 +- ...-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml | 6 +- ...-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml | 6 +- .../de/meter/sma-sunny-island-modbus.yaml | 6 +- templates/release/de/meter/sma-webbox.yaml | 2 +- .../de/meter/sma-wechselrichter-modbus.yaml | 2 +- .../de/meter/sofarsolar-hybrid-inverter.yaml | 2 +- .../de/meter/sofarsolar-hyd-3-6k-ep.yaml | 12 +- .../de/meter/sofarsolar-hyd-5-20k-3ph.yaml | 12 +- .../release/de/meter/sofarsolar-inverter.yaml | 2 +- .../de/meter/sofarsolar-sofar-5-24ktl-g3.yaml | 12 +- .../de/meter/sofarsolar-sofar-80-136ktl.yaml | 12 +- .../de/meter/solaredge-hybrid-inverter.yaml | 10 +- .../release/de/meter/solaredge-inverter.yaml | 2 +- ...rmax-max-storage-max-storage-ultimate.yaml | 10 +- .../de/meter/solarmax-solarmax-smt.yaml | 2 +- .../de/meter/solarmax-sp-series-inverter.yaml | 2 +- .../de/meter/solax-hybrid-x1-x3-g3-g4.yaml | 26 +- templates/release/de/meter/solinteng.yaml | 10 +- .../de/meter/sonnen-sonnenbatterie.yaml | 6 +- templates/release/de/meter/st-ems.yaml | 10 +- .../de/meter/sungrow-sg-series-inverter.yaml | 2 +- .../sungrow-sh-series-hybrid-inverter.yaml | 2 +- .../de/meter/sunspec-battery-model-124.yaml | 2 +- .../de/meter/sunspec-battery-model-802.yaml | 2 +- .../de/meter/sunspec-hybrid-inverter.yaml | 2 +- .../release/de/meter/sunspec-inverter.yaml | 2 +- templates/release/de/meter/sunspec-meter.yaml | 2 +- .../de/meter/sunsynk-3p-hybrid-inverter.yaml | 6 +- .../de/meter/sunsynk-hp3-hybrid-inverter.yaml | 14 +- .../de/meter/sunsynk-micro-inverter.yaml | 2 +- .../sunsynk-storage-hybrid-inverter.yaml | 2 +- .../de/meter/sunsynk-string-inverter.yaml | 2 +- templates/release/de/meter/sunway.yaml | 10 +- .../release/de/meter/tesla-powerwall.yaml | 32 +- templates/release/de/meter/tibber-pulse.yaml | 8 +- templates/release/de/meter/victron-em24.yaml | 2 +- .../release/de/meter/victron-em24_e1.yaml | 2 +- .../release/de/meter/victron-em530-em540.yaml | 2 +- .../release/de/meter/victron-energy.yaml | 12 +- templates/release/de/meter/victron-et340.yaml | 2 +- ...olkszahler-http-api-import-and-export.yaml | 16 +- .../de/meter/volkszahler-http-api.yaml | 12 +- .../de/meter/volkszahler-websocket-api.yaml | 4 +- templates/release/de/meter/vzlogger.yaml | 60 +- templates/release/de/meter/wago-879-30xx.yaml | 2 +- templates/release/de/meter/wattsonic.yaml | 10 +- .../de/meter/weidmuller-em110-rtu-2p.yaml | 2 +- .../de/meter/weidmuller-em111-rtu-2p.yaml | 2 +- .../de/meter/weidmuller-em120-rtu-2p.yaml | 2 +- .../de/meter/weidmuller-em122-rtu-2p.yaml | 2 +- .../de/meter/zcs-azzurro-hybrid-inverter.yaml | 2 +- .../de/meter/zcs-azzurro-inverter.yaml | 2 +- .../release/de/meter/zendure-hyper-2000.yaml | 30 +- .../release/de/tariff/amber-electric.yaml | 18 +- templates/release/de/tariff/awattar.yaml | 6 +- .../electricity-maps-commercial-api.yaml | 8 +- .../de/tariff/electricity-maps-free-api.yaml | 8 +- templates/release/de/tariff/energinet.yaml | 6 +- templates/release/de/tariff/enever.yaml | 16 +- templates/release/de/tariff/entso-e.yaml | 12 +- .../release/de/tariff/forecast-solar.yaml | 8 +- .../release/de/tariff/fraunhofer-ise.yaml | 8 +- .../release/de/tariff/green-grid-compass.yaml | 4 +- .../release/de/tariff/grunstromindex.yaml | 8 +- .../release/de/tariff/national-grid-eso.yaml | 8 +- .../de/tariff/nordpool-spot-prices.yaml | 12 +- .../release/de/tariff/octopus-energy-api.yaml | 14 +- .../tariff/octopus-energy-product-code.yaml | 12 +- templates/release/de/tariff/open-meteo.yaml | 4 +- templates/release/de/tariff/ostrom.yaml | 12 +- .../de/tariff/smartenergy-smartcontrol.yaml | 1 + templates/release/de/tariff/solcast.yaml | 24 +- .../release/de/tariff/spotty-energie.yaml | 12 +- templates/release/de/tariff/tibber.yaml | 12 +- .../de/tariff/victron-vrm-solar-forecast.yaml | 4 +- templates/release/de/vehicle/aiways.yaml | 6 +- templates/release/de/vehicle/audi.yaml | 6 +- templates/release/de/vehicle/bmw.yaml | 12 +- templates/release/de/vehicle/citroen.yaml | 18 +- templates/release/de/vehicle/dacia.yaml | 6 +- templates/release/de/vehicle/ds.yaml | 18 +- templates/release/de/vehicle/evnotify.yaml | 18 +- templates/release/de/vehicle/fiat.yaml | 12 +- templates/release/de/vehicle/ford.yaml | 18 +- .../vehicle/generic-vehicle-without-api.yaml | 6 +- .../release/de/vehicle/hyundai-bluelink.yaml | 6 +- .../release/de/vehicle/iobroker-bmw.yaml | 14 +- templates/release/de/vehicle/iso15118.yaml | 6 +- templates/release/de/vehicle/jeep.yaml | 12 +- .../release/de/vehicle/kia-bluelink.yaml | 6 +- .../release/de/vehicle/mercedes-benz.yaml | 24 +- templates/release/de/vehicle/mg.yaml | 6 +- templates/release/de/vehicle/mg2mqtt.yaml | 6 +- templates/release/de/vehicle/mini.yaml | 12 +- templates/release/de/vehicle/mz2mqtt.yaml | 6 +- .../release/de/vehicle/nissan-ariya.yaml | 6 +- .../de/vehicle/nissan-leaf-pre-2019.yaml | 6 +- templates/release/de/vehicle/nissan-leaf.yaml | 6 +- templates/release/de/vehicle/opel.yaml | 18 +- .../open-vehicle-monitoring-system.yaml | 16 +- templates/release/de/vehicle/peugeot.yaml | 18 +- templates/release/de/vehicle/polestar.yaml | 6 +- .../de/vehicle/psa-car-controller.yaml | 18 +- templates/release/de/vehicle/renault.yaml | 6 +- ...ect-gen3-ateca-leon-formentor-tarraco.yaml | 6 +- ...aconnect-gen4-born-formentor-tavascan.yaml | 6 +- templates/release/de/vehicle/skoda-enyaq.yaml | 6 +- templates/release/de/vehicle/smart-1.yaml | 6 +- templates/release/de/vehicle/smart-eq.yaml | 24 +- templates/release/de/vehicle/tesla-ble.yaml | 12 +- templates/release/de/vehicle/tesla.yaml | 34 +- templates/release/de/vehicle/teslalogger.yaml | 12 +- templates/release/de/vehicle/teslamate.yaml | 6 +- templates/release/de/vehicle/tessie.yaml | 6 +- templates/release/de/vehicle/toyota.yaml | 6 +- templates/release/de/vehicle/tronity.yaml | 6 +- .../de/vehicle/volkswagen-we-connect-id.yaml | 6 +- templates/release/de/vehicle/volvo.yaml | 38 +- templates/release/de/vehicle/volvo2mqtt.yaml | 6 +- .../release/de/vehicle/zero-motorcycles.yaml | 6 +- .../release/en/charger/abb-terra-ac-ocpp.yaml | 36 +- .../release/en/charger/abb-terra-ac.yaml | 2 +- .../en/charger/abl-em4-single-ocpp.yaml | 36 +- .../en/charger/abl-em4-single-sbcx.yaml | 2 +- .../release/en/charger/abl-em4-twin-ocpp.yaml | 36 +- .../release/en/charger/abl-em4-twin-sbcx.yaml | 2 +- templates/release/en/charger/abl-emh1.yaml | 2 +- .../release/en/charger/abl-emh2-ocpp.yaml | 36 +- templates/release/en/charger/abl-emh2.yaml | 2 +- .../release/en/charger/abl-emh3-ocpp.yaml | 36 +- .../release/en/charger/alfen-eve-ocpp.yaml | 36 +- templates/release/en/charger/alfen-eve.yaml | 2 +- .../release/en/charger/alpha-innotec.yaml | 14 +- .../en/charger/alphatec-ladesaule-twin.yaml | 2 +- .../en/charger/alphatec-wallbox-mini.yaml | 2 +- .../en/charger/alphatec-wallbox-power.yaml | 2 +- .../amperfied-wallbox-connect-business.yaml | 2 +- .../amperfied-wallbox-connect-home.yaml | 2 +- .../amperfied-wallbox-connect-solar.yaml | 2 +- .../amperfied-wallbox-energy-control.yaml | 2 +- .../release/en/charger/ampure-unite.yaml | 2 +- .../release/en/charger/autel-ac-compact.yaml | 36 +- .../en/charger/autel-ac-maxicharger.yaml | 36 +- .../en/charger/autoaid-business-wallbox.yaml | 36 +- .../charger/autoaid-intelligent-wallbox.yaml | 36 +- .../release/en/charger/bender-cc612.yaml | 2 +- .../release/en/charger/bender-cc613.yaml | 2 +- .../release/en/charger/bender-icc1314.yaml | 2 +- .../release/en/charger/bender-icc1324.yaml | 2 +- .../release/en/charger/bmw-i-wallbox.yaml | 2 +- .../release/en/charger/bosch-sg-ready.yaml | 4 +- .../release/en/charger/bosch-x-change.yaml | 4 +- .../charger/buderus-logamatic-hmc-20-z.yaml | 14 +- .../en/charger/buderus-logamatic-hmc-20.yaml | 14 +- .../release/en/charger/buderus-sg-ready.yaml | 4 +- .../release/en/charger/charge-amps-halo.yaml | 36 +- .../release/en/charger/compleo-ebox.yaml | 2 +- .../en/charger/cta-all-in-one-aeroplus.yaml | 14 +- templates/release/en/charger/cubos-c11e.yaml | 2 +- templates/release/en/charger/cubos-c22e.yaml | 2 +- .../en/charger/dadapower-premium-wallbox.yaml | 2 +- .../en/charger/daikin-homehub-sg-ready.yaml | 2 +- .../en/charger/delta-ac-max-basic.yaml | 2 +- .../en/charger/delta-ac-max-smart.yaml | 2 +- .../en/charger/delta-slim-charger.yaml | 2 +- .../en/charger/delta-ultra-fast-charger.yaml | 2 +- .../release/en/charger/e-on-drive-ebox.yaml | 2 +- .../release/en/charger/e-on-drive-vbox.yaml | 2 +- .../en/charger/e3-dc-easy-connect.yaml | 2 +- .../release/en/charger/easee-charge-core.yaml | 8 +- .../release/en/charger/easee-charge-lite.yaml | 8 +- .../release/en/charger/easee-charge.yaml | 8 +- templates/release/en/charger/easee-home.yaml | 8 +- .../release/en/charger/ebee-wallbox.yaml | 2 +- .../charger/ecoharmony-evse-epc-2-0-plus.yaml | 2 +- .../en/charger/edgetech-smart-evse.yaml | 2 +- templates/release/en/charger/elco.yaml | 14 +- templates/release/en/charger/elecq-biz.yaml | 36 +- templates/release/en/charger/elecq-home.yaml | 36 +- .../release/en/charger/elecq-station.yaml | 36 +- templates/release/en/charger/eledio-go.yaml | 36 +- .../en/charger/em2go-pro-power-ocpp-onc.yaml | 2 +- .../release/en/charger/enercab-smart.yaml | 36 +- .../en/charger/enplus-ac-ev-charger.yaml | 36 +- .../en/charger/ensto-chago-wallbox.yaml | 2 +- .../en/charger/entratek-power-dot-fix.yaml | 36 +- .../en/charger/entratek-power-dot-pro-2.yaml | 36 +- .../release/en/charger/esl-walli-light.yaml | 2 +- templates/release/en/charger/evbox-elvi.yaml | 36 +- templates/release/en/charger/evse-din.yaml | 2 +- .../charger/free2move-eprowallbox-move.yaml | 2 +- .../en/charger/free2move-eprowallbox.yaml | 2 +- .../free2move-esolutions-eprowallbox.yaml | 36 +- .../en/charger/fronius-wattpilot-ocpp.yaml | 36 +- templates/release/en/charger/garo-glb.yaml | 2 +- .../release/en/charger/garo-glbplus.yaml | 2 +- .../release/en/charger/garo-ls4-compact.yaml | 2 +- templates/release/en/charger/garo-ls4.yaml | 2 +- .../en/charger/go-e-charger-gemini-ocpp.yaml | 36 +- .../en/charger/go-e-charger-pro-ocpp.yaml | 36 +- .../en/charger/go-e-charger-v3-ocpp.yaml | 36 +- .../en/charger/heidelberg-energy-control.yaml | 2 +- .../release/en/charger/hesotec-ebox.yaml | 2 +- .../release/en/charger/hesotec-esat.yaml | 2 +- .../en/charger/homecharge-homecharger.yaml | 36 +- .../release/en/charger/homematic-ip.yaml | 24 +- .../en/charger/huawei-scharger-22kt-s0.yaml | 36 +- .../en/charger/huawei-scharger-7ks-s0.yaml | 36 +- templates/release/en/charger/idm.yaml | 2 +- templates/release/en/charger/innogy-ebox.yaml | 2 +- .../release/en/charger/juice-charger-me.yaml | 2 +- .../release/en/charger/junkers-sg-ready.yaml | 4 +- .../release/en/charger/kathrein-kwb-ac20.yaml | 2 +- .../release/en/charger/kathrein-kwb-ac35.yaml | 2 +- .../en/charger/kathrein-kwb-ac40-e.yaml | 2 +- .../release/en/charger/kathrein-kwb-ac40.yaml | 2 +- .../en/charger/kathrein-kwb-ac60-e.yaml | 2 +- .../release/en/charger/kathrein-kwb-ac60.yaml | 2 +- .../en/charger/keba-kecontact-p20.yaml | 2 +- .../charger/keba-kecontact-p30-c-series.yaml | 2 +- .../charger/keba-kecontact-p30-x-series.yaml | 2 +- .../en/charger/keba-kecontact-p40-pro.yaml | 2 +- .../en/charger/keba-kecontact-p40.yaml | 2 +- .../en/charger/kermi-x-center-pro.yaml | 4 +- .../release/en/charger/kostal-enector.yaml | 2 +- templates/release/en/charger/kse-wbx16.yaml | 2 +- .../release/en/charger/ladefoxx-evload.yaml | 2 +- .../en/charger/ladefoxx-mikro-2-0.yaml | 2 +- .../en/charger/lambda-eu-l-series.yaml | 4 +- .../en/charger/lrt-home-essentialplus.yaml | 2 +- .../charger/mennekes-amedio-professional.yaml | 2 +- .../mennekes-amtron-4business-700.yaml | 2 +- .../en/charger/mennekes-amtron-4you-300.yaml | 2 +- .../en/charger/mennekes-amtron-4you-500.yaml | 2 +- .../mennekes-amtron-chargecontrol.yaml | 2 +- .../charger/mennekes-amtron-compact-2-0s.yaml | 2 +- .../en/charger/mennekes-amtron-premium.yaml | 2 +- .../charger/mennekes-amtron-professional.yaml | 2 +- .../en/charger/mennekes-amtron-xtra.yaml | 2 +- .../mennekes-emobility-gateway-acu.yaml | 36 +- .../en/charger/mennekes-smart-acu.yaml | 36 +- .../en/charger/mennekes-smart-t-acu.yaml | 36 +- .../release/en/charger/my-pv-ac-elwa-2.yaml | 2 +- .../release/en/charger/my-pv-ac-thor-9s.yaml | 6 +- .../release/en/charger/my-pv-ac-thor.yaml | 6 +- .../release/en/charger/nibe-ap-aw10.yaml | 14 +- .../release/en/charger/novelan-wpr-net.yaml | 14 +- .../release/en/charger/nrgkick-connect.yaml | 4 +- .../release/en/charger/nrgkick-gen2.yaml | 8 +- .../en/charger/obo-bettermann-ion.yaml | 2 +- .../ocpp-1-6j-compatible-smart-charging.yaml | 36 +- .../en/charger/openwb-software-2-x.yaml | 2 +- .../en/charger/optec-mobility-one.yaml | 2 +- .../release/en/charger/orbis-viaris.yaml | 36 +- .../release/en/charger/peblar-business.yaml | 2 +- .../release/en/charger/peblar-home-plus.yaml | 2 +- templates/release/en/charger/peblar-home.yaml | 2 +- .../en/charger/phoenix-contact-charx.yaml | 2 +- .../charger/phoenix-contact-em-cp-pp-eth.yaml | 2 +- ...x-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml | 2 +- ...enix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml | 2 +- ...ix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml | 2 +- ...oenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml | 2 +- .../en/charger/phoenix-contact-ev-ser.yaml | 2 +- templates/release/en/charger/plugchoice.yaml | 24 +- .../release/en/charger/pracht-alpha-xt.yaml | 2 +- .../release/en/charger/pracht-mono-xt.yaml | 2 +- templates/release/en/charger/pracht-pni.yaml | 2 +- .../release/en/charger/pracht-xtplus.yaml | 2 +- .../en/charger/pulsares-simplebox.yaml | 2 +- .../en/charger/qcells-q-home-edrive-a.yaml | 2 +- .../release/en/charger/roth-thermoaura.yaml | 14 +- .../release/en/charger/roth-thermoterra.yaml | 14 +- .../en/charger/schneider-evlink-pro.yaml | 2 +- .../en/charger/schrack-i-charge-cion.yaml | 2 +- .../en/charger/senec-wallbox-pro-s.yaml | 2 +- .../release/en/charger/senec-wallbox-pro.yaml | 2 +- templates/release/en/charger/shelly-1.yaml | 6 +- .../release/en/charger/shelly-plug-s.yaml | 6 +- .../release/en/charger/shelly-plus-1.yaml | 6 +- .../release/en/charger/shelly-pro-1.yaml | 6 +- .../en/charger/siemens-versicharge-gen3.yaml | 2 +- .../en/charger/smartfox-pro-charger.yaml | 2 +- .../en/charger/solaredge-home-ev-charger.yaml | 2 +- .../release/en/charger/solax-x3-evc.yaml | 2 +- .../charger/spelsberg-wallbox-smart-pro.yaml | 2 +- .../en/charger/stark-in-strom-easy.yaml | 2 +- .../stiebel-eltron-lwa-lwz-sg-ready.yaml | 2 +- .../charger/stiebel-eltron-wpm-sg-ready.yaml | 2 +- .../release/en/charger/sungrow-ac011e-01.yaml | 2 +- .../release/en/charger/sungrow-ac011e.yaml | 36 +- .../release/en/charger/sungrow-ac22e-01.yaml | 2 +- .../en/charger/tecalor-thz-sg-ready.yaml | 2 +- .../en/charger/technisat-technivolt.yaml | 2 +- templates/release/en/charger/tessie.yaml | 6 +- .../en/charger/tigo-go-ev-charger.yaml | 2 +- .../charger/tinkerforge-warp-charger-pro.yaml | 8 +- .../tinkerforge-warp-charger-smart.yaml | 8 +- .../release/en/charger/ubitricity-heinz.yaml | 2 +- .../charger/vaillant-sensonet-sg-ready.yaml | 16 +- .../en/charger/vestel-connect-plus.yaml | 2 +- .../en/charger/vestel-evc04-home-smart.yaml | 2 +- .../victron-ev-charging-station-via-gx.yaml | 2 +- .../charger/victron-ev-charging-station.yaml | 2 +- .../viridian-ev-evse-epc-2-0-plus.yaml | 2 +- .../release/en/charger/volt-time-one.yaml | 8 +- .../en/charger/volt-time-source-2.yaml | 8 +- .../en/charger/volt-time-source-2s.yaml | 8 +- .../release/en/charger/volt-time-source.yaml | 8 +- .../release/en/charger/wallbe-eco-2-0-s.yaml | 2 +- templates/release/en/charger/wallbe-eco.yaml | 2 +- templates/release/en/charger/wallbe-pro.yaml | 2 +- .../charger/wallbox-commander-2-fw-5-x.yaml | 36 +- .../en/charger/wallbox-commander-2.yaml | 36 +- .../en/charger/wallbox-copper-sb-fw-5-x.yaml | 36 +- .../release/en/charger/wallbox-copper-sb.yaml | 36 +- .../en/charger/wallbox-pulsar-max-fw-5-x.yaml | 36 +- .../en/charger/wallbox-pulsar-max.yaml | 36 +- .../charger/wallbox-pulsar-plus-fw-5-x.yaml | 36 +- .../en/charger/wallbox-pulsar-plus.yaml | 36 +- .../charger/walther-werke-basic-evo-pro.yaml | 2 +- .../release/en/charger/webasto-live.yaml | 2 +- .../release/en/charger/webasto-unite.yaml | 2 +- templates/release/en/charger/wolf-bwl.yaml | 14 +- templates/release/en/charger/wolf-bws.yaml | 14 +- templates/release/en/charger/zaptec-go-2.yaml | 4 +- .../release/en/charger/zaptec-go-ocpp.yaml | 36 +- templates/release/en/charger/zaptec-go.yaml | 4 +- templates/release/en/charger/zaptec-pro.yaml | 4 +- .../en/charger/zewotherm-eu-l-series.yaml | 4 +- .../en/charger/zj-beny-bcp-ev-charger.yaml | 36 +- templates/release/en/meter/a-tronix.yaml | 10 +- templates/release/en/meter/abb-a43.yaml | 2 +- templates/release/en/meter/abb-a44.yaml | 2 +- templates/release/en/meter/abb-b23.yaml | 2 +- templates/release/en/meter/abb-b24.yaml | 2 +- templates/release/en/meter/acrel-adw300.yaml | 2 +- .../release/en/meter/ads-tec-storaxe.yaml | 2 +- .../en/meter/alpha-ess-storion-smile.yaml | 6 +- .../en/meter/ampere-ampere-storagepro.yaml | 6 +- .../en/meter/anker-micro-inverter.yaml | 2 +- .../en/meter/axitec-axihycon-12-15h.yaml | 2 +- .../meter/bernecker-engineering-mpm3pm.yaml | 2 +- templates/release/en/meter/bgetech-ds100.yaml | 2 +- templates/release/en/meter/bgetech-ws100.yaml | 2 +- .../en/meter/bosswerk-micro-inverter.yaml | 2 +- .../en/meter/carlo-gavazzi-em110-111-112.yaml | 2 +- .../release/en/meter/carlo-gavazzi-em24.yaml | 2 +- .../en/meter/carlo-gavazzi-em24_e1.yaml | 2 +- .../en/meter/carlo-gavazzi-em330-em340.yaml | 2 +- .../en/meter/carlo-gavazzi-em530-em540.yaml | 2 +- .../release/en/meter/carlo-gavazzi-et112.yaml | 2 +- .../en/meter/carlo-gavazzi-et330-et340.yaml | 2 +- .../en/meter/cfos-powerbrain-meter.yaml | 2 +- .../en/meter/deye-3p-hybrid-inverter.yaml | 6 +- .../en/meter/deye-hp3-hybrid-inverter.yaml | 14 +- .../release/en/meter/deye-micro-inverter.yaml | 2 +- .../meter/deye-storage-hybrid-inverter.yaml | 2 +- .../en/meter/deye-string-inverter.yaml | 2 +- templates/release/en/meter/discovergy.yaml | 6 +- templates/release/en/meter/dzg-dvh4013.yaml | 2 +- templates/release/en/meter/e3-dc.yaml | 14 +- .../en/meter/eastron-sdm120-modbus.yaml | 2 +- .../release/en/meter/eastron-sdm220-230.yaml | 2 +- .../en/meter/eastron-sdm630-modbus.yaml | 2 +- .../release/en/meter/eastron-sdm72d-m.yaml | 2 +- .../release/en/meter/eastron-sdm72dm-v2.yaml | 2 +- .../release/en/meter/enphase-iq-envoy.yaml | 14 +- templates/release/en/meter/fenecon.yaml | 10 +- .../foxess-h1-series-hybrid-inverter.yaml | 2 +- .../foxess-h3-series-hybrid-inverter.yaml | 6 +- ...oxess-h3-smart-series-hybrid-inverter.yaml | 6 +- .../en/meter/fronius-primo-gen24-plus.yaml | 4 +- .../fronius-smartmeter-via-inverter.yaml | 2 +- .../en/meter/fronius-solar-api-v1.yaml | 10 +- .../en/meter/fronius-symo-gen24-plus.yaml | 4 +- ...long-solis-hybrid-inverter-rhi-series.yaml | 2 +- ...inlong-solis-hybrid-inverter-s-series.yaml | 2 +- .../en/meter/ginlong-solis-inverter.yaml | 2 +- .../goodwe-et-eh-bh-bt-hybrid-inverter.yaml | 16 +- .../en/meter/goodwe-sdt-dt-inverter.yaml | 2 +- .../en/meter/growatt-hybrid-inverter.yaml | 2 +- .../meter/growatt-tl-x-h-hybrid-inverter.yaml | 2 +- templates/release/en/meter/homematic-ip.yaml | 24 +- ...oymiles-hm-and-hms-series-via-ahoydtu.yaml | 6 +- templates/release/en/meter/huawei-emma.yaml | 2 +- .../release/en/meter/huawei-smartlogger.yaml | 10 +- .../en/meter/huawei-sun2000-sdongle.yaml | 2 +- .../release/en/meter/huawei-sun2000.yaml | 10 +- .../release/en/meter/inepro-pro380-mod.yaml | 2 +- .../release/en/meter/janitza-b-series.yaml | 2 +- .../release/en/meter/janitza-umg-series.yaml | 2 +- .../release/en/meter/keba-kecontact-e10.yaml | 2 +- .../en/meter/kostal-energy-meter-c-kem-c.yaml | 2 +- .../en/meter/kostal-energy-meter-p-kem-p.yaml | 2 +- ...cl-grid-charging-of-the-house-battery.yaml | 8 +- .../en/meter/kostal-plenticore-hybrid.yaml | 10 +- ...ostal-smart-energy-meter-via-inverter.yaml | 2 +- .../en/meter/kostal-smart-energy-meter.yaml | 2 +- .../release/en/meter/lg-ess-home-15.yaml | 14 +- .../release/en/meter/lg-ess-home-8-10.yaml | 14 +- .../en/meter/m-tec-energy-butler-gen2.yaml | 2 +- .../en/meter/m-tec-energy-butler-gen3.yaml | 2 +- .../meter/marstek-venus-battery-storage.yaml | 22 +- .../release/en/meter/my-pv-wifi-meter.yaml | 2 +- templates/release/en/meter/openems.yaml | 10 +- .../release/en/meter/orno-or-we-516.yaml | 2 +- .../release/en/meter/orno-or-we-517.yaml | 2 +- templates/release/en/meter/plexlog.yaml | 2 +- templates/release/en/meter/powerdog.yaml | 2 +- .../release/en/meter/powerfox-poweropti.yaml | 6 +- .../en/meter/qcells-q-home-ess-hyb-g3.yaml | 26 +- templates/release/en/meter/rct-power.yaml | 6 - .../meter/saia-burgess-controls-sbc-ale3.yaml | 2 +- .../meter/saia-burgess-controls-sbc-awd3.yaml | 2 +- .../saj-h1-series-hybrid-solar-inverter.yaml | 2 +- .../saj-h2-series-hybrid-solar-inverter.yaml | 6 +- .../meter/saj-r5-series-solar-inverter.yaml | 2 +- .../release/en/meter/sax-homespeicher.yaml | 2 +- .../schneider-electric-iem3xxx-modbus.yaml | 2 +- templates/release/en/meter/senec-home.yaml | 14 +- .../senergy-se-4-5-6ktl-s1-g2-inverter.yaml | 2 +- .../release/en/meter/shelly-1pm-mini.yaml | 8 +- templates/release/en/meter/shelly-1pm.yaml | 8 +- templates/release/en/meter/shelly-em.yaml | 8 +- templates/release/en/meter/shelly-plug-s.yaml | 8 +- .../release/en/meter/shelly-pm-mini.yaml | 8 +- .../release/en/meter/shelly-pro-1pm.yaml | 8 +- .../meter/shelly-pro-3em-monophase-mode.yaml | 8 +- templates/release/en/meter/shelly-pro-em.yaml | 8 +- .../release/en/meter/siemens-7kt1665.yaml | 2 +- .../siemens-junelight-smart-battery.yaml | 2 +- .../release/en/meter/siemens-pac-2200.yaml | 2 +- ...gen-hybrid-sigen-pv-max-sigenstore-ec.yaml | 14 +- .../release/en/meter/sma-data-manager.yaml | 2 +- .../sma-smart-energy-hybrid-inverter.yaml | 6 +- ...-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml | 6 +- ...-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml | 6 +- .../en/meter/sma-sunny-island-modbus.yaml | 6 +- templates/release/en/meter/sma-webbox.yaml | 2 +- .../en/meter/sma-wechselrichter-modbus.yaml | 2 +- .../en/meter/sofarsolar-hybrid-inverter.yaml | 2 +- .../en/meter/sofarsolar-hyd-3-6k-ep.yaml | 12 +- .../en/meter/sofarsolar-hyd-5-20k-3ph.yaml | 12 +- .../release/en/meter/sofarsolar-inverter.yaml | 2 +- .../en/meter/sofarsolar-sofar-5-24ktl-g3.yaml | 12 +- .../en/meter/sofarsolar-sofar-80-136ktl.yaml | 12 +- .../en/meter/solaredge-hybrid-inverter.yaml | 10 +- .../release/en/meter/solaredge-inverter.yaml | 2 +- ...rmax-max-storage-max-storage-ultimate.yaml | 10 +- .../en/meter/solarmax-solarmax-smt.yaml | 2 +- .../en/meter/solarmax-sp-series-inverter.yaml | 2 +- .../en/meter/solax-hybrid-x1-x3-g3-g4.yaml | 26 +- templates/release/en/meter/solinteng.yaml | 10 +- .../en/meter/sonnen-sonnenbatterie.yaml | 6 +- templates/release/en/meter/st-ems.yaml | 10 +- .../en/meter/sungrow-sg-series-inverter.yaml | 2 +- .../sungrow-sh-series-hybrid-inverter.yaml | 2 +- .../en/meter/sunspec-battery-model-124.yaml | 2 +- .../en/meter/sunspec-battery-model-802.yaml | 2 +- .../en/meter/sunspec-hybrid-inverter.yaml | 2 +- .../release/en/meter/sunspec-inverter.yaml | 2 +- templates/release/en/meter/sunspec-meter.yaml | 2 +- .../en/meter/sunsynk-3p-hybrid-inverter.yaml | 6 +- .../en/meter/sunsynk-hp3-hybrid-inverter.yaml | 14 +- .../en/meter/sunsynk-micro-inverter.yaml | 2 +- .../sunsynk-storage-hybrid-inverter.yaml | 2 +- .../en/meter/sunsynk-string-inverter.yaml | 2 +- templates/release/en/meter/sunway.yaml | 10 +- .../release/en/meter/tesla-powerwall.yaml | 32 +- templates/release/en/meter/tibber-pulse.yaml | 8 +- templates/release/en/meter/victron-em24.yaml | 2 +- .../release/en/meter/victron-em24_e1.yaml | 2 +- .../release/en/meter/victron-em530-em540.yaml | 2 +- .../release/en/meter/victron-energy.yaml | 12 +- templates/release/en/meter/victron-et340.yaml | 2 +- ...olkszahler-http-api-import-and-export.yaml | 16 +- .../en/meter/volkszahler-http-api.yaml | 12 +- .../en/meter/volkszahler-websocket-api.yaml | 4 +- templates/release/en/meter/vzlogger.yaml | 60 +- templates/release/en/meter/wago-879-30xx.yaml | 2 +- templates/release/en/meter/wattsonic.yaml | 10 +- .../en/meter/weidmuller-em110-rtu-2p.yaml | 2 +- .../en/meter/weidmuller-em111-rtu-2p.yaml | 2 +- .../en/meter/weidmuller-em120-rtu-2p.yaml | 2 +- .../en/meter/weidmuller-em122-rtu-2p.yaml | 2 +- .../en/meter/zcs-azzurro-hybrid-inverter.yaml | 2 +- .../en/meter/zcs-azzurro-inverter.yaml | 2 +- .../release/en/meter/zendure-hyper-2000.yaml | 30 +- .../release/en/tariff/amber-electric.yaml | 18 +- templates/release/en/tariff/awattar.yaml | 6 +- .../electricity-maps-commercial-api.yaml | 8 +- .../en/tariff/electricity-maps-free-api.yaml | 8 +- templates/release/en/tariff/energinet.yaml | 6 +- templates/release/en/tariff/enever.yaml | 16 +- templates/release/en/tariff/entso-e.yaml | 12 +- .../release/en/tariff/forecast-solar.yaml | 8 +- .../release/en/tariff/fraunhofer-ise.yaml | 8 +- .../release/en/tariff/grunstromindex.yaml | 8 +- .../release/en/tariff/national-grid-eso.yaml | 8 +- .../en/tariff/nordpool-spot-prices.yaml | 12 +- .../release/en/tariff/octopus-energy-api.yaml | 14 +- .../tariff/octopus-energy-product-code.yaml | 12 +- templates/release/en/tariff/open-meteo.yaml | 4 +- templates/release/en/tariff/ostrom.yaml | 12 +- .../en/tariff/smartenergy-smartcontrol.yaml | 1 + templates/release/en/tariff/solcast.yaml | 28 +- .../release/en/tariff/spotty-energie.yaml | 12 +- templates/release/en/tariff/tibber.yaml | 12 +- .../en/tariff/victron-vrm-solar-forecast.yaml | 4 +- templates/release/en/vehicle/aiways.yaml | 6 +- templates/release/en/vehicle/audi.yaml | 6 +- templates/release/en/vehicle/bmw.yaml | 12 +- templates/release/en/vehicle/citroen.yaml | 18 +- templates/release/en/vehicle/dacia.yaml | 6 +- templates/release/en/vehicle/ds.yaml | 18 +- templates/release/en/vehicle/evnotify.yaml | 18 +- templates/release/en/vehicle/fiat.yaml | 12 +- templates/release/en/vehicle/ford.yaml | 18 +- .../vehicle/generic-vehicle-without-api.yaml | 6 +- .../release/en/vehicle/hyundai-bluelink.yaml | 6 +- .../release/en/vehicle/iobroker-bmw.yaml | 14 +- templates/release/en/vehicle/iso15118.yaml | 6 +- templates/release/en/vehicle/jeep.yaml | 12 +- .../release/en/vehicle/kia-bluelink.yaml | 6 +- .../release/en/vehicle/mercedes-benz.yaml | 24 +- templates/release/en/vehicle/mg.yaml | 6 +- templates/release/en/vehicle/mg2mqtt.yaml | 6 +- templates/release/en/vehicle/mini.yaml | 12 +- templates/release/en/vehicle/mz2mqtt.yaml | 6 +- .../release/en/vehicle/nissan-ariya.yaml | 6 +- .../en/vehicle/nissan-leaf-pre-2019.yaml | 6 +- templates/release/en/vehicle/nissan-leaf.yaml | 6 +- templates/release/en/vehicle/opel.yaml | 18 +- .../open-vehicle-monitoring-system.yaml | 16 +- templates/release/en/vehicle/peugeot.yaml | 18 +- templates/release/en/vehicle/polestar.yaml | 6 +- .../en/vehicle/psa-car-controller.yaml | 18 +- templates/release/en/vehicle/renault.yaml | 6 +- ...ect-gen3-ateca-leon-formentor-tarraco.yaml | 6 +- ...aconnect-gen4-born-formentor-tavascan.yaml | 6 +- templates/release/en/vehicle/skoda-enyaq.yaml | 6 +- templates/release/en/vehicle/smart-1.yaml | 6 +- templates/release/en/vehicle/smart-eq.yaml | 24 +- templates/release/en/vehicle/tesla-ble.yaml | 12 +- templates/release/en/vehicle/tesla.yaml | 34 +- templates/release/en/vehicle/teslalogger.yaml | 12 +- templates/release/en/vehicle/teslamate.yaml | 6 +- templates/release/en/vehicle/tessie.yaml | 6 +- templates/release/en/vehicle/toyota.yaml | 6 +- templates/release/en/vehicle/tronity.yaml | 6 +- .../en/vehicle/volkswagen-we-connect-id.yaml | 6 +- templates/release/en/vehicle/volvo.yaml | 38 +- templates/release/en/vehicle/volvo2mqtt.yaml | 6 +- .../release/en/vehicle/zero-motorcycles.yaml | 6 +- 2055 files changed, 26277 insertions(+), 11152 deletions(-) diff --git a/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx b/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx index b35690c829..c207444d09 100644 --- a/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx +++ b/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB Terra AC (OCPP) - +
+
+ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf @@ -21,29 +24,40 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-abb-tac` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/abb-terra-ac.mdx b/docs/devices-next/chargers/abb-terra-ac.mdx index fa04914cfa..5d7df7d230 100644 --- a/docs/devices-next/chargers/abb-terra-ac.mdx +++ b/docs/devices-next/chargers/abb-terra-ac.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB Terra AC - +
+
+ Requires firmware >= 1.6.5 @@ -40,12 +43,23 @@ Requires firmware >= 1.6.5 id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `abb` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/chargers/abl-em4-single-ocpp.mdx b/docs/devices-next/chargers/abl-em4-single-ocpp.mdx index 7d79eff172..aa1e225117 100644 --- a/docs/devices-next/chargers/abl-em4-single-ocpp.mdx +++ b/docs/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Single (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-abl` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/abl-em4-single-sbcx.mdx b/docs/devices-next/chargers/abl-em4-single-sbcx.mdx index 6cf17fea0e..619b44735f 100644 --- a/docs/devices-next/chargers/abl-em4-single-sbcx.mdx +++ b/docs/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Single (SBCx) - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `abl-em4` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx b/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx index fe43ca44ae..01c60fb005 100644 --- a/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx +++ b/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Twin (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-abl` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx b/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx index 46639454d3..bbaa775fa2 100644 --- a/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx +++ b/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Twin (SBCx) - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `abl-em4` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/abl-emh1.mdx b/docs/devices-next/chargers/abl-emh1.mdx index 0500bd3e2e..06e9d7a6d8 100644 --- a/docs/devices-next/chargers/abl-emh1.mdx +++ b/docs/devices-next/chargers/abl-emh1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH1 - +
+
+ +
+
+ +
+
## Template Parameter `abl` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | diff --git a/docs/devices-next/chargers/abl-emh2-ocpp.mdx b/docs/devices-next/chargers/abl-emh2-ocpp.mdx index ed23abcbf5..d89cc30e2b 100644 --- a/docs/devices-next/chargers/abl-emh2-ocpp.mdx +++ b/docs/devices-next/chargers/abl-emh2-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH2 (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-abl` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/abl-emh2.mdx b/docs/devices-next/chargers/abl-emh2.mdx index 8489de2b8b..23fff9bef2 100644 --- a/docs/devices-next/chargers/abl-emh2.mdx +++ b/docs/devices-next/chargers/abl-emh2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH2 - +
+
+ +
+
+ +
+
## Template Parameter `abl` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | diff --git a/docs/devices-next/chargers/abl-emh3-ocpp.mdx b/docs/devices-next/chargers/abl-emh3-ocpp.mdx index 5e719ba995..ef917c67c4 100644 --- a/docs/devices-next/chargers/abl-emh3-ocpp.mdx +++ b/docs/devices-next/chargers/abl-emh3-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH3 (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-abl` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/alfen-eve-ocpp.mdx b/docs/devices-next/chargers/alfen-eve-ocpp.mdx index b34f71d60d..6cafdc100f 100644 --- a/docs/devices-next/chargers/alfen-eve-ocpp.mdx +++ b/docs/devices-next/chargers/alfen-eve-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alfen Eve (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-alfen` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/alfen-eve.mdx b/docs/devices-next/chargers/alfen-eve.mdx index 0811abd225..58c1138c1d 100644 --- a/docs/devices-next/chargers/alfen-eve.mdx +++ b/docs/devices-next/chargers/alfen-eve.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alfen Eve - +
+
+ The "Active load balancing" license is required for external Modbus control of the charger. Enable "Active Load Balancing" and select "Energy Management System" as Data Source in the configuration. It is recommended to set "ValidityTime" ("TCP/IP EMS" menu) to 300s. When using "Double" charger both loadpoints need to be added. The the first port (or single) is accessable on ID 1, second port on ID 2. @@ -27,12 +30,23 @@ The "Active load balancing" license is required for external Modbus control of t id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `alfen` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/alpha-innotec.mdx b/docs/devices-next/chargers/alpha-innotec.mdx index ddc78e0987..24b2ef820d 100644 --- a/docs/devices-next/chargers/alpha-innotec.mdx +++ b/docs/devices-next/chargers/alpha-innotec.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # alpha innotec - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx index 427488a061..18ae9888ce 100644 --- a/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx +++ b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alphatec Ladesäule Twin - +
+
+ The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. @@ -34,12 +37,23 @@ The motherboard requires current firmware. You can recognize a current software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `alphatec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/alphatec-wallbox-mini.mdx b/docs/devices-next/chargers/alphatec-wallbox-mini.mdx index cbf1a14ed0..056e41c29c 100644 --- a/docs/devices-next/chargers/alphatec-wallbox-mini.mdx +++ b/docs/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alphatec Wallbox Mini - +
+
+ The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. @@ -34,12 +37,23 @@ The motherboard requires current firmware. You can recognize a current software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `alphatec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/alphatec-wallbox-power.mdx b/docs/devices-next/chargers/alphatec-wallbox-power.mdx index e2e7832918..f6ae0bb6c6 100644 --- a/docs/devices-next/chargers/alphatec-wallbox-power.mdx +++ b/docs/devices-next/chargers/alphatec-wallbox-power.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alphatec Wallbox Power - +
+
+ The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. @@ -34,12 +37,23 @@ The motherboard requires current firmware. You can recognize a current software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `alphatec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx index 0f1f33d25d..e0f7823780 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox connect.business - +
+
+ +
+
+ +
+
## Template Parameter `amperfied` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx index 439e8c3df0..019bf3680d 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox connect.home - +
+
+ +
+
+ +
+
## Template Parameter `amperfied` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx index 653eba1989..d08f71244b 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox connect.solar - +
+
+ +
+
+ +
+
## Template Parameter `amperfied-solar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx index 4e31ead08d..5a1575e4bd 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox Energy Control - +
+
+ Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). @@ -34,12 +37,23 @@ Please read the wiring and configuration manual carefully. All boxes must be con id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `heidelberg` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/ampure-next.mdx b/docs/devices-next/chargers/ampure-next.mdx index 4a84b413e6..66c5256bea 100644 --- a/docs/devices-next/chargers/ampure-next.mdx +++ b/docs/devices-next/chargers/ampure-next.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ampure NEXT - +
+
+ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. @@ -23,6 +26,17 @@ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. template: webasto-next host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Template Parameter `webasto-next` diff --git a/docs/devices-next/chargers/ampure-unite.mdx b/docs/devices-next/chargers/ampure-unite.mdx index 0f66de22f1..22e2090dcc 100644 --- a/docs/devices-next/chargers/ampure-unite.mdx +++ b/docs/devices-next/chargers/ampure-unite.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ampure Unite - +
+
+ 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `vestel` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/audi-wallbox-plus.mdx b/docs/devices-next/chargers/audi-wallbox-plus.mdx index accc30cdf2..1550e79233 100644 --- a/docs/devices-next/chargers/audi-wallbox-plus.mdx +++ b/docs/devices-next/chargers/audi-wallbox-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Audi Wallbox plus - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -29,6 +32,17 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn template: elliconnect ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elliconnect` diff --git a/docs/devices-next/chargers/audi-wallbox-pro.mdx b/docs/devices-next/chargers/audi-wallbox-pro.mdx index 88d827a43b..63a7479c93 100644 --- a/docs/devices-next/chargers/audi-wallbox-pro.mdx +++ b/docs/devices-next/chargers/audi-wallbox-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Audi Wallbox pro - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -27,6 +30,17 @@ Important: A mostly flawless functionality can only be provided with an external template: ellipro ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `ellipro` diff --git a/docs/devices-next/chargers/autel-ac-compact.mdx b/docs/devices-next/chargers/autel-ac-compact.mdx index 090090bcc5..e163800445 100644 --- a/docs/devices-next/chargers/autel-ac-compact.mdx +++ b/docs/devices-next/chargers/autel-ac-compact.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AUTEL AC Compact - +
+
+ Setup Guide: * In the Autel Charge app, click on “OCPP Server” @@ -26,29 +29,40 @@ Setup Guide: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-autel` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/autel-ac-maxicharger.mdx b/docs/devices-next/chargers/autel-ac-maxicharger.mdx index 414f40550c..ae3dcfae90 100644 --- a/docs/devices-next/chargers/autel-ac-maxicharger.mdx +++ b/docs/devices-next/chargers/autel-ac-maxicharger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AUTEL AC MaxiCharger - +
+
+ Setup Guide: * In the Autel Charge app, click on “OCPP Server” @@ -26,29 +29,40 @@ Setup Guide: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-autel` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/autoaid-business-wallbox.mdx b/docs/devices-next/chargers/autoaid-business-wallbox.mdx index 8f9b16101c..4df185c4e9 100644 --- a/docs/devices-next/chargers/autoaid-business-wallbox.mdx +++ b/docs/devices-next/chargers/autoaid-business-wallbox.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Autoaid Business Wallbox - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-autoaid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx index 510f59ba37..563a5d04a5 100644 --- a/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx +++ b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Autoaid Intelligent Wallbox - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-autoaid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/avm-fritzdect.mdx b/docs/devices-next/chargers/avm-fritzdect.mdx index 17d4e655ed..d8286b2edf 100644 --- a/docs/devices-next/chargers/avm-fritzdect.mdx +++ b/docs/devices-next/chargers/avm-fritzdect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AVM FritzDECT - +
+
+ +
+
+ +
+
## Template Parameter `fritzdect` diff --git a/docs/devices-next/chargers/bender-cc612.mdx b/docs/devices-next/chargers/bender-cc612.mdx index 8ff16ed234..596a177a65 100644 --- a/docs/devices-next/chargers/bender-cc612.mdx +++ b/docs/devices-next/chargers/bender-cc612.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender CC612 - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/bender-cc613.mdx b/docs/devices-next/chargers/bender-cc613.mdx index 9ddd98231c..42d6ec21ca 100644 --- a/docs/devices-next/chargers/bender-cc613.mdx +++ b/docs/devices-next/chargers/bender-cc613.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender CC613 - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/bender-icc1314.mdx b/docs/devices-next/chargers/bender-icc1314.mdx index ea2127342d..7a6eac5f7c 100644 --- a/docs/devices-next/chargers/bender-icc1314.mdx +++ b/docs/devices-next/chargers/bender-icc1314.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender ICC1314 - +
+
+ The configuration option 'External Energy Management' must be enabled. @@ -27,12 +30,23 @@ The configuration option 'External Energy Management' must be enabled. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-icc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/bender-icc1324.mdx b/docs/devices-next/chargers/bender-icc1324.mdx index 5c2f893e16..f120728021 100644 --- a/docs/devices-next/chargers/bender-icc1324.mdx +++ b/docs/devices-next/chargers/bender-icc1324.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender ICC1324 - +
+
+ The configuration option 'External Energy Management' must be enabled. @@ -27,12 +30,23 @@ The configuration option 'External Energy Management' must be enabled. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-icc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/bmw-i-wallbox.mdx b/docs/devices-next/chargers/bmw-i-wallbox.mdx index 23ff9f06bc..3c01e87ef7 100644 --- a/docs/devices-next/chargers/bmw-i-wallbox.mdx +++ b/docs/devices-next/chargers/bmw-i-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BMW i Wallbox - +
+
+ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. @@ -37,12 +40,23 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +
+
+ +
+
## Template Parameter `keba-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/chargers/bosch-sg-ready.mdx b/docs/devices-next/chargers/bosch-sg-ready.mdx index fc879fdda7..abc528da35 100644 --- a/docs/devices-next/chargers/bosch-sg-ready.mdx +++ b/docs/devices-next/chargers/bosch-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bosch SG Ready - +
+
+ Integrated via [EMSESP](https://emsesp.org/) @@ -22,16 +25,27 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> +
+
+ +
+
## Template Parameter `emsesp` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| `token` | | | no | +| Token
`token` | | | no | | Power source
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater` | no | diff --git a/docs/devices-next/chargers/bosch-x-change.mdx b/docs/devices-next/chargers/bosch-x-change.mdx index 439f0107e5..f35810a642 100644 --- a/docs/devices-next/chargers/bosch-x-change.mdx +++ b/docs/devices-next/chargers/bosch-x-change.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bösch x-change - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `kermi` @@ -33,5 +47,5 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx b/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx index 07eb74689d..e8759cca1a 100644 --- a/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Buderus Logamatic HMC 20 Z - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx b/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx index c5928d9af3..1ee7c8309a 100644 --- a/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Buderus Logamatic HMC 20 - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/buderus-sg-ready.mdx b/docs/devices-next/chargers/buderus-sg-ready.mdx index 3857db3e59..e01b55a4d8 100644 --- a/docs/devices-next/chargers/buderus-sg-ready.mdx +++ b/docs/devices-next/chargers/buderus-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Buderus SG Ready - +
+
+ Integrated via [EMSESP](https://emsesp.org/) @@ -22,16 +25,27 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> +
+
+ +
+
## Template Parameter `emsesp` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| `token` | | | no | +| Token
`token` | | | no | | Power source
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater` | no | diff --git a/docs/devices-next/chargers/cfos-power-brain-solar.mdx b/docs/devices-next/chargers/cfos-power-brain-solar.mdx index 422895b2ee..1d5547fe56 100644 --- a/docs/devices-next/chargers/cfos-power-brain-solar.mdx +++ b/docs/devices-next/chargers/cfos-power-brain-solar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # cFos Power Brain Solar - +
+
+ S0 meters must be configured separately as charge meter. Phase switching is only available with the Solar variant and must be enabled by the user: @@ -25,6 +28,17 @@ Phase switching is only available with the Solar variant and must be enabled by type: template template: cfos host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `cfos` diff --git a/docs/devices-next/chargers/cfos-power-brain.mdx b/docs/devices-next/chargers/cfos-power-brain.mdx index a5c27d90b7..a699759914 100644 --- a/docs/devices-next/chargers/cfos-power-brain.mdx +++ b/docs/devices-next/chargers/cfos-power-brain.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # cFos Power Brain - +
+
+ S0 meters must be configured separately as charge meter. Phase switching is only available with the Solar variant and must be enabled by the user: @@ -25,6 +28,17 @@ Phase switching is only available with the Solar variant and must be enabled by type: template template: cfos host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `cfos` diff --git a/docs/devices-next/chargers/charge-amps-halo.mdx b/docs/devices-next/chargers/charge-amps-halo.mdx index 29cadaeba2..16547a6053 100644 --- a/docs/devices-next/chargers/charge-amps-halo.mdx +++ b/docs/devices-next/chargers/charge-amps-halo.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Charge Amps Halo - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-chargeamps` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/compleo-ebox.mdx b/docs/devices-next/chargers/compleo-ebox.mdx index 96f6108c76..4fdd8cb101 100644 --- a/docs/devices-next/chargers/compleo-ebox.mdx +++ b/docs/devices-next/chargers/compleo-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Compleo eBox - +
+
+ +
+
+ +
+
## Template Parameter `innogy-ebox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx b/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx index 1186ec7683..cb02000da5 100644 --- a/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx +++ b/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # CTA All-In-One Aeroplus - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/cubos-c11e.mdx b/docs/devices-next/chargers/cubos-c11e.mdx index 5ab9876748..70908a7f2f 100644 --- a/docs/devices-next/chargers/cubos-c11e.mdx +++ b/docs/devices-next/chargers/cubos-c11e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # CUBOS C11E - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/cubos-c22e.mdx b/docs/devices-next/chargers/cubos-c22e.mdx index 55db0558a2..ee423598af 100644 --- a/docs/devices-next/chargers/cubos-c22e.mdx +++ b/docs/devices-next/chargers/cubos-c22e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # CUBOS C22E - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/cupra-charger-connect-2.mdx b/docs/devices-next/chargers/cupra-charger-connect-2.mdx index 572adf7bef..30ab77ec2d 100644 --- a/docs/devices-next/chargers/cupra-charger-connect-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-connect-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Connect 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/cupra-charger-connect.mdx b/docs/devices-next/chargers/cupra-charger-connect.mdx index 98b1ac4341..989510a5ce 100644 --- a/docs/devices-next/chargers/cupra-charger-connect.mdx +++ b/docs/devices-next/chargers/cupra-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Connect - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -29,6 +32,17 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn template: elliconnect ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elliconnect` diff --git a/docs/devices-next/chargers/cupra-charger-pro-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-2.mdx index 92ffc58fa7..5ac13c3577 100644 --- a/docs/devices-next/chargers/cupra-charger-pro-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Pro 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx index b4d96cfa7c..a44de36579 100644 --- a/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Pro Eichrecht 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/cupra-charger-pro.mdx b/docs/devices-next/chargers/cupra-charger-pro.mdx index b66843cede..8bc66dd45d 100644 --- a/docs/devices-next/chargers/cupra-charger-pro.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Pro - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -27,6 +30,17 @@ Important: A mostly flawless functionality can only be provided with an external template: ellipro ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `ellipro` diff --git a/docs/devices-next/chargers/dadapower-premium-wallbox.mdx b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx index 17771a0b7c..3da55d93d6 100644 --- a/docs/devices-next/chargers/dadapower-premium-wallbox.mdx +++ b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Dadapower Premium Wallbox - +
+
+ +
+
+ +
+
## Template Parameter `dadapower` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/daheimladen-wallbox.mdx b/docs/devices-next/chargers/daheimladen-wallbox.mdx index 435bc29154..4211393b48 100644 --- a/docs/devices-next/chargers/daheimladen-wallbox.mdx +++ b/docs/devices-next/chargers/daheimladen-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DaheimLaden Wallbox - +
+
+ Wallbox must be operated with a recent firmware including Modbus support. Furthermore, “Nachladen” (Smart) or “RSDA” (Touch) must be activated in settings. @@ -23,6 +26,17 @@ Wallbox must be operated with a recent firmware including Modbus support. Furthe template: daheimladen-mb host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Template Parameter `daheimladen-mb` diff --git a/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx index ee1de3fa59..27ca6dd03d 100644 --- a/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx +++ b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Daikin HomeHub (SG Ready) - +
+
+ +
+
+ +
+
## Template Parameter `daikin-homehub` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | diff --git a/docs/devices-next/chargers/delta-ac-max-basic.mdx b/docs/devices-next/chargers/delta-ac-max-basic.mdx index 65244b2a07..0be6734cf8 100644 --- a/docs/devices-next/chargers/delta-ac-max-basic.mdx +++ b/docs/devices-next/chargers/delta-ac-max-basic.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta AC Max Basic - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `delta` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/delta-ac-max-smart.mdx b/docs/devices-next/chargers/delta-ac-max-smart.mdx index 3a191f8e4a..ea40457e09 100644 --- a/docs/devices-next/chargers/delta-ac-max-smart.mdx +++ b/docs/devices-next/chargers/delta-ac-max-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta AC MAX Smart - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `delta` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/delta-slim-charger.mdx b/docs/devices-next/chargers/delta-slim-charger.mdx index db555fbd40..7202fa9d9a 100644 --- a/docs/devices-next/chargers/delta-slim-charger.mdx +++ b/docs/devices-next/chargers/delta-slim-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta SLIM Charger - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `delta` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/delta-ultra-fast-charger.mdx b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx index b184805abf..b2d9e473a4 100644 --- a/docs/devices-next/chargers/delta-ultra-fast-charger.mdx +++ b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta Ultra Fast Charger - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `delta` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/demo-charger.mdx b/docs/devices-next/chargers/demo-charger.mdx index d7794b883b..7fd3a0a700 100644 --- a/docs/devices-next/chargers/demo-charger.mdx +++ b/docs/devices-next/chargers/demo-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Demo charger - +
+
+ For demonstration purposes. Charger with a fixed set of values. @@ -32,6 +35,17 @@ For demonstration purposes. Charger with a fixed set of values. enabled: true # Enabled, optional maxcurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) phases1p3p: false # Phase switching, optional`} /> +
+
+ +
+
## Template Parameter `demo-charger` diff --git a/docs/devices-next/chargers/e-on-drive-ebox.mdx b/docs/devices-next/chargers/e-on-drive-ebox.mdx index de7f7118da..7a5b22206f 100644 --- a/docs/devices-next/chargers/e-on-drive-ebox.mdx +++ b/docs/devices-next/chargers/e-on-drive-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E.ON Drive eBox - +
+
+ +
+
+ +
+
## Template Parameter `innogy-ebox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/e-on-drive-vbox.mdx b/docs/devices-next/chargers/e-on-drive-vbox.mdx index fefc4bf2f2..2ce06571f0 100644 --- a/docs/devices-next/chargers/e-on-drive-vbox.mdx +++ b/docs/devices-next/chargers/e-on-drive-vbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E.ON Drive vBox - +
+
+ 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `vestel` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/e3-dc-easy-connect.mdx b/docs/devices-next/chargers/e3-dc-easy-connect.mdx index bc1e76f3e3..ae687d5e1b 100644 --- a/docs/devices-next/chargers/e3-dc-easy-connect.mdx +++ b/docs/devices-next/chargers/e3-dc-easy-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E3/DC Easy Connect - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/easee-charge-core.mdx b/docs/devices-next/chargers/easee-charge-core.mdx index 0ffdfd7195..09ed4394fe 100644 --- a/docs/devices-next/chargers/easee-charge-core.mdx +++ b/docs/devices-next/chargers/easee-charge-core.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Charge Core - +
+
+ + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +
+
+ +
+
## Template Parameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | Username
`user` | Email address | | yes | | Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | -| `charger` | | Beispiel: `EH______` | yes | +| Charger serial number
`charger` | | Beispiel: `EH______` | yes | | Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | -| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | +| Authentication enabled
`authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | diff --git a/docs/devices-next/chargers/easee-charge-lite.mdx b/docs/devices-next/chargers/easee-charge-lite.mdx index 888376913f..848a0a9617 100644 --- a/docs/devices-next/chargers/easee-charge-lite.mdx +++ b/docs/devices-next/chargers/easee-charge-lite.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Charge Lite - +
+
+ + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +
+
+ +
+
## Template Parameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | Username
`user` | Email address | | yes | | Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | -| `charger` | | Beispiel: `EH______` | yes | +| Charger serial number
`charger` | | Beispiel: `EH______` | yes | | Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | -| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | +| Authentication enabled
`authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | diff --git a/docs/devices-next/chargers/easee-charge.mdx b/docs/devices-next/chargers/easee-charge.mdx index efb812e7d7..3bfff7bc18 100644 --- a/docs/devices-next/chargers/easee-charge.mdx +++ b/docs/devices-next/chargers/easee-charge.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Charge - +
+
+ + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +
+
+ +
+
## Template Parameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | Username
`user` | Email address | | yes | | Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | -| `charger` | | Beispiel: `EH______` | yes | +| Charger serial number
`charger` | | Beispiel: `EH______` | yes | | Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | -| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | +| Authentication enabled
`authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | diff --git a/docs/devices-next/chargers/easee-home.mdx b/docs/devices-next/chargers/easee-home.mdx index dd532e264f..3f80d94390 100644 --- a/docs/devices-next/chargers/easee-home.mdx +++ b/docs/devices-next/chargers/easee-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Home - +
+
+ + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> +
+
+ +
+
## Template Parameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | Username
`user` | Email address | | yes | | Password
`password` | same as Easee app or the web portal (https://easee.cloud) | | yes | -| `charger` | | Beispiel: `EH______` | yes | +| Charger serial number
`charger` | | Beispiel: `EH______` | yes | | Timeout
`timeout` | Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. | Standard: `20s`
Beispiel: `10s` | no | -| `authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | +| Authentication enabled
`authorize` | Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. | | no | diff --git a/docs/devices-next/chargers/ebee-wallbox.mdx b/docs/devices-next/chargers/ebee-wallbox.mdx index 4f610a8900..5d02827758 100644 --- a/docs/devices-next/chargers/ebee-wallbox.mdx +++ b/docs/devices-next/chargers/ebee-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ebee Wallbox - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/echarge-cph1.mdx b/docs/devices-next/chargers/echarge-cph1.mdx index c3d0ac772f..82d76b7d51 100644 --- a/docs/devices-next/chargers/echarge-cph1.mdx +++ b/docs/devices-next/chargers/echarge-cph1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # echarge cPH1 - +
+
+ Charge mode must be configured as `manual` @@ -27,13 +30,24 @@ Charge mode must be configured as `manual` template: hardybarth-ecb1 host: 192.0.2.2 # IP address or hostname connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `hardybarth-ecb1` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/echarge-cph2.mdx b/docs/devices-next/chargers/echarge-cph2.mdx index 47e8fe531d..b636f7fb83 100644 --- a/docs/devices-next/chargers/echarge-cph2.mdx +++ b/docs/devices-next/chargers/echarge-cph2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # echarge cPH2 - +
+
+ +
+
+ +
+
## Template Parameter `hardybarth-salia` diff --git a/docs/devices-next/chargers/echarge-cpm2.mdx b/docs/devices-next/chargers/echarge-cpm2.mdx index 5886040db5..edfccf903c 100644 --- a/docs/devices-next/chargers/echarge-cpm2.mdx +++ b/docs/devices-next/chargers/echarge-cpm2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # echarge cPμ2 - +
+
+ +
+
+ +
+
## Template Parameter `hardybarth-salia` diff --git a/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx b/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx index ee9ef213f7..0585d3648e 100644 --- a/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx +++ b/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EcoHarmony EVSE EPC 2.0 Plus - +
+
+ +
+
+ +
+
## Template Parameter `obo` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/chargers/edgetech-smart-evse.mdx b/docs/devices-next/chargers/edgetech-smart-evse.mdx index 11eafc16b1..7b8d59de3f 100644 --- a/docs/devices-next/chargers/edgetech-smart-evse.mdx +++ b/docs/devices-next/chargers/edgetech-smart-evse.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Edgetech Smart EVSE - +
+
+ +
+
+ +
+
## Template Parameter `smartevse` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/eebus-compatible.mdx b/docs/devices-next/chargers/eebus-compatible.mdx index 7e22859905..7a65ff5f53 100644 --- a/docs/devices-next/chargers/eebus-compatible.mdx +++ b/docs/devices-next/chargers/eebus-compatible.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EEBUS compatible - +
+
+ +
+
+ +
+
## Template Parameter `eebus` diff --git a/docs/devices-next/chargers/elco.mdx b/docs/devices-next/chargers/elco.mdx index a9df553694..0e31e2b41d 100644 --- a/docs/devices-next/chargers/elco.mdx +++ b/docs/devices-next/chargers/elco.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elco - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/elecq-biz.mdx b/docs/devices-next/chargers/elecq-biz.mdx index fe63e627c6..8269dfea42 100644 --- a/docs/devices-next/chargers/elecq-biz.mdx +++ b/docs/devices-next/chargers/elecq-biz.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elecq Biz - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-elecq` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/elecq-home.mdx b/docs/devices-next/chargers/elecq-home.mdx index 9cef59bc11..ac97483875 100644 --- a/docs/devices-next/chargers/elecq-home.mdx +++ b/docs/devices-next/chargers/elecq-home.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elecq Home - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-elecq` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/elecq-station.mdx b/docs/devices-next/chargers/elecq-station.mdx index 43fea337f2..06aa971bfa 100644 --- a/docs/devices-next/chargers/elecq-station.mdx +++ b/docs/devices-next/chargers/elecq-station.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elecq Station - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-elecq` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/eledio-go.mdx b/docs/devices-next/chargers/eledio-go.mdx index ad2ae603d4..478c3e9074 100644 --- a/docs/devices-next/chargers/eledio-go.mdx +++ b/docs/devices-next/chargers/eledio-go.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # eledio go - +
+
+ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 @@ -21,29 +24,40 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-enercab` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/elli-charger-connect-2.mdx b/docs/devices-next/chargers/elli-charger-connect-2.mdx index 539097c62f..6ec54ff0b7 100644 --- a/docs/devices-next/chargers/elli-charger-connect-2.mdx +++ b/docs/devices-next/chargers/elli-charger-connect-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Connect 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/elli-charger-connect.mdx b/docs/devices-next/chargers/elli-charger-connect.mdx index ae92f9d6fb..6d466b3821 100644 --- a/docs/devices-next/chargers/elli-charger-connect.mdx +++ b/docs/devices-next/chargers/elli-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Connect - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -29,6 +32,17 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn template: elliconnect ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elliconnect` diff --git a/docs/devices-next/chargers/elli-charger-pro-2.mdx b/docs/devices-next/chargers/elli-charger-pro-2.mdx index 3f4b3c3147..a5bb341a84 100644 --- a/docs/devices-next/chargers/elli-charger-pro-2.mdx +++ b/docs/devices-next/chargers/elli-charger-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Pro 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx index 3f220a92df..363ccfc913 100644 --- a/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Pro Eichrecht 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/elli-charger-pro.mdx b/docs/devices-next/chargers/elli-charger-pro.mdx index d78895d99e..22d7801e35 100644 --- a/docs/devices-next/chargers/elli-charger-pro.mdx +++ b/docs/devices-next/chargers/elli-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Pro - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -27,6 +30,17 @@ Important: A mostly flawless functionality can only be provided with an external template: ellipro ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `ellipro` diff --git a/docs/devices-next/chargers/em2go-home.mdx b/docs/devices-next/chargers/em2go-home.mdx index 30638a0f05..a752a6f523 100644 --- a/docs/devices-next/chargers/em2go-home.mdx +++ b/docs/devices-next/chargers/em2go-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EM2GO Home - +
+
+ Requires FW Version >= E3C_V1.1. mA regulation requires FW version >= E3C_V1.3. @@ -22,6 +25,17 @@ Requires FW Version >= E3C_V1.1. mA regulation requires FW version >= E3C_V1.3. type: template template: em2go-home host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `em2go-home` diff --git a/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx b/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx index 3c680ba50f..c7b5cfc074 100644 --- a/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx +++ b/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EM2GO Pro Power (OCPP/ONC) - +
+
+ Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15) @@ -27,10 +30,21 @@ Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15 id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `em2go` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/enercab-smart.mdx b/docs/devices-next/chargers/enercab-smart.mdx index c95899f200..b91e729816 100644 --- a/docs/devices-next/chargers/enercab-smart.mdx +++ b/docs/devices-next/chargers/enercab-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # enercab smart - +
+
+ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 @@ -21,29 +24,40 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-enercab` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/enplus-ac-ev-charger.mdx b/docs/devices-next/chargers/enplus-ac-ev-charger.mdx index c2a9414cd4..da0518c07c 100644 --- a/docs/devices-next/chargers/enplus-ac-ev-charger.mdx +++ b/docs/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EN+ AC EV Charger - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-enplus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/ensto-chago-wallbox.mdx b/docs/devices-next/chargers/ensto-chago-wallbox.mdx index 07310463bd..80b9a86f6c 100644 --- a/docs/devices-next/chargers/ensto-chago-wallbox.mdx +++ b/docs/devices-next/chargers/ensto-chago-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ensto Chago Wallbox - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/entratek-power-dot-fix.mdx b/docs/devices-next/chargers/entratek-power-dot-fix.mdx index af035b2296..7846ca8356 100644 --- a/docs/devices-next/chargers/entratek-power-dot-fix.mdx +++ b/docs/devices-next/chargers/entratek-power-dot-fix.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EntraTek Power Dot Fix - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-entratek` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx index 100efd0d5c..c89da73200 100644 --- a/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx +++ b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EntraTek Power Dot Pro 2 - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-entratek` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/esl-walli-light.mdx b/docs/devices-next/chargers/esl-walli-light.mdx index 4ce5b517d5..02bd45981d 100644 --- a/docs/devices-next/chargers/esl-walli-light.mdx +++ b/docs/devices-next/chargers/esl-walli-light.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ESL Walli LIGHT - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/esystems-ghostone.mdx b/docs/devices-next/chargers/esystems-ghostone.mdx index a5eef6e95e..40b59171fd 100644 --- a/docs/devices-next/chargers/esystems-ghostone.mdx +++ b/docs/devices-next/chargers/esystems-ghostone.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # eSystems ghostONE - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: ghost ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `ghost` diff --git a/docs/devices-next/chargers/etrel-inch-duo.mdx b/docs/devices-next/chargers/etrel-inch-duo.mdx index e88c19ed09..bbfc3ce3dc 100644 --- a/docs/devices-next/chargers/etrel-inch-duo.mdx +++ b/docs/devices-next/chargers/etrel-inch-duo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Etrel INCH Duo - +
+
+ The charger must be switched to "Power" charging mode. @@ -29,6 +32,17 @@ The charger must be switched to "Power" charging mode. host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `etrel-duo` @@ -36,7 +50,7 @@ The charger must be switched to "Power" charging mode. |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `502` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/etrel-inch.mdx b/docs/devices-next/chargers/etrel-inch.mdx index 9cbe001883..e430efacf6 100644 --- a/docs/devices-next/chargers/etrel-inch.mdx +++ b/docs/devices-next/chargers/etrel-inch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Etrel INCH - +
+
+ The charger must be switched to "Power" charging mode. @@ -23,6 +26,17 @@ The charger must be switched to "Power" charging mode. template: etrel host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Template Parameter `etrel` diff --git a/docs/devices-next/chargers/evbox-elvi.mdx b/docs/devices-next/chargers/evbox-elvi.mdx index 61ac8c831a..b474d1664b 100644 --- a/docs/devices-next/chargers/evbox-elvi.mdx +++ b/docs/devices-next/chargers/evbox-elvi.mdx @@ -9,39 +9,53 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVBox Elvi - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) + meter: true # Meter ID, optional`} advanced={`chargers: - name: my_charger type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) + meter: true # Meter ID, optional connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-evbox-elvi` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | -| `meter` | | Standard: `true` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Meter ID
`meter` | | Standard: `true` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/evbox-livo.mdx b/docs/devices-next/chargers/evbox-livo.mdx index 6ed0e2801b..9db3e05714 100644 --- a/docs/devices-next/chargers/evbox-livo.mdx +++ b/docs/devices-next/chargers/evbox-livo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVBox Livo - +
+
+ The device requires a fixed IP addres. It's important to set up EEBus first. After setting up EEBus the charger will recognize evcc as a HEMS device on the network. Please use the installer tool to select evcc as HEMS. After this has been done, copy the given SKI from the Install app and add it to your yaml. @@ -23,6 +26,17 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft template: livo ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `livo` diff --git a/docs/devices-next/chargers/evse-din.mdx b/docs/devices-next/chargers/evse-din.mdx index 72b1f73f50..4d9d870732 100644 --- a/docs/devices-next/chargers/evse-din.mdx +++ b/docs/devices-next/chargers/evse-din.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVSE DIN - +
+
+ +
+
+ +
+
## Template Parameter `evse-din` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/evse-wifi.mdx b/docs/devices-next/chargers/evse-wifi.mdx index 5c1b2a05b9..fe1ea0d753 100644 --- a/docs/devices-next/chargers/evse-wifi.mdx +++ b/docs/devices-next/chargers/evse-wifi.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVSE-WiFi - +
+
+ +
+
+ +
+
## Template Parameter `evsewifi` diff --git a/docs/devices-next/chargers/free2move-eprowallbox-move.mdx b/docs/devices-next/chargers/free2move-eprowallbox-move.mdx index 06f6421e12..ac987f7820 100644 --- a/docs/devices-next/chargers/free2move-eprowallbox-move.mdx +++ b/docs/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Free2Move eProWallbox Move - +
+
+ +
+
+ +
+
## Template Parameter `eprowallbox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/free2move-eprowallbox.mdx b/docs/devices-next/chargers/free2move-eprowallbox.mdx index 32f6154e4d..b24c6260a3 100644 --- a/docs/devices-next/chargers/free2move-eprowallbox.mdx +++ b/docs/devices-next/chargers/free2move-eprowallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Free2Move eProWallbox - +
+
+ +
+
+ +
+
## Template Parameter `eprowallbox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx index aca2bad025..8df3f589cc 100644 --- a/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx +++ b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Free2move eSolutions eProWallbox - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-esolutions` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx b/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx index 52ec2ada0b..a418118665 100644 --- a/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx +++ b/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Wattpilot (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-goe` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/garo-glb.mdx b/docs/devices-next/chargers/garo-glb.mdx index 54280af247..0294cbc05f 100644 --- a/docs/devices-next/chargers/garo-glb.mdx +++ b/docs/devices-next/chargers/garo-glb.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo GLB - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/garo-glbplus.mdx b/docs/devices-next/chargers/garo-glbplus.mdx index e0ad8c835b..e4de43c2af 100644 --- a/docs/devices-next/chargers/garo-glbplus.mdx +++ b/docs/devices-next/chargers/garo-glbplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo GLB+ - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/garo-ls4-compact.mdx b/docs/devices-next/chargers/garo-ls4-compact.mdx index e43f0f09a2..db7de3644d 100644 --- a/docs/devices-next/chargers/garo-ls4-compact.mdx +++ b/docs/devices-next/chargers/garo-ls4-compact.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo LS4 compact - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/garo-ls4.mdx b/docs/devices-next/chargers/garo-ls4.mdx index d42012e3f5..758b21a9ef 100644 --- a/docs/devices-next/chargers/garo-ls4.mdx +++ b/docs/devices-next/chargers/garo-ls4.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo LS4 - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx index 5b43422d0b..45f81e0b68 100644 --- a/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx +++ b/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger Gemini (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-goe` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/go-e-charger-gemini.mdx b/docs/devices-next/chargers/go-e-charger-gemini.mdx index d77cb936aa..0c19bef48e 100644 --- a/docs/devices-next/chargers/go-e-charger-gemini.mdx +++ b/docs/devices-next/chargers/go-e-charger-gemini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger Gemini - +
+
+ Requires firmware 052.1 or later. Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. @@ -24,6 +27,17 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" type: template template: go-e-v3 host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `go-e-v3` diff --git a/docs/devices-next/chargers/go-e-charger-homefix.mdx b/docs/devices-next/chargers/go-e-charger-homefix.mdx index f60e1107a6..1063311749 100644 --- a/docs/devices-next/chargers/go-e-charger-homefix.mdx +++ b/docs/devices-next/chargers/go-e-charger-homefix.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger HOMEfix - +
+
+ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. @@ -22,6 +25,17 @@ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. type: template template: go-e host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `go-e` diff --git a/docs/devices-next/chargers/go-e-charger-homeplus.mdx b/docs/devices-next/chargers/go-e-charger-homeplus.mdx index e1781976e9..28499013cf 100644 --- a/docs/devices-next/chargers/go-e-charger-homeplus.mdx +++ b/docs/devices-next/chargers/go-e-charger-homeplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger HOME+ - +
+
+ Requires firmware 052.1 or later. Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. @@ -24,6 +27,17 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" type: template template: go-e-v3 host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `go-e-v3` diff --git a/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx index 48638d700d..815f147e9b 100644 --- a/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx +++ b/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger PRO (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-goe` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/go-e-charger-pro.mdx b/docs/devices-next/chargers/go-e-charger-pro.mdx index eb32e864bd..3c0b621fd8 100644 --- a/docs/devices-next/chargers/go-e-charger-pro.mdx +++ b/docs/devices-next/chargers/go-e-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger PRO - +
+
+ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. @@ -22,6 +25,17 @@ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. type: template template: go-e host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `go-e` diff --git a/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx index 4dab005bef..169c34c44c 100644 --- a/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx +++ b/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger V3 (OCPP) - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-goe` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/go-e-charger-v3.mdx b/docs/devices-next/chargers/go-e-charger-v3.mdx index 7878ab3fe3..135133d195 100644 --- a/docs/devices-next/chargers/go-e-charger-v3.mdx +++ b/docs/devices-next/chargers/go-e-charger-v3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger V3 - +
+
+ Requires firmware 052.1 or later. Requires "HTTP API v1" api, "HTTP API v2" for 1P/3P phase switching. @@ -24,6 +27,17 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" type: template template: go-e-v3 host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `go-e-v3` diff --git a/docs/devices-next/chargers/hardy-barth-cph1.mdx b/docs/devices-next/chargers/hardy-barth-cph1.mdx index bdda6656a4..ce24a121f6 100644 --- a/docs/devices-next/chargers/hardy-barth-cph1.mdx +++ b/docs/devices-next/chargers/hardy-barth-cph1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hardy Barth cPH1 - +
+
+ Charge mode must be configured as `manual` @@ -27,13 +30,24 @@ Charge mode must be configured as `manual` template: hardybarth-ecb1 host: 192.0.2.2 # IP address or hostname connector: 1 # Loadpoint (if >1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `hardybarth-ecb1` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/hardy-barth-cph2.mdx b/docs/devices-next/chargers/hardy-barth-cph2.mdx index 907b33b0da..bb3a2c5dbd 100644 --- a/docs/devices-next/chargers/hardy-barth-cph2.mdx +++ b/docs/devices-next/chargers/hardy-barth-cph2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hardy Barth cPH2 - +
+
+ +
+
+ +
+
## Template Parameter `hardybarth-salia` diff --git a/docs/devices-next/chargers/hardy-barth-cpm2.mdx b/docs/devices-next/chargers/hardy-barth-cpm2.mdx index 3e7b6a2cd5..516ce26e64 100644 --- a/docs/devices-next/chargers/hardy-barth-cpm2.mdx +++ b/docs/devices-next/chargers/hardy-barth-cpm2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hardy Barth cPμ2 - +
+
+ +
+
+ +
+
## Template Parameter `hardybarth-salia` diff --git a/docs/devices-next/chargers/heidelberg-energy-control.mdx b/docs/devices-next/chargers/heidelberg-energy-control.mdx index 7784efbc87..3f5527a242 100644 --- a/docs/devices-next/chargers/heidelberg-energy-control.mdx +++ b/docs/devices-next/chargers/heidelberg-energy-control.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Heidelberg Energy Control - +
+
+ Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). @@ -34,12 +37,23 @@ Please read the wiring and configuration manual carefully. All boxes must be con id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `heidelberg` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/hesotec-ebox.mdx b/docs/devices-next/chargers/hesotec-ebox.mdx index c48477cdb7..7293267089 100644 --- a/docs/devices-next/chargers/hesotec-ebox.mdx +++ b/docs/devices-next/chargers/hesotec-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hesotec eBox - +
+
+ +
+
+ +
+
## Template Parameter `hesotec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/hesotec-esat.mdx b/docs/devices-next/chargers/hesotec-esat.mdx index 08e7a0037a..30c38c7647 100644 --- a/docs/devices-next/chargers/hesotec-esat.mdx +++ b/docs/devices-next/chargers/hesotec-esat.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hesotec eSat - +
+
+ +
+
+ +
+
## Template Parameter `hesotec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/home-assistant-switch.mdx b/docs/devices-next/chargers/home-assistant-switch.mdx index ac62a24fd8..1c781a513f 100644 --- a/docs/devices-next/chargers/home-assistant-switch.mdx +++ b/docs/devices-next/chargers/home-assistant-switch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Home Assistant Switch - +
+
+ +
+
+ +
+
## Template Parameter `homeassistant-switch` diff --git a/docs/devices-next/chargers/homecharge-homecharger.mdx b/docs/devices-next/chargers/homecharge-homecharger.mdx index 836410def7..7eb78b2036 100644 --- a/docs/devices-next/chargers/homecharge-homecharger.mdx +++ b/docs/devices-next/chargers/homecharge-homecharger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Homecharge Homecharger - +
+
+ The charger must be equipped with a built-in meter (models HC11L/HC22L Energy or Profi). For the OCPP configuration, you need to access the EFR-SECC charge controller at http://host/secc. @@ -23,29 +26,40 @@ For login credentials, ask your dealer or the vendor EFR (www.efr.de). - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-homecharge` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/homematic-ip.mdx b/docs/devices-next/chargers/homematic-ip.mdx index 5704dcdeec..041576f696 100644 --- a/docs/devices-next/chargers/homematic-ip.mdx +++ b/docs/devices-next/chargers/homematic-ip.mdx @@ -9,17 +9,20 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Homematic IP - +
+
+ +
+
+ +
+
## Template Parameter `homematic` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010)
`port` | | Standard: `2010` | no | +| XML-RPC server port number
`port` | | Standard: `2010`
Beispiel: `BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010` | no | | Device address/Serial number
`device` | Homematic device id like shown in the CCU web user interface. | Beispiel: `0001EE89AAD848` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | | Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | -| Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2)
`meterchannel` | Homematic meter channel number like shown in the CCU web user interface. | Standard: `6` | yes | -| Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1)
`switchchannel` | Homematic switch actor channel number like shown in the CCU web user interface. | Standard: `3` | yes | -| XML-RPC api cache duration - Default 1s. (valid units are s,m,h)
`cache` | In case of duty cycle problems try a cache setting of 30s. | Standard: `1s`
Beispiel: `5m` | no | +| Meter channel number
`meterchannel` | Homematic meter channel number like shown in the CCU web user interface. | Standard: `6`
Beispiel: `HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2` | yes | +| Switch/Actor channel number
`switchchannel` | Homematic switch actor channel number like shown in the CCU web user interface. | Standard: `3`
Beispiel: `HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1` | yes | +| XML-RPC API cache duration
`cache` | In case of duty cycle problems try a cache setting of 30s. | Standard: `1s`
Beispiel: `5m` | no | | Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | | Heating device
`heating` | Shows °C instead of % | | no | | Icon
`icon` | Will be displayed in the user interface | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | diff --git a/docs/devices-next/chargers/homewizard.mdx b/docs/devices-next/chargers/homewizard.mdx index 51dd5e83db..23f16e4bc7 100644 --- a/docs/devices-next/chargers/homewizard.mdx +++ b/docs/devices-next/chargers/homewizard.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # HomeWizard - +
+
+ +
+
+ +
+
## Template Parameter `homewizard` diff --git a/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx b/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx index ef8af32765..0f76010b87 100644 --- a/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx +++ b/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SCharger-22KT-S0 - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-huawei` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx b/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx index 0fea498495..53187b5d6b 100644 --- a/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx +++ b/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SCharger-7KS-S0 - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-huawei` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/idm.mdx b/docs/devices-next/chargers/idm.mdx index f7c53a6ecf..6836b14f83 100644 --- a/docs/devices-next/chargers/idm.mdx +++ b/docs/devices-next/chargers/idm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IDM - +
+
+ +
+
+ +
+
## Template Parameter `idm` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer` | no | diff --git a/docs/devices-next/chargers/innogy-ebox.mdx b/docs/devices-next/chargers/innogy-ebox.mdx index 07a15edc6d..d203e58862 100644 --- a/docs/devices-next/chargers/innogy-ebox.mdx +++ b/docs/devices-next/chargers/innogy-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Innogy eBox - +
+
+ +
+
+ +
+
## Template Parameter `innogy-ebox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/inro-pantabox.mdx b/docs/devices-next/chargers/inro-pantabox.mdx index 968f06aaef..158c98063b 100644 --- a/docs/devices-next/chargers/inro-pantabox.mdx +++ b/docs/devices-next/chargers/inro-pantabox.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # INRO Pantabox - +
+
+ +
+
+ +
+
## Template Parameter `pantabox` diff --git a/docs/devices-next/chargers/juice-charger-me.mdx b/docs/devices-next/chargers/juice-charger-me.mdx index 6399c5772a..10d6bf265f 100644 --- a/docs/devices-next/chargers/juice-charger-me.mdx +++ b/docs/devices-next/chargers/juice-charger-me.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Juice Charger Me - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/junkers-sg-ready.mdx b/docs/devices-next/chargers/junkers-sg-ready.mdx index bc289f0749..e468bc27a2 100644 --- a/docs/devices-next/chargers/junkers-sg-ready.mdx +++ b/docs/devices-next/chargers/junkers-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Junkers SG Ready - +
+
+ Integrated via [EMSESP](https://emsesp.org/) @@ -22,16 +25,27 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> +
+
+ +
+
## Template Parameter `emsesp` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| `token` | | | no | +| Token
`token` | | | no | | Power source
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater` | no | diff --git a/docs/devices-next/chargers/kathrein-kwb-ac20.mdx b/docs/devices-next/chargers/kathrein-kwb-ac20.mdx index 964f868df2..8b715f3592 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac20.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC20 - +
+
+ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 @@ -27,12 +30,23 @@ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `Kathrein` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/kathrein-kwb-ac35.mdx b/docs/devices-next/chargers/kathrein-kwb-ac35.mdx index 158d9933dc..4e24e81e4a 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac35.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC35 - +
+
+ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 @@ -27,12 +30,23 @@ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `Kathrein` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx index 28f4b9376b..3655e81074 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC40 E - +
+
+ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 @@ -27,12 +30,23 @@ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `Kathrein` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/kathrein-kwb-ac40.mdx b/docs/devices-next/chargers/kathrein-kwb-ac40.mdx index a27c9858b7..92f99c1085 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac40.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC40 - +
+
+ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 @@ -27,12 +30,23 @@ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `Kathrein` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx index 280db3ed76..3e942b71ad 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC60 E - +
+
+ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 @@ -27,12 +30,23 @@ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `Kathrein` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/kathrein-kwb-ac60.mdx b/docs/devices-next/chargers/kathrein-kwb-ac60.mdx index 32ddd6d8c0..86826f1a4b 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac60.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC60 - +
+
+ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web interface. Tested with Firmware version v2.3.2 @@ -27,12 +30,23 @@ The Modbus server (TCP port 502) must be activated on the Wallbox using the Web id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `Kathrein` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/keba-kecontact-p20.mdx b/docs/devices-next/chargers/keba-kecontact-p20.mdx index 7301934382..148ffba4e6 100644 --- a/docs/devices-next/chargers/keba-kecontact-p20.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p20.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P20 - +
+
+ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. @@ -37,12 +40,23 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +
+
+ +
+
## Template Parameter `keba-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx b/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx index 6410bab519..5ed52f8895 100644 --- a/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P30 C-Series - +
+
+ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. @@ -37,12 +40,23 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +
+
+ +
+
## Template Parameter `keba-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx b/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx index 52d72e8e56..dbf95dc12c 100644 --- a/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P30 X-Series - +
+
+ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. @@ -37,12 +40,23 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +
+
+ +
+
## Template Parameter `keba-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx b/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx index d7ac2d398d..bff59a3d7c 100644 --- a/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P40 Pro - +
+
+ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. @@ -37,12 +40,23 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +
+
+ +
+
## Template Parameter `keba-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/chargers/keba-kecontact-p40.mdx b/docs/devices-next/chargers/keba-kecontact-p40.mdx index 81c51f3c59..e90428d240 100644 --- a/docs/devices-next/chargers/keba-kecontact-p40.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p40.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P40 - +
+
+ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. @@ -37,12 +40,23 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +
+
+ +
+
## Template Parameter `keba-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/chargers/kermi-x-center-pro.mdx b/docs/devices-next/chargers/kermi-x-center-pro.mdx index 2834b37c66..53d76d9877 100644 --- a/docs/devices-next/chargers/kermi-x-center-pro.mdx +++ b/docs/devices-next/chargers/kermi-x-center-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kermi x-center pro - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `kermi` @@ -33,5 +47,5 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/chargers/kontron-solar-charger.mdx b/docs/devices-next/chargers/kontron-solar-charger.mdx index f4b6d66b2a..4532bd3c0f 100644 --- a/docs/devices-next/chargers/kontron-solar-charger.mdx +++ b/docs/devices-next/chargers/kontron-solar-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kontron Solar Charger - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: ghost ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `ghost` diff --git a/docs/devices-next/chargers/kostal-enector.mdx b/docs/devices-next/chargers/kostal-enector.mdx index dd1104969b..3959aed5b2 100644 --- a/docs/devices-next/chargers/kostal-enector.mdx +++ b/docs/devices-next/chargers/kostal-enector.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Enector - +
+
+ The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. @@ -36,12 +39,23 @@ For Kostal systems with Smart Energy Meter (KSEM), the additional activation cod id: 50 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `mennekes-compact` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/kse-wbx16.mdx b/docs/devices-next/chargers/kse-wbx16.mdx index 6615040b3f..81f3f27dab 100644 --- a/docs/devices-next/chargers/kse-wbx16.mdx +++ b/docs/devices-next/chargers/kse-wbx16.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KSE wBX16 - +
+
+ +
+
+ +
+
## Template Parameter `kse` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/ladefoxx-evload.mdx b/docs/devices-next/chargers/ladefoxx-evload.mdx index 77f94ad9c4..b3c5b7a24c 100644 --- a/docs/devices-next/chargers/ladefoxx-evload.mdx +++ b/docs/devices-next/chargers/ladefoxx-evload.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LadeFoxx EvLoad - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `phoenix-charx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx b/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx index 022ec2ecf9..5f6bfaf433 100644 --- a/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx +++ b/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LadeFoxx Mikro 2.0 - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `phoenix-charx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/lambda-eu-l-series.mdx b/docs/devices-next/chargers/lambda-eu-l-series.mdx index 86d580ab45..741941cd6e 100644 --- a/docs/devices-next/chargers/lambda-eu-l-series.mdx +++ b/docs/devices-next/chargers/lambda-eu-l-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Lambda EU-L Series - +
+
+ Energy management settings of the device: @@ -31,7 +34,18 @@ Energy management settings of the device: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `lambda-zewotherm` @@ -39,5 +53,5 @@ Energy management settings of the device: |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Temperature source
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/chargers/lrt-home-essentialplus.mdx b/docs/devices-next/chargers/lrt-home-essentialplus.mdx index b7ff0a40a1..df3416d7e0 100644 --- a/docs/devices-next/chargers/lrt-home-essentialplus.mdx +++ b/docs/devices-next/chargers/lrt-home-essentialplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LRT HOME Essential+ - +
+
+ The motherboard requires current firmware. You can recognize a current software version by the fact that the serial number on the brown relay starts with 2022 or there is a 15 on the small white relays. Otherwise, please contact the manufacturer directly. @@ -34,12 +37,23 @@ The motherboard requires current firmware. You can recognize a current software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `alphatec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/mennekes-amedio-professional.mdx b/docs/devices-next/chargers/mennekes-amedio-professional.mdx index 3c01c8cc61..f9652a542c 100644 --- a/docs/devices-next/chargers/mennekes-amedio-professional.mdx +++ b/docs/devices-next/chargers/mennekes-amedio-professional.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMEDIO Professional - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx index 42bb1cd509..51d250b7d3 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON 4Business 700 - +
+
+ The configuration option 'External Energy Management' must be enabled. @@ -27,12 +30,23 @@ The configuration option 'External Energy Management' must be enabled. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-icc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx index 337b9b178a..d918d6a2da 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON 4You 300 - +
+
+ The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. @@ -36,12 +39,23 @@ For Kostal systems with Smart Energy Meter (KSEM), the additional activation cod id: 50 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `mennekes-compact` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx index d579ab3404..81b880263b 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON 4You 500 - +
+
+ The configuration option 'External Energy Management' must be enabled. @@ -27,12 +30,23 @@ The configuration option 'External Energy Management' must be enabled. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-icc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx index f0debd43d4..b3e4735b28 100644 --- a/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON ChargeControl - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx b/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx index 7531ae7980..bab95a3195 100644 --- a/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Compact 2.0s - +
+
+ The wallbox must be configured as satellite/slave using the DIP switches on the mainboard and Modbus RTU must be enabled (bank S1: 4=ON, 5=ON, 7=OFF). No external meter should be connected directly to the wallbox, as all functions are controlled directly by evcc. @@ -36,12 +39,23 @@ For Kostal systems with Smart Energy Meter (KSEM), the additional activation cod id: 50 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `mennekes-compact` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-premium.mdx b/docs/devices-next/chargers/mennekes-amtron-premium.mdx index 3f27a943ff..3d950381dc 100644 --- a/docs/devices-next/chargers/mennekes-amtron-premium.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-premium.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Premium - +
+
+ +
+
+ +
+
## Template Parameter `mennekes-hcc3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-professional.mdx b/docs/devices-next/chargers/mennekes-amtron-professional.mdx index 93eea7fd21..32f55b4d06 100644 --- a/docs/devices-next/chargers/mennekes-amtron-professional.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-professional.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Professional - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/mennekes-amtron-xtra.mdx b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx index 2695c36cac..f54e8d70ed 100644 --- a/docs/devices-next/chargers/mennekes-amtron-xtra.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Xtra - +
+
+ +
+
+ +
+
## Template Parameter `mennekes-hcc3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx index 0fa4fc1472..97353d26d1 100644 --- a/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx +++ b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes eMobility Gateway (ACU) - +
+
+ To configure, open the web interface of the ACU. Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J @@ -23,29 +26,40 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-mennekes-acu` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/mennekes-smart-acu.mdx b/docs/devices-next/chargers/mennekes-smart-acu.mdx index 5349be7c8b..869f246263 100644 --- a/docs/devices-next/chargers/mennekes-smart-acu.mdx +++ b/docs/devices-next/chargers/mennekes-smart-acu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes Smart (ACU) - +
+
+ To configure, open the web interface of the ACU. Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J @@ -23,29 +26,40 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-mennekes-acu` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/mennekes-smart-t-acu.mdx b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx index 9553f2e51a..ada58add4c 100644 --- a/docs/devices-next/chargers/mennekes-smart-t-acu.mdx +++ b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes Smart T (ACU) - +
+
+ To configure, open the web interface of the ACU. Setup, Backend, Communication Protocol: Open Charge Point Protocol v1.6J @@ -23,29 +26,40 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-mennekes-acu` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx index 20463e5162..36e25847b6 100644 --- a/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx +++ b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC ELWA 2 - +
+
+ +
+
+ +
+
## Template Parameter `ac-elwa-2` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Scale factor for power limit
`scale` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx b/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx index fda3b9d4cd..b4f7193412 100644 --- a/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx +++ b/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC•THOR 9s - +
+
+ +
+
+ +
+
## Template Parameter `ac-thor` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Temperature sensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Temperature source
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | no | | Scale factor for power limit
`scale` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/my-pv-ac-thor.mdx b/docs/devices-next/chargers/my-pv-ac-thor.mdx index ef1549b477..fdf8e2f1f4 100644 --- a/docs/devices-next/chargers/my-pv-ac-thor.mdx +++ b/docs/devices-next/chargers/my-pv-ac-thor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC•THOR - +
+
+ +
+
+ +
+
## Template Parameter `ac-thor` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Temperature sensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Temperature source
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | no | | Scale factor for power limit
`scale` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/mystrom-switch.mdx b/docs/devices-next/chargers/mystrom-switch.mdx index 0f359e1b0b..782699fbfe 100644 --- a/docs/devices-next/chargers/mystrom-switch.mdx +++ b/docs/devices-next/chargers/mystrom-switch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # myStrom Switch - +
+
+ +
+
+ +
+
## Template Parameter `mystrom` diff --git a/docs/devices-next/chargers/nibe-ap-aw10.mdx b/docs/devices-next/chargers/nibe-ap-aw10.mdx index 58d7aa1bf9..84ef9a7d71 100644 --- a/docs/devices-next/chargers/nibe-ap-aw10.mdx +++ b/docs/devices-next/chargers/nibe-ap-aw10.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nibe AP-AW10 - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/novelan-wpr-net.mdx b/docs/devices-next/chargers/novelan-wpr-net.mdx index be343aa505..0df911d277 100644 --- a/docs/devices-next/chargers/novelan-wpr-net.mdx +++ b/docs/devices-next/chargers/novelan-wpr-net.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Novelan WPR NET - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/nrgkick-connect.mdx b/docs/devices-next/chargers/nrgkick-connect.mdx index 5c9e0bd02b..1e03bf5c57 100644 --- a/docs/devices-next/chargers/nrgkick-connect.mdx +++ b/docs/devices-next/chargers/nrgkick-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # NRGkick Connect - +
+
+ NRGkick charging unit via HTTP (older than 2022/2023) @@ -22,14 +25,25 @@ NRGkick charging unit via HTTP (older than 2022/2023) type: template template: nrgkick-connect host: 192.0.2.2 # IP address or hostname - mac: + mac: # MAC Address password: # Password, Use single quotes in case of leading zeros`} /> +
+
+ +
+
## Template Parameter `nrgkick-connect` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| `mac` | | | yes | +| MAC Address
`mac` | | | yes | | Password
`password` | Use single quotes in case of leading zeros | | yes | diff --git a/docs/devices-next/chargers/nrgkick-gen2.mdx b/docs/devices-next/chargers/nrgkick-gen2.mdx index a006a6f774..c1502b44c8 100644 --- a/docs/devices-next/chargers/nrgkick-gen2.mdx +++ b/docs/devices-next/chargers/nrgkick-gen2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # NRGkick Gen2 - +
+
+ + phases1p3p: false # Phase Switching enabled, Extended feature "Phase Switching" must be activated in the NRGKick app. (optional)`} /> +
+
+ +
+
## Template Parameter `nrggen2` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `phases1p3p` | Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. | | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Phase Switching enabled
`phases1p3p` | Extended feature "Phase Switching" must be activated in the NRGKick app. | | no | diff --git a/docs/devices-next/chargers/obo-bettermann-ion.mdx b/docs/devices-next/chargers/obo-bettermann-ion.mdx index 94b4125a6e..d0f6acbea3 100644 --- a/docs/devices-next/chargers/obo-bettermann-ion.mdx +++ b/docs/devices-next/chargers/obo-bettermann-ion.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OBO Bettermann Ion - +
+
+ +
+
+ +
+
## Template Parameter `obo` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx b/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx index c1e2561f29..420d8f8650 100644 --- a/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx +++ b/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OCPP 1.6J compatible (Smart Charging) - +
+
+ With OCPP the connection will be established from charger (client) to evcc (server). The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. @@ -39,29 +42,40 @@ The specific configuration and the actual usable functionality depend on the cha - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/openevse.mdx b/docs/devices-next/chargers/openevse.mdx index 8cba61c922..59c8306e53 100644 --- a/docs/devices-next/chargers/openevse.mdx +++ b/docs/devices-next/chargers/openevse.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OpenEVSE - +
+
+ Requires firmware 7.0 or later. @@ -24,6 +27,17 @@ Requires firmware 7.0 or later. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +
+
+ +
+
## Template Parameter `openevse` diff --git a/docs/devices-next/chargers/openwb-pro.mdx b/docs/devices-next/chargers/openwb-pro.mdx index 1633e1facc..3cdb09701b 100644 --- a/docs/devices-next/chargers/openwb-pro.mdx +++ b/docs/devices-next/chargers/openwb-pro.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # openWB Pro - +
+
+ +
+
+ +
+
## Template Parameter `openwb-pro` diff --git a/docs/devices-next/chargers/openwb-series2.mdx b/docs/devices-next/chargers/openwb-series2.mdx index 4a401ef868..4e13e80c45 100644 --- a/docs/devices-next/chargers/openwb-series2.mdx +++ b/docs/devices-next/chargers/openwb-series2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # openWB series2 - +
+
+ The wallbox has to be configured as loadpoint. @@ -28,12 +31,23 @@ The wallbox has to be configured as loadpoint. host: 192.0.2.2 # IP address or hostname connector: 1 # Loadpoint (if >1 loadpoint), optional phases1p3p: false # Charger is equipped with phase switching feature, optional`} /> +
+
+ +
+
## Template Parameter `openwb` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | | Charger is equipped with phase switching feature
`phases1p3p` | | | no | diff --git a/docs/devices-next/chargers/openwb-software-2-x.mdx b/docs/devices-next/chargers/openwb-software-2-x.mdx index 96fc608fc6..158c874d1a 100644 --- a/docs/devices-next/chargers/openwb-software-2-x.mdx +++ b/docs/devices-next/chargers/openwb-software-2-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # openWB Software 2.x - +
+
+ Requires [`Software 2.x`](https://github.com/openWB/core). The following changes are necessary under the 'Einstellungen' tab: @@ -42,12 +45,23 @@ The following changes are necessary under the 'Einstellungen' tab: port: 1502 # Port connector: 1 # Loadpoint (if >1 loadpoint), optional phases1p3p: true # Charger is equipped with phase switching feature, optional`} /> +
+
+ +
+
## Template Parameter `openwb-2.0` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | | Charger is equipped with phase switching feature
`phases1p3p` | | Standard: `true` | no | diff --git a/docs/devices-next/chargers/optec-mobility-one.mdx b/docs/devices-next/chargers/optec-mobility-one.mdx index e93b74cb48..0dba6ee631 100644 --- a/docs/devices-next/chargers/optec-mobility-one.mdx +++ b/docs/devices-next/chargers/optec-mobility-one.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Optec Mobility One - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/orbis-viaris.mdx b/docs/devices-next/chargers/orbis-viaris.mdx index ba234cff82..0edacc846f 100644 --- a/docs/devices-next/chargers/orbis-viaris.mdx +++ b/docs/devices-next/chargers/orbis-viaris.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Orbis Viaris - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-orbis` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/pc-electric-garo.mdx b/docs/devices-next/chargers/pc-electric-garo.mdx index ea51373233..d014eca50a 100644 --- a/docs/devices-next/chargers/pc-electric-garo.mdx +++ b/docs/devices-next/chargers/pc-electric-garo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # PC Electric Garo - +
+
+ Only devices configured as master can be used right now! @@ -23,6 +26,17 @@ Only devices configured as master can be used right now! template: pcelectric-garo host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional`} /> +
+
+ +
+
## Template Parameter `pcelectric-garo` diff --git a/docs/devices-next/chargers/peblar-business.mdx b/docs/devices-next/chargers/peblar-business.mdx index b12a8b61f7..b9f227d1d3 100644 --- a/docs/devices-next/chargers/peblar-business.mdx +++ b/docs/devices-next/chargers/peblar-business.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peblar Business - +
+
+ Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. @@ -27,12 +30,23 @@ Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via por id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `peblar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/peblar-home-plus.mdx b/docs/devices-next/chargers/peblar-home-plus.mdx index 44a1deefdf..f424afe937 100644 --- a/docs/devices-next/chargers/peblar-home-plus.mdx +++ b/docs/devices-next/chargers/peblar-home-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peblar Home Plus - +
+
+ Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. @@ -27,12 +30,23 @@ Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via por id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `peblar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/peblar-home.mdx b/docs/devices-next/chargers/peblar-home.mdx index 1f4c00fdac..0c6daddb66 100644 --- a/docs/devices-next/chargers/peblar-home.mdx +++ b/docs/devices-next/chargers/peblar-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peblar Home - +
+
+ Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via port 502. The Modbus server needs to be enabled via the charger web interface. Ensure that smart charging strategies are disabled and set to Default. @@ -27,12 +30,23 @@ Peblar chargers with firmware version 1.6 and onwards support Modbus TCP via por id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `peblar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/phoenix-contact-charx.mdx b/docs/devices-next/chargers/phoenix-contact-charx.mdx index 540bdbbfb5..d8642a8bf0 100644 --- a/docs/devices-next/chargers/phoenix-contact-charx.mdx +++ b/docs/devices-next/chargers/phoenix-contact-charx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact CHARX - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `phoenix-charx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx index c9b0136e3a..66165fc6bb 100644 --- a/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx +++ b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EM-CP-PP-ETH - +
+
+ +
+
+ +
+
## Template Parameter `phoenix-em-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx index fefd5bfe6b..899023e13b 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx index c64e9450a1..67613f0437 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx index e2415ae806..974be4f994 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx index 8e87a768c9..80722e8e24 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx index aa935bdc46..511d1fd0e2 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-SER - +
+
+ +
+
+ +
+
## Template Parameter `phoenix-ev-ser` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/plugchoice.mdx b/docs/devices-next/chargers/plugchoice.mdx index 78bdbe5c6e..079781b064 100644 --- a/docs/devices-next/chargers/plugchoice.mdx +++ b/docs/devices-next/chargers/plugchoice.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Plugchoice - +
+
+ Chargers connected through Plugchoice can leverage its OCPP proxy functionality to establish a connection to other backoffices while maintaining full control through EVCC. This allows seamless management of Plugchoice-registered chargers directly from EVCC. @@ -28,22 +31,33 @@ These adjustments enable more frequent and detailed reporting of charging data t - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456)`} advanced={`chargers: + token: # Token, API Token + identity: AA123456 # Charger identity`} advanced={`chargers: - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456) - connector: 1 # Loadpoint (if >1 loadpoint), Connector ID (usually 1)`} /> + token: # Token, API Token + identity: AA123456 # Charger identity + connector: 1 # Connector ID`} /> +
+
+ +
+
## Template Parameter `plugchoice` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | API Token | | yes | -| `identity` | Charger identity (e.g. AA123456) | | yes | -| Loadpoint (if >1 loadpoint)
`connector` | Connector ID (usually 1) | Standard: `1` | yes | +| Token
`token` | API Token | | yes | +| Charger identity
`identity` | | Beispiel: `AA123456` | yes | +| Connector ID
`connector` | | Standard: `1`
Beispiel: `1` | yes | diff --git a/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx index 874a1ac216..681d0ec47a 100644 --- a/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx +++ b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Porsche Mobile Charger Connect - +
+
+ +
+
+ +
+
## Template Parameter `pmcc` diff --git a/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx index e5eb32f4fb..c892a96ae9 100644 --- a/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx +++ b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Porsche Mobile Charger Plus - +
+
+ +
+
+ +
+
## Template Parameter `pmcp` diff --git a/docs/devices-next/chargers/porsche-wallbox.mdx b/docs/devices-next/chargers/porsche-wallbox.mdx index f396beb7e3..925f0a56bb 100644 --- a/docs/devices-next/chargers/porsche-wallbox.mdx +++ b/docs/devices-next/chargers/porsche-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Porsche Wallbox - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: porsche-wallbox ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `porsche-wallbox` diff --git a/docs/devices-next/chargers/pracht-alpha-xt.mdx b/docs/devices-next/chargers/pracht-alpha-xt.mdx index 6479adc4b9..b2c812290d 100644 --- a/docs/devices-next/chargers/pracht-alpha-xt.mdx +++ b/docs/devices-next/chargers/pracht-alpha-xt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht Alpha XT - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `pracht-alpha` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/pracht-mono-xt.mdx b/docs/devices-next/chargers/pracht-mono-xt.mdx index 72728fef30..96a4281876 100644 --- a/docs/devices-next/chargers/pracht-mono-xt.mdx +++ b/docs/devices-next/chargers/pracht-mono-xt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht Mono XT - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `pracht-alpha` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/pracht-pni.mdx b/docs/devices-next/chargers/pracht-pni.mdx index 2703128f98..3cd2e02e45 100644 --- a/docs/devices-next/chargers/pracht-pni.mdx +++ b/docs/devices-next/chargers/pracht-pni.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht PNI - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `pracht-alpha` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/pracht-xtplus.mdx b/docs/devices-next/chargers/pracht-xtplus.mdx index 956cface67..56ffe7520a 100644 --- a/docs/devices-next/chargers/pracht-xtplus.mdx +++ b/docs/devices-next/chargers/pracht-xtplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht XT+ - +
+
+ 1 loadpoint), optional`} /> +
+
+ +
+
## Template Parameter `pracht-alpha` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | -| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | +| Loadpoint (if >1 loadpoint)
`connector` | | Standard: `1` | no | diff --git a/docs/devices-next/chargers/pulsares-simplebox.mdx b/docs/devices-next/chargers/pulsares-simplebox.mdx index c06824dfac..acc0357ae4 100644 --- a/docs/devices-next/chargers/pulsares-simplebox.mdx +++ b/docs/devices-next/chargers/pulsares-simplebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pulsares SimpleBox - +
+
+ +
+
+ +
+
## Template Parameter `pulsares` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/pulsatrix.mdx b/docs/devices-next/chargers/pulsatrix.mdx index 752e2dbe98..0009e7d965 100644 --- a/docs/devices-next/chargers/pulsatrix.mdx +++ b/docs/devices-next/chargers/pulsatrix.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pulsatrix - +
+
+ +
+
+ +
+
## Template Parameter `pulsatrix` diff --git a/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx b/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx index 6e407efb07..b468bcfa31 100644 --- a/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx +++ b/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Qcells Q.HOME EDRIVE A - +
+
+ The charger must be in “Fast” mode and decoupled from the inverter system. @@ -34,12 +37,23 @@ The charger must be in “Fast” mode and decoupled from the inverter system. id: 70 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `solax` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/roth-thermoaura.mdx b/docs/devices-next/chargers/roth-thermoaura.mdx index 964f80de3d..1b9596c38d 100644 --- a/docs/devices-next/chargers/roth-thermoaura.mdx +++ b/docs/devices-next/chargers/roth-thermoaura.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Roth ThermoAura - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/roth-thermoterra.mdx b/docs/devices-next/chargers/roth-thermoterra.mdx index c7c060d312..8775bec4ff 100644 --- a/docs/devices-next/chargers/roth-thermoterra.mdx +++ b/docs/devices-next/chargers/roth-thermoterra.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Roth ThermoTerra - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/schneider-evlink-pro.mdx b/docs/devices-next/chargers/schneider-evlink-pro.mdx index 86dcff93b8..40413cca72 100644 --- a/docs/devices-next/chargers/schneider-evlink-pro.mdx +++ b/docs/devices-next/chargers/schneider-evlink-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Schneider EVlink Pro - +
+
+ +
+
+ +
+
## Template Parameter `schneider-evlink-v3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/schrack-i-charge-cion.mdx b/docs/devices-next/chargers/schrack-i-charge-cion.mdx index cbde9b5903..1c2c1819b7 100644 --- a/docs/devices-next/chargers/schrack-i-charge-cion.mdx +++ b/docs/devices-next/chargers/schrack-i-charge-cion.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Schrack i-CHARGE CION - +
+
+ +
+
+ +
+
## Template Parameter `ichargecion` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/senec-wallbox-pro-s.mdx b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx index 4b05c78413..ae101d0e1f 100644 --- a/docs/devices-next/chargers/senec-wallbox-pro-s.mdx +++ b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SENEC Wallbox pro s - +
+
+ Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). @@ -34,12 +37,23 @@ Please read the wiring and configuration manual carefully. All boxes must be con id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `heidelberg` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/senec-wallbox-pro.mdx b/docs/devices-next/chargers/senec-wallbox-pro.mdx index 670a84ffef..407f763caf 100644 --- a/docs/devices-next/chargers/senec-wallbox-pro.mdx +++ b/docs/devices-next/chargers/senec-wallbox-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SENEC Wallbox pro - +
+
+ +
+
+ +
+
## Template Parameter `abl` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | diff --git a/docs/devices-next/chargers/shelly-1.mdx b/docs/devices-next/chargers/shelly-1.mdx index b8d8027117..5d073869b9 100644 --- a/docs/devices-next/chargers/shelly-1.mdx +++ b/docs/devices-next/chargers/shelly-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 1 - +
+
+ +
+
+ +
+
## Template Parameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | | Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | | Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | | Heating device
`heating` | Shows °C instead of % | | no | diff --git a/docs/devices-next/chargers/shelly-plug-s.mdx b/docs/devices-next/chargers/shelly-plug-s.mdx index 4dbd9ac452..05e35d074a 100644 --- a/docs/devices-next/chargers/shelly-plug-s.mdx +++ b/docs/devices-next/chargers/shelly-plug-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Plug S - +
+
+ +
+
+ +
+
## Template Parameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | | Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | | Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | | Heating device
`heating` | Shows °C instead of % | | no | diff --git a/docs/devices-next/chargers/shelly-plus-1.mdx b/docs/devices-next/chargers/shelly-plus-1.mdx index 1dbbf6b80e..bc88d47635 100644 --- a/docs/devices-next/chargers/shelly-plus-1.mdx +++ b/docs/devices-next/chargers/shelly-plus-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Plus 1 - +
+
+ +
+
+ +
+
## Template Parameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | | Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | | Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | | Heating device
`heating` | Shows °C instead of % | | no | diff --git a/docs/devices-next/chargers/shelly-pro-1.mdx b/docs/devices-next/chargers/shelly-pro-1.mdx index 36b39b7aa5..5c9647949b 100644 --- a/docs/devices-next/chargers/shelly-pro-1.mdx +++ b/docs/devices-next/chargers/shelly-pro-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 1 - +
+
+ +
+
+ +
+
## Template Parameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | | Standby power
`standbypower` | Power values above this value will be considered as charging power | Standard: `15`
Einheit: W | no | | Integrated device
`integrateddevice` | Integrated device. No charging sessions | | no | | Heating device
`heating` | Shows °C instead of % | | no | diff --git a/docs/devices-next/chargers/siemens-versicharge-gen3.mdx b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx index b7b16215ac..64134b9b6b 100644 --- a/docs/devices-next/chargers/siemens-versicharge-gen3.mdx +++ b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens Versicharge GEN3 - +
+
+ Requires firmware >= 2.135 @@ -27,12 +30,23 @@ Requires firmware >= 2.135 id: 2 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `versicharge` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/skoda-charger-connect.mdx b/docs/devices-next/chargers/skoda-charger-connect.mdx index 4119e22ae4..915340ab81 100644 --- a/docs/devices-next/chargers/skoda-charger-connect.mdx +++ b/docs/devices-next/chargers/skoda-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Charger Connect - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx index bdf917be2b..7b31c2212a 100644 --- a/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx +++ b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Charger Pro Eichrecht - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/skoda-charger-pro.mdx b/docs/devices-next/chargers/skoda-charger-pro.mdx index ddae605919..61afd2d35b 100644 --- a/docs/devices-next/chargers/skoda-charger-pro.mdx +++ b/docs/devices-next/chargers/skoda-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Charger Pro - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/skoda-iv-charger-connect.mdx b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx index 18c2ab9e42..f27ffcaed7 100644 --- a/docs/devices-next/chargers/skoda-iv-charger-connect.mdx +++ b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda iV Charger Connect - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -29,6 +32,17 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn template: elliconnect ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elliconnect` diff --git a/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx b/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx index 6af9218dc1..fb0d284362 100644 --- a/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx +++ b/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda iV Charger Connect+ - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -27,6 +30,17 @@ Important: A mostly flawless functionality can only be provided with an external template: ellipro ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `ellipro` diff --git a/docs/devices-next/chargers/sma-echarger.mdx b/docs/devices-next/chargers/sma-echarger.mdx index 249e77a6ac..60e0b27ca3 100644 --- a/docs/devices-next/chargers/sma-echarger.mdx +++ b/docs/devices-next/chargers/sma-echarger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA eCharger - +
+
+ The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. @@ -24,6 +27,17 @@ The charger must be switched to "Fast" charging mode and the user must have "Adm host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros`} /> +
+
+ +
+
## Template Parameter `smaevcharger` diff --git a/docs/devices-next/chargers/sma-ev-charger.mdx b/docs/devices-next/chargers/sma-ev-charger.mdx index 7e73d7c81c..4ce9787aa4 100644 --- a/docs/devices-next/chargers/sma-ev-charger.mdx +++ b/docs/devices-next/chargers/sma-ev-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA EV Charger - +
+
+ The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights. @@ -24,6 +27,17 @@ The charger must be switched to "Fast" charging mode and the user must have "Adm host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros`} /> +
+
+ +
+
## Template Parameter `smaevcharger` diff --git a/docs/devices-next/chargers/smartfox-pro-charger.mdx b/docs/devices-next/chargers/smartfox-pro-charger.mdx index d2864b80aa..393fddf830 100644 --- a/docs/devices-next/chargers/smartfox-pro-charger.mdx +++ b/docs/devices-next/chargers/smartfox-pro-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro Charger - +
+
+ +
+
+ +
+
## Template Parameter `ichargecion` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/smartwb.mdx b/docs/devices-next/chargers/smartwb.mdx index f051492112..9a428cc30c 100644 --- a/docs/devices-next/chargers/smartwb.mdx +++ b/docs/devices-next/chargers/smartwb.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # smartWB - +
+
+ +
+
+ +
+
## Template Parameter `smartwb` diff --git a/docs/devices-next/chargers/solaredge-home-ev-charger.mdx b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx index 82d20c8754..f463826deb 100644 --- a/docs/devices-next/chargers/solaredge-home-ev-charger.mdx +++ b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarEdge Home EV Charger - +
+
+ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required and the switching control via Modbus must be set in the wallbox settings. For the X-series in the web menu, for the C-series via Modbus by setting the value "3" in register 5050. @@ -37,12 +40,23 @@ Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase swi host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)`} /> +
+
+ +
+
## Template Parameter `keba-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Charge on connection
`welcomecharge` | Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. | | no | diff --git a/docs/devices-next/chargers/solax-x3-evc.mdx b/docs/devices-next/chargers/solax-x3-evc.mdx index ef85206983..a860c57922 100644 --- a/docs/devices-next/chargers/solax-x3-evc.mdx +++ b/docs/devices-next/chargers/solax-x3-evc.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax X3-EVC - +
+
+ The charger must be in “Fast” mode and decoupled from the inverter system. @@ -34,12 +37,23 @@ The charger must be in “Fast” mode and decoupled from the inverter system. id: 70 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `solax` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/sonnen-sonnencharger.mdx b/docs/devices-next/chargers/sonnen-sonnencharger.mdx index a9038918fc..17ed87e054 100644 --- a/docs/devices-next/chargers/sonnen-sonnencharger.mdx +++ b/docs/devices-next/chargers/sonnen-sonnencharger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen sonnenCharger - +
+
+ The charger must be switched to "Power" charging mode. @@ -23,6 +26,17 @@ The charger must be switched to "Power" charging mode. template: etrel host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Template Parameter `etrel` diff --git a/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx index 13fe2decb9..3b3ffde47c 100644 --- a/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx +++ b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Spelsberg Wallbox Smart Pro - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/stark-in-strom-easy.mdx b/docs/devices-next/chargers/stark-in-strom-easy.mdx index 6cd3e22a5d..e9023e2c65 100644 --- a/docs/devices-next/chargers/stark-in-strom-easy.mdx +++ b/docs/devices-next/chargers/stark-in-strom-easy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Stark in Strom Easy - +
+
+ +
+
+ +
+
## Template Parameter `evse-din` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx index 8761319b97..13c5adc519 100644 --- a/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx +++ b/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Stiebel Eltron LWA/LWZ (SG Ready) - +
+
+ +
+
+ +
+
## Template Parameter `stiebel-lwa` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater` | no | diff --git a/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx index 0d8f5f661c..0c9d2497e0 100644 --- a/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx +++ b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Stiebel Eltron WPM (SG Ready) - +
+
+ +
+
+ +
+
## Template Parameter `stiebel-wpm` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater`, `buffer` | no | diff --git a/docs/devices-next/chargers/sungrow-ac011e-01.mdx b/docs/devices-next/chargers/sungrow-ac011e-01.mdx index 09b1864d0c..bfb2fa3c7d 100644 --- a/docs/devices-next/chargers/sungrow-ac011e-01.mdx +++ b/docs/devices-next/chargers/sungrow-ac011e-01.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow AC011E-01 - +
+
+ +
+
+ +
+
## Template Parameter `sungrow` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/chargers/sungrow-ac011e.mdx b/docs/devices-next/chargers/sungrow-ac011e.mdx index c3e9313490..42cc2284bb 100644 --- a/docs/devices-next/chargers/sungrow-ac011e.mdx +++ b/docs/devices-next/chargers/sungrow-ac011e.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow AC011E - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-sungrow` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/sungrow-ac22e-01.mdx b/docs/devices-next/chargers/sungrow-ac22e-01.mdx index 1887815f9f..4ac74b61d6 100644 --- a/docs/devices-next/chargers/sungrow-ac22e-01.mdx +++ b/docs/devices-next/chargers/sungrow-ac22e-01.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow AC22E-01 - +
+
+ +
+
+ +
+
## Template Parameter `sungrow` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/chargers/tasmota-single-phase.mdx b/docs/devices-next/chargers/tasmota-single-phase.mdx index 8728520c3d..e28dafcdc4 100644 --- a/docs/devices-next/chargers/tasmota-single-phase.mdx +++ b/docs/devices-next/chargers/tasmota-single-phase.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota single phase - +
+
+ +
+
+ +
+
## Template Parameter `tasmota` diff --git a/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx index e994a0ac5f..bb47bc9436 100644 --- a/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx +++ b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tecalor THZ (SG Ready) - +
+
+ +
+
+ +
+
## Template Parameter `stiebel-lwa` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Temperature source
`tempsource` | | Auswahl: `warmwater` | no | diff --git a/docs/devices-next/chargers/technisat-technivolt.mdx b/docs/devices-next/chargers/technisat-technivolt.mdx index 8d3c8b09a5..9039ec9e59 100644 --- a/docs/devices-next/chargers/technisat-technivolt.mdx +++ b/docs/devices-next/chargers/technisat-technivolt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TechniSat Technivolt - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx b/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx index 531694529f..ab90caf96a 100644 --- a/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx +++ b/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla Wall Connector (Gen 3) - +
+
+ The TWC wallbox cannot be controlled directly. Control is via the vehicle. The vehicle must be selected at the TWC3 loadpoint. At this time only [Tesla vehicles](https://docs.evcc.io/en/docs/devices/vehicles#tesla) are supported. @@ -22,6 +25,17 @@ The TWC wallbox cannot be controlled directly. Control is via the vehicle. The v type: template template: twc3 host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `twc3` diff --git a/docs/devices-next/chargers/tessie.mdx b/docs/devices-next/chargers/tessie.mdx index bdb8c5361d..347ca4636f 100644 --- a/docs/devices-next/chargers/tessie.mdx +++ b/docs/devices-next/chargers/tessie.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tessie - +
+
+ Charger connected via the Tessie API. Allows control of charging state and configuration of maximum current. @@ -23,7 +26,18 @@ Charger connected via the Tessie API. Allows control of charging state and confi template: tessie vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer token: # Tessie API Token - location: tessiehome # Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive)`} /> + location: tessiehome # Location, Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive)`} /> +
+
+ +
+
## Template Parameter `tessie` @@ -31,5 +45,5 @@ Charger connected via the Tessie API. Allows control of charging state and confi |-----------|-------------|-------|----------| | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | | Tessie API Token
`token` | | | yes | -| Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive)
`location` | | Beispiel: `tessiehome` | yes | +| Location
`location` | Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) | Beispiel: `tessiehome` | yes | diff --git a/docs/devices-next/chargers/tigo-go-ev-charger.mdx b/docs/devices-next/chargers/tigo-go-ev-charger.mdx index 9aa7e6bce4..c242506442 100644 --- a/docs/devices-next/chargers/tigo-go-ev-charger.mdx +++ b/docs/devices-next/chargers/tigo-go-ev-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tigo GO EV Charger - +
+
+ The charger must be in “Fast” mode and decoupled from the inverter system. @@ -34,12 +37,23 @@ The charger must be in “Fast” mode and decoupled from the inverter system. id: 70 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `solax` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx index b65a191774..c6e355e4b0 100644 --- a/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP Charger Pro - +
+
+ WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. @@ -25,7 +28,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional)`} advanced={`chargers: + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -33,9 +36,20 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +
+
+ +
+
## Template Parameter `tinkerforge-warp` @@ -45,7 +59,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR | Port
`port` | MQTT broker port | Standard: `1883` | no | | Topic
`topic` | Topic (omit leading /) | Standard: `warp` | no | | Timeout
`timeout` | Don't accept values older than this value | Standard: `30s`
Beispiel: `10s` | no | -| `energymanager` | WEM Firmware v2 required. EnergyManager MQTT topic (if installed) | | no | +| Energy manager MQTT topic
`energymanager` | WEM Firmware v2 required. | | no | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx index c3e6b6552b..e19188b079 100644 --- a/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP Charger Smart - +
+
+ WARP Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager. @@ -25,7 +28,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional)`} advanced={`chargers: + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -33,9 +36,20 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +
+
+ +
+
## Template Parameter `tinkerforge-warp` @@ -45,7 +59,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR | Port
`port` | MQTT broker port | Standard: `1883` | no | | Topic
`topic` | Topic (omit leading /) | Standard: `warp` | no | | Timeout
`timeout` | Don't accept values older than this value | Standard: `30s`
Beispiel: `10s` | no | -| `energymanager` | WEM Firmware v2 required. EnergyManager MQTT topic (if installed) | | no | +| Energy manager MQTT topic
`energymanager` | WEM Firmware v2 required. | | no | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx index 66da08e436..edd323e908 100644 --- a/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP3 Charger Pro - +
+
+ The automatic phase switching for 1p vehicles must be deactivated. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. @@ -34,6 +37,17 @@ The automatic phase switching for 1p vehicles must be deactivated. Siehe https:/ timeout: 30s # Timeout, Don't accept values older than this value (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> +
+
+ +
+
## Template Parameter `tinkerforge-warp3` diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx index ef4beccc09..e97839fecd 100644 --- a/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP3 Charger Smart - +
+
+ +
+
+ +
+
## Template Parameter `tinkerforge-warp3-smart` diff --git a/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx index 178a110e5c..30e059f678 100644 --- a/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx +++ b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link H-Series Smart Plug - +
+
+ +
+
+ +
+
## Template Parameter `tplink` diff --git a/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx index 7c0990d4a6..eb0483332e 100644 --- a/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx +++ b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link Tapo P-Series Smart Plug - +
+
+ +
+
+ +
+
## Template Parameter `tapo` diff --git a/docs/devices-next/chargers/ubitricity-heinz.mdx b/docs/devices-next/chargers/ubitricity-heinz.mdx index c3c23230ab..81861d988a 100644 --- a/docs/devices-next/chargers/ubitricity-heinz.mdx +++ b/docs/devices-next/chargers/ubitricity-heinz.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ubitricity Heinz - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/v2c-trydan.mdx b/docs/devices-next/chargers/v2c-trydan.mdx index f0c842d0f5..467fd32db2 100644 --- a/docs/devices-next/chargers/v2c-trydan.mdx +++ b/docs/devices-next/chargers/v2c-trydan.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # V2C Trydan - +
+
+ V2C trydan @@ -22,6 +25,17 @@ V2C trydan type: template template: trydan host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `trydan` diff --git a/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx index 1b8ae11ed4..d750546402 100644 --- a/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx +++ b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Vaillant SensoNET (SG Ready) - +
+
+ The boost function heats hot water or a boost zone. The boost zone is identified by the ID. The boost temperature is specified in degrees Celsius. If boost temperature is specified, the boost zone is activated, otherwise hot water. @@ -23,9 +26,20 @@ The boost function heats hot water or a boost zone. The boost zone is identified template: vaillant user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - realm: DE # [DE, AT] (optional) - zone: # Boost zone id (optional) - setpoint: # Boost temperature setpoint (optional)`} /> + realm: DE # Region, [DE, AT] (optional) + zone: # Boost zone ID, optional + setpoint: # Boost temperature, optional`} /> +
+
+ +
+
## Template Parameter `vaillant` @@ -33,7 +47,7 @@ The boost function heats hot water or a boost zone. The boost zone is identified |-----------|-------------|-------|----------| | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `realm` | | Standard: `DE`
Auswahl: `DE`, `AT` | no | -| `zone` | Boost zone id | | no | -| `setpoint` | Boost temperature setpoint | | no | +| Region
`realm` | | Standard: `DE`
Auswahl: `DE`, `AT` | no | +| Boost zone ID
`zone` | | | no | +| Boost temperature
`setpoint` | | | no | diff --git a/docs/devices-next/chargers/vestel-connect-plus.mdx b/docs/devices-next/chargers/vestel-connect-plus.mdx index 2f86afc11b..d2a7a2bfd5 100644 --- a/docs/devices-next/chargers/vestel-connect-plus.mdx +++ b/docs/devices-next/chargers/vestel-connect-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Vestel Connect Plus - +
+
+ 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `vestel` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/vestel-evc04-home-smart.mdx b/docs/devices-next/chargers/vestel-evc04-home-smart.mdx index f7ca16c065..fbc2c5472f 100644 --- a/docs/devices-next/chargers/vestel-evc04-home-smart.mdx +++ b/docs/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Vestel EVC04 Home Smart - +
+
+ 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `vestel` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx index f86e595ea2..02a066b0d0 100644 --- a/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx +++ b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EV Charging Station (via GX) - +
+
+ Enter the host of the GX device (not the charger). The charger has to be in manual mode and Modbus has to be configured for ID 100. @@ -27,10 +30,21 @@ Enter the host of the GX device (not the charger). The charger has to be in manu id: 100 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `victron` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/victron-ev-charging-station.mdx b/docs/devices-next/chargers/victron-ev-charging-station.mdx index 9d31dc2db0..97e127c0a4 100644 --- a/docs/devices-next/chargers/victron-ev-charging-station.mdx +++ b/docs/devices-next/chargers/victron-ev-charging-station.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EV Charging Station - +
+
+ Enter the host of the charger (not the GX device) and ensure that the charger is in manual mode. @@ -27,10 +30,21 @@ Enter the host of the charger (not the GX device) and ensure that the charger is id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `victron-evcs` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx index 63988debb1..d03acd4453 100644 --- a/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx +++ b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Viessmann Heatpump (SG Ready) - +
+
+ One-time hot water preparation to a configurable target temperature. The device automatically decides whether to use the heat pump or the auxiliary electric heater (if available). @@ -28,6 +31,17 @@ One-time hot water preparation to a configurable target temperature. The device installation_id: # Installation ID, Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...
Prerequisites: curl, jq, and the following parameters: \`\`\` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= \`\`\` Then execute the following to get an oauth token (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): \`\`\` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\\?code=\\(.*\\).*/\\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) \`\`\` Finally, get the installation id: \`\`\` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' \`\`\` device_id: 0 # Device ID, typically \`0\` target_temperature: 45 # Target temperature for one-time charge (°C), max. 60°C`} /> +
+
+ +
+
## Template Parameter `viessmann` @@ -36,8 +50,8 @@ One-time hot water preparation to a configurable target temperature. The device | Username
`user` | Register at \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | yes | | Password
`password` | For the configured Viessmann account. | | yes | | Client ID
`clientid` | Configure at \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | yes | -| Gateway Serial
`gateway_serial` | VitoConnect serial number (VitoCare App -> Settings -> Communication module -> Serial number) | | yes | -| Installation ID
`installation_id` | Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...<br/> Prerequisites: curl, jq, and the following parameters: ``` VIESSMANN_USER=<your-user> VIESSMANN_PASS=<your-password> VIESSMANN_CLIENT_ID=<your-clientid> ``` Then execute the following to get an oauth token (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ \| grep "^location: " \ \| sed 's/.*\?code=\(.*\).*/\1/' \ \| tr -d '\[:space:\]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE \| jq --raw-output .access_token) ``` Finally, get the installation id: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ \| jq '.data\[\].id' ``` | | yes | +| Gateway Serial
`gateway_serial` | VitoConnect serial number (VitoCare App -> Settings -> Communication module -> Serial number) | | yes | +| Installation ID
`installation_id` | Unfortunately you cannot simply lookup this number in the Viessmann app - instead you need to use the following commands on the command line... we're aware this is not for every user, but currently we don't have a better workflow...
Prerequisites: curl, jq, and the following parameters: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Then execute the following to get an oauth token (n.b. it's best to paste the entire block as-is, since the intermediate 'CODE' is only valid for 20 seconds): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ \| grep "^location: " \ \| sed 's/.*\?code=\(.*\).*/\1/' \ \| tr -d '\[:space:\]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE \| jq --raw-output .access_token) ``` Finally, get the installation id: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ \| jq '.data\[\].id' ``` | | yes | | Device ID
`device_id` | typically `0` | | yes | | Target temperature for one-time charge
`target_temperature` | max. 60°C | Standard: `45`
Einheit: °C | yes | diff --git a/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx b/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx index 3048b90aeb..a90ebdfdb3 100644 --- a/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx +++ b/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Viridian EV EVSE EPC 2.0 Plus - +
+
+ +
+
+ +
+
## Template Parameter `obo` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx index 949650ab4f..bb32a8ef04 100644 --- a/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen Charger Connect 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx index 34e11df6a2..cdb67df507 100644 --- a/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen Charger Pro 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx index b7f6f4d36a..e3c86db9d6 100644 --- a/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen Charger Pro Eichrecht 2 - +
+
+ The device has to be used in the normal charging mode. @@ -27,6 +30,17 @@ The identification of a vehicle using the RFID card is not possible. template: elli-2 ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elli-2` diff --git a/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx index e51560f21d..f2eca1b062 100644 --- a/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx +++ b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen ID. Charger Connect - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -29,6 +32,17 @@ Note: If you've added an energy meter to your charger please use the Pro or Conn template: elliconnect ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `elliconnect` diff --git a/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx index 4f8c142913..2e5a20ae0b 100644 --- a/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx +++ b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen ID. Charger Pro - +
+
+ The device has to have a fix IP address (manuall or via DHCP). @@ -27,6 +30,17 @@ Important: A mostly flawless functionality can only be provided with an external template: ellipro ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox ip: 192.0.2.2 # IP address, optional`} /> +
+
+ +
+
## Template Parameter `ellipro` diff --git a/docs/devices-next/chargers/volt-time-one.mdx b/docs/devices-next/chargers/volt-time-one.mdx index c26ebac84f..519b0f9f5d 100644 --- a/docs/devices-next/chargers/volt-time-one.mdx +++ b/docs/devices-next/chargers/volt-time-one.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time One - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> +
+
+ +
+
## Template Parameter `volttime` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | -| `serial_number` | Serial number (e.g. 1008621) | | yes | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| Serial Number
`serial_number` | Serial number (e.g. 1008621) | | yes | diff --git a/docs/devices-next/chargers/volt-time-source-2.mdx b/docs/devices-next/chargers/volt-time-source-2.mdx index a29ea2922a..f20033673e 100644 --- a/docs/devices-next/chargers/volt-time-source-2.mdx +++ b/docs/devices-next/chargers/volt-time-source-2.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time Source 2 - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> +
+
+ +
+
## Template Parameter `volttime` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | -| `serial_number` | Serial number (e.g. 1008621) | | yes | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| Serial Number
`serial_number` | Serial number (e.g. 1008621) | | yes | diff --git a/docs/devices-next/chargers/volt-time-source-2s.mdx b/docs/devices-next/chargers/volt-time-source-2s.mdx index 82d2dc0b1b..9415de0424 100644 --- a/docs/devices-next/chargers/volt-time-source-2s.mdx +++ b/docs/devices-next/chargers/volt-time-source-2s.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time Source 2s - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> +
+
+ +
+
## Template Parameter `volttime` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | -| `serial_number` | Serial number (e.g. 1008621) | | yes | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| Serial Number
`serial_number` | Serial number (e.g. 1008621) | | yes | diff --git a/docs/devices-next/chargers/volt-time-source.mdx b/docs/devices-next/chargers/volt-time-source.mdx index b83e1fa8f9..aebc8ffcf2 100644 --- a/docs/devices-next/chargers/volt-time-source.mdx +++ b/docs/devices-next/chargers/volt-time-source.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time Source - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> +
+
+ +
+
## Template Parameter `volttime` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | -| `serial_number` | Serial number (e.g. 1008621) | | yes | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | yes | +| Serial Number
`serial_number` | Serial number (e.g. 1008621) | | yes | diff --git a/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx b/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx index e3af349fd2..febada156c 100644 --- a/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx +++ b/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wallbe Eco 2.0(s) - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/wallbe-eco.mdx b/docs/devices-next/chargers/wallbe-eco.mdx index 795742e957..2cebd97384 100644 --- a/docs/devices-next/chargers/wallbe-eco.mdx +++ b/docs/devices-next/chargers/wallbe-eco.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wallbe Eco - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/wallbe-pro.mdx b/docs/devices-next/chargers/wallbe-pro.mdx index cdddaeecb1..153aa3976a 100644 --- a/docs/devices-next/chargers/wallbe-pro.mdx +++ b/docs/devices-next/chargers/wallbe-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wallbe Pro - +
+
+ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended. @@ -27,12 +30,23 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `phoenix-ev-eth` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx index 6871f0cbf2..d55e6802cf 100644 --- a/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Commander 2 (FW 5.x) - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `wallbox-fw5` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/wallbox-commander-2.mdx b/docs/devices-next/chargers/wallbox-commander-2.mdx index a451eafb73..d616f97ea4 100644 --- a/docs/devices-next/chargers/wallbox-commander-2.mdx +++ b/docs/devices-next/chargers/wallbox-commander-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Commander 2 - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-wallbox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx index 3bc8561a26..19d12d793a 100644 --- a/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Copper SB (FW 5.x) - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `wallbox-fw5` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/wallbox-copper-sb.mdx b/docs/devices-next/chargers/wallbox-copper-sb.mdx index 954d6c3e53..143b6a2d6b 100644 --- a/docs/devices-next/chargers/wallbox-copper-sb.mdx +++ b/docs/devices-next/chargers/wallbox-copper-sb.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Copper SB - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-wallbox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx index 93ef670c26..ea40329e66 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Max (FW 5.x) - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `wallbox-fw5` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/wallbox-pulsar-max.mdx b/docs/devices-next/chargers/wallbox-pulsar-max.mdx index bda2f8702d..4c43f37793 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-max.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-max.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Max - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-wallbox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx index b7c291c594..f7e9a34936 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Plus (FW 5.x) - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `wallbox-fw5` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx index 19a6590ed2..e29f17bd2d 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-plus.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Plus - +
+
+ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-wallbox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx index 929711dff7..e5bed4d64b 100644 --- a/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx +++ b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Walther Werke Basic Evo Pro - +
+
+ Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2). @@ -34,12 +37,23 @@ Please read the wiring and configuration manual carefully. All boxes must be con id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `heidelberg` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/chargers/webasto-live.mdx b/docs/devices-next/chargers/webasto-live.mdx index fb3f01b17b..57fb6dfd85 100644 --- a/docs/devices-next/chargers/webasto-live.mdx +++ b/docs/devices-next/chargers/webasto-live.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Webasto Live - +
+
+ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On. @@ -27,12 +30,23 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `bender-cc` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/webasto-next.mdx b/docs/devices-next/chargers/webasto-next.mdx index 5f0a909143..44f100a274 100644 --- a/docs/devices-next/chargers/webasto-next.mdx +++ b/docs/devices-next/chargers/webasto-next.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Webasto NEXT - +
+
+ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. @@ -23,6 +26,17 @@ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. template: webasto-next host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Template Parameter `webasto-next` diff --git a/docs/devices-next/chargers/webasto-unite.mdx b/docs/devices-next/chargers/webasto-unite.mdx index 462bcd20cc..f95c127900 100644 --- a/docs/devices-next/chargers/webasto-unite.mdx +++ b/docs/devices-next/chargers/webasto-unite.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Webasto Unite - +
+
+ 1P3P requires at least firmware version 3.187.0, RFID at least 3.156.0. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Template Parameter `vestel` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/chargers/weidmuller-ac-smart.mdx b/docs/devices-next/chargers/weidmuller-ac-smart.mdx index 31e485a5f5..4ee5702aa2 100644 --- a/docs/devices-next/chargers/weidmuller-ac-smart.mdx +++ b/docs/devices-next/chargers/weidmuller-ac-smart.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller AC Smart - +
+
+ +
+
+ +
+
## Template Parameter `weidmüller` diff --git a/docs/devices-next/chargers/wolf-bwl.mdx b/docs/devices-next/chargers/wolf-bwl.mdx index 7f1cef4437..a1b8d02d05 100644 --- a/docs/devices-next/chargers/wolf-bwl.mdx +++ b/docs/devices-next/chargers/wolf-bwl.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wolf BWL - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/wolf-bws.mdx b/docs/devices-next/chargers/wolf-bws.mdx index 8be88939fd..01349f6b10 100644 --- a/docs/devices-next/chargers/wolf-bws.mdx +++ b/docs/devices-next/chargers/wolf-bws.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wolf BWS - +
+
+ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software v3.90.3 or later. Enable via SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> +
+
+ +
+
## Template Parameter `luxtronik` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | -| `heatoffset` | Temperature boost offset for heating. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | -| `wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Heating temperature boost
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | no | +| Hot water temperature boost
`wwoffset` | Temperature boost offset for hot water. Possibly increases wear on compressor. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | no | diff --git a/docs/devices-next/chargers/zaptec-go-2.mdx b/docs/devices-next/chargers/zaptec-go-2.mdx index 6c25f11749..90e6b39ffc 100644 --- a/docs/devices-next/chargers/zaptec-go-2.mdx +++ b/docs/devices-next/chargers/zaptec-go-2.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Go 2 - +
+
+ +
+
+ +
+
## Template Parameter `zaptec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `id` | Charger ID | | no | +| ID
`id` | Charger ID | | no | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | diff --git a/docs/devices-next/chargers/zaptec-go-ocpp.mdx b/docs/devices-next/chargers/zaptec-go-ocpp.mdx index d2b5c818bc..1194d8ac71 100644 --- a/docs/devices-next/chargers/zaptec-go-ocpp.mdx +++ b/docs/devices-next/chargers/zaptec-go-ocpp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Go (OCPP) - +
+
+ OCPP Native mode @@ -23,29 +26,40 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-zaptec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/chargers/zaptec-go.mdx b/docs/devices-next/chargers/zaptec-go.mdx index c8b6798eac..fec735b046 100644 --- a/docs/devices-next/chargers/zaptec-go.mdx +++ b/docs/devices-next/chargers/zaptec-go.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Go - +
+
+ +
+
+ +
+
## Template Parameter `zaptec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `id` | Charger ID | | no | +| ID
`id` | Charger ID | | no | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | diff --git a/docs/devices-next/chargers/zaptec-pro.mdx b/docs/devices-next/chargers/zaptec-pro.mdx index 7d0097e0b2..fb34a57e89 100644 --- a/docs/devices-next/chargers/zaptec-pro.mdx +++ b/docs/devices-next/chargers/zaptec-pro.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Pro - +
+
+ +
+
+ +
+
## Template Parameter `zaptec` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `id` | Charger ID | | no | +| ID
`id` | Charger ID | | no | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | diff --git a/docs/devices-next/chargers/zewotherm-eu-l-series.mdx b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx index 68faeed8b7..296f781e3d 100644 --- a/docs/devices-next/chargers/zewotherm-eu-l-series.mdx +++ b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zewotherm EU-L Series - +
+
+ Energy management settings of the device: @@ -31,7 +34,18 @@ Energy management settings of the device: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `lambda-zewotherm` @@ -39,5 +53,5 @@ Energy management settings of the device: |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Temperature source
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx index e7dff3d3db..1af25fb0a1 100644 --- a/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx +++ b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ZJ Beny BCP EV charger - +
+
+ :8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Template Parameter `ocpp-beny` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | +| Station ID
`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no | | Connector number
`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no | -| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no | -| Identifier used for authentication of external transactions (RemoteStartTransaction)
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no | -| Timeout for the registration of the charging point
`connecttimeout` | | Standard: `5m` | no | -| Transmission interval of meter values (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | no | -| Manual specification of the meter values to be configured (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | +| Start remote transaction on vehicle connection
`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) | | no | +| Authentication token
`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) | Beispiel: `evcc` | no | +| Timeout for registration
`connecttimeout` | Timeout for the registration of the charging point | Standard: `5m` | no | +| Transmission interval for meter values
`meterinterval` | Time interval for transmission of meter values (MeterValueSampleInterval) | Standard: `10s` | no | +| Meter values for transmission
`metervalues` | Manual specification of the meter values to be configured (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no | diff --git a/docs/devices-next/meters/a-tronix.mdx b/docs/devices-next/meters/a-tronix.mdx index 5bd3f06eb6..8368246cad 100644 --- a/docs/devices-next/meters/a-tronix.mdx +++ b/docs/devices-next/meters/a-tronix.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # A-Tronix - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> +
+
+ +
+
## Template Parameter `wattsonic` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `delay` | | Standard: `100ms` | no | +| Delay
`delay` | | Standard: `100ms` | no | diff --git a/docs/devices-next/meters/abb-a43.mdx b/docs/devices-next/meters/abb-a43.mdx index 8420702774..2e8bf17e12 100644 --- a/docs/devices-next/meters/abb-a43.mdx +++ b/docs/devices-next/meters/abb-a43.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB A43 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `abb-ab` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/abb-a44.mdx b/docs/devices-next/meters/abb-a44.mdx index 197c339009..f9db613bf4 100644 --- a/docs/devices-next/meters/abb-a44.mdx +++ b/docs/devices-next/meters/abb-a44.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB A44 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `abb-ab` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/abb-b23.mdx b/docs/devices-next/meters/abb-b23.mdx index 9a91918c24..cb53d42922 100644 --- a/docs/devices-next/meters/abb-b23.mdx +++ b/docs/devices-next/meters/abb-b23.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB B23 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `abb-ab` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/abb-b24.mdx b/docs/devices-next/meters/abb-b24.mdx index c770606b63..50b4245af8 100644 --- a/docs/devices-next/meters/abb-b24.mdx +++ b/docs/devices-next/meters/abb-b24.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB B24 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `abb-ab` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/acrel-adw300.mdx b/docs/devices-next/meters/acrel-adw300.mdx index bfcde75a1f..ac1ce4737f 100644 --- a/docs/devices-next/meters/acrel-adw300.mdx +++ b/docs/devices-next/meters/acrel-adw300.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Acrel ADW300 - +
+
+ @@ -100,10 +103,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `acrel-adw300` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/ads-tec-storaxe.mdx b/docs/devices-next/meters/ads-tec-storaxe.mdx index 0ef2c118ce..2d4d6ea66a 100644 --- a/docs/devices-next/meters/ads-tec-storaxe.mdx +++ b/docs/devices-next/meters/ads-tec-storaxe.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ads-tec StoraXe - +
+
+ +
+
+ +
+
## Template Parameter `storaxe` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/alpha-ess-storion-smile.mdx b/docs/devices-next/meters/alpha-ess-storion-smile.mdx index f41518246f..9ceb8e2480 100644 --- a/docs/devices-next/meters/alpha-ess-storion-smile.mdx +++ b/docs/devices-next/meters/alpha-ess-storion-smile.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alpha ESS Storion SMILE - +
+
+ To use active battery control, times for grid charging must be defined once via the web interface or app. (Settings->Function settings->Grid charging/discharging) A continuous time period should be entered here (e.g.: Charging time 1 00:00-23:00, Charging time 2 23:00-00:00). However, deactivate the "Grid charging" switch. The actual control takes place via evcc. Discharge stop is realized via a scheduled grid charge with a target SoC of 10%. Alternatively, it can also be configured via Modbus. To do this, set the registers `2134,2142,2135,2136,2144,2137,2175` to the values `0,0,23,0,23,0,0,0,0`. @@ -43,32 +46,7 @@ To use active battery control, times for grid charging must be defined once via modbus: tcpip id: 85 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -120,8 +98,6 @@ To use active battery control, times for grid charging must be defined once via id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -180,12 +156,23 @@ To use active battery control, times for grid charging must be defined once via +
+
+ +
+
## Template Parameter `alpha-ess-smile` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/ampere-ampere-storagepro.mdx b/docs/devices-next/meters/ampere-ampere-storagepro.mdx index 326fd880b5..47bdbad243 100644 --- a/docs/devices-next/meters/ampere-ampere-storagepro.mdx +++ b/docs/devices-next/meters/ampere-ampere-storagepro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ampere Ampere.StoragePro - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -93,32 +71,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -177,12 +130,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `saj-h2` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | Standard: `2` | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | diff --git a/docs/devices-next/meters/anker-micro-inverter.mdx b/docs/devices-next/meters/anker-micro-inverter.mdx index 7de7993c55..826fbb4c10 100644 --- a/docs/devices-next/meters/anker-micro-inverter.mdx +++ b/docs/devices-next/meters/anker-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Anker Micro inverter - +
+
+ +
+
+ +
+
## Template Parameter `deye-mi` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/apsystems-ez1.mdx b/docs/devices-next/meters/apsystems-ez1.mdx index b3dca8fe7c..fdb1665080 100644 --- a/docs/devices-next/meters/apsystems-ez1.mdx +++ b/docs/devices-next/meters/apsystems-ez1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # APsystems EZ1 - +
+
+ +
+
+ +
+
## Template Parameter `apsystems-ez1` diff --git a/docs/devices-next/meters/avm-fritzdect.mdx b/docs/devices-next/meters/avm-fritzdect.mdx index faea2b05ea..7ff2791747 100644 --- a/docs/devices-next/meters/avm-fritzdect.mdx +++ b/docs/devices-next/meters/avm-fritzdect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AVM FritzDECT - +
+
+ @@ -42,6 +45,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `fritzdect` diff --git a/docs/devices-next/meters/axitec-axihycon-12-15h.mdx b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx index f5d06f9984..a8f7a3410f 100644 --- a/docs/devices-next/meters/axitec-axihycon-12-15h.mdx +++ b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Axitec AXIhycon 12-15H - +
+
+ @@ -118,12 +121,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solis-hybrid-s` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx index bf3b04f4e7..8d1447c448 100644 --- a/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx +++ b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bernecker Engineering MPM3PM - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `mpm3pm` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/bgetech-ds100.mdx b/docs/devices-next/meters/bgetech-ds100.mdx index 915f965238..af5ad487aa 100644 --- a/docs/devices-next/meters/bgetech-ds100.mdx +++ b/docs/devices-next/meters/bgetech-ds100.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BGEtech DS100 - +
+
+ @@ -128,10 +131,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `bge_tech_ds100` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/bgetech-ws100.mdx b/docs/devices-next/meters/bgetech-ws100.mdx index c5b053f643..d9e1c4c45e 100644 --- a/docs/devices-next/meters/bgetech-ws100.mdx +++ b/docs/devices-next/meters/bgetech-ws100.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BGEtech WS100 - +
+
+ @@ -128,10 +131,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `bge_tech_ws100` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx index 944191f7fa..8fb670c1f8 100644 --- a/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx +++ b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bosch BPT-S 5 Hybrid - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `bosch-bpt` diff --git a/docs/devices-next/meters/bosswerk-micro-inverter.mdx b/docs/devices-next/meters/bosswerk-micro-inverter.mdx index ef2b169802..0cc961fb94 100644 --- a/docs/devices-next/meters/bosswerk-micro-inverter.mdx +++ b/docs/devices-next/meters/bosswerk-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bosswerk Micro inverter - +
+
+ +
+
+ +
+
## Template Parameter `deye-mi` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx b/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx index 7911e5c143..9b63cdb8a6 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM110/111/112 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt1xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/carlo-gavazzi-em24.mdx b/docs/devices-next/meters/carlo-gavazzi-em24.mdx index 8bf71aa3e8..f72b725bf6 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em24.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em24.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM24 - +
+
+ EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. @@ -63,10 +66,21 @@ EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Etherne +
+
+ +
+
## Template Parameter `cg-em24` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx b/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx index db5f10d056..13165e7624 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM24_E1 - +
+
+ EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) @@ -50,10 +53,21 @@ The firmware version should be at least version 1.8.3, you can find this version +
+
+ +
+
## Template Parameter `cg-em24_e1` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx b/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx index f6d870c5c7..a3ae1a4820 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM330/EM340 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt3xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx b/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx index 1a23f424be..f29cdc133a 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM530/EM540 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt3xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/carlo-gavazzi-et112.mdx b/docs/devices-next/meters/carlo-gavazzi-et112.mdx index b8b8a8b4ec..1cdaad8208 100644 --- a/docs/devices-next/meters/carlo-gavazzi-et112.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-et112.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi ET112 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt1xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx b/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx index 561e9670f0..d46f7eaced 100644 --- a/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi ET330/ET340 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt3xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/cfos-powerbrain-meter.mdx b/docs/devices-next/meters/cfos-powerbrain-meter.mdx index 217b040d59..65a89062ac 100644 --- a/docs/devices-next/meters/cfos-powerbrain-meter.mdx +++ b/docs/devices-next/meters/cfos-powerbrain-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # cFos PowerBrain Meter - +
+
+ +
+
+ +
+
## Template Parameter `cfos` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/demo-battery.mdx b/docs/devices-next/meters/demo-battery.mdx index fe3c8928b6..8bbaf95c5d 100644 --- a/docs/devices-next/meters/demo-battery.mdx +++ b/docs/devices-next/meters/demo-battery.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Demo battery - +
+
+ For demonstration purposes. Battery with a fixed set of values. @@ -36,6 +39,17 @@ For demonstration purposes. Battery with a fixed set of values. currentL1: # L1 current (A), optional currentL2: # L2 current (A), optional currentL3: # L3 current (A), optional`} /> +
+
+ +
+
## Template Parameter `demo-battery` diff --git a/docs/devices-next/meters/demo-meter.mdx b/docs/devices-next/meters/demo-meter.mdx index e1ab7b065c..43964be755 100644 --- a/docs/devices-next/meters/demo-meter.mdx +++ b/docs/devices-next/meters/demo-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Demo meter - +
+
+ For demonstration purposes. Meter with a fixed set of values. @@ -95,6 +98,17 @@ For demonstration purposes. Meter with a fixed set of values. +
+
+ +
+
## Template Parameter `demo-meter` diff --git a/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx index 1d1dcc05c6..d43d5b1735 100644 --- a/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye 3p hybrid inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `deye-hybrid-3p` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx index cd614552a9..0b7178e0be 100644 --- a/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye hp3 hybrid inverter - +
+
+ @@ -64,9 +67,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -119,9 +120,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -175,7 +174,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -183,13 +182,24 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `deye-hybrid-hp3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| `storageunit` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery storage unit index
`storageunit` | | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/deye-micro-inverter.mdx b/docs/devices-next/meters/deye-micro-inverter.mdx index 92c6da2bdc..82772666da 100644 --- a/docs/devices-next/meters/deye-micro-inverter.mdx +++ b/docs/devices-next/meters/deye-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye Micro inverter - +
+
+ +
+
+ +
+
## Template Parameter `deye-mi` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx index effd2280e3..1908f23b9c 100644 --- a/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye Storage (hybrid) inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `deye-storage` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/deye-string-inverter.mdx b/docs/devices-next/meters/deye-string-inverter.mdx index 1e7c364a27..910034f2fa 100644 --- a/docs/devices-next/meters/deye-string-inverter.mdx +++ b/docs/devices-next/meters/deye-string-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye String inverter - +
+
+ +
+
+ +
+
## Template Parameter `deye-string` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/discovergy.mdx b/docs/devices-next/meters/discovergy.mdx index bcd47cf323..1029c2a334 100644 --- a/docs/devices-next/meters/discovergy.mdx +++ b/docs/devices-next/meters/discovergy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Discovergy - +
+
+ @@ -24,7 +27,7 @@ import TabItem from '@theme/TabItem'; usage: grid user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Meter ID`} /> @@ -36,10 +39,21 @@ import TabItem from '@theme/TabItem'; usage: pv user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Meter ID`} /> +
+
+ +
+
## Template Parameter `discovergy` @@ -47,5 +61,5 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | Username
`user` | e.g. email address, user id, etc. | | yes | | Password
`password` | Use single quotes in case of leading zeros | | yes | -| `meter` | | Beispiel: `1ESY1161229886` | yes | +| Meter ID
`meter` | | Beispiel: `1ESY1161229886` | yes | diff --git a/docs/devices-next/meters/dsmr.mdx b/docs/devices-next/meters/dsmr.mdx index 71d889bb34..fbec6d3f02 100644 --- a/docs/devices-next/meters/dsmr.mdx +++ b/docs/devices-next/meters/dsmr.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DSMR - +
+
+ +
+
+ +
+
## Template Parameter `dsmr` diff --git a/docs/devices-next/meters/dzg-dvh4013.mdx b/docs/devices-next/meters/dzg-dvh4013.mdx index fd9eff1eb9..605ff0dbb7 100644 --- a/docs/devices-next/meters/dzg-dvh4013.mdx +++ b/docs/devices-next/meters/dzg-dvh4013.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DZG DVH4013 - +
+
+ +
+
+ +
+
## Template Parameter `dzg` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/e3-dc.mdx b/docs/devices-next/meters/e3-dc.mdx index 5ef572189b..545b1cc883 100644 --- a/docs/devices-next/meters/e3-dc.mdx +++ b/docs/devices-next/meters/e3-dc.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E3/DC - +
+
+ Username and password are identical to Web Portal or My E3/DC App access. Key (=RSCP-Password) must be set in the E3/DC system at Personalize/User Profile. The IP adresses of evcc and E3/DC system must be in the same subnet. @@ -31,7 +34,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_grid type: template template: e3dc-rscp @@ -40,7 +43,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional)`} /> @@ -55,7 +58,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_pv type: template template: e3dc-rscp @@ -64,7 +67,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -80,7 +83,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_battery type: template template: e3dc-rscp @@ -89,12 +92,23 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) capacity: 50 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `e3dc-rscp` @@ -104,7 +118,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= | Port
`port` | | Standard: `5033` | no | | Username
`user` | e.g. email address, user id, etc. | | yes | | Password
`password` | Use single quotes in case of leading zeros | | yes | -| `key` | | | yes | +| RSCP-Password
`key` | | | yes | | Discharge limit in W
`dischargelimit` | Limits discharge power in 'Hold' battery mode | | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/eastron-sdm120-modbus.mdx b/docs/devices-next/meters/eastron-sdm120-modbus.mdx index bf6c21cc9d..312e54abf6 100644 --- a/docs/devices-next/meters/eastron-sdm120-modbus.mdx +++ b/docs/devices-next/meters/eastron-sdm120-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM120-Modbus - +
+
+ @@ -82,10 +85,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron-sdm120` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/eastron-sdm220-230.mdx b/docs/devices-next/meters/eastron-sdm220-230.mdx index 3ec38750b9..4a0c3ebf52 100644 --- a/docs/devices-next/meters/eastron-sdm220-230.mdx +++ b/docs/devices-next/meters/eastron-sdm220-230.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM220/230 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron-sdm220_230` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/eastron-sdm630-modbus.mdx b/docs/devices-next/meters/eastron-sdm630-modbus.mdx index b86eab1fc8..c8e83a7756 100644 --- a/docs/devices-next/meters/eastron-sdm630-modbus.mdx +++ b/docs/devices-next/meters/eastron-sdm630-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM630-Modbus - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/eastron-sdm72d-m.mdx b/docs/devices-next/meters/eastron-sdm72d-m.mdx index 8bea6fe9a3..d4eb83b76b 100644 --- a/docs/devices-next/meters/eastron-sdm72d-m.mdx +++ b/docs/devices-next/meters/eastron-sdm72d-m.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM72D-M - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron-sdm72` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/eastron-sdm72dm-v2.mdx b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx index f197a07083..ac8d30343e 100644 --- a/docs/devices-next/meters/eastron-sdm72dm-v2.mdx +++ b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM72DM-V2 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/enphase-iq-envoy.mdx b/docs/devices-next/meters/enphase-iq-envoy.mdx index 5be05d7273..ea97dce4b8 100644 --- a/docs/devices-next/meters/enphase-iq-envoy.mdx +++ b/docs/devices-next/meters/enphase-iq-envoy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Enphase IQ Envoy - +
+
+ Only batteries of type "AC Battery" are currently supported by Enphase-API. @@ -26,13 +29,13 @@ Only batteries of type "AC Battery" are currently supported by Enphase-API. template: enphase usage: grid host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_grid type: template template: enphase usage: grid host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -44,13 +47,13 @@ Only batteries of type "AC Battery" are currently supported by Enphase-API. template: enphase usage: pv host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_pv type: template template: enphase usage: pv host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -62,25 +65,36 @@ Only batteries of type "AC Battery" are currently supported by Enphase-API. template: enphase usage: battery host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_battery type: template template: enphase usage: battery host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) capacity: 50 # Battery capacity (kWh), optional cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +
+
+ +
+
## Template Parameter `enphase` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| `token` | Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication | | no | +| Token
`token` | Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | diff --git a/docs/devices-next/meters/esphome-dlms-meter-austria.mdx b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx index acfa30d61b..a1977fb70b 100644 --- a/docs/devices-next/meters/esphome-dlms-meter-austria.mdx +++ b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ESPHome DLMS Meter Austria - +
+
+ Requires an ESPHome node running the `dlms_meter` component (e.g., from `github://SimonFischer04/esphome@dlms-meter`), configured for Austrian DLMS meters. @@ -30,6 +33,17 @@ configured for Austrian DLMS meters. usage: grid host: 192.0.2.2 # IP address or hostname timeout: 10s # Timeout, optional`} /> +
+
+ +
+
## Template Parameter `esphome-dlms-austria` diff --git a/docs/devices-next/meters/esphome-dsmr.mdx b/docs/devices-next/meters/esphome-dsmr.mdx index 397c156ce4..855ac6f273 100644 --- a/docs/devices-next/meters/esphome-dsmr.mdx +++ b/docs/devices-next/meters/esphome-dsmr.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ESPHome DSMR - +
+
+ +
+
+ +
+
## Template Parameter `slimmelezer` diff --git a/docs/devices-next/meters/fenecon.mdx b/docs/devices-next/meters/fenecon.mdx index b90cc9c79e..e8b136d8b3 100644 --- a/docs/devices-next/meters/fenecon.mdx +++ b/docs/devices-next/meters/fenecon.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FENECON - +
+
+ A commercial license is required for FEMS FENECON systems for active battery control. @@ -65,12 +68,23 @@ A commercial license is required for FEMS FENECON systems for active battery con usage: battery host: 192.0.2.2 # IP address or hostname password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) + battery: ess0 # Controllable battery component, optional + watchdog: 60s # Watchdog, adjusted to the API timeout (optional) capacity: 50 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `openems` @@ -78,8 +92,8 @@ A commercial license is required for FEMS FENECON systems for active battery con |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Password
`password` | Use single quotes in case of leading zeros | Standard: `user` | no | -| `battery` | controllable battery component | Beispiel: `ess0` | no | -| `watchdog` | adjusted to the API timeout | Standard: `60s` | no | +| Controllable battery component
`battery` | | Beispiel: `ess0` | no | +| Watchdog
`watchdog` | adjusted to the API timeout | Standard: `60s` | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx index 81d88eccf2..cc4dc2bb24 100644 --- a/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FoxESS H1 Series Hybrid Inverter - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `fox-ess-h1` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx index 807557c105..249da7abb8 100644 --- a/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FoxESS H3 Series Hybrid Inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `fox-ess-h3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx index ac8e5a156f..1a3a76defd 100644 --- a/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FoxESS H3-Smart Series Hybrid Inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `fox-ess-h3-smart` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/fronius-ohmpilot.mdx b/docs/devices-next/meters/fronius-ohmpilot.mdx index ca7a992baf..00cd422db3 100644 --- a/docs/devices-next/meters/fronius-ohmpilot.mdx +++ b/docs/devices-next/meters/fronius-ohmpilot.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Ohmpilot - +
+
+ +
+
+ +
+
## Template Parameter `fronius-ohmpilot` diff --git a/docs/devices-next/meters/fronius-primo-gen24-plus.mdx b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx index cf76c73bd7..6c224fd967 100644 --- a/docs/devices-next/meters/fronius-primo-gen24-plus.mdx +++ b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Primo GEN24 Plus - +
+
+ @@ -30,7 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> + id: 200 # ID, Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> @@ -71,6 +74,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `fronius-gen24` @@ -78,7 +92,7 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `502` | no | -| `id` | Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). | Standard: `200` | no | +| ID
`id` | Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). | Standard: `200` | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx index 987bc1734d..e9a5a9bf0c 100644 --- a/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx +++ b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Smartmeter (via Inverter) - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sunspec-meter` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/fronius-solar-api-v1.mdx b/docs/devices-next/meters/fronius-solar-api-v1.mdx index d94426ebf8..04de90d186 100644 --- a/docs/devices-next/meters/fronius-solar-api-v1.mdx +++ b/docs/devices-next/meters/fronius-solar-api-v1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Solar API V1 - +
+
+ Solar API should only be used as fallback. Integration via Modbus is preferred. @@ -39,7 +42,7 @@ Username and password are only required for active battery control. host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -59,7 +62,7 @@ Username and password are only required for active battery control. host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -80,10 +83,21 @@ Username and password are only required for active battery control. user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) capacity: 50 # Battery capacity (kWh), optional - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> +
+
+ +
+
## Template Parameter `fronius-solarapi-v1` @@ -93,5 +107,5 @@ Username and password are only required for active battery control. | Username (for active battery control)
`user` | e.g. email address, user id, etc. | Standard: `customer` | no | | Password (for active battery control)
`password` | Use single quotes in case of leading zeros | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| Firmware starting with 1.36.5-1 require /api/config.
`batteryconfiguri` | | Standard: `/config`
Auswahl: `/config`, `/api/config` | no | +| Battery configuration URI
`batteryconfiguri` | Firmware starting with 1.36.5-1 requires /api/config. | Standard: `/config`
Auswahl: `/config`, `/api/config` | no | diff --git a/docs/devices-next/meters/fronius-symo-gen24-plus.mdx b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx index a83500687c..950ede817b 100644 --- a/docs/devices-next/meters/fronius-symo-gen24-plus.mdx +++ b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Symo GEN24 Plus - +
+
+ @@ -30,7 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> + id: 200 # ID, Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> @@ -71,6 +74,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `fronius-gen24` @@ -78,7 +92,7 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `502` | no | -| `id` | Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). | Standard: `200` | no | +| ID
`id` | Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). | Standard: `200` | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx index 9770d8e6d9..9a7be65fb2 100644 --- a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ginlong Solis Hybrid Inverter (RHI series) - +
+
+ @@ -118,12 +121,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solis-hybrid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx index c231f1dbfb..b139ae9ff2 100644 --- a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ginlong Solis Hybrid Inverter (S Series) - +
+
+ @@ -118,12 +121,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solis-hybrid-s` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/ginlong-solis-inverter.mdx b/docs/devices-next/meters/ginlong-solis-inverter.mdx index 6d38692a2f..d8081be5d6 100644 --- a/docs/devices-next/meters/ginlong-solis-inverter.mdx +++ b/docs/devices-next/meters/ginlong-solis-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ginlong Solis Inverter - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solis` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/go-e-controller.mdx b/docs/devices-next/meters/go-e-controller.mdx index abb32f8a4f..616f25c861 100644 --- a/docs/devices-next/meters/go-e-controller.mdx +++ b/docs/devices-next/meters/go-e-controller.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Controller - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `go-e-controller` diff --git a/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx b/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx index aab18b6eae..0d70392e73 100644 --- a/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx +++ b/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # GoodWe ET/EH/BH/BT Hybrid Inverter - +
+
+ @@ -41,7 +44,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} /> + battery: 1 # Battery number, [1, 2] (optional)`} /> @@ -70,7 +73,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Battery number, [1, 2] (optional)`} advanced={`meters: - name: my_pv type: template template: goodwe-hybrid @@ -94,7 +97,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -124,7 +127,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Battery number, [1, 2] (optional)`} advanced={`meters: - name: my_battery type: template template: goodwe-hybrid @@ -148,18 +151,29 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) capacity: 50 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `goodwe-hybrid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip`, `udp` | no | -| `battery` | | Standard: `1`
Auswahl: `1`, `2` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip`, `udp` | no | +| Battery number
`battery` | | Standard: `1`
Auswahl: `1`, `2` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx index 347be75c10..53165a3351 100644 --- a/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx +++ b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # GoodWe GoodWe over Wifi - +
+
+ @@ -46,6 +49,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `goodwe-wifi` diff --git a/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx b/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx index be940ae405..6b8b5d600a 100644 --- a/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx +++ b/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # GoodWe SDT/DT Inverter - +
+
+ +
+
+ +
+
## Template Parameter `goodwe-dt` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/growatt-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-hybrid-inverter.mdx index 101e3c326b..1f3a51ec7b 100644 --- a/docs/devices-next/meters/growatt-hybrid-inverter.mdx +++ b/docs/devices-next/meters/growatt-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Growatt Hybrid Inverter - +
+
+ To use the active battery control, a one-time manual setup is necessary. The modbus registers `1100, 1101, 1102` need to be set to the values `0, 5947, 0` at the same time (via "write multiple", FC 16). @@ -154,12 +157,23 @@ The active battery control uses the first "Battery first" timeslot, so it cannot +
+
+ +
+
## Template Parameter `growatt-hybrid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx index 30246d9e41..4cf4f6af0d 100644 --- a/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx +++ b/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Growatt TL-X(H) Hybrid Inverter - +
+
+ @@ -148,12 +151,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `growatt-hybrid-tlxh` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/homematic-ip.mdx b/docs/devices-next/meters/homematic-ip.mdx index c15d2d44fd..77f1089b45 100644 --- a/docs/devices-next/meters/homematic-ip.mdx +++ b/docs/devices-next/meters/homematic-ip.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Homematic IP - +
+
+ @@ -26,7 +29,7 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: - name: my_grid type: template template: homematic @@ -35,8 +38,8 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional)`} /> + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional)`} /> @@ -50,7 +53,7 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: - name: my_pv type: template template: homematic @@ -59,8 +62,8 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional)`} /> + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional)`} /> @@ -74,7 +77,7 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: - name: my_charger type: template template: homematic @@ -83,11 +86,22 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional)`} /> + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional)`} /> +
+
+ +
+
## Template Parameter `homematic` @@ -97,6 +111,6 @@ import TabItem from '@theme/TabItem'; | Device address/Serial number
`device` | Homematic device id like shown in the CCU web user interface. | Beispiel: `0001EE89AAD848` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1)
`meterchannel` | Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. | Standard: `6` | yes | -| XML-RPC api cache duration - Default 1s. (valid units are s,m,h)
`cache` | In case of duty cycle problems try a cache setting of 30s. | Standard: `1s`
Beispiel: `5m` | no | +| Meter channel number
`meterchannel` | Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. | Standard: `6`
Beispiel: `HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1` | yes | +| XML-RPC API cache duration
`cache` | In case of duty cycle problems try a cache setting of 30s. | Standard: `1s`
Beispiel: `5m` | no | diff --git a/docs/devices-next/meters/homewizard-kwh-meter.mdx b/docs/devices-next/meters/homewizard-kwh-meter.mdx index 87f8b6c3d7..ce9b142298 100644 --- a/docs/devices-next/meters/homewizard-kwh-meter.mdx +++ b/docs/devices-next/meters/homewizard-kwh-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # HomeWizard kWh Meter - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `homewizard-kwh` diff --git a/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx index a6816f9ed4..b7ba9ccc30 100644 --- a/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx +++ b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # HomeWizard Wi-Fi P1 Meter - +
+
+ +
+
+ +
+
## Template Parameter `homewizard` diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx index b1f16136ed..d9813432cf 100644 --- a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hoymiles HM & HMS Series (via AhoyDTU) - +
+
+ Inverter #[ID], optional`} /> + id: 0 # Inverter ID, If multiple exist. The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID] (optional)`} /> +
+
+ +
+
## Template Parameter `hoymiles-ahoydtu` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #\[ID\]
`id` | | | no | +| Inverter ID
`id` | If multiple exist. The numbering starts at 0. See AhoyDTU webinterface -> Inverter #\[ID\] | | no | diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx index d406a1f428..a7bda354e5 100644 --- a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hoymiles HM & HMS Series (via OpenDTU) - +
+
+ +
+
+ +
+
## Template Parameter `hoymiles-opendtu` diff --git a/docs/devices-next/meters/huawei-emma.mdx b/docs/devices-next/meters/huawei-emma.mdx index 3bfcc0d6c2..ab0a3218de 100644 --- a/docs/devices-next/meters/huawei-emma.mdx +++ b/docs/devices-next/meters/huawei-emma.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei EMMA - +
+
+ @@ -72,11 +75,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `huawei-emma` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/huawei-smartlogger.mdx b/docs/devices-next/meters/huawei-smartlogger.mdx index 68a56794ad..34b57a6b60 100644 --- a/docs/devices-next/meters/huawei-smartlogger.mdx +++ b/docs/devices-next/meters/huawei-smartlogger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SmartLogger - +
+
+ @@ -40,7 +43,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Battery storage unit index, optional`} /> @@ -68,7 +71,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -97,19 +100,30 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `huawei-smartlogger` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | no | -| `storageunit` | | Standard: `1` | no | +| Battery storage unit index
`storageunit` | | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/huawei-sun2000-sdongle.mdx b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx index 132329fbab..0b23cbfa12 100644 --- a/docs/devices-next/meters/huawei-sun2000-sdongle.mdx +++ b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SUN2000 (SDongle) - +
+
+ Needs "Modbus/TCP". Activation using "maintenance access" within the communication settings of the inverter. See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 @@ -30,11 +33,22 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional`} /> +
+
+ +
+
## Template Parameter `huawei-dongle` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | no | diff --git a/docs/devices-next/meters/huawei-sun2000.mdx b/docs/devices-next/meters/huawei-sun2000.mdx index 1d14b6b223..97261c3b2a 100644 --- a/docs/devices-next/meters/huawei-sun2000.mdx +++ b/docs/devices-next/meters/huawei-sun2000.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SUN2000 - +
+
+ Grid and Battery require the PowerSensor. Modbus/TCP requires activation using "maintenance access" within the communication settings of the inverter. @@ -71,7 +74,7 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Battery storage unit index, optional`} /> @@ -125,7 +128,7 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -180,21 +183,32 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxchargepower: 10000 # Maximum charge power (W), For forced charging of the battery. (optional) capacity: 50 # Battery capacity (kWh), optional forceaccharging: false # Inverter cascade, Keep AC charging active to charge the storage from other inverters via AC. Prevents stand-by. (optional)`} /> +
+
+ +
+
## Template Parameter `huawei-sun2000` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | no | -| `storageunit` | | Standard: `1` | no | +| Battery storage unit index
`storageunit` | | Standard: `1` | no | | Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `10000`
Einheit: W | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/iammeter-wem3080.mdx b/docs/devices-next/meters/iammeter-wem3080.mdx index dfd5b5e65e..5cdee38c3f 100644 --- a/docs/devices-next/meters/iammeter-wem3080.mdx +++ b/docs/devices-next/meters/iammeter-wem3080.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IAMMETER WEM3080 - +
+
+ 3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. See https://www.iammeter.com/newsshow/net-energy-metering @@ -50,6 +53,17 @@ See https://www.iammeter.com/newsshow/net-energy-metering +
+
+ +
+
## Template Parameter `iammeter` diff --git a/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx b/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx index da56e4e3f3..93ab517abc 100644 --- a/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx +++ b/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IAMMETER WEM3080T/WEM3046T/WEM3050T - +
+
+ 3-phase meters (WEM3080T/WEM3046T/WEM3050T) require Net Metering Mode (NEM) to be enabled. See https://www.iammeter.com/newsshow/net-energy-metering @@ -50,6 +53,17 @@ See https://www.iammeter.com/newsshow/net-energy-metering +
+
+ +
+
## Template Parameter `iammeter` diff --git a/docs/devices-next/meters/igen-tech-solarman-logger.mdx b/docs/devices-next/meters/igen-tech-solarman-logger.mdx index daa1532704..87d074c10e 100644 --- a/docs/devices-next/meters/igen-tech-solarman-logger.mdx +++ b/docs/devices-next/meters/igen-tech-solarman-logger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IGEN Tech Solarman Logger - +
+
+ +
+
+ +
+
## Template Parameter `solarman` diff --git a/docs/devices-next/meters/inepro-pro380-mod.mdx b/docs/devices-next/meters/inepro-pro380-mod.mdx index 8ea681d21a..fce3407793 100644 --- a/docs/devices-next/meters/inepro-pro380-mod.mdx +++ b/docs/devices-next/meters/inepro-pro380-mod.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # inepro PRO380-MOD - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `inepro` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/iometer.mdx b/docs/devices-next/meters/iometer.mdx index df733dad24..8bf9978b8a 100644 --- a/docs/devices-next/meters/iometer.mdx +++ b/docs/devices-next/meters/iometer.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IOmeter - +
+
+ +
+
+ +
+
## Template Parameter `iometer` diff --git a/docs/devices-next/meters/janitza-b-series.mdx b/docs/devices-next/meters/janitza-b-series.mdx index 73c5706f3b..eb0e3c3a97 100644 --- a/docs/devices-next/meters/janitza-b-series.mdx +++ b/docs/devices-next/meters/janitza-b-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Janitza B series - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `janitza` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/janitza-umg-series.mdx b/docs/devices-next/meters/janitza-umg-series.mdx index 1e931c79cd..1df501492c 100644 --- a/docs/devices-next/meters/janitza-umg-series.mdx +++ b/docs/devices-next/meters/janitza-umg-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Janitza UMG series - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `janitza` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/keba-kecontact-e10.mdx b/docs/devices-next/meters/keba-kecontact-e10.mdx index fc357a1d76..0588f43f08 100644 --- a/docs/devices-next/meters/keba-kecontact-e10.mdx +++ b/docs/devices-next/meters/keba-kecontact-e10.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact E10 - +
+
+ +
+
+ +
+
## Template Parameter `keba-kecontact` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx index e1a6dbbd6c..f486848d92 100644 --- a/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx +++ b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Energy Meter C (KEM-C) - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt3xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx index f95a1292c6..0cac9ea36d 100644 --- a/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx +++ b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Energy Meter P (KEM-P) - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/kostal-piko-ba.mdx b/docs/devices-next/meters/kostal-piko-ba.mdx index 3ee5dc67cf..282b2cbb91 100644 --- a/docs/devices-next/meters/kostal-piko-ba.mdx +++ b/docs/devices-next/meters/kostal-piko-ba.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko BA - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `kostal-piko-pv` diff --git a/docs/devices-next/meters/kostal-piko-hybrid.mdx b/docs/devices-next/meters/kostal-piko-hybrid.mdx index 7614400f55..d4cf92ac3d 100644 --- a/docs/devices-next/meters/kostal-piko-hybrid.mdx +++ b/docs/devices-next/meters/kostal-piko-hybrid.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko Hybrid - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `kostal-piko-hybrid` diff --git a/docs/devices-next/meters/kostal-piko-legacy.mdx b/docs/devices-next/meters/kostal-piko-legacy.mdx index 57179714a3..8d9f7609d7 100644 --- a/docs/devices-next/meters/kostal-piko-legacy.mdx +++ b/docs/devices-next/meters/kostal-piko-legacy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko (legacy) - +
+
+ +
+
+ +
+
## Template Parameter `kostal-piko-legacy` diff --git a/docs/devices-next/meters/kostal-piko-mp-plus.mdx b/docs/devices-next/meters/kostal-piko-mp-plus.mdx index 0975f5754d..2c4bd68f77 100644 --- a/docs/devices-next/meters/kostal-piko-mp-plus.mdx +++ b/docs/devices-next/meters/kostal-piko-mp-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko MP Plus - +
+
+ +
+
+ +
+
## Template Parameter `kostal-piko-mp-plus` diff --git a/docs/devices-next/meters/kostal-piko.mdx b/docs/devices-next/meters/kostal-piko.mdx index 69e0b21ede..57b409c2ca 100644 --- a/docs/devices-next/meters/kostal-piko.mdx +++ b/docs/devices-next/meters/kostal-piko.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `kostal-piko-pv` diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx index 1d010b9c94..31f3da614c 100644 --- a/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx +++ b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Plenticore Hybrid, incl. grid charging of the house battery - +
+
+ Only a single system may access the inverter! For active battery control, the feature external battery control via modbus must be activated using installer access. **_Can basically be used for various inverter generations (G1/G2/G3)._** **The function for grid charging the battery is available using this template, but is currently incompatible with some older inverters - _test carefully_!** @@ -45,7 +48,7 @@ _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ port: 1502 # Port endianness: little # Endianness (Little/Big), [little, big] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -74,19 +77,30 @@ _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ endianness: little # Endianness (Little/Big), [little, big] (optional) capacity: 50 # Battery capacity (kWh), optional maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `kostal-plenticore-gen2` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Endianness (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx index 578b8f0d4e..672d56556d 100644 --- a/docs/devices-next/meters/kostal-plenticore-hybrid.mdx +++ b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Plenticore Hybrid - +
+
+ Only a single system may access the inverter! For active battery control the function external battery control via Modbus must be activated using installer access. **Grid charging is not available!** _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ @@ -44,9 +47,7 @@ Only a single system may access the inverter! For active battery control the fun port: 1502 # Port endianness: little # Endianness (Little/Big), [little, big] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -76,20 +77,31 @@ Only a single system may access the inverter! For active battery control the fun capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `kostal-plenticore` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Endianness (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx index ad3250e277..f7880234e1 100644 --- a/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx +++ b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Smart Energy Meter (via inverter) - +
+
+ The energy meter must be installed in sensor position 2 (grid connection). Sensor position 1 (House consumption) is not supported. @@ -28,10 +31,21 @@ The energy meter must be installed in sensor position 2 (grid connection). Senso id: 71 host: 192.0.2.2 # Hostname port: 1502 # Port`} /> +
+
+ +
+
## Template Parameter `kostal-ksem-inverter` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/kostal-smart-energy-meter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter.mdx index d59b1fdd6c..aacf8adc47 100644 --- a/docs/devices-next/meters/kostal-smart-energy-meter.mdx +++ b/docs/devices-next/meters/kostal-smart-energy-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Smart Energy Meter - +
+
+ +
+
+ +
+
## Template Parameter `kostal-ksem` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/lg-ess-home-15.mdx b/docs/devices-next/meters/lg-ess-home-15.mdx index 605a7b6e1d..2f5914f8e1 100644 --- a/docs/devices-next/meters/lg-ess-home-15.mdx +++ b/docs/devices-next/meters/lg-ess-home-15.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LG ESS Home 15 - +
+
+ @@ -30,9 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -50,9 +51,7 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -70,13 +69,24 @@ import TabItem from '@theme/TabItem'; usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> +
+
+ +
+
## Template Parameter `lg-ess-home-15` @@ -84,7 +94,7 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Password
`password` | User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. | | no | -| `registration` | Registration id of the LG ESS HOME inverter. | Beispiel: `DE200...` | no | +| Registration ID
`registration` | ID of the LG ESS HOME inverter. | Beispiel: `DE200...` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/lg-ess-home-8-10.mdx b/docs/devices-next/meters/lg-ess-home-8-10.mdx index f3e9dec586..0485549582 100644 --- a/docs/devices-next/meters/lg-ess-home-8-10.mdx +++ b/docs/devices-next/meters/lg-ess-home-8-10.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LG ESS Home 8/10 - +
+
+ To use the battery control, a firmware version greater than or equal to 10.05.7433 / R2155 is required @@ -33,9 +36,7 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -53,9 +54,7 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -73,13 +72,24 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> +
+
+ +
+
## Template Parameter `lg-ess-home-8-10` @@ -87,7 +97,7 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Password
`password` | User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. | | no | -| `registration` | Registration id of the LG ESS HOME inverter. | Beispiel: `DE200...` | no | +| Registration ID
`registration` | ID of the LG ESS HOME inverter. | Beispiel: `DE200...` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/loxone-miniserver.mdx b/docs/devices-next/meters/loxone-miniserver.mdx index 05989cc6fd..d168b01077 100644 --- a/docs/devices-next/meters/loxone-miniserver.mdx +++ b/docs/devices-next/meters/loxone-miniserver.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Loxone Miniserver - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `loxone` diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx index c8cfbd5209..db134f8722 100644 --- a/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx +++ b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # M-TEC Energy Butler GEN2 - +
+
+ @@ -82,10 +85,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `mtec-eb-gen2` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx index 7b2e369958..33a0fad342 100644 --- a/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx +++ b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # M-TEC Energy Butler GEN3 - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `mtec-eb-gen3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/marstek-venus-battery-storage.mdx b/docs/devices-next/meters/marstek-venus-battery-storage.mdx index 5ddde8b1c9..1b9af288b8 100644 --- a/docs/devices-next/meters/marstek-venus-battery-storage.mdx +++ b/docs/devices-next/meters/marstek-venus-battery-storage.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Marstek Venus Battery Storage - +
+
+ + maxchargepower: 2500 # Maximum charge power (W), 2500W is the maximum for Venus. (optional) + work_mode_normal: 1 # Work mode for Normal state, 0=manual, 1=anti-feed, 2=trade mode. (optional)`} /> +
+
+ +
+
## Template Parameter `marstek-venus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | Venus-E 5.12 kWh, Venus-C 2.56 kWh | Standard: `5.12`
Beispiel: `50`
Einheit: kWh | no | -| Venus can only be discharged down to 11%.
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `11`
Beispiel: `25`
Einheit: % | no | +| Minimum charge
`minsoc` | Venus can only be discharged down to 11%. | Standard: `11`
Beispiel: `11`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `100`
Beispiel: `95`
Einheit: % | no | -| Charge power in watts for Charge mode. 2500W is the maximum for Venus.
`maxchargepower` | For forced charging of the battery. | Standard: `2500`
Einheit: W | no | -| Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode.
`work_mode_normal` | | Standard: `1` | no | +| Maximum charge power
`maxchargepower` | 2500W is the maximum for Venus. | Standard: `2500`
Einheit: W | no | +| Work mode for Normal state
`work_mode_normal` | 0=manual, 1=anti-feed, 2=trade mode. | Standard: `1` | no | diff --git a/docs/devices-next/meters/mhendriks-p1-dongle.mdx b/docs/devices-next/meters/mhendriks-p1-dongle.mdx index 92918dd944..5b63e51bd5 100644 --- a/docs/devices-next/meters/mhendriks-p1-dongle.mdx +++ b/docs/devices-next/meters/mhendriks-p1-dongle.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # mhendriks P1 dongle - +
+
+ +
+
+ +
+
## Template Parameter `slimmelezer` diff --git a/docs/devices-next/meters/my-pv-ac-elwa-2.mdx b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx index f52c5ba6a9..cdbc5ab1dc 100644 --- a/docs/devices-next/meters/my-pv-ac-elwa-2.mdx +++ b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC ELWA 2 - +
+
+ +
+
+ +
+
## Template Parameter `ac-elwa-2` diff --git a/docs/devices-next/meters/my-pv-ac-elwa-e.mdx b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx index 83a5a3d40b..f6eeafa70d 100644 --- a/docs/devices-next/meters/my-pv-ac-elwa-e.mdx +++ b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC ELWA-E - +
+
+ +
+
+ +
+
## Template Parameter `ac-elwa-e` diff --git a/docs/devices-next/meters/my-pv-ac-thor.mdx b/docs/devices-next/meters/my-pv-ac-thor.mdx index c428ef23d3..8e04b88dac 100644 --- a/docs/devices-next/meters/my-pv-ac-thor.mdx +++ b/docs/devices-next/meters/my-pv-ac-thor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC•THOR - +
+
+ +
+
+ +
+
## Template Parameter `thor` diff --git a/docs/devices-next/meters/my-pv-wifi-meter.mdx b/docs/devices-next/meters/my-pv-wifi-meter.mdx index 7c13006d33..dbdb5bc9b2 100644 --- a/docs/devices-next/meters/my-pv-wifi-meter.mdx +++ b/docs/devices-next/meters/my-pv-wifi-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV WiFi Meter - +
+
+ +
+
+ +
+
## Template Parameter `mypv-wifi-meter` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/mystrom-switch.mdx b/docs/devices-next/meters/mystrom-switch.mdx index 5c992fb900..805963bd76 100644 --- a/docs/devices-next/meters/mystrom-switch.mdx +++ b/docs/devices-next/meters/mystrom-switch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # myStrom Switch - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `mystrom` diff --git a/docs/devices-next/meters/openems.mdx b/docs/devices-next/meters/openems.mdx index 7b91fc2297..8e21a40d6d 100644 --- a/docs/devices-next/meters/openems.mdx +++ b/docs/devices-next/meters/openems.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OpenEMS - +
+
+ A commercial license is required for FEMS FENECON systems for active battery control. @@ -65,12 +68,23 @@ A commercial license is required for FEMS FENECON systems for active battery con usage: battery host: 192.0.2.2 # IP address or hostname password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) + battery: ess0 # Controllable battery component, optional + watchdog: 60s # Watchdog, adjusted to the API timeout (optional) capacity: 50 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `openems` @@ -78,8 +92,8 @@ A commercial license is required for FEMS FENECON systems for active battery con |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Password
`password` | Use single quotes in case of leading zeros | Standard: `user` | no | -| `battery` | controllable battery component | Beispiel: `ess0` | no | -| `watchdog` | adjusted to the API timeout | Standard: `60s` | no | +| Controllable battery component
`battery` | | Beispiel: `ess0` | no | +| Watchdog
`watchdog` | adjusted to the API timeout | Standard: `60s` | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/orno-or-we-516.mdx b/docs/devices-next/meters/orno-or-we-516.mdx index b65eedce7b..0402342539 100644 --- a/docs/devices-next/meters/orno-or-we-516.mdx +++ b/docs/devices-next/meters/orno-or-we-516.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ORNO OR-WE-516 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `orno` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/orno-or-we-517.mdx b/docs/devices-next/meters/orno-or-we-517.mdx index d75a04e510..026cd5b403 100644 --- a/docs/devices-next/meters/orno-or-we-517.mdx +++ b/docs/devices-next/meters/orno-or-we-517.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ORNO OR-WE-517 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `orno` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/p1monitor-p1-monitor.mdx b/docs/devices-next/meters/p1monitor-p1-monitor.mdx index 6fe2036cf0..7c6f0ef956 100644 --- a/docs/devices-next/meters/p1monitor-p1-monitor.mdx +++ b/docs/devices-next/meters/p1monitor-p1-monitor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # P1Monitor P1 Monitor - +
+
+ +
+
+ +
+
## Template Parameter `p1monitor` diff --git a/docs/devices-next/meters/plexlog.mdx b/docs/devices-next/meters/plexlog.mdx index dd0f27e0e0..41b0562e26 100644 --- a/docs/devices-next/meters/plexlog.mdx +++ b/docs/devices-next/meters/plexlog.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Plexlog - +
+
+ The values are updated approximately every 15 seconds, hence the evcc `interval` should not be less than 30 seconds. @@ -75,11 +78,22 @@ The values are updated approximately every 15 seconds, hence the evcc `interval` +
+
+ +
+
## Template Parameter `plexlog` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/powerdog.mdx b/docs/devices-next/meters/powerdog.mdx index 0c5967908c..369aeaa887 100644 --- a/docs/devices-next/meters/powerdog.mdx +++ b/docs/devices-next/meters/powerdog.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Powerdog - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `powerdog` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/powerfox-poweropti.mdx b/docs/devices-next/meters/powerfox-poweropti.mdx index cb7099f950..55b08db0cf 100644 --- a/docs/devices-next/meters/powerfox-poweropti.mdx +++ b/docs/devices-next/meters/powerfox-poweropti.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Powerfox Poweropti - +
+
+ @@ -30,7 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti`} /> + id: main # ID, Id in case of multiple PowerOpti`} /> @@ -48,10 +51,21 @@ import TabItem from '@theme/TabItem'; usage: pv user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti`} /> + id: main # ID, Id in case of multiple PowerOpti`} /> +
+
+ +
+
## Template Parameter `powerfox-poweropti` @@ -59,5 +73,5 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | Username
`user` | e.g. email address, user id, etc. | | yes | | Password
`password` | Use single quotes in case of leading zeros | | yes | -| `id` | Id in case of multiple PowerOpti | Standard: `main` | yes | +| ID
`id` | Id in case of multiple PowerOpti | Standard: `main` | yes | diff --git a/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx index e25ecbda9a..431b4ef604 100644 --- a/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx +++ b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Qcells Hybrid-Inverter (Cloud) - +
+
+ The Qcells hybrid inverter has to be registered in the QcellsCloud. @@ -61,6 +64,17 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. +
+
+ +
+
## Template Parameter `qcells-hybrid-cloud` diff --git a/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx b/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx index 728e0c6b47..dde94a2681 100644 --- a/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx +++ b/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Qcells Q.HOME ESS HYB-G3 - +
+
+ @@ -41,7 +44,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -65,8 +68,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional`} /> @@ -95,7 +98,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -119,8 +122,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -150,7 +153,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -174,21 +177,32 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional)`} /> +
+
+ +
+
## Template Parameter `solax` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| The inverter has a third PV input (MPPT3)
`mppt3` | | | no | -| `storageunit` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Third PV input
`mppt3` | The inverter has a third PV input (MPPT3) | | no | +| Battery storage unit index
`storageunit` | | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | | no | diff --git a/docs/devices-next/meters/rct-power.mdx b/docs/devices-next/meters/rct-power.mdx index 4261375a6c..7e5065aff2 100644 --- a/docs/devices-next/meters/rct-power.mdx +++ b/docs/devices-next/meters/rct-power.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # RCT Power - +
+
+ @@ -28,10 +31,7 @@ import TabItem from '@theme/TabItem'; template: rct-power usage: grid host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional)`} /> + cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -47,8 +47,6 @@ import TabItem from '@theme/TabItem'; template: rct-power usage: pv host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) externalpower: # External power, Query external power of all devices connected to S0 (optional)`} /> @@ -70,11 +68,21 @@ import TabItem from '@theme/TabItem'; minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional)`} /> + maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional)`} /> +
+
+ +
+
## Template Parameter `rct-power` diff --git a/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx index 5e32e8fb70..9482cf2818 100644 --- a/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Saia-Burgess Controls (SBC) ALE3 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sbc-axx3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx b/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx index e1e8adca06..0b735a0722 100644 --- a/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Saia-Burgess Controls (SBC) AWD3 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sbc-axx3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx index c485d7dfa6..38140ad741 100644 --- a/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAJ H1 Series Hybrid Solar Inverter - +
+
+ @@ -76,12 +79,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `saj-h1` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Timeout
`timeout` | | Standard: `5s`
Beispiel: `10s` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx index bd7735ecea..62ef79a1b9 100644 --- a/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAJ H2 Series Hybrid Solar Inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -93,32 +71,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -177,12 +130,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `saj-h2` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | Standard: `2` | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | diff --git a/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx index 6968e5eb68..4aa4e4a30c 100644 --- a/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAJ R5 Series Solar Inverter - +
+
+ +
+
+ +
+
## Template Parameter `saj-r5` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/sax-homespeicher.mdx b/docs/devices-next/meters/sax-homespeicher.mdx index 8591ea5cd6..7be939fea2 100644 --- a/docs/devices-next/meters/sax-homespeicher.mdx +++ b/docs/devices-next/meters/sax-homespeicher.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAX Homespeicher - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sax` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx index 44a475f4e9..9468581252 100644 --- a/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx +++ b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Schneider Electric iEM3xxx Modbus - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `schneider-iem3000` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/senec-home.mdx b/docs/devices-next/meters/senec-home.mdx index e7dc6d671b..df2fde141f 100644 --- a/docs/devices-next/meters/senec-home.mdx +++ b/docs/devices-next/meters/senec-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SENEC .Home - +
+
+ @@ -23,7 +26,7 @@ import TabItem from '@theme/TabItem'; template: senec-home usage: grid host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -34,7 +37,7 @@ import TabItem from '@theme/TabItem'; template: senec-home usage: pv host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -45,23 +48,34 @@ import TabItem from '@theme/TabItem'; template: senec-home usage: battery host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional)`} advanced={`meters: + schema: https # Schema, [https, http] (optional)`} advanced={`meters: - name: my_battery type: template template: senec-home usage: battery host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) capacity: 50 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `senec-home` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | -| `schema` | | Standard: `https`
Auswahl: `https`, `http` | no | +| Schema
`schema` | | Standard: `https`
Auswahl: `https`, `http` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx b/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx index fc23b04970..beb03c94b1 100644 --- a/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx +++ b/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Senergy SE 4/5/6KTL-S1/G2 Inverter - +
+
+ +
+
+ +
+
## Template Parameter `senergy` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/shelly-1pm-mini.mdx b/docs/devices-next/meters/shelly-1pm-mini.mdx index 26ddcd3dbf..b7553c0a92 100644 --- a/docs/devices-next/meters/shelly-1pm-mini.mdx +++ b/docs/devices-next/meters/shelly-1pm-mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 1PM mini - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/shelly-1pm.mdx b/docs/devices-next/meters/shelly-1pm.mdx index 6154a05728..8dea667115 100644 --- a/docs/devices-next/meters/shelly-1pm.mdx +++ b/docs/devices-next/meters/shelly-1pm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 1PM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/shelly-3em.mdx b/docs/devices-next/meters/shelly-3em.mdx index a1b8476efe..256eb277c3 100644 --- a/docs/devices-next/meters/shelly-3em.mdx +++ b/docs/devices-next/meters/shelly-3em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 3EM - +
+
+ @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `shelly-3em` diff --git a/docs/devices-next/meters/shelly-em.mdx b/docs/devices-next/meters/shelly-em.mdx index fd6b6c0657..8616b3ce7f 100644 --- a/docs/devices-next/meters/shelly-em.mdx +++ b/docs/devices-next/meters/shelly-em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly EM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/shelly-plug-s.mdx b/docs/devices-next/meters/shelly-plug-s.mdx index 9507c07ef1..a28c4de0a7 100644 --- a/docs/devices-next/meters/shelly-plug-s.mdx +++ b/docs/devices-next/meters/shelly-plug-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Plug S - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/shelly-pm-mini.mdx b/docs/devices-next/meters/shelly-pm-mini.mdx index 14f5e21651..a4915c02d5 100644 --- a/docs/devices-next/meters/shelly-pm-mini.mdx +++ b/docs/devices-next/meters/shelly-pm-mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly PM mini - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/shelly-pro-1pm.mdx b/docs/devices-next/meters/shelly-pro-1pm.mdx index 89ba5d3f8e..8b29ddd75e 100644 --- a/docs/devices-next/meters/shelly-pro-1pm.mdx +++ b/docs/devices-next/meters/shelly-pro-1pm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 1PM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/shelly-pro-3-em.mdx b/docs/devices-next/meters/shelly-pro-3-em.mdx index 49e1fb8918..7d14b0272e 100644 --- a/docs/devices-next/meters/shelly-pro-3-em.mdx +++ b/docs/devices-next/meters/shelly-pro-3-em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 3 EM - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `shelly-pro-3em` diff --git a/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx b/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx index 02981a5287..e6ef3db824 100644 --- a/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx +++ b/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 3EM (monophase mode) - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/shelly-pro-em.mdx b/docs/devices-next/meters/shelly-pro-em.mdx index 3188e90108..159cde1718 100644 --- a/docs/devices-next/meters/shelly-pro-em.mdx +++ b/docs/devices-next/meters/shelly-pro-em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro EM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> +
+
+ +
+
## Template Parameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Username
`user` | e.g. email address, user id, etc. | | no | | Password
`password` | Use single quotes in case of leading zeros | | no | -| `channel` | | | no | +| Channel
`channel` | | | no | diff --git a/docs/devices-next/meters/siemens-7kt1665.mdx b/docs/devices-next/meters/siemens-7kt1665.mdx index 8c75e1a416..9c97b8ae23 100644 --- a/docs/devices-next/meters/siemens-7kt1665.mdx +++ b/docs/devices-next/meters/siemens-7kt1665.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens 7KT1665 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `siemens-7kt1665` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/siemens-junelight-smart-battery.mdx b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx index 7a5645dca5..119dcf8517 100644 --- a/docs/devices-next/meters/siemens-junelight-smart-battery.mdx +++ b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens Junelight Smart Battery - +
+
+ The battery has to be set to Loxone with the installer account. @@ -75,11 +78,22 @@ The battery has to be set to Loxone with the installer account. +
+
+ +
+
## Template Parameter `siemens-junelight` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/siemens-pac-2200.mdx b/docs/devices-next/meters/siemens-pac-2200.mdx index 4f2773e5f6..fdc646dc25 100644 --- a/docs/devices-next/meters/siemens-pac-2200.mdx +++ b/docs/devices-next/meters/siemens-pac-2200.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens PAC 2200 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `siemens-pac2200` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx b/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx index cec44117dd..04d404335c 100644 --- a/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx +++ b/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC - +
+
+ The electrician needs to enable the Modbus via TCP/IP in their service app before the setup is functional. This is not available in the customers mySigen app. @@ -27,7 +30,7 @@ The electrician needs to enable the Modbus via TCP/IP in their service app befor usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -39,7 +42,7 @@ The electrician needs to enable the Modbus via TCP/IP in their service app befor usage: pv host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -51,18 +54,29 @@ The electrician needs to enable the Modbus via TCP/IP in their service app befor usage: battery host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional`} advanced={`meters: + id: 1 # ID, optional`} advanced={`meters: - name: my_battery type: template template: sigenergy usage: battery host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional capacity: 50 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `sigenergy` @@ -70,6 +84,6 @@ The electrician needs to enable the Modbus via TCP/IP in their service app befor |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `502` | no | -| `id` | | Standard: `1` | no | +| ID
`id` | | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/sma-data-manager.mdx b/docs/devices-next/meters/sma-data-manager.mdx index f2b3f298e5..a48f216f5b 100644 --- a/docs/devices-next/meters/sma-data-manager.mdx +++ b/docs/devices-next/meters/sma-data-manager.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Data Manager - +
+
+ In the web interface of the SMA Data Manager you need to activate "Modbus Server activated" in the section "External communication". @@ -75,11 +78,22 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server +
+
+ +
+
## Template Parameter `sma-data-manager` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/sma-energy-meter.mdx b/docs/devices-next/meters/sma-energy-meter.mdx index 868a380ba7..d32a4834bf 100644 --- a/docs/devices-next/meters/sma-energy-meter.mdx +++ b/docs/devices-next/meters/sma-energy-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Energy Meter - +
+
+ @@ -48,6 +51,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sma-energy-meter` diff --git a/docs/devices-next/meters/sma-inverter-speedwire.mdx b/docs/devices-next/meters/sma-inverter-speedwire.mdx index 009e01b44e..970e7177b5 100644 --- a/docs/devices-next/meters/sma-inverter-speedwire.mdx +++ b/docs/devices-next/meters/sma-inverter-speedwire.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Inverter (Speedwire) - +
+
+ @@ -45,6 +48,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sma-inverter-speedwire` diff --git a/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx index 3a14008e49..d8a47fbdd4 100644 --- a/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Smart Energy Hybrid Inverter - +
+
+ @@ -66,18 +69,29 @@ import TabItem from '@theme/TabItem'; port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `sma-hybrid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx index 1aaf69675a..1ccc3215fe 100644 --- a/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx +++ b/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `sma-sbs-15-25-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx index 8fbf08be32..735b1b2065 100644 --- a/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx +++ b/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `sma-sbs-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx b/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx index e8874c81ef..b7ca55961a 100644 --- a/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx +++ b/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Home Manager 2.0 - +
+
+ +
+
+ +
+
## Template Parameter `sma-home-manager` diff --git a/docs/devices-next/meters/sma-sunny-island-modbus.mdx b/docs/devices-next/meters/sma-sunny-island-modbus.mdx index 67e85816b6..ada673ed6f 100644 --- a/docs/devices-next/meters/sma-sunny-island-modbus.mdx +++ b/docs/devices-next/meters/sma-sunny-island-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Island (Modbus) - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `sma-si-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `4200`
Einheit: W | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/sma-webbox.mdx b/docs/devices-next/meters/sma-webbox.mdx index d162cd8f78..99ab778191 100644 --- a/docs/devices-next/meters/sma-webbox.mdx +++ b/docs/devices-next/meters/sma-webbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA WebBox - +
+
+ +
+
+ +
+
## Template Parameter `sma-webbox` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/sma-wechselrichter-modbus.mdx b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx index f80531e0b4..fcd29f9c93 100644 --- a/docs/devices-next/meters/sma-wechselrichter-modbus.mdx +++ b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Wechselrichter (Modbus) - +
+
+ +
+
+ +
+
## Template Parameter `sma-inverter-modbus` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | ModbusTCP server needs to be enabled. | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/smartfox-box.mdx b/docs/devices-next/meters/smartfox-box.mdx index c99ed8450b..b6a15af3cd 100644 --- a/docs/devices-next/meters/smartfox-box.mdx +++ b/docs/devices-next/meters/smartfox-box.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Box - +
+
+ `aux` can be used for water heating power. @@ -49,6 +52,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox` diff --git a/docs/devices-next/meters/smartfox-light-em2-firmware.mdx b/docs/devices-next/meters/smartfox-light-em2-firmware.mdx index dbe4ccdc7f..3c2879514b 100644 --- a/docs/devices-next/meters/smartfox-light-em2-firmware.mdx +++ b/docs/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Light (EM2 firmware) - +
+
+ `aux` can be used for water heating power. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox-em2` diff --git a/docs/devices-next/meters/smartfox-pro-2.mdx b/docs/devices-next/meters/smartfox-pro-2.mdx index 0b1245ae3a..124fa5e93c 100644 --- a/docs/devices-next/meters/smartfox-pro-2.mdx +++ b/docs/devices-next/meters/smartfox-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro 2 - +
+
+ `aux` can be used for water heating power. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox-em2` diff --git a/docs/devices-next/meters/smartfox-pro-light-2.mdx b/docs/devices-next/meters/smartfox-pro-light-2.mdx index 58512e774a..7966381266 100644 --- a/docs/devices-next/meters/smartfox-pro-light-2.mdx +++ b/docs/devices-next/meters/smartfox-pro-light-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro Light 2 - +
+
+ `aux` can be used for water heating power. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox-em2` diff --git a/docs/devices-next/meters/smartfox-pro-light.mdx b/docs/devices-next/meters/smartfox-pro-light.mdx index 5fc9ce950a..b4bdcdc659 100644 --- a/docs/devices-next/meters/smartfox-pro-light.mdx +++ b/docs/devices-next/meters/smartfox-pro-light.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro Light - +
+
+ `aux` can be used for water heating power. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox-em2` diff --git a/docs/devices-next/meters/smartfox-pro.mdx b/docs/devices-next/meters/smartfox-pro.mdx index 4a88e7476b..f99fb3073f 100644 --- a/docs/devices-next/meters/smartfox-pro.mdx +++ b/docs/devices-next/meters/smartfox-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro - +
+
+ `aux` can be used for water heating power. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox-em2` diff --git a/docs/devices-next/meters/smartfox-reg-extended.mdx b/docs/devices-next/meters/smartfox-reg-extended.mdx index 1b1c664a03..f42c49f1bd 100644 --- a/docs/devices-next/meters/smartfox-reg-extended.mdx +++ b/docs/devices-next/meters/smartfox-reg-extended.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Reg extended - +
+
+ `aux` can be used for water heating power. @@ -49,6 +52,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox` diff --git a/docs/devices-next/meters/smartfox-reg.mdx b/docs/devices-next/meters/smartfox-reg.mdx index 146d2c8cbd..027fff3e8f 100644 --- a/docs/devices-next/meters/smartfox-reg.mdx +++ b/docs/devices-next/meters/smartfox-reg.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Reg - +
+
+ `aux` can be used for water heating power. @@ -49,6 +52,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `smartfox` diff --git a/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx b/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx index 299c0b2e87..cc5a544ce3 100644 --- a/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar Hybrid Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sofarsolar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx b/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx index 74f34bd5f9..41df8075eb 100644 --- a/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx +++ b/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar HYD 3…6K-EP - +
+
+ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. @@ -67,7 +70,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -119,7 +122,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -172,19 +175,30 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> +
+
+ +
+
## Template Parameter `sofarsolar-g3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | -| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Battery storage unit index
`storageunit` | In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | diff --git a/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx b/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx index 17f24fb396..139d037a28 100644 --- a/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx +++ b/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar HYD 5…20K-3PH - +
+
+ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. @@ -67,7 +70,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -119,7 +122,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -172,19 +175,30 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> +
+
+ +
+
## Template Parameter `sofarsolar-g3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | -| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Battery storage unit index
`storageunit` | In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | diff --git a/docs/devices-next/meters/sofarsolar-inverter.mdx b/docs/devices-next/meters/sofarsolar-inverter.mdx index 00beddb5b5..a29048bd50 100644 --- a/docs/devices-next/meters/sofarsolar-inverter.mdx +++ b/docs/devices-next/meters/sofarsolar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sofarsolar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx b/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx index 54eb8de6bc..6515f8c45e 100644 --- a/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx +++ b/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar SOFAR 5…24KTL-G3 - +
+
+ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. @@ -67,7 +70,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -119,7 +122,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -172,19 +175,30 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> +
+
+ +
+
## Template Parameter `sofarsolar-g3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | -| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Battery storage unit index
`storageunit` | In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | diff --git a/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx b/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx index fc6becf89b..d06fb170ec 100644 --- a/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx +++ b/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar SOFAR 80…136KTL - +
+
+ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is the easiest connection. The LSW-3 WiFi stick is not supported. For a RS485 serial connection using the inverter's COM port the inverter's side must be properly terminated. @@ -67,7 +70,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -119,7 +122,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -172,19 +175,30 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> +
+
+ +
+
## Template Parameter `sofarsolar-g3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | -| `storageunit` | Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Battery storage unit index
`storageunit` | In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Default mode for battery control
`defaultmode` | Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) | | no | diff --git a/docs/devices-next/meters/solaranzeige-solaranzeige.mdx b/docs/devices-next/meters/solaranzeige-solaranzeige.mdx index ba70968929..548fe5869d 100644 --- a/docs/devices-next/meters/solaranzeige-solaranzeige.mdx +++ b/docs/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solaranzeige Solaranzeige - +
+
+ @@ -62,6 +65,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solaranzeige` diff --git a/docs/devices-next/meters/solaredge-hybrid-inverter.mdx b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx index d2e576e651..b93f4bdd5f 100644 --- a/docs/devices-next/meters/solaredge-hybrid-inverter.mdx +++ b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarEdge Hybrid Inverter - +
+
+ Only one system can and may have a Modbus TCP connection to the inverter at the same time! For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Remote". @@ -70,7 +73,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re host: 192.0.2.2 # Hostname port: 1502 # Port timeout: 10s # Timeout, optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -125,7 +128,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re port: 1502 # Port timeout: 10s # Timeout, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -180,18 +183,29 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re port: 1502 # Port timeout: 10s # Timeout, optional capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `solaredge-hybrid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/solaredge-inverter.mdx b/docs/devices-next/meters/solaredge-inverter.mdx index 583d32dfcd..a540748517 100644 --- a/docs/devices-next/meters/solaredge-inverter.mdx +++ b/docs/devices-next/meters/solaredge-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarEdge Inverter - +
+
+ Only one system may access the inverter! @@ -77,11 +80,22 @@ Only one system may access the inverter! +
+
+ +
+
## Template Parameter `solaredge-inverter` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | diff --git a/docs/devices-next/meters/solarlog.mdx b/docs/devices-next/meters/solarlog.mdx index 3903900e6b..ab26f17bd0 100644 --- a/docs/devices-next/meters/solarlog.mdx +++ b/docs/devices-next/meters/solarlog.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarlog - +
+
+ We recommend to use this device for grid power values only, if no other device is available providing this data. If you have a home battery installed, please do not use this device at all for grid power values. @@ -42,6 +45,17 @@ If you have a home battery installed, please do not use this device at all for g +
+
+ +
+
## Template Parameter `solarlog` diff --git a/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx b/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx index da18c7e75f..a7454e87df 100644 --- a/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx +++ b/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarMax MAX.STORAGE / MAX.STORAGE Ultimate - +
+
+ For batter control, the "Connectivity+" function must be activated via the Solarmax support. Available from software version 3.4.4. Without activation, the function remains without effect. Grid charging is generally not available. @@ -41,7 +44,7 @@ For batter control, the "Connectivity+" function must be activated via the Solar id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -68,7 +71,7 @@ For batter control, the "Connectivity+" function must be activated via the Solar host: 192.0.2.2 # Hostname port: 502 # Port maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -95,17 +98,28 @@ For batter control, the "Connectivity+" function must be activated via the Solar host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Template Parameter `solarmax-maxstorage` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | -| `watchdog` | | Standard: `60s` | no | +| Watchdog
`watchdog` | | Standard: `60s` | no | diff --git a/docs/devices-next/meters/solarmax-solarmax-smt.mdx b/docs/devices-next/meters/solarmax-solarmax-smt.mdx index e4577948e3..ac4e3a13ec 100644 --- a/docs/devices-next/meters/solarmax-solarmax-smt.mdx +++ b/docs/devices-next/meters/solarmax-solarmax-smt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarMax SolarMax SMT - +
+
+ +
+
+ +
+
## Template Parameter `solarmax-smt` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/solarmax-sp-series-inverter.mdx b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx index ebe6c4fd3e..2a2c1f014f 100644 --- a/docs/devices-next/meters/solarmax-sp-series-inverter.mdx +++ b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarMax SP Series Inverter - +
+
+ +
+
+ +
+
## Template Parameter `senergy` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/solarwatt-energymanager-pro.mdx b/docs/devices-next/meters/solarwatt-energymanager-pro.mdx index 252a89a629..bca4fc8c03 100644 --- a/docs/devices-next/meters/solarwatt-energymanager-pro.mdx +++ b/docs/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt EnergyManager Pro - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solarwatt` diff --git a/docs/devices-next/meters/solarwatt-energymanager.mdx b/docs/devices-next/meters/solarwatt-energymanager.mdx index 7f76b2b67f..cec7c37a94 100644 --- a/docs/devices-next/meters/solarwatt-energymanager.mdx +++ b/docs/devices-next/meters/solarwatt-energymanager.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt EnergyManager - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solarwatt` diff --git a/docs/devices-next/meters/solarwatt-manager-flex.mdx b/docs/devices-next/meters/solarwatt-manager-flex.mdx index dda70e6eb1..4d59036d6a 100644 --- a/docs/devices-next/meters/solarwatt-manager-flex.mdx +++ b/docs/devices-next/meters/solarwatt-manager-flex.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt Manager flex - +
+
+ Combines data of all connected PV inverters or batteries. @@ -55,6 +58,17 @@ Combines data of all connected PV inverters or batteries. +
+
+ +
+
## Template Parameter `solarwatt-flex` diff --git a/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx index 2f82b995e7..6362688a8a 100644 --- a/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx +++ b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt MyReserve Matrix (LAN oder PowerGateway) - +
+
+ @@ -56,6 +59,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solarwatt-myreserve-matrix` diff --git a/docs/devices-next/meters/solarwatt-myreserve.mdx b/docs/devices-next/meters/solarwatt-myreserve.mdx index 3452287ef3..91a3d9c580 100644 --- a/docs/devices-next/meters/solarwatt-myreserve.mdx +++ b/docs/devices-next/meters/solarwatt-myreserve.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt MyReserve - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `solarwatt` diff --git a/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx index 6006df6843..493b3a069a 100644 --- a/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx +++ b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax Hybrid-Inverter (Cloud) - +
+
+ The Solax hybrid inverter has to be registered in the SolaxCloud. @@ -61,12 +64,23 @@ The Solax hybrid inverter has to be registered in the SolaxCloud. +
+
+ +
+
## Template Parameter `solax-hybrid-cloud` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') | | yes | -| Serial number
`serial` | https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number | | yes | +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') | | yes | +| Serial number
`serial` | https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number | | yes | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx b/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx index 58692e41bd..57834d2a3c 100644 --- a/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx +++ b/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax Hybrid X1/X3 G3/G4 - +
+
+ @@ -41,7 +44,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -65,8 +68,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional`} /> @@ -95,7 +98,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -119,8 +122,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -150,7 +153,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -174,21 +177,32 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional)`} /> +
+
+ +
+
## Template Parameter `solax` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| The inverter has a third PV input (MPPT3)
`mppt3` | | | no | -| `storageunit` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Third PV input
`mppt3` | The inverter has a third PV input (MPPT3) | | no | +| Battery storage unit index
`storageunit` | | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | | no | diff --git a/docs/devices-next/meters/solax-inverter-cloud.mdx b/docs/devices-next/meters/solax-inverter-cloud.mdx index 3ebaac7820..d6e2184487 100644 --- a/docs/devices-next/meters/solax-inverter-cloud.mdx +++ b/docs/devices-next/meters/solax-inverter-cloud.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax Inverter (Cloud) - +
+
+ The Solax inverter has to be registered in the SolaxCloud. @@ -26,11 +29,22 @@ The Solax inverter has to be registered in the SolaxCloud. usage: pv tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of \`tokenID\` here in single quotes (Example: '20241028488283838') serial: # Serial number, https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number`} /> +
+
+ +
+
## Template Parameter `solax-inverter-cloud` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') | | yes | -| Serial number
`serial` | https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number | | yes | +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Third-party Ecology (old site) or Service -> API (new site), put the value of `tokenID` here in single quotes (Example: '20241028488283838') | | yes | +| Serial number
`serial` | https://www.solaxcloud.com/ -> Device -> Inverter (new site) or Support (old site), use the registration number | | yes | diff --git a/docs/devices-next/meters/solinteng.mdx b/docs/devices-next/meters/solinteng.mdx index ec34c33155..7974b05180 100644 --- a/docs/devices-next/meters/solinteng.mdx +++ b/docs/devices-next/meters/solinteng.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solinteng - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> +
+
+ +
+
## Template Parameter `wattsonic` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `delay` | | Standard: `100ms` | no | +| Delay
`delay` | | Standard: `100ms` | no | diff --git a/docs/devices-next/meters/sonnen-comfort.mdx b/docs/devices-next/meters/sonnen-comfort.mdx index a71444e384..9778789aba 100644 --- a/docs/devices-next/meters/sonnen-comfort.mdx +++ b/docs/devices-next/meters/sonnen-comfort.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen comfort - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sonnenbatterie-eco56` diff --git a/docs/devices-next/meters/sonnen-eco-5.mdx b/docs/devices-next/meters/sonnen-eco-5.mdx index 8cc05f0f3c..483807f3e8 100644 --- a/docs/devices-next/meters/sonnen-eco-5.mdx +++ b/docs/devices-next/meters/sonnen-eco-5.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen eco 5 - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sonnenbatterie-eco56` diff --git a/docs/devices-next/meters/sonnen-eco-6.mdx b/docs/devices-next/meters/sonnen-eco-6.mdx index bddb11e02d..39023ca6fc 100644 --- a/docs/devices-next/meters/sonnen-eco-6.mdx +++ b/docs/devices-next/meters/sonnen-eco-6.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen eco 6 - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sonnenbatterie-eco56` diff --git a/docs/devices-next/meters/sonnen-oem-6-5.mdx b/docs/devices-next/meters/sonnen-oem-6-5.mdx index cf9abb4013..8f294eaa80 100644 --- a/docs/devices-next/meters/sonnen-oem-6-5.mdx +++ b/docs/devices-next/meters/sonnen-oem-6-5.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen oem 6.5 - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sonnenbatterie-eco56` diff --git a/docs/devices-next/meters/sonnen-sonnenbatterie.mdx b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx index 4ad0955e34..24c187cb97 100644 --- a/docs/devices-next/meters/sonnen-sonnenbatterie.mdx +++ b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen sonnenBatterie - +
+
+ For active battery control, the "JSON Write API" must be activated via the sonnenBatterie web interface (under Software-Integration) and the API token generated there must be entered in the battery configuration under `token`. The two operating modes supported for the sonnenBatterie are “self-consumption” (default) and “time-of-use”. The mode can be adapted to the configuration of the sonnenBatterie via the 'defaultmode' parameter. @@ -51,20 +54,31 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa usage: battery host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional)`} advanced={`meters: + token: # Token, API Token (required for active battery control) (optional)`} advanced={`meters: - name: my_battery type: template template: sonnenbatterie usage: battery host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional) + token: # Token, API Token (required for active battery control) (optional) capacity: 50 # Battery capacity (kWh), optional maxchargepower: 3300 # Maximum charge power (W), For forced charging of the battery. (optional) defaultmode: self-consumption # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. [self-consumption, time-of-use]`} /> +
+
+ +
+
## Template Parameter `sonnenbatterie` @@ -72,7 +86,7 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `8080` | no | -| `token` | API Token (required for active battery control) | | no | +| Token
`token` | API Token (required for active battery control) | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum charge power
`maxchargepower` | For forced charging of the battery. | Standard: `3300`
Einheit: W | no | | Default mode for battery control
`defaultmode` | Inverter falls back to this mode after charging the battery or after stopping discharge. | Standard: `self-consumption`
Auswahl: `self-consumption`, `time-of-use` | yes | diff --git a/docs/devices-next/meters/st-ems.mdx b/docs/devices-next/meters/st-ems.mdx index b1537aa04a..6bd31afc4f 100644 --- a/docs/devices-next/meters/st-ems.mdx +++ b/docs/devices-next/meters/st-ems.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # St-ems - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> +
+
+ +
+
## Template Parameter `wattsonic` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `delay` | | Standard: `100ms` | no | +| Delay
`delay` | | Standard: `100ms` | no | diff --git a/docs/devices-next/meters/steca-coolcept-flex.mdx b/docs/devices-next/meters/steca-coolcept-flex.mdx index 185a785d6f..4a4cdcdb91 100644 --- a/docs/devices-next/meters/steca-coolcept-flex.mdx +++ b/docs/devices-next/meters/steca-coolcept-flex.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Steca coolcept fleX - +
+
+ +
+
+ +
+
## Template Parameter `kostal-piko-mp-plus` diff --git a/docs/devices-next/meters/sungrow-sg-series-inverter.mdx b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx index 5ab5fde275..0597176918 100644 --- a/docs/devices-next/meters/sungrow-sg-series-inverter.mdx +++ b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow SG Series Inverter - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sungrow-inverter` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx index 18a23a32cd..c4816b56dd 100644 --- a/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow SH Series Hybrid Inverter - +
+
+ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmware. Older versions do not provide all required data (power, state of charge). @@ -157,12 +160,23 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw +
+
+ +
+
## Template Parameter `sungrow-hybrid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Timeout
`timeout` | | Beispiel: `10s` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/sunspec-battery-model-124.mdx b/docs/devices-next/meters/sunspec-battery-model-124.mdx index 85f8406965..b8e3f4f913 100644 --- a/docs/devices-next/meters/sunspec-battery-model-124.mdx +++ b/docs/devices-next/meters/sunspec-battery-model-124.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Battery (Model 124) - +
+
+ +
+
+ +
+
## Template Parameter `sunspec-inverter-control` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | | Maximum charge power
`maxchargerate` | For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. | Standard: `100`
Einheit: % | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/sunspec-battery-model-802.mdx b/docs/devices-next/meters/sunspec-battery-model-802.mdx index 7d01f4ab5e..5383f5fc07 100644 --- a/docs/devices-next/meters/sunspec-battery-model-802.mdx +++ b/docs/devices-next/meters/sunspec-battery-model-802.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Battery (Model 802) - +
+
+ +
+
+ +
+
## Template Parameter `sunspec-battery-control` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/sunspec-hybrid-inverter.mdx b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx index 211b4a3ea9..48dab01eea 100644 --- a/docs/devices-next/meters/sunspec-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Hybrid Inverter - +
+
+ @@ -148,12 +151,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sunspec-hybrid` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | diff --git a/docs/devices-next/meters/sunspec-inverter.mdx b/docs/devices-next/meters/sunspec-inverter.mdx index d8c23c5897..d0fa66a1b8 100644 --- a/docs/devices-next/meters/sunspec-inverter.mdx +++ b/docs/devices-next/meters/sunspec-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sunspec-inverter` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip`, `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/sunspec-meter.mdx b/docs/devices-next/meters/sunspec-meter.mdx index 5d3f06f24f..51c0e80210 100644 --- a/docs/devices-next/meters/sunspec-meter.mdx +++ b/docs/devices-next/meters/sunspec-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Meter - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sunspec-meter` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx index 852f2b63b0..c241316a32 100644 --- a/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk 3p hybrid inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `deye-hybrid-3p` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx index 76d9b81afa..db72673352 100644 --- a/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk hp3 hybrid inverter - +
+
+ @@ -64,9 +67,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -119,9 +120,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -175,7 +174,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -183,13 +182,24 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `deye-hybrid-hp3` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | -| `storageunit` | | Standard: `1` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Battery storage unit index
`storageunit` | | Standard: `1` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Standard: `20`
Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Standard: `95`
Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/sunsynk-micro-inverter.mdx b/docs/devices-next/meters/sunsynk-micro-inverter.mdx index aaddf387bc..158a3da870 100644 --- a/docs/devices-next/meters/sunsynk-micro-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk Micro inverter - +
+
+ +
+
+ +
+
## Template Parameter `deye-mi` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx index 7cd222a65f..fc0e1c29a1 100644 --- a/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk Storage (hybrid) inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `deye-storage` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/sunsynk-string-inverter.mdx b/docs/devices-next/meters/sunsynk-string-inverter.mdx index 7669e57a5a..a3fa141614 100644 --- a/docs/devices-next/meters/sunsynk-string-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-string-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk String inverter - +
+
+ +
+
+ +
+
## Template Parameter `deye-string` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/sunway.mdx b/docs/devices-next/meters/sunway.mdx index e664161b45..18dec73bcc 100644 --- a/docs/devices-next/meters/sunway.mdx +++ b/docs/devices-next/meters/sunway.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunway - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> +
+
+ +
+
## Template Parameter `wattsonic` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `delay` | | Standard: `100ms` | no | +| Delay
`delay` | | Standard: `100ms` | no | diff --git a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx index 97c52d35bf..89048a63d4 100644 --- a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx +++ b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota SML IR-reader for smartmeters e.g. Hichi - +
+
+ To be able to read the values of the smart meter for evcc correctly, the IR reader script must be changed so that the following JSON tags are generated: - **SML** as the group name of the read parameters @@ -89,6 +92,17 @@ A corresponding IR reader script looks like this: +
+
+ +
+
## Template Parameter `tasmota-sml` diff --git a/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx b/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx index e3a1683700..ec6b3f7621 100644 --- a/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx +++ b/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota Tasmota (1 Phase + SML Meter) - +
+
+ @@ -68,6 +71,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `tasmota` diff --git a/docs/devices-next/meters/tasmota-three-phase.mdx b/docs/devices-next/meters/tasmota-three-phase.mdx index e510467e69..af3536b161 100644 --- a/docs/devices-next/meters/tasmota-three-phase.mdx +++ b/docs/devices-next/meters/tasmota-three-phase.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota three phase - +
+
+ Meter channels 1,2,3 must be used. @@ -67,6 +70,17 @@ Meter channels 1,2,3 must be used. +
+
+ +
+
## Template Parameter `tasmota-3p` diff --git a/docs/devices-next/meters/tesla-powerwall.mdx b/docs/devices-next/meters/tesla-powerwall.mdx index 81e74e65f6..5dd371f575 100644 --- a/docs/devices-next/meters/tesla-powerwall.mdx +++ b/docs/devices-next/meters/tesla-powerwall.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla Powerwall - +
+
+ To use the optional battery control you need to generate a `refresh` token for communicating with the Tesla API. @@ -32,18 +35,8 @@ The following apps allow to create the token: usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: - - name: my_grid - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional)`} /> @@ -55,18 +48,8 @@ The following apps allow to create the token: usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: - - name: my_pv - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional)`} /> @@ -78,21 +61,32 @@ The following apps allow to create the token: usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: - name: my_battery type: template template: tesla-powerwall usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> +
+
+ +
+
## Template Parameter `tesla-powerwall` @@ -100,8 +94,8 @@ The following apps allow to create the token: |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Password
`password` | Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. | | yes | -| `refreshToken` | | | no | -| `siteId` | optional product identifier of the energy site, use to override autodectction | | no | +| Refresh token
`refreshToken` | | | no | +| Site ID
`siteId` | optional product identifier of the energy site, use to override autodectction | | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | | Maximum charge
`maxsoc` | Upper limit when charging the battery from the grid | Beispiel: `95`
Einheit: % | no | diff --git a/docs/devices-next/meters/tibber-pulse.mdx b/docs/devices-next/meters/tibber-pulse.mdx index bcb4e8abc4..ed245cfa67 100644 --- a/docs/devices-next/meters/tibber-pulse.mdx +++ b/docs/devices-next/meters/tibber-pulse.mdx @@ -9,23 +9,37 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tibber Pulse - +
+
+ + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional`} /> +
+
+ +
+
## Template Parameter `tibber-pulse` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | | Beispiel: `5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE` | yes | -| `homeid` | | Beispiel: `96a14971-525a-4420-aae9-e5aedaa129ff` | no | +| Token
`token` | | Beispiel: `5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE` | yes | +| Home ID
`homeid` | | Beispiel: `96a14971-525a-4420-aae9-e5aedaa129ff` | no | diff --git a/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx index 2c9f82bdcc..060a54b5f6 100644 --- a/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx +++ b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link H-Series Smart Plug - +
+
+ +
+
+ +
+
## Template Parameter `tplink` diff --git a/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx index c62d8f17cc..3cf65ae1bf 100644 --- a/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx +++ b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link Tapo P-Series Smart Plug - +
+
+ +
+
+ +
+
## Template Parameter `tapo` diff --git a/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx b/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx index 1d0a0f9f08..68f71d7e6d 100644 --- a/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx +++ b/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TQ Energy Manager EM2xx/EM3xx - +
+
+ +
+
+ +
+
## Template Parameter `tq-em` diff --git a/docs/devices-next/meters/tq-energy-manager-em420.mdx b/docs/devices-next/meters/tq-energy-manager-em420.mdx index 6391d106ac..21bf495ca8 100644 --- a/docs/devices-next/meters/tq-energy-manager-em420.mdx +++ b/docs/devices-next/meters/tq-energy-manager-em420.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TQ Energy Manager EM420 - +
+
+ Data Endpoint (optional) token: ey... # Access token, Access token for EM420 (Create in Profile -> Access tokens)`} /> +
+
+ +
+
## Template Parameter `tq-em420` @@ -30,6 +44,6 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `80` | no | -| API Device Path
`device` | JSON-API -> Data Endpoint | Standard: `local` | no | -| Access token
`token` | Access token for EM420 (Create in Profile -> Access tokens) | Beispiel: `ey...` | yes | +| API Device Path
`device` | JSON-API -> Data Endpoint | Standard: `local` | no | +| Access token
`token` | Access token for EM420 (Create in Profile -> Access tokens) | Beispiel: `ey...` | yes | diff --git a/docs/devices-next/meters/varta-element.mdx b/docs/devices-next/meters/varta-element.mdx index 8ab28b64be..7377527786 100644 --- a/docs/devices-next/meters/varta-element.mdx +++ b/docs/devices-next/meters/varta-element.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # VARTA element - +
+
+ PV only available with PV sensor @@ -59,6 +62,17 @@ PV only available with PV sensor +
+
+ +
+
## Template Parameter `varta` diff --git a/docs/devices-next/meters/varta-pulse-neo.mdx b/docs/devices-next/meters/varta-pulse-neo.mdx index 8b28e3a402..e3acc11ab0 100644 --- a/docs/devices-next/meters/varta-pulse-neo.mdx +++ b/docs/devices-next/meters/varta-pulse-neo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # VARTA pulse neo - +
+
+ PV only available with PV sensor @@ -59,6 +62,17 @@ PV only available with PV sensor +
+
+ +
+
## Template Parameter `varta` diff --git a/docs/devices-next/meters/varta-pulse.mdx b/docs/devices-next/meters/varta-pulse.mdx index abc4aa0308..251514e49c 100644 --- a/docs/devices-next/meters/varta-pulse.mdx +++ b/docs/devices-next/meters/varta-pulse.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # VARTA pulse - +
+
+ PV only available with PV sensor @@ -59,6 +62,17 @@ PV only available with PV sensor +
+
+ +
+
## Template Parameter `varta` diff --git a/docs/devices-next/meters/victron-em24.mdx b/docs/devices-next/meters/victron-em24.mdx index 82cce12e81..0380d187b8 100644 --- a/docs/devices-next/meters/victron-em24.mdx +++ b/docs/devices-next/meters/victron-em24.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EM24 - +
+
+ EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Ethernet connection, the definitions are not compatible. @@ -63,10 +66,21 @@ EM24 with RS-485 connection. Use the EM24_E1 if you have an EM24_E1 with Etherne +
+
+ +
+
## Template Parameter `cg-em24` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/victron-em24_e1.mdx b/docs/devices-next/meters/victron-em24_e1.mdx index ca609c0e80..0d6e7a0bc5 100644 --- a/docs/devices-next/meters/victron-em24_e1.mdx +++ b/docs/devices-next/meters/victron-em24_e1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EM24_E1 - +
+
+ EM24_E1 with Ethernet connection. Use the EM24 if you have an EM24 with RS-485 connection, the definitions are not compatible. The firmware version should be at least version 1.8.3, you can find this version here: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) @@ -50,10 +53,21 @@ The firmware version should be at least version 1.8.3, you can find this version +
+
+ +
+
## Template Parameter `cg-em24_e1` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | diff --git a/docs/devices-next/meters/victron-em530-em540.mdx b/docs/devices-next/meters/victron-em530-em540.mdx index ccbc77e50c..19085770b4 100644 --- a/docs/devices-next/meters/victron-em530-em540.mdx +++ b/docs/devices-next/meters/victron-em530-em540.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EM530/EM540 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt3xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/victron-energy.mdx b/docs/devices-next/meters/victron-energy.mdx index 009d9a5fe2..692b270154 100644 --- a/docs/devices-next/meters/victron-energy.mdx +++ b/docs/devices-next/meters/victron-energy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron Energy - +
+
+ For grid usage, a grid meter VRM instance is require to enabled load management. @@ -27,16 +30,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional)`} advanced={`meters: - - name: my_grid - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + meterid: # Grid meter VRM instance, Can be read out in VRM portal or via remoteUI. (optional)`} /> @@ -54,9 +48,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. usage: pv host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -80,6 +72,17 @@ For grid usage, a grid meter VRM instance is require to enabled load management. +
+
+ +
+
## Template Parameter `victron-energy` @@ -87,7 +90,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `502` | no | -| `meterid` | Grid meter VRM instance- can be read out in VRM portal or via remoteUI. | | no | +| Grid meter VRM instance
`meterid` | Can be read out in VRM portal or via remoteUI. | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Maximum AC power of the hybrid inverter
`maxacpower` | | Beispiel: `5000`
Einheit: W | no | | Minimum charge
`minsoc` | Lower limit when discharging the battery in normal operation | Beispiel: `25`
Einheit: % | no | diff --git a/docs/devices-next/meters/victron-et340.mdx b/docs/devices-next/meters/victron-et340.mdx index 718a79e59f..3986b664f4 100644 --- a/docs/devices-next/meters/victron-et340.mdx +++ b/docs/devices-next/meters/victron-et340.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron ET340 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `cg-emt3xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | diff --git a/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx index b0fba6d670..ca17c6ba18 100644 --- a/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx +++ b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -9,25 +9,39 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkszähler HTTP API, Import & Export - +
+
+ + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID`} /> +
+
+ +
+
## Template Parameter `volkszaehler-importexport` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| URL of the middleware's "data" context
`url` | The URL is for example: http://zaehler.network.local:8080/api/data | | no | -| `importuuid` | | | yes | -| `exportuuid` | | | yes | +| Middleware URL
`url` | | Beispiel: `http://zaehler.network.local:8080/api/data` | no | +| Import UUID
`importuuid` | | | yes | +| Export UUID
`exportuuid` | | | yes | diff --git a/docs/devices-next/meters/volkszahler-http-api.mdx b/docs/devices-next/meters/volkszahler-http-api.mdx index 8495b8a2da..11d897da09 100644 --- a/docs/devices-next/meters/volkszahler-http-api.mdx +++ b/docs/devices-next/meters/volkszahler-http-api.mdx @@ -9,23 +9,37 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkszähler HTTP API - +
+
+ + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID`} /> +
+
+ +
+
## Template Parameter `volkszaehler-http` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| URL of the middleware's "data" context
`url` | Example: http://zaehler.network.local:8080/api/data | | no | -| `uuid` | | | yes | +| Middleware URL
`url` | | Beispiel: `http://zaehler.network.local:8080/api/data` | no | +| UUID
`uuid` | | | yes | diff --git a/docs/devices-next/meters/volkszahler-websocket-api.mdx b/docs/devices-next/meters/volkszahler-websocket-api.mdx index ae212f1525..cbb39318eb 100644 --- a/docs/devices-next/meters/volkszahler-websocket-api.mdx +++ b/docs/devices-next/meters/volkszahler-websocket-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkszähler WebSocket API - +
+
+ + uuid: # UUID`} /> +
+
+ +
+
## Template Parameter `volkszaehler-ws` @@ -29,5 +43,5 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `8082` | no | -| `uuid` | | | yes | +| UUID
`uuid` | | | yes | diff --git a/docs/devices-next/meters/vzlogger.mdx b/docs/devices-next/meters/vzlogger.mdx index 22e41feb42..d4d18c7214 100644 --- a/docs/devices-next/meters/vzlogger.mdx +++ b/docs/devices-next/meters/vzlogger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # vzlogger - +
+
+ +
+
+ +
+
## Template Parameter `vzlogger` @@ -47,16 +61,16 @@ import TabItem from '@theme/TabItem'; |-----------|-------------|-------|----------| | IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | | Port
`port` | | Standard: `8081` | no | -| `uuid` | | | yes | +| UUID
`uuid` | | | yes | | Scale factor
`scale` | Multiply by this value | Standard: `1` | no | -| The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0)
`l1currentuuid` | | | no | -| The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0)
`l2currentuuid` | | | no | -| The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0)
`l3currentuuid` | | | no | -| The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0)
`l1poweruuid` | | | no | -| The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0)
`l2poweruuid` | | | no | -| The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0)
`l3poweruuid` | | | no | -| The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0)
`l1voltageuuid` | | | no | -| The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0)
`l2voltageuuid` | | | no | -| The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0)
`l3voltageuuid` | | | no | +| Current on phase 1
`l1currentuuid` | The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0) | | no | +| Current on phase 2
`l2currentuuid` | The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0) | | no | +| Current on phase 3
`l3currentuuid` | The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0) | | no | +| Power on phase 1
`l1poweruuid` | The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0) | | no | +| Power on phase 2
`l2poweruuid` | The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0) | | no | +| Power on phase 3
`l3poweruuid` | The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0) | | no | +| Voltage on phase 1
`l1voltageuuid` | The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0) | | no | +| Voltage on phase 2
`l2voltageuuid` | The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0) | | no | +| Voltage on phase 3
`l3voltageuuid` | The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0) | | no | | Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `1s`
Beispiel: `5m` | no | diff --git a/docs/devices-next/meters/wago-879-30xx.mdx b/docs/devices-next/meters/wago-879-30xx.mdx index ead445d006..34e5e731b2 100644 --- a/docs/devices-next/meters/wago-879-30xx.mdx +++ b/docs/devices-next/meters/wago-879-30xx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wago 879-30xx - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `wago-879-30xx` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/wattsonic.mdx b/docs/devices-next/meters/wattsonic.mdx index 113b2155ff..49e45eb806 100644 --- a/docs/devices-next/meters/wattsonic.mdx +++ b/docs/devices-next/meters/wattsonic.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wattsonic - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> +
+
+ +
+
## Template Parameter `wattsonic` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `delay` | | Standard: `100ms` | no | +| Delay
`delay` | | Standard: `100ms` | no | diff --git a/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx index 2d24554ffc..d64def5380 100644 --- a/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM110-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron-sdm220_230` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx index 11ee8a4924..af44e1e367 100644 --- a/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM111-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron-sdm220_230` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx index 5c88cff21f..fb30b0ad7a 100644 --- a/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM120-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx index 71272265e3..5e97dbf67e 100644 --- a/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM122-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `eastron` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | diff --git a/docs/devices-next/meters/youless-energy-monitor.mdx b/docs/devices-next/meters/youless-energy-monitor.mdx index c027086f1a..f9bd671196 100644 --- a/docs/devices-next/meters/youless-energy-monitor.mdx +++ b/docs/devices-next/meters/youless-energy-monitor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Youless Energy Monitor - +
+
+ An externally connected S0 generation meter is required to record the solar production. @@ -39,6 +42,17 @@ An externally connected S0 generation meter is required to record the solar prod +
+
+ +
+
## Template Parameter `youless` diff --git a/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx index eda4fd7870..95bde4cbab 100644 --- a/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx +++ b/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ZCS Azzurro Hybrid Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sofarsolar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/zcs-azzurro-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-inverter.mdx index 36237710be..46f44f9482 100644 --- a/docs/devices-next/meters/zcs-azzurro-inverter.mdx +++ b/docs/devices-next/meters/zcs-azzurro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ZCS Azzurro Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Template Parameter `sofarsolar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/zendure-hyper-2000.mdx b/docs/devices-next/meters/zendure-hyper-2000.mdx index 7e813e31be..546f91641e 100644 --- a/docs/devices-next/meters/zendure-hyper-2000.mdx +++ b/docs/devices-next/meters/zendure-hyper-2000.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zendure Hyper 2000 - +
+
+ @@ -22,9 +25,9 @@ import TabItem from '@theme/TabItem'; type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional`} /> @@ -35,30 +38,41 @@ import TabItem from '@theme/TabItem'; type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional`} advanced={`meters: - name: my_battery type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional capacity: 2 # Battery capacity (kWh), optional`} /> +
+
+ +
+
## Template Parameter `zendure` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `account` | | Beispiel: `dev@zendure.com` | yes | -| `serial` | You can find this in the Zendure App in the settings of the device | Beispiel: `VU5D99F74021B04` | yes | -| `region` | | Standard: `EU`
Auswahl: `EU`, `Global` | yes | +| Account ID
`account` | | Beispiel: `dev@zendure.com` | yes | +| Serial
`serial` | You can find this in the Zendure App in the settings of the device | Beispiel: `VU5D99F74021B04` | yes | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `Global` | yes | | Timeout
`timeout` | | Beispiel: `10s` | no | | Battery capacity
`capacity` | | Standard: `2`
Beispiel: `50`
Einheit: kWh | no | diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx index e1452aee57..4f9a1386a9 100644 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zuidwijk SlimmeLezer(+) in Luxembourg - +
+
+ Slimmelezer devices use different sensor names in Luxembourg. @@ -23,6 +26,17 @@ Slimmelezer devices use different sensor names in Luxembourg. template: slimmelezer-luxembourg usage: grid host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `slimmelezer-luxembourg` diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx index 13d071c614..d8c559670a 100644 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zuidwijk SlimmeLezer(+) V2 - +
+
+ More recent slimmelezer devices use a different configuration. Try this template if the other one fails. @@ -23,6 +26,17 @@ More recent slimmelezer devices use a different configuration. Try this template template: slimmelezer-V2 usage: grid host: 192.0.2.2 # IP address or hostname`} /> +
+
+ +
+
## Template Parameter `slimmelezer-V2` diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx index 68c0c71ab7..d1d844e41e 100644 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zuidwijk SlimmeLezer(+) - +
+
+ +
+
+ +
+
## Template Parameter `slimmelezer` diff --git a/docs/devices-next/tariffs/amber-electric.mdx b/docs/devices-next/tariffs/amber-electric.mdx index a59237258e..f73bcfd2aa 100644 --- a/docs/devices-next/tariffs/amber-electric.mdx +++ b/docs/devices-next/tariffs/amber-electric.mdx @@ -9,35 +9,49 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amber Electric - +
+
+ +
+
+ +
+
## Template Parameter `amber` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | | | no | -| `siteid` | | | no | -| `channel` | | | no | +| Token
`token` | | | no | +| Site ID
`siteid` | | | no | +| Channel
`channel` | | | no | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/awattar.mdx b/docs/devices-next/tariffs/awattar.mdx index 30e88ded82..6efe4038bb 100644 --- a/docs/devices-next/tariffs/awattar.mdx +++ b/docs/devices-next/tariffs/awattar.mdx @@ -9,29 +9,43 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Awattar - +
+
+ +
+
+ +
+
## Template Parameter `awattar` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `region` | | Beispiel: `AT`
Auswahl: `DE`, `AT` | yes | +| Region
`region` | | Beispiel: `AT`
Auswahl: `DE`, `AT` | yes | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx index 8d619bd385..20a5c85031 100644 --- a/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx +++ b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Electricity Maps Commercial API - +
+
+ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. @@ -22,14 +25,25 @@ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps type: template template: electricitymaps uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) address - token: - zone: DE # see https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, see https://api.electricitymap.org/v3/zones`} /> +
+
+ +
+
## Template Parameter `electricitymaps` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | URI
`uri` | HTTP(S) address | Beispiel: `https://api-access.electricitymaps.com/2w...1g/` | yes | -| `token` | | | yes | -| `zone` | see https://api.electricitymap.org/v3/zones | Beispiel: `DE` | yes | +| Token
`token` | | | yes | +| Zone
`zone` | see https://api.electricitymap.org/v3/zones | Beispiel: `DE` | yes | diff --git a/docs/devices-next/tariffs/electricity-maps-free-api.mdx b/docs/devices-next/tariffs/electricity-maps-free-api.mdx index 0b5d69ed1e..0013da1fba 100644 --- a/docs/devices-next/tariffs/electricity-maps-free-api.mdx +++ b/docs/devices-next/tariffs/electricity-maps-free-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Electricity Maps Free API - +
+
+ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps.com). The 'Free Personal Tier' unfortunately does not include forecast data. You'll need a commercial account from [portal.electricitymaps.com](https://portal.electricitymaps.com). Free trial available. @@ -21,13 +24,24 @@ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps co2: type: template template: electricitymaps-free - token: - zone: DE # see https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, see https://api.electricitymap.org/v3/zones`} /> +
+
+ +
+
## Template Parameter `electricitymaps-free` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | | | yes | -| `zone` | see https://api.electricitymap.org/v3/zones | Beispiel: `DE` | yes | +| Token
`token` | | | yes | +| Zone
`zone` | see https://api.electricitymap.org/v3/zones | Beispiel: `DE` | yes | diff --git a/docs/devices-next/tariffs/energinet.mdx b/docs/devices-next/tariffs/energinet.mdx index 4ab2487b35..4691b84e55 100644 --- a/docs/devices-next/tariffs/energinet.mdx +++ b/docs/devices-next/tariffs/energinet.mdx @@ -9,29 +9,43 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Energinet - +
+
+ +
+
+ +
+
## Template Parameter `energinet` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `region` | | Beispiel: `dk1`
Auswahl: `dk1`, `dk2` | yes | +| Region
`region` | | Beispiel: `dk1`
Auswahl: `dk1`, `dk2` | yes | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/enever.mdx b/docs/devices-next/tariffs/enever.mdx index 288cbdfaee..6970506e3a 100644 --- a/docs/devices-next/tariffs/enever.mdx +++ b/docs/devices-next/tariffs/enever.mdx @@ -9,35 +9,49 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Enever - +
+
+ + interval: 3h # Interval, optional`} /> +
+
+ +
+
## Template Parameter `enever` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | | | yes | -| `provider` | | Auswahl: ``, `AA`, `AIP`, `ANWB`, `BE`
, `EE`, `EN`, `EVO`, `EZ`, `FR`
, `GSL`, `MDE`, `NE`, `PE`, `TI`
, `VDB`, `VON`, `WE`, `ZG`, `ZP`
| yes | +| Token
`token` | | | yes | +| Provider
`provider` | | Auswahl: ``, `AA`, `AIP`, `ANWB`, `BE`
, `EE`, `EN`, `EVO`, `EZ`, `FR`
, `GSL`, `MDE`, `NE`, `PE`, `TI`
, `VDB`, `VON`, `WE`, `ZG`, `ZP`
| yes | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | -| `interval` | | Standard: `3h` | no | +| Interval
`interval` | | Standard: `3h` | no | diff --git a/docs/devices-next/tariffs/entso-e.mdx b/docs/devices-next/tariffs/entso-e.mdx index 539099674c..b35a19c8a9 100644 --- a/docs/devices-next/tariffs/entso-e.mdx +++ b/docs/devices-next/tariffs/entso-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ENTSO-E - +
+
+ Day-ahead prices for the European electricity market. See https://transparency.entsoe.eu for more information. Basis for many dynamic tariffs. @@ -22,23 +25,34 @@ Basis for many dynamic tariffs. grid: type: template template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: + securitytoken: # Security token, Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: grid: type: template template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +
+
+ +
+
## Template Parameter `entsoe` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `securitytoken` | Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation | | no | -| `domain` | see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas | Beispiel: `BZN\|DE-LU` | no | +| Security token
`securitytoken` | Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation | | no | +| Domain
`domain` | see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas | Beispiel: `BZN\|DE-LU` | no | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/forecast-solar.mdx b/docs/devices-next/tariffs/forecast-solar.mdx index 2ac10302c2..576dc50e20 100644 --- a/docs/devices-next/tariffs/forecast-solar.mdx +++ b/docs/devices-next/tariffs/forecast-solar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Forecast.Solar - +
+
+ [forecast.solar](https://forecast.solar) can be used for free. Paid plans can also be used by specifying an API key. @@ -35,8 +38,19 @@ import TabItem from '@theme/TabItem'; kwp: 9.8 # Maximum generator power (kWp) az: 180 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizon, Simulates terrain shadows, [more information](https://doc.forecast.solar/horizon) (optional) - apikey: # API key, optional - interval: 1h # optional`} /> + apikey: # API Key, optional + interval: 1h # Interval, optional`} /> +
+
+ +
+
## Template Parameter `forecast-solar` @@ -48,6 +62,6 @@ import TabItem from '@theme/TabItem'; | Maximum generator power
`kwp` | | Beispiel: `9.8`
Einheit: kWp | yes | | Azimuth
`az` | -180 = north, -90 = east, 0 = south, 90 = west, 180 = north | Beispiel: `180` | yes | | Horizon
`horizon` | Simulates terrain shadows, \[more information\](https://doc.forecast.solar/horizon) | Beispiel: `0,0,15,30,45,60,60,60,45,30,15,0` | no | -| API key
`apikey` | | | no | -| `interval` | | Standard: `1h` | no | +| API Key
`apikey` | | | no | +| Interval
`interval` | | Standard: `1h` | no | diff --git a/docs/devices-next/tariffs/fraunhofer-ise.mdx b/docs/devices-next/tariffs/fraunhofer-ise.mdx index 258fc4ddf4..ecdda8254d 100644 --- a/docs/devices-next/tariffs/fraunhofer-ise.mdx +++ b/docs/devices-next/tariffs/fraunhofer-ise.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fraunhofer ISE - +
+
+ Day-ahead forecast of energy prices (per kWh) on the exchange. No prior registration for https://api.energy-charts.info/ necessary. Can be used for dynamic electricity tariffs, for example, where the supplier does not yet offer a price forecast on the customer interface. @@ -21,20 +24,31 @@ Day-ahead forecast of energy prices (per kWh) on the exchange. No prior registra grid: type: template template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: + bzn: DE-LU # Bidding zone, see https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: grid: type: template template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Bidding zone, see https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +
+
+ +
+
## Template Parameter `energy-charts-api` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `bzn` | Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get | Standard: `DE-LU`
Auswahl: `AT`, `BE`, `CH`, `CZ`, `DE-LU`
, `DE-AT-LU`, `DK1`, `DK2`, `FR`, `HU`
, `IT-NORTH`, `NL`, `NO2`, `PL`, `SE4`
, `SI` | yes | +| Bidding zone
`bzn` | see https://api.energy-charts.info/#/prices/day_ahead_price_price_get | Standard: `DE-LU`
Auswahl: `AT`, `BE`, `CH`, `CZ`, `DE-LU`
, `DE-AT-LU`, `DK1`, `DK2`, `FR`, `HU`
, `IT-NORTH`, `NL`, `NO2`, `PL`, `SE4`
, `SI` | yes | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/green-grid-compass.mdx b/docs/devices-next/tariffs/green-grid-compass.mdx index c0b6d16c72..eef8bc2a03 100644 --- a/docs/devices-next/tariffs/green-grid-compass.mdx +++ b/docs/devices-next/tariffs/green-grid-compass.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Green Grid Compass - +
+
+ European CO₂ intensity data from [greengrid-compass.eu](https://www.greengrid-compass.eu). Provides forecasts for the next hours and is free of charge after registration. @@ -23,6 +26,17 @@ European CO₂ intensity data from [greengrid-compass.eu](https://www.greengrid- template: green-grid-compass apiKey: # API Key, Create an app in https://api-portal.eco2grid.com and copy the key zone: DE_LU # Zone code, [BE, DE_LU]`} /> +
+
+ +
+
## Template Parameter `green-grid-compass` diff --git a/docs/devices-next/tariffs/groupe-e-vario-plus.mdx b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx index 0f662fe55f..6cbba1ac06 100644 --- a/docs/devices-next/tariffs/groupe-e-vario-plus.mdx +++ b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Groupe E Vario Plus - +
+
+ +
+
+ +
+
## Template Parameter `groupe-e` diff --git a/docs/devices-next/tariffs/grunstromindex.mdx b/docs/devices-next/tariffs/grunstromindex.mdx index 7fbe4e49d3..af0df49b25 100644 --- a/docs/devices-next/tariffs/grunstromindex.mdx +++ b/docs/devices-next/tariffs/grunstromindex.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Grünstromindex - +
+
+ Regional emission data from https://gruenstromindex.de @@ -21,13 +24,24 @@ Regional emission data from https://gruenstromindex.de co2: type: template template: grünstromindex - zip: - token: # Token for accessing the API from https://console.corrently.io (optional)`} /> + zip: # ZIP code + token: # Token, Token for accessing the API from https://console.corrently.io (optional)`} /> +
+
+ +
+
## Template Parameter `grünstromindex` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `zip` | | | yes | -| `token` | Token for accessing the API from https://console.corrently.io | | no | +| ZIP code
`zip` | | | yes | +| Token
`token` | Token for accessing the API from https://console.corrently.io | | no | diff --git a/docs/devices-next/tariffs/national-grid-eso.mdx b/docs/devices-next/tariffs/national-grid-eso.mdx index e5979d741f..0e34302899 100644 --- a/docs/devices-next/tariffs/national-grid-eso.mdx +++ b/docs/devices-next/tariffs/national-grid-eso.mdx @@ -9,22 +9,36 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # National Grid ESO - +
+
+ + region: 1 # Region, Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Postcode, Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. (optional)`} /> +
+
+ +
+
## Template Parameter `ngeso` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `region` | Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list | Beispiel: `1` | no | -| `postalcode` | Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. | Beispiel: `SW1` | no | +| Region
`region` | Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list | Beispiel: `1` | no | +| Postcode
`postalcode` | Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. | Beispiel: `SW1` | no | diff --git a/docs/devices-next/tariffs/nordpool-spot-prices.mdx b/docs/devices-next/tariffs/nordpool-spot-prices.mdx index 0257bf98cc..0234f8f0b7 100644 --- a/docs/devices-next/tariffs/nordpool-spot-prices.mdx +++ b/docs/devices-next/tariffs/nordpool-spot-prices.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nordpool spot prices - +
+
+ Nordpool spot prices in day-ahead market for all markets in the Nordpool region. @@ -21,23 +24,34 @@ Nordpool spot prices in day-ahead market for all markets in the Nordpool region. grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Currency, [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Currency, [DKK, EUR, NOK, PLN, RON, SEK] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +
+
+ +
+
## Template Parameter `nordpool` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `region` | | Beispiel: `GER`
Auswahl: `EE`, `LT`, `LV`, `AT`, `BE`
, `FR`, `GER`, `NL`, `PL`, `DK1`
, `DK2`, `FI`, `NO1`, `NO2`, `NO3`
, `NO4`, `NO5`, `SE1`, `SE2`, `SE3`
, `SE4`, `TEL`, `SYS` | no | -| `currency` | | Standard: `EUR`
Auswahl: `DKK`, `EUR`, `NOK`, `PLN`, `RON`, `SEK` | yes | +| Region
`region` | | Beispiel: `GER`
Auswahl: `EE`, `LT`, `LV`, `AT`, `BE`
, `FR`, `GER`, `NL`, `PL`, `DK1`
, `DK2`, `FI`, `NO1`, `NO2`, `NO3`
, `NO4`, `NO5`, `SE1`, `SE2`, `SE3`
, `SE4`, `TEL`, `SYS` | no | +| Currency
`currency` | | Standard: `EUR`
Auswahl: `DKK`, `EUR`, `NOK`, `PLN`, `RON`, `SEK` | yes | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/octopus-energy-api.mdx b/docs/devices-next/tariffs/octopus-energy-api.mdx index 7a0090081e..8c5546faaf 100644 --- a/docs/devices-next/tariffs/octopus-energy-api.mdx +++ b/docs/devices-next/tariffs/octopus-energy-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Octopus Energy API - +
+
+ You can get the API key in the Octopus portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access @@ -21,13 +24,24 @@ You can get the API key in the Octopus portal https://octopus.energy/dashboard/n grid: type: template template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional)`} /> + apiKey: # API Key + accountNumber: X-XXXXXXXX # Account Number, Only required if you have multiple accounts. (optional)`} /> +
+
+ +
+
## Template Parameter `octopus-api` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `apiKey` | Octopus Energy API Key. | | yes | -| `accountNumber` | Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. | | no | +| API Key
`apiKey` | | | yes | +| Account Number
`accountNumber` | Only required if you have multiple accounts. | Beispiel: `X-XXXXXXXX` | no | diff --git a/docs/devices-next/tariffs/octopus-energy-product-code.mdx b/docs/devices-next/tariffs/octopus-energy-product-code.mdx index 019ceb4516..9c9f4f233d 100644 --- a/docs/devices-next/tariffs/octopus-energy-product-code.mdx +++ b/docs/devices-next/tariffs/octopus-energy-product-code.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Octopus Energy Product Code - +
+
+ + productCode: AGILE-FLEX-22-11-25 # Product Code, The tariff code for your energy contract. Make sure this is set to your import tariff code. + region: # Region, The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Direct debit tariff, Use Direct Debit tariff rates. (optional)`} /> +
+
+ +
+
## Template Parameter `octopus-productcode` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `productCode` | The tariff code for your energy contract. Make sure this is set to your import tariff code. | Beispiel: `AGILE-FLEX-22-11-25` | yes | -| `region` | The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ | Auswahl: `A`, `B`, `C`, `D`, `E`
, `F`, `G`, `H`, `J`, `K`
, `L`, `M`, `N`, `P` | yes | -| `directDebit` | Use Direct Debit tariff rates. | Standard: `true` | no | +| Product Code
`productCode` | The tariff code for your energy contract. Make sure this is set to your import tariff code. | Beispiel: `AGILE-FLEX-22-11-25` | yes | +| Region
`region` | The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ | Auswahl: `A`, `B`, `C`, `D`, `E`
, `F`, `G`, `H`, `J`, `K`
, `L`, `M`, `N`, `P` | yes | +| Direct debit tariff
`directDebit` | Use Direct Debit tariff rates. | Standard: `true` | no | diff --git a/docs/devices-next/tariffs/open-meteo.mdx b/docs/devices-next/tariffs/open-meteo.mdx index e77c9935f4..2672e3444f 100644 --- a/docs/devices-next/tariffs/open-meteo.mdx +++ b/docs/devices-next/tariffs/open-meteo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Open-Meteo - +
+
+ Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open-source weather API and offers free access for non-commercial use. No API key required. @@ -40,7 +43,18 @@ Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open- efficiency: 100 # Efficiency [%], optional alphatemp: -0.004 # Temperature coefficient, optional rossmodel: 0.0342 # Cooling type [Ross Model], Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional`} /> + interval: 1h # Interval, optional`} /> +
+
+ +
+
## Template Parameter `open-meteo` @@ -57,5 +71,5 @@ Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open- | Efficiency \[%\]
`efficiency` | | Standard: `100` | no | | Temperature coefficient
`alphatemp` | | Standard: `-0.004` | no | | Cooling type \[Ross Model\]
`rossmodel` | Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) \[Paper\](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) | Standard: `0.0342` | no | -| `interval` | | Standard: `1h` | no | +| Interval
`interval` | | Standard: `1h` | no | diff --git a/docs/devices-next/tariffs/ostrom.mdx b/docs/devices-next/tariffs/ostrom.mdx index 040affa0d2..8be10c196f 100644 --- a/docs/devices-next/tariffs/ostrom.mdx +++ b/docs/devices-next/tariffs/ostrom.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ostrom - +
+
+ Create a 'Production Client' in the Ostrom developer portal: https://developer.ostrom-api.io/ @@ -21,15 +24,26 @@ Create a 'Production Client' in the Ostrom developer portal: https://developer.o grid: type: template template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Only required if multiple contracts belong to the same user (optional)`} /> + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # Client ID + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a # Client Secret + contract: 100523456 # Contract number, Only required if multiple contracts belong to the same user (optional)`} /> +
+
+ +
+
## Template Parameter `ostrom` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `clientid` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | yes | -| `clientsecret` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a` | yes | -| `contract` | Only required if multiple contracts belong to the same user | Beispiel: `100523456` | no | +| Client ID
`clientid` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | yes | +| Client Secret
`clientsecret` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a` | yes | +| Contract number
`contract` | Only required if multiple contracts belong to the same user | Beispiel: `100523456` | no | diff --git a/docs/devices-next/tariffs/pun-orario.mdx b/docs/devices-next/tariffs/pun-orario.mdx index 6233268936..33d6ff9da7 100644 --- a/docs/devices-next/tariffs/pun-orario.mdx +++ b/docs/devices-next/tariffs/pun-orario.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # PUN Orario - +
+
+ Price data from https://www.mercatoelettrico.org/it/. Often used for feeding into the grid. @@ -27,6 +30,17 @@ Price data from https://www.mercatoelettrico.org/it/. Often used for feeding int charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +
+
+ +
+
## Template Parameter `pun` diff --git a/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx index 81bf2b8fa6..ff6b6db802 100644 --- a/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx +++ b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SmartEnergy smartCONTROL - +
+
+ +
+
+ +
+
## Template Parameter `smartenergy` diff --git a/docs/devices-next/tariffs/solcast.mdx b/docs/devices-next/tariffs/solcast.mdx index 1a855b2064..89282cee7d 100644 --- a/docs/devices-next/tariffs/solcast.mdx +++ b/docs/devices-next/tariffs/solcast.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solcast - +
+
+ Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) account. The free "Home User" tier is often sufficient for private use. This plan has an API limit of 10 requests per day. @@ -21,24 +24,35 @@ Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) acc solar: - type: template template: solcast - site: # ressource ID of your site - token: # Solcast API Token`} advanced={`tariffs: + site: # Ressource ID of your site + token: # API Token`} advanced={`tariffs: solar: - type: template template: solcast - site: # ressource ID of your site - token: # Solcast API Token - from: # Start time of data retrieval, specified in full hours, e.g. "6" (optional) - to: # End time of data retrieval, specified in full hours, e.g. "20" (optional) - interval: 3h # optional`} /> + site: # Ressource ID of your site + token: # API Token + from: # Start time, Start time of data retrieval, specified in full hours, e.g. "6" (optional) + to: # End time, End time of data retrieval, specified in full hours, e.g. "20" (optional) + interval: 3h # Interval, optional`} /> +
+
+ +
+
## Template Parameter `solcast` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `site` | ressource ID of your site | | yes | -| `token` | Solcast API Token | | yes | -| `from` | Start time of data retrieval, specified in full hours, e.g. "6" | | no | -| `to` | End time of data retrieval, specified in full hours, e.g. "20" | | no | -| `interval` | | Standard: `3h` | no | +| Ressource ID of your site
`site` | | | yes | +| API Token
`token` | | | yes | +| Start time
`from` | Start time of data retrieval, specified in full hours, e.g. "6" | | no | +| End time
`to` | End time of data retrieval, specified in full hours, e.g. "20" | | no | +| Interval
`interval` | | Standard: `3h` | no | diff --git a/docs/devices-next/tariffs/spotty-energie.mdx b/docs/devices-next/tariffs/spotty-energie.mdx index 91596f7cf2..47268540de 100644 --- a/docs/devices-next/tariffs/spotty-energie.mdx +++ b/docs/devices-next/tariffs/spotty-energie.mdx @@ -9,32 +9,46 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Spotty Energie - +
+
+ +
+
+ +
+
## Template Parameter `spottyenergy` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `contractid` | You can get your contract id from the customer portal https://i.spottyenergie.at/ | Beispiel: `ffffffff-4444-6666-2222-aaaaaabbbbbb` | yes | -| `pricetype` | Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren | Standard: `CONSUMPTION`
Auswahl: `MARKET`, `CONSUMPTION`, `GENERATION` | yes | +| Contract ID
`contractid` | You can get your contract id from the customer portal https://i.spottyenergie.at/ | Beispiel: `ffffffff-4444-6666-2222-aaaaaabbbbbb` | yes | +| Price type
`pricetype` | Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren | Standard: `CONSUMPTION`
Auswahl: `MARKET`, `CONSUMPTION`, `GENERATION` | yes | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/tibber.mdx b/docs/devices-next/tariffs/tibber.mdx index d54e51eec1..53b45613de 100644 --- a/docs/devices-next/tariffs/tibber.mdx +++ b/docs/devices-next/tariffs/tibber.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tibber - +
+
+ Get your API token from the Tibber developer portal: https://developer.tibber.com/ @@ -21,23 +24,34 @@ Get your API token from the Tibber developer portal: https://developer.tibber.co grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional)`} advanced={`tariffs: + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Only required if you have multiple homes in your Tibber account. (optional)`} advanced={`tariffs: grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Only required if you have multiple homes in your Tibber account. (optional) charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> +
+
+ +
+
## Template Parameter `tibber` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `token` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | yes | -| `homeid` | Only required if you have multiple homes in your Tibber account. | Beispiel: `cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c` | no | +| API Token
`token` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | yes | +| Home ID
`homeid` | Only required if you have multiple homes in your Tibber account. | Beispiel: `cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c` | no | | Charge
`charges` | Additional fixed charge per kWh (e.g. 0.05 for 5 cents) | | no | | Tax
`tax` | Additional percentage charge (e.g. 0.2 for 20%) | | no | | Formula
`formula` | Individual formula for calculating the price | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | no | diff --git a/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx index 2f956fb480..ef4392bc2b 100644 --- a/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx +++ b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron VRM Solar Forecast - +
+
+ [vrm.victronenergy.com](https://vrm.victronenergy.com) get the 2-days-forecast from your installation in VRM portal. You need a free user access token. @@ -28,13 +31,24 @@ import TabItem from '@theme/TabItem'; template: victron idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" token: # API access token, Tokens can be created in VRM in Preferences->Integrations - interval: 1h # optional`} /> + interval: 1h # Interval, optional`} /> +
+
+ +
+
## Template Parameter `victron` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| | VRM Site ID of the installation
`idsite` | The VRM Site ID is displayed in the installation settings under "General" | Beispiel: `123456` | yes | -| API access token
`token` | Tokens can be created in VRM in Preferences->Integrations | | yes | -| `interval` | | Standard: `1h` | no | +| API access token
`token` | Tokens can be created in VRM in Preferences->Integrations | | yes | +| Interval
`interval` | | Standard: `1h` | no | diff --git a/docs/devices-next/vehicles/aiways.mdx b/docs/devices-next/vehicles/aiways.mdx index 743725cd33..9f4598895b 100644 --- a/docs/devices-next/vehicles/aiways.mdx +++ b/docs/devices-next/vehicles/aiways.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Aiways - +
+ +
+
+ +
+
## Template Parameter `aiways` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/audi.mdx b/docs/devices-next/vehicles/audi.mdx index a11ce1a7c1..79c3c42c78 100644 --- a/docs/devices-next/vehicles/audi.mdx +++ b/docs/devices-next/vehicles/audi.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Audi - +
+ +
+
+ +
+ ## Template Parameter `audi` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/bmw.mdx b/docs/devices-next/vehicles/bmw.mdx index 07c90f9641..bfecdead27 100644 --- a/docs/devices-next/vehicles/bmw.mdx +++ b/docs/devices-next/vehicles/bmw.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BMW -Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. +
+
+ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. +
+
+ +
+
## Template Parameter `bmw` @@ -55,10 +69,10 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WBMW...` | no | | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `hcaptcha` | | | yes | +| Captcha Token
`hcaptcha` | | | yes | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/citroen.mdx b/docs/devices-next/vehicles/citroen.mdx index 2c7a49bd31..c4e7da9672 100644 --- a/docs/devices-next/vehicles/citroen.mdx +++ b/docs/devices-next/vehicles/citroen.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Citroën -Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ +
+
## Template Parameter `citroen` @@ -50,12 +64,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Username
`user` | e.g. email address, user id, etc. | | yes | -| `accessToken` | | | yes | -| `refreshToken` | | | yes | +| Access token
`accessToken` | | | yes | +| Refresh token
`refreshToken` | | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/dacia.mdx b/docs/devices-next/vehicles/dacia.mdx index 138713b0ef..2484ffc17b 100644 --- a/docs/devices-next/vehicles/dacia.mdx +++ b/docs/devices-next/vehicles/dacia.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Dacia - +
+ +
+
+ +
+ ## Template Parameter `dacia` @@ -51,7 +65,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/ds.mdx b/docs/devices-next/vehicles/ds.mdx index eb39abd430..30da4f9eaf 100644 --- a/docs/devices-next/vehicles/ds.mdx +++ b/docs/devices-next/vehicles/ds.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DS -Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ +
+
## Template Parameter `ds` @@ -50,12 +64,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Username
`user` | e.g. email address, user id, etc. | | yes | -| `accessToken` | | | yes | -| `refreshToken` | | | yes | +| Access token
`accessToken` | | | yes | +| Refresh token
`refreshToken` | | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/evnotify.mdx b/docs/devices-next/vehicles/evnotify.mdx index 5e5ef1dee1..5338560111 100644 --- a/docs/devices-next/vehicles/evnotify.mdx +++ b/docs/devices-next/vehicles/evnotify.mdx @@ -9,43 +9,57 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # evNotify - +
+ +
+
+ +
+ ## Template Parameter `evnotify` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `akey` | | | yes | -| `token` | | | yes | +| API Key
`akey` | | | yes | +| Token
`token` | | | yes | | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/fiat.mdx b/docs/devices-next/vehicles/fiat.mdx index 1bb7d6f668..8dca70a9e8 100644 --- a/docs/devices-next/vehicles/fiat.mdx +++ b/docs/devices-next/vehicles/fiat.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fiat - +
+ +
+
+ +
+ ## Template Parameter `fiat` @@ -51,10 +65,10 @@ import TabItem from '@theme/TabItem'; | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `ZFAE...` | no | | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `pin` | Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. | | no | +| PIN
`pin` | Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. | | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/ford.mdx b/docs/devices-next/vehicles/ford.mdx index 92ea2aeb8f..1d13fa0a2f 100644 --- a/docs/devices-next/vehicles/ford.mdx +++ b/docs/devices-next/vehicles/ford.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ford - +
+ +
+
+ +
+ ## Template Parameter `ford-connect` @@ -50,12 +64,12 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | FordConnect API Client ID
`clientid` | Setup at https://developer.ford.com | | yes | | FordConnect API Client Secret
`clientsecret` | Setup at https://developer.ford.com | | yes | -| `accessToken` | | | yes | -| `refreshToken` | | | yes | +| Access token
`accessToken` | | | yes | +| Refresh token
`refreshToken` | | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WF0FXX...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/generic-vehicle-without-api.mdx b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx index 1bd97d28c2..4793ccec9f 100644 --- a/docs/devices-next/vehicles/generic-vehicle-without-api.mdx +++ b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Generic vehicle (without API) - +
+ +
+
+ +
+ ## Template Parameter `offline` @@ -39,7 +53,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/hyundai-bluelink.mdx b/docs/devices-next/vehicles/hyundai-bluelink.mdx index ea1887b90e..58ff10bfae 100644 --- a/docs/devices-next/vehicles/hyundai-bluelink.mdx +++ b/docs/devices-next/vehicles/hyundai-bluelink.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hyundai Bluelink -Some models (e.g. Kona) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. +
+
+ Some models (e.g. Kona) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. +
+
+ +
+
## Template Parameter `hyundai` @@ -55,7 +69,7 @@ Some models (e.g. Kona) switch internally to 2 phases at low charging currents ( | Language
`language` | | Standard: `en`
Auswahl: `en`, `de` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/iobroker-bmw.mdx b/docs/devices-next/vehicles/iobroker-bmw.mdx index 681a40c327..f7aad5547c 100644 --- a/docs/devices-next/vehicles/iobroker-bmw.mdx +++ b/docs/devices-next/vehicles/iobroker-bmw.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ioBroker.bmw -ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api +
+
+ ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api +
+
+ +
+
## Template Parameter `ioBroker.bmw` @@ -48,10 +62,10 @@ ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Vehicle Identification Number
`vin` | BMW VehicleIdentificationNumber | Beispiel: `WBA8E9G50GM091234` | yes | -| ioBroker URL inlcuding ioBroker.simple-api Port
`uri` | HTTP(S) address | | yes | +| ioBroker URL
`uri` | including ioBroker.simple-api Port | | yes | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/iso15118.mdx b/docs/devices-next/vehicles/iso15118.mdx index dde55a6588..de933abd69 100644 --- a/docs/devices-next/vehicles/iso15118.mdx +++ b/docs/devices-next/vehicles/iso15118.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ISO15118 -Only supported if the vehicle can provide the state of charge (Soc) to the connected charger. +
+
+ Only supported if the vehicle can provide the state of charge (Soc) to the connected charger. Using ISO15118 with some VW group vehicles, e.g. Porsche Taycan, requires additional configuration in the vehicle. This requires an active location-based charging profile with the lowest minimum charge (25%) and direct charging disabled. Otherwise the vehicle cannot be put into sleep mode. @@ -31,11 +34,22 @@ Otherwise the vehicle cannot be put into sleep mode. capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +
+
+ +
+
## Template Parameter `iso15118` @@ -45,7 +59,7 @@ Otherwise the vehicle cannot be put into sleep mode. | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/jeep.mdx b/docs/devices-next/vehicles/jeep.mdx index a2dba1d04f..7578580071 100644 --- a/docs/devices-next/vehicles/jeep.mdx +++ b/docs/devices-next/vehicles/jeep.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Jeep - +
+ +
+
+ +
+ ## Template Parameter `fiat` @@ -51,10 +65,10 @@ import TabItem from '@theme/TabItem'; | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `ZFAE...` | no | | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `pin` | Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. | | no | +| PIN
`pin` | Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. | | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/kia-bluelink.mdx b/docs/devices-next/vehicles/kia-bluelink.mdx index 315116913f..680dbedc66 100644 --- a/docs/devices-next/vehicles/kia-bluelink.mdx +++ b/docs/devices-next/vehicles/kia-bluelink.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kia Bluelink -Some models (e.g. Niro EV) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. +
+
+ Some models (e.g. Niro EV) switch internally to 2 phases at low charging currents (< 8A). In cases where the wallbox also measures the phase currents, this leads to undesirable fluctuations in the charging power. The remedy here is to set the minimum charging current to 8A. +
+
+ +
+
## Template Parameter `kia` @@ -55,7 +69,7 @@ Some models (e.g. Niro EV) switch internally to 2 phases at low charging current | Language
`language` | | Standard: `en`
Auswahl: `en`, `de` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/mercedes-benz.mdx b/docs/devices-next/vehicles/mercedes-benz.mdx index a4dab6ea0d..c2727e6bd0 100644 --- a/docs/devices-next/vehicles/mercedes-benz.mdx +++ b/docs/devices-next/vehicles/mercedes-benz.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mercedes-Benz -Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/mbapi2020helptoken. +
+
+ Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/mbapi2020helptoken. +
+
+ +
+
## Template Parameter `mercedes` @@ -52,13 +66,13 @@ Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/ | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Username
`user` | e.g. email address, user id, etc. | | yes | -| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | yes | -| `accessToken` | | | yes | -| `refreshToken` | | | yes | +| Region
`region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | yes | +| Access token
`accessToken` | | | yes | +| Refresh token
`refreshToken` | | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/mg.mdx b/docs/devices-next/vehicles/mg.mdx index a6ad7bfb48..d994ca0e0f 100644 --- a/docs/devices-next/vehicles/mg.mdx +++ b/docs/devices-next/vehicles/mg.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # MG - +
+ +
+
+ +
+ ## Template Parameter `mg` @@ -50,7 +64,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/mg2mqtt.mdx b/docs/devices-next/vehicles/mg2mqtt.mdx index 2f468e07a0..a02144f32d 100644 --- a/docs/devices-next/vehicles/mg2mqtt.mdx +++ b/docs/devices-next/vehicles/mg2mqtt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # mg2mqtt -Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway or https://github.com/SAIC-iSmart-API/saic-java-client) +
+
+ Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway or https://github.com/SAIC-iSmart-API/saic-java-client) +
+
+ +
+
## Template Parameter `mg2mqtt` @@ -51,7 +65,7 @@ Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/S | Timeout
`timeout` | | Standard: `1h`
Beispiel: `10s` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/mini.mdx b/docs/devices-next/vehicles/mini.mdx index a6f5e61d03..322d9915ed 100644 --- a/docs/devices-next/vehicles/mini.mdx +++ b/docs/devices-next/vehicles/mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mini -Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. +
+
+ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html). The token is only valid for a short time. Please copy it into the configuration and start evcc as soon as possible after generation. +
+
+ +
+
## Template Parameter `mini` @@ -55,10 +69,10 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WBMW...` | no | | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `hcaptcha` | | | yes | +| Captcha Token
`hcaptcha` | | | yes | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/mz2mqtt.mdx b/docs/devices-next/vehicles/mz2mqtt.mdx index 06f0ad0d41..e80041d23b 100644 --- a/docs/devices-next/vehicles/mz2mqtt.mdx +++ b/docs/devices-next/vehicles/mz2mqtt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # mz2mqtt -myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation https://github.com/C64Axel/mz2mqtt. +
+
+ myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation https://github.com/C64Axel/mz2mqtt. +
+
+ +
+
## Template Parameter `mz2mqtt` @@ -46,7 +60,7 @@ myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation h | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/nissan-ariya.mdx b/docs/devices-next/vehicles/nissan-ariya.mdx index ae050f9728..4c5d24ce5c 100644 --- a/docs/devices-next/vehicles/nissan-ariya.mdx +++ b/docs/devices-next/vehicles/nissan-ariya.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nissan Ariya - +
+ +
+
+ +
+ ## Template Parameter `nissan-ariya` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx index c89fe1235e..23d8478d78 100644 --- a/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx +++ b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nissan Leaf (pre 2019) - +
+ +
+
+ +
+ ## Template Parameter `carwings` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/nissan-leaf.mdx b/docs/devices-next/vehicles/nissan-leaf.mdx index 5962597639..5f45726671 100644 --- a/docs/devices-next/vehicles/nissan-leaf.mdx +++ b/docs/devices-next/vehicles/nissan-leaf.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nissan Leaf - +
+ +
+
+ +
+ ## Template Parameter `nissan` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/niu-e-scooter.mdx b/docs/devices-next/vehicles/niu-e-scooter.mdx index 70509aabec..bb5e560c6c 100644 --- a/docs/devices-next/vehicles/niu-e-scooter.mdx +++ b/docs/devices-next/vehicles/niu-e-scooter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # NIU E-Scooter - +
+ +
+
+ +
+ ## Template Parameter `niu-e-scooter` diff --git a/docs/devices-next/vehicles/opel.mdx b/docs/devices-next/vehicles/opel.mdx index b038f1e95d..6e5fa48187 100644 --- a/docs/devices-next/vehicles/opel.mdx +++ b/docs/devices-next/vehicles/opel.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Opel -Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ +
+
## Template Parameter `opel` @@ -50,12 +64,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Username
`user` | e.g. email address, user id, etc. | | yes | -| `accessToken` | | | yes | -| `refreshToken` | | | yes | +| Access token
`accessToken` | | | yes | +| Refresh token
`refreshToken` | | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx index ff76082257..d1dec8ba23 100644 --- a/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx +++ b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Open Vehicle Monitoring System -Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Vehicle Monitoring System](http://api.openvehicles.com/). +
+
+ Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Vehicle Monitoring System](http://api.openvehicles.com/). +
+
+ +
+
## Template Parameter `ovms` @@ -50,14 +64,14 @@ Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Veh | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Username
`user` | e.g. email address, user id, etc. | | yes | | Password
`password` | Use single quotes in case of leading zeros | | yes | -| `vehicleid` | | | yes | +| Vehicle ID
`vehicleid` | | | yes | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | | Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | -| `server` | | Standard: `dexters-web.de` | yes | +| Server
`server` | | Standard: `dexters-web.de` | yes | | Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | diff --git a/docs/devices-next/vehicles/peugeot.mdx b/docs/devices-next/vehicles/peugeot.mdx index aca315f31e..8426456057 100644 --- a/docs/devices-next/vehicles/peugeot.mdx +++ b/docs/devices-next/vehicles/peugeot.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peugeot -Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ +
+
## Template Parameter `peugeot` @@ -50,12 +64,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Username
`user` | e.g. email address, user id, etc. | | yes | -| `accessToken` | | | yes | -| `refreshToken` | | | yes | +| Access token
`accessToken` | | | yes | +| Refresh token
`refreshToken` | | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/polestar.mdx b/docs/devices-next/vehicles/polestar.mdx index 1ba09cf783..3cf2a1d002 100644 --- a/docs/devices-next/vehicles/polestar.mdx +++ b/docs/devices-next/vehicles/polestar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Polestar - +
+ +
+
+ +
+ ## Template Parameter `polestar` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/psa-car-controller.mdx b/docs/devices-next/vehicles/psa-car-controller.mdx index 1c8f459346..0a9414c5e2 100644 --- a/docs/devices-next/vehicles/psa-car-controller.mdx +++ b/docs/devices-next/vehicles/psa-car-controller.mdx @@ -9,50 +9,64 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # PSA Car Controller -Remote Control of PSA car https://github.com/flobz/psa_car_controller +
+
+ Remote Control of PSA car https://github.com/flobz/psa_car_controller + wakeup_alt: false # Alternative wakeup code, Can lead to increased discharge of the 12V battery. (optional)`} /> +
+
+ +
+
## Template Parameter `flobz` | Name | Explanation | Value | Optional | |-----------|-------------|-------|----------| -| `url` | | Beispiel: `http://192.0.2.2` | yes | +| URL
`url` | | Beispiel: `http://192.0.2.2` | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | yes | | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | | Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | -| `wakeup_alt` | alternative wakeup-code; could lead to increased discharge of the 12V battery. | | no | +| Alternative wakeup code
`wakeup_alt` | Can lead to increased discharge of the 12V battery. | | no | diff --git a/docs/devices-next/vehicles/renault.mdx b/docs/devices-next/vehicles/renault.mdx index 52ba787fdb..73b974f095 100644 --- a/docs/devices-next/vehicles/renault.mdx +++ b/docs/devices-next/vehicles/renault.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Renault - +
+ +
+
+ +
+ ## Template Parameter `renault` @@ -50,7 +64,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx index cd14ce34be..d2b03b7a7d 100644 --- a/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) - +
+ +
+
+ +
+ ## Template Parameter `seat` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx index 748b2c4c31..a6d85c5e62 100644 --- a/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Seat CupraConnect Gen4 (Born, Formentor, Tavascan) - +
+ +
+
+ +
+ ## Template Parameter `cupra` @@ -51,7 +65,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/skoda-enyaq.mdx b/docs/devices-next/vehicles/skoda-enyaq.mdx index 36fdca4bc5..b18fccad75 100644 --- a/docs/devices-next/vehicles/skoda-enyaq.mdx +++ b/docs/devices-next/vehicles/skoda-enyaq.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Enyaq - +
+ +
+
+ +
+ ## Template Parameter `enyaq` @@ -52,7 +66,7 @@ import TabItem from '@theme/TabItem'; | Timeout
`timeout` | | Standard: `10s`
Beispiel: `10s` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/smart-1.mdx b/docs/devices-next/vehicles/smart-1.mdx index aedff82345..48647c51a6 100644 --- a/docs/devices-next/vehicles/smart-1.mdx +++ b/docs/devices-next/vehicles/smart-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smart - +
+ +
+
+ +
+ ## Template Parameter `smart-hello` @@ -51,7 +65,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/smart-eq.mdx b/docs/devices-next/vehicles/smart-eq.mdx index dd9a74a8ee..fa63588d1a 100644 --- a/docs/devices-next/vehicles/smart-eq.mdx +++ b/docs/devices-next/vehicles/smart-eq.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smart EQ -Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ Requires `access` and `refresh` tokens. These can be generated with command `evcc token [name]`. +
+
+ +
+
## Template Parameter `smart` @@ -52,13 +66,13 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Username
`user` | e.g. email address, user id, etc. | | yes | -| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | yes | -| `accessToken` | | | yes | -| `refreshToken` | | | yes | +| Region
`region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | yes | +| Access token
`accessToken` | | | yes | +| Refresh token
`refreshToken` | | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `V...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/tesla-ble.mdx b/docs/devices-next/vehicles/tesla-ble.mdx index 5fd32582ba..81bbdc3c97 100644 --- a/docs/devices-next/vehicles/tesla-ble.mdx +++ b/docs/devices-next/vehicles/tesla-ble.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla BLE -Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy +
+
+ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy +
+
+ +
+
## Template Parameter `tesla-ble` @@ -47,11 +61,11 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Vehicle Identification Number
`vin` | Required for BLE connection | Beispiel: `W...` | yes | -| `url` | URL of the Tesla BLE HTTP Proxy | Beispiel: `http://192.168.178.27` | yes | +| URL
`url` | URL of the Tesla BLE HTTP Proxy | Beispiel: `http://192.168.178.27` | yes | | Port
`port` | Port of the Tesla BLE HTTP Proxy | Standard: `8080`
Beispiel: `8080` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/tesla.mdx b/docs/devices-next/vehicles/tesla.mdx index fc5c6b4365..79b45c098f 100644 --- a/docs/devices-next/vehicles/tesla.mdx +++ b/docs/devices-next/vehicles/tesla.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla -Tesla offers an official, but paid vehicle API. +
+
+ Tesla offers an official, but paid vehicle API. For private use, you can create a [Tesla Developer Account](https://developer.tesla.com/) and receive a monthly API credit of $10. This is usually sufficient for the common evcc use cases. @@ -34,29 +37,40 @@ More information and alternatives can be found in [our blog post](https://docs.e template: tesla title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, from [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, from [myteslamate.com](https://app.myteslamate.com/). vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template template: tesla title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, from [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, from [myteslamate.com](https://app.myteslamate.com/). vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - commandProxy: https://api.myteslamate.com # When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) - proxyToken: # Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) + commandProxy: https://api.myteslamate.com # Command Proxy, When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) + proxyToken: # Proxy Token, Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> +
+
+ +
+
## Template Parameter `tesla` @@ -64,18 +78,18 @@ More information and alternatives can be found in [our blog post](https://docs.e |-----------|-------------|-------|----------| | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `clientId` | Client ID of your \[Tesla Developer App\](https://developer.tesla.com/dashboard). | | yes | -| `accessToken` | from \[myteslamate.com\](https://app.myteslamate.com/). | | yes | -| `refreshToken` | from \[myteslamate.com\](https://app.myteslamate.com/). | | yes | +| Client ID
`clientId` | from \[Tesla Developer App\](https://developer.tesla.com/dashboard). | | yes | +| Access token
`accessToken` | from \[myteslamate.com\](https://app.myteslamate.com/). | | yes | +| Refresh token
`refreshToken` | from \[myteslamate.com\](https://app.myteslamate.com/). | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | | Priority
`priority` | Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy | | no | -| `commandProxy` | When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the \[myteslamate.com\](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example \[TeslaBleHttpProxy\](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. | Standard: `https://api.myteslamate.com` | no | -| `proxyToken` | Token for the \[myteslamate.com\](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. | | no | +| Command Proxy
`commandProxy` | When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the \[myteslamate.com\](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example \[TeslaBleHttpProxy\](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. | Standard: `https://api.myteslamate.com` | no | +| Proxy Token
`proxyToken` | Token for the \[myteslamate.com\](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. | | no | | Cache
`cache` | Time interval with when data should be reloaded from the vehicle | Standard: `15m`
Beispiel: `5m` | no | diff --git a/docs/devices-next/vehicles/teslalogger.mdx b/docs/devices-next/vehicles/teslalogger.mdx index 6a2c0eb3b4..8e5d95f218 100644 --- a/docs/devices-next/vehicles/teslalogger.mdx +++ b/docs/devices-next/vehicles/teslalogger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TeslaLogger -Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger +
+
+ Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger +
+
+ +
+
## Template Parameter `teslalogger` @@ -47,11 +61,11 @@ Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | TeslaLogger CarID
`id` | | Standard: `1` | no | -| `url` | | Beispiel: `http://192.0.2.2` | yes | +| URL
`url` | | Beispiel: `http://192.0.2.2` | yes | | Port
`port` | | Standard: `5000`
Beispiel: `5000` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/teslamate.mdx b/docs/devices-next/vehicles/teslamate.mdx index 44eed6b68c..dd434feb92 100644 --- a/docs/devices-next/vehicles/teslamate.mdx +++ b/docs/devices-next/vehicles/teslamate.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TeslaMate -Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT broker required. +
+
+ Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT broker required. +
+
+ +
+
## Template Parameter `teslamate` @@ -45,7 +59,7 @@ Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT bro | Vehicle ID
`id` | | Standard: `1` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/tessie.mdx b/docs/devices-next/vehicles/tessie.mdx index 5cddb14b5b..3470ae35bd 100644 --- a/docs/devices-next/vehicles/tessie.mdx +++ b/docs/devices-next/vehicles/tessie.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tessie -Connect your Tesla using the Tessie API. This will never wake up the car, polling can be set to "always" and interval "1M". If the vehicle is awake, the data is usually less than 15 seconds old. If the vehicle is asleep, the data is from the time the vehicle went to sleep. Get your token at https://dash.tessie.com/settings/api +
+
+ Connect your Tesla using the Tessie API. This will never wake up the car, polling can be set to "always" and interval "1M". If the vehicle is awake, the data is usually less than 15 seconds old. If the vehicle is asleep, the data is from the time the vehicle went to sleep. Get your token at https://dash.tessie.com/settings/api +
+
+ +
+
## Template Parameter `tessie` @@ -48,7 +62,7 @@ Connect your Tesla using the Tessie API. This will never wake up the car, pollin | Tessie API Token
`token` | | | yes | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/toyota.mdx b/docs/devices-next/vehicles/toyota.mdx index c482188ac4..f35d461b3b 100644 --- a/docs/devices-next/vehicles/toyota.mdx +++ b/docs/devices-next/vehicles/toyota.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Toyota -Requires Toyota Connected Services Account. +
+
+ Requires Toyota Connected Services Account. +
+
+ +
+
## Template Parameter `toyota` @@ -52,7 +66,7 @@ Requires Toyota Connected Services Account. | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `JT...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/tronity.mdx b/docs/devices-next/vehicles/tronity.mdx index 8477a2a02f..9e2f0f53ac 100644 --- a/docs/devices-next/vehicles/tronity.mdx +++ b/docs/devices-next/vehicles/tronity.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tronity - +
+ +
+
+ +
+ ## Template Parameter `tronity` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `W...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx index 007bce4d78..16ffaf4bea 100644 --- a/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx +++ b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen We Connect ID -e-Golf, e-Up, ID family +
+
+ e-Golf, e-Up, ID family +
+
+ +
+
## Template Parameter `vw` @@ -57,7 +71,7 @@ e-Golf, e-Up, ID family | Timeout
`timeout` | | Standard: `10s`
Beispiel: `10s` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/volvo.mdx b/docs/devices-next/vehicles/volvo.mdx index 2c6aff7d7b..bf13b49a66 100644 --- a/docs/devices-next/vehicles/volvo.mdx +++ b/docs/devices-next/vehicles/volvo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volvo -To use with EVCC, you need a Volvo account and a Volvo Connected Car API Key. +
+
+ To use with EVCC, you need a Volvo account and a Volvo Connected Car API Key. To do this, create a new application on the [Account page](https://developer.volvocars.com/account/) and save the primary VCC API key. Now publish your application and select the permissions "Connected Vehicle API -> conve:vehicle-relation" and "Energy API -> (everything)" under "Scopes". You must enter the URL of your EVCC instance as the redirect URL, e.g. "http://evcc.local:7070/oauth/callback". @@ -28,28 +31,39 @@ Log in with your Volvo account and allow access to the data. If the authorizatio template: volvo-connected title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. + vccapikey: # VCC API Key, from [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, from [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, from [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect URI of your evcc instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template template: volvo-connected title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. + vccapikey: # VCC API Key, from [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, from [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, from [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect URI of your evcc instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)`} /> +
+
+ +
+
## Template Parameter `volvo-connected` @@ -57,14 +71,14 @@ Log in with your Volvo account and allow access to the data. If the authorizatio |-----------|-------------|-------|----------| | Title
`title` | Will be displayed in the user interface | | no | | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | -| `vccapikey` | VCC API Key of your \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | -| `clientId` | Client ID of your \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | -| `clientSecret` | Client Secret of your \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | -| `redirectUri` | Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. | | yes | +| VCC API Key
`vccapikey` | from \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | +| Client ID
`clientId` | from \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | +| Client Secret
`clientSecret` | from \[Volvo Developer App\](https://developer.volvocars.com/). | | yes | +| Redirect URI
`redirectUri` | Redirect URI of your evcc instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. | | yes | | Vehicle Identification Number
`vin` | If you own multiple vehicles from the same manufacturer | Beispiel: `WF0FXX...` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/volvo2mqtt.mdx b/docs/devices-next/vehicles/volvo2mqtt.mdx index ad9ad19cc7..dee134d77f 100644 --- a/docs/devices-next/vehicles/volvo2mqtt.mdx +++ b/docs/devices-next/vehicles/volvo2mqtt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # volvo2mqtt -Requires MQTT broker configuration and a volvo2mqtt installation https://github.com/Dielee/volvo2mqtt +
+
+ Requires MQTT broker configuration and a volvo2mqtt installation https://github.com/Dielee/volvo2mqtt +
+
+ +
+
## Template Parameter `volvo2mqtt` @@ -48,7 +62,7 @@ Requires MQTT broker configuration and a volvo2mqtt installation https://github. | Timeout
`timeout` | | Standard: `720h`
Beispiel: `10s` | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices-next/vehicles/zero-motorcycles.mdx b/docs/devices-next/vehicles/zero-motorcycles.mdx index 6c55f5a218..510a5157ff 100644 --- a/docs/devices-next/vehicles/zero-motorcycles.mdx +++ b/docs/devices-next/vehicles/zero-motorcycles.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zero Motorcycles - +
+ +
+
+ +
+ ## Template Parameter `zero` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | | Icon
`icon` | Will be displayed in the user interface | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | no | | Maximum number of phases
`phases` | The maximum number of phases which can be used | Beispiel: `3` | no | -| Default charging mode when a vehicle is connected
`mode` | Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | +| Default charging mode
`mode` | Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set | | no | | Minimum amperage
`minCurrent` | The minimum amperage per connected phase with which the car should be charged | Beispiel: `6`
Einheit: A | no | | Maximum amperage
`maxCurrent` | The maximum amperage per connected phase with which the car shuold be charged | Beispiel: `16`
Einheit: A | no | | Identification
`identifiers` | Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle | | no | diff --git a/docs/devices/chargers.mdx b/docs/devices/chargers.mdx index 93becf2722..ab84c057e2 100644 --- a/docs/devices/chargers.mdx +++ b/docs/devices/chargers.mdx @@ -99,17 +99,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -127,17 +127,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -184,17 +184,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -299,17 +299,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -325,17 +325,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -376,17 +376,17 @@ Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus exte - name: my_charger type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -688,17 +688,17 @@ Anleitung: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -721,17 +721,17 @@ Anleitung: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -749,17 +749,17 @@ Anleitung: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -775,17 +775,17 @@ Anleitung: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -972,17 +972,17 @@ Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigescha - name: my_charger type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -1517,9 +1517,9 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> @@ -1537,9 +1537,9 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> @@ -1557,9 +1557,9 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> @@ -1577,9 +1577,9 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> @@ -1735,17 +1735,17 @@ Als Betriebsmodus muss `manual` ausgewählt sein - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -1761,17 +1761,17 @@ Als Betriebsmodus muss `manual` ausgewählt sein - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -1787,17 +1787,17 @@ Als Betriebsmodus muss `manual` ausgewählt sein - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -1815,17 +1815,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -1989,17 +1989,17 @@ Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP - name: my_charger type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2017,17 +2017,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2068,17 +2068,17 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2094,17 +2094,17 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2212,18 +2212,18 @@ Die Wallbox muss sich im "Power" Modus befinden. - name: my_charger type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # Zählernummer, optional`} advanced={`chargers: - name: my_charger type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # Zählernummer, optional connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2354,17 +2354,17 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri - name: my_charger type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2380,17 +2380,17 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2522,17 +2522,17 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2604,17 +2604,17 @@ Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss akt - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2650,17 +2650,17 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2811,17 +2811,17 @@ Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händl - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2839,17 +2839,17 @@ Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händl - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -2865,17 +2865,17 @@ Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händl - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -3654,17 +3654,17 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -3684,17 +3684,17 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -3714,17 +3714,17 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -3745,7 +3745,7 @@ NRGkick Ladeeinheit via HTTP (älter als 2022/2023) type: template template: nrgkick-connect host: 192.0.2.2 # IP-Adresse oder Hostname - mac: + mac: # MAC Adresse password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen`} /> @@ -3775,7 +3775,7 @@ NRGkick Ladeeinheit via HTTP (älter als 2022/2023) id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - phases1p3p: false # Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional)`} /> + phases1p3p: false # Phasenumschaltung aktiviert, Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional)`} /> @@ -3938,17 +3938,17 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg - name: my_charger type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5040,17 +5040,17 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg - name: my_charger type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5177,7 +5177,7 @@ Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung de template: tessie vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind token: # Tessie API Token - location: tessiehome # Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive)`} /> + location: tessiehome # Ort, Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive)`} /> @@ -5229,7 +5229,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional)`} advanced={`chargers: + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -5237,7 +5237,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> @@ -5259,7 +5259,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional)`} advanced={`chargers: + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -5267,7 +5267,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> @@ -5611,8 +5611,8 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> @@ -5628,8 +5628,8 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> @@ -5645,8 +5645,8 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> @@ -5662,8 +5662,8 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> @@ -5760,17 +5760,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5794,17 +5794,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5828,17 +5828,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5862,17 +5862,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5896,17 +5896,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5930,17 +5930,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5964,17 +5964,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -5998,17 +5998,17 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -6139,7 +6139,7 @@ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gel - name: my_charger type: template template: zaptec - id: # Wallbox ID (optional) + id: # ID, Wallbox ID (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> @@ -6161,17 +6161,17 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -6187,7 +6187,7 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: zaptec - id: # Wallbox ID (optional) + id: # ID, Wallbox ID (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> @@ -6205,7 +6205,7 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: zaptec - id: # Wallbox ID (optional) + id: # ID, Wallbox ID (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> @@ -6223,17 +6223,17 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -6366,17 +6366,17 @@ Die konkrete Konfiguration und der tatsächlich nutzbare Funktionsumfang hängen - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> @@ -6401,14 +6401,14 @@ Diese Anpassungen ermöglichen eine häufigere und detailliertere Meldung der La - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456)`} advanced={`chargers: + token: # Token, API Token + identity: AA123456 # Identity des Ladepunkts`} advanced={`chargers: - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456) - connector: 1 # Ladepunkt (falls >1 Ladepunkt), Anschluss-ID (üblicherweise 1)`} /> + token: # Token, API Token + identity: AA123456 # Identity des Ladepunkts + connector: 1 # Anschluss-ID`} /> @@ -6434,7 +6434,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6444,8 +6444,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6462,7 +6462,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> @@ -6488,7 +6488,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6498,8 +6498,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6521,7 +6521,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6531,8 +6531,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6549,7 +6549,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> @@ -6572,7 +6572,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6594,7 +6594,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6604,8 +6604,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6647,7 +6647,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6657,8 +6657,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6695,7 +6695,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> @@ -6718,7 +6718,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6744,7 +6744,7 @@ Energiemanagementeinstellungen am Gerät: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6788,7 +6788,7 @@ Energiemanagementeinstellungen am Gerät: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + tempsource: 1 # Temperaturquelle, [1, 2, 3] (optional) scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional`} /> @@ -6811,7 +6811,7 @@ Energiemanagementeinstellungen am Gerät: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + tempsource: 1 # Temperaturquelle, [1, 2, 3] (optional) scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional`} /> @@ -6836,7 +6836,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6846,8 +6846,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6869,7 +6869,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6879,8 +6879,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6904,7 +6904,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6914,8 +6914,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -6937,7 +6937,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6947,8 +6947,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -7028,9 +7028,9 @@ Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird d template: vaillant user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - realm: DE # [DE, AT] (optional) - zone: # Id der Boostzone (optional) - setpoint: # Boost Temperatur (optional)`} /> + realm: DE # Region, [DE, AT] (optional) + zone: # ID der Boostzone, optional + setpoint: # Boost Temperatur, optional`} /> @@ -7076,7 +7076,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -7086,8 +7086,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -7109,7 +7109,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -7119,8 +7119,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -7146,7 +7146,7 @@ Energiemanagementeinstellungen am Gerät: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> diff --git a/docs/devices/heating.mdx b/docs/devices/heating.mdx index b4c414e56f..2b0005f179 100644 --- a/docs/devices/heating.mdx +++ b/docs/devices/heating.mdx @@ -185,7 +185,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -195,8 +195,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -211,7 +211,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> @@ -235,7 +235,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -245,8 +245,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -266,7 +266,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -276,8 +276,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -292,7 +292,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> @@ -313,7 +313,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -333,7 +333,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -343,8 +343,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -382,7 +382,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -392,8 +392,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -426,7 +426,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> @@ -447,7 +447,7 @@ Eingebunden via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -471,7 +471,7 @@ Energiemanagementeinstellungen am Gerät: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -511,7 +511,7 @@ Energiemanagementeinstellungen am Gerät: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + tempsource: 1 # Temperaturquelle, [1, 2, 3] (optional) scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional`} /> @@ -532,7 +532,7 @@ Energiemanagementeinstellungen am Gerät: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + tempsource: 1 # Temperaturquelle, [1, 2, 3] (optional) scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional`} /> @@ -555,7 +555,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -565,8 +565,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -586,7 +586,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -596,8 +596,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -619,7 +619,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -629,8 +629,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -650,7 +650,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -660,8 +660,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -733,9 +733,9 @@ Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird d template: vaillant user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - realm: DE # [DE, AT] (optional) - zone: # Id der Boostzone (optional) - setpoint: # Boost Temperatur (optional)`} /> + realm: DE # Region, [DE, AT] (optional) + zone: # ID der Boostzone, optional + setpoint: # Boost Temperatur, optional`} /> @@ -777,7 +777,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -787,8 +787,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -808,7 +808,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -818,8 +818,8 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> @@ -843,7 +843,7 @@ Energiemanagementeinstellungen am Gerät: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> diff --git a/docs/devices/meters.mdx b/docs/devices/meters.mdx index 1209967729..bd9311af98 100644 --- a/docs/devices/meters.mdx +++ b/docs/devices/meters.mdx @@ -121,7 +121,7 @@ Die meisten modernen PV-Technikkomponenten, insbesondere Wechselrichter und Batt id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -163,7 +163,7 @@ Die meisten modernen PV-Technikkomponenten, insbesondere Wechselrichter und Batt id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -206,7 +206,7 @@ Die meisten modernen PV-Technikkomponenten, insbesondere Wechselrichter und Batt host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -607,32 +607,7 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder modbus: tcpip id: 85 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -686,8 +661,6 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -783,32 +756,7 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -838,32 +786,7 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -1977,32 +1900,7 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -2056,8 +1954,6 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -2177,9 +2073,7 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -2234,9 +2128,7 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -2292,7 +2184,7 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -2508,7 +2400,7 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde usage: grid user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Zählernummer`} /> @@ -2522,7 +2414,7 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde usage: pv user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Zählernummer`} /> @@ -2601,7 +2493,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_grid type: template template: e3dc-rscp @@ -2610,7 +2502,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional)`} /> @@ -2627,7 +2519,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_pv type: template template: e3dc-rscp @@ -2636,7 +2528,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -2654,7 +2546,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_battery type: template template: e3dc-rscp @@ -2663,7 +2555,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -3000,13 +2892,13 @@ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vo template: enphase usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_grid type: template template: enphase usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -3020,13 +2912,13 @@ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vo template: enphase usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_pv type: template template: enphase usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -3040,13 +2932,13 @@ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vo template: enphase usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_battery type: template template: enphase usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) capacity: 50 # Akkukapazität (kWh), optional cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -3162,8 +3054,8 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) + battery: ess0 # Steuerbare Batterie Komponente, optional + watchdog: 60s # Watchdog, abgestimmt auf das API-Timeout (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -3274,32 +3166,7 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -3353,8 +3220,6 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -3450,32 +3315,7 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -3529,8 +3369,6 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -3639,7 +3477,7 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> + id: 200 # ID, Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> @@ -3760,7 +3598,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -3782,7 +3620,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -3805,7 +3643,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) capacity: 50 # Akkukapazität (kWh), optional - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -3834,7 +3672,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> + id: 200 # ID, Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> @@ -4243,7 +4081,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} /> + battery: 1 # Batteriespeichernummer, [1, 2] (optional)`} /> @@ -4274,7 +4112,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Batteriespeichernummer, [1, 2] (optional)`} advanced={`meters: - name: my_pv type: template template: goodwe-hybrid @@ -4298,7 +4136,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -4330,7 +4168,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Batteriespeichernummer, [1, 2] (optional)`} advanced={`meters: - name: my_battery type: template template: goodwe-hybrid @@ -4354,7 +4192,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -4805,7 +4643,7 @@ Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modu template: hoymiles-ahoydtu usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - id: 0 # Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID], optional`} /> + id: 0 # Wechselrichter ID, Falls mehrere vorhanden. Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID] (optional)`} /> @@ -4929,7 +4767,7 @@ Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modu host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -4959,7 +4797,7 @@ Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modu host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -4990,7 +4828,7 @@ Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modu host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -5060,7 +4898,7 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -5116,7 +4954,7 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -5173,7 +5011,7 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxchargepower: 10000 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) capacity: 50 # Akkukapazität (kWh), optional forceaccharging: false # Wechselrichterkaskade, AC-Laden bleibt aktiv zum Laden des Speichers aus anderen AC Quellen für Wechselrichterkaskaden. Verhindert Stand-by. (optional)`} /> @@ -5866,9 +5704,7 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive B port: 1502 # Port endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -5900,7 +5736,7 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive B capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -5943,7 +5779,7 @@ _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ port: 1502 # Port endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -5974,7 +5810,7 @@ _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) capacity: 50 # Akkukapazität (kWh), optional maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6047,9 +5883,7 @@ Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorpos usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -6069,9 +5903,7 @@ Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorpos usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -6091,7 +5923,7 @@ Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorpos usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> @@ -6125,9 +5957,7 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -6147,9 +5977,7 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -6169,7 +5997,7 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> @@ -6501,10 +6329,10 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich host: 192.0.2.2 # Hostname port: 502 # Port capacity: 5.12 # Akkukapazität (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - minsoc: 11 # Venus kann nur bis 11% entladen werden. (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + minsoc: 11 # Minimaler Ladestand (%), Venus kann nur bis 11% entladen werden. (optional) maxsoc: 100 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxchargepower: 2500 # Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus. (W), Für erzwungenes Laden des Speichers. (optional) - work_mode_normal: 1 # Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung., optional`} /> + maxchargepower: 2500 # Maximale Ladeleistung (W), 2500W ist das Maximum für Venus. (optional) + work_mode_normal: 1 # Work mode für Normal-Modus, 0=manuell, 1=Eigenverbrauch, 2=AI-Optimierung. (optional)`} /> @@ -6656,8 +6484,8 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) + battery: ess0 # Steuerbare Batterie Komponente, optional + watchdog: 60s # Watchdog, abgestimmt auf das API-Timeout (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -6934,7 +6762,7 @@ Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `int usage: grid user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti`} /> + id: main # ID, Id im Falle mehrerer PowerOpti`} /> @@ -6954,7 +6782,7 @@ Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `int usage: pv user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti`} /> + id: main # ID, Id im Falle mehrerer PowerOpti`} /> @@ -7055,7 +6883,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -7079,8 +6907,8 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -7111,7 +6939,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -7135,8 +6963,8 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -7168,7 +6996,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -7192,8 +7020,8 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional)`} /> @@ -7222,10 +7050,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. template: rct-power usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional)`} /> + cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -7243,8 +7068,6 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. template: rct-power usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional)`} /> @@ -7268,8 +7091,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional)`} /> + maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional)`} /> @@ -7501,32 +7323,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -7556,32 +7353,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -7787,7 +7559,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. template: senec-home usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -7800,7 +7572,7 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. template: senec-home usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -7813,13 +7585,13 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. template: senec-home usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional)`} advanced={`meters: + schema: https # Schema, [https, http] (optional)`} advanced={`meters: - name: my_battery type: template template: senec-home usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -8197,7 +7969,7 @@ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen A usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -8211,7 +7983,7 @@ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen A usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -8225,14 +7997,14 @@ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen A usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional`} advanced={`meters: + id: 1 # ID, optional`} advanced={`meters: - name: my_battery type: template template: sigenergy usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional capacity: 50 # Akkukapazität (kWh), optional`} /> @@ -8420,7 +8192,7 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -8456,7 +8228,7 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -8489,7 +8261,7 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -8543,7 +8315,7 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -9280,7 +9052,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -9334,7 +9106,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -9389,7 +9161,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> @@ -9456,7 +9228,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -9510,7 +9282,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -9565,7 +9337,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> @@ -9755,7 +9527,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -9809,7 +9581,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -9864,7 +9636,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> @@ -9931,7 +9703,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -9985,7 +9757,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -10040,7 +9812,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> @@ -10171,7 +9943,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R host: 192.0.2.2 # Hostname port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10228,7 +10000,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10285,7 +10057,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10437,7 +10209,7 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10466,7 +10238,7 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit host: 192.0.2.2 # Hostname port: 502 # Port maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10495,7 +10267,7 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10840,7 +10612,7 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -10864,8 +10636,8 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -10896,7 +10668,7 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -10920,8 +10692,8 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -10953,7 +10725,7 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -10977,8 +10749,8 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional)`} /> @@ -11110,7 +10882,7 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -11152,7 +10924,7 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -11195,7 +10967,7 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -11534,14 +11306,14 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional)`} advanced={`meters: + token: # Token, API Token (benötigt für aktive Batteriesteuerung) (optional)`} advanced={`meters: - name: my_battery type: template template: sonnenbatterie usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional) + token: # Token, API Token (benötigt für aktive Batteriesteuerung) (optional) capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 3300 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) defaultmode: self-consumption # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. [self-consumption, time-of-use]`} /> @@ -11595,7 +11367,7 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -11637,7 +11409,7 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -11680,7 +11452,7 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -12005,32 +11777,7 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -12084,8 +11831,6 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -12205,9 +11950,7 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -12262,9 +12005,7 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -12320,7 +12061,7 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -12564,7 +12305,7 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -12606,7 +12347,7 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -12649,7 +12390,7 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -12768,18 +12509,8 @@ Folgende Apps ermöglichen das Erstellen des Tokens: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: - - name: my_grid - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} /> @@ -12793,18 +12524,8 @@ Folgende Apps ermöglichen das Erstellen des Tokens: usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: - - name: my_pv - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} /> @@ -12818,16 +12539,16 @@ Folgende Apps ermöglichen das Erstellen des Tokens: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: - name: my_battery type: template template: tesla-powerwall usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> @@ -12847,8 +12568,8 @@ Folgende Apps ermöglichen das Erstellen des Tokens: type: template template: tibber-pulse usage: grid - token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE - homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional`} /> + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional`} /> @@ -13256,16 +12977,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional)`} advanced={`meters: - - name: my_grid - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + meterid: # Grid-Energiezähler VRM Instanz, Kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional)`} /> @@ -13285,9 +12997,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -13486,7 +13196,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -13528,7 +13238,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -13571,7 +13281,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -14105,9 +13815,9 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional`} /> @@ -14120,17 +13830,17 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional`} advanced={`meters: - name: my_battery type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional capacity: 2 # Akkukapazität (kWh), optional`} /> @@ -14759,8 +14469,8 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. type: template template: volkszaehler-http usage: grid - url: # URL des "data" Kontexts der Volkszähler Middleware, Beispiel: http://zaehler.network.local:8080/api/data (optional) - uuid:`} /> + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID`} /> @@ -14775,9 +14485,9 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. type: template template: volkszaehler-importexport usage: grid - url: # URL des "data" Kontexts der Volkszähler Middleware, Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data (optional) - importuuid: - exportuuid:`} /> + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID`} /> @@ -14794,7 +14504,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 8082 # Port, optional - uuid:`} /> + uuid: # UUID`} /> @@ -14811,24 +14521,24 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 8081 # Port, optional - uuid:`} advanced={`meters: + uuid: # UUID`} advanced={`meters: - name: my_grid type: template template: vzlogger usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 8081 # Port, optional - uuid: + uuid: # UUID scale: 1 # Skalierungsfaktor, Multipliziere Rohwert mit diesem Faktor (optional) - l1currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0), optional - l2currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0), optional - l3currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0), optional - l1poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0), optional - l2poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0), optional - l3poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0), optional - l1voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0), optional - l2voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0), optional - l3voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0), optional + l1currentuuid: # Strom in Phase 1, Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0) (optional) + l2currentuuid: # Strom in Phase 2, Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0) (optional) + l3currentuuid: # Strom in Phase 3, Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0) (optional) + l1poweruuid: # Leistung in Phase 1, Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0) (optional) + l2poweruuid: # Leistung in Phase 2, Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0) (optional) + l3poweruuid: # Leistung in Phase 3, Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0) (optional) + l1voltageuuid: # Spannung in Phase 1, Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0) (optional) + l2voltageuuid: # Spannung in Phase 2, Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0) (optional) + l3voltageuuid: # Spannung in Phase 3, Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0) (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -14892,7 +14602,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: - name: my_grid type: template template: homematic @@ -14901,8 +14611,8 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> @@ -14918,7 +14628,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: - name: my_pv type: template template: homematic @@ -14927,8 +14637,8 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> @@ -14944,7 +14654,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: - name: my_charger type: template template: homematic @@ -14953,8 +14663,8 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> @@ -15013,7 +14723,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15028,7 +14738,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15043,7 +14753,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15067,7 +14777,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15082,7 +14792,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15097,7 +14807,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15121,7 +14831,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15136,7 +14846,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15151,7 +14861,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15175,7 +14885,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15190,7 +14900,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15205,7 +14915,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15229,7 +14939,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15244,7 +14954,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15259,7 +14969,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15283,7 +14993,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15298,7 +15008,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15313,7 +15023,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15337,7 +15047,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15352,7 +15062,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15367,7 +15077,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15391,7 +15101,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15406,7 +15116,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -15421,7 +15131,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> diff --git a/docs/devices/smartswitches.mdx b/docs/devices/smartswitches.mdx index 3a109fd812..f6103bbe05 100644 --- a/docs/devices/smartswitches.mdx +++ b/docs/devices/smartswitches.mdx @@ -176,7 +176,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al type: template template: homematic host: 192.0.2.2 # IP-Adresse oder Hostname - port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC-Server Port-Nummer, optional device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) @@ -185,14 +185,14 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al type: template template: homematic host: 192.0.2.2 # IP-Adresse oder Hostname - port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC-Server Port-Nummer, optional device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - meterchannel: 6 # Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. - switchchannel: 3 # Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + meterchannel: 6 # Kanalnummer des Power-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. + switchchannel: 3 # Kanalnummer der schaltbaren Steckdose, Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> @@ -254,7 +254,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -262,7 +262,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) @@ -281,7 +281,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -289,7 +289,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) @@ -308,7 +308,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -316,7 +316,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) @@ -335,7 +335,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -343,7 +343,7 @@ Zudem wird der `soc` des Chargers (sofern verfügbar) nicht mehr in % sondern al host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) diff --git a/docs/devices/vehicles.mdx b/docs/devices/vehicles.mdx index b4acd4be2f..a6021e1dda 100644 --- a/docs/devices/vehicles.mdx +++ b/docs/devices/vehicles.mdx @@ -62,7 +62,7 @@ Die Qualität und Verfügbarkeit der Fahrzeugschnittstellen variiert von Herstel capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -94,7 +94,7 @@ Die Qualität und Verfügbarkeit der Fahrzeugschnittstellen variiert von Herstel capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -118,7 +118,7 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha:`} advanced={`vehicles: + hcaptcha: # Captcha Token`} advanced={`vehicles: - name: my_car type: template template: bmw @@ -127,10 +127,10 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -155,8 +155,8 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template @@ -164,12 +164,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -201,7 +201,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -225,8 +225,8 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template @@ -234,12 +234,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -261,7 +261,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional)`} advanced={`vehicles: + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional)`} advanced={`vehicles: - name: my_car type: template template: fiat @@ -270,10 +270,10 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -296,8 +296,8 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template @@ -306,12 +306,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -347,7 +347,7 @@ Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf language: en # Sprache, [en, de] (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -369,7 +369,7 @@ Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional)`} advanced={`vehicles: + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional)`} advanced={`vehicles: - name: my_car type: template template: fiat @@ -378,10 +378,10 @@ Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -419,7 +419,7 @@ Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern a language: en # Sprache, [en, de] (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -441,9 +441,9 @@ Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https:/ title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template @@ -451,13 +451,13 @@ Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https:/ title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -489,7 +489,7 @@ Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https:/ capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -514,7 +514,7 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha:`} advanced={`vehicles: + hcaptcha: # Captcha Token`} advanced={`vehicles: - name: my_car type: template template: mini @@ -523,10 +523,10 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -563,7 +563,7 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -595,7 +595,7 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -627,7 +627,7 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -649,8 +649,8 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template @@ -658,12 +658,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -685,8 +685,8 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template @@ -694,12 +694,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -731,7 +731,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -763,7 +763,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -798,7 +798,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -830,7 +830,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -866,7 +866,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to timeout: 10s # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -900,7 +900,7 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -924,9 +924,9 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template @@ -934,13 +934,13 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -974,28 +974,28 @@ Weitere Informationen und Alternativen findest du in [unserem Blogbeitrag](https template: tesla title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, von [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, von [myteslamate.com](https://app.myteslamate.com/). vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template template: tesla title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, von [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, von [myteslamate.com](https://app.myteslamate.com/). vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - commandProxy: https://api.myteslamate.com # Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) - proxyToken: # Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) + commandProxy: https://api.myteslamate.com # Command Proxy, Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) + proxyToken: # Proxy Token, Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -1025,7 +1025,7 @@ Benötigt Toyota Connected Services Account. vin: JT... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1061,7 +1061,7 @@ e-Golf, e-Up, ID Familie timeout: 10s # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1091,24 +1091,24 @@ Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Is template: volvo-connected title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vccapikey: # VCC API Key, aus [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, aus [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, aus [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template template: volvo-connected title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vccapikey: # VCC API Key, aus [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, aus [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, aus [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1139,7 +1139,7 @@ Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Is capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1192,20 +1192,20 @@ vehicles: - name: my_car type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional`} advanced={`vehicles: - name: my_car type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1230,7 +1230,7 @@ vehicles: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1251,17 +1251,17 @@ ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer - uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse`} advanced={`vehicles: + uri: # ioBroker URL, einschliesslich ioBroker.simple-api Port`} advanced={`vehicles: - name: my_car type: template template: ioBroker.bmw title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer - uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse + uri: # ioBroker URL, einschliesslich ioBroker.simple-api Port icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1294,7 +1294,7 @@ angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1327,7 +1327,7 @@ Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (http timeout: 1h # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1356,7 +1356,7 @@ myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mq vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1379,7 +1379,7 @@ Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vehicleid:`} advanced={`vehicles: + vehicleid: # Vehicle ID`} advanced={`vehicles: - name: my_car type: template template: ovms @@ -1387,15 +1387,15 @@ Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vehicleid: + vehicleid: # Vehicle ID icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - server: dexters-web.de + server: dexters-web.de # Server cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -1410,25 +1410,25 @@ Remote Control of PSA car https://github.com/flobz/psa_car_controller - name: my_car type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional`} advanced={`vehicles: - name: my_car type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - wakeup_alt: false # alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. (optional)`} /> + wakeup_alt: false # Alternativer Wakeup-Code, Kann zu erhöhter Entladung der 12V-Batterie führen. (optional)`} /> @@ -1445,7 +1445,7 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung - url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL des Tesla BLE HTTP Proxy port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional)`} advanced={`vehicles: - name: my_car type: template @@ -1453,11 +1453,11 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung - url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL des Tesla BLE HTTP Proxy port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1478,7 +1478,7 @@ Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional`} advanced={`vehicles: - name: my_car type: template @@ -1486,11 +1486,11 @@ Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1519,7 +1519,7 @@ Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Vorausse id: 1 # Fahrzeug-ID, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1550,7 +1550,7 @@ Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug ni token: # Tessie API Token icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1581,7 +1581,7 @@ Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug ni vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -1615,7 +1615,7 @@ Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqt timeout: 720h # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) diff --git a/docs/tariffs.mdx b/docs/tariffs.mdx index 87abed2205..8961b6121b 100644 --- a/docs/tariffs.mdx +++ b/docs/tariffs.mdx @@ -276,15 +276,15 @@ Das Plugin wird einmal pro Stunde aktualisiert. grid: type: template template: amber - token: # optional - siteid: # optional - channel: # optional`} advanced={`tariffs: + token: # Token, optional + siteid: # Site ID, optional + channel: # Kanal, optional`} advanced={`tariffs: grid: type: template template: amber - token: # optional - siteid: # optional - channel: # optional + token: # Token, optional + siteid: # Site ID, optional + channel: # Kanal, optional charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -301,11 +301,11 @@ Das Plugin wird einmal pro Stunde aktualisiert. grid: type: template template: awattar - region: AT # [DE, AT]`} advanced={`tariffs: + region: AT # Region, [DE, AT]`} advanced={`tariffs: grid: type: template template: awattar - region: AT # [DE, AT] + region: AT # Region, [DE, AT] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -322,11 +322,11 @@ Das Plugin wird einmal pro Stunde aktualisiert. grid: type: template template: energinet - region: dk1 # [dk1, dk2]`} advanced={`tariffs: + region: dk1 # Region, [dk1, dk2]`} advanced={`tariffs: grid: type: template template: energinet - region: dk1 # [dk1, dk2] + region: dk1 # Region, [dk1, dk2] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -343,17 +343,17 @@ Das Plugin wird einmal pro Stunde aktualisiert. grid: type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP]`} advanced={`tariffs: + token: # Token + provider: # Anbieter, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP]`} advanced={`tariffs: grid: type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + token: # Token + provider: # Anbieter, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) - interval: 3h # optional`} /> + interval: 3h # Intervall, optional`} /> @@ -370,13 +370,13 @@ Basis für viele dynamische Tarife. grid: type: template template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: + securitytoken: # Security token, Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: grid: type: template template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -395,11 +395,11 @@ Day-ahead Energiepreise (je kWh) an der Börse. Kann ohne vorherige Anmeldung au grid: type: template template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: + bzn: DE-LU # Gebotszone, siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: grid: type: template template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Gebotszone, siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -437,13 +437,13 @@ Nordpool Spot Preise im Day-Ahead-Markt für alle Märkte in der Nordpool-Region grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Währung, [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Währung, [DKK, EUR, NOK, PLN, RON, SEK] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -464,8 +464,8 @@ Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/a grid: type: template template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional)`} /> + apiKey: # API Key + accountNumber: X-XXXXXXXX # Kundennummer, Nur erforderlich, wenn mehrere Konten vorhanden sind. (optional)`} /> @@ -479,9 +479,9 @@ Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/a grid: type: template template: octopus-productcode - productCode: AGILE-FLEX-22-11-25 # Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. - region: # Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] - directDebit: true # Ich benutze den BACS-Lastschrifttarif. (optional)`} /> + productCode: AGILE-FLEX-22-11-25 # Tarifcode, Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. + region: # Region, Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Lastschrifttarif, Ich benutze den BACS-Lastschrifttarif. (optional)`} /> @@ -497,9 +497,9 @@ Erzeuge einen 'Production Client' im Ostrom-Entwicklerportal: https://developer. grid: type: template template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional)`} /> + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # Client ID + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a # Client Secret + contract: 100523456 # Vertragsnummer, Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional)`} /> @@ -553,13 +553,13 @@ Preisdaten von https://www.mercatoelettrico.org/it/. Wird oft zur Einspeisung in grid: type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION]`} advanced={`tariffs: + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Vertragsnummer, Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Preistyp, Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION]`} advanced={`tariffs: grid: type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Vertragsnummer, Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Preistyp, Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -578,13 +578,13 @@ Hol dir deinen API-Token aus dem Tibber-Entwicklerportal: https://developer.tibb grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional)`} advanced={`tariffs: + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional)`} advanced={`tariffs: grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> @@ -608,8 +608,8 @@ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps type: template template: electricitymaps uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) Adresse - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, siehe https://api.electricitymap.org/v3/zones`} /> @@ -625,8 +625,8 @@ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps co2: type: template template: electricitymaps-free - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, siehe https://api.electricitymap.org/v3/zones`} /> @@ -642,7 +642,7 @@ Europäische CO₂-Intensitätsdaten von [greengrid-compass.eu](https://www.gree co2: type: template template: green-grid-compass - apiKey: # API-Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key + apiKey: # API Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key zone: DE_LU # Zonencode, [BE, DE_LU]`} /> @@ -659,8 +659,8 @@ Regionale Emissionsdaten von https://gruenstromindex.de co2: type: template template: grünstromindex - zip: - token: # Token für den Zugriff auf die API von https://console.corrently.io/ (optional)`} /> + zip: # Postleitzahl + token: # Token, Token für den Zugriff auf die API von https://console.corrently.io/ (optional)`} /> @@ -674,8 +674,8 @@ Regionale Emissionsdaten von https://gruenstromindex.de co2: type: template template: ngeso - region: 1 # Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list (optional) - postalcode: SW1 # Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. (optional)`} /> + region: 1 # Region, Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Postleitzahl, Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. (optional)`} /> @@ -727,8 +727,8 @@ Daher musst du ggf. das Update-Intervall (`interval`) erhöhen. kwp: 9.8 # Maximale Generatorleistung (kWp) az: 180 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizont, Simuliert Verschattung durch Gelände, [mehr Informationen](https://doc.forecast.solar/horizon) (optional) - apikey: # API-Key, optional - interval: 1h # optional`} /> + apikey: # API Key, optional + interval: 1h # Intervall, optional`} /> @@ -763,7 +763,7 @@ Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Op efficiency: 100 # Wirkungsgrad [%], optional alphatemp: -0.004 # Temperaturkoeffizient, optional rossmodel: 0.0342 # Kühlung [Ross-Modell], Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional`} /> + interval: 1h # Intervall, optional`} /> @@ -780,15 +780,15 @@ Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting - type: template template: solcast site: # Ressource ID deiner Anlage - token: # Solcast API Token`} advanced={`tariffs: + token: # API Token`} advanced={`tariffs: solar: - type: template template: solcast site: # Ressource ID deiner Anlage - token: # Solcast API Token - from: # Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) - to: # Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) - interval: 3h # optional`} /> + token: # API Token + from: # Startzeit, Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) + to: # Endzeit, Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) + interval: 3h # Intervall, optional`} /> @@ -811,7 +811,7 @@ Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting template: victron idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen - interval: 1h # optional`} /> + interval: 1h # Intervall, optional`} /> diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx index a77bb0802e..8da8aceb23 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB Terra AC (OCPP) - +
+
+ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf @@ -21,29 +24,40 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-abb-tac` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx index f916303050..23e754ed77 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB Terra AC - +
+
+ Erfordert Firmware >= 1.6.5 @@ -40,12 +43,23 @@ Erfordert Firmware >= 1.6.5 id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `abb` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx index 91ede7a3f0..35445ee036 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Single (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-abl` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx index 911d43ac09..5045ee7359 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Single (SBCx) - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `abl-em4` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx index 0295b30c6e..8f80ed18f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Twin (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-abl` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx index 10aec80620..f25dfdf3d3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eM4 Twin (SBCx) - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `abl-em4` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx index 03924f47dc..6f75ded4fa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH1 - +
+
+ +
+
+ +
+
## Templateparameter `abl` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx index bbe90647b8..cc7395d1dd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH2 (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-abl` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx index b9fcf8f6e9..42e7f8b44a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH2 - +
+
+ +
+
+ +
+
## Templateparameter `abl` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx index 16049cbd9a..6798304376 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABL eMH3 (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-abl` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx index 804b35e0d8..323f6ec9ea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alfen Eve (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-alfen` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx index 19940c1dcb..607de1ea69 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alfen Eve - +
+
+ Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus extern zu steuern. In den Einstellungen muss "Active Load Balancing" aktiviert und "Energy Management System" als Data Source ausgewählt werden. Es wird empfohlen "ValidityTime" (Menu "TCP/IP EMS") auf 300s einzustellen. Falls die "Double"-Box verwendet wird müssen beide Ladepunkte getrennt voneinander hinzugefügt werden. Der erste Port (oder einzelne Port) ist unter ID 1 zugänglich, der zweite unter ID 2. @@ -27,12 +30,23 @@ Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus exte id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `alfen` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx index 4a9edc711c..9e4c7e001a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # alpha innotec - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx index 58ca24a2a2..4cebe39820 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alphatec Ladesäule Twin - +
+
+ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. @@ -34,12 +37,23 @@ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `alphatec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx index cee191fd04..a2224d44b3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alphatec Wallbox Mini - +
+
+ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. @@ -34,12 +37,23 @@ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `alphatec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx index 2a274ac38b..d78d0412ce 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alphatec Wallbox Power - +
+
+ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. @@ -34,12 +37,23 @@ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `alphatec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx index d910c96bb4..ffffcfe33c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox connect.business - +
+
+ +
+
+ +
+
## Templateparameter `amperfied` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx index b517ec0867..54a9b63bfb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox connect.home - +
+
+ +
+
+ +
+
## Templateparameter `amperfied` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx index 931307ed5d..d9bb8a8f14 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox connect.solar - +
+
+ +
+
+ +
+
## Templateparameter `amperfied-solar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx index fee0b5bebe..729cece3bb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amperfied Wallbox Energy Control - +
+
+ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. @@ -34,12 +37,23 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `heidelberg` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx index 7c976b1ab6..8d0ff62616 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ampure NEXT - +
+
+ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. @@ -23,6 +26,17 @@ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gel template: webasto-next host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Templateparameter `webasto-next` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx index ae69f9c9f7..a6cb398b5e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ampure Unite - +
+
+ 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `vestel` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx index c3757833ef..b6a5623714 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Audi Wallbox plus - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -29,6 +32,17 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt template: elliconnect ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elliconnect` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx index 982939e3b0..7cc023124e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Audi Wallbox pro - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -27,6 +30,17 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F template: ellipro ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `ellipro` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx index 9a54127824..3cde1c47c3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AUTEL AC Compact - +
+
+ Anleitung: * In der Autel Charge app, klicken sie auf “OCPP Server” @@ -26,29 +29,40 @@ Anleitung: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-autel` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx index 239894b47f..6bd8334b82 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AUTEL AC MaxiCharger - +
+
+ Anleitung: * In der Autel Charge app, klicken sie auf “OCPP Server” @@ -26,29 +29,40 @@ Anleitung: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-autel` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx index 7517091984..1f1e8c0e5c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Autoaid Business Wallbox - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-autoaid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx index 6f5fab7108..3cfc018a6e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Autoaid Intelligent Wallbox - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-autoaid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx index 7aa2b8ab62..b608d0cce0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AVM FritzDECT - +
+
+ +
+
+ +
+
## Templateparameter `fritzdect` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx index b91540a2b3..72dc90c737 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender CC612 - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx index d968a220fb..d9db8b83b1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender CC613 - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx index 4f431eefd4..b2ec9fd26e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender ICC1314 - +
+
+ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. @@ -27,12 +30,23 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-icc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx index 122ef519e1..8038016b66 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bender ICC1324 - +
+
+ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. @@ -27,12 +30,23 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-icc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx index 5eb5aaea56..2964dcc96a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BMW i Wallbox - +
+
+ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. @@ -37,12 +40,23 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +
+
+ +
+
## Templateparameter `keba-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx index bcbb5b8453..83a647545b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bosch SG Ready - +
+
+ Eingebunden via [EMSESP](https://emsesp.org/) @@ -22,16 +25,27 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> +
+
+ +
+
## Templateparameter `emsesp` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| `token` | | | nein | +| Token
`token` | | | nein | | Leistungsquelle
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx index 124bce1281..38bed8603e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bösch x-change - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `kermi` @@ -33,5 +47,5 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx index 36da472e1d..d0013b757b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Buderus Logamatic HMC 20 Z - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx index 6f36debcd0..7d7728175e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Buderus Logamatic HMC 20 - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx index 95a70864f7..5a9b000bfe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Buderus SG Ready - +
+
+ Eingebunden via [EMSESP](https://emsesp.org/) @@ -22,16 +25,27 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> +
+
+ +
+
## Templateparameter `emsesp` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| `token` | | | nein | +| Token
`token` | | | nein | | Leistungsquelle
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx index 84e55b7eae..fe82fe0e2c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # cFos Power Brain Solar - +
+
+ Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: @@ -25,6 +28,17 @@ Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigescha type: template template: cfos host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `cfos` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx index df3d837799..f4971380b4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # cFos Power Brain - +
+
+ Ein evtl. vorhandener S0 Zähler muss separat als Ladezähler konfiguriert werden. Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigeschaltet werden: @@ -25,6 +28,17 @@ Phasenumschaltung bietet nur die Solar-Variante und muss vom Anwender freigescha type: template template: cfos host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `cfos` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx index 53670bddca..1d23003415 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Charge Amps Halo - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-chargeamps` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx index d0799bde2c..21c8d2392a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Compleo eBox - +
+
+ +
+
+ +
+
## Templateparameter `innogy-ebox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx index b26342a58f..69fe088cce 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # CTA All-In-One Aeroplus - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx index 7ef53bd179..d51a7a05f0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # CUBOS C11E - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx index cd3ed97f2b..e189388123 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # CUBOS C22E - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx index a62a48601c..534265d7d6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Connect 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx index 7338920cfa..bfeb888f0c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Connect - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -29,6 +32,17 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt template: elliconnect ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elliconnect` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx index 307d04aecd..f077dd5a90 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Pro 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx index 13437dc1d2..f40a00c312 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Pro Eichrecht 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx index 025073dbda..45155311be 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Cupra Charger Pro - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -27,6 +30,17 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F template: ellipro ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `ellipro` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx index a941ce3341..7875d02839 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Dadapower Premium Wallbox - +
+
+ +
+
+ +
+
## Templateparameter `dadapower` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx index e12ed27c24..2bc6d87db1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DaheimLaden Wallbox - +
+
+ Die Wallbox muss über eine aktuelle Firmware mit Modbus-Unterstützung verfügen. In den Einstellungen muss "Nachladen" (Smart) bzw. "RSDA" (Touch) aktiviert sein @@ -23,6 +26,17 @@ Die Wallbox muss über eine aktuelle Firmware mit Modbus-Unterstützung verfüge template: daheimladen-mb host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Templateparameter `daheimladen-mb` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx index 1635511dc2..12169287de 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Daikin HomeHub (SG Ready) - +
+
+ +
+
+ +
+
## Templateparameter `daikin-homehub` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx index ab847ee320..6ffd01ebf3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta AC Max Basic - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `delta` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx index 1fc4bfd14a..7aadd9517a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta AC MAX Smart - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `delta` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx index 285ab09cae..bf8951a6f2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta SLIM Charger - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `delta` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx index 486e27c47d..edc8b5b43a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Delta Ultra Fast Charger - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `delta` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx index b4ddf1cbd7..faf3118716 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Demowallbox - +
+
+ Zu Demonstrationszwecken. Wallbox mit festen Werten. @@ -32,6 +35,17 @@ Zu Demonstrationszwecken. Wallbox mit festen Werten. enabled: true # Ladebereit, optional maxcurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) phases1p3p: false # Phasenumschaltung, optional`} /> +
+
+ +
+
## Templateparameter `demo-charger` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx index 152fa5c34c..f3cbdd8c12 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E.ON Drive eBox - +
+
+ +
+
+ +
+
## Templateparameter `innogy-ebox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx index 0c24618572..5ef2aa5e6d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E.ON Drive vBox - +
+
+ 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `vestel` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx index b3c8a1b2b6..b84530f6cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E3/DC Easy Connect - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx index cf611b3c5e..0c116a9456 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Charge Core - +
+
+ + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +
+
+ +
+
## Templateparameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | Benutzerkonto
`user` | Emailadresse | | ja | | Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | -| `charger` | | Beispiel: `EH______` | ja | +| Charger Seriennummer
`charger` | | Beispiel: `EH______` | ja | | Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | -| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | +| Authentifizierung aktiviert
`authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx index 1cac202664..faae4ece76 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Charge Lite - +
+
+ + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +
+
+ +
+
## Templateparameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | Benutzerkonto
`user` | Emailadresse | | ja | | Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | -| `charger` | | Beispiel: `EH______` | ja | +| Charger Seriennummer
`charger` | | Beispiel: `EH______` | ja | | Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | -| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | +| Authentifizierung aktiviert
`authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx index f240b39169..7191beae15 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Charge - +
+
+ + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +
+
+ +
+
## Templateparameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | Benutzerkonto
`user` | Emailadresse | | ja | | Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | -| `charger` | | Beispiel: `EH______` | ja | +| Charger Seriennummer
`charger` | | Beispiel: `EH______` | ja | | Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | -| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | +| Authentifizierung aktiviert
`authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx index 6187b3e09a..abe17c3af2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Easee Home - +
+
+ + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional)`} /> +
+
+ +
+
## Templateparameter `easee` @@ -30,9 +44,9 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | Benutzerkonto
`user` | Emailadresse | | ja | | Passwort
`password` | wie Login für Easee App oder Web Portal (https://easee.cloud) | | ja | -| `charger` | | Beispiel: `EH______` | ja | +| Charger Seriennummer
`charger` | | Beispiel: `EH______` | ja | | Zeitüberschreitung
`timeout` | Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. | Standard: `20s`
Beispiel: `10s` | nein | -| `authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | +| Authentifizierung aktiviert
`authorize` | Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx index 2b44fb2154..e4fe1520d8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ebee Wallbox - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx index 2ce9d1ece5..0b50e8d653 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # echarge cPH1 - +
+
+ Als Betriebsmodus muss `manual` ausgewählt sein @@ -27,13 +30,24 @@ Als Betriebsmodus muss `manual` ausgewählt sein template: hardybarth-ecb1 host: 192.0.2.2 # IP-Adresse oder Hostname connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `hardybarth-ecb1` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx index 4fae3f7cf7..48b41d8f24 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # echarge cPH2 - +
+
+ +
+
+ +
+
## Templateparameter `hardybarth-salia` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx index 25c40222af..8412e64e6e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # echarge cPμ2 - +
+
+ +
+
+ +
+
## Templateparameter `hardybarth-salia` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx index edcb76c4e8..09ef0cf3ea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EcoHarmony EVSE EPC 2.0 Plus - +
+
+ +
+
+ +
+
## Templateparameter `obo` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx index 0279e5d50c..099824580f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Edgetech Smart EVSE - +
+
+ +
+
+ +
+
## Templateparameter `smartevse` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx index a6288fde94..4294d7a5ec 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EEBUS kompatibel - +
+
+ +
+
+ +
+
## Templateparameter `eebus` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx index b800712d30..5945cb3c34 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elco - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx index 0774648ccd..c1b2af17b0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elecq Biz - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-elecq` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx index a111d8007d..4fcce7a343 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elecq Home - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-elecq` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx index 60ae317742..16b4d55b31 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elecq Station - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-elecq` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx index b97894dd70..cce097b4d8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # eledio go - +
+
+ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 @@ -21,29 +24,40 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-enercab` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx index f7ca69121d..64f84dd82e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Connect 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx index 110c73f4fa..5a6b5a7597 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Connect - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -29,6 +32,17 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt template: elliconnect ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elliconnect` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx index bfd46ddc3f..224958e1cf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Pro 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx index 0ff0622702..3924c2fa19 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Pro Eichrecht 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx index 0b3cde9f4a..e8e2fc7ade 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Elli Charger Pro - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -27,6 +30,17 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F template: ellipro ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `ellipro` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx index 2d97291649..aa432ee3b9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EM2GO Home - +
+
+ Benötigt FW version >= E3C_V1.1. mA Regelung benötigt FW version >= E3C_V1.3. @@ -22,6 +25,17 @@ Benötigt FW version >= E3C_V1.1. mA Regelung benötigt FW version >= E3C_V1.3. type: template template: em2go-home host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `em2go-home` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx index 351c5072a4..81cdbd179b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EM2GO Pro Power (OCPP/ONC) - +
+
+ Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP/ONC: 3.15) @@ -27,10 +30,21 @@ Aktuelle Firmware mit Modbus-Unterstützung notwendig (Pro Power: 1.01 bzw. OCPP id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `em2go` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx index 0ef1bc4c8e..534a199967 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # enercab smart - +
+
+ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 @@ -21,29 +24,40 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-enercab` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx index 7e57226e7d..13fcbf6a14 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EN+ AC EV Charger - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-enplus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx index 7223a27c60..4ef000a027 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ensto Chago Wallbox - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx index b9aff698ca..17020b66ca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EntraTek Power Dot Fix - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-entratek` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx index 45a0127257..f722481c8b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EntraTek Power Dot Pro 2 - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-entratek` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx index 8c8e70f71f..e38bca9ea3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ESL Walli LIGHT - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx index 7f09f1eede..ee25834f16 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # eSystems ghostONE - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: ghost ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `ghost` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx index 97ab281f71..6e1d420caa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Etrel INCH Duo - +
+
+ Die Wallbox muss sich im "Power" Modus befinden. @@ -29,6 +32,17 @@ Die Wallbox muss sich im "Power" Modus befinden. host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `etrel-duo` @@ -36,7 +50,7 @@ Die Wallbox muss sich im "Power" Modus befinden. |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `502` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx index 08d98f6f44..f1acf853c1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Etrel INCH - +
+
+ Die Wallbox muss sich im "Power" Modus befinden. @@ -23,6 +26,17 @@ Die Wallbox muss sich im "Power" Modus befinden. template: etrel host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Templateparameter `etrel` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx index 0d1556b6b5..f9ddd93f87 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx @@ -9,39 +9,53 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVBox Elvi - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # Zählernummer, optional`} advanced={`chargers: - name: my_charger type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # Zählernummer, optional connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-evbox-elvi` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | -| `meter` | | Standard: `true` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Zählernummer
`meter` | | Standard: `true` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx index 6c30e36ba1..53647b8851 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVBox Livo - +
+
+ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzurichten. Danach erkennt das Ladegerät evcc als HEMS-Gerät im Netzwerk. Verwende das Installationstool, um evcc als HEMS auszuwählen. Kopiere anschließend den angegebenen SKI aus der Installations-App und fügen ihn zu Ihrem YAML hinzu. @@ -23,6 +26,17 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri template: livo ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `livo` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx index 7b11372241..a81b1db013 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVSE DIN - +
+
+ +
+
+ +
+
## Templateparameter `evse-din` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx index 0b52393415..10ba1cadf6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # EVSE-WiFi - +
+
+ +
+
+ +
+
## Templateparameter `evsewifi` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx index 40539c3e70..251c587201 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Free2Move eProWallbox Move - +
+
+ +
+
+ +
+
## Templateparameter `eprowallbox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx index b20d65aeb4..7e6a5c67f4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Free2Move eProWallbox - +
+
+ +
+
+ +
+
## Templateparameter `eprowallbox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx index 31452169b6..c42bdb49b9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Free2move eSolutions eProWallbox - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-esolutions` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx index 1d961dee53..96cd34ae53 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Wattpilot (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-goe` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx index 14b7db4bf5..807af1078d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo GLB - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx index 92b7a6cdbf..5186dcc0d8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo GLB+ - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx index 6dfa4b91c2..4a7f22e70c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo LS4 compact - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx index 57146d397e..630c815ec7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Garo LS4 - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx index 4b21e52e83..1738dbef63 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger Gemini (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-goe` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx index 6265a6ec30..065db795d5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger Gemini - +
+
+ Benötigt mindestens Firmware 052.1 oder neuer. Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". @@ -24,6 +27,17 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak type: template template: go-e-v3 host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `go-e-v3` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx index a08bf476b6..20549d9b7c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger HOMEfix - +
+
+ Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. @@ -22,6 +25,17 @@ Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss akt type: template template: go-e host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `go-e` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx index e790137020..3f0d84fd57 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger HOME+ - +
+
+ Benötigt mindestens Firmware 052.1 oder neuer. Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". @@ -24,6 +27,17 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak type: template template: go-e-v3 host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `go-e-v3` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx index 0925c13fdc..ecff298031 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger PRO (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-goe` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx index 393ce1c00f..a94b5224d3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger PRO - +
+
+ Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss aktiviert sein. @@ -22,6 +25,17 @@ Benötigt mindestens Firmware 040.0 oder neuer. Das HTTP API v1 oder v2 muss akt type: template template: go-e host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `go-e` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx index e841717538..23c5426ae1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger V3 (OCPP) - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-goe` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx index 795fb76615..7cc7300daa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Charger V3 - +
+
+ Benötigt mindestens Firmware 052.1 oder neuer. Es wird die "HTTP-API v1"benötigt, für 1P/3P-Phasenumschaltung die "HTTP API v2". @@ -24,6 +27,17 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak type: template template: go-e-v3 host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `go-e-v3` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx index 0d70505ccd..70da3ab065 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hardy Barth cPH1 - +
+
+ Als Betriebsmodus muss `manual` ausgewählt sein @@ -27,13 +30,24 @@ Als Betriebsmodus muss `manual` ausgewählt sein template: hardybarth-ecb1 host: 192.0.2.2 # IP-Adresse oder Hostname connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `hardybarth-ecb1` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx index 79deeef9e2..8dde5fc3c3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hardy Barth cPH2 - +
+
+ +
+
+ +
+
## Templateparameter `hardybarth-salia` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx index 18d6ba0839..e6ad64f4d2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hardy Barth cPμ2 - +
+
+ +
+
+ +
+
## Templateparameter `hardybarth-salia` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx index 52ed4f6fca..90538c5293 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Heidelberg Energy Control - +
+
+ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. @@ -34,12 +37,23 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `heidelberg` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx index 4ac140cdaf..542535e19b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hesotec eBox - +
+
+ +
+
+ +
+
## Templateparameter `hesotec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx index 1cd4fe35ae..17345aa334 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hesotec eSat - +
+
+ +
+
+ +
+
## Templateparameter `hesotec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx index 976da4d73b..03e401f368 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Home Assistant Schalter - +
+
+ +
+
+ +
+
## Templateparameter `homeassistant-switch` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx index 890cb58fe4..017794bc49 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Homecharge Homecharger - +
+
+ Die Verwendung mit evcc erfordert einen eingebauten Stromzähler (Ausführungen HC11L/HC22L Energy oder Profi). Die OCPP-Konfiguration erfolgt über den EFR-SECC-Ladecontroller über die URL http://host/secc. @@ -23,29 +26,40 @@ Den Zugang erfragen Sie bitte beim Hersteller EFR (www.efr.de) oder Ihrem Händl - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-homecharge` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx index f51fccf0a3..5f777d25d2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx @@ -9,17 +9,20 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Homematic IP - +
+
+ +
+
+ +
+
## Templateparameter `homematic` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010)
`port` | | Standard: `2010` | nein | +| XML-RPC-Server Port-Nummer
`port` | | Standard: `2010`
Beispiel: `BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010` | nein | | Geräteadresse/Seriennummer
`device` | Homematic Geräte Id, wie im CCU Webfrontend angezeigt. | Beispiel: `0001EE89AAD848` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | | Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | -| Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2)
`meterchannel` | Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. | Standard: `6` | ja | -| Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1)
`switchchannel` | Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. | Standard: `3` | ja | -| XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h)
`cache` | Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. | Standard: `1s`
Beispiel: `5m` | nein | +| Kanalnummer des Power-Meters
`meterchannel` | Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. | Standard: `6`
Beispiel: `HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2` | ja | +| Kanalnummer der schaltbaren Steckdose
`switchchannel` | Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. | Standard: `3`
Beispiel: `HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1` | ja | +| XML-RPC API Cache Zeitraum
`cache` | Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. | Standard: `1s`
Beispiel: `5m` | nein | | Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | | Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx index 1611ce4932..ae1510c35e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # HomeWizard - +
+
+ +
+
+ +
+
## Templateparameter `homewizard` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx index e36814c744..649fabd58b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SCharger-22KT-S0 - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-huawei` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx index 8788bdb97c..ea0d5105ca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SCharger-7KS-S0 - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-huawei` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx index 70398f6d4e..ea1f46574e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IDM - +
+
+ +
+
+ +
+
## Templateparameter `idm` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx index c8059a2a37..8b84dc3dc2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Innogy eBox - +
+
+ +
+
+ +
+
## Templateparameter `innogy-ebox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx index cd5d26cac9..19cafca252 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # INRO Pantabox - +
+
+ +
+
+ +
+
## Templateparameter `pantabox` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx index 8ba1d48b81..d40882cbe4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Juice Charger Me - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx index 7c5786070a..5f931fdc06 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Junkers SG Ready - +
+
+ Eingebunden via [EMSESP](https://emsesp.org/) @@ -22,16 +25,27 @@ Eingebunden via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional)`} /> +
+
+ +
+
## Templateparameter `emsesp` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| `token` | | | nein | +| Token
`token` | | | nein | | Leistungsquelle
`powersource` | | Standard: `hpcurrpower`
Auswahl: `hpcurrpower`, `hppower` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx index 2b82c631db..49802b058b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC20 - +
+
+ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 @@ -27,12 +30,23 @@ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiv id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `Kathrein` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx index 0957bccd41..b377f6c5d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC35 - +
+
+ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 @@ -27,12 +30,23 @@ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiv id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `Kathrein` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx index e7fcb00b36..ff8fda6a3b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC40 E - +
+
+ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 @@ -27,12 +30,23 @@ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiv id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `Kathrein` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx index 670e41c669..8965d2ac2c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC40 - +
+
+ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 @@ -27,12 +30,23 @@ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiv id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `Kathrein` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx index 173df76fa1..ab2d246aba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC60 E - +
+
+ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 @@ -27,12 +30,23 @@ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiv id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `Kathrein` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx index 6d550e604d..2d87213740 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kathrein KWB-AC60 - +
+
+ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiviert werden. Getestet mit Firmware-Version v2.3.2 @@ -27,12 +30,23 @@ Der Modbus-Server (TCP-Port 502) muss über die Weboberfläche der Wallbox aktiv id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `Kathrein` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx index 7f20e61c47..0d8c492bdb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P20 - +
+
+ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. @@ -37,12 +40,23 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +
+
+ +
+
## Templateparameter `keba-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx index df9640175a..2af5ac5576 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P30 C-Series - +
+
+ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. @@ -37,12 +40,23 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +
+
+ +
+
## Templateparameter `keba-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx index 23a3005875..dca77d2497 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P30 X-Series - +
+
+ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. @@ -37,12 +40,23 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +
+
+ +
+
## Templateparameter `keba-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx index 7d1d6397c5..99c80a52fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P40 Pro - +
+
+ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. @@ -37,12 +40,23 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +
+
+ +
+
## Templateparameter `keba-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx index d6e1c6eddf..2b9f3f7b7d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact P40 - +
+
+ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. @@ -37,12 +40,23 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +
+
+ +
+
## Templateparameter `keba-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx index 3ab60cb8e2..44c0a6ca01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kermi x-center pro - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `kermi` @@ -33,5 +47,5 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx index 32e82b2a8d..9cf5de0dd3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kontron Solar Charger - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: ghost ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `ghost` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx index 0af651ca5f..b8f8a6a668 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Enector - +
+
+ Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. @@ -36,12 +39,23 @@ Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivieru id: 50 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `mennekes-compact` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx index def0f6e5cd..da73d59d0a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KSE wBX16 - +
+
+ +
+
+ +
+
## Templateparameter `kse` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx index f84dd9fb3e..67bb2e18ea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LadeFoxx EvLoad - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `phoenix-charx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx index 99c269e977..4d4705633f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LadeFoxx Mikro 2.0 - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `phoenix-charx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx index 1a2a499c45..5627f97e7c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Lambda EU-L Serie - +
+
+ Energiemanagementeinstellungen am Gerät: @@ -31,7 +34,18 @@ Energiemanagementeinstellungen am Gerät: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `lambda-zewotherm` @@ -39,5 +53,5 @@ Energiemanagementeinstellungen am Gerät: |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx index 1277b05d33..a5bb045e02 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LRT HOME Essential+ - +
+
+ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion kann man daran erkennen, dass die Seriennummer auf dem braunen Relais mit 2022 beginnt oder auf den kleinen weißen Relais eine 15 steht. Andernfalls bitte direkt an den Hersteller wenden. @@ -34,12 +37,23 @@ Die Hauptplatine benötigt eine aktuelle Firmware. Eine aktuelle Softwareversion id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `alphatec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx index ca5e8f8de5..41f5020b9a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMEDIO Professional - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx index 5720234954..95eaaede5b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON 4Business 700 - +
+
+ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. @@ -27,12 +30,23 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-icc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx index c599d968bc..fccc759a8c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON 4You 300 - +
+
+ Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. @@ -36,12 +39,23 @@ Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivieru id: 50 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `mennekes-compact` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx index b121ba311a..e3b00945bc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON 4You 500 - +
+
+ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. @@ -27,12 +30,23 @@ Die Konfigurationsoption 'Externes Energiemanagement' muss aktiviert sein. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-icc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx index 74a6a7d48c..3bae2447d3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON ChargeControl - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx index b8669dcb91..b068e8fe08 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Compact 2.0s - +
+
+ Die Wallbox muss mit Hilfe der DIP-Schalter auf der Hauptplatine als Satellit/Slave konfiguriert werden und Modbus RTU aktiviert sein (Bank S1: 4=ON, 5=ON, 7=OFF). Es sollte kein externes Meter direkt mit der Wallbox verbunden sein, da die Steuerung aller Funktionen direkt durch evcc erfolgt. @@ -36,12 +39,23 @@ Bei Kostal-Systemen mit Smart Energy Meter (KSEM) ist der zusätzliche Aktivieru id: 50 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `mennekes-compact` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx index f2f092d1d3..5d155b95e8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Premium - +
+
+ +
+
+ +
+
## Templateparameter `mennekes-hcc3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx index 7f2ca9841b..53ecb7ea1b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Professional - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx index 3a4919633b..c2a1fd38e9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes AMTRON Xtra - +
+
+ +
+
+ +
+
## Templateparameter `mennekes-hcc3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx index 41571186bd..06ed75f290 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes eMobility Gateway (ACU) - +
+
+ Zur Konfiguration die Weboberfläche der ACU aufrufen. Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J @@ -23,29 +26,40 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-mennekes-acu` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx index 51026a279f..6824c5ce3a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes Smart (ACU) - +
+
+ Zur Konfiguration die Weboberfläche der ACU aufrufen. Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J @@ -23,29 +26,40 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-mennekes-acu` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx index 7c9b660c18..1ab6352708 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mennekes Smart T (ACU) - +
+
+ Zur Konfiguration die Weboberfläche der ACU aufrufen. Setup, Backend, Übertragungsprotokoll: Open Charge Point Protocol v1.6J @@ -23,29 +26,40 @@ Setup, Backend, Backend-Server: Hier muss die evcc URL `ws://:8887 - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-mennekes-acu` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx index b6e2abb6c5..ba8ae6c694 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC ELWA 2 - +
+
+ +
+
+ +
+
## Templateparameter `ac-elwa-2` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Skalierungsfaktor der Leistungsvorgabe
`scale` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx index bdda33641d..d390c87182 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC•THOR 9s - +
+
+ +
+
+ +
+
## Templateparameter `ac-thor` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Temperatursensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Temperaturquelle
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | nein | | Skalierungsfaktor der Leistungsvorgabe
`scale` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx index 731ad93d74..f72982dc32 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC•THOR - +
+
+ +
+
+ +
+
## Templateparameter `ac-thor` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Temperatursensor
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Temperaturquelle
`tempsource` | | Standard: `1`
Auswahl: `1`, `2`, `3` | nein | | Skalierungsfaktor der Leistungsvorgabe
`scale` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx index 2c909ef518..74ed9fc035 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # myStrom Switch - +
+
+ +
+
+ +
+
## Templateparameter `mystrom` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx index d4eb515755..46284de9e7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nibe AP-AW10 - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx index 5bb99b4bcf..9696db2604 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Novelan WPR NET - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx index bc6eeef729..48471bc65b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # NRGkick Connect - +
+
+ NRGkick Ladeeinheit via HTTP (älter als 2022/2023) @@ -22,14 +25,25 @@ NRGkick Ladeeinheit via HTTP (älter als 2022/2023) type: template template: nrgkick-connect host: 192.0.2.2 # IP-Adresse oder Hostname - mac: + mac: # MAC Adresse password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen`} /> +
+
+ +
+
## Templateparameter `nrgkick-connect` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| `mac` | | | ja | +| MAC Adresse
`mac` | | | ja | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx index 1b1740d2b8..87342ea3d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # NRGkick Gen2 - +
+
+ + phases1p3p: false # Phasenumschaltung aktiviert, Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional)`} /> +
+
+ +
+
## Templateparameter `nrggen2` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `phases1p3p` | Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. | | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Phasenumschaltung aktiviert
`phases1p3p` | Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx index 72d5cb29e8..a4ad366ef1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OBO Bettermann Ion - +
+
+ +
+
+ +
+
## Templateparameter `obo` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx index 33b4ce4723..0c53c4923a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OCPP 1.6J kompatibel (Smart Charging) - +
+
+ Bei OCPP verbindet sich die Wallbox (Client) zu evcc (Server). Die Wallbox muss daher evcc via Hostname (funktionierende DNS-Auflösung erforderlich!) oder über die IP-Adresse auf Port 8887 erreichen können. @@ -39,29 +42,40 @@ Die konkrete Konfiguration und der tatsächlich nutzbare Funktionsumfang hängen - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx index c3fca183ce..bda62a28ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OpenEVSE - +
+
+ Benötigt mindestens Firmware 7.0 oder neuer. @@ -24,6 +27,17 @@ Benötigt mindestens Firmware 7.0 oder neuer. host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +
+
+ +
+
## Templateparameter `openevse` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx index 6f7cbdeb1a..5abe203a6b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # openWB Pro - +
+
+ +
+
+ +
+
## Templateparameter `openwb-pro` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx index ff39e51d05..5398a4f732 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # openWB series2 - +
+
+ Die Wallbox muss als Ladepunkt konfiguriert sein. @@ -28,12 +31,23 @@ Die Wallbox muss als Ladepunkt konfiguriert sein. host: 192.0.2.2 # IP-Adresse oder Hostname connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional phases1p3p: false # Phasenumschaltung vorhanden, optional`} /> +
+
+ +
+
## Templateparameter `openwb` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | | Phasenumschaltung vorhanden
`phases1p3p` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx index 2ed389ad0e..20a03929a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # openWB Software 2.x - +
+
+ Erfordert [`Software 2.x`](https://github.com/openWB/core). Folgende Änderungen sind unter dem `Einstellungen`-Reiter erforderlich: @@ -42,12 +45,23 @@ Folgende Änderungen sind unter dem `Einstellungen`-Reiter erforderlich: port: 1502 # Port connector: 1 # Ladepunkt (falls >1 Ladepunkt), optional phases1p3p: true # Phasenumschaltung vorhanden, optional`} /> +
+
+ +
+
## Templateparameter `openwb-2.0` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | | Phasenumschaltung vorhanden
`phases1p3p` | | Standard: `true` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx index fdcd8407be..0d389bf5b2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Optec Mobility One - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx index 2a827a67ea..3d9b59e4a6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Orbis Viaris - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-orbis` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx index 63f10f1762..4d596472fa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # PC Electric Garo - +
+
+ Es können momentan nur als Master konfigurierte Geräte verwendet werden! @@ -23,6 +26,17 @@ Es können momentan nur als Master konfigurierte Geräte verwendet werden! template: pcelectric-garo host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional`} /> +
+
+ +
+
## Templateparameter `pcelectric-garo` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx index e9304f71d9..f324e2c4db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peblar Business - +
+
+ Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. @@ -27,12 +30,23 @@ Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `peblar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx index 1528b514f1..04aa540331 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peblar Home Plus - +
+
+ Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. @@ -27,12 +30,23 @@ Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `peblar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx index ea14452341..79fa3761c9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peblar Home - +
+
+ Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP über Port 502. Der Modbus-Server muss über die Weboberfläche des Ladegeräts aktiviert werden. Stellen Sie sicher, dass Smart-Charging-Strategien deaktiviert und auf Standard gesetzt sind. @@ -27,12 +30,23 @@ Peblar-Ladegeräte mit Firmware-Version 1.6 und höher unterstützen Modbus TCP id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `peblar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx index 5014738e72..8ef549b5c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact CHARX - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `phoenix-charx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx index 253ff24f16..178c09982e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EM-CP-PP-ETH - +
+
+ +
+
+ +
+
## Templateparameter `phoenix-em-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx index 1652bdee12..10dc565de0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx index 645ef77635..c8cbed0c87 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx index fd7136f5a8..ecea5865f6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx index adfa4c975e..170408d6ba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx index 933fea0dee..446f9edcc2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Phoenix Contact EV-SER - +
+
+ +
+
+ +
+
## Templateparameter `phoenix-ev-ser` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx index eb7fc20685..e7623af210 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Plugchoice - +
+
+ Über Plugchoice angeschlossene Ladegeräte können die OCPP-Proxy-Funktionalität nutzen, um eine Verbindung zu anderen Backoffices herzustellen und gleichzeitig die volle Kontrolle über EVCC zu behalten. Dies ermöglicht eine nahtlose Verwaltung der bei Plugchoice registrierten Ladegeräte direkt vom EVCC aus. @@ -28,22 +31,33 @@ Diese Anpassungen ermöglichen eine häufigere und detailliertere Meldung der La - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456)`} advanced={`chargers: + token: # Token, API Token + identity: AA123456 # Identity des Ladepunkts`} advanced={`chargers: - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456) - connector: 1 # Ladepunkt (falls >1 Ladepunkt), Anschluss-ID (üblicherweise 1)`} /> + token: # Token, API Token + identity: AA123456 # Identity des Ladepunkts + connector: 1 # Anschluss-ID`} /> +
+
+ +
+
## Templateparameter `plugchoice` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | API Token | | ja | -| `identity` | Identity des Ladepunkts (z.B. AA123456) | | ja | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | Anschluss-ID (üblicherweise 1) | Standard: `1` | ja | +| Token
`token` | API Token | | ja | +| Identity des Ladepunkts
`identity` | | Beispiel: `AA123456` | ja | +| Anschluss-ID
`connector` | | Standard: `1`
Beispiel: `1` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx index 1c8bb313de..4bb3be9cad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Porsche Mobile Charger Connect - +
+
+ +
+
+ +
+
## Templateparameter `pmcc` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx index a56e4d26ad..a4dd7956c1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Porsche Mobile Charger Plus - +
+
+ +
+
+ +
+
## Templateparameter `pmcp` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx index e411cd46ad..6030beff18 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Porsche Wallbox - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: porsche-wallbox ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `porsche-wallbox` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx index 9b4deb3d72..73eeaceda9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht Alpha XT - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `pracht-alpha` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx index 2e8b630717..c964b86945 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht Mono XT - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `pracht-alpha` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx index cd560aa9e4..179062e818 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht PNI - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `pracht-alpha` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx index ce766e0539..c2a49cd70c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pracht XT+ - +
+
+ 1 Ladepunkt), optional`} /> +
+
+ +
+
## Templateparameter `pracht-alpha` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | -| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | +| Ladepunkt (falls >1 Ladepunkt)
`connector` | | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx index 5d2644cc92..8b03100ae6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pulsares SimpleBox - +
+
+ +
+
+ +
+
## Templateparameter `pulsares` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx index 8bbc52ec56..d59f1c0280 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Pulsatrix - +
+
+ +
+
+ +
+
## Templateparameter `pulsatrix` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx index c37ab4dd03..ba5ee09dd4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Qcells Q.HOME EDRIVE A - +
+
+ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. @@ -34,12 +37,23 @@ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem e id: 70 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `solax` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx index a966da08b7..f46649c9dc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Roth ThermoAura - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx index 83a157f2c0..beb46a3538 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Roth ThermoTerra - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx index f31550ad51..41b8f47b92 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Schneider EVlink Pro - +
+
+ +
+
+ +
+
## Templateparameter `schneider-evlink-v3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx index 6d68959462..a9b518b755 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Schrack i-CHARGE CION - +
+
+ +
+
+ +
+
## Templateparameter `ichargecion` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx index 5dcc642663..90ff79a5f3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SENEC Wallbox pro s - +
+
+ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. @@ -34,12 +37,23 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `heidelberg` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx index f7e4791aee..8bf773be5d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SENEC Wallbox pro - +
+
+ +
+
+ +
+
## Templateparameter `abl` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx index 59f9038219..cfdc1a8ea4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 1 - +
+
+ +
+
+ +
+
## Templateparameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | | Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | | Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | | Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx index 2f8cb3548f..60cf8b1e39 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Plug S - +
+
+ +
+
+ +
+
## Templateparameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | | Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | | Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | | Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx index 5d2272d6d0..eda715d6e8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Plus 1 - +
+
+ +
+
+ +
+
## Templateparameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | | Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | | Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | | Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx index 679db318f6..78e87805ce 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 1 - +
+
+ +
+
+ +
+
## Templateparameter `shelly` @@ -42,7 +56,7 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | | Standby-Leistung
`standbypower` | Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet | Standard: `15`
Einheit: W | nein | | Integriertes Gerät
`integrateddevice` | Fest angeschlossenes Gerät. Keine Ladevorgänge | | nein | | Wärmeerzeuger
`heating` | Zeigt °C anstatt % an | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx index 065e9f07c0..fd4a9e0584 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens Versicharge GEN3 - +
+
+ Erfordert Firmware >= 2.135 @@ -27,12 +30,23 @@ Erfordert Firmware >= 2.135 id: 2 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `versicharge` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx index 3142169e55..9c547f7712 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Charger Connect - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx index 96c0b32360..443d563e10 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Charger Pro Eichrecht - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx index 1428ea0bcd..50751e06c6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Charger Pro - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx index e6b714629f..d304ae52ab 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda iV Charger Connect - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -29,6 +32,17 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt template: elliconnect ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elliconnect` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx index 88e95b309c..3e39bb7821 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda iV Charger Connect+ - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -27,6 +30,17 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F template: ellipro ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `ellipro` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx index 27c1dd418f..abe7fd7d50 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA eCharger - +
+
+ Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. @@ -24,6 +27,17 @@ Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rech host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen`} /> +
+
+ +
+
## Templateparameter `smaevcharger` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx index 73f81afccb..1bb5c2de01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA EV Charger - +
+
+ Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rechte "Administrator" haben. @@ -24,6 +27,17 @@ Der EV Charger muss sich im Modus "Fast" befinden und der Benutzer muss die Rech host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen`} /> +
+
+ +
+
## Templateparameter `smaevcharger` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx index d67129dc9f..dc432f7b68 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro Charger - +
+
+ +
+
+ +
+
## Templateparameter `ichargecion` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx index 3ae4e7958d..85effba909 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # smartWB - +
+
+ +
+
+ +
+
## Templateparameter `smartwb` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx index 627c1e4b61..edb37affe5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarEdge Home EV Charger - +
+
+ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenumschaltung wird zusätzlich der Keba Phasenumschalter (KeContact S10) benötigt und in den Wallboxeinstellungen muss die Umschaltsteuerung per Modbus aktiviert werden. Bei der x-Serie im WebMenü, bei der C-Serie per Modbus durch setzen des Wertes "3" im Register 5050. @@ -37,12 +40,23 @@ Erfordert Firmwareversion 3.10.42 (C-series) bzw. 1.11 (X-series). Zur Phasenums host: 192.0.2.2 # Hostname port: 502 # Port welcomecharge: # Laden bei Verbindung, Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. (optional)`} /> +
+
+ +
+
## Templateparameter `keba-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Laden bei Verbindung
`welcomecharge` | Wallbox gibt kurzzeitige Ladefreigabe bei Fahrzeugverbindung. Das ermöglicht es Fahrzeugen, die eine Stromversorgung beim Anschließen benötigen, einen Fehlerzustand zu vermeiden. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx index 5a8830372b..e106366c44 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax X3-EVC - +
+
+ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. @@ -34,12 +37,23 @@ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem e id: 70 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `solax` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx index 1504eb382f..bfcccba85b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen sonnenCharger - +
+
+ Die Wallbox muss sich im "Power" Modus befinden. @@ -23,6 +26,17 @@ Die Wallbox muss sich im "Power" Modus befinden. template: etrel host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Templateparameter `etrel` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx index 9371153c2c..6de9e50f2f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Spelsberg Wallbox Smart Pro - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx index 013c3ea84d..71c966a2b3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Stark in Strom Easy - +
+
+ +
+
+ +
+
## Templateparameter `evse-din` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx index 7fafd494f3..8448597a8f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Stiebel Eltron LWA/LWZ (SG Ready) - +
+
+ +
+
+ +
+
## Templateparameter `stiebel-lwa` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx index 11c5272f77..fdd5567199 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Stiebel Eltron WPM (SG Ready) - +
+
+ +
+
+ +
+
## Templateparameter `stiebel-wpm` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater`, `buffer` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx index f2e0142503..bed181b7d5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow AC011E-01 - +
+
+ +
+
+ +
+
## Templateparameter `sungrow` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx index bd19607162..2e7684ded6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow AC011E - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-sungrow` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx index 33e2a52349..87de9170f8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow AC22E-01 - +
+
+ +
+
+ +
+
## Templateparameter `sungrow` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx index fcdf240a74..c2ae4c5bca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota einphasig - +
+
+ +
+
+ +
+
## Templateparameter `tasmota` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx index e8a4081fba..9e7534f104 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tecalor THZ (SG Ready) - +
+
+ +
+
+ +
+
## Templateparameter `stiebel-lwa` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx index 8a6a17792c..17dd3035e7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TechniSat Technivolt - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx index 0f552fdf64..f969a6aefc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla Wall Connector (Gen 3) - +
+
+ Die TWC Wallbox ist nicht direkt regelbar. Die Regelung erfolgt über das Fahrzeug. Das Fahrzeug muss am TWC3 Ladepunkt ausgewählt sein. Aktuell ausschließlich mit [Tesla Fahrzeugen](https://docs.evcc.io/docs/devices/vehicles#tesla) nutzbar. @@ -22,6 +25,17 @@ Die TWC Wallbox ist nicht direkt regelbar. Die Regelung erfolgt über das Fahrze type: template template: twc3 host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `twc3` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx index ee8146b422..6961af7bea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tessie - +
+
+ Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung des Ladezustands und die Konfiguration des maximalen Stroms. @@ -23,7 +26,18 @@ Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung de template: tessie vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind token: # Tessie API Token - location: tessiehome # Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive)`} /> + location: tessiehome # Ort, Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive)`} /> +
+
+ +
+
## Templateparameter `tessie` @@ -31,5 +45,5 @@ Ladegerät, das über die Tessie-API verbunden ist. Ermöglicht die Steuerung de |-----------|-----------|------|----------| | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | | Tessie API Token
`token` | | | ja | -| Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive)
`location` | | Beispiel: `tessiehome` | ja | +| Ort
`location` | Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) | Beispiel: `tessiehome` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx index e31f177625..b6c428d99b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tigo GO EV Charger - +
+
+ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem entkoppelt sein. @@ -34,12 +37,23 @@ Die Wallbox muss sich im Modus "Schnell" befinden und vom Wechselrichtersystem e id: 70 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `solax` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx index 998eebba39..46d765d723 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP Charger Pro - +
+
+ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. @@ -25,7 +28,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional)`} advanced={`chargers: + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -33,9 +36,20 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +
+
+ +
+
## Templateparameter `tinkerforge-warp` @@ -45,7 +59,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl | Port
`port` | MQTT Broker Port | Standard: `1883` | nein | | Topic
`topic` | Topic (ohne / am Anfang) | Standard: `warp` | nein | | Zeitüberschreitung
`timeout` | Akzeptiere keine Daten die älter sind als dieser Wert | Standard: `30s`
Beispiel: `10s` | nein | -| `energymanager` | WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) | | nein | +| Energiemanager MQTT Topic
`energymanager` | WEM Firmware v2 erforderlich. | | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx index 61ebcda67e..375ad41c63 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP Charger Smart - +
+
+ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzlich der WARP Energy Manager benötigt. @@ -25,7 +28,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional)`} advanced={`chargers: + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -33,9 +36,20 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +
+
+ +
+
## Templateparameter `tinkerforge-warp` @@ -45,7 +59,7 @@ WARP Firmware v2 erforderlich. Für automatische Phasenumschaltung wird zusätzl | Port
`port` | MQTT Broker Port | Standard: `1883` | nein | | Topic
`topic` | Topic (ohne / am Anfang) | Standard: `warp` | nein | | Zeitüberschreitung
`timeout` | Akzeptiere keine Daten die älter sind als dieser Wert | Standard: `30s`
Beispiel: `10s` | nein | -| `energymanager` | WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) | | nein | +| Energiemanager MQTT Topic
`energymanager` | WEM Firmware v2 erforderlich. | | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx index 3f936b9a96..83b3e88165 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP3 Charger Pro - +
+
+ Die automatische Phasenumschaltung bei 1p Fahrzeugen muss deaktiviert sein. Siehe https://docs.warp-charger.com/docs/mqtt_http/api_reference/evse#evse_phase_auto_switch_warp3. @@ -34,6 +37,17 @@ Die automatische Phasenumschaltung bei 1p Fahrzeugen muss deaktiviert sein. Sieh timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional)`} /> +
+
+ +
+
## Templateparameter `tinkerforge-warp3` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx index b391e7f494..9494ce109e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TinkerForge WARP3 Charger Smart - +
+
+ +
+
+ +
+
## Templateparameter `tinkerforge-warp3-smart` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx index f8bd2a1ce3..0a33069ca2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link H-Series Smart Plug - +
+
+ +
+
+ +
+
## Templateparameter `tplink` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx index 13b3482f2d..a84de8f53a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link Tapo P-Series Smart Plug - +
+
+ +
+
+ +
+
## Templateparameter `tapo` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx index dc71bf9799..c745473352 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ubitricity Heinz - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx index bdbce3d5e1..3245c0c169 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # V2C Trydan - +
+
+ +
+
+ +
+
## Templateparameter `trydan` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx index 803773dc48..9d383a1ad6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Vaillant SensoNET (SG Ready) - +
+
+ Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird durch die ID identifiziert. Die Boost Temperatur wird in Grad Celsius angegeben. Ist eine Boost Temperatur angegeben, wird die Boostzone aktiviert, anderenfalls Warmwasser. @@ -23,9 +26,20 @@ Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird d template: vaillant user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - realm: DE # [DE, AT] (optional) - zone: # Id der Boostzone (optional) - setpoint: # Boost Temperatur (optional)`} /> + realm: DE # Region, [DE, AT] (optional) + zone: # ID der Boostzone, optional + setpoint: # Boost Temperatur, optional`} /> +
+
+ +
+
## Templateparameter `vaillant` @@ -33,7 +47,7 @@ Die Boost Funktion erwärmt Warmwasser oder eine Boostzone. Die Boostzone wird d |-----------|-----------|------|----------| | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `realm` | | Standard: `DE`
Auswahl: `DE`, `AT` | nein | -| `zone` | Id der Boostzone | | nein | -| `setpoint` | Boost Temperatur | | nein | +| Region
`realm` | | Standard: `DE`
Auswahl: `DE`, `AT` | nein | +| ID der Boostzone
`zone` | | | nein | +| Boost Temperatur
`setpoint` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx index 392b57ef36..aa9424a550 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Vestel Connect Plus - +
+
+ 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `vestel` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx index 07bac2a8e7..484c79a68b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Vestel EVC04 Home Smart - +
+
+ 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `vestel` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx index f8ff064976..fd9c0f49a3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EV Charging Station (via GX) - +
+
+ Trage den Host des GX-Gerätes (nicht der Wallbox) ein. Die Wallbox muss sich im Modus "Manual" befinden und Modbus ID 100 konfiguriert sein. @@ -27,10 +30,21 @@ Trage den Host des GX-Gerätes (nicht der Wallbox) ein. Die Wallbox muss sich im id: 100 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `victron` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx index b61b976d3e..675eea781b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EV Charging Station - +
+
+ Trage den Host der Wallbox (nicht des GX-Geräts) ein und stelle sicher, dass die Wallbox sich im Modus "Manual" befindet. @@ -27,10 +30,21 @@ Trage den Host der Wallbox (nicht des GX-Geräts) ein und stelle sicher, dass di id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `victron-evcs` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx index 4ecb8dff72..3a25e38ddd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Viessmann Heatpump (SG Ready) - +
+
+ Einmalige Warmwasserbereitung auf eine konfigurierbare Solltemperatur. Das Gerät entscheidet eigenständig, ob die Wärmepumpe oder die elektrische Zusatzheizung (falls vorhanden) genutzt wird. @@ -28,6 +31,17 @@ Einmalige Warmwasserbereitung auf eine konfigurierbare Solltemperatur. Das Gerä installation_id: # Installation ID, Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...
Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: \`\`\` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= \`\`\` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable 'CODE' nur 20 Sekunden gültig ist): \`\`\` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ | grep "^location: " \ | sed 's/.*\\?code=\\(.*\\).*/\\1/' \ | tr -d '[:space:]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE | jq --raw-output .access_token) \`\`\` Damit können wir jetzt die Installation ID abfragen: \`\`\` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ | jq '.data[].id' \`\`\` device_id: 0 # Device ID, normalerweise \`0\` target_temperature: 45 # Zieltemperatur für Einmal-Warmwasser-Zubereitung (°C), max. 60°C`} /> +
+
+ +
+
## Templateparameter `viessmann` @@ -36,8 +50,8 @@ Einmalige Warmwasserbereitung auf eine konfigurierbare Solltemperatur. Das Gerä | Benutzerkonto
`user` | Registrieren auf \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | ja | | Passwort
`password` | Für den konfigurierten Viessmann Account. | | ja | | Client ID
`clientid` | Konfigurieren in \[app.developer.viessmann.com\](https://app.developer.viessmann.com) | | ja | -| Gateway Serial
`gateway_serial` | Seriennummer des VitoConnect modul (VitoCare App -> Einstellungen -> Kommunikationsmodul -> Seriennummer) | | ja | -| Installation ID
`installation_id` | Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...<br/> Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: ``` VIESSMANN_USER=<your-user> VIESSMANN_PASS=<your-password> VIESSMANN_CLIENT_ID=<your-clientid> ``` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable 'CODE' nur 20 Sekunden gültig ist): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ \| grep "^location: " \ \| sed 's/.*\?code=\(.*\).*/\1/' \ \| tr -d '\[:space:\]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE \| jq --raw-output .access_token) ``` Damit können wir jetzt die Installation ID abfragen: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ \| jq '.data\[\].id' ``` | | ja | +| Gateway Serial
`gateway_serial` | Seriennummer des VitoConnect modul (VitoCare App -> Einstellungen -> Kommunikationsmodul -> Seriennummer) | | ja | +| Installation ID
`installation_id` | Leider kann man die Installation ID nicht einfach in der Viessmann App einsehen - stattdessen müssen wir die folgenden Kommandos in der Kommandozeile ausführen. Es ist uns bewusst, dass das nicht für jeden Benutzer einfach umsetzbar ist, aber bisher haben wir leider keinen besseren Ablauf...
Vorraussetzungen: curl, jq, und die folgenden Umgebungsvariblen: ``` VIESSMANN_USER= VIESSMANN_PASS= VIESSMANN_CLIENT_ID= ``` Dann holen wir uns einen oauth token (n.b. am besten den gesamten Block in das Terminal kopieren, da die Zwischenvariable 'CODE' nur 20 Sekunden gültig ist): ``` VIESSMANN_REDIRECT_URI="http://localhost:4200/" VIESSMANN_CODE_CHALLENGE="5M5nhkBfkWZCGfLZYcTL-l7esjPUN7PpZ4rq8k4cmys" VIESSMANN_CODE_VERIFIER="6PygdmeK8JKPuuftlkc6q4ceyvjhMM_a_cJrPbcmcLc-SPjx2ZXTYr-SOofPUBydQ3McNYRy7Hibc2L2WtVLJFpOQ~Qbgic455ArKjUz9_UiTLnO6q8A3e.I_fIF8hAo" VIESSMANN_CODE=$(curl -X POST --silent \ --user $VIESSMANN_USER:$VIESSMANN_PASS \ --output /dev/null \ --dump-header - \ "https://iam.viessmann.com/idp/v3/authorize?client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&scope=IoT%20User%20offline_access&response_type=code&code_challenge=$VIESSMANN_CODE_CHALLENGE&code_challenge_method=S256" \ \| grep "^location: " \ \| sed 's/.*\?code=\(.*\).*/\1/' \ \| tr -d '\[:space:\]') TOKEN_RESPONSE=$(curl -XPOST --silent \ -H "Content-Type: application/x-www-form-urlencoded" \ --data "grant_type=authorization_code&client_id=$VIESSMANN_CLIENT_ID&redirect_uri=$VIESSMANN_REDIRECT_URI&code_verifier=$VIESSMANN_CODE_VERIFIER&code=$VIESSMANN_CODE" \ https://iam.viessmann.com/idp/v3/token) VIESSMANN_TOKEN=$(echo $TOKEN_RESPONSE \| jq --raw-output .access_token) ``` Damit können wir jetzt die Installation ID abfragen: ``` curl --silent -H "Authorization: Bearer $VIESSMANN_TOKEN" \ https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true \ \| jq '.data\[\].id' ``` | | ja | | Device ID
`device_id` | normalerweise `0` | | ja | | Zieltemperatur für Einmal-Warmwasser-Zubereitung
`target_temperature` | max. 60°C | Standard: `45`
Einheit: °C | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx index 7f7d6a4b21..ca5e5a9317 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Viridian EV EVSE EPC 2.0 Plus - +
+
+ +
+
+ +
+
## Templateparameter `obo` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx index dbb67fdfb2..c831676464 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen Charger Connect 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx index c35e8f3e1c..d80c9001fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen Charger Pro 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx index fe6acb2b94..ae70fd7b57 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen Charger Pro Eichrecht 2 - +
+
+ Die Wallbox muss im normalen Lademodus betrieben werden. @@ -27,6 +30,17 @@ Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. template: elli-2 ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elli-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx index abd76c27d6..f92b1b22db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen ID. Charger Connect - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -29,6 +32,17 @@ Hinweis: Wenn du deiner Wallbox nachträglich einen Energiezähler hinzugefügt template: elliconnect ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `elliconnect` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx index b843e7d5df..5746c13803 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen ID. Charger Pro - +
+
+ Dem Gerät muss eine feste IP Adresse zugewiesen sein (Manuell oder per DHCP). @@ -27,6 +30,17 @@ Wichtig: Die möglichst reibungslose Funktionalität ist aufgrund von Software-F template: ellipro ski: # Identifikationsschlüssel (SKI), Üblicherweise im Web Interface der Wallbox zu finden ip: 192.0.2.2 # IP-Adresse, optional`} /> +
+
+ +
+
## Templateparameter `ellipro` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx index 385ea4b2e2..ce5ff880e2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time One - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> +
+
+ +
+
## Templateparameter `volttime` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | -| `serial_number` | Seriennummer (z. B. 1008621) | | ja | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| Seriennummer
`serial_number` | Seriennummer (z. B. 1008621) | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx index b0199ff719..67fea3ab6b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time Source 2 - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> +
+
+ +
+
## Templateparameter `volttime` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | -| `serial_number` | Seriennummer (z. B. 1008621) | | ja | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| Seriennummer
`serial_number` | Seriennummer (z. B. 1008621) | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx index 8d4b4e3e3d..4edc1d7cef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time Source 2s - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> +
+
+ +
+
## Templateparameter `volttime` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | -| `serial_number` | Seriennummer (z. B. 1008621) | | ja | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| Seriennummer
`serial_number` | Seriennummer (z. B. 1008621) | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx index b82cdb0065..c6e22d360c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volt Time Source - +
+
+ + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621)`} /> +
+
+ +
+
## Templateparameter `volttime` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | -| `serial_number` | Seriennummer (z. B. 1008621) | | ja | +| Token
`token` | API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) | | ja | +| Seriennummer
`serial_number` | Seriennummer (z. B. 1008621) | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx index ef56c59886..fbf224f27f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wallbe Eco 2.0(s) - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx index 8c8dbb905e..9a681807e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wallbe Eco - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx index 6ab2dd59df..3f800e0d76 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wallbe Pro - +
+
+ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Controller-Firmware wird empfohlen. @@ -27,12 +30,23 @@ DIP Schalter 10 des Controllers muss auf 'ON' gestellt sein. Eine aktuelle Contr id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `phoenix-ev-eth` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx index 33b68eea42..8d3653109f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Commander 2 (FW 5.x) - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `wallbox-fw5` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx index 4b0be8a1f7..7e12c61427 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Commander 2 - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-wallbox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx index 5bf247b395..aa999045eb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Copper SB (FW 5.x) - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `wallbox-fw5` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx index 34f9db496d..e08b90c18d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Copper SB - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-wallbox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx index 6887a5d29d..a8dc4cc102 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Max (FW 5.x) - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `wallbox-fw5` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx index 385c11544d..944021fecc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Max - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-wallbox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx index 294310a8fb..0a8aeba2cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Plus (FW 5.x) - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `wallbox-fw5` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Standard: `-Current.Offered,Power.Offered`
Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx index aa6bdefcff..66bc5253e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # wallbox Pulsar Plus - +
+
+ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/ @@ -27,29 +30,40 @@ Anleitung: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-set - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-wallbox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx index 13eab1c834..5351ec3b97 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Walther Werke Basic Evo Pro - +
+
+ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen müssen für die externe Steuerung auf Follower-Modus konfiguriert sein (DIP S5/4 OFF). Jede Box braucht eine individuelle Modbus-ID (DIP S4). Auf korrekte RS485-Verkabelung inkl. Busterminierung (DIP S6/2) achten. @@ -34,12 +37,23 @@ Bitte das Handbuch zur Verkabelung und Konfiguration genau lesen. Alle Boxen mü id: 1 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `heidelberg` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx index 06564f93b2..7848d808db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Webasto Live - +
+
+ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein. @@ -27,12 +30,23 @@ Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Reg id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `bender-cc` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx index 6687836b0b..1d354c72c4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Webasto NEXT - +
+
+ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gelesen werden. @@ -23,6 +26,17 @@ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gel template: webasto-next host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional`} /> +
+
+ +
+
## Templateparameter `webasto-next` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx index aa68bc935b..b79f18d189 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Webasto Unite - +
+
+ 1P3P erfordert Firmware 3.187.0 oder neuer, RFID erfordert 3.156.0 oder neuer. @@ -27,12 +30,23 @@ import TabItem from '@theme/TabItem'; id: 255 host: 192.0.2.2 # Hostname port: 502 # Port`} /> +
+
+ +
+
## Templateparameter `vestel` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx index bd6161e5f9..9bc42407a3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx @@ -9,16 +9,30 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller AC Smart - +
+
+ +
+
+ +
+
## Templateparameter `weidmüller` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx index f2c4533606..9e59bd25a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wolf BWL - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx index 515d74d3cd..aa81f3c4fe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wolf BWS - +
+
+ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindestens Software v3.90.3. Aktivierung über SERVICE, Systemsteuerung, Konnektivität, Smart-Home-Interface. @@ -27,7 +30,7 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -37,14 +40,25 @@ Für Wärmepumpen mit Luxtronik 2.1 Steuerung. Nutzt modbus-tcp. Braucht mindest id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional)`} /> +
+
+ +
+
## Templateparameter `luxtronik` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | -| `heatoffset` | Anhebung der Heizwassertemperatur. | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | -| `wwoffset` | Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Anhebung der Heizwassertemperatur
`heatoffset` | | Standard: `0.0`
Beispiel: `2.0`
Einheit: K | nein | +| Anhebung der Warmwassertemperatur
`wwoffset` | Erhöht evtl. den Verschleiss des Kompressors. | Standard: `0.0`
Beispiel: `8.5`
Einheit: K | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx index 14bc7bc52f..6fd598dc1c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Go 2 - +
+
+ +
+
+ +
+
## Templateparameter `zaptec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `id` | Wallbox ID | | nein | +| ID
`id` | Wallbox ID | | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx index 339def8e98..36e47170a5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Go (OCPP) - +
+
+ OCPP Native mode @@ -23,29 +26,40 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-zaptec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx index 0c6aedc83b..9643c93a87 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Go - +
+
+ +
+
+ +
+
## Templateparameter `zaptec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `id` | Wallbox ID | | nein | +| ID
`id` | Wallbox ID | | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx index 4ae91fb588..64cbf223e3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zaptec Pro - +
+
+ +
+
+ +
+
## Templateparameter `zaptec` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `id` | Wallbox ID | | nein | +| ID
`id` | Wallbox ID | | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx index a7970062c4..abe80cbd71 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zewotherm EU-L Serie - +
+
+ Energiemanagementeinstellungen am Gerät: @@ -31,7 +34,18 @@ Energiemanagementeinstellungen am Gerät: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `lambda-zewotherm` @@ -39,5 +53,5 @@ Energiemanagementeinstellungen am Gerät: |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Temperaturquelle
`tempsource` | | Auswahl: `warmwater_top`, `warmwater_bottom`, `buffer_top`, `buffer_bottom` | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx index 27244a3ef5..0d735214aa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -9,38 +9,52 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ZJ Beny BCP EV charger - +
+
+ :8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form \`ws://:8887/\` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional`} /> + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional)`} /> +
+
+ +
+
## Templateparameter `ocpp-beny` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | +| Station ID
`stationid` | Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. | Beispiel: `EVB-P12354` | nein | | Anschlussnummer
`connector` | Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. | Standard: `1` | nein | -| Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! | | nein | -| Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction)
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. | Beispiel: `evcc` | nein | -| Zeitlimit für die Registrierung des Ladepunktes
`connecttimeout` | | Standard: `5m` | nein | -| Übertragungsintervall der Zählerwerte (MeterValueSampleInterval)
`meterinterval` | | Standard: `10s` | nein | -| Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData)
`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | +| Remote-Transaktion bei Fahrzeugverbindung starten
`remotestart` | Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) | | nein | +| Authentifizierungs-Token
`idtag` | Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) | Beispiel: `evcc` | nein | +| Zeitlimit für die Registrierung
`connecttimeout` | Zeitlimit für die Registrierung des Ladepunktes | Standard: `5m` | nein | +| Übertragungsintervall der Zählerwerte
`meterinterval` | Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) | Standard: `10s` | nein | +| Zählerwerte für die Übertragung
`metervalues` | Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx index 034c2000d0..1d1ddd0d31 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # A-Tronix - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> +
+
+ +
+
## Templateparameter `wattsonic` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `delay` | | Standard: `100ms` | nein | +| Verzögerung
`delay` | | Standard: `100ms` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx index 43a3c91f65..7336a35c69 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB A43 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `abb-ab` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx index 774ec57e93..d6f93a63de 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB A44 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `abb-ab` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx index cc5a096fce..e4b3a7d84f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB B23 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `abb-ab` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx index ea71c609e4..dec66ce8bc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ABB B24 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `abb-ab` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx index 2d40765701..1ddfcd5482 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Acrel ADW300 - +
+
+ @@ -100,10 +103,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `acrel-adw300` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx index 3d4e4b48cc..32cb1afc74 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ads-tec StoraXe - +
+
+ +
+
+ +
+
## Templateparameter `storaxe` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx index 664267d1cb..516608234e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Alpha ESS Storion SMILE - +
+
+ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder App Zeiten für das Netzladen definiert werden. (Einstellungen->Funktionseinstellungen->Netzladen/Entladen) Hier sollte ein durchgehender Zeitraum (z.B: Ladezeit 1 00:00-23:00, Ladezeit 2 23:00-00:00) eingetragen werden. Den Schalter "Netzladen" aber deaktivieren. Die eigentliche Steuerung erfolgt über evcc. Der Entladestopp wird über eine geplante Netzladung mit einem Ziel-SoC von 10% realisiert. Alternativ können die Zeiten auch über Modbus konfiguriert werden. Dafür die Register `2134,2142,2135,2136,2144,2137,2175` auf die Werte `0,0,23,0,23,0,0,0` setzen. @@ -43,32 +46,7 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder modbus: tcpip id: 85 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -120,8 +98,6 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -180,12 +156,23 @@ Um die aktive Ladesteuerung zu nutzen muss einmalig über das Webinterface oder +
+
+ +
+
## Templateparameter `alpha-ess-smile` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx index 1b5b4f5624..3a8582919b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ampere Ampere.StoragePro - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -93,32 +71,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -177,12 +130,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `saj-h2` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | Standard: `2` | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx index 41da27a8d8..0c9df6561d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Anker Micro inverter - +
+
+ +
+
+ +
+
## Templateparameter `deye-mi` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx index 7a84f287e6..77a8ae29c1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # APsystems EZ1 - +
+
+ +
+
+ +
+
## Templateparameter `apsystems-ez1` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx index 907cf00f93..afd89e8a16 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # AVM FritzDECT - +
+
+ @@ -42,6 +45,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `fritzdect` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx index 1b3812cebf..30cd69fd87 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Axitec AXIhycon 12-15H - +
+
+ @@ -118,12 +121,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solis-hybrid-s` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx index 6760c68ae1..1fee7376a3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bernecker Engineering MPM3PM - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `mpm3pm` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx index 5e3d5482ba..5814b49dbc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BGEtech DS100 - +
+
+ @@ -128,10 +131,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `bge_tech_ds100` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx index f750a26124..3398cc6fae 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BGEtech WS100 - +
+
+ @@ -128,10 +131,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `bge_tech_ws100` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx index 6b7d70e416..f650baa3f9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bosch BPT-S 5 Hybrid - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `bosch-bpt` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx index b275c69de4..a1aa34fb2b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Bosswerk Micro inverter - +
+
+ +
+
+ +
+
## Templateparameter `deye-mi` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx index 5a648dd9ce..8d7ee5b3aa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM110/111/112 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt1xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx index 0be77cfd07..565af3a34a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM24 - +
+
+ EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. @@ -63,10 +66,21 @@ EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschl +
+
+ +
+
## Templateparameter `cg-em24` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx index 97f565f87e..29c1635fae 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM24_E1 - +
+
+ EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) @@ -50,10 +53,21 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde +
+
+ +
+
## Templateparameter `cg-em24_e1` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx index 0e70cf17fc..231561dd2b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM330/EM340 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt3xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx index 8f9a7dacde..3801e1399f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi EM530/EM540 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt3xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx index 16cc3f033e..7af05774cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi ET112 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt1xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx index ae737b6440..b514d8e6da 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Carlo Gavazzi ET330/ET340 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt3xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx index 727412dce4..d3895df9c6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # cFos PowerBrain Meter - +
+
+ +
+
+ +
+
## Templateparameter `cfos` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx index 87ea7e4c86..fd2ac6c12b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Demobatterie - +
+
+ Zu Demonstrationszwecken. Hausbatterie mit festen Werten. @@ -36,6 +39,17 @@ Zu Demonstrationszwecken. Hausbatterie mit festen Werten. currentL1: # L1 Stromstärke (A), optional currentL2: # L2 Stromstärke (A), optional currentL3: # L3 Stromstärke (A), optional`} /> +
+
+ +
+
## Templateparameter `demo-battery` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx index 7b2101396a..2db0010ff6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Demozähler - +
+
+ Zu Demonstrationszwecken. Zähler mit festen Werten. @@ -95,6 +98,17 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. +
+
+ +
+
## Templateparameter `demo-meter` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx index 18acec57a1..ddc0c73f62 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye 3p hybrid inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `deye-hybrid-3p` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx index 3ac8c2b567..92bf506f97 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye hp3 hybrid inverter - +
+
+ @@ -64,9 +67,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -119,9 +120,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -175,7 +174,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -183,13 +182,24 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `deye-hybrid-hp3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| `storageunit` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Nummer des Batteriespeichers
`storageunit` | | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx index 6df694d6ed..3e54052ee5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye Micro inverter - +
+
+ +
+
+ +
+
## Templateparameter `deye-mi` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx index 1f02cbf912..f6caa324fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye Storage (hybrid) inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `deye-storage` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx index a7f6523687..2863f6f380 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Deye String inverter - +
+
+ +
+
+ +
+
## Templateparameter `deye-string` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx index 371519b021..379ecd5a57 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Discovergy - +
+
+ @@ -24,7 +27,7 @@ import TabItem from '@theme/TabItem'; usage: grid user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Zählernummer`} /> @@ -36,10 +39,21 @@ import TabItem from '@theme/TabItem'; usage: pv user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Zählernummer`} /> +
+
+ +
+
## Templateparameter `discovergy` @@ -47,5 +61,5 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | -| `meter` | | Beispiel: `1ESY1161229886` | ja | +| Zählernummer
`meter` | | Beispiel: `1ESY1161229886` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx index 6ab03c1cdc..754caff198 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DSMR - +
+
+ +
+
+ +
+
## Templateparameter `dsmr` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx index 8a84b58ac3..3a31bc6b7f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DZG DVH4013 - +
+
+ +
+
+ +
+
## Templateparameter `dzg` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx index 3638b6f4ba..bb056ad8c1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # E3/DC - +
+
+ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key (=RSCP-Passwort) muss im Hauskraftwerk unter Personalisieren/Benutzerprofil angelegt werden. Die IP-Adressen von evcc und des Hauskraftwerks müssen sich im selben Subnetz befinden. @@ -31,7 +34,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_grid type: template template: e3dc-rscp @@ -40,7 +43,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional)`} /> @@ -55,7 +58,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_pv type: template template: e3dc-rscp @@ -64,7 +67,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -80,7 +83,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_battery type: template template: e3dc-rscp @@ -89,12 +92,23 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `e3dc-rscp` @@ -104,7 +118,7 @@ Benutzername und Passwort sind identisch zum Web-Portal bzw. My E3/DC App. Key ( | Port
`port` | | Standard: `5033` | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | -| `key` | | | ja | +| RSCP-Password
`key` | | | ja | | Entladelimit in W
`dischargelimit` | Limitiert die Entladeleistung im 'Halten' Batteriemodus | | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx index 09c27b44b2..b3191afc61 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM120-Modbus - +
+
+ @@ -82,10 +85,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron-sdm120` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx index 37cd676367..14b5a7ecd9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM220/230 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron-sdm220_230` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx index d146a5e6cc..577b3b6b01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM630-Modbus - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx index 9345728bab..75d90bcab8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM72D-M - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron-sdm72` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx index ad958e9660..6a07411c9c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Eastron SDM72DM-V2 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx index c1a56d7a13..68344ef039 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Enphase IQ Envoy - +
+
+ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vom Typ "AC Battery" unterstützt. @@ -26,13 +29,13 @@ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vo template: enphase usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_grid type: template template: enphase usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -44,13 +47,13 @@ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vo template: enphase usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_pv type: template template: enphase usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -62,25 +65,36 @@ Als Batteriespeicher werden seitens der Enphase-API derzeit nur die Batterien vo template: enphase usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_battery type: template template: enphase usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) capacity: 50 # Akkukapazität (kWh), optional cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +
+
+ +
+
## Templateparameter `enphase` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| `token` | Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication | | nein | +| Token
`token` | Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx index 214211d2db..f8b5fd6b49 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ESPHome DLMS Meter Austria - +
+
+ Benötigt ein ESPHome Gerät mit der `dlms_meter` Komponente (z.B. von `github://SimonFischer04/esphome@dlms-meter`), konfiguriert für österreichische DLMS-Zähler. @@ -30,6 +33,17 @@ konfiguriert für österreichische DLMS-Zähler. usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname timeout: 10s # Zeitüberschreitung, optional`} /> +
+
+ +
+
## Templateparameter `esphome-dlms-austria` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx index ad6cac2aec..974de29a34 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ESPHome DSMR - +
+
+ +
+
+ +
+
## Templateparameter `slimmelezer` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx index 3dac12461a..9481afbb8f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FENECON - +
+
+ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. @@ -65,12 +68,23 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) + battery: ess0 # Steuerbare Batterie Komponente, optional + watchdog: 60s # Watchdog, abgestimmt auf das API-Timeout (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `openems` @@ -78,8 +92,8 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | Standard: `user` | nein | -| `battery` | steuerbare Batterie Komponente | Beispiel: `ess0` | nein | -| `watchdog` | abgestimmt auf das API-Timeout | Standard: `60s` | nein | +| Steuerbare Batterie Komponente
`battery` | | Beispiel: `ess0` | nein | +| Watchdog
`watchdog` | abgestimmt auf das API-Timeout | Standard: `60s` | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx index dc2718ea03..479707b33a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FoxESS H1 Series Hybrid Inverter - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `fox-ess-h1` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx index 5582d47d30..836600ac4d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FoxESS H3 Series Hybrid Inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `fox-ess-h3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx index e93dd23f7e..11b7475239 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # FoxESS H3-Smart Series Hybrid Inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `fox-ess-h3-smart` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx index 2c1d672f9b..b822a14b50 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Ohmpilot - +
+
+ +
+
+ +
+
## Templateparameter `fronius-ohmpilot` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx index 3b98dcda71..ea56f6d8e5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Primo GEN24 Plus - +
+
+ @@ -30,7 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> + id: 200 # ID, Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> @@ -71,6 +74,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `fronius-gen24` @@ -78,7 +92,7 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `502` | nein | -| `id` | Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). | Standard: `200` | nein | +| ID
`id` | Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). | Standard: `200` | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx index 5beeb8c359..b0c7b9dcda 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Smartmeter (über Wechselrichter) - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sunspec-meter` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx index b24d0c4857..8b3e772d82 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Solar API V1 - +
+
+ Solar API sollte nur als Fallback genutzt werden. Die Integration über Modbus ist bevorzugt. @@ -39,7 +42,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -59,7 +62,7 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -80,10 +83,21 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) capacity: 50 # Akkukapazität (kWh), optional - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> +
+
+ +
+
## Templateparameter `fronius-solarapi-v1` @@ -93,5 +107,5 @@ Benutzername und Passwort werden nur für die aktive Batteriesteuerung benötigt | Benutzername (für aktive Batteriesteuerung)
`user` | bspw. E-Mail Adresse, User Id, etc. | Standard: `customer` | nein | | Passwort (für aktive Batteriesteuerung)
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| Firmware Versionen ab 1.36.5-1 erfordern /api/config.
`batteryconfiguri` | | Standard: `/config`
Auswahl: `/config`, `/api/config` | nein | +| Batteriekonfigurations-URI
`batteryconfiguri` | Firmware Versionen ab 1.36.5-1 erfordern /api/config. | Standard: `/config`
Auswahl: `/config`, `/api/config` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx index 1e414de808..bf5444b5de 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fronius Symo GEN24 Plus - +
+
+ @@ -30,7 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> + id: 200 # ID, Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional)`} /> @@ -71,6 +74,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `fronius-gen24` @@ -78,7 +92,7 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `502` | nein | -| `id` | Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). | Standard: `200` | nein | +| ID
`id` | Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). | Standard: `200` | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx index fa02ac36c7..699debbe14 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ginlong Solis Hybrid Inverter (RHI series) - +
+
+ @@ -118,12 +121,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solis-hybrid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx index 87d282643e..df66b18ac8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ginlong Solis Hybrid Inverter (S Series) - +
+
+ @@ -118,12 +121,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solis-hybrid-s` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx index fbe8d5dbc9..6e881bc7fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ginlong Solis Inverter - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solis` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx index b8c81bd86f..fd0027ab47 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # go-e Controller - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `go-e-controller` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx index 01b0b52d83..52031f7205 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # GoodWe ET/EH/BH/BT Hybrid Inverter - +
+
+ @@ -41,7 +44,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} /> + battery: 1 # Batteriespeichernummer, [1, 2] (optional)`} /> @@ -70,7 +73,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Batteriespeichernummer, [1, 2] (optional)`} advanced={`meters: - name: my_pv type: template template: goodwe-hybrid @@ -94,7 +97,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -124,7 +127,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Batteriespeichernummer, [1, 2] (optional)`} advanced={`meters: - name: my_battery type: template template: goodwe-hybrid @@ -148,18 +151,29 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `goodwe-hybrid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip`, `udp` | nein | -| `battery` | | Standard: `1`
Auswahl: `1`, `2` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip`, `udp` | nein | +| Batteriespeichernummer
`battery` | | Standard: `1`
Auswahl: `1`, `2` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx index bde8abfe0b..c189421338 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # GoodWe GoodWe over Wifi - +
+
+ @@ -46,6 +49,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `goodwe-wifi` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx index e6c865cef4..263e7ee931 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # GoodWe SDT/DT Inverter - +
+
+ +
+
+ +
+
## Templateparameter `goodwe-dt` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx index e9a917a812..edb469666f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Growatt Hybrid Inverter - +
+
+ Um die aktive Ladesteuerung nutzen zu können ist eine einmalige manuelle Einrichtung notwendig. Es müssen die Modbusregister `1100, 1101, 1102` gleichzeitig (via "write multiple", FC 16) auf die Werte `0, 5947, 0` gesetzt werden. @@ -154,12 +157,23 @@ Die aktive Ladesteuerung nutzt den ersten Zeitslot für den "Battery first" modu +
+
+ +
+
## Templateparameter `growatt-hybrid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx index 50b6222b38..169e74eca9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Growatt TL-X(H) Hybrid Inverter - +
+
+ @@ -148,12 +151,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `growatt-hybrid-tlxh` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx index 1e3dd33706..32d17e045a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Homematic IP - +
+
+ @@ -26,7 +29,7 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: - name: my_grid type: template template: homematic @@ -35,8 +38,8 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> @@ -50,7 +53,7 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: - name: my_pv type: template template: homematic @@ -59,8 +62,8 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> @@ -74,7 +77,7 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt.`} advanced={`meters: - name: my_charger type: template template: homematic @@ -83,11 +86,22 @@ import TabItem from '@theme/TabItem'; device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional)`} /> +
+
+ +
+
## Templateparameter `homematic` @@ -97,6 +111,6 @@ import TabItem from '@theme/TabItem'; | Geräteadresse/Seriennummer
`device` | Homematic Geräte Id, wie im CCU Webfrontend angezeigt. | Beispiel: `0001EE89AAD848` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1)
`meterchannel` | Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. | Standard: `6` | ja | -| XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h)
`cache` | Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. | Standard: `1s`
Beispiel: `5m` | nein | +| Kanalnummer des Power- oder Netz-Meters
`meterchannel` | Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. | Standard: `6`
Beispiel: `HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1` | ja | +| XML-RPC API Cache Zeitraum
`cache` | Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. | Standard: `1s`
Beispiel: `5m` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx index 76ea382498..650c378b0d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # HomeWizard kWh Meter - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `homewizard-kwh` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx index 66dc3f860c..92198ee56a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # HomeWizard Wi-Fi P1 Meter - +
+
+ +
+
+ +
+
## Templateparameter `homewizard` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx index feb94c6cd1..98f1298d61 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hoymiles HM & HMS Series (via AhoyDTU) - +
+
+ Inverter #[ID], optional`} /> + id: 0 # Wechselrichter ID, Falls mehrere vorhanden. Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID] (optional)`} /> +
+
+ +
+
## Templateparameter `hoymiles-ahoydtu` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #\[ID\]
`id` | | | nein | +| Wechselrichter ID
`id` | Falls mehrere vorhanden. Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #\[ID\] | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx index b542461b85..16a56ee9dd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hoymiles HM & HMS Series (via OpenDTU) - +
+
+ +
+
+ +
+
## Templateparameter `hoymiles-opendtu` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx index 50f58ffee8..9a3e6b570b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei EMMA - +
+
+ @@ -72,11 +75,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `huawei-emma` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx index a44c2adab1..2a50a2da19 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SmartLogger - +
+
+ @@ -40,7 +43,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -68,7 +71,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -97,19 +100,30 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `huawei-smartlogger` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | nein | -| `storageunit` | | Standard: `1` | nein | +| Nummer des Batteriespeichers
`storageunit` | | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx index 52df54cff8..b63111c67c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SUN2000 (SDongle) - +
+
+ Erfordert "Modbus/TCP". Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 @@ -30,11 +33,22 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional`} /> +
+
+ +
+
## Templateparameter `huawei-dongle` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx index 9a000c0e82..73b494d53d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Huawei SUN2000 - +
+
+ Grid und Batterie erfordern den PowerSensor. "Modbus/TCP" erfordert Freischaltung via "Errichterzugang" in den Kommunikationseinstellungen des Wechselrichters. @@ -71,7 +74,7 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -125,7 +128,7 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -180,21 +183,32 @@ Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/66725067715 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxchargepower: 10000 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) capacity: 50 # Akkukapazität (kWh), optional forceaccharging: false # Wechselrichterkaskade, AC-Laden bleibt aktiv zum Laden des Speichers aus anderen AC Quellen für Wechselrichterkaskaden. Verhindert Stand-by. (optional)`} /> +
+
+ +
+
## Templateparameter `huawei-sun2000` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | nein | -| `storageunit` | | Standard: `1` | nein | +| Nummer des Batteriespeichers
`storageunit` | | Standard: `1` | nein | | Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `10000`
Einheit: W | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx index 4a0b9f2147..f51809b626 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IAMMETER WEM3080 - +
+
+ Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). Siehe https://www.iammeter.com/newsshow/net-energy-metering @@ -50,6 +53,17 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering +
+
+ +
+
## Templateparameter `iammeter` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx index 76189261f8..30e34656a0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IAMMETER WEM3080T/WEM3046T/WEM3050T - +
+
+ Die 3-phasigen Zähler (WEM3080T/WEM3046T/WEM3050T) benötigen die Aktivierung des Net Metering Mode (NEM) (=phasensaldierende Zählung). Siehe https://www.iammeter.com/newsshow/net-energy-metering @@ -50,6 +53,17 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering +
+
+ +
+
## Templateparameter `iammeter` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx index 8982398efc..f3e8c31ca3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IGEN Tech Solarman Logger - +
+
+ +
+
+ +
+
## Templateparameter `solarman` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx index 29b38145b6..f0a833c903 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # inepro PRO380-MOD - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `inepro` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx index 3ee0e284ad..e15b20accf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # IOmeter - +
+
+ +
+
+ +
+
## Templateparameter `iometer` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx index dd105c37af..e293e3d9ea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Janitza B series - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `janitza` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx index 599fb7cf00..6fd8a6e4b3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Janitza UMG series - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `janitza` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx index 5bb16d766f..67859de438 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # KEBA KeContact E10 - +
+
+ +
+
+ +
+
## Templateparameter `keba-kecontact` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx index ff2b6b7443..a82921d16e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Energy Meter C (KEM-C) - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt3xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx index 2e9698b572..f26440158b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Energy Meter P (KEM-P) - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx index 426a8f0197..2954511f44 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko BA - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `kostal-piko-pv` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx index 9edddb84e0..2b84242e6b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko Hybrid - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `kostal-piko-hybrid` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx index 69a5ee26cc..8fe92836ec 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko (legacy) - +
+
+ +
+
+ +
+
## Templateparameter `kostal-piko-legacy` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx index d2e8e0bec2..8836d7572e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko MP Plus - +
+
+ +
+
+ +
+
## Templateparameter `kostal-piko-mp-plus` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx index 8bf2671f6a..2b23da4c03 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Piko - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `kostal-piko-pv` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx index 907e19e0f1..3847430f6a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Plenticore Hybrid, inkl. Netzladung der Hausbatterie - +
+
+ Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. **_Ist grundsätzlich anwendbar für verschiedene Wechselrichter Generationen (G1/G2/G3)._** **Das Netzladen der Batterie steht mit dieser Vorlage zur Verfügung, ist aktuell jedoch inkompatibel mit wenigen älteren Wechselrichtern - _sorgfältig testen_!** @@ -45,7 +48,7 @@ _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ port: 1502 # Port endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -74,19 +77,30 @@ _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) capacity: 50 # Akkukapazität (kWh), optional maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `kostal-plenticore-gen2` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Byte-Reihenfolge (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx index 6dec8a6975..f0592ad055 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Plenticore Hybrid - +
+
+ Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive Batteriesteuerung muss die Funktion externe Batteriesteuerung über Modbus mit dem Handwerkerzugang aktiviert sein. **Das Netzladen der Batterie steht nicht zur Verfügung!** _siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ @@ -44,9 +47,7 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive B port: 1502 # Port endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -76,20 +77,31 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! Für die aktive B capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `kostal-plenticore` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Byte-Reihenfolge (Little/Big)
`endianness` | | Standard: `little`
Auswahl: `little`, `big` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx index 188f64d939..6e17b7b2de 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Smart Energy Meter (über den Wechselrichter) - +
+
+ Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorposition 1 (Haushaltsverbrauch) wird nicht unterstützt. @@ -28,10 +31,21 @@ Der Zähler muss in Sensorposition 2 (Netzanschluss) installiert sein. Sensorpos id: 71 host: 192.0.2.2 # Hostname port: 1502 # Port`} /> +
+
+ +
+
## Templateparameter `kostal-ksem-inverter` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx index 1760873255..1a4610c975 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kostal Smart Energy Meter - +
+
+ +
+
+ +
+
## Templateparameter `kostal-ksem` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx index 8da937727a..dd7787ec9e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LG ESS Home 15 - +
+
+ @@ -30,9 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -50,9 +51,7 @@ import TabItem from '@theme/TabItem'; usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -70,13 +69,24 @@ import TabItem from '@theme/TabItem'; usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> +
+
+ +
+
## Templateparameter `lg-ess-home-15` @@ -84,7 +94,7 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Passwort
`password` | Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. | | nein | -| `registration` | Registriernummer des LG ESS HOME Wechselrichters. | Beispiel: `DE200...` | nein | +| Registriernummer
`registration` | Nummer des LG ESS HOME Wechselrichters. | Beispiel: `DE200...` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx index b26e625dc5..7e3ad9344d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # LG ESS Home 8/10 - +
+
+ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich 10.05.7433 / R2155 benötigt @@ -33,9 +36,7 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -53,9 +54,7 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional)`} /> @@ -73,13 +72,24 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> +
+
+ +
+
## Templateparameter `lg-ess-home-8-10` @@ -87,7 +97,7 @@ Um die Batteriesteuerung zu nutzen, wird eine Firmwareversionen größer gleich |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Passwort
`password` | Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. | | nein | -| `registration` | Registriernummer des LG ESS HOME Wechselrichters. | Beispiel: `DE200...` | nein | +| Registriernummer
`registration` | Nummer des LG ESS HOME Wechselrichters. | Beispiel: `DE200...` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx index f18516d203..b57d37453c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Loxone Miniserver - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `loxone` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx index d3bde2e4c5..0a07a905ef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # M-TEC Energy Butler GEN2 - +
+
+ @@ -82,10 +85,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `mtec-eb-gen2` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx index 7312de16be..387ef71493 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # M-TEC Energy Butler GEN3 - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `mtec-eb-gen3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx index 5f8d703592..96ed33ef27 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Marstek Venus Battery Storage - +
+
+ + maxchargepower: 2500 # Maximale Ladeleistung (W), 2500W ist das Maximum für Venus. (optional) + work_mode_normal: 1 # Work mode für Normal-Modus, 0=manuell, 1=Eigenverbrauch, 2=AI-Optimierung. (optional)`} /> +
+
+ +
+
## Templateparameter `marstek-venus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | Venus-E 5.12 kWh, Venus-C 2.56 kWh | Standard: `5.12`
Beispiel: `50`
Einheit: kWh | nein | -| Venus kann nur bis 11% entladen werden.
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `11`
Beispiel: `25`
Einheit: % | nein | +| Minimaler Ladestand
`minsoc` | Venus kann nur bis 11% entladen werden. | Standard: `11`
Beispiel: `11`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `100`
Beispiel: `95`
Einheit: % | nein | -| Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus.
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `2500`
Einheit: W | nein | -| Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung.
`work_mode_normal` | | Standard: `1` | nein | +| Maximale Ladeleistung
`maxchargepower` | 2500W ist das Maximum für Venus. | Standard: `2500`
Einheit: W | nein | +| Work mode für Normal-Modus
`work_mode_normal` | 0=manuell, 1=Eigenverbrauch, 2=AI-Optimierung. | Standard: `1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx index 448856a088..7a555ee2f1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # mhendriks P1 dongle - +
+
+ +
+
+ +
+
## Templateparameter `slimmelezer` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx index 5914665c8d..d004b2caac 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC ELWA 2 - +
+
+ +
+
+ +
+
## Templateparameter `ac-elwa-2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx index b49367d38e..7c106663d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC ELWA-E - +
+
+ +
+
+ +
+
## Templateparameter `ac-elwa-e` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx index ea142ec908..55b0dc01f3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV AC•THOR - +
+
+ +
+
+ +
+
## Templateparameter `thor` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx index c261c4829d..6f52dba1a3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # my-PV WiFi Meter - +
+
+ +
+
+ +
+
## Templateparameter `mypv-wifi-meter` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx index 6bab29de9e..bdf273c975 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # myStrom Switch - +
+
+ @@ -36,6 +39,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `mystrom` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx index 21fbba4ffe..1623633d39 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # OpenEMS - +
+
+ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteriesteuerung erforderlich. @@ -65,12 +68,23 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) + battery: ess0 # Steuerbare Batterie Komponente, optional + watchdog: 60s # Watchdog, abgestimmt auf das API-Timeout (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `openems` @@ -78,8 +92,8 @@ Für FEMS FENECON-Systeme ist eine kommerzielle Lizenz für die aktive Batteries |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | Standard: `user` | nein | -| `battery` | steuerbare Batterie Komponente | Beispiel: `ess0` | nein | -| `watchdog` | abgestimmt auf das API-Timeout | Standard: `60s` | nein | +| Steuerbare Batterie Komponente
`battery` | | Beispiel: `ess0` | nein | +| Watchdog
`watchdog` | abgestimmt auf das API-Timeout | Standard: `60s` | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx index ab7df5806f..b386556b57 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ORNO OR-WE-516 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `orno` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx index 6e84b66fb7..19aedcba2f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ORNO OR-WE-517 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `orno` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx index 0fb07dba23..9bed8a0ef0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # P1Monitor P1 Monitor - +
+
+ +
+
+ +
+
## Templateparameter `p1monitor` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx index 9281593daa..539c15339c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Plexlog - +
+
+ Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `interval` nicht kleiner als 30 Sekunden gewählt werden. @@ -75,11 +78,22 @@ Die Werte werden ca. alle 15 Sekunden aktualisiert, deshalb sollte das evcc `int +
+
+ +
+
## Templateparameter `plexlog` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx index 07c6b92c4c..44f01f04e4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Powerdog - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `powerdog` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx index 8dfa05b19a..0ac7fce06f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Powerfox Poweropti - +
+
+ @@ -30,7 +33,7 @@ import TabItem from '@theme/TabItem'; usage: grid user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti`} /> + id: main # ID, Id im Falle mehrerer PowerOpti`} /> @@ -48,10 +51,21 @@ import TabItem from '@theme/TabItem'; usage: pv user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti`} /> + id: main # ID, Id im Falle mehrerer PowerOpti`} /> +
+
+ +
+
## Templateparameter `powerfox-poweropti` @@ -59,5 +73,5 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | -| `id` | Id im Falle mehrerer PowerOpti | Standard: `main` | ja | +| ID
`id` | Id im Falle mehrerer PowerOpti | Standard: `main` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx index fd6d9d5cc3..7791d6ac4a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Qcells Hybrid-Wechselrichter (Cloud) - +
+
+ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. @@ -61,6 +64,17 @@ Der Qcells Hybrid-Wechselrichter muss in der QcellsCloud angemeldet sein. +
+
+ +
+
## Templateparameter `qcells-hybrid-cloud` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx index 218be9eef9..2ac4334f61 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Qcells Q.HOME ESS HYB-G3 - +
+
+ @@ -41,7 +44,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -65,8 +68,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -95,7 +98,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -119,8 +122,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -150,7 +153,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -174,21 +177,32 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional)`} /> +
+
+ +
+
## Templateparameter `solax` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| Der Wechselrichter hat einen dritten PV-Eingang (MPPT3)
`mppt3` | | | nein | -| `storageunit` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Dritter PV-Eingang
`mppt3` | Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) | | nein | +| Nummer des Batteriespeichers
`storageunit` | | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx index ebad8223e1..28a9000efa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # RCT Power - +
+
+ @@ -28,10 +31,7 @@ import TabItem from '@theme/TabItem'; template: rct-power usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional)`} /> + cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> @@ -47,8 +47,6 @@ import TabItem from '@theme/TabItem'; template: rct-power usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional)`} /> @@ -70,11 +68,21 @@ import TabItem from '@theme/TabItem'; minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional)`} /> + maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional)`} /> +
+
+ +
+
## Templateparameter `rct-power` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx index 6c5db4b11b..8d9cda4b09 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Saia-Burgess Controls (SBC) ALE3 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sbc-axx3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx index e13ce243f8..e6fd2e9ebe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Saia-Burgess Controls (SBC) AWD3 - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sbc-axx3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx index 38b02e8d0d..f1b6f10842 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAJ H1 Series Hybrid Solar Inverter - +
+
+ @@ -76,12 +79,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `saj-h1` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Standard: `5s`
Beispiel: `10s` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx index 6be395639f..6df6750909 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAJ H2 Series Hybrid Solar Inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -93,32 +71,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -177,12 +130,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `saj-h2` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | Standard: `2` | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx index d0589dcfbe..098bf3c1a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAJ R5 Series Solar Inverter - +
+
+ +
+
+ +
+
## Templateparameter `saj-r5` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx index 515c5685d2..3f39fed86f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SAX Homespeicher - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sax` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx index dc70c798b9..94c68cd6f3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Schneider Electric iEM3xxx Modbus - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `schneider-iem3000` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx index 9d70c5a93a..98b8a002f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SENEC .Home - +
+
+ @@ -23,7 +26,7 @@ import TabItem from '@theme/TabItem'; template: senec-home usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -34,7 +37,7 @@ import TabItem from '@theme/TabItem'; template: senec-home usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -45,23 +48,34 @@ import TabItem from '@theme/TabItem'; template: senec-home usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional)`} advanced={`meters: + schema: https # Schema, [https, http] (optional)`} advanced={`meters: - name: my_battery type: template template: senec-home usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) capacity: 50 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `senec-home` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | -| `schema` | | Standard: `https`
Auswahl: `https`, `http` | nein | +| Schema
`schema` | | Standard: `https`
Auswahl: `https`, `http` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx index 4e958de9ac..e913fc350e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Senergy SE 4/5/6KTL-S1/G2 Inverter - +
+
+ +
+
+ +
+
## Templateparameter `senergy` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx index 1f4e226777..ac11591742 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 1PM mini - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx index 0f5a7b8846..c349c94fc9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 1PM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx index cf9a37cbab..3fb158cead 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly 3EM - +
+
+ @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `shelly-3em` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx index 601ff88a20..68109fd546 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly EM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx index c865363933..13fa8a0be1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Plug S - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx index d53789a723..1e7c5e1992 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly PM mini - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx index bfb482e21b..a24c116526 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 1PM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx index 98e5a246e9..1ac7b1d9d2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 3 EM - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `shelly-pro-3em` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx index 83c5e90985..de59ff9569 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro 3EM (monophase mode) - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx index c292c58fc5..0ebefe75f0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Shelly Pro EM - +
+
+ @@ -25,7 +28,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -38,7 +41,7 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> @@ -51,10 +54,21 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional`} /> + channel: 0 # Kanal, optional`} /> +
+
+ +
+
## Templateparameter `shelly-1pm` @@ -63,5 +77,5 @@ import TabItem from '@theme/TabItem'; | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | nein | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | nein | -| `channel` | | | nein | +| Kanal
`channel` | | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx index ef2e6cc609..d7f613fe93 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens 7KT1665 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `siemens-7kt1665` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx index d4b1e4d36c..a1f2454b77 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens Junelight Smart Battery - +
+
+ Die Batterie muss mit dem Installer Zugang auf Loxone gestellt werden. @@ -75,11 +78,22 @@ Die Batterie muss mit dem Installer Zugang auf Loxone gestellt werden. +
+
+ +
+
## Templateparameter `siemens-junelight` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx index dd9816c083..9718062c3a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Siemens PAC 2200 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `siemens-pac2200` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx index 138a3901f5..6540c016b3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC - +
+
+ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen App aktivieren bevor diese Konfiguration funktional ist. Diese Option ist in der mySigen App für Kunden nicht verfügbar. @@ -27,7 +30,7 @@ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen A usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -39,7 +42,7 @@ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen A usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -51,18 +54,29 @@ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen A usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional`} advanced={`meters: + id: 1 # ID, optional`} advanced={`meters: - name: my_battery type: template template: sigenergy usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional capacity: 50 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `sigenergy` @@ -70,6 +84,6 @@ Der Elektriker muss die Funktion Modbus via TCP/IP in seiner Version der Sigen A |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `502` | nein | -| `id` | | Standard: `1` | nein | +| ID
`id` | | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx index 689611e411..7266d6f5c9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Data Manager - +
+
+ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikation" der Schalter "Modbus Server aktivieren" eingeschaltet sein. @@ -75,11 +78,22 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio +
+
+ +
+
## Templateparameter `sma-data-manager` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx index 06e5c26c2f..2a0fc72cfa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Energy Meter - +
+
+ @@ -48,6 +51,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sma-energy-meter` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx index 17f69efce1..7119d57682 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Wechselrichter (Speedwire) - +
+
+ @@ -45,6 +48,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sma-inverter-speedwire` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx index 407c7c1033..fe22948e94 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Smart Energy Hybrid-Wechselrichter - +
+
+ @@ -66,18 +69,29 @@ import TabItem from '@theme/TabItem'; port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `sma-hybrid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx index 7579520b6e..65a8f6a2b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `sma-sbs-15-25-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx index 6142465087..b9668c6333 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `sma-sbs-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx index 872a6bc832..dd17a69d4c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Home Manager 2.0 - +
+
+ +
+
+ +
+
## Templateparameter `sma-home-manager` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx index d16d3ed958..0db187ee6b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Sunny Island (Modbus) - +
+
+ + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `sma-si-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `4200`
Einheit: W | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx index 650d2bb8e6..b1c6ff4fb6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA WebBox - +
+
+ +
+
+ +
+
## Templateparameter `sma-webbox` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx index 83fe9ca292..f0e1f1f8d2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SMA Wechselrichter (Modbus) - +
+
+ +
+
+ +
+
## Templateparameter `sma-inverter-modbus` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | Der ModbusTCP Server muss aktiviert sein. | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx index fe1f9905b3..75f07e247d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Box - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -49,6 +52,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx index 1ea191d0f6..32a19fb63d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Light (EM2 firmware) - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox-em2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx index dab21187f8..44771b7de0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro 2 - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox-em2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx index a8586ef35d..2c85ff06c4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro Light 2 - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox-em2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx index 39fcb7537e..b7e045a785 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro Light - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox-em2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx index 0826070a21..4d8202e3a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Pro - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -67,6 +70,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox-em2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx index 577063b99c..8f456258d2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Reg extended - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -49,6 +52,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx index b9bd76498a..a3167a4330 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smartfox Reg - +
+
+ `aux` kann für die Leistung der Warmwasserbereitung verwendet werden. @@ -49,6 +52,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `smartfox` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx index b3ac87e4be..2a79fa1333 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar Hybrid Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sofarsolar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx index a3aea78fe6..60f5740b67 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar HYD 3…6K-EP - +
+
+ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. @@ -67,7 +70,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -119,7 +122,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -172,19 +175,30 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> +
+
+ +
+
## Templateparameter `sofarsolar-g3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | -| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Nummer des Batteriespeichers
`storageunit` | Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx index 5fa66ea3d3..03da65580d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar HYD 5…20K-3PH - +
+
+ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. @@ -67,7 +70,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -119,7 +122,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -172,19 +175,30 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> +
+
+ +
+
## Templateparameter `sofarsolar-g3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | -| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Nummer des Batteriespeichers
`storageunit` | Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx index f5fabc4a15..8d5481dc83 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sofarsolar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx index 8cab00a12d..c272554669 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar SOFAR 5…24KTL-G3 - +
+
+ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. @@ -67,7 +70,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -119,7 +122,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -172,19 +175,30 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> +
+
+ +
+
## Templateparameter `sofarsolar-g3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | -| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Nummer des Batteriespeichers
`storageunit` | Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx index 04b3bf8aac..57b0a23afc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SofarSolar SOFAR 80…136KTL - +
+
+ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus TCP über Port 8899 ist die einfachste Anbindung. Der LSW-3 WLAN Stick wird nicht unterstützt. Bei seriellem Anschluss via RS485 am COM Port ist eine wechselrichterseitige Terminierung notwendig. @@ -67,7 +70,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional)`} /> @@ -119,7 +122,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -172,19 +175,30 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional)`} /> +
+
+ +
+
## Templateparameter `sofarsolar-g3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | -| `storageunit` | Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Nummer des Batteriespeichers
`storageunit` | Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx index 025c1ca24f..0be7ee3d47 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solaranzeige Solaranzeige - +
+
+ @@ -62,6 +65,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solaranzeige` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx index 9f42a4b631..884bed6e7e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarEdge Hybrid Inverter - +
+
+ Nur ein System kann und darf zeitgleich eine Modbus TCP-Verbindung zum Wechselrichter haben! Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "Remote" stehen. @@ -70,7 +73,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R host: 192.0.2.2 # Hostname port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -125,7 +128,7 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -180,18 +183,29 @@ Für die optionale Batteriesteuerung muss StorageConf_CtrlMode (0xE004) auf 4 "R port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `solaredge-hybrid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx index 4e987cd500..7b5551d7c3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarEdge Wechselrichter - +
+
+ Nur ein System kann und darf auf den Wechselrichter zugreifen! @@ -77,11 +80,22 @@ Nur ein System kann und darf auf den Wechselrichter zugreifen! +
+
+ +
+
## Templateparameter `solaredge-inverter` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx index 7adf835db9..e38848d776 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarlog - +
+
+ Wir empfehlen dieses Gerät für den Netzbezug/Einspeisewerte nur zu verwenden, wenn kein anderes Gerät diese Daten liefert. Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall für die erwähnten Werte verwendet werden! @@ -42,6 +45,17 @@ Falls eine Hausbatterie angeschlossen ist sollte dieses Gerät auf keinen Fall f +
+
+ +
+
## Templateparameter `solarlog` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx index 588ef6e91d..ad36c2ddfa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarMax MAX.STORAGE / MAX.STORAGE Ultimate - +
+
+ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivity+" freigeschaltet werden. Verfügbar ab Software 3.4.4. Ohne Freischaltung bleibt die Funktion ohne Wirkung. Netzladung ist generell nicht verfügbar. @@ -41,7 +44,7 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -68,7 +71,7 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit host: 192.0.2.2 # Hostname port: 502 # Port maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -95,17 +98,28 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> +
+
+ +
+
## Templateparameter `solarmax-maxstorage` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | -| `watchdog` | | Standard: `60s` | nein | +| Watchdog
`watchdog` | | Standard: `60s` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx index 9925e6c81b..33789ab640 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarMax SolarMax SMT - +
+
+ +
+
+ +
+
## Templateparameter `solarmax-smt` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx index fa278807d1..4d809774f1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SolarMax SP Series Inverter - +
+
+ +
+
+ +
+
## Templateparameter `senergy` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx index 83c902c98f..f2700c4ae6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt EnergyManager Pro - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solarwatt` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx index 3bd165c6e8..a06b99ec28 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt EnergyManager - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solarwatt` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx index b7851ccb1f..aeb7a9b3ef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt Manager flex - +
+
+ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. @@ -55,6 +58,17 @@ Kombiniert Daten von allen verbundenen Solar-Wechselrichtern oder Batterien. +
+
+ +
+
## Templateparameter `solarwatt-flex` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx index d465eaf3c5..88b2e0460c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt MyReserve Matrix (LAN oder PowerGateway) - +
+
+ @@ -56,6 +59,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solarwatt-myreserve-matrix` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx index b754c95e7f..01b5f5090b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solarwatt MyReserve - +
+
+ @@ -52,6 +55,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `solarwatt` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx index d0cf64650f..e950c5d1a4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax Hybrid-Wechselrichter (Cloud) - +
+
+ Der Solax Hybrid-Wechselrichter muss in der SolaxCloud angemeldet sein. @@ -61,12 +64,23 @@ Der Solax Hybrid-Wechselrichter muss in der SolaxCloud angemeldet sein. +
+
+ +
+
## Templateparameter `solax-hybrid-cloud` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') | | ja | -| Seriennummer
`serial` | https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen | | ja | +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') | | ja | +| Seriennummer
`serial` | https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen | | ja | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx index eb1332ca1c..54b513e620 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax Hybrid X1/X3 G3/G4 - +
+
+ @@ -41,7 +44,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -65,8 +68,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional`} /> @@ -95,7 +98,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -119,8 +122,8 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -150,7 +153,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional`} advanced={`meters: + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -174,21 +177,32 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional)`} /> +
+
+ +
+
## Templateparameter `solax` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| Der Wechselrichter hat einen dritten PV-Eingang (MPPT3)
`mppt3` | | | nein | -| `storageunit` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Dritter PV-Eingang
`mppt3` | Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) | | nein | +| Nummer des Batteriespeichers
`storageunit` | | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx index b6818e123d..72c945039c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solax PV-Wechselrichter (Cloud) - +
+
+ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. @@ -26,11 +29,22 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. usage: pv tokenid: # SolaxCloud TokenID, https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von \`tokenID\` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') serial: # Seriennummer, https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen`} /> +
+
+ +
+
## Templateparameter `solax-inverter-cloud` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') | | ja | -| Seriennummer
`serial` | https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen | | ja | +| SolaxCloud TokenID
`tokenid` | https://www.solaxcloud.com/ -> Support -> Drittanbieter-Ökosystem (alte Website) oder Dienst -> API (neue Website), den Wert von `tokenID` hier in Anführungszeichen eintragen (Beispiel: '20241028488283838') | | ja | +| Seriennummer
`serial` | https://www.solaxcloud.com/ -> Gerät -> Wechselrichter (neue Website) oder Support (alte Website), Wert von Registrierungsnummer hier eintragen | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx index e15f993450..2129485e01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solinteng - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> +
+
+ +
+
## Templateparameter `wattsonic` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `delay` | | Standard: `100ms` | nein | +| Verzögerung
`delay` | | Standard: `100ms` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx index a8cb1b6c8d..8519710a02 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen comfort - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sonnenbatterie-eco56` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx index 3aaa3df3ac..1252c7f947 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen eco 5 - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sonnenbatterie-eco56` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx index cdf2d7dda0..2acfdcd0f8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen eco 6 - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sonnenbatterie-eco56` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx index 45bd8ad524..4dec02324e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen oem 6.5 - +
+
+ @@ -72,6 +75,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sonnenbatterie-eco56` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx index 8c84c7f77e..38fe4f92f8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sonnen sonnenBatterie - +
+
+ Für die aktive Batteriesteuerung muss über das Webinterface der sonnenBatterie (unter Software-Integration) das "JSON Write API" aktiviert und das dort generierte API-Token in der Batteriekonfiguration unter `token` eingetragen werden. Als Betriebsart der sonnenBatterie werden die beiden Modi "Eigenverbrauch" (Standard) und "Time-of-use" unterstützt. Der Modus kann über den Parameter `defaultmode` an die Konfiguration der sonnenBatterie angepasst werden. @@ -51,20 +54,31 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional)`} advanced={`meters: + token: # Token, API Token (benötigt für aktive Batteriesteuerung) (optional)`} advanced={`meters: - name: my_battery type: template template: sonnenbatterie usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional) + token: # Token, API Token (benötigt für aktive Batteriesteuerung) (optional) capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 3300 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) defaultmode: self-consumption # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. [self-consumption, time-of-use]`} /> +
+
+ +
+
## Templateparameter `sonnenbatterie` @@ -72,7 +86,7 @@ Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBat |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `8080` | nein | -| `token` | API Token (benötigt für aktive Batteriesteuerung) | | nein | +| Token
`token` | API Token (benötigt für aktive Batteriesteuerung) | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale Ladeleistung
`maxchargepower` | Für erzwungenes Laden des Speichers. | Standard: `3300`
Einheit: W | nein | | Standardmodus für die aktive Batteriesteuerung
`defaultmode` | Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. | Standard: `self-consumption`
Auswahl: `self-consumption`, `time-of-use` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx index 7af099bab7..1d8d0fe590 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # St-ems - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> +
+
+ +
+
## Templateparameter `wattsonic` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `delay` | | Standard: `100ms` | nein | +| Verzögerung
`delay` | | Standard: `100ms` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx index 834855417c..4edc1a1738 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Steca coolcept fleX - +
+
+ +
+
+ +
+
## Templateparameter `kostal-piko-mp-plus` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx index 5405e437db..2da6d64f2d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow SG Series Inverter - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sungrow-inverter` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx index c0a217f352..b1e7873e72 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sungrow SH Series Hybrid Inverter - +
+
+ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktueller Firmware. Ältere Versionen liefern nicht alle benötigten Daten (Leistung, Ladestand). @@ -157,12 +160,23 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu +
+
+ +
+
## Templateparameter `sungrow-hybrid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx index d0ade717b0..4a33b51bcd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Batterie (Model 124) - +
+
+ +
+
+ +
+
## Templateparameter `sunspec-inverter-control` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | | Maximale Ladeleistung
`maxchargerate` | Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. | Standard: `100`
Einheit: % | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx index 2f5275665e..a42af80181 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Batterie (Model 802) - +
+
+ +
+
+ +
+
## Templateparameter `sunspec-battery-control` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx index e4edb7b0e0..c13963e595 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Hybridwechselrichter - +
+
+ @@ -148,12 +151,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sunspec-hybrid` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx index 28a0118eae..b284817729 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Wechselrichter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sunspec-inverter` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip`, `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip`, `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx index 617a7db682..51f1623c71 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SunSpec Zähler - +
+
+ @@ -46,10 +49,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sunspec-meter` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx index 1f3c51b006..a4bed14d60 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk 3p hybrid inverter - +
+
+ @@ -40,32 +43,7 @@ import TabItem from '@theme/TabItem'; modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + port: 502 # Port`} /> @@ -117,8 +95,6 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -177,12 +153,23 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `deye-hybrid-3p` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx index 0064b68c9a..6f647ae705 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk hp3 hybrid inverter - +
+
+ @@ -64,9 +67,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -119,9 +120,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional`} /> @@ -175,7 +174,7 @@ import TabItem from '@theme/TabItem'; id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -183,13 +182,24 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `deye-hybrid-hp3` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | -| `storageunit` | | Standard: `1` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Nummer des Batteriespeichers
`storageunit` | | Standard: `1` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Standard: `20`
Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Standard: `95`
Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx index 0897fee320..20ad572719 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk Micro inverter - +
+
+ +
+
+ +
+
## Templateparameter `deye-mi` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx index 353815961b..d54785c283 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk Storage (hybrid) inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `deye-storage` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx index d39bedf162..0dd35c3c42 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunsynk String inverter - +
+
+ +
+
+ +
+
## Templateparameter `deye-string` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx index 3703c569fa..41eda964d5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Sunway - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> +
+
+ +
+
## Templateparameter `wattsonic` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `delay` | | Standard: `100ms` | nein | +| Verzögerung
`delay` | | Standard: `100ms` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx index 00540e6c47..840cf89753 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi - +
+
+ Um die Werte des Smartmeters für evcc korrekt auslesen zu können, muss das Lesekopf-Script so geändert werden, dass folgende JSON-Tags erzeugt werden: - **SML** als Gruppenname der ausgelesenen Parameter @@ -89,6 +92,17 @@ Ein entsprechendes Lesekopf-Script sieht wie folgt aus: +
+
+ +
+
## Templateparameter `tasmota-sml` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx index 5714ecfe43..ee0395df34 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota Tasmota (1 Phase + SML Meter) - +
+
+ @@ -68,6 +71,17 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `tasmota` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx index 53bb807793..27c8c52362 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tasmota dreiphasig - +
+
+ Kanäle 1,2,3 müssen verwendet werden. @@ -67,6 +70,17 @@ Kanäle 1,2,3 müssen verwendet werden. +
+
+ +
+
## Templateparameter `tasmota-3p` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx index 5a4b45aa90..45c3a0ce96 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla Powerwall - +
+
+ Um die optionale Entladesteuerung der Battery zu nutzen wird ein `refresh` Token für die Kommunikation mit der Tesla API benötigt. @@ -32,18 +35,8 @@ Folgende Apps ermöglichen das Erstellen des Tokens: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: - - name: my_grid - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} /> @@ -55,18 +48,8 @@ Folgende Apps ermöglichen das Erstellen des Tokens: usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: - - name: my_pv - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP-Adresse oder Hostname - password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} /> @@ -78,21 +61,32 @@ Folgende Apps ermöglichen das Erstellen des Tokens: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional)`} advanced={`meters: - name: my_battery type: template template: tesla-powerwall usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> +
+
+ +
+
## Templateparameter `tesla-powerwall` @@ -100,8 +94,8 @@ Folgende Apps ermöglichen das Erstellen des Tokens: |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Passwort
`password` | Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. | | ja | -| `refreshToken` | | | nein | -| `siteId` | optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung | | nein | +| Refresh token
`refreshToken` | | | nein | +| Site ID
`siteId` | optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung | | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | | Maximaler Ladestand
`maxsoc` | Oberes Limit beim Laden der Batterie aus dem Netz | Beispiel: `95`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx index d4519fd468..c10cb5dd3b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx @@ -9,23 +9,37 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tibber Pulse - +
+
+ + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional`} /> +
+
+ +
+
## Templateparameter `tibber-pulse` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | | Beispiel: `5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE` | ja | -| `homeid` | | Beispiel: `96a14971-525a-4420-aae9-e5aedaa129ff` | nein | +| Token
`token` | | Beispiel: `5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE` | ja | +| Home ID
`homeid` | | Beispiel: `96a14971-525a-4420-aae9-e5aedaa129ff` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx index 6780ebbc6a..88b554a20e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link H-Series Smart Plug - +
+
+ +
+
+ +
+
## Templateparameter `tplink` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx index 6e4862ceba..1c1ffcb6c8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TP-Link Tapo P-Series Smart Plug - +
+
+ +
+
+ +
+
## Templateparameter `tapo` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx index 84bd29f912..105bd75093 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TQ Energy Manager EM2xx/EM3xx - +
+
+ +
+
+ +
+
## Templateparameter `tq-em` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx index 5514b8ad45..1850eeadf9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TQ Energy Manager EM420 - +
+
+ Datenendpunkt (optional) token: ey... # Accesstoken, Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel)`} /> +
+
+ +
+
## Templateparameter `tq-em420` @@ -30,6 +44,6 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `80` | nein | -| API Gerätepfad
`device` | JSON-Schnittstelle -> Datenendpunkt | Standard: `local` | nein | -| Accesstoken
`token` | Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel) | Beispiel: `ey...` | ja | +| API Gerätepfad
`device` | JSON-Schnittstelle -> Datenendpunkt | Standard: `local` | nein | +| Accesstoken
`token` | Token des EM420 (Erstellen unter Profil -> Zugangsschlüssel) | Beispiel: `ey...` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx index b0a7b15254..944ab445d3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # VARTA element - +
+
+ PV nur verfügbar mit PV-Sensor @@ -59,6 +62,17 @@ PV nur verfügbar mit PV-Sensor +
+
+ +
+
## Templateparameter `varta` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx index 6af1eb6ec3..45932f4895 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # VARTA pulse neo - +
+
+ PV nur verfügbar mit PV-Sensor @@ -59,6 +62,17 @@ PV nur verfügbar mit PV-Sensor +
+
+ +
+
## Templateparameter `varta` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx index 0ef29d3fa8..ee49684823 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # VARTA pulse - +
+
+ PV nur verfügbar mit PV-Sensor @@ -59,6 +62,17 @@ PV nur verfügbar mit PV-Sensor +
+
+ +
+
## Templateparameter `varta` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx index d3634052c0..3d0e997b10 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EM24 - +
+
+ EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschluss, denn die Definition ist nicht kompatibel. @@ -63,10 +66,21 @@ EM24 mit RS-485-Anschluss. Benutze die EM24_E1 für die EM24 mit Ethernet-Anschl +
+
+ +
+
## Templateparameter `cg-em24` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx index 54399affd7..9225c3e68b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EM24_E1 - +
+
+ EM24_E1 mit Ethernet-Anschluss. Benutze die EM24 für die EM24 mit RS-485-Anschluss, denn die Definition ist nicht kompatibel. Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finden: [victronenergy.com](https://professional.victronenergy.com/downloads/firmware/) @@ -50,10 +53,21 @@ Die EM24_E1 muss mindestens Firmware version 1.8.3 haben, diese is hier zu finde +
+
+ +
+
## Templateparameter `cg-em24_e1` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx index 7c8152b5ee..d108093e66 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron EM530/EM540 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt3xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx index 07cdfda647..d1951ace5a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron Energy - +
+
+ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt werden soll. @@ -27,16 +30,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional)`} advanced={`meters: - - name: my_grid - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP-Adresse oder Hostname - port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + meterid: # Grid-Energiezähler VRM Instanz, Kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional)`} /> @@ -54,9 +48,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional)`} /> + maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional`} /> @@ -80,6 +72,17 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer +
+
+ +
+
## Templateparameter `victron-energy` @@ -87,7 +90,7 @@ Für Grid-Nutzung ist eine VRM-Instanz notwendig wenn Lastmanagement genutzt wer |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `502` | nein | -| `meterid` | Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. | | nein | +| Grid-Energiezähler VRM Instanz
`meterid` | Kann im VRM Portal oder im RemoteUI ausgelesen werden. | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Maximale AC Leistung des Hybrid-Wechselrichters
`maxacpower` | | Beispiel: `5000`
Einheit: W | nein | | Minimaler Ladestand
`minsoc` | Untere Grenze beim Entladen der Batterie im normalen Betrieb | Beispiel: `25`
Einheit: % | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx index 63d9220ac6..ba2498efb0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron ET340 - +
+
+ @@ -72,10 +75,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `cg-emt3xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx index df34db790a..f8f43e521d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -9,25 +9,39 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkszähler HTTP API, Import & Export - +
+
+ + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID`} /> +
+
+ +
+
## Templateparameter `volkszaehler-importexport` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| URL des "data" Kontexts der Volkszähler Middleware
`url` | Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data | | nein | -| `importuuid` | | | ja | -| `exportuuid` | | | ja | +| Middleware URL
`url` | | Beispiel: `http://zaehler.network.local:8080/api/data` | nein | +| Import UUID
`importuuid` | | | ja | +| Export UUID
`exportuuid` | | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx index f89c920713..7afc7ca952 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx @@ -9,23 +9,37 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkszähler HTTP API - +
+
+ + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID`} /> +
+
+ +
+
## Templateparameter `volkszaehler-http` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| URL des "data" Kontexts der Volkszähler Middleware
`url` | Beispiel: http://zaehler.network.local:8080/api/data | | nein | -| `uuid` | | | ja | +| Middleware URL
`url` | | Beispiel: `http://zaehler.network.local:8080/api/data` | nein | +| UUID
`uuid` | | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx index 93e7249a46..54702ec557 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkszähler WebSocket API - +
+
+ + uuid: # UUID`} /> +
+
+ +
+
## Templateparameter `volkszaehler-ws` @@ -29,5 +43,5 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `8082` | nein | -| `uuid` | | | ja | +| UUID
`uuid` | | | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx index 4d82eec231..64896b95c2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # vzlogger - +
+
+ +
+
+ +
+
## Templateparameter `vzlogger` @@ -47,16 +61,16 @@ import TabItem from '@theme/TabItem'; |-----------|-----------|------|----------| | IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | | Port
`port` | | Standard: `8081` | nein | -| `uuid` | | | ja | +| UUID
`uuid` | | | ja | | Skalierungsfaktor
`scale` | Multipliziere Rohwert mit diesem Faktor | Standard: `1` | nein | -| Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0)
`l1currentuuid` | | | nein | -| Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0)
`l2currentuuid` | | | nein | -| Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0)
`l3currentuuid` | | | nein | -| Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0)
`l1poweruuid` | | | nein | -| Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0)
`l2poweruuid` | | | nein | -| Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0)
`l3poweruuid` | | | nein | -| Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0)
`l1voltageuuid` | | | nein | -| Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0)
`l2voltageuuid` | | | nein | -| Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0)
`l3voltageuuid` | | | nein | +| Strom in Phase 1
`l1currentuuid` | Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0) | | nein | +| Strom in Phase 2
`l2currentuuid` | Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0) | | nein | +| Strom in Phase 3
`l3currentuuid` | Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0) | | nein | +| Leistung in Phase 1
`l1poweruuid` | Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0) | | nein | +| Leistung in Phase 2
`l2poweruuid` | Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0) | | nein | +| Leistung in Phase 3
`l3poweruuid` | Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0) | | nein | +| Spannung in Phase 1
`l1voltageuuid` | Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0) | | nein | +| Spannung in Phase 2
`l2voltageuuid` | Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0) | | nein | +| Spannung in Phase 3
`l3voltageuuid` | Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0) | | nein | | Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `1s`
Beispiel: `5m` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx index 1d4a6be57b..6cc6a6e730 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wago 879-30xx - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `wago-879-30xx` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx index b9af12f013..e41a58b043 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Wattsonic - +
+
+ @@ -52,7 +55,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -92,7 +95,7 @@ import TabItem from '@theme/TabItem'; id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> @@ -133,16 +136,27 @@ import TabItem from '@theme/TabItem'; host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Verzögerung, optional`} /> +
+
+ +
+
## Templateparameter `wattsonic` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `delay` | | Standard: `100ms` | nein | +| Verzögerung
`delay` | | Standard: `100ms` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx index f37ea26704..e111432037 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM110-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron-sdm220_230` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx index d09251e953..aadc1e7e68 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM111-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron-sdm220_230` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx index 21cea49bd6..0c68f069c8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM120-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx index f4e0ade113..2c5d4f76c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Weidmüller EM122-RTU-2P - +
+
+ @@ -60,10 +63,21 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `eastron` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx index 16d17dde07..99998aaa9c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Youless Energy Monitor - +
+
+ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszähler benötigt. @@ -39,6 +42,17 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh +
+
+ +
+
## Templateparameter `youless` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx index 7f22c74c94..c4836e6404 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ZCS Azzurro Hybrid Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sofarsolar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx index 4a7bd8edea..ad7cc447bd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ZCS Azzurro Inverter - +
+
+ @@ -124,11 +127,22 @@ import TabItem from '@theme/TabItem'; +
+
+ +
+
## Templateparameter `sofarsolar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx index a22e1112fc..ecdd794a4b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zendure Hyper 2000 - +
+
+ @@ -22,9 +25,9 @@ import TabItem from '@theme/TabItem'; type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional`} /> @@ -35,30 +38,41 @@ import TabItem from '@theme/TabItem'; type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional`} advanced={`meters: - name: my_battery type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional capacity: 2 # Akkukapazität (kWh), optional`} /> +
+
+ +
+
## Templateparameter `zendure` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `account` | | Beispiel: `dev@zendure.com` | ja | -| `serial` | Zu finden in der Zendure App in den Einstellungen des Geräts | Beispiel: `VU5D99F74021B04` | ja | -| `region` | | Standard: `EU`
Auswahl: `EU`, `Global` | ja | +| Account ID
`account` | | Beispiel: `dev@zendure.com` | ja | +| Seriennummer
`serial` | Zu finden in der Zendure App in den Einstellungen des Geräts | Beispiel: `VU5D99F74021B04` | ja | +| Region
`region` | | Standard: `EU`
Auswahl: `EU`, `Global` | ja | | Zeitüberschreitung
`timeout` | | Beispiel: `10s` | nein | | Akkukapazität
`capacity` | | Standard: `2`
Beispiel: `50`
Einheit: kWh | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx index 88eb90fd75..0c2b4af582 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zuidwijk SlimmeLezer(+) in Luxembourg - +
+
+ Slimmelezer-Geräte in Luxemburg verwenden für verschiedene Sensoren andere Namen. @@ -23,6 +26,17 @@ Slimmelezer-Geräte in Luxemburg verwenden für verschiedene Sensoren andere Nam template: slimmelezer-luxembourg usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `slimmelezer-luxembourg` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx index 9726ef6664..7a2be16da6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zuidwijk SlimmeLezer(+) V2 - +
+
+ Neuere Slimmelezer-Geräte verwenden eine andere Konfiguration. Probieren Sie diese Vorlage aus, wenn die andere fehlschlägt. @@ -23,6 +26,17 @@ Neuere Slimmelezer-Geräte verwenden eine andere Konfiguration. Probieren Sie di template: slimmelezer-V2 usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname`} /> +
+
+ +
+
## Templateparameter `slimmelezer-V2` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx index 8ebef4e269..03a9339b4c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zuidwijk SlimmeLezer(+) - +
+
+ +
+
+ +
+
## Templateparameter `slimmelezer` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx index 6c98728d56..1f2e308d91 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx @@ -9,35 +9,49 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Amber Electric - +
+
+ +
+
+ +
+
## Templateparameter `amber` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | | | nein | -| `siteid` | | | nein | -| `channel` | | | nein | +| Token
`token` | | | nein | +| Site ID
`siteid` | | | nein | +| Kanal
`channel` | | | nein | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx index d20e527ff7..981996ea6a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx @@ -9,29 +9,43 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Awattar - +
+
+ +
+
+ +
+
## Templateparameter `awattar` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `region` | | Beispiel: `AT`
Auswahl: `DE`, `AT` | ja | +| Region
`region` | | Beispiel: `AT`
Auswahl: `DE`, `AT` | ja | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx index 1613d62671..84d3f32f93 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Electricity Maps Commercial API - +
+
+ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. @@ -22,14 +25,25 @@ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps type: template template: electricitymaps uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) Adresse - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, siehe https://api.electricitymap.org/v3/zones`} /> +
+
+ +
+
## Templateparameter `electricitymaps` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | URI
`uri` | HTTP(S) Adresse | Beispiel: `https://api-access.electricitymaps.com/2w...1g/` | ja | -| `token` | | | ja | -| `zone` | siehe https://api.electricitymap.org/v3/zones | Beispiel: `DE` | ja | +| Token
`token` | | | ja | +| Zone
`zone` | siehe https://api.electricitymap.org/v3/zones | Beispiel: `DE` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx index 3cd687d904..80a90cf1eb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Electricity Maps Free API - +
+
+ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps.com). Der 'Free Personal Tier' beinhaltet leider keine Prognosedaten. Dafür benötigst du einen kommerziellen Account von [portal.electricitymaps.com](https://portal.electricitymaps.com). Kostenloser Testmonat verfügbar. @@ -21,13 +24,24 @@ CO₂-Daten für viele Länder von [electricitymaps.com](https://electricitymaps co2: type: template template: electricitymaps-free - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, siehe https://api.electricitymap.org/v3/zones`} /> +
+
+ +
+
## Templateparameter `electricitymaps-free` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | | | ja | -| `zone` | siehe https://api.electricitymap.org/v3/zones | Beispiel: `DE` | ja | +| Token
`token` | | | ja | +| Zone
`zone` | siehe https://api.electricitymap.org/v3/zones | Beispiel: `DE` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx index d9a7b61bd2..4d2e167050 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx @@ -9,29 +9,43 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Energinet - +
+
+ +
+
+ +
+
## Templateparameter `energinet` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `region` | | Beispiel: `dk1`
Auswahl: `dk1`, `dk2` | ja | +| Region
`region` | | Beispiel: `dk1`
Auswahl: `dk1`, `dk2` | ja | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx index ff1f9e0040..a9b6bea1c2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx @@ -9,35 +9,49 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Enever - +
+
+ + interval: 3h # Intervall, optional`} /> +
+
+ +
+
## Templateparameter `enever` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | | | ja | -| `provider` | | Auswahl: ``, `AA`, `AIP`, `ANWB`, `BE`
, `EE`, `EN`, `EVO`, `EZ`, `FR`
, `GSL`, `MDE`, `NE`, `PE`, `TI`
, `VDB`, `VON`, `WE`, `ZG`, `ZP`
| ja | +| Token
`token` | | | ja | +| Anbieter
`provider` | | Auswahl: ``, `AA`, `AIP`, `ANWB`, `BE`
, `EE`, `EN`, `EVO`, `EZ`, `FR`
, `GSL`, `MDE`, `NE`, `PE`, `TI`
, `VDB`, `VON`, `WE`, `ZG`, `ZP`
| ja | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | -| `interval` | | Standard: `3h` | nein | +| Intervall
`interval` | | Standard: `3h` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx index ccc14d8de9..be3808cbdc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ENTSO-E - +
+
+ Day-ahead-Preise für den europäischen Strommarkt. Siehe https://transparency.entsoe.eu für weitere Informationen. Basis für viele dynamische Tarife. @@ -22,23 +25,34 @@ Basis für viele dynamische Tarife. grid: type: template template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: + securitytoken: # Security token, Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: grid: type: template template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +
+
+ +
+
## Templateparameter `entsoe` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `securitytoken` | Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation | | nein | -| `domain` | siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas | Beispiel: `BZN\|DE-LU` | nein | +| Security token
`securitytoken` | Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation | | nein | +| Domain
`domain` | siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas | Beispiel: `BZN\|DE-LU` | nein | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx index 75ad5056a0..5bbbfd42de 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Forecast.Solar - +
+
+ [forecast.solar](https://forecast.solar) kann kostenlos verwendet werden. Kostenpflichtige Pläne können ebenfalls verwendet werden, indem ein API-Key angegeben wird. @@ -35,8 +38,19 @@ import TabItem from '@theme/TabItem'; kwp: 9.8 # Maximale Generatorleistung (kWp) az: 180 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizont, Simuliert Verschattung durch Gelände, [mehr Informationen](https://doc.forecast.solar/horizon) (optional) - apikey: # API-Key, optional - interval: 1h # optional`} /> + apikey: # API Key, optional + interval: 1h # Intervall, optional`} /> +
+
+ +
+
## Templateparameter `forecast-solar` @@ -48,6 +62,6 @@ import TabItem from '@theme/TabItem'; | Maximale Generatorleistung
`kwp` | | Beispiel: `9.8`
Einheit: kWp | ja | | Azimut
`az` | -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden | Beispiel: `180` | ja | | Horizont
`horizon` | Simuliert Verschattung durch Gelände, \[mehr Informationen\](https://doc.forecast.solar/horizon) | Beispiel: `0,0,15,30,45,60,60,60,45,30,15,0` | nein | -| API-Key
`apikey` | | | nein | -| `interval` | | Standard: `1h` | nein | +| API Key
`apikey` | | | nein | +| Intervall
`interval` | | Standard: `1h` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx index 4c4c14abf9..02b39afacb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fraunhofer ISE - +
+
+ Day-ahead Energiepreise (je kWh) an der Börse. Kann ohne vorherige Anmeldung auf https://api.energy-charts.info/ abgerufen werden. Nutzbar u.a. für dynamische Stromtarife, wo der Anbieter bis dato auf der Kundenschnittstelle noch kein Preis-Vorhersagen anbietet. @@ -21,20 +24,31 @@ Day-ahead Energiepreise (je kWh) an der Börse. Kann ohne vorherige Anmeldung au grid: type: template template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: + bzn: DE-LU # Gebotszone, siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: grid: type: template template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Gebotszone, siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +
+
+ +
+
## Templateparameter `energy-charts-api` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `bzn` | Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get | Standard: `DE-LU`
Auswahl: `AT`, `BE`, `CH`, `CZ`, `DE-LU`
, `DE-AT-LU`, `DK1`, `DK2`, `FR`, `HU`
, `IT-NORTH`, `NL`, `NO2`, `PL`, `SE4`
, `SI` | ja | +| Gebotszone
`bzn` | siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get | Standard: `DE-LU`
Auswahl: `AT`, `BE`, `CH`, `CZ`, `DE-LU`
, `DE-AT-LU`, `DK1`, `DK2`, `FR`, `HU`
, `IT-NORTH`, `NL`, `NO2`, `PL`, `SE4`
, `SI` | ja | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx index 6435bc387b..021577e0aa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Green Grid Compass - +
+
+ Europäische CO₂-Intensitätsdaten von [greengrid-compass.eu](https://www.greengrid-compass.eu). Liefert Vorhersagen der nächsten Stunden und ist nach Registrierung kostenlos nutzbar. @@ -21,13 +24,24 @@ Europäische CO₂-Intensitätsdaten von [greengrid-compass.eu](https://www.gree co2: type: template template: green-grid-compass - apiKey: # API-Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key + apiKey: # API Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key zone: DE_LU # Zonencode, [BE, DE_LU]`} /> +
+
+ +
+
## Templateparameter `green-grid-compass` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| API-Key
`apiKey` | Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key | | ja | +| API Key
`apiKey` | Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key | | ja | | Zonencode
`zone` | | Standard: `DE_LU`
Auswahl: `BE`, `DE_LU` | ja | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx index 9ad6dc8c2a..1c6a310b51 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Groupe E Vario Plus - +
+
+ +
+
+ +
+
## Templateparameter `groupe-e` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx index b9bef4a18f..20c8164cb5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Grünstromindex - +
+
+ Regionale Emissionsdaten von https://gruenstromindex.de @@ -21,13 +24,24 @@ Regionale Emissionsdaten von https://gruenstromindex.de co2: type: template template: grünstromindex - zip: - token: # Token für den Zugriff auf die API von https://console.corrently.io/ (optional)`} /> + zip: # Postleitzahl + token: # Token, Token für den Zugriff auf die API von https://console.corrently.io/ (optional)`} /> +
+
+ +
+
## Templateparameter `grünstromindex` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `zip` | | | ja | -| `token` | Token für den Zugriff auf die API von https://console.corrently.io/ | | nein | +| Postleitzahl
`zip` | | | ja | +| Token
`token` | Token für den Zugriff auf die API von https://console.corrently.io/ | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx index 7ef82c22d2..a400b736b1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx @@ -9,22 +9,36 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # National Grid ESO - +
+
+ + region: 1 # Region, Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Postleitzahl, Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. (optional)`} /> +
+
+ +
+
## Templateparameter `ngeso` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `region` | Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list | Beispiel: `1` | nein | -| `postalcode` | Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. | Beispiel: `SW1` | nein | +| Region
`region` | Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list | Beispiel: `1` | nein | +| Postleitzahl
`postalcode` | Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. | Beispiel: `SW1` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx index e77b043369..4abe321c34 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nordpool spot prices - +
+
+ Nordpool Spot Preise im Day-Ahead-Markt für alle Märkte in der Nordpool-Region. @@ -21,23 +24,34 @@ Nordpool Spot Preise im Day-Ahead-Markt für alle Märkte in der Nordpool-Region grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Währung, [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Währung, [DKK, EUR, NOK, PLN, RON, SEK] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +
+
+ +
+
## Templateparameter `nordpool` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `region` | | Beispiel: `GER`
Auswahl: `EE`, `LT`, `LV`, `AT`, `BE`
, `FR`, `GER`, `NL`, `PL`, `DK1`
, `DK2`, `FI`, `NO1`, `NO2`, `NO3`
, `NO4`, `NO5`, `SE1`, `SE2`, `SE3`
, `SE4`, `TEL`, `SYS` | nein | -| `currency` | | Standard: `EUR`
Auswahl: `DKK`, `EUR`, `NOK`, `PLN`, `RON`, `SEK` | ja | +| Region
`region` | | Beispiel: `GER`
Auswahl: `EE`, `LT`, `LV`, `AT`, `BE`
, `FR`, `GER`, `NL`, `PL`, `DK1`
, `DK2`, `FI`, `NO1`, `NO2`, `NO3`
, `NO4`, `NO5`, `SE1`, `SE2`, `SE3`
, `SE4`, `TEL`, `SYS` | nein | +| Währung
`currency` | | Standard: `EUR`
Auswahl: `DKK`, `EUR`, `NOK`, `PLN`, `RON`, `SEK` | ja | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx index 29d5d5fb3d..cd4383755a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Octopus Energy API - +
+
+ Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/accounts/personal-details/api-access @@ -21,13 +24,24 @@ Den API-Key bekommst du im Octopus Portal https://octopus.energy/dashboard/new/a grid: type: template template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional)`} /> + apiKey: # API Key + accountNumber: X-XXXXXXXX # Kundennummer, Nur erforderlich, wenn mehrere Konten vorhanden sind. (optional)`} /> +
+
+ +
+
## Templateparameter `octopus-api` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `apiKey` | Octopus Energy API Key. | | ja | -| `accountNumber` | Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. | | nein | +| API Key
`apiKey` | | | ja | +| Kundennummer
`accountNumber` | Nur erforderlich, wenn mehrere Konten vorhanden sind. | Beispiel: `X-XXXXXXXX` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx index f51c5b874e..47c4c2dd7d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx @@ -9,24 +9,38 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Octopus Energy Product Code - +
+
+ + productCode: AGILE-FLEX-22-11-25 # Tarifcode, Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. + region: # Region, Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Lastschrifttarif, Ich benutze den BACS-Lastschrifttarif. (optional)`} /> +
+
+ +
+
## Templateparameter `octopus-productcode` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `productCode` | Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. | Beispiel: `AGILE-FLEX-22-11-25` | ja | -| `region` | Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ | Auswahl: `A`, `B`, `C`, `D`, `E`
, `F`, `G`, `H`, `J`, `K`
, `L`, `M`, `N`, `P` | ja | -| `directDebit` | Ich benutze den BACS-Lastschrifttarif. | Standard: `true` | nein | +| Tarifcode
`productCode` | Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. | Beispiel: `AGILE-FLEX-22-11-25` | ja | +| Region
`region` | Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ | Auswahl: `A`, `B`, `C`, `D`, `E`
, `F`, `G`, `H`, `J`, `K`
, `L`, `M`, `N`, `P` | ja | +| Lastschrifttarif
`directDebit` | Ich benutze den BACS-Lastschrifttarif. | Standard: `true` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx index 4249e155a2..223332167d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Open-Meteo - +
+
+ Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Open-Source-Wetter-API und bietet kostenlosen Zugriff für nicht-kommerzielle Nutzung. Kein API-Schlüssel erforderlich. @@ -40,7 +43,18 @@ Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Op efficiency: 100 # Wirkungsgrad [%], optional alphatemp: -0.004 # Temperaturkoeffizient, optional rossmodel: 0.0342 # Kühlung [Ross-Modell], Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional`} /> + interval: 1h # Intervall, optional`} /> +
+
+ +
+
## Templateparameter `open-meteo` @@ -57,5 +71,5 @@ Freie Wetter API [open-meteo.com](https://open-meteo.com) Open-Meteo ist eine Op | Wirkungsgrad \[%\]
`efficiency` | | Standard: `100` | nein | | Temperaturkoeffizient
`alphatemp` | | Standard: `-0.004` | nein | | Kühlung \[Ross-Modell\]
`rossmodel` | Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) \[Paper\](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) | Standard: `0.0342` | nein | -| `interval` | | Standard: `1h` | nein | +| Intervall
`interval` | | Standard: `1h` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx index 0ec4d183f8..14082294c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ostrom - +
+
+ Erzeuge einen 'Production Client' im Ostrom-Entwicklerportal: https://developer.ostrom-api.io/ @@ -21,15 +24,26 @@ Erzeuge einen 'Production Client' im Ostrom-Entwicklerportal: https://developer. grid: type: template template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional)`} /> + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # Client ID + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a # Client Secret + contract: 100523456 # Vertragsnummer, Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional)`} /> +
+
+ +
+
## Templateparameter `ostrom` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `clientid` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | ja | -| `clientsecret` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a` | ja | -| `contract` | Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren | Beispiel: `100523456` | nein | +| Client ID
`clientid` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | ja | +| Client Secret
`clientsecret` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a` | ja | +| Vertragsnummer
`contract` | Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren | Beispiel: `100523456` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx index 67afbd0fd5..3d87b71c36 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # PUN Orario - +
+
+ Preisdaten von https://www.mercatoelettrico.org/it/. Wird oft zur Einspeisung ins Netz verwendet. @@ -27,6 +30,17 @@ Preisdaten von https://www.mercatoelettrico.org/it/. Wird oft zur Einspeisung in charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +
+
+ +
+
## Templateparameter `pun` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx index 8c9447a16f..4f480fb733 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # SmartEnergy smartCONTROL - +
+
+ +
+
+ +
+
## Templateparameter `smartenergy` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx index 01d7f22952..e3f0e23c50 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Solcast - +
+
+ Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting)-Account. Der kostenlose "Home User" Tarif ist für private Anwendungen oft ausreichend. Dieser Plan hat ein API-Limit von 10 Anfragen pro Tag. @@ -22,23 +25,34 @@ Benötigt einen [solcast.com](https://solcast.com/free-rooftop-solar-forecasting - type: template template: solcast site: # Ressource ID deiner Anlage - token: # Solcast API Token`} advanced={`tariffs: + token: # API Token`} advanced={`tariffs: solar: - type: template template: solcast site: # Ressource ID deiner Anlage - token: # Solcast API Token - from: # Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) - to: # Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) - interval: 3h # optional`} /> + token: # API Token + from: # Startzeit, Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) + to: # Endzeit, Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) + interval: 3h # Intervall, optional`} /> +
+
+ +
+
## Templateparameter `solcast` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `site` | Ressource ID deiner Anlage | | ja | -| `token` | Solcast API Token | | ja | -| `from` | Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" | | nein | -| `to` | Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" | | nein | -| `interval` | | Standard: `3h` | nein | +| Ressource ID deiner Anlage
`site` | | | ja | +| API Token
`token` | | | ja | +| Startzeit
`from` | Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" | | nein | +| Endzeit
`to` | Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" | | nein | +| Intervall
`interval` | | Standard: `3h` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx index cd8054a1b7..166080e0dd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx @@ -9,32 +9,46 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Spotty Energie - +
+
+ +
+
+ +
+
## Templateparameter `spottyenergy` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `contractid` | Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ | Beispiel: `ffffffff-4444-6666-2222-aaaaaabbbbbb` | ja | -| `pricetype` | Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren | Standard: `CONSUMPTION`
Auswahl: `MARKET`, `CONSUMPTION`, `GENERATION` | ja | +| Vertragsnummer
`contractid` | Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ | Beispiel: `ffffffff-4444-6666-2222-aaaaaabbbbbb` | ja | +| Preistyp
`pricetype` | Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren | Standard: `CONSUMPTION`
Auswahl: `MARKET`, `CONSUMPTION`, `GENERATION` | ja | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx index 36a8ce1a67..9255192e07 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tibber - +
+
+ Hol dir deinen API-Token aus dem Tibber-Entwicklerportal: https://developer.tibber.com/ @@ -21,23 +24,34 @@ Hol dir deinen API-Token aus dem Tibber-Entwicklerportal: https://developer.tibb grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional)`} advanced={`tariffs: + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional)`} advanced={`tariffs: grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional)`} /> +
+
+ +
+
## Templateparameter `tibber` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `token` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | ja | -| `homeid` | Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. | Beispiel: `cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c` | nein | +| API Token
`token` | | Beispiel: `476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4` | ja | +| Home ID
`homeid` | Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. | Beispiel: `cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c` | nein | | Aufschlag
`charges` | Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) | | nein | | Steuer
`tax` | Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) | | nein | | Formel
`formula` | Individuelle Formel zur Berechnung des Preises | Beispiel: `math.Max((price + charges) * (1 + tax), 0.0)` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx index 50ffc55e70..554ef7d252 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Victron VRM Solar Forecast - +
+
+ [vrm.victronenergy.com](https://vrm.victronenergy.com) abrufen der 2-Tage-Prognose einer Installation im VRM-Portal. Es wird ein kostenloses User Access Token benoetigt. @@ -28,13 +31,24 @@ import TabItem from '@theme/TabItem'; template: victron idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen - interval: 1h # optional`} /> + interval: 1h # Intervall, optional`} /> +
+
+ +
+
## Templateparameter `victron` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| | VRM-Installations-ID der Installation
`idsite` | Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt | Beispiel: `123456` | ja | -| API Zugriffstoken
`token` | Token können im VRM erstellt werden unter Präferenzen->Integrationen | | ja | -| `interval` | | Standard: `1h` | nein | +| API Zugriffstoken
`token` | Token können im VRM erstellt werden unter Präferenzen->Integrationen | | ja | +| Intervall
`interval` | | Standard: `1h` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx index 28a77fd586..f207e371f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Aiways - +
+ +
+
+ +
+ ## Templateparameter `aiways` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx index bb7aed0ffb..c9f7dc1ba8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Audi - +
+ +
+
+ +
+ ## Templateparameter `audi` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx index 2e392a73ad..fe5d84cd04 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # BMW -Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. +
+
+ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. +
+
+ +
+
## Templateparameter `bmw` @@ -55,10 +69,10 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WBMW...` | nein | | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `hcaptcha` | | | ja | +| Captcha Token
`hcaptcha` | | | ja | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx index d71318d3b9..78ebf7df96 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Citroën -Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ +
+
## Templateparameter `citroen` @@ -50,12 +64,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | -| `accessToken` | | | ja | -| `refreshToken` | | | ja | +| Access token
`accessToken` | | | ja | +| Refresh token
`refreshToken` | | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx index 2db9881835..d55a9b21dd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Dacia - +
+ +
+
+ +
+ ## Templateparameter `dacia` @@ -51,7 +65,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx index 1824af68f2..89586d0112 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # DS -Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ +
+
## Templateparameter `ds` @@ -50,12 +64,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | -| `accessToken` | | | ja | -| `refreshToken` | | | ja | +| Access token
`accessToken` | | | ja | +| Refresh token
`refreshToken` | | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx index ffc1087f81..e8b623f030 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx @@ -9,43 +9,57 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # evNotify - +
+ +
+
+ +
+ ## Templateparameter `evnotify` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `akey` | | | ja | -| `token` | | | ja | +| API Key
`akey` | | | ja | +| Token
`token` | | | ja | | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx index 5864f5ec78..2546bc773a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Fiat - +
+ +
+
+ +
+ ## Templateparameter `fiat` @@ -51,10 +65,10 @@ import TabItem from '@theme/TabItem'; | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `ZFAE...` | nein | | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `pin` | Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. | | nein | +| PIN
`pin` | Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. | | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx index 4437193c1a..d04b5e69ef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Ford - +
+ +
+
+ +
+ ## Templateparameter `ford-connect` @@ -50,12 +64,12 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | FordConnect API Client ID
`clientid` | Einrichtung unter https://developer.ford.com | | ja | | FordConnect API Client Secret
`clientsecret` | Einrichtung unter https://developer.ford.com | | ja | -| `accessToken` | | | ja | -| `refreshToken` | | | ja | +| Access token
`accessToken` | | | ja | +| Refresh token
`refreshToken` | | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WF0FXX...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx index de46a4b083..eea6c19d76 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Generisches Fahrzeug (ohne API) - +
+ +
+
+ +
+ ## Templateparameter `offline` @@ -39,7 +53,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx index d5b3b50feb..9c7b36a4ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Hyundai Bluelink -Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. +
+
+ Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. +
+
+ +
+
## Templateparameter `hyundai` @@ -55,7 +69,7 @@ Manche Modelle (z.B. Kona) schalten bei geringen Ladeströmen (< 8A) intern auf | Sprache
`language` | | Standard: `en`
Auswahl: `en`, `de` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx index af81ca30d1..0d73560a41 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ioBroker.bmw -ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api +
+
+ ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api +
+
+ +
+
## Templateparameter `ioBroker.bmw` @@ -48,10 +62,10 @@ ioBroker BMW Adapter. Benötigt ioBroker.bmw und ioBroker.simple-api | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Fahrzeugidentifikationsnummer
`vin` | BMW Fahrzeugidentifikationsnummer | Beispiel: `WBA8E9G50GM091234` | ja | -| ioBroker URL einschliesslich ioBroker.simple-api Port
`uri` | HTTP(S) Adresse | | ja | +| ioBroker URL
`uri` | einschliesslich ioBroker.simple-api Port | | ja | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx index c3149bc0c3..e9210f5746 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ISO15118 -Nur unterstützt wenn das Fahrzeug den Ladestand (Soc) an die verbundene Wallbox übermitteln kann. +
+
+ Nur unterstützt wenn das Fahrzeug den Ladestand (Soc) an die verbundene Wallbox übermitteln kann. Bei Verwendung von ISO15118 mit bestimmten VW Konzernfahrzeugen, z.B. Porsche Taycan, ist zusätzliche Konfiguration im Fahrzeug erforderlich. Dafür muss ein aktives Ortsbezogenes Ladeprofil mit der niedrigsten Minimalladung (25%) angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht in den Schalfmodus übergeben. @@ -31,11 +34,22 @@ angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +
+
+ +
+
## Templateparameter `iso15118` @@ -45,7 +59,7 @@ angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx index b990425542..ee039c5bca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Jeep - +
+ +
+
+ +
+ ## Templateparameter `fiat` @@ -51,10 +65,10 @@ import TabItem from '@theme/TabItem'; | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `ZFAE...` | nein | | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `pin` | Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. | | nein | +| PIN
`pin` | Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. | | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx index b3f4272aff..69a9f8079a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Kia Bluelink -Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. +
+
+ Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern auf 2 Phasen um. In den Fällen, in denen die Wallbox auch die Phasenströme misst, führt das zu unerwünschten Schwankungen der Ladeleistung. Abhilfe schafft hier, den Mindestladestrom auf 8A zu setzen. +
+
+ +
+
## Templateparameter `kia` @@ -55,7 +69,7 @@ Manche Modelle (z.B. Niro EV) schalten bei geringen Ladeströmen (< 8A) intern a | Sprache
`language` | | Standard: `en`
Auswahl: `en`, `de` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx index 1bee6f3498..a97d3f8b59 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mercedes-Benz -Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https://tinyurl.com/mbapi2020helptoken. +
+
+ Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https://tinyurl.com/mbapi2020helptoken. +
+
+ +
+
## Templateparameter `mercedes` @@ -52,13 +66,13 @@ Benötigt `access` und `refresh` Tokens. Anleitung zur Generierung hier: https:/ | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | -| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | ja | -| `accessToken` | | | ja | -| `refreshToken` | | | ja | +| Region
`region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | ja | +| Access token
`accessToken` | | | ja | +| Refresh token
`refreshToken` | | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx index 23f37582ef..5398101bb5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # MG - +
+ +
+
+ +
+ ## Templateparameter `mg` @@ -50,7 +64,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx index 60dc449a33..3f9afcd6c9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # mg2mqtt -Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway oder https://github.com/SAIC-iSmart-API/saic-java-client) +
+
+ Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway oder https://github.com/SAIC-iSmart-API/saic-java-client) +
+
+ +
+
## Templateparameter `mg2mqtt` @@ -51,7 +65,7 @@ Voraussetzung ist ein konfigurierter MQTT Broker und ein SAIC/MQTT Gateway (http | Zeitüberschreitung
`timeout` | | Standard: `1h`
Beispiel: `10s` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx index 2692280d32..70934a3932 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Mini -Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. +
+
+ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthedocs.io](https://bimmer-connected.readthedocs.io/en/latest/captcha/rest_of_world.html) generiert werden. Das Token ist nur für kurze Zeit gültig. Bitte möglichst schnell nach Generierung in die Konfiguration kopieren und evcc starten. +
+
+ +
+
## Templateparameter `mini` @@ -55,10 +69,10 @@ Benötigt `hcaptcha` Token. Dieses muss einmalig unter [bimmer-connected.readthe | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WBMW...` | nein | | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `hcaptcha` | | | ja | +| Captcha Token
`hcaptcha` | | | ja | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx index 85cbc1d249..e8b04f2d7e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # mz2mqtt -myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mqtt Installation https://github.com/C64Axel/mz2mqtt. +
+
+ myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mqtt Installation https://github.com/C64Axel/mz2mqtt. +
+
+ +
+
## Templateparameter `mz2mqtt` @@ -46,7 +60,7 @@ myMazda zu MQTT. Voraussetzung ist ein konfigurierter MQTT Broker und eine mz2mq | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx index 34105418f4..b189a038f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nissan Ariya - +
+ +
+
+ +
+ ## Templateparameter `nissan-ariya` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx index 4ed7588c2e..52826892e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nissan Leaf (pre 2019) - +
+ +
+
+ +
+ ## Templateparameter `carwings` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx index de9c4cffd3..9f5af7bc77 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Nissan Leaf - +
+ +
+
+ +
+ ## Templateparameter `nissan` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx index 1cc3d69700..2f33836e2f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # NIU E-Scooter - +
+ +
+
+ +
+ ## Templateparameter `niu-e-scooter` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx index bfc6d3dd91..4429eb7e01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Opel -Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ +
+
## Templateparameter `opel` @@ -50,12 +64,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | -| `accessToken` | | | ja | -| `refreshToken` | | | ja | +| Access token
`accessToken` | | | ja | +| Refresh token
`refreshToken` | | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx index 3fe697a26f..917aac9be1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Open Vehicle Monitoring System -Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei [Open Vehicle Monitoring System](http://api.openvehicles.com/). +
+
+ Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei [Open Vehicle Monitoring System](http://api.openvehicles.com/). +
+
+ +
+
## Templateparameter `ovms` @@ -50,14 +64,14 @@ Unterstützung für alle Fahrzeuge via ODB2 Adapter im Fahrzeug. Mehr Infos bei | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | | Passwort
`password` | Bei führenden Nullen bitte in einfache Hochkommata setzen | | ja | -| `vehicleid` | | | ja | +| Vehicle ID
`vehicleid` | | | ja | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | | Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | -| `server` | | Standard: `dexters-web.de` | ja | +| Server
`server` | | Standard: `dexters-web.de` | ja | | Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx index 8a359d2ca4..e5f44aa136 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Peugeot -Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ +
+
## Templateparameter `peugeot` @@ -50,12 +64,12 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | -| `accessToken` | | | ja | -| `refreshToken` | | | ja | +| Access token
`accessToken` | | | ja | +| Refresh token
`refreshToken` | | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx index c7522d8ee8..6f1f302694 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Polestar - +
+ +
+
+ +
+ ## Templateparameter `polestar` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx index 5fe3266216..4d08b5f53a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx @@ -9,50 +9,64 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # PSA Car Controller -Remote Control of PSA car https://github.com/flobz/psa_car_controller +
+
+ Remote Control of PSA car https://github.com/flobz/psa_car_controller + wakeup_alt: false # Alternativer Wakeup-Code, Kann zu erhöhter Entladung der 12V-Batterie führen. (optional)`} /> +
+
+ +
+
## Templateparameter `flobz` | Name | Erklärung | Wert | Optional | |-----------|-----------|------|----------| -| `url` | | Beispiel: `http://192.0.2.2` | ja | +| URL
`url` | | Beispiel: `http://192.0.2.2` | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | | Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | -| `wakeup_alt` | alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. | | nein | +| Alternativer Wakeup-Code
`wakeup_alt` | Kann zu erhöhter Entladung der 12V-Batterie führen. | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx index 2384a2104c..2e79b059e8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Renault - +
+ +
+
+ +
+ ## Templateparameter `renault` @@ -50,7 +64,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx index 185126ba83..6d6970869f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) - +
+ +
+
+ +
+ ## Templateparameter `seat` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx index b576d59a9c..9c3934618e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Seat CupraConnect Gen4 (Born, Formentor, Tavascan) - +
+ +
+
+ +
+ ## Templateparameter `cupra` @@ -51,7 +65,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx index 412dcd118f..8de4a50b01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Skoda Enyaq - +
+ +
+
+ +
+ ## Templateparameter `enyaq` @@ -52,7 +66,7 @@ import TabItem from '@theme/TabItem'; | Zeitüberschreitung
`timeout` | | Standard: `10s`
Beispiel: `10s` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx index 8e6688e249..7c3c1a745c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smart - +
+ +
+
+ +
+ ## Templateparameter `smart-hello` @@ -51,7 +65,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx index 85b6b45d52..bb9718ff17 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Smart EQ -Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc token [name]` generiert werden. +
+
+ +
+
## Templateparameter `smart` @@ -52,13 +66,13 @@ Benötigt `access` und `refresh` Tokens. Diese können über den Befehl `evcc to | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Benutzerkonto
`user` | bspw. E-Mail Adresse, User Id, etc. | | ja | -| `region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | ja | -| `accessToken` | | | ja | -| `refreshToken` | | | ja | +| Region
`region` | | Standard: `EMEA`
Auswahl: `EMEA`, `APAC`, `NORAM` | ja | +| Access token
`accessToken` | | | ja | +| Refresh token
`refreshToken` | | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `V...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx index d63f47fd01..089d811293 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla BLE -Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy +
+
+ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy +
+
+ +
+
## Templateparameter `tesla-ble` @@ -47,11 +61,11 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Fahrzeugidentifikationsnummer
`vin` | Erforderlich für BLE-Verbindung | Beispiel: `W...` | ja | -| `url` | URL des Tesla BLE HTTP Proxy | Beispiel: `http://192.168.178.27` | ja | +| URL
`url` | URL des Tesla BLE HTTP Proxy | Beispiel: `http://192.168.178.27` | ja | | Port
`port` | Port des Tesla BLE HTTP Proxy | Standard: `8080`
Beispiel: `8080` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx index c3e69c06ef..b77dae8e51 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tesla -Tesla bietet eine offizielle, aber kostenpflichtige Fahrzeug-API an. +
+
+ Tesla bietet eine offizielle, aber kostenpflichtige Fahrzeug-API an. Für private Nutzung kannst du dir einen [Tesla Developer Account](https://developer.tesla.com/) erstellen und erhältst ein monatliches API-Guthaben von 10 €. Das ist für die gängigen evcc-Anwendungsfälle in der Regel ausreichend. @@ -34,29 +37,40 @@ Weitere Informationen und Alternativen findest du in [unserem Blogbeitrag](https template: tesla title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, von [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, von [myteslamate.com](https://app.myteslamate.com/). vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template template: tesla title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, von [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, von [myteslamate.com](https://app.myteslamate.com/). vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - commandProxy: https://api.myteslamate.com # Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) - proxyToken: # Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) + commandProxy: https://api.myteslamate.com # Command Proxy, Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) + proxyToken: # Proxy Token, Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)`} /> +
+
+ +
+
## Templateparameter `tesla` @@ -64,18 +78,18 @@ Weitere Informationen und Alternativen findest du in [unserem Blogbeitrag](https |-----------|-----------|------|----------| | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `clientId` | Kunden ID deiner \[Tesla Developer App\](https://developer.tesla.com/dashboard). | | ja | -| `accessToken` | von \[myteslamate.com\](https://app.myteslamate.com/). | | ja | -| `refreshToken` | von \[myteslamate.com\](https://app.myteslamate.com/). | | ja | +| Client ID
`clientId` | von \[Tesla Developer App\](https://developer.tesla.com/dashboard). | | ja | +| Access token
`accessToken` | von \[myteslamate.com\](https://app.myteslamate.com/). | | ja | +| Refresh token
`refreshToken` | von \[myteslamate.com\](https://app.myteslamate.com/). | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | | Priorität
`priority` | Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie | | nein | -| `commandProxy` | Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der \[myteslamate.com\](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel \[TeslaBleHttpProxy\](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. | Standard: `https://api.myteslamate.com` | nein | -| `proxyToken` | Token für den Command Proxy von \[myteslamate.com\](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. | | nein | +| Command Proxy
`commandProxy` | Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der \[myteslamate.com\](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel \[TeslaBleHttpProxy\](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. | Standard: `https://api.myteslamate.com` | nein | +| Proxy Token
`proxyToken` | Token für den Command Proxy von \[myteslamate.com\](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. | | nein | | Cache
`cache` | Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden | Standard: `15m`
Beispiel: `5m` | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx index 31bcb2ef52..54a0b9e7e8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TeslaLogger -Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger +
+
+ Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger +
+
+ +
+
## Templateparameter `teslalogger` @@ -47,11 +61,11 @@ Open Source Tesla Datenlogger https://github.com/bassmaster187/TeslaLogger | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | TeslaLogger CarID
`id` | | Standard: `1` | nein | -| `url` | | Beispiel: `http://192.0.2.2` | ja | +| URL
`url` | | Beispiel: `http://192.0.2.2` | ja | | Port
`port` | | Standard: `5000`
Beispiel: `5000` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx index 0e976919fc..47f4efde90 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # TeslaMate -Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Voraussetzung ist konfigurierter MQTT Broker. +
+
+ Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Voraussetzung ist konfigurierter MQTT Broker. +
+
+ +
+
## Templateparameter `teslamate` @@ -45,7 +59,7 @@ Open Source Tesla Datenlogger https://github.com/adriankumpf/teslamate. Vorausse | Fahrzeug-ID
`id` | | Standard: `1` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx index 327b71c728..10a45a596c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tessie -Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug niemals aufwecken; das Polling kann auf „always“ und interval „1M“ eingestellt werden. Wenn das Fahrzeug wach ist, sind die Daten normalerweise weniger als 15 Sekunden alt. Wenn das Fahrzeug schläft, stammen die Daten aus dem Zeitpunkt, zu dem es eingeschlafen ist. Holen Sie sich Ihr Token unter https://dash.tessie.com/settings/api +
+
+ Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug niemals aufwecken; das Polling kann auf „always“ und interval „1M“ eingestellt werden. Wenn das Fahrzeug wach ist, sind die Daten normalerweise weniger als 15 Sekunden alt. Wenn das Fahrzeug schläft, stammen die Daten aus dem Zeitpunkt, zu dem es eingeschlafen ist. Holen Sie sich Ihr Token unter https://dash.tessie.com/settings/api +
+
+ +
+
## Templateparameter `tessie` @@ -48,7 +62,7 @@ Verbinden Sie Ihr Tesla-Fahrzeug über die Tessie-API. Dies wird das Fahrzeug ni | Tessie API Token
`token` | | | ja | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx index aedf7e8b38..fc768b1aba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Toyota -Benötigt Toyota Connected Services Account. +
+
+ Benötigt Toyota Connected Services Account. +
+
+ +
+
## Templateparameter `toyota` @@ -52,7 +66,7 @@ Benötigt Toyota Connected Services Account. | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `JT...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx index 0335cb1776..cb9ec66fc2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Tronity - +
+ +
+
+ +
+ ## Templateparameter `tronity` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx index f428ac1a17..88d0258dde 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volkswagen We Connect ID -e-Golf, e-Up, ID Familie +
+
+ e-Golf, e-Up, ID Familie +
+
+ +
+
## Templateparameter `vw` @@ -57,7 +71,7 @@ e-Golf, e-Up, ID Familie | Zeitüberschreitung
`timeout` | | Standard: `10s`
Beispiel: `10s` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx index aa232dcd2a..0edf78b607 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Volvo -Für die Nutzung mit EVCC benötigst du einen Volvo Account und einen Volvo Connected Car API Key. +
+
+ Für die Nutzung mit EVCC benötigst du einen Volvo Account und einen Volvo Connected Car API Key. Erstelle dazu auf der [Account Seite](https://developer.volvocars.com/account/) eine neue Applikation und speichere den primären VCC API Key ab. Veröffentliche nun deine Applikation und wähle unter "Scopes" die Berechtigungen "Connected Vehicle API -> conve:vehicle-relation" und "Energy API -> (alles)" aus. Als Redirect URL musst du die URL deiner EVCC Instanz eintragen, zb "http://evcc.local:7070/oauth/callback". @@ -28,28 +31,39 @@ Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Is template: volvo-connected title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vccapikey: # VCC API Key, aus [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, aus [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, aus [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional)`} advanced={`vehicles: - name: my_car type: template template: volvo-connected title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vccapikey: # VCC API Key, aus [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, aus [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, aus [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)`} /> +
+
+ +
+
## Templateparameter `volvo-connected` @@ -57,14 +71,14 @@ Melde dich mit deinem Volvo Account an und erlaube den Zugriff auf die Daten. Is |-----------|-----------|------|----------| | Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | -| `vccapikey` | VCC API Key deiner \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | -| `clientId` | Client ID deiner \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | -| `clientSecret` | Client Secret deiner \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | -| `redirectUri` | Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. | | ja | +| VCC API Key
`vccapikey` | aus \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | +| Client ID
`clientId` | aus \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | +| Client Secret
`clientSecret` | aus \[Volvo Developer App\](https://developer.volvocars.com/). | | ja | +| Redirect URI
`redirectUri` | Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. | | ja | | Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `WF0FXX...` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx index 91b66a1187..70576b93f8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # volvo2mqtt -Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqtt-Installation https://github.com/Dielee/volvo2mqtt. +
+
+ Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqtt-Installation https://github.com/Dielee/volvo2mqtt. +
+
+ +
+
## Templateparameter `volvo2mqtt` @@ -48,7 +62,7 @@ Erforderlich ist eine konfigurierte MQTT Broker-Konfiguration und eine volvo2mqt | Zeitüberschreitung
`timeout` | | Standard: `720h`
Beispiel: `10s` | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx index 67ba0c3bd9..a54049e9f9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx @@ -9,10 +9,13 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # Zero Motorcycles - +
+ +
+
+ +
+ ## Templateparameter `zero` @@ -49,7 +63,7 @@ import TabItem from '@theme/TabItem'; | Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | | Icon
`icon` | Wird in der Benutzeroberfläche angezeigt | Standard: `car`
Auswahl: `car`, `bike`, `bus`, `moped`, `motorcycle`
, `rocket`, `scooter`, `taxi`, `tractor`, `rickshaw`
, `shuttle`, `van`, `airpurifier`, `battery`, `bulb`
, `climate`, `coffeemaker`, `compute`, `cooking`, `cooler`
, `desktop`, `device`, `dishwasher`, `dryer`, `floorlamp`
, `generic`, `heater`, `heatexchange`, `heatpump`, `kettle`
, `laundry`, `laundry2`, `machine`, `meter`, `microwave`
, `pump`, `smartconsumer`, `tool`, `waterheater` | nein | | Maximale Phasenanzahl
`phases` | Die maximale Anzahl der Phasen welche genutzt werden können | Beispiel: `3` | nein | -| Standardlademodus, wenn ein Fahrzeug angeschlossen ist
`mode` | Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | +| Standardlademodus
`mode` | Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll | | nein | | Minimale Stromstärke
`minCurrent` | Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `6`
Einheit: A | nein | | Maximale Stromstärke
`maxCurrent` | Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll | Beispiel: `16`
Einheit: A | nein | | Identifikation
`identifiers` | Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle | | nein | diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx index a324d1dcd1..bab24f2b63 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/chargers.mdx @@ -100,17 +100,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -128,17 +128,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -185,17 +185,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -300,17 +300,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -326,17 +326,17 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -377,17 +377,17 @@ The "Active load balancing" license is required for external Modbus control of t - name: my_charger type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -689,17 +689,17 @@ Setup Guide: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -722,17 +722,17 @@ Setup Guide: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -750,17 +750,17 @@ Setup Guide: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -776,17 +776,17 @@ Setup Guide: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -973,17 +973,17 @@ Phase switching is only available with the Solar variant and must be enabled by - name: my_charger type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -1518,9 +1518,9 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> @@ -1538,9 +1538,9 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> @@ -1558,9 +1558,9 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> @@ -1578,9 +1578,9 @@ DIP switch 10 at the controller needs to be set to 'ON'. A recent controller fir template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)`} /> @@ -1736,17 +1736,17 @@ Charge mode must be configured as `manual` - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -1762,17 +1762,17 @@ Charge mode must be configured as `manual` - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -1788,17 +1788,17 @@ Charge mode must be configured as `manual` - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -1816,17 +1816,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -1990,17 +1990,17 @@ Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15 - name: my_charger type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2018,17 +2018,17 @@ https://www.enercab.at/index.php?controller=attachment&id_attachment=311 - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2069,17 +2069,17 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2095,17 +2095,17 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2213,18 +2213,18 @@ The charger must be switched to "Power" charging mode. - name: my_charger type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) + meter: true # Meter ID, optional`} advanced={`chargers: - name: my_charger type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) + meter: true # Meter ID, optional connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2355,17 +2355,17 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft - name: my_charger type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2381,17 +2381,17 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2523,17 +2523,17 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2605,17 +2605,17 @@ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2651,17 +2651,17 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2812,17 +2812,17 @@ For login credentials, ask your dealer or the vendor EFR (www.efr.de). - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2840,17 +2840,17 @@ For login credentials, ask your dealer or the vendor EFR (www.efr.de). - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -2866,17 +2866,17 @@ For login credentials, ask your dealer or the vendor EFR (www.efr.de). - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -3655,17 +3655,17 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -3685,17 +3685,17 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -3715,17 +3715,17 @@ Setup, Backend, Backend Server: The evcc URL `ws://:8887/` must be - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -3746,7 +3746,7 @@ NRGkick charging unit via HTTP (older than 2022/2023) type: template template: nrgkick-connect host: 192.0.2.2 # IP address or hostname - mac: + mac: # MAC Address password: # Password, Use single quotes in case of leading zeros`} /> @@ -3776,7 +3776,7 @@ NRGkick charging unit via HTTP (older than 2022/2023) id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - phases1p3p: false # Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. (optional)`} /> + phases1p3p: false # Phase Switching enabled, Extended feature "Phase Switching" must be activated in the NRGKick app. (optional)`} /> @@ -3939,17 +3939,17 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must - name: my_charger type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5041,17 +5041,17 @@ The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must - name: my_charger type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5178,7 +5178,7 @@ Charger connected via the Tessie API. Allows control of charging state and confi template: tessie vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer token: # Tessie API Token - location: tessiehome # Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive)`} /> + location: tessiehome # Location, Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive)`} /> @@ -5230,7 +5230,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional)`} advanced={`chargers: + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -5238,7 +5238,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> @@ -5260,7 +5260,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional)`} advanced={`chargers: + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional)`} advanced={`chargers: - name: my_charger type: template template: tinkerforge-warp @@ -5268,7 +5268,7 @@ WARP Firmware v2 required. Automatic phase switching requires the additional WAR port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> @@ -5614,8 +5614,8 @@ Important: A mostly flawless functionality can only be provided with an external - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> @@ -5631,8 +5631,8 @@ Important: A mostly flawless functionality can only be provided with an external - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> @@ -5648,8 +5648,8 @@ Important: A mostly flawless functionality can only be provided with an external - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> @@ -5665,8 +5665,8 @@ Important: A mostly flawless functionality can only be provided with an external - name: my_charger type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621)`} /> + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621)`} /> @@ -5763,17 +5763,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5797,17 +5797,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5831,17 +5831,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5865,17 +5865,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5899,17 +5899,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5933,17 +5933,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -5967,17 +5967,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -6001,17 +6001,17 @@ Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-s - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -6142,7 +6142,7 @@ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. - name: my_charger type: template template: zaptec - id: # Charger ID (optional) + id: # ID, Charger ID (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> @@ -6164,17 +6164,17 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -6190,7 +6190,7 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: zaptec - id: # Charger ID (optional) + id: # ID, Charger ID (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> @@ -6208,7 +6208,7 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: zaptec - id: # Charger ID (optional) + id: # ID, Charger ID (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional)`} /> @@ -6226,17 +6226,17 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- - name: my_charger type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -6368,17 +6368,17 @@ The specific configuration and the actual usable functionality depend on the cha - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers: - name: my_charger type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form \`ws://:8887/\`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} /> + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)`} /> @@ -6403,14 +6403,14 @@ These adjustments enable more frequent and detailed reporting of charging data t - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456)`} advanced={`chargers: + token: # Token, API Token + identity: AA123456 # Charger identity`} advanced={`chargers: - name: my_charger type: template template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456) - connector: 1 # Loadpoint (if >1 loadpoint), Connector ID (usually 1)`} /> + token: # Token, API Token + identity: AA123456 # Charger identity + connector: 1 # Connector ID`} /> @@ -6436,7 +6436,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6446,8 +6446,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6464,7 +6464,7 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> @@ -6490,7 +6490,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6500,8 +6500,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6523,7 +6523,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6533,8 +6533,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6551,7 +6551,7 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> @@ -6574,7 +6574,7 @@ Integrated via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6596,7 +6596,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6606,8 +6606,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6649,7 +6649,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6659,8 +6659,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6697,7 +6697,7 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> @@ -6720,7 +6720,7 @@ Integrated via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6746,7 +6746,7 @@ Energy management settings of the device: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6790,7 +6790,7 @@ Energy management settings of the device: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + tempsource: 1 # Temperature source, [1, 2, 3] (optional) scale: 1 # Scale factor for power limit, optional`} /> @@ -6813,7 +6813,7 @@ Energy management settings of the device: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + tempsource: 1 # Temperature source, [1, 2, 3] (optional) scale: 1 # Scale factor for power limit, optional`} /> @@ -6838,7 +6838,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6848,8 +6848,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6871,7 +6871,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6881,8 +6881,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6906,7 +6906,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6916,8 +6916,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -6939,7 +6939,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -6949,8 +6949,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -7030,9 +7030,9 @@ The boost function heats hot water or a boost zone. The boost zone is identified template: vaillant user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - realm: DE # [DE, AT] (optional) - zone: # Boost zone id (optional) - setpoint: # Boost temperature setpoint (optional)`} /> + realm: DE # Region, [DE, AT] (optional) + zone: # Boost zone ID, optional + setpoint: # Boost temperature, optional`} /> @@ -7078,7 +7078,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -7088,8 +7088,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -7111,7 +7111,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_charger type: template template: luxtronik @@ -7121,8 +7121,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -7148,7 +7148,7 @@ Energy management settings of the device: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/heating.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/heating.mdx index bbd05e2cf1..cd5a5fcaa4 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/heating.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/heating.mdx @@ -176,7 +176,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -186,8 +186,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -202,7 +202,7 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> @@ -226,7 +226,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -236,8 +236,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -257,7 +257,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -267,8 +267,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -283,7 +283,7 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> @@ -304,7 +304,7 @@ Integrated via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -324,7 +324,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -334,8 +334,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -373,7 +373,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -383,8 +383,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -417,7 +417,7 @@ Integrated via [EMSESP](https://emsesp.org/) type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional)`} /> @@ -438,7 +438,7 @@ Integrated via [EMSESP](https://emsesp.org/) template: kermi host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -462,7 +462,7 @@ Energy management settings of the device: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -502,7 +502,7 @@ Energy management settings of the device: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + tempsource: 1 # Temperature source, [1, 2, 3] (optional) scale: 1 # Scale factor for power limit, optional`} /> @@ -523,7 +523,7 @@ Energy management settings of the device: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + tempsource: 1 # Temperature source, [1, 2, 3] (optional) scale: 1 # Scale factor for power limit, optional`} /> @@ -546,7 +546,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -556,8 +556,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -577,7 +577,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -587,8 +587,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -610,7 +610,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -620,8 +620,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -641,7 +641,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -651,8 +651,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -724,9 +724,9 @@ The boost function heats hot water or a boost zone. The boost zone is identified template: vaillant user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - realm: DE # [DE, AT] (optional) - zone: # Boost zone id (optional) - setpoint: # Boost temperature setpoint (optional)`} /> + realm: DE # Region, [DE, AT] (optional) + zone: # Boost zone ID, optional + setpoint: # Boost temperature, optional`} /> @@ -768,7 +768,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -778,8 +778,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -799,7 +799,7 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional)`} advanced={`chargers: + heatoffset: 0.0 # Heating temperature boost (K), optional`} advanced={`chargers: - name: my_heating type: template template: luxtronik @@ -809,8 +809,8 @@ For heatpumps with Luxtronik 2.1 controller. Uses modbus-tcp. Requires software id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional)`} /> @@ -834,7 +834,7 @@ Energy management settings of the device: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx index db860dc942..b0fcb303bb 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/meters.mdx @@ -122,7 +122,7 @@ If your system isn't listed here, that might mean that it is 100% SunSpec-compat id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -164,7 +164,7 @@ If your system isn't listed here, that might mean that it is 100% SunSpec-compat id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -207,7 +207,7 @@ If your system isn't listed here, that might mean that it is 100% SunSpec-compat host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -608,32 +608,7 @@ To use active battery control, times for grid charging must be defined once via modbus: tcpip id: 85 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: alpha-ess-smile - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 85 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 85 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -687,8 +662,6 @@ To use active battery control, times for grid charging must be defined once via id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -784,32 +757,7 @@ To use active battery control, times for grid charging must be defined once via modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -839,32 +787,7 @@ To use active battery control, times for grid charging must be defined once via modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -1978,32 +1901,7 @@ The firmware version should be at least version 1.8.3, you can find this version modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -2057,8 +1955,6 @@ The firmware version should be at least version 1.8.3, you can find this version id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -2178,9 +2074,7 @@ The firmware version should be at least version 1.8.3, you can find this version id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -2235,9 +2129,7 @@ The firmware version should be at least version 1.8.3, you can find this version id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -2293,7 +2185,7 @@ The firmware version should be at least version 1.8.3, you can find this version id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -2509,7 +2401,7 @@ The firmware version should be at least version 1.8.3, you can find this version usage: grid user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Meter ID`} /> @@ -2523,7 +2415,7 @@ The firmware version should be at least version 1.8.3, you can find this version usage: pv user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886`} /> + meter: 1ESY1161229886 # Meter ID`} /> @@ -2602,7 +2494,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_grid type: template template: e3dc-rscp @@ -2611,7 +2503,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional)`} /> @@ -2628,7 +2520,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_pv type: template template: e3dc-rscp @@ -2637,7 +2529,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -2655,7 +2547,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key:`} advanced={`meters: + key: # RSCP-Password`} advanced={`meters: - name: my_battery type: template template: e3dc-rscp @@ -2664,7 +2556,7 @@ Username and password are identical to Web Portal or My E3/DC App access. Key (= port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) capacity: 50 # Battery capacity (kWh), optional`} /> @@ -3001,13 +2893,13 @@ Only batteries of type "AC Battery" are currently supported by Enphase-API. template: enphase usage: grid host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_grid type: template template: enphase usage: grid host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -3021,13 +2913,13 @@ Only batteries of type "AC Battery" are currently supported by Enphase-API. template: enphase usage: pv host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_pv type: template template: enphase usage: pv host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -3041,13 +2933,13 @@ Only batteries of type "AC Battery" are currently supported by Enphase-API. template: enphase usage: battery host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional)`} advanced={`meters: - name: my_battery type: template template: enphase usage: battery host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) capacity: 50 # Battery capacity (kWh), optional cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -3163,8 +3055,8 @@ A commercial license is required for FEMS FENECON systems for active battery con usage: battery host: 192.0.2.2 # IP address or hostname password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) + battery: ess0 # Controllable battery component, optional + watchdog: 60s # Watchdog, adjusted to the API timeout (optional) capacity: 50 # Battery capacity (kWh), optional`} /> @@ -3275,32 +3167,7 @@ A commercial license is required for FEMS FENECON systems for active battery con modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -3354,8 +3221,6 @@ A commercial license is required for FEMS FENECON systems for active battery con id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -3451,32 +3316,7 @@ A commercial license is required for FEMS FENECON systems for active battery con modbus: tcpip id: 247 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: fox-ess-h3-smart - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 247 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 247 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -3530,8 +3370,6 @@ A commercial license is required for FEMS FENECON systems for active battery con id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -3640,7 +3478,7 @@ A commercial license is required for FEMS FENECON systems for active battery con usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> + id: 200 # ID, Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> @@ -3761,7 +3599,7 @@ Username and password are only required for active battery control. host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -3783,7 +3621,7 @@ Username and password are only required for active battery control. host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -3806,7 +3644,7 @@ Username and password are only required for active battery control. user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) capacity: 50 # Battery capacity (kWh), optional - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional)`} /> + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -3835,7 +3673,7 @@ Username and password are only required for active battery control. usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> + id: 200 # ID, Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional)`} /> @@ -4244,7 +4082,7 @@ Username and password are only required for active battery control. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} /> + battery: 1 # Battery number, [1, 2] (optional)`} /> @@ -4275,7 +4113,7 @@ Username and password are only required for active battery control. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Battery number, [1, 2] (optional)`} advanced={`meters: - name: my_pv type: template template: goodwe-hybrid @@ -4299,7 +4137,7 @@ Username and password are only required for active battery control. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -4331,7 +4169,7 @@ Username and password are only required for active battery control. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional)`} advanced={`meters: + battery: 1 # Battery number, [1, 2] (optional)`} advanced={`meters: - name: my_battery type: template template: goodwe-hybrid @@ -4355,7 +4193,7 @@ Username and password are only required for active battery control. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) capacity: 50 # Battery capacity (kWh), optional`} /> @@ -4806,7 +4644,7 @@ The active battery control uses the first "Battery first" timeslot, so it cannot template: hoymiles-ahoydtu usage: pv host: 192.0.2.2 # IP address or hostname - id: 0 # Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID], optional`} /> + id: 0 # Inverter ID, If multiple exist. The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID] (optional)`} /> @@ -4930,7 +4768,7 @@ The active battery control uses the first "Battery first" timeslot, so it cannot host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Battery storage unit index, optional`} /> @@ -4960,7 +4798,7 @@ The active battery control uses the first "Battery first" timeslot, so it cannot host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -4991,7 +4829,7 @@ The active battery control uses the first "Battery first" timeslot, so it cannot host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional`} /> @@ -5061,7 +4899,7 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional`} /> + storageunit: 1 # Battery storage unit index, optional`} /> @@ -5117,7 +4955,7 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -5174,7 +5012,7 @@ See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/6672506771534 host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxchargepower: 10000 # Maximum charge power (W), For forced charging of the battery. (optional) capacity: 50 # Battery capacity (kWh), optional forceaccharging: false # Inverter cascade, Keep AC charging active to charge the storage from other inverters via AC. Prevents stand-by. (optional)`} /> @@ -5867,9 +5705,7 @@ Only a single system may access the inverter! For active battery control the fun port: 1502 # Port endianness: little # Endianness (Little/Big), [little, big] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -5901,7 +5737,7 @@ Only a single system may access the inverter! For active battery control the fun capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -5944,7 +5780,7 @@ _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ port: 1502 # Port endianness: little # Endianness (Little/Big), [little, big] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -5975,7 +5811,7 @@ _see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ endianness: little # Endianness (Little/Big), [little, big] (optional) capacity: 50 # Battery capacity (kWh), optional maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -6048,9 +5884,7 @@ The energy meter must be installed in sensor position 2 (grid connection). Senso usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -6070,9 +5904,7 @@ The energy meter must be installed in sensor position 2 (grid connection). Senso usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -6092,7 +5924,7 @@ The energy meter must be installed in sensor position 2 (grid connection). Senso usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> @@ -6126,9 +5958,7 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -6148,9 +5978,7 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional)`} /> @@ -6170,7 +5998,7 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> @@ -6502,10 +6330,10 @@ To use the battery control, a firmware version greater than or equal to 10.05.74 host: 192.0.2.2 # Hostname port: 502 # Port capacity: 5.12 # Battery capacity (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - minsoc: 11 # Venus can only be discharged down to 11%. (%), Lower limit when discharging the battery in normal operation (optional) + minsoc: 11 # Minimum charge (%), Venus can only be discharged down to 11%. (optional) maxsoc: 100 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxchargepower: 2500 # Charge power in watts for Charge mode. 2500W is the maximum for Venus. (W), For forced charging of the battery. (optional) - work_mode_normal: 1 # Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode., optional`} /> + maxchargepower: 2500 # Maximum charge power (W), 2500W is the maximum for Venus. (optional) + work_mode_normal: 1 # Work mode for Normal state, 0=manual, 1=anti-feed, 2=trade mode. (optional)`} /> @@ -6657,8 +6485,8 @@ A commercial license is required for FEMS FENECON systems for active battery con usage: battery host: 192.0.2.2 # IP address or hostname password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) + battery: ess0 # Controllable battery component, optional + watchdog: 60s # Watchdog, adjusted to the API timeout (optional) capacity: 50 # Battery capacity (kWh), optional`} /> @@ -6935,7 +6763,7 @@ The values are updated approximately every 15 seconds, hence the evcc `interval` usage: grid user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti`} /> + id: main # ID, Id in case of multiple PowerOpti`} /> @@ -6955,7 +6783,7 @@ The values are updated approximately every 15 seconds, hence the evcc `interval` usage: pv user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti`} /> + id: main # ID, Id in case of multiple PowerOpti`} /> @@ -7056,7 +6884,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -7080,8 +6908,8 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional`} /> @@ -7112,7 +6940,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -7136,8 +6964,8 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -7169,7 +6997,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -7193,8 +7021,8 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional)`} /> @@ -7223,10 +7051,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. template: rct-power usage: grid host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional)`} /> + cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -7244,8 +7069,6 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. template: rct-power usage: pv host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) externalpower: # External power, Query external power of all devices connected to S0 (optional)`} /> @@ -7269,8 +7092,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional)`} /> + maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional)`} /> @@ -7502,32 +7324,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: saj-h2 - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -7557,32 +7354,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_pv - type: template - template: saj-h2 - usage: pv - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 115200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -7788,7 +7560,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. template: senec-home usage: grid host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -7801,7 +7573,7 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. template: senec-home usage: pv host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional)`} /> + schema: https # Schema, [https, http] (optional)`} /> @@ -7814,13 +7586,13 @@ The Qcells hybrid inverter has to be registered in the QcellsCloud. template: senec-home usage: battery host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional)`} advanced={`meters: + schema: https # Schema, [https, http] (optional)`} advanced={`meters: - name: my_battery type: template template: senec-home usage: battery host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) capacity: 50 # Battery capacity (kWh), optional`} /> @@ -8198,7 +7970,7 @@ The electrician needs to enable the Modbus via TCP/IP in their service app befor usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -8212,7 +7984,7 @@ The electrician needs to enable the Modbus via TCP/IP in their service app befor usage: pv host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional`} /> + id: 1 # ID, optional`} /> @@ -8226,14 +7998,14 @@ The electrician needs to enable the Modbus via TCP/IP in their service app befor usage: battery host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional`} advanced={`meters: + id: 1 # ID, optional`} advanced={`meters: - name: my_battery type: template template: sigenergy usage: battery host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional capacity: 50 # Battery capacity (kWh), optional`} /> @@ -8463,7 +8235,7 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -8499,7 +8271,7 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -8532,7 +8304,7 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -8586,7 +8358,7 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -9281,7 +9053,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -9335,7 +9107,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -9390,7 +9162,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> @@ -9457,7 +9229,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -9511,7 +9283,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -9566,7 +9338,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> @@ -9756,7 +9528,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -9810,7 +9582,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -9865,7 +9637,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> @@ -9932,7 +9704,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional)`} /> @@ -9986,7 +9758,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -10041,7 +9813,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional)`} /> @@ -10172,7 +9944,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re host: 192.0.2.2 # Hostname port: 1502 # Port timeout: 10s # Timeout, optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10229,7 +10001,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re port: 1502 # Port timeout: 10s # Timeout, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10286,7 +10058,7 @@ For optional battery control, StorageConf_CtrlMode (0xE004) must be set to 4 "Re port: 1502 # Port timeout: 10s # Timeout, optional capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10438,7 +10210,7 @@ For batter control, the "Connectivity+" function must be activated via the Solar id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10467,7 +10239,7 @@ For batter control, the "Connectivity+" function must be activated via the Solar host: 192.0.2.2 # Hostname port: 502 # Port maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10496,7 +10268,7 @@ For batter control, the "Connectivity+" function must be activated via the Solar host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional`} /> + watchdog: 60s # Watchdog, optional`} /> @@ -10841,7 +10613,7 @@ Combines data of all connected PV inverters or batteries. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_grid type: template template: solax @@ -10865,8 +10637,8 @@ Combines data of all connected PV inverters or batteries. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional`} /> + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional`} /> @@ -10897,7 +10669,7 @@ Combines data of all connected PV inverters or batteries. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_pv type: template template: solax @@ -10921,8 +10693,8 @@ Combines data of all connected PV inverters or batteries. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -10954,7 +10726,7 @@ Combines data of all connected PV inverters or batteries. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional`} advanced={`meters: + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional)`} advanced={`meters: - name: my_battery type: template template: solax @@ -10978,8 +10750,8 @@ Combines data of all connected PV inverters or batteries. id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional)`} /> @@ -11111,7 +10883,7 @@ The Solax inverter has to be registered in the SolaxCloud. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -11153,7 +10925,7 @@ The Solax inverter has to be registered in the SolaxCloud. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -11196,7 +10968,7 @@ The Solax inverter has to be registered in the SolaxCloud. host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -11535,14 +11307,14 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa usage: battery host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional)`} advanced={`meters: + token: # Token, API Token (required for active battery control) (optional)`} advanced={`meters: - name: my_battery type: template template: sonnenbatterie usage: battery host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional) + token: # Token, API Token (required for active battery control) (optional) capacity: 50 # Battery capacity (kWh), optional maxchargepower: 3300 # Maximum charge power (W), For forced charging of the battery. (optional) defaultmode: self-consumption # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. [self-consumption, time-of-use]`} /> @@ -11596,7 +11368,7 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -11638,7 +11410,7 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -11681,7 +11453,7 @@ The power for grid charging can be adapted to the inverter power of the sonnenBa host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -12006,32 +11778,7 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw modbus: tcpip id: 1 host: 192.0.2.2 # Hostname - port: 502 # Port`} advanced={`meters: - - name: my_grid - type: template - template: deye-hybrid-3p - usage: grid - - # RS485 via adapter (Modbus RTU) - modbus: rs485serial - id: 1 - device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse - baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200 - comset: "8N1" # Kommunikationsparameter für den Adapter - - # RS485 via TCP/IP (Modbus RTU) - modbus: rs485tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - - # Modbus TCP - modbus: tcpip - id: 1 - host: 192.0.2.2 # Hostname - port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + port: 502 # Port`} /> @@ -12085,8 +11832,6 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -12206,9 +11951,7 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -12263,9 +12006,7 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional includegenport: # Treat GEN port as solar input, optional`} /> @@ -12321,7 +12062,7 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -12565,7 +12306,7 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -12607,7 +12348,7 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -12650,7 +12391,7 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -12769,18 +12510,8 @@ The following apps allow to create the token: usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: - - name: my_grid - type: template - template: tesla-powerwall - usage: grid - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional)`} /> @@ -12794,18 +12525,8 @@ The following apps allow to create the token: usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: - - name: my_pv - type: template - template: tesla-powerwall - usage: pv - host: 192.0.2.2 # IP address or hostname - password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional)`} /> @@ -12819,16 +12540,16 @@ The following apps allow to create the token: usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional)`} advanced={`meters: - name: my_battery type: template template: tesla-powerwall usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> @@ -12848,8 +12569,8 @@ The following apps allow to create the token: type: template template: tibber-pulse usage: grid - token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE - homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional`} /> + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional`} /> @@ -13257,16 +12978,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional)`} advanced={`meters: - - name: my_grid - type: template - template: victron-energy - usage: grid - host: 192.0.2.2 # IP address or hostname - port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + meterid: # Grid meter VRM instance, Can be read out in VRM portal or via remoteUI. (optional)`} /> @@ -13286,9 +12998,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. usage: pv host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional)`} /> + maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional`} /> @@ -13487,7 +13197,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -13529,7 +13239,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -13572,7 +13282,7 @@ For grid usage, a grid meter VRM instance is require to enabled load management. host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional`} /> + delay: 100ms # Delay, optional`} /> @@ -14106,9 +13816,9 @@ An externally connected S0 generation meter is required to record the solar prod type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional`} /> @@ -14121,17 +13831,17 @@ An externally connected S0 generation meter is required to record the solar prod type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional`} advanced={`meters: - name: my_battery type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional capacity: 2 # Battery capacity (kWh), optional`} /> @@ -14760,8 +14470,8 @@ For demonstration purposes. Meter with a fixed set of values. type: template template: volkszaehler-http usage: grid - url: # URL of the middleware's "data" context, Example: http://zaehler.network.local:8080/api/data (optional) - uuid:`} /> + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID`} /> @@ -14776,9 +14486,9 @@ For demonstration purposes. Meter with a fixed set of values. type: template template: volkszaehler-importexport usage: grid - url: # URL of the middleware's "data" context, The URL is for example: http://zaehler.network.local:8080/api/data (optional) - importuuid: - exportuuid:`} /> + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID`} /> @@ -14795,7 +14505,7 @@ For demonstration purposes. Meter with a fixed set of values. usage: grid host: 192.0.2.2 # IP address or hostname port: 8082 # Port, optional - uuid:`} /> + uuid: # UUID`} /> @@ -14812,24 +14522,24 @@ For demonstration purposes. Meter with a fixed set of values. usage: grid host: 192.0.2.2 # IP address or hostname port: 8081 # Port, optional - uuid:`} advanced={`meters: + uuid: # UUID`} advanced={`meters: - name: my_grid type: template template: vzlogger usage: grid host: 192.0.2.2 # IP address or hostname port: 8081 # Port, optional - uuid: + uuid: # UUID scale: 1 # Scale factor, Multiply by this value (optional) - l1currentuuid: # The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0), optional - l2currentuuid: # The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0), optional - l3currentuuid: # The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0), optional - l1poweruuid: # The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0), optional - l2poweruuid: # The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0), optional - l3poweruuid: # The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0), optional - l1voltageuuid: # The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0), optional - l2voltageuuid: # The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0), optional - l3voltageuuid: # The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0), optional + l1currentuuid: # Current on phase 1, The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0) (optional) + l2currentuuid: # Current on phase 2, The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0) (optional) + l3currentuuid: # Current on phase 3, The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0) (optional) + l1poweruuid: # Power on phase 1, The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0) (optional) + l2poweruuid: # Power on phase 2, The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0) (optional) + l3poweruuid: # Power on phase 3, The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0) (optional) + l1voltageuuid: # Voltage on phase 1, The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0) (optional) + l2voltageuuid: # Voltage on phase 2, The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0) (optional) + l3voltageuuid: # Voltage on phase 3, The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0) (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -14893,7 +14603,7 @@ For demonstration purposes. Meter with a fixed set of values. device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: - name: my_grid type: template template: homematic @@ -14902,8 +14612,8 @@ For demonstration purposes. Meter with a fixed set of values. device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional)`} /> + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional)`} /> @@ -14919,7 +14629,7 @@ For demonstration purposes. Meter with a fixed set of values. device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: - name: my_pv type: template template: homematic @@ -14928,8 +14638,8 @@ For demonstration purposes. Meter with a fixed set of values. device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional)`} /> + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional)`} /> @@ -14945,7 +14655,7 @@ For demonstration purposes. Meter with a fixed set of values. device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface.`} advanced={`meters: - name: my_charger type: template template: homematic @@ -14954,8 +14664,8 @@ For demonstration purposes. Meter with a fixed set of values. device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional)`} /> + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional)`} /> @@ -15014,7 +14724,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15029,7 +14739,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15044,7 +14754,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15068,7 +14778,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15083,7 +14793,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15098,7 +14808,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15122,7 +14832,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15137,7 +14847,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15152,7 +14862,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15176,7 +14886,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15191,7 +14901,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15206,7 +14916,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15230,7 +14940,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15245,7 +14955,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15260,7 +14970,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15284,7 +14994,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15299,7 +15009,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15314,7 +15024,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15338,7 +15048,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15353,7 +15063,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15368,7 +15078,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15392,7 +15102,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15407,7 +15117,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> @@ -15422,7 +15132,7 @@ For demonstration purposes. Meter with a fixed set of values. host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional`} /> + channel: 0 # Channel, optional`} /> diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx index fc0277ff0d..55dad25514 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/smartswitches.mdx @@ -178,7 +178,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in type: template template: homematic host: 192.0.2.2 # IP address or hostname - port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC server port number, optional device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) @@ -187,14 +187,14 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in type: template template: homematic host: 192.0.2.2 # IP address or hostname - port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC server port number, optional device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Homematic meter channel number like shown in the CCU web user interface. - switchchannel: 3 # Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Homematic switch actor channel number like shown in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown in the CCU web user interface. + switchchannel: 3 # Switch/Actor channel number, Homematic switch actor channel number like shown in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)`} /> @@ -256,7 +256,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -264,7 +264,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) @@ -283,7 +283,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -291,7 +291,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) @@ -310,7 +310,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -318,7 +318,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) @@ -337,7 +337,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional)`} advanced={`chargers: - name: my_smartswitch type: template @@ -345,7 +345,7 @@ Additionally, the `soc` of the charger (if available) is no longer displayed in host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) diff --git a/i18n/en/docusaurus-plugin-content-docs/current/devices/vehicles.mdx b/i18n/en/docusaurus-plugin-content-docs/current/devices/vehicles.mdx index 88b270fc2c..ca27f8c0cc 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/devices/vehicles.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/devices/vehicles.mdx @@ -65,7 +65,7 @@ The availability and general quality of Vehicle data can vary greatly by manufac capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,7 +97,7 @@ The availability and general quality of Vehicle data can vary greatly by manufac capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -121,7 +121,7 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha:`} advanced={`vehicles: + hcaptcha: # Captcha Token`} advanced={`vehicles: - name: my_car type: template template: bmw @@ -130,10 +130,10 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -158,8 +158,8 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template @@ -167,12 +167,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -204,7 +204,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -228,8 +228,8 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template @@ -237,12 +237,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -264,7 +264,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional)`} advanced={`vehicles: + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional)`} advanced={`vehicles: - name: my_car type: template template: fiat @@ -273,10 +273,10 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -299,8 +299,8 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional clientid: # FordConnect API Client ID, Setup at https://developer.ford.com clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template @@ -309,12 +309,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional clientid: # FordConnect API Client ID, Setup at https://developer.ford.com clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -350,7 +350,7 @@ Some models (e.g. Kona) switch internally to 2 phases at low charging currents ( language: en # Language, [en, de] (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -372,7 +372,7 @@ Some models (e.g. Kona) switch internally to 2 phases at low charging currents ( vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional)`} advanced={`vehicles: + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional)`} advanced={`vehicles: - name: my_car type: template template: fiat @@ -381,10 +381,10 @@ Some models (e.g. Kona) switch internally to 2 phases at low charging currents ( vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -422,7 +422,7 @@ Some models (e.g. Niro EV) switch internally to 2 phases at low charging current language: en # Language, [en, de] (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -444,9 +444,9 @@ Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/ title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template @@ -454,13 +454,13 @@ Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/ title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -492,7 +492,7 @@ Requires `access` and `refresh` tokens. Documentation here: https://tinyurl.com/ capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -517,7 +517,7 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha:`} advanced={`vehicles: + hcaptcha: # Captcha Token`} advanced={`vehicles: - name: my_car type: template template: mini @@ -526,10 +526,10 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -566,7 +566,7 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -598,7 +598,7 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -630,7 +630,7 @@ Requires `hcaptcha` token. This must be generated once at [bimmer-connected.read capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -652,8 +652,8 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template @@ -661,12 +661,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -688,8 +688,8 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template @@ -697,12 +697,12 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -734,7 +734,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -766,7 +766,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -801,7 +801,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -833,7 +833,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -869,7 +869,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc timeout: 10s # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -903,7 +903,7 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -927,9 +927,9 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template @@ -937,13 +937,13 @@ Requires `access` and `refresh` tokens. These can be generated with command `evc title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -978,28 +978,28 @@ More information and alternatives can be found in [our blog post](https://docs.e template: tesla title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, from [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, from [myteslamate.com](https://app.myteslamate.com/). vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template template: tesla title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, from [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, from [myteslamate.com](https://app.myteslamate.com/). vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - commandProxy: https://api.myteslamate.com # When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) - proxyToken: # Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) + commandProxy: https://api.myteslamate.com # Command Proxy, When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) + proxyToken: # Proxy Token, Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -1029,7 +1029,7 @@ Requires Toyota Connected Services Account. vin: JT... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1065,7 +1065,7 @@ e-Golf, e-Up, ID family timeout: 10s # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1095,24 +1095,24 @@ Log in with your Volvo account and allow access to the data. If the authorizatio template: volvo-connected title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. + vccapikey: # VCC API Key, from [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, from [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, from [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect URI of your evcc instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional)`} advanced={`vehicles: - name: my_car type: template template: volvo-connected title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. + vccapikey: # VCC API Key, from [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, from [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, from [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect URI of your evcc instance, format: \`http://evcc.local:7070/oauth/callback\`. Must match the redirect URI set in your Volvo Developer App. vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1143,7 +1143,7 @@ Log in with your Volvo account and allow access to the data. If the authorizatio capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1196,20 +1196,20 @@ vehicles: - name: my_car type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional`} advanced={`vehicles: - name: my_car type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1234,7 +1234,7 @@ vehicles: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1255,17 +1255,17 @@ ioBroker BMW Adapter. Requires ioBroker.bmw and ioBroker.simple-api title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber - uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address`} advanced={`vehicles: + uri: # ioBroker URL, including ioBroker.simple-api Port`} advanced={`vehicles: - name: my_car type: template template: ioBroker.bmw title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber - uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address + uri: # ioBroker URL, including ioBroker.simple-api Port icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1298,7 +1298,7 @@ Otherwise the vehicle cannot be put into sleep mode. capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1331,7 +1331,7 @@ Required MQTT broker configuration and a SAIC/MQTT Gateway (https://github.com/S timeout: 1h # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1360,7 +1360,7 @@ myMazda to MQTT. Required MQTT broker configuration and a mz2mqtt installation h vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1383,7 +1383,7 @@ Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Veh capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - vehicleid:`} advanced={`vehicles: + vehicleid: # Vehicle ID`} advanced={`vehicles: - name: my_car type: template template: ovms @@ -1391,15 +1391,15 @@ Support for all vehicles via ODB2 adapter in the vehicle. More info at [Open Veh capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - vehicleid: + vehicleid: # Vehicle ID icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - server: dexters-web.de + server: dexters-web.de # Server cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional)`} /> @@ -1414,25 +1414,25 @@ Remote Control of PSA car https://github.com/flobz/psa_car_controller - name: my_car type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional`} advanced={`vehicles: - name: my_car type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - wakeup_alt: false # alternative wakeup-code; could lead to increased discharge of the 12V battery. (optional)`} /> + wakeup_alt: false # Alternative wakeup code, Can lead to increased discharge of the 12V battery. (optional)`} /> @@ -1449,7 +1449,7 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: W... # Vehicle Identification Number, Required for BLE connection - url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL of the Tesla BLE HTTP Proxy port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional)`} advanced={`vehicles: - name: my_car type: template @@ -1457,11 +1457,11 @@ Open Source Tesla BLE HTTP Proxy https://github.com/wimaha/TeslaBleHttpProxy title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: W... # Vehicle Identification Number, Required for BLE connection - url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL of the Tesla BLE HTTP Proxy port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1482,7 +1482,7 @@ Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional`} advanced={`vehicles: - name: my_car type: template @@ -1490,11 +1490,11 @@ Open source Tesla data logger https://github.com/bassmaster187/TeslaLogger title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1523,7 +1523,7 @@ Open source Tesla data logger https://github.com/adriankumpf/teslamate. MQTT bro id: 1 # Vehicle ID, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1554,7 +1554,7 @@ Connect your Tesla using the Tessie API. This will never wake up the car, pollin token: # Tessie API Token icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1585,7 +1585,7 @@ Connect your Tesla using the Tessie API. This will never wake up the car, pollin vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -1619,7 +1619,7 @@ Requires MQTT broker configuration and a volvo2mqtt installation https://github. timeout: 720h # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) diff --git a/i18n/en/docusaurus-plugin-content-docs/current/tariffs.mdx b/i18n/en/docusaurus-plugin-content-docs/current/tariffs.mdx index 1ef10730a1..f05ba53beb 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current/tariffs.mdx +++ b/i18n/en/docusaurus-plugin-content-docs/current/tariffs.mdx @@ -277,15 +277,15 @@ The plugin is updated once per hour. grid: type: template template: amber - token: # optional - siteid: # optional - channel: # optional`} advanced={`tariffs: + token: # Token, optional + siteid: # Site ID, optional + channel: # Channel, optional`} advanced={`tariffs: grid: type: template template: amber - token: # optional - siteid: # optional - channel: # optional + token: # Token, optional + siteid: # Site ID, optional + channel: # Channel, optional charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -302,11 +302,11 @@ The plugin is updated once per hour. grid: type: template template: awattar - region: AT # [DE, AT]`} advanced={`tariffs: + region: AT # Region, [DE, AT]`} advanced={`tariffs: grid: type: template template: awattar - region: AT # [DE, AT] + region: AT # Region, [DE, AT] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -323,11 +323,11 @@ The plugin is updated once per hour. grid: type: template template: energinet - region: dk1 # [dk1, dk2]`} advanced={`tariffs: + region: dk1 # Region, [dk1, dk2]`} advanced={`tariffs: grid: type: template template: energinet - region: dk1 # [dk1, dk2] + region: dk1 # Region, [dk1, dk2] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -344,17 +344,17 @@ The plugin is updated once per hour. grid: type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP]`} advanced={`tariffs: + token: # Token + provider: # Provider, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP]`} advanced={`tariffs: grid: type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + token: # Token + provider: # Provider, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) - interval: 3h # optional`} /> + interval: 3h # Interval, optional`} /> @@ -371,13 +371,13 @@ Basis for many dynamic tariffs. grid: type: template template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: + securitytoken: # Security token, Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)`} advanced={`tariffs: grid: type: template template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -396,11 +396,11 @@ Day-ahead forecast of energy prices (per kWh) on the exchange. No prior registra grid: type: template template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: + bzn: DE-LU # Bidding zone, see https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI]`} advanced={`tariffs: grid: type: template template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Bidding zone, see https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -438,13 +438,13 @@ Nordpool spot prices in day-ahead market for all markets in the Nordpool region. grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Currency, [DKK, EUR, NOK, PLN, RON, SEK]`} advanced={`tariffs: grid: type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Currency, [DKK, EUR, NOK, PLN, RON, SEK] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -465,8 +465,8 @@ You can get the API key in the Octopus portal https://octopus.energy/dashboard/n grid: type: template template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional)`} /> + apiKey: # API Key + accountNumber: X-XXXXXXXX # Account Number, Only required if you have multiple accounts. (optional)`} /> @@ -480,9 +480,9 @@ You can get the API key in the Octopus portal https://octopus.energy/dashboard/n grid: type: template template: octopus-productcode - productCode: AGILE-FLEX-22-11-25 # The tariff code for your energy contract. Make sure this is set to your import tariff code. - region: # The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] - directDebit: true # Use Direct Debit tariff rates. (optional)`} /> + productCode: AGILE-FLEX-22-11-25 # Product Code, The tariff code for your energy contract. Make sure this is set to your import tariff code. + region: # Region, The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Direct debit tariff, Use Direct Debit tariff rates. (optional)`} /> @@ -498,9 +498,9 @@ Create a 'Production Client' in the Ostrom developer portal: https://developer.o grid: type: template template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Only required if multiple contracts belong to the same user (optional)`} /> + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # Client ID + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a # Client Secret + contract: 100523456 # Contract number, Only required if multiple contracts belong to the same user (optional)`} /> @@ -554,13 +554,13 @@ Price data from https://www.mercatoelettrico.org/it/. Often used for feeding int grid: type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION]`} advanced={`tariffs: + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Contract ID, You can get your contract id from the customer portal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Price type, Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION]`} advanced={`tariffs: grid: type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Contract ID, You can get your contract id from the customer portal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Price type, Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -579,13 +579,13 @@ Get your API token from the Tibber developer portal: https://developer.tibber.co grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional)`} advanced={`tariffs: + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Only required if you have multiple homes in your Tibber account. (optional)`} advanced={`tariffs: grid: type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Only required if you have multiple homes in your Tibber account. (optional) charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional)`} /> @@ -609,8 +609,8 @@ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps type: template template: electricitymaps uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) address - token: - zone: DE # see https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, see https://api.electricitymap.org/v3/zones`} /> @@ -626,8 +626,8 @@ CO₂ data for many countries from [electricitymaps.com](https://electricitymaps co2: type: template template: electricitymaps-free - token: - zone: DE # see https://api.electricitymap.org/v3/zones`} /> + token: # Token + zone: DE # Zone, see https://api.electricitymap.org/v3/zones`} /> @@ -660,8 +660,8 @@ Regional emission data from https://gruenstromindex.de co2: type: template template: grünstromindex - zip: - token: # Token for accessing the API from https://console.corrently.io (optional)`} /> + zip: # ZIP code + token: # Token, Token for accessing the API from https://console.corrently.io (optional)`} /> @@ -675,8 +675,8 @@ Regional emission data from https://gruenstromindex.de co2: type: template template: ngeso - region: 1 # Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list (optional) - postalcode: SW1 # Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. (optional)`} /> + region: 1 # Region, Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Postcode, Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. (optional)`} /> @@ -729,8 +729,8 @@ Therefore, you may need to increase the update `interval`. kwp: 9.8 # Maximum generator power (kWp) az: 180 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizon, Simulates terrain shadows, [more information](https://doc.forecast.solar/horizon) (optional) - apikey: # API key, optional - interval: 1h # optional`} /> + apikey: # API Key, optional + interval: 1h # Interval, optional`} /> @@ -765,7 +765,7 @@ Free Weather API [open-meteo.com](https://open-meteo.com) Open-Meteo is an open- efficiency: 100 # Efficiency [%], optional alphatemp: -0.004 # Temperature coefficient, optional rossmodel: 0.0342 # Cooling type [Ross Model], Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional`} /> + interval: 1h # Interval, optional`} /> @@ -781,16 +781,16 @@ Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) acc solar: - type: template template: solcast - site: # ressource ID of your site - token: # Solcast API Token`} advanced={`tariffs: + site: # Ressource ID of your site + token: # API Token`} advanced={`tariffs: solar: - type: template template: solcast - site: # ressource ID of your site - token: # Solcast API Token - from: # Start time of data retrieval, specified in full hours, e.g. "6" (optional) - to: # End time of data retrieval, specified in full hours, e.g. "20" (optional) - interval: 3h # optional`} /> + site: # Ressource ID of your site + token: # API Token + from: # Start time, Start time of data retrieval, specified in full hours, e.g. "6" (optional) + to: # End time, End time of data retrieval, specified in full hours, e.g. "20" (optional) + interval: 3h # Interval, optional`} /> @@ -813,7 +813,7 @@ Requires a [solcast.com](https://solcast.com/free-rooftop-solar-forecasting) acc template: victron idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" token: # API access token, Tokens can be created in VRM in Preferences->Integrations - interval: 1h # optional`} /> + interval: 1h # Interval, optional`} /> diff --git a/package-lock.json b/package-lock.json index 1d4f7bdc8d..36292fa362 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,7 +13,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.9", + "@evcc/icons": "^0.5.11", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -4523,9 +4523,9 @@ } }, "node_modules/@evcc/icons": { - "version": "0.5.9", - "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.9.tgz", - "integrity": "sha512-c9Hof95fxDo/QaygRhpnZURw1l2E7GeD8thKvf7mKW6goDZSubIP6sb7WeSY1Uq5I4AW0XbYH6LTZej66PSd3w==", + "version": "0.5.11", + "resolved": "https://registry.npmjs.org/@evcc/icons/-/icons-0.5.11.tgz", + "integrity": "sha512-4BgmUtaRtN/vWf15tKr+arffGZqSYk1xSQf1xKI64rHMfBedb4b/nTnvBwyS/2dfpcULmNIWoqYPl1rcPKCwqQ==", "license": "CC-BY-NC-SA-4.0", "dependencies": { "fuse.js": "^7.1.0" diff --git a/package.json b/package.json index c848da67d9..d23e99ee12 100644 --- a/package.json +++ b/package.json @@ -26,7 +26,7 @@ "@docusaurus/plugin-client-redirects": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@docusaurus/theme-search-algolia": "^3.7.0", - "@evcc/icons": "^0.5.9", + "@evcc/icons": "^0.5.11", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", diff --git a/src/css/custom.css b/src/css/custom.css index 75a3b6f390..4c5a47050b 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -160,3 +160,45 @@ table th { text-align: left; vertical-align: top; } + +/* Device Detail Styles */ +.device-detail-container { + display: flex; + gap: 2rem; + align-items: flex-start; + margin-bottom: 2rem; +} + +.device-detail-content { + flex: 1; + min-width: 0; /* Prevents flex item from overflowing */ +} + +.device-detail-icon { + flex: 0 0 400px; + display: flex; + justify-content: center; +} + +.device-detail-icon-img { + width: 400px; + height: auto; +} + +@media (max-width: 768px) { + .device-detail-container { + flex-direction: column; + } + + .device-detail-icon { + flex: 0 0 auto; + width: 100%; + max-width: 400px; + margin: 0 auto; + } + + .device-detail-icon-img { + width: 100%; + height: auto; + } +} diff --git a/src/generateDevicesNext.ts b/src/generateDevicesNext.ts index 36d385fbaa..219a06a379 100644 --- a/src/generateDevicesNext.ts +++ b/src/generateDevicesNext.ts @@ -261,12 +261,7 @@ ${cards }; const escapeMarkdown = (text: string): string => { - return text - .replace(//g, ">") - .replace(/\|/g, "\\|") - .replace(/\[/g, "\\[") - .replace(/\]/g, "\\]"); + return text.replace(/\|/g, "\\|").replace(/\[/g, "\\[").replace(/\]/g, "\\]"); }; const getParameterTable = ( @@ -448,10 +443,24 @@ import DeviceFeatures from '@site/src/components/DeviceFeatures'; import SponsorshipRequired from '/docs/_sponsorship_required.mdx'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import '@evcc/icons'; # ${title} -${deviceFeatures}${longDescription ? longDescription + "\n\n" : ""}${codeSection} +
+
+ ${deviceFeatures}${longDescription ? longDescription + "\n\n" : ""}${codeSection} +
+
+ +
+
${parameterTable ? parameterTable + "\n\n" : ""}${sponsor}`; }; diff --git a/templates/release/de/charger/abb-terra-ac-ocpp.yaml b/templates/release/de/charger/abb-terra-ac-ocpp.yaml index d6421baa6e..602477d9b9 100644 --- a/templates/release/de/charger/abb-terra-ac-ocpp.yaml +++ b/templates/release/de/charger/abb-terra-ac-ocpp.yaml @@ -11,17 +11,17 @@ render: - default: | type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -29,7 +29,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -46,8 +46,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -55,8 +55,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -64,8 +64,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -73,8 +73,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abb-terra-ac.yaml b/templates/release/de/charger/abb-terra-ac.yaml index 0b8c1198bc..381783931f 100644 --- a/templates/release/de/charger/abb-terra-ac.yaml +++ b/templates/release/de/charger/abb-terra-ac.yaml @@ -36,7 +36,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/abl-em4-single-ocpp.yaml b/templates/release/de/charger/abl-em4-single-ocpp.yaml index 0f8db48915..202b76005e 100644 --- a/templates/release/de/charger/abl-em4-single-ocpp.yaml +++ b/templates/release/de/charger/abl-em4-single-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-em4-single-sbcx.yaml b/templates/release/de/charger/abl-em4-single-sbcx.yaml index 72d5a56e1e..d048ff07c2 100644 --- a/templates/release/de/charger/abl-em4-single-sbcx.yaml +++ b/templates/release/de/charger/abl-em4-single-sbcx.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/abl-em4-twin-ocpp.yaml b/templates/release/de/charger/abl-em4-twin-ocpp.yaml index fbee674238..98123d8355 100644 --- a/templates/release/de/charger/abl-em4-twin-ocpp.yaml +++ b/templates/release/de/charger/abl-em4-twin-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-em4-twin-sbcx.yaml b/templates/release/de/charger/abl-em4-twin-sbcx.yaml index 42c3303621..18ca90ea78 100644 --- a/templates/release/de/charger/abl-em4-twin-sbcx.yaml +++ b/templates/release/de/charger/abl-em4-twin-sbcx.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/abl-emh1.yaml b/templates/release/de/charger/abl-emh1.yaml index 9cbb582bfe..a043baad3d 100644 --- a/templates/release/de/charger/abl-emh1.yaml +++ b/templates/release/de/charger/abl-emh1.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/abl-emh2-ocpp.yaml b/templates/release/de/charger/abl-emh2-ocpp.yaml index bac10760a4..42ffa15785 100644 --- a/templates/release/de/charger/abl-emh2-ocpp.yaml +++ b/templates/release/de/charger/abl-emh2-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/abl-emh2.yaml b/templates/release/de/charger/abl-emh2.yaml index 55ad16e372..07d7cb3840 100644 --- a/templates/release/de/charger/abl-emh2.yaml +++ b/templates/release/de/charger/abl-emh2.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/abl-emh3-ocpp.yaml b/templates/release/de/charger/abl-emh3-ocpp.yaml index 3c69c83b73..5684f91464 100644 --- a/templates/release/de/charger/abl-emh3-ocpp.yaml +++ b/templates/release/de/charger/abl-emh3-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/alfen-eve-ocpp.yaml b/templates/release/de/charger/alfen-eve-ocpp.yaml index 173d4e72fb..904ee1f451 100644 --- a/templates/release/de/charger/alfen-eve-ocpp.yaml +++ b/templates/release/de/charger/alfen-eve-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/alfen-eve.yaml b/templates/release/de/charger/alfen-eve.yaml index e54c4d0a05..a2d42f98c2 100644 --- a/templates/release/de/charger/alfen-eve.yaml +++ b/templates/release/de/charger/alfen-eve.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/alpha-innotec.yaml b/templates/release/de/charger/alpha-innotec.yaml index f16d018d86..d9dd3942f8 100644 --- a/templates/release/de/charger/alpha-innotec.yaml +++ b/templates/release/de/charger/alpha-innotec.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -25,15 +25,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -42,8 +42,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -51,8 +51,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/alphatec-ladesaule-twin.yaml b/templates/release/de/charger/alphatec-ladesaule-twin.yaml index 37a36d85c3..518aa009f2 100644 --- a/templates/release/de/charger/alphatec-ladesaule-twin.yaml +++ b/templates/release/de/charger/alphatec-ladesaule-twin.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/alphatec-wallbox-mini.yaml b/templates/release/de/charger/alphatec-wallbox-mini.yaml index ab7f35f86c..5e8d5c6136 100644 --- a/templates/release/de/charger/alphatec-wallbox-mini.yaml +++ b/templates/release/de/charger/alphatec-wallbox-mini.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/alphatec-wallbox-power.yaml b/templates/release/de/charger/alphatec-wallbox-power.yaml index 698c648197..46b124e318 100644 --- a/templates/release/de/charger/alphatec-wallbox-power.yaml +++ b/templates/release/de/charger/alphatec-wallbox-power.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/amperfied-wallbox-connect-business.yaml b/templates/release/de/charger/amperfied-wallbox-connect-business.yaml index 9aa1661f93..ac680333a6 100644 --- a/templates/release/de/charger/amperfied-wallbox-connect-business.yaml +++ b/templates/release/de/charger/amperfied-wallbox-connect-business.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/amperfied-wallbox-connect-home.yaml b/templates/release/de/charger/amperfied-wallbox-connect-home.yaml index 31f18ff3e1..1257080b93 100644 --- a/templates/release/de/charger/amperfied-wallbox-connect-home.yaml +++ b/templates/release/de/charger/amperfied-wallbox-connect-home.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/amperfied-wallbox-connect-solar.yaml b/templates/release/de/charger/amperfied-wallbox-connect-solar.yaml index 976171a73b..432df8690f 100644 --- a/templates/release/de/charger/amperfied-wallbox-connect-solar.yaml +++ b/templates/release/de/charger/amperfied-wallbox-connect-solar.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/amperfied-wallbox-energy-control.yaml b/templates/release/de/charger/amperfied-wallbox-energy-control.yaml index e662f751f4..a2a2ddbb2f 100644 --- a/templates/release/de/charger/amperfied-wallbox-energy-control.yaml +++ b/templates/release/de/charger/amperfied-wallbox-energy-control.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/ampure-unite.yaml b/templates/release/de/charger/ampure-unite.yaml index 5fc3a05171..70bb45cd67 100644 --- a/templates/release/de/charger/ampure-unite.yaml +++ b/templates/release/de/charger/ampure-unite.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/autel-ac-compact.yaml b/templates/release/de/charger/autel-ac-compact.yaml index 0fe6c585ba..cccb197829 100644 --- a/templates/release/de/charger/autel-ac-compact.yaml +++ b/templates/release/de/charger/autel-ac-compact.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/autel-ac-maxicharger.yaml b/templates/release/de/charger/autel-ac-maxicharger.yaml index ac5b6c262e..46c2289f07 100644 --- a/templates/release/de/charger/autel-ac-maxicharger.yaml +++ b/templates/release/de/charger/autel-ac-maxicharger.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/autoaid-business-wallbox.yaml b/templates/release/de/charger/autoaid-business-wallbox.yaml index 5c7444081f..aa094ab876 100644 --- a/templates/release/de/charger/autoaid-business-wallbox.yaml +++ b/templates/release/de/charger/autoaid-business-wallbox.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/autoaid-intelligent-wallbox.yaml b/templates/release/de/charger/autoaid-intelligent-wallbox.yaml index 0591622ba8..6410310b37 100644 --- a/templates/release/de/charger/autoaid-intelligent-wallbox.yaml +++ b/templates/release/de/charger/autoaid-intelligent-wallbox.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/bender-cc612.yaml b/templates/release/de/charger/bender-cc612.yaml index f0304a76ca..147ab2527b 100644 --- a/templates/release/de/charger/bender-cc612.yaml +++ b/templates/release/de/charger/bender-cc612.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/bender-cc613.yaml b/templates/release/de/charger/bender-cc613.yaml index 3a4642f9ae..9e57f070d2 100644 --- a/templates/release/de/charger/bender-cc613.yaml +++ b/templates/release/de/charger/bender-cc613.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/bender-icc1314.yaml b/templates/release/de/charger/bender-icc1314.yaml index 8eb9a1bd73..2690aef082 100644 --- a/templates/release/de/charger/bender-icc1314.yaml +++ b/templates/release/de/charger/bender-icc1314.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/bender-icc1324.yaml b/templates/release/de/charger/bender-icc1324.yaml index 091f7aa4c5..76b72a5541 100644 --- a/templates/release/de/charger/bender-icc1324.yaml +++ b/templates/release/de/charger/bender-icc1324.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/bmw-i-wallbox.yaml b/templates/release/de/charger/bmw-i-wallbox.yaml index f77abf8d8b..06bbd1e79c 100644 --- a/templates/release/de/charger/bmw-i-wallbox.yaml +++ b/templates/release/de/charger/bmw-i-wallbox.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/bosch-sg-ready.yaml b/templates/release/de/charger/bosch-sg-ready.yaml index 994ce5d8f4..031cebdd06 100644 --- a/templates/release/de/charger/bosch-sg-ready.yaml +++ b/templates/release/de/charger/bosch-sg-ready.yaml @@ -11,7 +11,7 @@ render: type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional) params: @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true diff --git a/templates/release/de/charger/bosch-x-change.yaml b/templates/release/de/charger/bosch-x-change.yaml index 287b92f1c4..1cddf2d75f 100644 --- a/templates/release/de/charger/bosch-x-change.yaml +++ b/templates/release/de/charger/bosch-x-change.yaml @@ -15,7 +15,7 @@ render: template: kermi host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -40,7 +40,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml b/templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml index 6cf5e1ae2e..a78a37256c 100644 --- a/templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml +++ b/templates/release/de/charger/buderus-logamatic-hmc-20-z.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/buderus-logamatic-hmc-20.yaml b/templates/release/de/charger/buderus-logamatic-hmc-20.yaml index 09fc5b1f99..411823aea7 100644 --- a/templates/release/de/charger/buderus-logamatic-hmc-20.yaml +++ b/templates/release/de/charger/buderus-logamatic-hmc-20.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/buderus-sg-ready.yaml b/templates/release/de/charger/buderus-sg-ready.yaml index 5d2dceb14c..e23e2b6518 100644 --- a/templates/release/de/charger/buderus-sg-ready.yaml +++ b/templates/release/de/charger/buderus-sg-ready.yaml @@ -11,7 +11,7 @@ render: type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional) params: @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true diff --git a/templates/release/de/charger/charge-amps-halo.yaml b/templates/release/de/charger/charge-amps-halo.yaml index a3e7810c65..2b5c8cc7eb 100644 --- a/templates/release/de/charger/charge-amps-halo.yaml +++ b/templates/release/de/charger/charge-amps-halo.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/compleo-ebox.yaml b/templates/release/de/charger/compleo-ebox.yaml index 7f5a029899..7c42c83ad6 100644 --- a/templates/release/de/charger/compleo-ebox.yaml +++ b/templates/release/de/charger/compleo-ebox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/cta-all-in-one-aeroplus.yaml b/templates/release/de/charger/cta-all-in-one-aeroplus.yaml index e4cc9a92fc..d0857a9d4a 100644 --- a/templates/release/de/charger/cta-all-in-one-aeroplus.yaml +++ b/templates/release/de/charger/cta-all-in-one-aeroplus.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/cubos-c11e.yaml b/templates/release/de/charger/cubos-c11e.yaml index 5385bf6ef6..6c2c11de6b 100644 --- a/templates/release/de/charger/cubos-c11e.yaml +++ b/templates/release/de/charger/cubos-c11e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/cubos-c22e.yaml b/templates/release/de/charger/cubos-c22e.yaml index f013af38a8..4f1c2cf82c 100644 --- a/templates/release/de/charger/cubos-c22e.yaml +++ b/templates/release/de/charger/cubos-c22e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/dadapower-premium-wallbox.yaml b/templates/release/de/charger/dadapower-premium-wallbox.yaml index 8774b672ed..ca29f52767 100644 --- a/templates/release/de/charger/dadapower-premium-wallbox.yaml +++ b/templates/release/de/charger/dadapower-premium-wallbox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/daikin-homehub-sg-ready.yaml b/templates/release/de/charger/daikin-homehub-sg-ready.yaml index 1c9b1fa49d..ca3ce7dfb0 100644 --- a/templates/release/de/charger/daikin-homehub-sg-ready.yaml +++ b/templates/release/de/charger/daikin-homehub-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/delta-ac-max-basic.yaml b/templates/release/de/charger/delta-ac-max-basic.yaml index d9a320d592..8ffd1c5409 100644 --- a/templates/release/de/charger/delta-ac-max-basic.yaml +++ b/templates/release/de/charger/delta-ac-max-basic.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/delta-ac-max-smart.yaml b/templates/release/de/charger/delta-ac-max-smart.yaml index 3e0118be87..8193f11c5d 100644 --- a/templates/release/de/charger/delta-ac-max-smart.yaml +++ b/templates/release/de/charger/delta-ac-max-smart.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/delta-slim-charger.yaml b/templates/release/de/charger/delta-slim-charger.yaml index ad0564c181..58925a414a 100644 --- a/templates/release/de/charger/delta-slim-charger.yaml +++ b/templates/release/de/charger/delta-slim-charger.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/delta-ultra-fast-charger.yaml b/templates/release/de/charger/delta-ultra-fast-charger.yaml index 1d195f6d7e..c76440831e 100644 --- a/templates/release/de/charger/delta-ultra-fast-charger.yaml +++ b/templates/release/de/charger/delta-ultra-fast-charger.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/e-on-drive-ebox.yaml b/templates/release/de/charger/e-on-drive-ebox.yaml index 932f0f1f8c..e7d33aeb20 100644 --- a/templates/release/de/charger/e-on-drive-ebox.yaml +++ b/templates/release/de/charger/e-on-drive-ebox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/e-on-drive-vbox.yaml b/templates/release/de/charger/e-on-drive-vbox.yaml index 0274136030..e9b4148a6a 100644 --- a/templates/release/de/charger/e-on-drive-vbox.yaml +++ b/templates/release/de/charger/e-on-drive-vbox.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/e3-dc-easy-connect.yaml b/templates/release/de/charger/e3-dc-easy-connect.yaml index 27587a0abf..fc14b99386 100644 --- a/templates/release/de/charger/e3-dc-easy-connect.yaml +++ b/templates/release/de/charger/e3-dc-easy-connect.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/easee-charge-core.yaml b/templates/release/de/charger/easee-charge-core.yaml index cf8be6d548..bbae3333d0 100644 --- a/templates/release/de/charger/easee-charge-core.yaml +++ b/templates/release/de/charger/easee-charge-core.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger Seriennummer help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentifizierung aktiviert help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/charger/easee-charge-lite.yaml b/templates/release/de/charger/easee-charge-lite.yaml index 5dee53c0d6..510d76907f 100644 --- a/templates/release/de/charger/easee-charge-lite.yaml +++ b/templates/release/de/charger/easee-charge-lite.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger Seriennummer help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentifizierung aktiviert help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/charger/easee-charge.yaml b/templates/release/de/charger/easee-charge.yaml index 74fd3a0f57..1c9dfef81b 100644 --- a/templates/release/de/charger/easee-charge.yaml +++ b/templates/release/de/charger/easee-charge.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger Seriennummer help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentifizierung aktiviert help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/charger/easee-home.yaml b/templates/release/de/charger/easee-home.yaml index f5effefe3e..9f0cc8d18a 100644 --- a/templates/release/de/charger/easee-home.yaml +++ b/templates/release/de/charger/easee-home.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Benutzerkonto, Emailadresse password: # Passwort, wie Login für Easee App oder Web Portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger Seriennummer timeout: 20s # Zeitüberschreitung, Spezifisches Timeout für Easee API Interaktionen. Kann Warnungen und Fehler bei träger Easee API reduzieren. (optional) - authorize: # Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) + authorize: # Authentifizierung aktiviert, Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger Seriennummer help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentifizierung aktiviert help: Steuert ob evcc die Authentifizierung am Charger vornimmt. Vorteil ist ein kontrollierter Ladestart. Nicht kompatibel mit RFID Identifikation von Fahrzeugen. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/charger/ebee-wallbox.yaml b/templates/release/de/charger/ebee-wallbox.yaml index 75fb55c6a5..5096c31074 100644 --- a/templates/release/de/charger/ebee-wallbox.yaml +++ b/templates/release/de/charger/ebee-wallbox.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml b/templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml index d648bddcec..84f82d1c90 100644 --- a/templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml +++ b/templates/release/de/charger/ecoharmony-evse-epc-2-0-plus.yaml @@ -32,7 +32,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/edgetech-smart-evse.yaml b/templates/release/de/charger/edgetech-smart-evse.yaml index c34cb02e76..494ecfff60 100644 --- a/templates/release/de/charger/edgetech-smart-evse.yaml +++ b/templates/release/de/charger/edgetech-smart-evse.yaml @@ -27,7 +27,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/elco.yaml b/templates/release/de/charger/elco.yaml index 444c4c2cb8..91dc50e629 100644 --- a/templates/release/de/charger/elco.yaml +++ b/templates/release/de/charger/elco.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -25,15 +25,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -42,8 +42,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -51,8 +51,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/elecq-biz.yaml b/templates/release/de/charger/elecq-biz.yaml index 3f6374d69c..2ce79aaba2 100644 --- a/templates/release/de/charger/elecq-biz.yaml +++ b/templates/release/de/charger/elecq-biz.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elecq-home.yaml b/templates/release/de/charger/elecq-home.yaml index 7d0758639e..f8a6430183 100644 --- a/templates/release/de/charger/elecq-home.yaml +++ b/templates/release/de/charger/elecq-home.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/elecq-station.yaml b/templates/release/de/charger/elecq-station.yaml index 1f457969c3..942e647193 100644 --- a/templates/release/de/charger/elecq-station.yaml +++ b/templates/release/de/charger/elecq-station.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/eledio-go.yaml b/templates/release/de/charger/eledio-go.yaml index c4228fe64c..f5e8dc999c 100644 --- a/templates/release/de/charger/eledio-go.yaml +++ b/templates/release/de/charger/eledio-go.yaml @@ -12,17 +12,17 @@ render: - default: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -30,7 +30,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -47,8 +47,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -56,8 +56,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -65,8 +65,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -74,8 +74,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -83,7 +83,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml b/templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml index c54734b7d4..532cffcb96 100644 --- a/templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml +++ b/templates/release/de/charger/em2go-pro-power-ocpp-onc.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/enercab-smart.yaml b/templates/release/de/charger/enercab-smart.yaml index fe17dd8dbf..802a3b6eae 100644 --- a/templates/release/de/charger/enercab-smart.yaml +++ b/templates/release/de/charger/enercab-smart.yaml @@ -12,17 +12,17 @@ render: - default: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -30,7 +30,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -47,8 +47,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -56,8 +56,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -65,8 +65,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -74,8 +74,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -83,7 +83,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/enplus-ac-ev-charger.yaml b/templates/release/de/charger/enplus-ac-ev-charger.yaml index 9081985c40..c780d02c0f 100644 --- a/templates/release/de/charger/enplus-ac-ev-charger.yaml +++ b/templates/release/de/charger/enplus-ac-ev-charger.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/ensto-chago-wallbox.yaml b/templates/release/de/charger/ensto-chago-wallbox.yaml index 8a1f54f289..6d3abd7099 100644 --- a/templates/release/de/charger/ensto-chago-wallbox.yaml +++ b/templates/release/de/charger/ensto-chago-wallbox.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/entratek-power-dot-fix.yaml b/templates/release/de/charger/entratek-power-dot-fix.yaml index f39b93530f..8e27ebac18 100644 --- a/templates/release/de/charger/entratek-power-dot-fix.yaml +++ b/templates/release/de/charger/entratek-power-dot-fix.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/entratek-power-dot-pro-2.yaml b/templates/release/de/charger/entratek-power-dot-pro-2.yaml index 9fdf5c0145..956aa3c2cd 100644 --- a/templates/release/de/charger/entratek-power-dot-pro-2.yaml +++ b/templates/release/de/charger/entratek-power-dot-pro-2.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/esl-walli-light.yaml b/templates/release/de/charger/esl-walli-light.yaml index 1740917849..dfab438319 100644 --- a/templates/release/de/charger/esl-walli-light.yaml +++ b/templates/release/de/charger/esl-walli-light.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/evbox-elvi.yaml b/templates/release/de/charger/evbox-elvi.yaml index 1dd629924a..42cd7deca6 100644 --- a/templates/release/de/charger/evbox-elvi.yaml +++ b/templates/release/de/charger/evbox-elvi.yaml @@ -8,18 +8,18 @@ render: - default: | type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # Zählernummer, optional advanced: | type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + meter: true # Zählernummer, optional connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: meter @@ -35,7 +35,7 @@ params: default: true choice: [] unit: - description: + description: Zählernummer help: advanced: false optional: true @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -62,8 +62,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -71,8 +71,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/evse-din.yaml b/templates/release/de/charger/evse-din.yaml index 782107d0b0..acb1a1ea2c 100644 --- a/templates/release/de/charger/evse-din.yaml +++ b/templates/release/de/charger/evse-din.yaml @@ -25,7 +25,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/free2move-eprowallbox-move.yaml b/templates/release/de/charger/free2move-eprowallbox-move.yaml index 1e8b314567..a7447b64e8 100644 --- a/templates/release/de/charger/free2move-eprowallbox-move.yaml +++ b/templates/release/de/charger/free2move-eprowallbox-move.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/free2move-eprowallbox.yaml b/templates/release/de/charger/free2move-eprowallbox.yaml index 095c5fd108..e18da4f2bd 100644 --- a/templates/release/de/charger/free2move-eprowallbox.yaml +++ b/templates/release/de/charger/free2move-eprowallbox.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/free2move-esolutions-eprowallbox.yaml b/templates/release/de/charger/free2move-esolutions-eprowallbox.yaml index 9fea841975..4af801c3d2 100644 --- a/templates/release/de/charger/free2move-esolutions-eprowallbox.yaml +++ b/templates/release/de/charger/free2move-esolutions-eprowallbox.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/fronius-wattpilot-ocpp.yaml b/templates/release/de/charger/fronius-wattpilot-ocpp.yaml index 5d6fb3269f..52ed47f2d2 100644 --- a/templates/release/de/charger/fronius-wattpilot-ocpp.yaml +++ b/templates/release/de/charger/fronius-wattpilot-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/garo-glb.yaml b/templates/release/de/charger/garo-glb.yaml index 938216481a..3251c024fc 100644 --- a/templates/release/de/charger/garo-glb.yaml +++ b/templates/release/de/charger/garo-glb.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/garo-glbplus.yaml b/templates/release/de/charger/garo-glbplus.yaml index ff88b3dc4d..10a5b62b35 100644 --- a/templates/release/de/charger/garo-glbplus.yaml +++ b/templates/release/de/charger/garo-glbplus.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/garo-ls4-compact.yaml b/templates/release/de/charger/garo-ls4-compact.yaml index 811930c681..e86d44d9a5 100644 --- a/templates/release/de/charger/garo-ls4-compact.yaml +++ b/templates/release/de/charger/garo-ls4-compact.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/garo-ls4.yaml b/templates/release/de/charger/garo-ls4.yaml index 3fe2f24b1c..0aa1bce998 100644 --- a/templates/release/de/charger/garo-ls4.yaml +++ b/templates/release/de/charger/garo-ls4.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/go-e-charger-gemini-ocpp.yaml b/templates/release/de/charger/go-e-charger-gemini-ocpp.yaml index 8de4b0744c..2bbdf98800 100644 --- a/templates/release/de/charger/go-e-charger-gemini-ocpp.yaml +++ b/templates/release/de/charger/go-e-charger-gemini-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-pro-ocpp.yaml b/templates/release/de/charger/go-e-charger-pro-ocpp.yaml index 01cd4a4e3f..b9e7e38211 100644 --- a/templates/release/de/charger/go-e-charger-pro-ocpp.yaml +++ b/templates/release/de/charger/go-e-charger-pro-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/go-e-charger-v3-ocpp.yaml b/templates/release/de/charger/go-e-charger-v3-ocpp.yaml index e3f5223cb0..abdd58e7a0 100644 --- a/templates/release/de/charger/go-e-charger-v3-ocpp.yaml +++ b/templates/release/de/charger/go-e-charger-v3-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/heidelberg-energy-control.yaml b/templates/release/de/charger/heidelberg-energy-control.yaml index fad2544155..fa52c14563 100644 --- a/templates/release/de/charger/heidelberg-energy-control.yaml +++ b/templates/release/de/charger/heidelberg-energy-control.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/hesotec-ebox.yaml b/templates/release/de/charger/hesotec-ebox.yaml index 5c80164d4a..3d46beed9b 100644 --- a/templates/release/de/charger/hesotec-ebox.yaml +++ b/templates/release/de/charger/hesotec-ebox.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/hesotec-esat.yaml b/templates/release/de/charger/hesotec-esat.yaml index 4c93f63fa0..e218deeea9 100644 --- a/templates/release/de/charger/hesotec-esat.yaml +++ b/templates/release/de/charger/hesotec-esat.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/homecharge-homecharger.yaml b/templates/release/de/charger/homecharge-homecharger.yaml index 51de9dd475..b37be6f287 100644 --- a/templates/release/de/charger/homecharge-homecharger.yaml +++ b/templates/release/de/charger/homecharge-homecharger.yaml @@ -13,17 +13,17 @@ render: - default: | type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -31,7 +31,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -48,8 +48,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -57,8 +57,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -66,8 +66,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -75,8 +75,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -84,7 +84,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/homematic-ip.yaml b/templates/release/de/charger/homematic-ip.yaml index d43f79e31e..7596cba277 100644 --- a/templates/release/de/charger/homematic-ip.yaml +++ b/templates/release/de/charger/homematic-ip.yaml @@ -8,7 +8,7 @@ render: type: template template: homematic host: 192.0.2.2 # IP-Adresse oder Hostname - port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC-Server Port-Nummer, optional device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) @@ -17,14 +17,14 @@ render: type: template template: homematic host: 192.0.2.2 # IP-Adresse oder Hostname - port: 2010 # XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC-Server Port-Nummer, optional device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) - meterchannel: 6 # Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. - switchchannel: 3 # Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + meterchannel: 6 # Kanalnummer des Power-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. + switchchannel: 3 # Kanalnummer der schaltbaren Steckdose, Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) icon: # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) @@ -39,11 +39,11 @@ params: advanced: false optional: false - name: port - example: + example: BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010 default: 2010 choice: [] unit: - description: XML-RPC-Server Port-Nummer (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010) + description: XML-RPC-Server Port-Nummer help: advanced: false optional: true @@ -84,20 +84,20 @@ params: advanced: false optional: true - name: meterchannel - example: + example: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2 default: 6 choice: [] unit: - description: Kanalnummer des Power-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2) + description: Kanalnummer des Power-Meters help: Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. advanced: true optional: false - name: switchchannel - example: + example: HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1 default: 3 choice: [] unit: - description: Kanalnummer der schaltbaren Steckdose (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1) + description: Kanalnummer der schaltbaren Steckdose help: Kanalnummer der schaltbaren Steckdose, wie im CCU Webfrontend angezeigt. advanced: true optional: false @@ -106,7 +106,7 @@ params: default: 1s choice: [] unit: - description: XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h) + description: XML-RPC API Cache Zeitraum help: Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. advanced: true optional: true diff --git a/templates/release/de/charger/huawei-scharger-22kt-s0.yaml b/templates/release/de/charger/huawei-scharger-22kt-s0.yaml index 7a398121f5..c8d08048ad 100644 --- a/templates/release/de/charger/huawei-scharger-22kt-s0.yaml +++ b/templates/release/de/charger/huawei-scharger-22kt-s0.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/huawei-scharger-7ks-s0.yaml b/templates/release/de/charger/huawei-scharger-7ks-s0.yaml index c74282da42..22081a66b4 100644 --- a/templates/release/de/charger/huawei-scharger-7ks-s0.yaml +++ b/templates/release/de/charger/huawei-scharger-7ks-s0.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/idm.yaml b/templates/release/de/charger/idm.yaml index 84517e70a3..44301dbd41 100644 --- a/templates/release/de/charger/idm.yaml +++ b/templates/release/de/charger/idm.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/innogy-ebox.yaml b/templates/release/de/charger/innogy-ebox.yaml index 4d8616ac7e..4366af96e0 100644 --- a/templates/release/de/charger/innogy-ebox.yaml +++ b/templates/release/de/charger/innogy-ebox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/juice-charger-me.yaml b/templates/release/de/charger/juice-charger-me.yaml index 9e16e437c0..1fc49c15df 100644 --- a/templates/release/de/charger/juice-charger-me.yaml +++ b/templates/release/de/charger/juice-charger-me.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/junkers-sg-ready.yaml b/templates/release/de/charger/junkers-sg-ready.yaml index 7dba7ecbb0..0babf196b1 100644 --- a/templates/release/de/charger/junkers-sg-ready.yaml +++ b/templates/release/de/charger/junkers-sg-ready.yaml @@ -11,7 +11,7 @@ render: type: template template: emsesp host: 192.0.2.2 # IP-Adresse oder Hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Leistungsquelle, [hpcurrpower, hppower] (optional) tempsource: # Temperaturquelle, [warmwater] (optional) params: @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true diff --git a/templates/release/de/charger/kathrein-kwb-ac20.yaml b/templates/release/de/charger/kathrein-kwb-ac20.yaml index 4eb68796f2..f09a4ca55c 100644 --- a/templates/release/de/charger/kathrein-kwb-ac20.yaml +++ b/templates/release/de/charger/kathrein-kwb-ac20.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/kathrein-kwb-ac35.yaml b/templates/release/de/charger/kathrein-kwb-ac35.yaml index 7d102a6ec0..6bf3f522e1 100644 --- a/templates/release/de/charger/kathrein-kwb-ac35.yaml +++ b/templates/release/de/charger/kathrein-kwb-ac35.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/kathrein-kwb-ac40-e.yaml b/templates/release/de/charger/kathrein-kwb-ac40-e.yaml index a711193f79..eb8e771f37 100644 --- a/templates/release/de/charger/kathrein-kwb-ac40-e.yaml +++ b/templates/release/de/charger/kathrein-kwb-ac40-e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/kathrein-kwb-ac40.yaml b/templates/release/de/charger/kathrein-kwb-ac40.yaml index b1472a0e4b..6944a07975 100644 --- a/templates/release/de/charger/kathrein-kwb-ac40.yaml +++ b/templates/release/de/charger/kathrein-kwb-ac40.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/kathrein-kwb-ac60-e.yaml b/templates/release/de/charger/kathrein-kwb-ac60-e.yaml index 5bdab9c459..7cc011e1cf 100644 --- a/templates/release/de/charger/kathrein-kwb-ac60-e.yaml +++ b/templates/release/de/charger/kathrein-kwb-ac60-e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/kathrein-kwb-ac60.yaml b/templates/release/de/charger/kathrein-kwb-ac60.yaml index 264c841887..4319e5798a 100644 --- a/templates/release/de/charger/kathrein-kwb-ac60.yaml +++ b/templates/release/de/charger/kathrein-kwb-ac60.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/keba-kecontact-p20.yaml b/templates/release/de/charger/keba-kecontact-p20.yaml index dac7ec1e2c..b95eb21203 100644 --- a/templates/release/de/charger/keba-kecontact-p20.yaml +++ b/templates/release/de/charger/keba-kecontact-p20.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/keba-kecontact-p30-c-series.yaml b/templates/release/de/charger/keba-kecontact-p30-c-series.yaml index 5a91b2cfe0..1aff489a7f 100644 --- a/templates/release/de/charger/keba-kecontact-p30-c-series.yaml +++ b/templates/release/de/charger/keba-kecontact-p30-c-series.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/keba-kecontact-p30-x-series.yaml b/templates/release/de/charger/keba-kecontact-p30-x-series.yaml index 032fbb8696..812319b57c 100644 --- a/templates/release/de/charger/keba-kecontact-p30-x-series.yaml +++ b/templates/release/de/charger/keba-kecontact-p30-x-series.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/keba-kecontact-p40-pro.yaml b/templates/release/de/charger/keba-kecontact-p40-pro.yaml index 0caa3a1854..99447e6951 100644 --- a/templates/release/de/charger/keba-kecontact-p40-pro.yaml +++ b/templates/release/de/charger/keba-kecontact-p40-pro.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/keba-kecontact-p40.yaml b/templates/release/de/charger/keba-kecontact-p40.yaml index ba9b925817..cfc0d51c66 100644 --- a/templates/release/de/charger/keba-kecontact-p40.yaml +++ b/templates/release/de/charger/keba-kecontact-p40.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/kermi-x-center-pro.yaml b/templates/release/de/charger/kermi-x-center-pro.yaml index 7fd350fa4a..e8cf13a616 100644 --- a/templates/release/de/charger/kermi-x-center-pro.yaml +++ b/templates/release/de/charger/kermi-x-center-pro.yaml @@ -15,7 +15,7 @@ render: template: kermi host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater, buffer] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -40,7 +40,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/kostal-enector.yaml b/templates/release/de/charger/kostal-enector.yaml index 2d6f648e29..a0d02ec476 100644 --- a/templates/release/de/charger/kostal-enector.yaml +++ b/templates/release/de/charger/kostal-enector.yaml @@ -33,7 +33,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/kse-wbx16.yaml b/templates/release/de/charger/kse-wbx16.yaml index c562f20efd..5286620cf3 100644 --- a/templates/release/de/charger/kse-wbx16.yaml +++ b/templates/release/de/charger/kse-wbx16.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/ladefoxx-evload.yaml b/templates/release/de/charger/ladefoxx-evload.yaml index 3b0b965d16..753046e24a 100644 --- a/templates/release/de/charger/ladefoxx-evload.yaml +++ b/templates/release/de/charger/ladefoxx-evload.yaml @@ -29,7 +29,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/ladefoxx-mikro-2-0.yaml b/templates/release/de/charger/ladefoxx-mikro-2-0.yaml index 3011b371d1..e161e8d2d3 100644 --- a/templates/release/de/charger/ladefoxx-mikro-2-0.yaml +++ b/templates/release/de/charger/ladefoxx-mikro-2-0.yaml @@ -29,7 +29,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/lambda-eu-l-series.yaml b/templates/release/de/charger/lambda-eu-l-series.yaml index 7125ef40bd..2ee8b9bab1 100644 --- a/templates/release/de/charger/lambda-eu-l-series.yaml +++ b/templates/release/de/charger/lambda-eu-l-series.yaml @@ -21,7 +21,7 @@ render: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -46,7 +46,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/lrt-home-essentialplus.yaml b/templates/release/de/charger/lrt-home-essentialplus.yaml index f5e9070c68..73664d03f8 100644 --- a/templates/release/de/charger/lrt-home-essentialplus.yaml +++ b/templates/release/de/charger/lrt-home-essentialplus.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amedio-professional.yaml b/templates/release/de/charger/mennekes-amedio-professional.yaml index 7b066198f6..50e5e22152 100644 --- a/templates/release/de/charger/mennekes-amedio-professional.yaml +++ b/templates/release/de/charger/mennekes-amedio-professional.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-4business-700.yaml b/templates/release/de/charger/mennekes-amtron-4business-700.yaml index 2045673b14..7843df784e 100644 --- a/templates/release/de/charger/mennekes-amtron-4business-700.yaml +++ b/templates/release/de/charger/mennekes-amtron-4business-700.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-4you-300.yaml b/templates/release/de/charger/mennekes-amtron-4you-300.yaml index abadbdcdec..a10df23eed 100644 --- a/templates/release/de/charger/mennekes-amtron-4you-300.yaml +++ b/templates/release/de/charger/mennekes-amtron-4you-300.yaml @@ -33,7 +33,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-4you-500.yaml b/templates/release/de/charger/mennekes-amtron-4you-500.yaml index d0bb2c5f69..c9d2989380 100644 --- a/templates/release/de/charger/mennekes-amtron-4you-500.yaml +++ b/templates/release/de/charger/mennekes-amtron-4you-500.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-chargecontrol.yaml b/templates/release/de/charger/mennekes-amtron-chargecontrol.yaml index 23e1751dd7..e8839e79c7 100644 --- a/templates/release/de/charger/mennekes-amtron-chargecontrol.yaml +++ b/templates/release/de/charger/mennekes-amtron-chargecontrol.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml b/templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml index 09a0bbe1c4..a35fbca50e 100644 --- a/templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml +++ b/templates/release/de/charger/mennekes-amtron-compact-2-0s.yaml @@ -33,7 +33,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-premium.yaml b/templates/release/de/charger/mennekes-amtron-premium.yaml index 4d919d93dc..6adf8faa37 100644 --- a/templates/release/de/charger/mennekes-amtron-premium.yaml +++ b/templates/release/de/charger/mennekes-amtron-premium.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-professional.yaml b/templates/release/de/charger/mennekes-amtron-professional.yaml index 98b6e2589b..8265dbae50 100644 --- a/templates/release/de/charger/mennekes-amtron-professional.yaml +++ b/templates/release/de/charger/mennekes-amtron-professional.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-amtron-xtra.yaml b/templates/release/de/charger/mennekes-amtron-xtra.yaml index 1669a80f46..c0100ac098 100644 --- a/templates/release/de/charger/mennekes-amtron-xtra.yaml +++ b/templates/release/de/charger/mennekes-amtron-xtra.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/mennekes-emobility-gateway-acu.yaml b/templates/release/de/charger/mennekes-emobility-gateway-acu.yaml index 2e48c11733..293e590fa3 100644 --- a/templates/release/de/charger/mennekes-emobility-gateway-acu.yaml +++ b/templates/release/de/charger/mennekes-emobility-gateway-acu.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-smart-acu.yaml b/templates/release/de/charger/mennekes-smart-acu.yaml index fa120f0afa..9f1bbef54d 100644 --- a/templates/release/de/charger/mennekes-smart-acu.yaml +++ b/templates/release/de/charger/mennekes-smart-acu.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/mennekes-smart-t-acu.yaml b/templates/release/de/charger/mennekes-smart-t-acu.yaml index d36c94dbea..1e1f2435b6 100644 --- a/templates/release/de/charger/mennekes-smart-t-acu.yaml +++ b/templates/release/de/charger/mennekes-smart-t-acu.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/my-pv-ac-elwa-2.yaml b/templates/release/de/charger/my-pv-ac-elwa-2.yaml index 32472270e8..4e60b584ed 100644 --- a/templates/release/de/charger/my-pv-ac-elwa-2.yaml +++ b/templates/release/de/charger/my-pv-ac-elwa-2.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/my-pv-ac-thor-9s.yaml b/templates/release/de/charger/my-pv-ac-thor-9s.yaml index be309fb33c..df54388a9a 100644 --- a/templates/release/de/charger/my-pv-ac-thor-9s.yaml +++ b/templates/release/de/charger/my-pv-ac-thor-9s.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + tempsource: 1 # Temperaturquelle, [1, 2, 3] (optional) scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional params: - name: modbus @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -32,7 +32,7 @@ params: default: 1 choice: ['1', '2', '3'] unit: - description: Temperatursensor + description: Temperaturquelle help: advanced: false optional: true diff --git a/templates/release/de/charger/my-pv-ac-thor.yaml b/templates/release/de/charger/my-pv-ac-thor.yaml index a5a0b93f43..07aeb0f87d 100644 --- a/templates/release/de/charger/my-pv-ac-thor.yaml +++ b/templates/release/de/charger/my-pv-ac-thor.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperatursensor, [1, 2, 3] (optional) + tempsource: 1 # Temperaturquelle, [1, 2, 3] (optional) scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional params: - name: modbus @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -32,7 +32,7 @@ params: default: 1 choice: ['1', '2', '3'] unit: - description: Temperatursensor + description: Temperaturquelle help: advanced: false optional: true diff --git a/templates/release/de/charger/nibe-ap-aw10.yaml b/templates/release/de/charger/nibe-ap-aw10.yaml index a82ed267da..d3763756b7 100644 --- a/templates/release/de/charger/nibe-ap-aw10.yaml +++ b/templates/release/de/charger/nibe-ap-aw10.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/novelan-wpr-net.yaml b/templates/release/de/charger/novelan-wpr-net.yaml index d87c82753d..d043653a61 100644 --- a/templates/release/de/charger/novelan-wpr-net.yaml +++ b/templates/release/de/charger/novelan-wpr-net.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/nrgkick-connect.yaml b/templates/release/de/charger/nrgkick-connect.yaml index a0e682ef62..711542acbe 100644 --- a/templates/release/de/charger/nrgkick-connect.yaml +++ b/templates/release/de/charger/nrgkick-connect.yaml @@ -10,7 +10,7 @@ render: type: template template: nrgkick-connect host: 192.0.2.2 # IP-Adresse oder Hostname - mac: + mac: # MAC Adresse password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen params: - name: host @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: MAC Adresse help: advanced: false optional: false diff --git a/templates/release/de/charger/nrgkick-gen2.yaml b/templates/release/de/charger/nrgkick-gen2.yaml index 994b3fa68b..370123be30 100644 --- a/templates/release/de/charger/nrgkick-gen2.yaml +++ b/templates/release/de/charger/nrgkick-gen2.yaml @@ -24,14 +24,14 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - phases1p3p: false # Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional) + phases1p3p: false # Phasenumschaltung aktiviert, Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -40,8 +40,8 @@ params: default: false choice: [] unit: - description: - help: Aktiviert Phasenumschaltung. Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. + description: Phasenumschaltung aktiviert + help: Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/obo-bettermann-ion.yaml b/templates/release/de/charger/obo-bettermann-ion.yaml index f0eb202144..42fb315b19 100644 --- a/templates/release/de/charger/obo-bettermann-ion.yaml +++ b/templates/release/de/charger/obo-bettermann-ion.yaml @@ -32,7 +32,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml b/templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml index fba46f8c63..1c864d0b83 100644 --- a/templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml +++ b/templates/release/de/charger/ocpp-1-6j-compatible-smart-charging.yaml @@ -30,17 +30,17 @@ render: - default: | type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -48,7 +48,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -65,8 +65,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -74,8 +74,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -83,8 +83,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -92,8 +92,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -101,7 +101,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/openwb-software-2-x.yaml b/templates/release/de/charger/openwb-software-2-x.yaml index c803661461..eec3b608c8 100644 --- a/templates/release/de/charger/openwb-software-2-x.yaml +++ b/templates/release/de/charger/openwb-software-2-x.yaml @@ -38,7 +38,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/optec-mobility-one.yaml b/templates/release/de/charger/optec-mobility-one.yaml index a0402b919e..26c8912fa8 100644 --- a/templates/release/de/charger/optec-mobility-one.yaml +++ b/templates/release/de/charger/optec-mobility-one.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/orbis-viaris.yaml b/templates/release/de/charger/orbis-viaris.yaml index 5e20b6a215..bd12d6cf91 100644 --- a/templates/release/de/charger/orbis-viaris.yaml +++ b/templates/release/de/charger/orbis-viaris.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/peblar-business.yaml b/templates/release/de/charger/peblar-business.yaml index 45be43b2c3..5a211194a9 100644 --- a/templates/release/de/charger/peblar-business.yaml +++ b/templates/release/de/charger/peblar-business.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/peblar-home-plus.yaml b/templates/release/de/charger/peblar-home-plus.yaml index 026ae5d434..33f9e9b86f 100644 --- a/templates/release/de/charger/peblar-home-plus.yaml +++ b/templates/release/de/charger/peblar-home-plus.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/peblar-home.yaml b/templates/release/de/charger/peblar-home.yaml index 6bc09e6134..b78a39d60b 100644 --- a/templates/release/de/charger/peblar-home.yaml +++ b/templates/release/de/charger/peblar-home.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/phoenix-contact-charx.yaml b/templates/release/de/charger/phoenix-contact-charx.yaml index a14778ed35..6b054d7b78 100644 --- a/templates/release/de/charger/phoenix-contact-charx.yaml +++ b/templates/release/de/charger/phoenix-contact-charx.yaml @@ -29,7 +29,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml b/templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml index 61f1ab493f..11652fe583 100644 --- a/templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml +++ b/templates/release/de/charger/phoenix-contact-em-cp-pp-eth.yaml @@ -19,7 +19,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml index a7212791c7..b17895859a 100644 --- a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml index e97dea064a..4c6627a45a 100644 --- a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml index 857cd048a5..1f61e88c03 100644 --- a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml index b91663fdcd..fed35f6699 100644 --- a/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml +++ b/templates/release/de/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/phoenix-contact-ev-ser.yaml b/templates/release/de/charger/phoenix-contact-ev-ser.yaml index ff1e20eb68..d0768126eb 100644 --- a/templates/release/de/charger/phoenix-contact-ev-ser.yaml +++ b/templates/release/de/charger/phoenix-contact-ev-ser.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/plugchoice.yaml b/templates/release/de/charger/plugchoice.yaml index 613685d21e..528efcece5 100644 --- a/templates/release/de/charger/plugchoice.yaml +++ b/templates/release/de/charger/plugchoice.yaml @@ -18,39 +18,39 @@ render: - default: | type: template template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456) + token: # Token, API Token + identity: AA123456 # Identity des Ladepunkts advanced: | type: template template: plugchoice - token: # API Token - identity: # Identity des Ladepunkts (z.B. AA123456) - connector: 1 # Ladepunkt (falls >1 Ladepunkt), Anschluss-ID (üblicherweise 1) + token: # Token, API Token + identity: AA123456 # Identity des Ladepunkts + connector: 1 # Anschluss-ID params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token advanced: false optional: false - name: identity - example: + example: AA123456 default: choice: [] unit: - description: - help: Identity des Ladepunkts (z.B. AA123456) + description: Identity des Ladepunkts + help: advanced: false optional: false - name: connector - example: + example: 1 default: 1 choice: [] unit: - description: Ladepunkt (falls >1 Ladepunkt) - help: Anschluss-ID (üblicherweise 1) + description: Anschluss-ID + help: advanced: true optional: false \ No newline at end of file diff --git a/templates/release/de/charger/pracht-alpha-xt.yaml b/templates/release/de/charger/pracht-alpha-xt.yaml index f0ee4ef8c9..57c7ad99db 100644 --- a/templates/release/de/charger/pracht-alpha-xt.yaml +++ b/templates/release/de/charger/pracht-alpha-xt.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/pracht-mono-xt.yaml b/templates/release/de/charger/pracht-mono-xt.yaml index 6bc3139149..6be65142ea 100644 --- a/templates/release/de/charger/pracht-mono-xt.yaml +++ b/templates/release/de/charger/pracht-mono-xt.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/pracht-pni.yaml b/templates/release/de/charger/pracht-pni.yaml index b744685fc9..83f2b2b963 100644 --- a/templates/release/de/charger/pracht-pni.yaml +++ b/templates/release/de/charger/pracht-pni.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/pracht-xtplus.yaml b/templates/release/de/charger/pracht-xtplus.yaml index 21d1aa5b24..c194946f44 100644 --- a/templates/release/de/charger/pracht-xtplus.yaml +++ b/templates/release/de/charger/pracht-xtplus.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/pulsares-simplebox.yaml b/templates/release/de/charger/pulsares-simplebox.yaml index 089c80a4d5..d422a7b8da 100644 --- a/templates/release/de/charger/pulsares-simplebox.yaml +++ b/templates/release/de/charger/pulsares-simplebox.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/qcells-q-home-edrive-a.yaml b/templates/release/de/charger/qcells-q-home-edrive-a.yaml index 06b2a2efe0..129f77be17 100644 --- a/templates/release/de/charger/qcells-q-home-edrive-a.yaml +++ b/templates/release/de/charger/qcells-q-home-edrive-a.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/roth-thermoaura.yaml b/templates/release/de/charger/roth-thermoaura.yaml index d6599d4798..c0089cc586 100644 --- a/templates/release/de/charger/roth-thermoaura.yaml +++ b/templates/release/de/charger/roth-thermoaura.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/roth-thermoterra.yaml b/templates/release/de/charger/roth-thermoterra.yaml index b1302bab28..64e4dcd486 100644 --- a/templates/release/de/charger/roth-thermoterra.yaml +++ b/templates/release/de/charger/roth-thermoterra.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/schneider-evlink-pro.yaml b/templates/release/de/charger/schneider-evlink-pro.yaml index 2204af38ba..a8980129d9 100644 --- a/templates/release/de/charger/schneider-evlink-pro.yaml +++ b/templates/release/de/charger/schneider-evlink-pro.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/schrack-i-charge-cion.yaml b/templates/release/de/charger/schrack-i-charge-cion.yaml index 921cd93531..a91568a162 100644 --- a/templates/release/de/charger/schrack-i-charge-cion.yaml +++ b/templates/release/de/charger/schrack-i-charge-cion.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/senec-wallbox-pro-s.yaml b/templates/release/de/charger/senec-wallbox-pro-s.yaml index 314cdc6473..35eb05e99f 100644 --- a/templates/release/de/charger/senec-wallbox-pro-s.yaml +++ b/templates/release/de/charger/senec-wallbox-pro-s.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/senec-wallbox-pro.yaml b/templates/release/de/charger/senec-wallbox-pro.yaml index bc39234a9b..1c72fd10aa 100644 --- a/templates/release/de/charger/senec-wallbox-pro.yaml +++ b/templates/release/de/charger/senec-wallbox-pro.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/shelly-1.yaml b/templates/release/de/charger/shelly-1.yaml index a3f7c74131..d107064df8 100644 --- a/templates/release/de/charger/shelly-1.yaml +++ b/templates/release/de/charger/shelly-1.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true diff --git a/templates/release/de/charger/shelly-plug-s.yaml b/templates/release/de/charger/shelly-plug-s.yaml index 8c9faefea4..f5a32ce9f3 100644 --- a/templates/release/de/charger/shelly-plug-s.yaml +++ b/templates/release/de/charger/shelly-plug-s.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true diff --git a/templates/release/de/charger/shelly-plus-1.yaml b/templates/release/de/charger/shelly-plus-1.yaml index ab01f4812c..d0ea70bd5b 100644 --- a/templates/release/de/charger/shelly-plus-1.yaml +++ b/templates/release/de/charger/shelly-plus-1.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true diff --git a/templates/release/de/charger/shelly-pro-1.yaml b/templates/release/de/charger/shelly-pro-1.yaml index 4de931dfe1..c15a6d97c3 100644 --- a/templates/release/de/charger/shelly-pro-1.yaml +++ b/templates/release/de/charger/shelly-pro-1.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional standbypower: 15 # Standby-Leistung (W), Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) integrateddevice: # Integriertes Gerät, Fest angeschlossenes Gerät. Keine Ladevorgänge (optional) heating: # Wärmeerzeuger, Zeigt °C anstatt % an (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true diff --git a/templates/release/de/charger/siemens-versicharge-gen3.yaml b/templates/release/de/charger/siemens-versicharge-gen3.yaml index c91ceb946e..77a2b7a8e6 100644 --- a/templates/release/de/charger/siemens-versicharge-gen3.yaml +++ b/templates/release/de/charger/siemens-versicharge-gen3.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/smartfox-pro-charger.yaml b/templates/release/de/charger/smartfox-pro-charger.yaml index 488e3de539..1525776761 100644 --- a/templates/release/de/charger/smartfox-pro-charger.yaml +++ b/templates/release/de/charger/smartfox-pro-charger.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/solaredge-home-ev-charger.yaml b/templates/release/de/charger/solaredge-home-ev-charger.yaml index 726e707bdd..829311ada9 100644 --- a/templates/release/de/charger/solaredge-home-ev-charger.yaml +++ b/templates/release/de/charger/solaredge-home-ev-charger.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/solax-x3-evc.yaml b/templates/release/de/charger/solax-x3-evc.yaml index da82455cc4..6a57622ff2 100644 --- a/templates/release/de/charger/solax-x3-evc.yaml +++ b/templates/release/de/charger/solax-x3-evc.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml b/templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml index 323466109a..5cd5ab6c39 100644 --- a/templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml +++ b/templates/release/de/charger/spelsberg-wallbox-smart-pro.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/stark-in-strom-easy.yaml b/templates/release/de/charger/stark-in-strom-easy.yaml index 34909a8afe..2632179575 100644 --- a/templates/release/de/charger/stark-in-strom-easy.yaml +++ b/templates/release/de/charger/stark-in-strom-easy.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml b/templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml index f735a994e9..58fcfe55a2 100644 --- a/templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml +++ b/templates/release/de/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml b/templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml index ff996cefa1..becde93e29 100644 --- a/templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml +++ b/templates/release/de/charger/stiebel-eltron-wpm-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/sungrow-ac011e-01.yaml b/templates/release/de/charger/sungrow-ac011e-01.yaml index 5b3e3e81ce..748742b150 100644 --- a/templates/release/de/charger/sungrow-ac011e-01.yaml +++ b/templates/release/de/charger/sungrow-ac011e-01.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/sungrow-ac011e.yaml b/templates/release/de/charger/sungrow-ac011e.yaml index b9fe80048c..32289fa1b4 100644 --- a/templates/release/de/charger/sungrow-ac011e.yaml +++ b/templates/release/de/charger/sungrow-ac011e.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/sungrow-ac22e-01.yaml b/templates/release/de/charger/sungrow-ac22e-01.yaml index 64254227f2..fd1c806586 100644 --- a/templates/release/de/charger/sungrow-ac22e-01.yaml +++ b/templates/release/de/charger/sungrow-ac22e-01.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/tecalor-thz-sg-ready.yaml b/templates/release/de/charger/tecalor-thz-sg-ready.yaml index d20c72b300..4421304e5b 100644 --- a/templates/release/de/charger/tecalor-thz-sg-ready.yaml +++ b/templates/release/de/charger/tecalor-thz-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/technisat-technivolt.yaml b/templates/release/de/charger/technisat-technivolt.yaml index 965528d401..35102e8fee 100644 --- a/templates/release/de/charger/technisat-technivolt.yaml +++ b/templates/release/de/charger/technisat-technivolt.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/tessie.yaml b/templates/release/de/charger/tessie.yaml index 00fe8ef9d3..ef5dd9437c 100644 --- a/templates/release/de/charger/tessie.yaml +++ b/templates/release/de/charger/tessie.yaml @@ -10,7 +10,7 @@ render: template: tessie vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind token: # Tessie API Token - location: tessiehome # Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) + location: tessiehome # Ort, Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) params: - name: vin example: W... @@ -35,7 +35,7 @@ params: default: choice: [] unit: - description: Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) - help: + description: Ort + help: Definieren Sie einen Ort, an dem das Tessie-Ladegerät funktioniert (always = immer, kein Geofence) oder ein benutzerdefinierter Ort (genauer Name), wie in Tessie definiert (Case sensitive) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/charger/tigo-go-ev-charger.yaml b/templates/release/de/charger/tigo-go-ev-charger.yaml index 0f43a25eed..d11732093f 100644 --- a/templates/release/de/charger/tigo-go-ev-charger.yaml +++ b/templates/release/de/charger/tigo-go-ev-charger.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/tinkerforge-warp-charger-pro.yaml b/templates/release/de/charger/tinkerforge-warp-charger-pro.yaml index d99a541211..c6b95305d0 100644 --- a/templates/release/de/charger/tinkerforge-warp-charger-pro.yaml +++ b/templates/release/de/charger/tinkerforge-warp-charger-pro.yaml @@ -15,7 +15,7 @@ render: port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) advanced: | type: template template: tinkerforge-warp @@ -23,7 +23,7 @@ render: port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) params: @@ -68,8 +68,8 @@ params: default: choice: [] unit: - description: - help: WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) + description: Energiemanager MQTT Topic + help: WEM Firmware v2 erforderlich. advanced: false optional: true - name: user diff --git a/templates/release/de/charger/tinkerforge-warp-charger-smart.yaml b/templates/release/de/charger/tinkerforge-warp-charger-smart.yaml index d2a718362a..793324af5b 100644 --- a/templates/release/de/charger/tinkerforge-warp-charger-smart.yaml +++ b/templates/release/de/charger/tinkerforge-warp-charger-smart.yaml @@ -15,7 +15,7 @@ render: port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) advanced: | type: template template: tinkerforge-warp @@ -23,7 +23,7 @@ render: port: 1883 # Port, MQTT Broker Port (optional) topic: warp # Topic, Topic (ohne / am Anfang) (optional) timeout: 30s # Zeitüberschreitung, Akzeptiere keine Daten die älter sind als dieser Wert (optional) - energymanager: # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) + energymanager: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) params: @@ -68,8 +68,8 @@ params: default: choice: [] unit: - description: - help: WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) + description: Energiemanager MQTT Topic + help: WEM Firmware v2 erforderlich. advanced: false optional: true - name: user diff --git a/templates/release/de/charger/ubitricity-heinz.yaml b/templates/release/de/charger/ubitricity-heinz.yaml index 59638f5b2b..683cd81422 100644 --- a/templates/release/de/charger/ubitricity-heinz.yaml +++ b/templates/release/de/charger/ubitricity-heinz.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/vaillant-sensonet-sg-ready.yaml b/templates/release/de/charger/vaillant-sensonet-sg-ready.yaml index 9f42ea2ffb..db14fb3f71 100644 --- a/templates/release/de/charger/vaillant-sensonet-sg-ready.yaml +++ b/templates/release/de/charger/vaillant-sensonet-sg-ready.yaml @@ -12,9 +12,9 @@ render: template: vaillant user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - realm: DE # [DE, AT] (optional) - zone: # Id der Boostzone (optional) - setpoint: # Boost Temperatur (optional) + realm: DE # Region, [DE, AT] (optional) + zone: # ID der Boostzone, optional + setpoint: # Boost Temperatur, optional params: - name: user example: @@ -39,7 +39,7 @@ params: default: DE choice: ['DE', 'AT'] unit: - description: + description: Region help: advanced: false optional: true @@ -48,8 +48,8 @@ params: default: choice: [] unit: - description: - help: Id der Boostzone + description: ID der Boostzone + help: advanced: false optional: true - name: setpoint @@ -57,7 +57,7 @@ params: default: choice: [] unit: - description: - help: Boost Temperatur + description: Boost Temperatur + help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/charger/vestel-connect-plus.yaml b/templates/release/de/charger/vestel-connect-plus.yaml index d5ad92c1b4..ba6cd4ffa0 100644 --- a/templates/release/de/charger/vestel-connect-plus.yaml +++ b/templates/release/de/charger/vestel-connect-plus.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/vestel-evc04-home-smart.yaml b/templates/release/de/charger/vestel-evc04-home-smart.yaml index 16b6d6a113..eeb2c7c2b8 100644 --- a/templates/release/de/charger/vestel-evc04-home-smart.yaml +++ b/templates/release/de/charger/vestel-evc04-home-smart.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/victron-ev-charging-station-via-gx.yaml b/templates/release/de/charger/victron-ev-charging-station-via-gx.yaml index f4cd502869..8c7e8b03b1 100644 --- a/templates/release/de/charger/victron-ev-charging-station-via-gx.yaml +++ b/templates/release/de/charger/victron-ev-charging-station-via-gx.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/victron-ev-charging-station.yaml b/templates/release/de/charger/victron-ev-charging-station.yaml index 0f34cb551e..4147fd8cd7 100644 --- a/templates/release/de/charger/victron-ev-charging-station.yaml +++ b/templates/release/de/charger/victron-ev-charging-station.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml b/templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml index 53ecd1be96..341632bcd1 100644 --- a/templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml +++ b/templates/release/de/charger/viridian-ev-evse-epc-2-0-plus.yaml @@ -32,7 +32,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/volt-time-one.yaml b/templates/release/de/charger/volt-time-one.yaml index 545bda3266..2a57f8dbb0 100644 --- a/templates/release/de/charger/volt-time-one.yaml +++ b/templates/release/de/charger/volt-time-one.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Seriennummer help: Seriennummer (z. B. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/charger/volt-time-source-2.yaml b/templates/release/de/charger/volt-time-source-2.yaml index f3abc89c09..59dac72a18 100644 --- a/templates/release/de/charger/volt-time-source-2.yaml +++ b/templates/release/de/charger/volt-time-source-2.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Seriennummer help: Seriennummer (z. B. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/charger/volt-time-source-2s.yaml b/templates/release/de/charger/volt-time-source-2s.yaml index 52097c42c6..3cafbd32f1 100644 --- a/templates/release/de/charger/volt-time-source-2s.yaml +++ b/templates/release/de/charger/volt-time-source-2s.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Seriennummer help: Seriennummer (z. B. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/charger/volt-time-source.yaml b/templates/release/de/charger/volt-time-source.yaml index 392ae38266..30d84a4ddf 100644 --- a/templates/release/de/charger/volt-time-source.yaml +++ b/templates/release/de/charger/volt-time-source.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Seriennummer (z. B. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Seriennummer, Seriennummer (z. B. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Seriennummer help: Seriennummer (z. B. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/charger/wallbe-eco-2-0-s.yaml b/templates/release/de/charger/wallbe-eco-2-0-s.yaml index d4f9b0c086..0d866fa2a2 100644 --- a/templates/release/de/charger/wallbe-eco-2-0-s.yaml +++ b/templates/release/de/charger/wallbe-eco-2-0-s.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/wallbe-eco.yaml b/templates/release/de/charger/wallbe-eco.yaml index 5b22c722b4..f71df5a49e 100644 --- a/templates/release/de/charger/wallbe-eco.yaml +++ b/templates/release/de/charger/wallbe-eco.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/wallbe-pro.yaml b/templates/release/de/charger/wallbe-pro.yaml index 0155f274c4..69e29d4ec4 100644 --- a/templates/release/de/charger/wallbe-pro.yaml +++ b/templates/release/de/charger/wallbe-pro.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml b/templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml index 7647304710..31cf20c32c 100644 --- a/templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml +++ b/templates/release/de/charger/wallbox-commander-2-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-commander-2.yaml b/templates/release/de/charger/wallbox-commander-2.yaml index db242cee82..23fc4b9446 100644 --- a/templates/release/de/charger/wallbox-commander-2.yaml +++ b/templates/release/de/charger/wallbox-commander-2.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml b/templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml index 6ef4e83a30..2cfeea6dc3 100644 --- a/templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml +++ b/templates/release/de/charger/wallbox-copper-sb-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-copper-sb.yaml b/templates/release/de/charger/wallbox-copper-sb.yaml index 29ee4ad073..cb7f1dec3d 100644 --- a/templates/release/de/charger/wallbox-copper-sb.yaml +++ b/templates/release/de/charger/wallbox-copper-sb.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml b/templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml index aa23253e98..0b8c545daa 100644 --- a/templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml +++ b/templates/release/de/charger/wallbox-pulsar-max-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-pulsar-max.yaml b/templates/release/de/charger/wallbox-pulsar-max.yaml index bf9ebc3609..fb192e8bb8 100644 --- a/templates/release/de/charger/wallbox-pulsar-max.yaml +++ b/templates/release/de/charger/wallbox-pulsar-max.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml b/templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml index a2d8008de7..6b76d1eca1 100644 --- a/templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml +++ b/templates/release/de/charger/wallbox-pulsar-plus-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/wallbox-pulsar-plus.yaml b/templates/release/de/charger/wallbox-pulsar-plus.yaml index 35864274bd..bdee3df40c 100644 --- a/templates/release/de/charger/wallbox-pulsar-plus.yaml +++ b/templates/release/de/charger/wallbox-pulsar-plus.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/walther-werke-basic-evo-pro.yaml b/templates/release/de/charger/walther-werke-basic-evo-pro.yaml index 003876400c..3aaefbc2af 100644 --- a/templates/release/de/charger/walther-werke-basic-evo-pro.yaml +++ b/templates/release/de/charger/walther-werke-basic-evo-pro.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/webasto-live.yaml b/templates/release/de/charger/webasto-live.yaml index 49dcd3dc6b..c5215f41f9 100644 --- a/templates/release/de/charger/webasto-live.yaml +++ b/templates/release/de/charger/webasto-live.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/webasto-unite.yaml b/templates/release/de/charger/webasto-unite.yaml index 1bc88d681f..b3cc480e87 100644 --- a/templates/release/de/charger/webasto-unite.yaml +++ b/templates/release/de/charger/webasto-unite.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/charger/wolf-bwl.yaml b/templates/release/de/charger/wolf-bwl.yaml index 463ac00783..323786a896 100644 --- a/templates/release/de/charger/wolf-bwl.yaml +++ b/templates/release/de/charger/wolf-bwl.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/wolf-bws.yaml b/templates/release/de/charger/wolf-bws.yaml index 00923e24ef..cb09101a15 100644 --- a/templates/release/de/charger/wolf-bws.yaml +++ b/templates/release/de/charger/wolf-bws.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Anhebung der Heizwassertemperatur. (optional) - wwoffset: 0.0 # Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. (optional) + heatoffset: 0.0 # Anhebung der Heizwassertemperatur (K), optional + wwoffset: 0.0 # Anhebung der Warmwassertemperatur (K), Erhöht evtl. den Verschleiss des Kompressors. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Heizwassertemperatur. + description: Anhebung der Heizwassertemperatur + help: advanced: false optional: true - name: wwoffset @@ -52,8 +52,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Anhebung der Warmwassertemperatur. Erhöht evtl. den Verschleiss des Kompressors. + description: Anhebung der Warmwassertemperatur + help: Erhöht evtl. den Verschleiss des Kompressors. advanced: true optional: true modbus: diff --git a/templates/release/de/charger/zaptec-go-2.yaml b/templates/release/de/charger/zaptec-go-2.yaml index 7ee42d1e79..ac9e70588b 100644 --- a/templates/release/de/charger/zaptec-go-2.yaml +++ b/templates/release/de/charger/zaptec-go-2.yaml @@ -9,7 +9,7 @@ render: - default: | type: template template: zaptec - id: # Wallbox ID (optional) + id: # ID, Wallbox ID (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) params: @@ -18,7 +18,7 @@ params: default: choice: [] unit: - description: + description: ID help: Wallbox ID advanced: false optional: true diff --git a/templates/release/de/charger/zaptec-go-ocpp.yaml b/templates/release/de/charger/zaptec-go-ocpp.yaml index 4d92602c0f..b0a6ffb9bf 100644 --- a/templates/release/de/charger/zaptec-go-ocpp.yaml +++ b/templates/release/de/charger/zaptec-go-ocpp.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/zaptec-go.yaml b/templates/release/de/charger/zaptec-go.yaml index 1d0029bbed..12d1ce84c5 100644 --- a/templates/release/de/charger/zaptec-go.yaml +++ b/templates/release/de/charger/zaptec-go.yaml @@ -9,7 +9,7 @@ render: - default: | type: template template: zaptec - id: # Wallbox ID (optional) + id: # ID, Wallbox ID (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) params: @@ -18,7 +18,7 @@ params: default: choice: [] unit: - description: + description: ID help: Wallbox ID advanced: false optional: true diff --git a/templates/release/de/charger/zaptec-pro.yaml b/templates/release/de/charger/zaptec-pro.yaml index f6e04b5a89..54d0b582cb 100644 --- a/templates/release/de/charger/zaptec-pro.yaml +++ b/templates/release/de/charger/zaptec-pro.yaml @@ -9,7 +9,7 @@ render: - default: | type: template template: zaptec - id: # Wallbox ID (optional) + id: # ID, Wallbox ID (optional) user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) params: @@ -18,7 +18,7 @@ params: default: choice: [] unit: - description: + description: ID help: Wallbox ID advanced: false optional: true diff --git a/templates/release/de/charger/zewotherm-eu-l-series.yaml b/templates/release/de/charger/zewotherm-eu-l-series.yaml index b02ced9352..a8b0398dce 100644 --- a/templates/release/de/charger/zewotherm-eu-l-series.yaml +++ b/templates/release/de/charger/zewotherm-eu-l-series.yaml @@ -21,7 +21,7 @@ render: template: lambda-zewotherm host: 192.0.2.2 # IP-Adresse oder Hostname tempsource: # Temperaturquelle, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -46,7 +46,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/charger/zj-beny-bcp-ev-charger.yaml b/templates/release/de/charger/zj-beny-bcp-ev-charger.yaml index 0b453dbc7a..19ee782783 100644 --- a/templates/release/de/charger/zj-beny-bcp-ev-charger.yaml +++ b/templates/release/de/charger/zj-beny-bcp-ev-charger.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) advanced: | type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) + stationid: EVB-P12354 # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional) connector: 1 # Anschlussnummer, Bei Ladestationen mit mehreren Anschlüssen. Die Zählung beginnt bei 1 für den ersten Anschluss. (optional) - remotestart: # Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional) - idtag: evcc # Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction), Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (optional) - connecttimeout: 5m # Zeitlimit für die Registrierung des Ladepunktes, optional - meterinterval: 10s # Übertragungsintervall der Zählerwerte (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData), optional + remotestart: # Remote-Transaktion bei Fahrzeugverbindung starten, Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentifizierungs-Token, Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Zeitlimit für die Registrierung, Zeitlimit für die Registrierung des Ladepunktes (optional) + meterinterval: 10s # Übertragungsintervall der Zählerwerte, Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Zählerwerte für die Übertragung, Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://:8887/ anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' + help: 'Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://:8887/` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Immer eine Remote-Transaktion starten (RemoteStartTransaction) sobald ein Fahrzeug angeschlossen wird - help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! + description: Remote-Transaktion bei Fahrzeugverbindung starten + help: Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifikator zur Authentifizierung von externen Transaktionen (RemoteStartTransaction) - help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. + description: Authentifizierungs-Token + help: Diese Option ist nur in Ausnahmefällen erforderlich wenn der Ladepunkt für die Annahme externer Transaktionen einen spezifischen Token erfordert. (Verwendet OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Zeitlimit für die Registrierung des Ladepunktes - help: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Übertragungsintervall der Zählerwerte (MeterValueSampleInterval) - help: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) - help: + description: Zählerwerte für die Übertragung + help: Manuelle Vorgabe der zu konfigurierenden Zählerwerte (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/meter/a-tronix.yaml b/templates/release/de/meter/a-tronix.yaml index 9e45ad87c1..696678de34 100644 --- a/templates/release/de/meter/a-tronix.yaml +++ b/templates/release/de/meter/a-tronix.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional + delay: 100ms # Verzögerung, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Verzögerung help: advanced: true optional: true diff --git a/templates/release/de/meter/abb-a43.yaml b/templates/release/de/meter/abb-a43.yaml index b8f9cde212..3228fb4bcf 100644 --- a/templates/release/de/meter/abb-a43.yaml +++ b/templates/release/de/meter/abb-a43.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/abb-a44.yaml b/templates/release/de/meter/abb-a44.yaml index 73a54d0f01..1b4917bf0b 100644 --- a/templates/release/de/meter/abb-a44.yaml +++ b/templates/release/de/meter/abb-a44.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/abb-b23.yaml b/templates/release/de/meter/abb-b23.yaml index 064db6b31f..a62d281f32 100644 --- a/templates/release/de/meter/abb-b23.yaml +++ b/templates/release/de/meter/abb-b23.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/abb-b24.yaml b/templates/release/de/meter/abb-b24.yaml index b82fd16671..9bcd42b72d 100644 --- a/templates/release/de/meter/abb-b24.yaml +++ b/templates/release/de/meter/abb-b24.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/acrel-adw300.yaml b/templates/release/de/meter/acrel-adw300.yaml index ed0f7ea506..c686556906 100644 --- a/templates/release/de/meter/acrel-adw300.yaml +++ b/templates/release/de/meter/acrel-adw300.yaml @@ -82,7 +82,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/ads-tec-storaxe.yaml b/templates/release/de/meter/ads-tec-storaxe.yaml index 3bf8874ee5..31644be2c4 100644 --- a/templates/release/de/meter/ads-tec-storaxe.yaml +++ b/templates/release/de/meter/ads-tec-storaxe.yaml @@ -32,7 +32,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/alpha-ess-storion-smile.yaml b/templates/release/de/meter/alpha-ess-storion-smile.yaml index 6975203c19..b0b01245f8 100644 --- a/templates/release/de/meter/alpha-ess-storion-smile.yaml +++ b/templates/release/de/meter/alpha-ess-storion-smile.yaml @@ -55,8 +55,6 @@ render: id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: pv default: | type: template @@ -104,8 +102,6 @@ render: id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -163,7 +159,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/ampere-ampere-storagepro.yaml b/templates/release/de/meter/ampere-ampere-storagepro.yaml index db897964dd..f6bcb35728 100644 --- a/templates/release/de/meter/ampere-ampere-storagepro.yaml +++ b/templates/release/de/meter/ampere-ampere-storagepro.yaml @@ -51,8 +51,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: pv default: | type: template @@ -100,8 +98,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: battery default: | type: template @@ -159,7 +155,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/anker-micro-inverter.yaml b/templates/release/de/meter/anker-micro-inverter.yaml index c2b07840a3..040b18f604 100644 --- a/templates/release/de/meter/anker-micro-inverter.yaml +++ b/templates/release/de/meter/anker-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: true optional: true diff --git a/templates/release/de/meter/axitec-axihycon-12-15h.yaml b/templates/release/de/meter/axitec-axihycon-12-15h.yaml index b225532c7c..4d053f8839 100644 --- a/templates/release/de/meter/axitec-axihycon-12-15h.yaml +++ b/templates/release/de/meter/axitec-axihycon-12-15h.yaml @@ -117,7 +117,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/bernecker-engineering-mpm3pm.yaml b/templates/release/de/meter/bernecker-engineering-mpm3pm.yaml index 7d3910399f..0aeae72e6e 100644 --- a/templates/release/de/meter/bernecker-engineering-mpm3pm.yaml +++ b/templates/release/de/meter/bernecker-engineering-mpm3pm.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/bgetech-ds100.yaml b/templates/release/de/meter/bgetech-ds100.yaml index c4718cb5cc..660b557147 100644 --- a/templates/release/de/meter/bgetech-ds100.yaml +++ b/templates/release/de/meter/bgetech-ds100.yaml @@ -106,7 +106,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/bgetech-ws100.yaml b/templates/release/de/meter/bgetech-ws100.yaml index b1f7bbd153..ccbbfd0a84 100644 --- a/templates/release/de/meter/bgetech-ws100.yaml +++ b/templates/release/de/meter/bgetech-ws100.yaml @@ -106,7 +106,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/bosswerk-micro-inverter.yaml b/templates/release/de/meter/bosswerk-micro-inverter.yaml index 0434da45af..a95b46a131 100644 --- a/templates/release/de/meter/bosswerk-micro-inverter.yaml +++ b/templates/release/de/meter/bosswerk-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: true optional: true diff --git a/templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml b/templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml index b75d465d27..21ca50a01d 100644 --- a/templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml +++ b/templates/release/de/meter/carlo-gavazzi-em110-111-112.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/carlo-gavazzi-em24.yaml b/templates/release/de/meter/carlo-gavazzi-em24.yaml index aa73f0e9a6..b814dbe081 100644 --- a/templates/release/de/meter/carlo-gavazzi-em24.yaml +++ b/templates/release/de/meter/carlo-gavazzi-em24.yaml @@ -49,7 +49,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/carlo-gavazzi-em24_e1.yaml b/templates/release/de/meter/carlo-gavazzi-em24_e1.yaml index ec04cf056f..4830963028 100644 --- a/templates/release/de/meter/carlo-gavazzi-em24_e1.yaml +++ b/templates/release/de/meter/carlo-gavazzi-em24_e1.yaml @@ -36,7 +36,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/carlo-gavazzi-em330-em340.yaml b/templates/release/de/meter/carlo-gavazzi-em330-em340.yaml index 71771d9771..8977fd01ea 100644 --- a/templates/release/de/meter/carlo-gavazzi-em330-em340.yaml +++ b/templates/release/de/meter/carlo-gavazzi-em330-em340.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/carlo-gavazzi-em530-em540.yaml b/templates/release/de/meter/carlo-gavazzi-em530-em540.yaml index d0f5a82c17..f2415e6b24 100644 --- a/templates/release/de/meter/carlo-gavazzi-em530-em540.yaml +++ b/templates/release/de/meter/carlo-gavazzi-em530-em540.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/carlo-gavazzi-et112.yaml b/templates/release/de/meter/carlo-gavazzi-et112.yaml index 16680813b5..d11eafa3f8 100644 --- a/templates/release/de/meter/carlo-gavazzi-et112.yaml +++ b/templates/release/de/meter/carlo-gavazzi-et112.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/carlo-gavazzi-et330-et340.yaml b/templates/release/de/meter/carlo-gavazzi-et330-et340.yaml index da396ac6cc..8316fa8059 100644 --- a/templates/release/de/meter/carlo-gavazzi-et330-et340.yaml +++ b/templates/release/de/meter/carlo-gavazzi-et330-et340.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/cfos-powerbrain-meter.yaml b/templates/release/de/meter/cfos-powerbrain-meter.yaml index 3eb38abc45..be38975814 100644 --- a/templates/release/de/meter/cfos-powerbrain-meter.yaml +++ b/templates/release/de/meter/cfos-powerbrain-meter.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/deye-3p-hybrid-inverter.yaml b/templates/release/de/meter/deye-3p-hybrid-inverter.yaml index d27fd593ae..20d45d592f 100644 --- a/templates/release/de/meter/deye-3p-hybrid-inverter.yaml +++ b/templates/release/de/meter/deye-3p-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml b/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml index a70db4a58a..1b4f7aa071 100644 --- a/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml +++ b/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml @@ -52,9 +52,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - usage: pv default: | @@ -103,9 +101,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - usage: battery @@ -155,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -166,7 +162,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -175,7 +171,7 @@ params: default: 1 choice: [] unit: - description: + description: Nummer des Batteriespeichers help: advanced: true optional: true diff --git a/templates/release/de/meter/deye-micro-inverter.yaml b/templates/release/de/meter/deye-micro-inverter.yaml index b8ec8bd1dc..136c4b0001 100644 --- a/templates/release/de/meter/deye-micro-inverter.yaml +++ b/templates/release/de/meter/deye-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: true optional: true diff --git a/templates/release/de/meter/deye-storage-hybrid-inverter.yaml b/templates/release/de/meter/deye-storage-hybrid-inverter.yaml index 00af002dbc..e03ce9644f 100644 --- a/templates/release/de/meter/deye-storage-hybrid-inverter.yaml +++ b/templates/release/de/meter/deye-storage-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/deye-string-inverter.yaml b/templates/release/de/meter/deye-string-inverter.yaml index 5c65be54c8..2147fcd202 100644 --- a/templates/release/de/meter/deye-string-inverter.yaml +++ b/templates/release/de/meter/deye-string-inverter.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/discovergy.yaml b/templates/release/de/meter/discovergy.yaml index 6e2da0bd6b..df382b5421 100644 --- a/templates/release/de/meter/discovergy.yaml +++ b/templates/release/de/meter/discovergy.yaml @@ -10,7 +10,7 @@ render: usage: grid user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886 + meter: 1ESY1161229886 # Zählernummer - usage: pv default: | type: template @@ -18,7 +18,7 @@ render: usage: pv user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - meter: 1ESY1161229886 + meter: 1ESY1161229886 # Zählernummer params: - name: user example: @@ -43,7 +43,7 @@ params: default: choice: [] unit: - description: + description: Zählernummer help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/meter/dzg-dvh4013.yaml b/templates/release/de/meter/dzg-dvh4013.yaml index 8a56066ec7..4eabb1f46e 100644 --- a/templates/release/de/meter/dzg-dvh4013.yaml +++ b/templates/release/de/meter/dzg-dvh4013.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/e3-dc.yaml b/templates/release/de/meter/e3-dc.yaml index bd4ea6138a..6cc7a3344a 100644 --- a/templates/release/de/meter/e3-dc.yaml +++ b/templates/release/de/meter/e3-dc.yaml @@ -18,7 +18,7 @@ render: port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password advanced: | type: template template: e3dc-rscp @@ -27,7 +27,7 @@ render: port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) - usage: pv default: | @@ -38,7 +38,7 @@ render: port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password advanced: | type: template template: e3dc-rscp @@ -47,7 +47,7 @@ render: port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery @@ -59,7 +59,7 @@ render: port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password advanced: | type: template template: e3dc-rscp @@ -68,7 +68,7 @@ render: port: 5033 # Port, optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - key: + key: # RSCP-Password dischargelimit: # Entladelimit in W, Limitiert die Entladeleistung im 'Halten' Batteriemodus (optional) capacity: 50 # Akkukapazität (kWh), optional params: @@ -113,7 +113,7 @@ params: default: choice: [] unit: - description: + description: RSCP-Password help: advanced: false optional: false diff --git a/templates/release/de/meter/eastron-sdm120-modbus.yaml b/templates/release/de/meter/eastron-sdm120-modbus.yaml index 73b2709021..3760971d3b 100644 --- a/templates/release/de/meter/eastron-sdm120-modbus.yaml +++ b/templates/release/de/meter/eastron-sdm120-modbus.yaml @@ -64,7 +64,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/eastron-sdm220-230.yaml b/templates/release/de/meter/eastron-sdm220-230.yaml index c6cf09acf7..c4356964b7 100644 --- a/templates/release/de/meter/eastron-sdm220-230.yaml +++ b/templates/release/de/meter/eastron-sdm220-230.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/eastron-sdm630-modbus.yaml b/templates/release/de/meter/eastron-sdm630-modbus.yaml index bb5ee3cccb..039de5eaa5 100644 --- a/templates/release/de/meter/eastron-sdm630-modbus.yaml +++ b/templates/release/de/meter/eastron-sdm630-modbus.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/eastron-sdm72d-m.yaml b/templates/release/de/meter/eastron-sdm72d-m.yaml index 9ebaf66503..956eced6c3 100644 --- a/templates/release/de/meter/eastron-sdm72d-m.yaml +++ b/templates/release/de/meter/eastron-sdm72d-m.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/eastron-sdm72dm-v2.yaml b/templates/release/de/meter/eastron-sdm72dm-v2.yaml index 552313a71d..e3b1948eec 100644 --- a/templates/release/de/meter/eastron-sdm72dm-v2.yaml +++ b/templates/release/de/meter/eastron-sdm72dm-v2.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/enphase-iq-envoy.yaml b/templates/release/de/meter/enphase-iq-envoy.yaml index c9b71016f1..a6de08539a 100644 --- a/templates/release/de/meter/enphase-iq-envoy.yaml +++ b/templates/release/de/meter/enphase-iq-envoy.yaml @@ -12,13 +12,13 @@ render: template: enphase usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) advanced: | type: template template: enphase usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - usage: pv default: | @@ -26,13 +26,13 @@ render: template: enphase usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) advanced: | type: template template: enphase usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - usage: battery default: | @@ -40,13 +40,13 @@ render: template: enphase usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) advanced: | type: template template: enphase usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - token: # Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) capacity: 50 # Akkukapazität (kWh), optional cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) params: @@ -64,7 +64,7 @@ params: default: choice: [] unit: - description: + description: Token help: 'Ab Envoy Firmware D7.x.xxx notwendig. Token ist ein Jahr gültig. Anleitung (Obtaining a token via web UI): https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication' advanced: false optional: true diff --git a/templates/release/de/meter/fenecon.yaml b/templates/release/de/meter/fenecon.yaml index 6e2ab29009..8f3ea97ca7 100644 --- a/templates/release/de/meter/fenecon.yaml +++ b/templates/release/de/meter/fenecon.yaml @@ -44,8 +44,8 @@ render: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) + battery: ess0 # Steuerbare Batterie Komponente, optional + watchdog: 60s # Watchdog, abgestimmt auf das API-Timeout (optional) capacity: 50 # Akkukapazität (kWh), optional params: - name: host @@ -71,8 +71,8 @@ params: default: choice: [] unit: - description: - help: steuerbare Batterie Komponente + description: Steuerbare Batterie Komponente + help: advanced: true optional: true - name: watchdog @@ -80,7 +80,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: abgestimmt auf das API-Timeout advanced: true optional: true diff --git a/templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml b/templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml index d696651368..9549403185 100644 --- a/templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml +++ b/templates/release/de/meter/foxess-h1-series-hybrid-inverter.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml b/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml index 893a87b25b..f0b86c2160 100644 --- a/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml +++ b/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml b/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml index 0069b8b62f..337a63b592 100644 --- a/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml +++ b/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/fronius-primo-gen24-plus.yaml b/templates/release/de/meter/fronius-primo-gen24-plus.yaml index 07bdd65d70..8e07e0f5a0 100644 --- a/templates/release/de/meter/fronius-primo-gen24-plus.yaml +++ b/templates/release/de/meter/fronius-primo-gen24-plus.yaml @@ -18,7 +18,7 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) + id: 200 # ID, Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) - usage: pv default: | type: template @@ -72,7 +72,7 @@ params: default: 200 choice: [] unit: - description: + description: ID help: 'Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201).' advanced: true optional: true diff --git a/templates/release/de/meter/fronius-smartmeter-via-inverter.yaml b/templates/release/de/meter/fronius-smartmeter-via-inverter.yaml index c56c0f0749..cfe9b7c773 100644 --- a/templates/release/de/meter/fronius-smartmeter-via-inverter.yaml +++ b/templates/release/de/meter/fronius-smartmeter-via-inverter.yaml @@ -32,7 +32,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/fronius-solar-api-v1.yaml b/templates/release/de/meter/fronius-solar-api-v1.yaml index c69ce0d5fe..ec286a57f4 100644 --- a/templates/release/de/meter/fronius-solar-api-v1.yaml +++ b/templates/release/de/meter/fronius-solar-api-v1.yaml @@ -27,7 +27,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional) + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional) - usage: pv default: | type: template @@ -43,7 +43,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional) + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional) - usage: battery default: | type: template @@ -60,7 +60,7 @@ render: user: customer # Benutzername (für aktive Batteriesteuerung), bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort (für aktive Batteriesteuerung), Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) capacity: 50 # Akkukapazität (kWh), optional - batteryconfiguri: /config # Firmware Versionen ab 1.36.5-1 erfordern /api/config., [/config, /api/config] (optional) + batteryconfiguri: /config # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional) params: - name: host example: 192.0.2.2 @@ -103,7 +103,7 @@ params: default: /config choice: ['/config', '/api/config'] unit: - description: Firmware Versionen ab 1.36.5-1 erfordern /api/config. - help: + description: Batteriekonfigurations-URI + help: Firmware Versionen ab 1.36.5-1 erfordern /api/config. advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/meter/fronius-symo-gen24-plus.yaml b/templates/release/de/meter/fronius-symo-gen24-plus.yaml index 8311dbc743..62bfcbb668 100644 --- a/templates/release/de/meter/fronius-symo-gen24-plus.yaml +++ b/templates/release/de/meter/fronius-symo-gen24-plus.yaml @@ -18,7 +18,7 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 200 # Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) + id: 200 # ID, Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201). (optional) - usage: pv default: | type: template @@ -72,7 +72,7 @@ params: default: 200 choice: [] unit: - description: + description: ID help: 'Zähleradresse von Primär- oder Sekundärzählern. Auf der Weboberfläche des Wechselrichters kann nur die Adresse des ersten Zählers (z.B. 200) eingestellt werden. Zusätzliche Zähler erhalten eine aufsteigende Nummer (z.B: 201).' advanced: true optional: true diff --git a/templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml b/templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml index 2a1bac8b9a..38a0a0eda5 100644 --- a/templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml +++ b/templates/release/de/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml @@ -117,7 +117,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml b/templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml index f66ded4712..4623fd8f62 100644 --- a/templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml +++ b/templates/release/de/meter/ginlong-solis-hybrid-inverter-s-series.yaml @@ -117,7 +117,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/ginlong-solis-inverter.yaml b/templates/release/de/meter/ginlong-solis-inverter.yaml index 92f207ca67..53e7a2c362 100644 --- a/templates/release/de/meter/ginlong-solis-inverter.yaml +++ b/templates/release/de/meter/ginlong-solis-inverter.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml b/templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml index ff06b0509b..68006b22fe 100644 --- a/templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml +++ b/templates/release/de/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml @@ -29,7 +29,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) advanced: | type: template template: goodwe-hybrid @@ -53,7 +53,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) - usage: pv default: | type: template @@ -78,7 +78,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) advanced: | type: template template: goodwe-hybrid @@ -102,7 +102,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -128,7 +128,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) advanced: | type: template template: goodwe-hybrid @@ -152,7 +152,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Batteriespeichernummer, [1, 2] (optional) capacity: 50 # Akkukapazität (kWh), optional params: - name: modbus @@ -160,7 +160,7 @@ params: default: choice: ['rs485', 'tcpip', 'udp'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -169,7 +169,7 @@ params: default: 1 choice: ['1', '2'] unit: - description: + description: Batteriespeichernummer help: advanced: false optional: true diff --git a/templates/release/de/meter/goodwe-sdt-dt-inverter.yaml b/templates/release/de/meter/goodwe-sdt-dt-inverter.yaml index 9780442ace..0231d53acf 100644 --- a/templates/release/de/meter/goodwe-sdt-dt-inverter.yaml +++ b/templates/release/de/meter/goodwe-sdt-dt-inverter.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/growatt-hybrid-inverter.yaml b/templates/release/de/meter/growatt-hybrid-inverter.yaml index 2306a0fb74..1f05cd6223 100644 --- a/templates/release/de/meter/growatt-hybrid-inverter.yaml +++ b/templates/release/de/meter/growatt-hybrid-inverter.yaml @@ -160,7 +160,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml b/templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml index f579df5921..8b4c44680f 100644 --- a/templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml +++ b/templates/release/de/meter/growatt-tl-x-h-hybrid-inverter.yaml @@ -154,7 +154,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/homematic-ip.yaml b/templates/release/de/meter/homematic-ip.yaml index 7fbebea3e7..034430b26f 100644 --- a/templates/release/de/meter/homematic-ip.yaml +++ b/templates/release/de/meter/homematic-ip.yaml @@ -13,7 +13,7 @@ render: device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. advanced: | type: template template: homematic @@ -22,8 +22,8 @@ render: device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) - usage: pv default: | type: template @@ -33,7 +33,7 @@ render: device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. advanced: | type: template template: homematic @@ -42,8 +42,8 @@ render: device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) - usage: charge default: | type: template @@ -53,7 +53,7 @@ render: device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. advanced: | type: template template: homematic @@ -62,8 +62,8 @@ render: device: 0001EE89AAD848 # Geräteadresse/Seriennummer, Homematic Geräte Id, wie im CCU Webfrontend angezeigt. user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. - cache: 1s # XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h), Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) + meterchannel: 6 # Kanalnummer des Power- oder Netz-Meters, Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. + cache: 1s # XML-RPC API Cache Zeitraum, Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. (optional) params: - name: host example: 192.0.2.2 @@ -102,11 +102,11 @@ params: advanced: false optional: true - name: meterchannel - example: + example: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1 default: 6 choice: [] unit: - description: Kanalnummer des Power- oder Netz-Meters (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1) + description: Kanalnummer des Power- oder Netz-Meters help: Kanalnummer des Messwertkanals, wie im CCU Webfrontend mit Doppelpunkt getrennt nach der Geräte Id angezeigt. advanced: false optional: false @@ -115,7 +115,7 @@ params: default: 1s choice: [] unit: - description: XML-RPC API Cache Zeitraum - Default 1s. (gültige Einheiten s,m,h) + description: XML-RPC API Cache Zeitraum help: Bei Problemen mit dem Duty Cycle setze den Cache auf bspw 30s. advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml b/templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml index 08517f1767..2e1fdce17a 100644 --- a/templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml +++ b/templates/release/de/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml @@ -10,7 +10,7 @@ render: template: hoymiles-ahoydtu usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - id: 0 # Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID], optional + id: 0 # Wechselrichter ID, Falls mehrere vorhanden. Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID] (optional) params: - name: host example: 192.0.2.2 @@ -26,7 +26,7 @@ params: default: 0 choice: [] unit: - description: 'Wechselrichter ID (falls mehrere vorhanden). Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID]' - help: + description: Wechselrichter ID + help: 'Falls mehrere vorhanden. Die Nummerierung beginnt bei 0. Siehe AhoyDTU Webinterface -> Inverter #[ID]' advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/huawei-emma.yaml b/templates/release/de/meter/huawei-emma.yaml index b4cff0e827..a9ff0156db 100644 --- a/templates/release/de/meter/huawei-emma.yaml +++ b/templates/release/de/meter/huawei-emma.yaml @@ -74,7 +74,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/huawei-smartlogger.yaml b/templates/release/de/meter/huawei-smartlogger.yaml index 2cb7a7e1df..0e8b9398ff 100644 --- a/templates/release/de/meter/huawei-smartlogger.yaml +++ b/templates/release/de/meter/huawei-smartlogger.yaml @@ -28,7 +28,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional - usage: pv default: | type: template @@ -52,7 +52,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -77,7 +77,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional params: - name: modbus @@ -85,7 +85,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -103,7 +103,7 @@ params: default: 1 choice: [] unit: - description: + description: Nummer des Batteriespeichers help: advanced: true optional: true diff --git a/templates/release/de/meter/huawei-sun2000-sdongle.yaml b/templates/release/de/meter/huawei-sun2000-sdongle.yaml index f7bf90881c..c76459f6b0 100644 --- a/templates/release/de/meter/huawei-sun2000-sdongle.yaml +++ b/templates/release/de/meter/huawei-sun2000-sdongle.yaml @@ -26,7 +26,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/huawei-sun2000.yaml b/templates/release/de/meter/huawei-sun2000.yaml index b249bab017..c026ff2953 100644 --- a/templates/release/de/meter/huawei-sun2000.yaml +++ b/templates/release/de/meter/huawei-sun2000.yaml @@ -59,7 +59,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional - usage: pv default: | type: template @@ -109,7 +109,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -160,7 +160,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Zeitüberschreitung, optional - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional maxchargepower: 10000 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) capacity: 50 # Akkukapazität (kWh), optional forceaccharging: false # Wechselrichterkaskade, AC-Laden bleibt aktiv zum Laden des Speichers aus anderen AC Quellen für Wechselrichterkaskaden. Verhindert Stand-by. (optional) @@ -170,7 +170,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -188,7 +188,7 @@ params: default: 1 choice: [] unit: - description: + description: Nummer des Batteriespeichers help: advanced: true optional: true diff --git a/templates/release/de/meter/inepro-pro380-mod.yaml b/templates/release/de/meter/inepro-pro380-mod.yaml index 66c63aefae..3843511583 100644 --- a/templates/release/de/meter/inepro-pro380-mod.yaml +++ b/templates/release/de/meter/inepro-pro380-mod.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/janitza-b-series.yaml b/templates/release/de/meter/janitza-b-series.yaml index 471cd33ce3..88b60f4853 100644 --- a/templates/release/de/meter/janitza-b-series.yaml +++ b/templates/release/de/meter/janitza-b-series.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/janitza-umg-series.yaml b/templates/release/de/meter/janitza-umg-series.yaml index c6c3c47f25..7843426eb3 100644 --- a/templates/release/de/meter/janitza-umg-series.yaml +++ b/templates/release/de/meter/janitza-umg-series.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/keba-kecontact-e10.yaml b/templates/release/de/meter/keba-kecontact-e10.yaml index 432af7879f..5549ab7ddd 100644 --- a/templates/release/de/meter/keba-kecontact-e10.yaml +++ b/templates/release/de/meter/keba-kecontact-e10.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml b/templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml index fdaed4b63f..fb93a948d9 100644 --- a/templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml +++ b/templates/release/de/meter/kostal-energy-meter-c-kem-c.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml b/templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml index a4f8d0cb8f..fbe79d304e 100644 --- a/templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml +++ b/templates/release/de/meter/kostal-energy-meter-p-kem-p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml b/templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml index 06a8a61eba..f4d4fa8f76 100644 --- a/templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml +++ b/templates/release/de/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml @@ -33,7 +33,7 @@ render: port: 1502 # Port endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -58,14 +58,14 @@ render: endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) capacity: 50 # Akkukapazität (kWh), optional maxchargerate: 100 # Maximale Ladeleistung (%), Für erzwungenes Laden des Speichers in Prozent in Relation zur maximalen Ladeleistung des Batteriewechselrichters. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -110,7 +110,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/kostal-plenticore-hybrid.yaml b/templates/release/de/meter/kostal-plenticore-hybrid.yaml index 2eca97fc75..6384072b26 100644 --- a/templates/release/de/meter/kostal-plenticore-hybrid.yaml +++ b/templates/release/de/meter/kostal-plenticore-hybrid.yaml @@ -32,9 +32,7 @@ render: port: 1502 # Port endianness: little # Byte-Reihenfolge (Little/Big), [little, big] (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -60,14 +58,14 @@ render: capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -121,7 +119,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml b/templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml index 445ad11caa..eff0b09aa8 100644 --- a/templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml +++ b/templates/release/de/meter/kostal-smart-energy-meter-via-inverter.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/kostal-smart-energy-meter.yaml b/templates/release/de/meter/kostal-smart-energy-meter.yaml index 63cad3375d..1764a257c8 100644 --- a/templates/release/de/meter/kostal-smart-energy-meter.yaml +++ b/templates/release/de/meter/kostal-smart-energy-meter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/lg-ess-home-15.yaml b/templates/release/de/meter/lg-ess-home-15.yaml index bdb9dc9f59..0bc73961dc 100644 --- a/templates/release/de/meter/lg-ess-home-15.yaml +++ b/templates/release/de/meter/lg-ess-home-15.yaml @@ -18,9 +18,7 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) - usage: pv default: | type: template @@ -34,9 +32,7 @@ render: usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) - usage: battery default: | type: template @@ -50,7 +46,7 @@ render: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -78,8 +74,8 @@ params: default: choice: [] unit: - description: - help: Registriernummer des LG ESS HOME Wechselrichters. + description: Registriernummer + help: Nummer des LG ESS HOME Wechselrichters. advanced: true optional: true - name: capacity diff --git a/templates/release/de/meter/lg-ess-home-8-10.yaml b/templates/release/de/meter/lg-ess-home-8-10.yaml index de2cd7e286..850c22d28a 100644 --- a/templates/release/de/meter/lg-ess-home-8-10.yaml +++ b/templates/release/de/meter/lg-ess-home-8-10.yaml @@ -21,9 +21,7 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) - usage: pv default: | type: template @@ -37,9 +35,7 @@ render: usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) - usage: battery default: | type: template @@ -53,7 +49,7 @@ render: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Benutzerpasswort, siehe https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alternativ kann die Registriernummer für Administratorlogin verwendet werden. (optional) - registration: DE200... # Registriernummer des LG ESS HOME Wechselrichters. (optional) + registration: DE200... # Registriernummer, Nummer des LG ESS HOME Wechselrichters. (optional) capacity: 50 # Akkukapazität (kWh), optional minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -81,8 +77,8 @@ params: default: choice: [] unit: - description: - help: Registriernummer des LG ESS HOME Wechselrichters. + description: Registriernummer + help: Nummer des LG ESS HOME Wechselrichters. advanced: true optional: true - name: capacity diff --git a/templates/release/de/meter/m-tec-energy-butler-gen2.yaml b/templates/release/de/meter/m-tec-energy-butler-gen2.yaml index d4e337c9b1..0e9f5ecf56 100644 --- a/templates/release/de/meter/m-tec-energy-butler-gen2.yaml +++ b/templates/release/de/meter/m-tec-energy-butler-gen2.yaml @@ -64,7 +64,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/m-tec-energy-butler-gen3.yaml b/templates/release/de/meter/m-tec-energy-butler-gen3.yaml index fb70968588..972a918717 100644 --- a/templates/release/de/meter/m-tec-energy-butler-gen3.yaml +++ b/templates/release/de/meter/m-tec-energy-butler-gen3.yaml @@ -153,7 +153,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/marstek-venus-battery-storage.yaml b/templates/release/de/meter/marstek-venus-battery-storage.yaml index e1cc5d92a3..dd87bddb3b 100644 --- a/templates/release/de/meter/marstek-venus-battery-storage.yaml +++ b/templates/release/de/meter/marstek-venus-battery-storage.yaml @@ -42,17 +42,17 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 5.12 # Akkukapazität (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - minsoc: 11 # Venus kann nur bis 11% entladen werden. (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) + minsoc: 11 # Minimaler Ladestand (%), Venus kann nur bis 11% entladen werden. (optional) maxsoc: 100 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - maxchargepower: 2500 # Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus. (W), Für erzwungenes Laden des Speichers. (optional) - work_mode_normal: 1 # Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung., optional + maxchargepower: 2500 # Maximale Ladeleistung (W), 2500W ist das Maximum für Venus. (optional) + work_mode_normal: 1 # Work mode für Normal-Modus, 0=manuell, 1=Eigenverbrauch, 2=AI-Optimierung. (optional) params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -66,12 +66,12 @@ params: advanced: false optional: true - name: minsoc - example: 25 + example: 11 default: 11 choice: [] unit: '%' - description: Venus kann nur bis 11% entladen werden. - help: Untere Grenze beim Entladen der Batterie im normalen Betrieb + description: Minimaler Ladestand + help: Venus kann nur bis 11% entladen werden. advanced: true optional: true - name: maxsoc @@ -88,8 +88,8 @@ params: default: 2500 choice: [] unit: W - description: Ladeleistung in Watt für den Charge-Modus. 2500W ist das Maximum für Venus. - help: Für erzwungenes Laden des Speichers. + description: Maximale Ladeleistung + help: 2500W ist das Maximum für Venus. advanced: true optional: true - name: work_mode_normal @@ -97,8 +97,8 @@ params: default: 1 choice: [] unit: - description: Work mode für Normal-Modus. 0 manuell, 1 Eigenverbrauch, 2 AI-Optimierung. - help: + description: Work mode für Normal-Modus + help: 0=manuell, 1=Eigenverbrauch, 2=AI-Optimierung. advanced: true optional: true modbus: diff --git a/templates/release/de/meter/my-pv-wifi-meter.yaml b/templates/release/de/meter/my-pv-wifi-meter.yaml index 01129aa7e8..a03ea2b1f2 100644 --- a/templates/release/de/meter/my-pv-wifi-meter.yaml +++ b/templates/release/de/meter/my-pv-wifi-meter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/openems.yaml b/templates/release/de/meter/openems.yaml index ae8047f1ec..f22126abc2 100644 --- a/templates/release/de/meter/openems.yaml +++ b/templates/release/de/meter/openems.yaml @@ -44,8 +44,8 @@ render: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: user # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - battery: ess0 # steuerbare Batterie Komponente (optional) - watchdog: 60s # abgestimmt auf das API-Timeout (optional) + battery: ess0 # Steuerbare Batterie Komponente, optional + watchdog: 60s # Watchdog, abgestimmt auf das API-Timeout (optional) capacity: 50 # Akkukapazität (kWh), optional params: - name: host @@ -71,8 +71,8 @@ params: default: choice: [] unit: - description: - help: steuerbare Batterie Komponente + description: Steuerbare Batterie Komponente + help: advanced: true optional: true - name: watchdog @@ -80,7 +80,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: abgestimmt auf das API-Timeout advanced: true optional: true diff --git a/templates/release/de/meter/orno-or-we-516.yaml b/templates/release/de/meter/orno-or-we-516.yaml index e5828f01eb..7683a5384b 100644 --- a/templates/release/de/meter/orno-or-we-516.yaml +++ b/templates/release/de/meter/orno-or-we-516.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/orno-or-we-517.yaml b/templates/release/de/meter/orno-or-we-517.yaml index 84efc46ba1..a47ee96e06 100644 --- a/templates/release/de/meter/orno-or-we-517.yaml +++ b/templates/release/de/meter/orno-or-we-517.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/plexlog.yaml b/templates/release/de/meter/plexlog.yaml index 3ff2cfe6d7..f68f2309cd 100644 --- a/templates/release/de/meter/plexlog.yaml +++ b/templates/release/de/meter/plexlog.yaml @@ -76,7 +76,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/powerdog.yaml b/templates/release/de/meter/powerdog.yaml index 5ec0e5a171..13dc3e7366 100644 --- a/templates/release/de/meter/powerdog.yaml +++ b/templates/release/de/meter/powerdog.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/powerfox-poweropti.yaml b/templates/release/de/meter/powerfox-poweropti.yaml index e22397a646..880199f485 100644 --- a/templates/release/de/meter/powerfox-poweropti.yaml +++ b/templates/release/de/meter/powerfox-poweropti.yaml @@ -17,7 +17,7 @@ render: usage: grid user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti + id: main # ID, Id im Falle mehrerer PowerOpti - usage: pv default: | type: template @@ -31,7 +31,7 @@ render: usage: pv user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - id: main # Id im Falle mehrerer PowerOpti + id: main # ID, Id im Falle mehrerer PowerOpti params: - name: user example: @@ -56,7 +56,7 @@ params: default: main choice: [] unit: - description: + description: ID help: Id im Falle mehrerer PowerOpti advanced: true optional: false \ No newline at end of file diff --git a/templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml b/templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml index e4a1101455..f065eb4bce 100644 --- a/templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml +++ b/templates/release/de/meter/qcells-q-home-ess-hyb-g3.yaml @@ -29,7 +29,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) advanced: | type: template template: solax @@ -53,8 +53,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional - usage: pv default: | type: template @@ -79,7 +79,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) advanced: | type: template template: solax @@ -103,8 +103,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -130,7 +130,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) advanced: | type: template template: solax @@ -154,8 +154,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) params: @@ -164,7 +164,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -173,8 +173,8 @@ params: default: false choice: [] unit: - description: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) - help: + description: Dritter PV-Eingang + help: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) advanced: false optional: true - name: storageunit @@ -182,7 +182,7 @@ params: default: 1 choice: [] unit: - description: + description: Nummer des Batteriespeichers help: advanced: true optional: true diff --git a/templates/release/de/meter/rct-power.yaml b/templates/release/de/meter/rct-power.yaml index ec64bcf2e4..a85acde75b 100644 --- a/templates/release/de/meter/rct-power.yaml +++ b/templates/release/de/meter/rct-power.yaml @@ -16,10 +16,7 @@ render: template: rct-power usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) - usage: pv default: | type: template @@ -31,8 +28,6 @@ render: template: rct-power usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - minsoc: 7 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) - usage: battery @@ -51,7 +46,6 @@ render: maxsoc: 97 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) maxchargepower: # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - externalpower: # Externe Leistung, Externe Leistung aller an S0 angeschlossenen Geräte abfragen (optional) params: - name: host example: 192.0.2.2 diff --git a/templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml b/templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml index 7a300b29b2..329f985de5 100644 --- a/templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml +++ b/templates/release/de/meter/saia-burgess-controls-sbc-ale3.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml b/templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml index 5d50d6befe..ebba403e8c 100644 --- a/templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml +++ b/templates/release/de/meter/saia-burgess-controls-sbc-awd3.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml b/templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml index 54c49a08c9..229faa0619 100644 --- a/templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml +++ b/templates/release/de/meter/saj-h1-series-hybrid-solar-inverter.yaml @@ -80,7 +80,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml b/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml index 8195e1293d..da618747c2 100644 --- a/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml +++ b/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml @@ -51,8 +51,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: pv default: | type: template @@ -100,8 +98,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: battery default: | type: template @@ -159,7 +155,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/saj-r5-series-solar-inverter.yaml b/templates/release/de/meter/saj-r5-series-solar-inverter.yaml index 7ebc2899e9..fd78d22c6c 100644 --- a/templates/release/de/meter/saj-r5-series-solar-inverter.yaml +++ b/templates/release/de/meter/saj-r5-series-solar-inverter.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sax-homespeicher.yaml b/templates/release/de/meter/sax-homespeicher.yaml index b81b514f91..01f7d29c72 100644 --- a/templates/release/de/meter/sax-homespeicher.yaml +++ b/templates/release/de/meter/sax-homespeicher.yaml @@ -32,7 +32,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml b/templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml index c57a0d25eb..14be7ebc94 100644 --- a/templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml +++ b/templates/release/de/meter/schneider-electric-iem3xxx-modbus.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/senec-home.yaml b/templates/release/de/meter/senec-home.yaml index 6dbe28eab0..1653680131 100644 --- a/templates/release/de/meter/senec-home.yaml +++ b/templates/release/de/meter/senec-home.yaml @@ -11,39 +11,39 @@ render: template: senec-home usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) advanced: | type: template template: senec-home usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) - usage: pv default: | type: template template: senec-home usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) advanced: | type: template template: senec-home usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) - usage: battery default: | type: template template: senec-home usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) advanced: | type: template template: senec-home usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) capacity: 50 # Akkukapazität (kWh), optional params: - name: host @@ -60,7 +60,7 @@ params: default: https choice: ['https', 'http'] unit: - description: + description: Schema help: advanced: false optional: true diff --git a/templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml b/templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml index f54338773c..824bc8cf4c 100644 --- a/templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml +++ b/templates/release/de/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/shelly-1pm-mini.yaml b/templates/release/de/meter/shelly-1pm-mini.yaml index 09f2db5ed3..bbd8ea9b0a 100644 --- a/templates/release/de/meter/shelly-1pm-mini.yaml +++ b/templates/release/de/meter/shelly-1pm-mini.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-1pm.yaml b/templates/release/de/meter/shelly-1pm.yaml index 07008d87c7..e7a37b78ac 100644 --- a/templates/release/de/meter/shelly-1pm.yaml +++ b/templates/release/de/meter/shelly-1pm.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-em.yaml b/templates/release/de/meter/shelly-em.yaml index 23bea3a866..935e03a4f0 100644 --- a/templates/release/de/meter/shelly-em.yaml +++ b/templates/release/de/meter/shelly-em.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-plug-s.yaml b/templates/release/de/meter/shelly-plug-s.yaml index 9a5d074588..ac36b43a48 100644 --- a/templates/release/de/meter/shelly-plug-s.yaml +++ b/templates/release/de/meter/shelly-plug-s.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pm-mini.yaml b/templates/release/de/meter/shelly-pm-mini.yaml index 715f252acb..e3e29f3ba3 100644 --- a/templates/release/de/meter/shelly-pm-mini.yaml +++ b/templates/release/de/meter/shelly-pm-mini.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pro-1pm.yaml b/templates/release/de/meter/shelly-pro-1pm.yaml index acb79b4c71..867e84f615 100644 --- a/templates/release/de/meter/shelly-pro-1pm.yaml +++ b/templates/release/de/meter/shelly-pro-1pm.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml b/templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml index 5b9a3446ce..07ca0d2ec0 100644 --- a/templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml +++ b/templates/release/de/meter/shelly-pro-3em-monophase-mode.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/shelly-pro-em.yaml b/templates/release/de/meter/shelly-pro-em.yaml index f644bc9d16..1e872f545f 100644 --- a/templates/release/de/meter/shelly-pro-em.yaml +++ b/templates/release/de/meter/shelly-pro-em.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) - channel: 0 # optional + channel: 0 # Kanal, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Kanal help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/siemens-7kt1665.yaml b/templates/release/de/meter/siemens-7kt1665.yaml index f5dbf9221f..6da9b0beea 100644 --- a/templates/release/de/meter/siemens-7kt1665.yaml +++ b/templates/release/de/meter/siemens-7kt1665.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/siemens-junelight-smart-battery.yaml b/templates/release/de/meter/siemens-junelight-smart-battery.yaml index 795dbeb72c..3b7af8f1f3 100644 --- a/templates/release/de/meter/siemens-junelight-smart-battery.yaml +++ b/templates/release/de/meter/siemens-junelight-smart-battery.yaml @@ -77,7 +77,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/siemens-pac-2200.yaml b/templates/release/de/meter/siemens-pac-2200.yaml index d508896cb5..2f6bb7a924 100644 --- a/templates/release/de/meter/siemens-pac-2200.yaml +++ b/templates/release/de/meter/siemens-pac-2200.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml b/templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml index 8a39e5d207..cfe9bf7413 100644 --- a/templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml +++ b/templates/release/de/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml @@ -13,14 +13,14 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional advanced: | type: template template: sigenergy usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional - usage: pv default: | type: template @@ -28,14 +28,14 @@ render: usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional advanced: | type: template template: sigenergy usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional - usage: battery default: | type: template @@ -43,14 +43,14 @@ render: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional advanced: | type: template template: sigenergy usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional capacity: 50 # Akkukapazität (kWh), optional params: - name: host @@ -76,7 +76,7 @@ params: default: 1 choice: [] unit: - description: + description: ID help: advanced: false optional: true diff --git a/templates/release/de/meter/sma-data-manager.yaml b/templates/release/de/meter/sma-data-manager.yaml index 45b70ffb2f..4c11da87ee 100644 --- a/templates/release/de/meter/sma-data-manager.yaml +++ b/templates/release/de/meter/sma-data-manager.yaml @@ -76,7 +76,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml b/templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml index 8dccb69d36..d9ee397973 100644 --- a/templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml +++ b/templates/release/de/meter/sma-smart-energy-hybrid-inverter.yaml @@ -50,14 +50,14 @@ render: port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: Der ModbusTCP Server muss aktiviert sein. advanced: false optional: true @@ -93,7 +93,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml b/templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml index 8cd1a32f45..209cebbb08 100644 --- a/templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml +++ b/templates/release/de/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml @@ -28,14 +28,14 @@ render: port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: Der ModbusTCP Server muss aktiviert sein. advanced: false optional: true @@ -62,7 +62,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml b/templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml index e311fc4697..ca7de8047c 100644 --- a/templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml +++ b/templates/release/de/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml @@ -28,14 +28,14 @@ render: port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: Der ModbusTCP Server muss aktiviert sein. advanced: false optional: true @@ -62,7 +62,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/sma-sunny-island-modbus.yaml b/templates/release/de/meter/sma-sunny-island-modbus.yaml index 1f28350869..be7bc123e1 100644 --- a/templates/release/de/meter/sma-sunny-island-modbus.yaml +++ b/templates/release/de/meter/sma-sunny-island-modbus.yaml @@ -28,14 +28,14 @@ render: port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 4200 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: Der ModbusTCP Server muss aktiviert sein. advanced: false optional: true @@ -62,7 +62,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/sma-webbox.yaml b/templates/release/de/meter/sma-webbox.yaml index 496c6f88e8..42781b632c 100644 --- a/templates/release/de/meter/sma-webbox.yaml +++ b/templates/release/de/meter/sma-webbox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: Der ModbusTCP Server muss aktiviert sein. advanced: false optional: true diff --git a/templates/release/de/meter/sma-wechselrichter-modbus.yaml b/templates/release/de/meter/sma-wechselrichter-modbus.yaml index 4c32d326ff..53b65db082 100644 --- a/templates/release/de/meter/sma-wechselrichter-modbus.yaml +++ b/templates/release/de/meter/sma-wechselrichter-modbus.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: Der ModbusTCP Server muss aktiviert sein. advanced: false optional: true diff --git a/templates/release/de/meter/sofarsolar-hybrid-inverter.yaml b/templates/release/de/meter/sofarsolar-hybrid-inverter.yaml index f298b6c3d7..adbe1260ed 100644 --- a/templates/release/de/meter/sofarsolar-hybrid-inverter.yaml +++ b/templates/release/de/meter/sofarsolar-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml b/templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml index f5d640675e..655dde19f1 100644 --- a/templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml +++ b/templates/release/de/meter/sofarsolar-hyd-3-6k-ep.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + description: Nummer des Batteriespeichers + help: Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). advanced: true optional: true - name: capacity diff --git a/templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml b/templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml index b040741cf2..d401bdef7f 100644 --- a/templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml +++ b/templates/release/de/meter/sofarsolar-hyd-5-20k-3ph.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + description: Nummer des Batteriespeichers + help: Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). advanced: true optional: true - name: capacity diff --git a/templates/release/de/meter/sofarsolar-inverter.yaml b/templates/release/de/meter/sofarsolar-inverter.yaml index 8b1ca89011..8e50426561 100644 --- a/templates/release/de/meter/sofarsolar-inverter.yaml +++ b/templates/release/de/meter/sofarsolar-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml b/templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml index 77d0626980..4dd2d58346 100644 --- a/templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml +++ b/templates/release/de/meter/sofarsolar-sofar-5-24ktl-g3.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + description: Nummer des Batteriespeichers + help: Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). advanced: true optional: true - name: capacity diff --git a/templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml b/templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml index 400591f37b..cf449b68ab 100644 --- a/templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml +++ b/templates/release/de/meter/sofarsolar-sofar-80-136ktl.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) + storageunit: 1 # Nummer des Batteriespeichers, Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). (optional) capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Gültige Werte sind 0 (Eigenbedarfsmodus), 1 (Nutzungszeitmodus), 2 (Zeitmodus), 4 (Peak-shaving Modus) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Nummer des Batteriespeichers. Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). + description: Nummer des Batteriespeichers + help: Im Fall eines BTS Speichers nicht die Adresse eines BTS 5K Batteriemodules, sondern der Speicherturm (BTS 5K-BDU Steuerungseinheit mit 1-4 BTS 5K Modulen). advanced: true optional: true - name: capacity diff --git a/templates/release/de/meter/solaredge-hybrid-inverter.yaml b/templates/release/de/meter/solaredge-hybrid-inverter.yaml index 3d0fd7df2f..f57f083594 100644 --- a/templates/release/de/meter/solaredge-hybrid-inverter.yaml +++ b/templates/release/de/meter/solaredge-hybrid-inverter.yaml @@ -58,7 +58,7 @@ render: host: 192.0.2.2 # Hostname port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: pv default: | type: template @@ -109,7 +109,7 @@ render: port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -160,14 +160,14 @@ render: port: 1502 # Port timeout: 10s # Zeitüberschreitung, optional capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -203,7 +203,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/solaredge-inverter.yaml b/templates/release/de/meter/solaredge-inverter.yaml index 0749031c49..11db5eca1b 100644 --- a/templates/release/de/meter/solaredge-inverter.yaml +++ b/templates/release/de/meter/solaredge-inverter.yaml @@ -62,7 +62,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml b/templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml index bc3b9188cd..14206ad0eb 100644 --- a/templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml +++ b/templates/release/de/meter/solarmax-max-storage-max-storage-ultimate.yaml @@ -28,7 +28,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: pv default: | type: template @@ -51,7 +51,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -74,14 +74,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -108,7 +108,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/de/meter/solarmax-solarmax-smt.yaml b/templates/release/de/meter/solarmax-solarmax-smt.yaml index f28a6b03f5..5c872413f6 100644 --- a/templates/release/de/meter/solarmax-solarmax-smt.yaml +++ b/templates/release/de/meter/solarmax-solarmax-smt.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/solarmax-sp-series-inverter.yaml b/templates/release/de/meter/solarmax-sp-series-inverter.yaml index 430c460089..0d41a2fa45 100644 --- a/templates/release/de/meter/solarmax-sp-series-inverter.yaml +++ b/templates/release/de/meter/solarmax-sp-series-inverter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml b/templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml index cd686566dd..c4679b271b 100644 --- a/templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml +++ b/templates/release/de/meter/solax-hybrid-x1-x3-g3-g4.yaml @@ -29,7 +29,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) advanced: | type: template template: solax @@ -53,8 +53,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional - usage: pv default: | type: template @@ -79,7 +79,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) advanced: | type: template template: solax @@ -103,8 +103,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -130,7 +130,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) advanced: | type: template template: solax @@ -154,8 +154,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # Der Wechselrichter hat einen dritten PV-Eingang (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional defaultmode: 0 # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. (optional) params: @@ -164,7 +164,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -173,8 +173,8 @@ params: default: false choice: [] unit: - description: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) - help: + description: Dritter PV-Eingang + help: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) advanced: false optional: true - name: storageunit @@ -182,7 +182,7 @@ params: default: 1 choice: [] unit: - description: + description: Nummer des Batteriespeichers help: advanced: true optional: true diff --git a/templates/release/de/meter/solinteng.yaml b/templates/release/de/meter/solinteng.yaml index 3f1385cf13..4a656b7757 100644 --- a/templates/release/de/meter/solinteng.yaml +++ b/templates/release/de/meter/solinteng.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional + delay: 100ms # Verzögerung, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Verzögerung help: advanced: true optional: true diff --git a/templates/release/de/meter/sonnen-sonnenbatterie.yaml b/templates/release/de/meter/sonnen-sonnenbatterie.yaml index 8c7709f177..7a6600d6e9 100644 --- a/templates/release/de/meter/sonnen-sonnenbatterie.yaml +++ b/templates/release/de/meter/sonnen-sonnenbatterie.yaml @@ -43,14 +43,14 @@ render: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional) + token: # Token, API Token (benötigt für aktive Batteriesteuerung) (optional) advanced: | type: template template: sonnenbatterie usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname port: 8080 # Port, optional - token: # API Token (benötigt für aktive Batteriesteuerung) (optional) + token: # Token, API Token (benötigt für aktive Batteriesteuerung) (optional) capacity: 50 # Akkukapazität (kWh), optional maxchargepower: 3300 # Maximale Ladeleistung (W), Für erzwungenes Laden des Speichers. (optional) defaultmode: self-consumption # Standardmodus für die aktive Batteriesteuerung, Wechselrichter fällt nach einem Laden des Speichers oder Unterbinden der Entladung zurück auf diesen Modus. [self-consumption, time-of-use] @@ -78,7 +78,7 @@ params: default: choice: [] unit: - description: + description: Token help: API Token (benötigt für aktive Batteriesteuerung) advanced: false optional: true diff --git a/templates/release/de/meter/st-ems.yaml b/templates/release/de/meter/st-ems.yaml index cbc6161fe6..f4f90bf5f1 100644 --- a/templates/release/de/meter/st-ems.yaml +++ b/templates/release/de/meter/st-ems.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional + delay: 100ms # Verzögerung, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Verzögerung help: advanced: true optional: true diff --git a/templates/release/de/meter/sungrow-sg-series-inverter.yaml b/templates/release/de/meter/sungrow-sg-series-inverter.yaml index 5616956caf..b964c24ab4 100644 --- a/templates/release/de/meter/sungrow-sg-series-inverter.yaml +++ b/templates/release/de/meter/sungrow-sg-series-inverter.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml b/templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml index d9153452b0..0d287b4467 100644 --- a/templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml +++ b/templates/release/de/meter/sungrow-sh-series-hybrid-inverter.yaml @@ -163,7 +163,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunspec-battery-model-124.yaml b/templates/release/de/meter/sunspec-battery-model-124.yaml index 81ce04bb59..f31c280b63 100644 --- a/templates/release/de/meter/sunspec-battery-model-124.yaml +++ b/templates/release/de/meter/sunspec-battery-model-124.yaml @@ -60,7 +60,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunspec-battery-model-802.yaml b/templates/release/de/meter/sunspec-battery-model-802.yaml index 9852433270..56ec4b0eb0 100644 --- a/templates/release/de/meter/sunspec-battery-model-802.yaml +++ b/templates/release/de/meter/sunspec-battery-model-802.yaml @@ -61,7 +61,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunspec-hybrid-inverter.yaml b/templates/release/de/meter/sunspec-hybrid-inverter.yaml index 26d7635bdd..78c482bb95 100644 --- a/templates/release/de/meter/sunspec-hybrid-inverter.yaml +++ b/templates/release/de/meter/sunspec-hybrid-inverter.yaml @@ -153,7 +153,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunspec-inverter.yaml b/templates/release/de/meter/sunspec-inverter.yaml index ffcfa39f00..f46a7bd8ac 100644 --- a/templates/release/de/meter/sunspec-inverter.yaml +++ b/templates/release/de/meter/sunspec-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunspec-meter.yaml b/templates/release/de/meter/sunspec-meter.yaml index dcfe6f9db0..8e9782d482 100644 --- a/templates/release/de/meter/sunspec-meter.yaml +++ b/templates/release/de/meter/sunspec-meter.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml b/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml index 294c2c5e24..4ddc175750 100644 --- a/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml +++ b/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml b/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml index d713276792..7cf237da68 100644 --- a/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml +++ b/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml @@ -52,9 +52,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - usage: pv default: | @@ -103,9 +101,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + storageunit: 1 # Nummer des Batteriespeichers, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional - usage: battery @@ -155,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Nummer des Batteriespeichers, optional capacity: 50 # Akkukapazität (kWh), optional minsoc: 20 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) @@ -166,7 +162,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -175,7 +171,7 @@ params: default: 1 choice: [] unit: - description: + description: Nummer des Batteriespeichers help: advanced: true optional: true diff --git a/templates/release/de/meter/sunsynk-micro-inverter.yaml b/templates/release/de/meter/sunsynk-micro-inverter.yaml index 69b8cde633..029a238372 100644 --- a/templates/release/de/meter/sunsynk-micro-inverter.yaml +++ b/templates/release/de/meter/sunsynk-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: true optional: true diff --git a/templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml b/templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml index 8a9e93a574..6df9f4f049 100644 --- a/templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml +++ b/templates/release/de/meter/sunsynk-storage-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunsynk-string-inverter.yaml b/templates/release/de/meter/sunsynk-string-inverter.yaml index ed15c76121..5ecd781508 100644 --- a/templates/release/de/meter/sunsynk-string-inverter.yaml +++ b/templates/release/de/meter/sunsynk-string-inverter.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/sunway.yaml b/templates/release/de/meter/sunway.yaml index 6e6d696f8a..1ebea79f78 100644 --- a/templates/release/de/meter/sunway.yaml +++ b/templates/release/de/meter/sunway.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional + delay: 100ms # Verzögerung, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Verzögerung help: advanced: true optional: true diff --git a/templates/release/de/meter/tesla-powerwall.yaml b/templates/release/de/meter/tesla-powerwall.yaml index fef95c3956..6fbd8bce9c 100644 --- a/templates/release/de/meter/tesla-powerwall.yaml +++ b/templates/release/de/meter/tesla-powerwall.yaml @@ -20,18 +20,16 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) advanced: | type: template template: tesla-powerwall usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - usage: pv default: | type: template @@ -39,18 +37,16 @@ render: usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) advanced: | type: template template: tesla-powerwall usage: pv host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) - usage: battery default: | type: template @@ -58,16 +54,16 @@ render: usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) advanced: | type: template template: tesla-powerwall usage: battery host: 192.0.2.2 # IP-Adresse oder Hostname password: # Passwort, Passwort des Benutzers "Kunde". Default sind die letzten 5 Zeichen des auf dem Tesla Gateway genannten Passworts. - refreshToken: # optional - siteId: # optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (optional) minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) params: @@ -94,7 +90,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: true @@ -103,7 +99,7 @@ params: default: choice: [] unit: - description: + description: Site ID help: optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung advanced: false optional: true diff --git a/templates/release/de/meter/tibber-pulse.yaml b/templates/release/de/meter/tibber-pulse.yaml index a81ed20044..ef324fdd33 100644 --- a/templates/release/de/meter/tibber-pulse.yaml +++ b/templates/release/de/meter/tibber-pulse.yaml @@ -10,15 +10,15 @@ render: type: template template: tibber-pulse usage: grid - token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE - homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional params: - name: token example: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: Home ID help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/meter/victron-em24.yaml b/templates/release/de/meter/victron-em24.yaml index 9afe506784..2971591ab0 100644 --- a/templates/release/de/meter/victron-em24.yaml +++ b/templates/release/de/meter/victron-em24.yaml @@ -49,7 +49,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/victron-em24_e1.yaml b/templates/release/de/meter/victron-em24_e1.yaml index e4d65fa572..2539a16e10 100644 --- a/templates/release/de/meter/victron-em24_e1.yaml +++ b/templates/release/de/meter/victron-em24_e1.yaml @@ -36,7 +36,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/victron-em530-em540.yaml b/templates/release/de/meter/victron-em530-em540.yaml index 57fc28e720..89b53122e2 100644 --- a/templates/release/de/meter/victron-em530-em540.yaml +++ b/templates/release/de/meter/victron-em530-em540.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/victron-energy.yaml b/templates/release/de/meter/victron-energy.yaml index ee5827d500..7e854c89bf 100644 --- a/templates/release/de/meter/victron-energy.yaml +++ b/templates/release/de/meter/victron-energy.yaml @@ -14,16 +14,14 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) + meterid: # Grid-Energiezähler VRM Instanz, Kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) advanced: | type: template template: victron-energy usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional - meterid: # Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) + meterid: # Grid-Energiezähler VRM Instanz, Kann im VRM Portal oder im RemoteUI ausgelesen werden. (optional) - usage: pv default: | type: template @@ -38,8 +36,6 @@ render: host: 192.0.2.2 # IP-Adresse oder Hostname port: 502 # Port, optional maxacpower: 0 # Maximale AC Leistung des Hybrid-Wechselrichters (W), optional - minsoc: 25 # Minimaler Ladestand (%), Untere Grenze beim Entladen der Batterie im normalen Betrieb (optional) - maxsoc: 95 # Maximaler Ladestand (%), Oberes Limit beim Laden der Batterie aus dem Netz (optional) - usage: battery default: | type: template @@ -80,8 +76,8 @@ params: default: choice: [] unit: - description: - help: Grid-Energiezähler VRM instance- kann im VRM Portal oder im RemoteUI ausgelesen werden. + description: Grid-Energiezähler VRM Instanz + help: Kann im VRM Portal oder im RemoteUI ausgelesen werden. advanced: false optional: true - name: capacity diff --git a/templates/release/de/meter/victron-et340.yaml b/templates/release/de/meter/victron-et340.yaml index 0f3d3b8836..2dbd183e3d 100644 --- a/templates/release/de/meter/victron-et340.yaml +++ b/templates/release/de/meter/victron-et340.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/volkszahler-http-api-import-and-export.yaml b/templates/release/de/meter/volkszahler-http-api-import-and-export.yaml index b69b2f3e26..3eee2a1725 100644 --- a/templates/release/de/meter/volkszahler-http-api-import-and-export.yaml +++ b/templates/release/de/meter/volkszahler-http-api-import-and-export.yaml @@ -10,17 +10,17 @@ render: type: template template: volkszaehler-importexport usage: grid - url: # URL des "data" Kontexts der Volkszähler Middleware, Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data (optional) - importuuid: - exportuuid: + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID params: - name: url - example: + example: http://zaehler.network.local:8080/api/data default: choice: [] unit: - description: URL des "data" Kontexts der Volkszähler Middleware - help: 'Die URL ist zum Beispiel: http://zaehler.network.local:8080/api/data' + description: Middleware URL + help: advanced: false optional: true - name: importuuid @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Import UUID help: advanced: false optional: false @@ -37,7 +37,7 @@ params: default: choice: [] unit: - description: + description: Export UUID help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/meter/volkszahler-http-api.yaml b/templates/release/de/meter/volkszahler-http-api.yaml index 5e900f8251..db48294703 100644 --- a/templates/release/de/meter/volkszahler-http-api.yaml +++ b/templates/release/de/meter/volkszahler-http-api.yaml @@ -10,16 +10,16 @@ render: type: template template: volkszaehler-http usage: grid - url: # URL des "data" Kontexts der Volkszähler Middleware, Beispiel: http://zaehler.network.local:8080/api/data (optional) - uuid: + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID params: - name: url - example: + example: http://zaehler.network.local:8080/api/data default: choice: [] unit: - description: URL des "data" Kontexts der Volkszähler Middleware - help: 'Beispiel: http://zaehler.network.local:8080/api/data' + description: Middleware URL + help: advanced: false optional: true - name: uuid @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: UUID help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/meter/volkszahler-websocket-api.yaml b/templates/release/de/meter/volkszahler-websocket-api.yaml index 0aa20aac06..e9da5931d3 100644 --- a/templates/release/de/meter/volkszahler-websocket-api.yaml +++ b/templates/release/de/meter/volkszahler-websocket-api.yaml @@ -13,7 +13,7 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 8082 # Port, optional - uuid: + uuid: # UUID params: - name: host example: 192.0.2.2 @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: UUID help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/meter/vzlogger.yaml b/templates/release/de/meter/vzlogger.yaml index 0052aef453..9ad7763037 100644 --- a/templates/release/de/meter/vzlogger.yaml +++ b/templates/release/de/meter/vzlogger.yaml @@ -11,24 +11,24 @@ render: usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 8081 # Port, optional - uuid: + uuid: # UUID advanced: | type: template template: vzlogger usage: grid host: 192.0.2.2 # IP-Adresse oder Hostname port: 8081 # Port, optional - uuid: + uuid: # UUID scale: 1 # Skalierungsfaktor, Multipliziere Rohwert mit diesem Faktor (optional) - l1currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0), optional - l2currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0), optional - l3currentuuid: # Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0), optional - l1poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0), optional - l2poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0), optional - l3poweruuid: # Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0), optional - l1voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0), optional - l2voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0), optional - l3voltageuuid: # Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0), optional + l1currentuuid: # Strom in Phase 1, Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0) (optional) + l2currentuuid: # Strom in Phase 2, Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0) (optional) + l3currentuuid: # Strom in Phase 3, Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0) (optional) + l1poweruuid: # Leistung in Phase 1, Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0) (optional) + l2poweruuid: # Leistung in Phase 2, Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0) (optional) + l3poweruuid: # Leistung in Phase 3, Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0) (optional) + l1voltageuuid: # Spannung in Phase 1, Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0) (optional) + l2voltageuuid: # Spannung in Phase 2, Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0) (optional) + l3voltageuuid: # Spannung in Phase 3, Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0) (optional) cache: 1s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) params: - name: host @@ -54,7 +54,7 @@ params: default: choice: [] unit: - description: + description: UUID help: advanced: false optional: false @@ -72,8 +72,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0) - help: + description: Strom in Phase 1 + help: Die vzlogger Kanal uuid für Strom in Phase 1 (OBIS Code 31.7.0) advanced: true optional: true - name: l2currentuuid @@ -81,8 +81,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0) - help: + description: Strom in Phase 2 + help: Die vzlogger Kanal uuid für Strom in Phase 2 (OBIS Code 51.7.0) advanced: true optional: true - name: l3currentuuid @@ -90,8 +90,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0) - help: + description: Strom in Phase 3 + help: Die vzlogger Kanal uuid für Strom in Phase 3 (OBIS Code 71.7.0) advanced: true optional: true - name: l1poweruuid @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0) - help: + description: Leistung in Phase 1 + help: Die vzlogger Kanal uuid für Leistung in Phase 1 (OBIS Code 36.7.0) advanced: true optional: true - name: l2poweruuid @@ -108,8 +108,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0) - help: + description: Leistung in Phase 2 + help: Die vzlogger Kanal uuid für Leistung in Phase 2 (OBIS Code 56.7.0) advanced: true optional: true - name: l3poweruuid @@ -117,8 +117,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0) - help: + description: Leistung in Phase 3 + help: Die vzlogger Kanal uuid für Leistung in Phase 3 (OBIS Code 76.7.0) advanced: true optional: true - name: l1voltageuuid @@ -126,8 +126,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0) - help: + description: Spannung in Phase 1 + help: Die vzlogger Kanal uuid für Spannung in Phase 1 (OBIS Code 32.7.0) advanced: true optional: true - name: l2voltageuuid @@ -135,8 +135,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0) - help: + description: Spannung in Phase 2 + help: Die vzlogger Kanal uuid für Spannung in Phase 2 (OBIS Code 52.7.0) advanced: true optional: true - name: l3voltageuuid @@ -144,8 +144,8 @@ params: default: choice: [] unit: - description: Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0) - help: + description: Spannung in Phase 3 + help: Die vzlogger Kanal uuid für Spannung in Phase 3 (OBIS Code 72.7.0) advanced: true optional: true - name: cache diff --git a/templates/release/de/meter/wago-879-30xx.yaml b/templates/release/de/meter/wago-879-30xx.yaml index 9e3a3ece70..1119969cec 100644 --- a/templates/release/de/meter/wago-879-30xx.yaml +++ b/templates/release/de/meter/wago-879-30xx.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/wattsonic.yaml b/templates/release/de/meter/wattsonic.yaml index 30cae19580..3db4e66660 100644 --- a/templates/release/de/meter/wattsonic.yaml +++ b/templates/release/de/meter/wattsonic.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Verzögerung, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Akkukapazität (kWh), optional - delay: 100ms # optional + delay: 100ms # Verzögerung, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Verzögerung help: advanced: true optional: true diff --git a/templates/release/de/meter/weidmuller-em110-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em110-rtu-2p.yaml index e5d38d0886..9ac0b5ea9c 100644 --- a/templates/release/de/meter/weidmuller-em110-rtu-2p.yaml +++ b/templates/release/de/meter/weidmuller-em110-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/weidmuller-em111-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em111-rtu-2p.yaml index 07c0b80e23..a360a8fab7 100644 --- a/templates/release/de/meter/weidmuller-em111-rtu-2p.yaml +++ b/templates/release/de/meter/weidmuller-em111-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/weidmuller-em120-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em120-rtu-2p.yaml index b1cb3fc002..4f239fd568 100644 --- a/templates/release/de/meter/weidmuller-em120-rtu-2p.yaml +++ b/templates/release/de/meter/weidmuller-em120-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/weidmuller-em122-rtu-2p.yaml b/templates/release/de/meter/weidmuller-em122-rtu-2p.yaml index 415863aac2..5ec5b3cb56 100644 --- a/templates/release/de/meter/weidmuller-em122-rtu-2p.yaml +++ b/templates/release/de/meter/weidmuller-em122-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml b/templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml index 3afd3d3dcc..6948af583f 100644 --- a/templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml +++ b/templates/release/de/meter/zcs-azzurro-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/zcs-azzurro-inverter.yaml b/templates/release/de/meter/zcs-azzurro-inverter.yaml index deb238c7c5..8e5f535b1c 100644 --- a/templates/release/de/meter/zcs-azzurro-inverter.yaml +++ b/templates/release/de/meter/zcs-azzurro-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Typ help: advanced: false optional: true diff --git a/templates/release/de/meter/zendure-hyper-2000.yaml b/templates/release/de/meter/zendure-hyper-2000.yaml index c950cc883f..79729c2591 100644 --- a/templates/release/de/meter/zendure-hyper-2000.yaml +++ b/templates/release/de/meter/zendure-hyper-2000.yaml @@ -10,34 +10,34 @@ render: type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional advanced: | type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional - usage: battery default: | type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional advanced: | type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # Zu finden in der Zendure App in den Einstellungen des Geräts - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Seriennummer, Zu finden in der Zendure App in den Einstellungen des Geräts + region: EU # Region, [EU, Global] timeout: 10s # Zeitüberschreitung, optional capacity: 2 # Akkukapazität (kWh), optional params: @@ -46,7 +46,7 @@ params: default: choice: [] unit: - description: + description: Account ID help: advanced: false optional: false @@ -55,7 +55,7 @@ params: default: choice: [] unit: - description: + description: Seriennummer help: Zu finden in der Zendure App in den Einstellungen des Geräts advanced: false optional: false @@ -64,7 +64,7 @@ params: default: EU choice: ['EU', 'Global'] unit: - description: + description: Region help: advanced: false optional: false diff --git a/templates/release/de/tariff/amber-electric.yaml b/templates/release/de/tariff/amber-electric.yaml index 40b4f8c86e..fd644ed4d3 100644 --- a/templates/release/de/tariff/amber-electric.yaml +++ b/templates/release/de/tariff/amber-electric.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: amber - token: # optional - siteid: # optional - channel: # optional + token: # Token, optional + siteid: # Site ID, optional + channel: # Kanal, optional advanced: | type: template template: amber - token: # optional - siteid: # optional - channel: # optional + token: # Token, optional + siteid: # Site ID, optional + channel: # Kanal, optional charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -26,7 +26,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true @@ -35,7 +35,7 @@ params: default: choice: [] unit: - description: + description: Site ID help: advanced: false optional: true @@ -44,7 +44,7 @@ params: default: choice: [] unit: - description: + description: Kanal help: advanced: false optional: true diff --git a/templates/release/de/tariff/awattar.yaml b/templates/release/de/tariff/awattar.yaml index b1861bcbfb..f777a8d052 100644 --- a/templates/release/de/tariff/awattar.yaml +++ b/templates/release/de/tariff/awattar.yaml @@ -8,11 +8,11 @@ render: - default: | type: template template: awattar - region: AT # [DE, AT] + region: AT # Region, [DE, AT] advanced: | type: template template: awattar - region: AT # [DE, AT] + region: AT # Region, [DE, AT] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -22,7 +22,7 @@ params: default: choice: ['DE', 'AT'] unit: - description: + description: Region help: advanced: false optional: false diff --git a/templates/release/de/tariff/electricity-maps-commercial-api.yaml b/templates/release/de/tariff/electricity-maps-commercial-api.yaml index 12eb3a2963..d6611e761f 100644 --- a/templates/release/de/tariff/electricity-maps-commercial-api.yaml +++ b/templates/release/de/tariff/electricity-maps-commercial-api.yaml @@ -12,8 +12,8 @@ render: type: template template: electricitymaps uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) Adresse - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones + token: # Token + zone: DE # Zone, siehe https://api.electricitymap.org/v3/zones params: - name: uri example: https://api-access.electricitymaps.com/2w...1g/ @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Zone help: siehe https://api.electricitymap.org/v3/zones advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/tariff/electricity-maps-free-api.yaml b/templates/release/de/tariff/electricity-maps-free-api.yaml index 8b258cf02b..5e0534254a 100644 --- a/templates/release/de/tariff/electricity-maps-free-api.yaml +++ b/templates/release/de/tariff/electricity-maps-free-api.yaml @@ -11,15 +11,15 @@ render: - default: | type: template template: electricitymaps-free - token: - zone: DE # siehe https://api.electricitymap.org/v3/zones + token: # Token + zone: DE # Zone, siehe https://api.electricitymap.org/v3/zones params: - name: token example: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Zone help: siehe https://api.electricitymap.org/v3/zones advanced: false optional: false \ No newline at end of file diff --git a/templates/release/de/tariff/energinet.yaml b/templates/release/de/tariff/energinet.yaml index 50bd013c09..b54f7cbea9 100644 --- a/templates/release/de/tariff/energinet.yaml +++ b/templates/release/de/tariff/energinet.yaml @@ -9,11 +9,11 @@ render: - default: | type: template template: energinet - region: dk1 # [dk1, dk2] + region: dk1 # Region, [dk1, dk2] advanced: | type: template template: energinet - region: dk1 # [dk1, dk2] + region: dk1 # Region, [dk1, dk2] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -23,7 +23,7 @@ params: default: choice: ['dk1', 'dk2'] unit: - description: + description: Region help: advanced: false optional: false diff --git a/templates/release/de/tariff/enever.yaml b/templates/release/de/tariff/enever.yaml index 8a9c836a71..78a99fef3d 100644 --- a/templates/release/de/tariff/enever.yaml +++ b/templates/release/de/tariff/enever.yaml @@ -9,24 +9,24 @@ render: - default: | type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + token: # Token + provider: # Anbieter, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] advanced: | type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + token: # Token + provider: # Anbieter, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) - interval: 3h # optional + interval: 3h # Intervall, optional params: - name: token example: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -35,7 +35,7 @@ params: default: choice: ['', 'AA', 'AIP', 'ANWB', 'BE', 'EE', 'EN', 'EVO', 'EZ', 'FR', 'GSL', 'MDE', 'NE', 'PE', 'TI', 'VDB', 'VON', 'WE', 'ZG', 'ZP'] unit: - description: + description: Anbieter help: advanced: false optional: false @@ -71,7 +71,7 @@ params: default: 3h choice: [] unit: - description: + description: Intervall help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/entso-e.yaml b/templates/release/de/tariff/entso-e.yaml index 3fe142d5bc..b005cd47a0 100644 --- a/templates/release/de/tariff/entso-e.yaml +++ b/templates/release/de/tariff/entso-e.yaml @@ -12,13 +12,13 @@ render: - default: | type: template template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) advanced: | type: template template: entsoe - securitytoken: # Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Security token help: Registrierung und anschließende Helpdesk-Anfrage erforderlich. Details zum Ablauf gibts hier https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation advanced: false optional: true @@ -37,7 +37,7 @@ params: default: choice: [] unit: - description: + description: Domain help: siehe https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas advanced: false optional: true diff --git a/templates/release/de/tariff/forecast-solar.yaml b/templates/release/de/tariff/forecast-solar.yaml index 10ef52addf..16089ba81e 100644 --- a/templates/release/de/tariff/forecast-solar.yaml +++ b/templates/release/de/tariff/forecast-solar.yaml @@ -24,8 +24,8 @@ render: kwp: 9.8 # Maximale Generatorleistung (kWp) az: 180 # Azimut, -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = Norden horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizont, Simuliert Verschattung durch Gelände, [mehr Informationen](https://doc.forecast.solar/horizon) (optional) - apikey: # API-Key, optional - interval: 1h # optional + apikey: # API Key, optional + interval: 1h # Intervall, optional params: - name: lat example: 55.7351 @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: API-Key + description: API Key help: advanced: true optional: true @@ -95,7 +95,7 @@ params: default: 1h choice: [] unit: - description: + description: Intervall help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/fraunhofer-ise.yaml b/templates/release/de/tariff/fraunhofer-ise.yaml index 78323adc0c..18d8e934ba 100644 --- a/templates/release/de/tariff/fraunhofer-ise.yaml +++ b/templates/release/de/tariff/fraunhofer-ise.yaml @@ -11,11 +11,11 @@ render: - default: | type: template template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Gebotszone, siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] advanced: | type: template template: energy-charts-api - bzn: DE-LU # Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Gebotszone, siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -25,8 +25,8 @@ params: default: DE-LU choice: ['AT', 'BE', 'CH', 'CZ', 'DE-LU', 'DE-AT-LU', 'DK1', 'DK2', 'FR', 'HU', 'IT-NORTH', 'NL', 'NO2', 'PL', 'SE4', 'SI'] unit: - description: - help: Gebotszonen - https://api.energy-charts.info/#/prices/day_ahead_price_price_get + description: Gebotszone + help: siehe https://api.energy-charts.info/#/prices/day_ahead_price_price_get advanced: false optional: false - name: charges diff --git a/templates/release/de/tariff/green-grid-compass.yaml b/templates/release/de/tariff/green-grid-compass.yaml index 1889c6442d..b0a07aa28e 100644 --- a/templates/release/de/tariff/green-grid-compass.yaml +++ b/templates/release/de/tariff/green-grid-compass.yaml @@ -11,7 +11,7 @@ render: - default: | type: template template: green-grid-compass - apiKey: # API-Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key + apiKey: # API Key, Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key zone: DE_LU # Zonencode, [BE, DE_LU] params: - name: apiKey @@ -19,7 +19,7 @@ params: default: choice: [] unit: - description: API-Key + description: API Key help: Erstelle eine App in https://api-portal.eco2grid.com und kopiere den Key advanced: false optional: false diff --git a/templates/release/de/tariff/grunstromindex.yaml b/templates/release/de/tariff/grunstromindex.yaml index dfb34b4499..a02a13d4e2 100644 --- a/templates/release/de/tariff/grunstromindex.yaml +++ b/templates/release/de/tariff/grunstromindex.yaml @@ -11,15 +11,15 @@ render: - default: | type: template template: grünstromindex - zip: - token: # Token für den Zugriff auf die API von https://console.corrently.io/ (optional) + zip: # Postleitzahl + token: # Token, Token für den Zugriff auf die API von https://console.corrently.io/ (optional) params: - name: zip example: default: choice: [] unit: - description: + description: Postleitzahl help: advanced: false optional: false @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Token help: Token für den Zugriff auf die API von https://console.corrently.io/ advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/national-grid-eso.yaml b/templates/release/de/tariff/national-grid-eso.yaml index ae59095492..b166be3f60 100644 --- a/templates/release/de/tariff/national-grid-eso.yaml +++ b/templates/release/de/tariff/national-grid-eso.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: ngeso - region: 1 # Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list (optional) - postalcode: SW1 # Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. (optional) + region: 1 # Region, Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Postleitzahl, Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. (optional) params: - name: region example: 1 default: choice: [] unit: - description: + description: Region help: Ungenauer als die Verwendung eines Postleitzahl. Siehe https://carbon-intensity.github.io/api-definitions/#region-list advanced: false optional: true @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Postleitzahl help: Postleitzahl z.B. RG41 oder SW1 oder TF8. Nicht die vollständige Postleitzahl, nur die ersten Stellen. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/nordpool-spot-prices.yaml b/templates/release/de/tariff/nordpool-spot-prices.yaml index 7667c3e997..512a05db26 100644 --- a/templates/release/de/tariff/nordpool-spot-prices.yaml +++ b/templates/release/de/tariff/nordpool-spot-prices.yaml @@ -11,13 +11,13 @@ render: - default: | type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Währung, [DKK, EUR, NOK, PLN, RON, SEK] advanced: | type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Währung, [DKK, EUR, NOK, PLN, RON, SEK] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -27,7 +27,7 @@ params: default: choice: ['EE', 'LT', 'LV', 'AT', 'BE', 'FR', 'GER', 'NL', 'PL', 'DK1', 'DK2', 'FI', 'NO1', 'NO2', 'NO3', 'NO4', 'NO5', 'SE1', 'SE2', 'SE3', 'SE4', 'TEL', 'SYS'] unit: - description: + description: Region help: advanced: false optional: true @@ -36,7 +36,7 @@ params: default: EUR choice: ['DKK', 'EUR', 'NOK', 'PLN', 'RON', 'SEK'] unit: - description: + description: Währung help: advanced: false optional: false diff --git a/templates/release/de/tariff/octopus-energy-api.yaml b/templates/release/de/tariff/octopus-energy-api.yaml index 1f5f76218d..217ef09b1b 100644 --- a/templates/release/de/tariff/octopus-energy-api.yaml +++ b/templates/release/de/tariff/octopus-energy-api.yaml @@ -11,24 +11,24 @@ render: - default: | type: template template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional) + apiKey: # API Key + accountNumber: X-XXXXXXXX # Kundennummer, Nur erforderlich, wenn mehrere Konten vorhanden sind. (optional) params: - name: apiKey example: default: choice: [] unit: - description: - help: Octopus Energy API Key. + description: API Key + help: advanced: false optional: false - name: accountNumber - example: + example: X-XXXXXXXX default: choice: [] unit: - description: - help: Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. + description: Kundennummer + help: Nur erforderlich, wenn mehrere Konten vorhanden sind. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/octopus-energy-product-code.yaml b/templates/release/de/tariff/octopus-energy-product-code.yaml index 88f69fb77a..02614270bb 100644 --- a/templates/release/de/tariff/octopus-energy-product-code.yaml +++ b/templates/release/de/tariff/octopus-energy-product-code.yaml @@ -9,16 +9,16 @@ render: - default: | type: template template: octopus-productcode - productCode: AGILE-FLEX-22-11-25 # Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. - region: # Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] - directDebit: true # Ich benutze den BACS-Lastschrifttarif. (optional) + productCode: AGILE-FLEX-22-11-25 # Tarifcode, Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. + region: # Region, Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Lastschrifttarif, Ich benutze den BACS-Lastschrifttarif. (optional) params: - name: productCode example: AGILE-FLEX-22-11-25 default: choice: [] unit: - description: + description: Tarifcode help: Der Tarifcode für Ihren Energievertrag. Stellen Sie sicher, dass dieser auf Ihren Importtarifcode eingestellt ist. advanced: false optional: false @@ -27,7 +27,7 @@ params: default: choice: ['A', 'B', 'C', 'D', 'E', 'F', 'G', 'H', 'J', 'K', 'L', 'M', 'N', 'P'] unit: - description: + description: Region help: 'Die DNO-Region, in der Sie sich befinden. Weitere Informationen: https://www.energy-stats.uk/dno-region-codes-explained/' advanced: false optional: false @@ -36,7 +36,7 @@ params: default: true choice: [] unit: - description: + description: Lastschrifttarif help: Ich benutze den BACS-Lastschrifttarif. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/open-meteo.yaml b/templates/release/de/tariff/open-meteo.yaml index fed0e5be2a..c2b5336293 100644 --- a/templates/release/de/tariff/open-meteo.yaml +++ b/templates/release/de/tariff/open-meteo.yaml @@ -29,7 +29,7 @@ render: efficiency: 100 # Wirkungsgrad [%], optional alphatemp: -0.004 # Temperaturkoeffizient, optional rossmodel: 0.0342 # Kühlung [Ross-Modell], Gut Gekühlt (0.0200), Freistehend (0.0208), Flach auf Dach (0.0260), Nicht So Gut Gekühlt (0.0342), Transparentes PV (0.0455), Fassadenintegriert (0.0538), Auf Schrägdach (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional + interval: 1h # Intervall, optional params: - name: lat example: 55.7351 @@ -135,7 +135,7 @@ params: default: 1h choice: [] unit: - description: + description: Intervall help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/ostrom.yaml b/templates/release/de/tariff/ostrom.yaml index 8560014056..ad9764e563 100644 --- a/templates/release/de/tariff/ostrom.yaml +++ b/templates/release/de/tariff/ostrom.yaml @@ -11,16 +11,16 @@ render: - default: | type: template template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional) + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # Client ID + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a # Client Secret + contract: 100523456 # Vertragsnummer, Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren (optional) params: - name: clientid example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 default: choice: [] unit: - description: + description: Client ID help: advanced: false optional: false @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Client Secret help: advanced: false optional: false @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Vertragsnummer help: Nur erforderlich, wenn mehrere Verträge unter einem Benutzer existieren advanced: false optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/smartenergy-smartcontrol.yaml b/templates/release/de/tariff/smartenergy-smartcontrol.yaml index db6b4f0755..5703b72363 100644 --- a/templates/release/de/tariff/smartenergy-smartcontrol.yaml +++ b/templates/release/de/tariff/smartenergy-smartcontrol.yaml @@ -5,6 +5,7 @@ product: description: smartCONTROL group: Dynamischer Strompreis countries: ["AT"] +requirements: ["skiptest"] render: - default: | type: template diff --git a/templates/release/de/tariff/solcast.yaml b/templates/release/de/tariff/solcast.yaml index da9fe517c9..53dbc89b71 100644 --- a/templates/release/de/tariff/solcast.yaml +++ b/templates/release/de/tariff/solcast.yaml @@ -11,23 +11,23 @@ render: type: template template: solcast site: # Ressource ID deiner Anlage - token: # Solcast API Token + token: # API Token advanced: | type: template template: solcast site: # Ressource ID deiner Anlage - token: # Solcast API Token - from: # Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) - to: # Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) - interval: 3h # optional + token: # API Token + from: # Startzeit, Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" (optional) + to: # Endzeit, Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" (optional) + interval: 3h # Intervall, optional params: - name: site example: default: choice: [] unit: - description: - help: Ressource ID deiner Anlage + description: Ressource ID deiner Anlage + help: advanced: false optional: false - name: token @@ -35,8 +35,8 @@ params: default: choice: [] unit: - description: - help: Solcast API Token + description: API Token + help: advanced: false optional: false - name: from @@ -44,7 +44,7 @@ params: default: choice: [] unit: - description: + description: Startzeit help: Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" advanced: true optional: true @@ -53,7 +53,7 @@ params: default: choice: [] unit: - description: + description: Endzeit help: Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" advanced: true optional: true @@ -62,7 +62,7 @@ params: default: 3h choice: [] unit: - description: + description: Intervall help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/tariff/spotty-energie.yaml b/templates/release/de/tariff/spotty-energie.yaml index 5238a12ca9..89397dd2ba 100644 --- a/templates/release/de/tariff/spotty-energie.yaml +++ b/templates/release/de/tariff/spotty-energie.yaml @@ -9,13 +9,13 @@ render: - default: | type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Vertragsnummer, Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Preistyp, Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] advanced: | type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Vertragsnummer, Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Preistyp, Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Vertragsnummer help: Die Vertragsnummer bekommst du im Kundenportal https://i.spottyenergie.at/ advanced: false optional: false @@ -34,7 +34,7 @@ params: default: CONSUMPTION choice: ['MARKET', 'CONSUMPTION', 'GENERATION'] unit: - description: + description: Preistyp help: Preistyp, entweder Börsenpreis, Verbrauchspreis oder Einspeisevergütung (falls vereinbart), siehe https://www.spottyenergie.at/blog/energie-smart-produzieren advanced: false optional: false diff --git a/templates/release/de/tariff/tibber.yaml b/templates/release/de/tariff/tibber.yaml index 390ad45c95..baa6e5f0bf 100644 --- a/templates/release/de/tariff/tibber.yaml +++ b/templates/release/de/tariff/tibber.yaml @@ -11,13 +11,13 @@ render: - default: | type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) advanced: | type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional) charges: # Aufschlag, Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional) tax: # Steuer, Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formel, Individuelle Formel zur Berechnung des Preises (optional) @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: API Token help: advanced: false optional: false @@ -36,7 +36,7 @@ params: default: choice: [] unit: - description: + description: Home ID help: Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. advanced: false optional: true diff --git a/templates/release/de/tariff/victron-vrm-solar-forecast.yaml b/templates/release/de/tariff/victron-vrm-solar-forecast.yaml index 1ded5b0719..3ce4bf4bcc 100644 --- a/templates/release/de/tariff/victron-vrm-solar-forecast.yaml +++ b/templates/release/de/tariff/victron-vrm-solar-forecast.yaml @@ -18,7 +18,7 @@ render: template: victron idsite: 123456 # VRM-Installations-ID der Installation, Die VRM-Installations-ID wird in den Einstellungen der Installation unter "Allgemeines" angezeigt token: # API Zugriffstoken, Token können im VRM erstellt werden unter Präferenzen->Integrationen - interval: 1h # optional + interval: 1h # Intervall, optional params: - name: idsite example: 123456 @@ -43,7 +43,7 @@ params: default: 1h choice: [] unit: - description: + description: Intervall help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/aiways.yaml b/templates/release/de/vehicle/aiways.yaml index 2428df9340..90295382ac 100644 --- a/templates/release/de/vehicle/aiways.yaml +++ b/templates/release/de/vehicle/aiways.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -96,8 +96,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/audi.yaml b/templates/release/de/vehicle/audi.yaml index e3f21d047b..f2e57177a8 100644 --- a/templates/release/de/vehicle/audi.yaml +++ b/templates/release/de/vehicle/audi.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -96,8 +96,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/bmw.yaml b/templates/release/de/vehicle/bmw.yaml index 26ea682910..4363633d4e 100644 --- a/templates/release/de/vehicle/bmw.yaml +++ b/templates/release/de/vehicle/bmw.yaml @@ -14,7 +14,7 @@ render: vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token advanced: | type: template template: bmw @@ -23,10 +23,10 @@ render: vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: + description: Captcha Token help: advanced: false optional: false @@ -113,8 +113,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/citroen.yaml b/templates/release/de/vehicle/citroen.yaml index b38f2a07fb..d1a6647c7c 100644 --- a/templates/release/de/vehicle/citroen.yaml +++ b/templates/release/de/vehicle/citroen.yaml @@ -12,8 +12,8 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/dacia.yaml b/templates/release/de/vehicle/dacia.yaml index a2829a658d..bfcbd4ac92 100644 --- a/templates/release/de/vehicle/dacia.yaml +++ b/templates/release/de/vehicle/dacia.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/ds.yaml b/templates/release/de/vehicle/ds.yaml index d3e33e9272..1357465e1c 100644 --- a/templates/release/de/vehicle/ds.yaml +++ b/templates/release/de/vehicle/ds.yaml @@ -12,8 +12,8 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/evnotify.yaml b/templates/release/de/vehicle/evnotify.yaml index 8488b849ee..7aa31bf119 100644 --- a/templates/release/de/vehicle/evnotify.yaml +++ b/templates/release/de/vehicle/evnotify.yaml @@ -7,20 +7,20 @@ render: - default: | type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional advanced: | type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -31,7 +31,7 @@ params: default: choice: [] unit: - description: + description: API Key help: advanced: false optional: false @@ -40,7 +40,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -85,8 +85,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/fiat.yaml b/templates/release/de/vehicle/fiat.yaml index 6b1133c87f..f249d551b4 100644 --- a/templates/release/de/vehicle/fiat.yaml +++ b/templates/release/de/vehicle/fiat.yaml @@ -11,7 +11,7 @@ render: vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) advanced: | type: template template: fiat @@ -20,10 +20,10 @@ render: vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: + description: PIN help: Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. advanced: false optional: true @@ -109,8 +109,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/ford.yaml b/templates/release/de/vehicle/ford.yaml index 67c61b1f96..092cea2fdd 100644 --- a/templates/release/de/vehicle/ford.yaml +++ b/templates/release/de/vehicle/ford.yaml @@ -10,8 +10,8 @@ render: capacity: 50 # Akkukapazität (kWh), optional clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template @@ -20,12 +20,12 @@ render: capacity: 50 # Akkukapazität (kWh), optional clientid: # FordConnect API Client ID, Einrichtung unter https://developer.ford.com clientsecret: # FordConnect API Client Secret, Einrichtung unter https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -73,7 +73,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -118,8 +118,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/generic-vehicle-without-api.yaml b/templates/release/de/vehicle/generic-vehicle-without-api.yaml index 9c05a9f976..bcb857f9a9 100644 --- a/templates/release/de/vehicle/generic-vehicle-without-api.yaml +++ b/templates/release/de/vehicle/generic-vehicle-without-api.yaml @@ -16,7 +16,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -63,8 +63,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/hyundai-bluelink.yaml b/templates/release/de/vehicle/hyundai-bluelink.yaml index c7b4f04d26..3be9bc3a0f 100644 --- a/templates/release/de/vehicle/hyundai-bluelink.yaml +++ b/templates/release/de/vehicle/hyundai-bluelink.yaml @@ -26,7 +26,7 @@ render: language: en # Sprache, [en, de] (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/iobroker-bmw.yaml b/templates/release/de/vehicle/iobroker-bmw.yaml index 5ae99e5e14..dedf3f6e6e 100644 --- a/templates/release/de/vehicle/iobroker-bmw.yaml +++ b/templates/release/de/vehicle/iobroker-bmw.yaml @@ -12,17 +12,17 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer - uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse + uri: # ioBroker URL, einschliesslich ioBroker.simple-api Port advanced: | type: template template: ioBroker.bmw title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: WBA8E9G50GM091234 # Fahrzeugidentifikationsnummer, BMW Fahrzeugidentifikationsnummer - uri: # ioBroker URL einschliesslich ioBroker.simple-api Port, HTTP(S) Adresse + uri: # ioBroker URL, einschliesslich ioBroker.simple-api Port icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -63,8 +63,8 @@ params: default: choice: [] unit: - description: ioBroker URL einschliesslich ioBroker.simple-api Port - help: HTTP(S) Adresse + description: ioBroker URL + help: einschliesslich ioBroker.simple-api Port advanced: false optional: false - name: icon @@ -90,8 +90,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/iso15118.yaml b/templates/release/de/vehicle/iso15118.yaml index 2f27a10dca..16681dce46 100644 --- a/templates/release/de/vehicle/iso15118.yaml +++ b/templates/release/de/vehicle/iso15118.yaml @@ -23,7 +23,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -70,8 +70,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/jeep.yaml b/templates/release/de/vehicle/jeep.yaml index 6e06964dfe..e34ef09e2a 100644 --- a/templates/release/de/vehicle/jeep.yaml +++ b/templates/release/de/vehicle/jeep.yaml @@ -11,7 +11,7 @@ render: vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) advanced: | type: template template: fiat @@ -20,10 +20,10 @@ render: vin: ZFAE... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - pin: # Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) + pin: # PIN, Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: + description: PIN help: Benötigt um das Fahrzeug zum Laden aufzuwecken and zur Aktualisierung des Ladestands während der Ladung. Bei Nutzung mit TWC3 kann der Ladevorgang mittels PIN gestartet und gestoppt werden. advanced: false optional: true @@ -109,8 +109,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/kia-bluelink.yaml b/templates/release/de/vehicle/kia-bluelink.yaml index ccdfe46ac3..e76bfccef0 100644 --- a/templates/release/de/vehicle/kia-bluelink.yaml +++ b/templates/release/de/vehicle/kia-bluelink.yaml @@ -26,7 +26,7 @@ render: language: en # Sprache, [en, de] (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/mercedes-benz.yaml b/templates/release/de/vehicle/mercedes-benz.yaml index 2418b582d2..1b5b52cd13 100644 --- a/templates/release/de/vehicle/mercedes-benz.yaml +++ b/templates/release/de/vehicle/mercedes-benz.yaml @@ -12,9 +12,9 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template @@ -22,13 +22,13 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -67,7 +67,7 @@ params: default: EMEA choice: ['EMEA', 'APAC', 'NORAM'] unit: - description: + description: Region help: advanced: false optional: false @@ -76,7 +76,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -121,8 +121,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/mg.yaml b/templates/release/de/vehicle/mg.yaml index f50f56d0ab..30bb16d7fe 100644 --- a/templates/release/de/vehicle/mg.yaml +++ b/templates/release/de/vehicle/mg.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/mg2mqtt.yaml b/templates/release/de/vehicle/mg2mqtt.yaml index 74550ea3bb..c26302b1c6 100644 --- a/templates/release/de/vehicle/mg2mqtt.yaml +++ b/templates/release/de/vehicle/mg2mqtt.yaml @@ -24,7 +24,7 @@ render: timeout: 1h # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/mini.yaml b/templates/release/de/vehicle/mini.yaml index 3381139fbf..ae5d38269a 100644 --- a/templates/release/de/vehicle/mini.yaml +++ b/templates/release/de/vehicle/mini.yaml @@ -14,7 +14,7 @@ render: vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token advanced: | type: template template: mini @@ -23,10 +23,10 @@ render: vin: WBMW... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: + description: Captcha Token help: advanced: false optional: false @@ -113,8 +113,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/mz2mqtt.yaml b/templates/release/de/vehicle/mz2mqtt.yaml index 382c0e69dd..7109aa57e1 100644 --- a/templates/release/de/vehicle/mz2mqtt.yaml +++ b/templates/release/de/vehicle/mz2mqtt.yaml @@ -20,7 +20,7 @@ render: vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -77,8 +77,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/nissan-ariya.yaml b/templates/release/de/vehicle/nissan-ariya.yaml index 31d15a0905..648f16b238 100644 --- a/templates/release/de/vehicle/nissan-ariya.yaml +++ b/templates/release/de/vehicle/nissan-ariya.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/nissan-leaf-pre-2019.yaml b/templates/release/de/vehicle/nissan-leaf-pre-2019.yaml index dd53859d64..5d98cf22a1 100644 --- a/templates/release/de/vehicle/nissan-leaf-pre-2019.yaml +++ b/templates/release/de/vehicle/nissan-leaf-pre-2019.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/nissan-leaf.yaml b/templates/release/de/vehicle/nissan-leaf.yaml index 0c80b9b792..8754483d77 100644 --- a/templates/release/de/vehicle/nissan-leaf.yaml +++ b/templates/release/de/vehicle/nissan-leaf.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/opel.yaml b/templates/release/de/vehicle/opel.yaml index 6309f74fd8..ed5b73d192 100644 --- a/templates/release/de/vehicle/opel.yaml +++ b/templates/release/de/vehicle/opel.yaml @@ -12,8 +12,8 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/open-vehicle-monitoring-system.yaml b/templates/release/de/vehicle/open-vehicle-monitoring-system.yaml index 548ac255c8..50602ff219 100644 --- a/templates/release/de/vehicle/open-vehicle-monitoring-system.yaml +++ b/templates/release/de/vehicle/open-vehicle-monitoring-system.yaml @@ -13,7 +13,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vehicleid: + vehicleid: # Vehicle ID advanced: | type: template template: ovms @@ -21,15 +21,15 @@ render: capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen - vehicleid: + vehicleid: # Vehicle ID icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - server: dexters-web.de + server: dexters-web.de # Server cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) params: - name: title @@ -73,7 +73,7 @@ params: default: choice: [] unit: - description: + description: Vehicle ID help: advanced: false optional: false @@ -100,8 +100,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent @@ -145,7 +145,7 @@ params: default: dexters-web.de choice: [] unit: - description: + description: Server help: advanced: true optional: false diff --git a/templates/release/de/vehicle/peugeot.yaml b/templates/release/de/vehicle/peugeot.yaml index ecdf2f5d34..250e4d9d2e 100644 --- a/templates/release/de/vehicle/peugeot.yaml +++ b/templates/release/de/vehicle/peugeot.yaml @@ -12,8 +12,8 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/polestar.yaml b/templates/release/de/vehicle/polestar.yaml index 36ecc2fea3..bfffeb4bb9 100644 --- a/templates/release/de/vehicle/polestar.yaml +++ b/templates/release/de/vehicle/polestar.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/psa-car-controller.yaml b/templates/release/de/vehicle/psa-car-controller.yaml index 95851e5eca..cc6deb0e28 100644 --- a/templates/release/de/vehicle/psa-car-controller.yaml +++ b/templates/release/de/vehicle/psa-car-controller.yaml @@ -9,32 +9,32 @@ render: - default: | type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional advanced: | type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - wakeup_alt: false # alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. (optional) + wakeup_alt: false # Alternativer Wakeup-Code, Kann zu erhöhter Entladung der 12V-Batterie führen. (optional) params: - name: url example: http://192.0.2.2 default: choice: [] unit: - description: + description: URL help: advanced: false optional: false @@ -88,8 +88,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent @@ -133,7 +133,7 @@ params: default: false choice: [] unit: - description: - help: alternativer wakeup-Code; könnte zu erhöhter Entladung der 12V-Batterie führen. + description: Alternativer Wakeup-Code + help: Kann zu erhöhter Entladung der 12V-Batterie führen. advanced: true optional: true \ No newline at end of file diff --git a/templates/release/de/vehicle/renault.yaml b/templates/release/de/vehicle/renault.yaml index 657ee2d145..d92a7b936d 100644 --- a/templates/release/de/vehicle/renault.yaml +++ b/templates/release/de/vehicle/renault.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml b/templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml index 363ce018be..3a4c4da310 100644 --- a/templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml +++ b/templates/release/de/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml b/templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml index 6223fe45f6..4b671dfae3 100644 --- a/templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml +++ b/templates/release/de/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/skoda-enyaq.yaml b/templates/release/de/vehicle/skoda-enyaq.yaml index c1caa1cf34..2185dfe81a 100644 --- a/templates/release/de/vehicle/skoda-enyaq.yaml +++ b/templates/release/de/vehicle/skoda-enyaq.yaml @@ -24,7 +24,7 @@ render: timeout: 10s # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -108,8 +108,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/smart-1.yaml b/templates/release/de/vehicle/smart-1.yaml index fa7e38303d..cfef86b931 100644 --- a/templates/release/de/vehicle/smart-1.yaml +++ b/templates/release/de/vehicle/smart-1.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/smart-eq.yaml b/templates/release/de/vehicle/smart-eq.yaml index 2232c320a5..5e400ec2ec 100644 --- a/templates/release/de/vehicle/smart-eq.yaml +++ b/templates/release/de/vehicle/smart-eq.yaml @@ -13,9 +13,9 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template @@ -23,13 +23,13 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -68,7 +68,7 @@ params: default: EMEA choice: ['EMEA', 'APAC', 'NORAM'] unit: - description: + description: Region help: advanced: false optional: false @@ -77,7 +77,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -122,8 +122,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/tesla-ble.yaml b/templates/release/de/vehicle/tesla-ble.yaml index 1f6e70b1bd..31a8aef372 100644 --- a/templates/release/de/vehicle/tesla-ble.yaml +++ b/templates/release/de/vehicle/tesla-ble.yaml @@ -12,7 +12,7 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung - url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL des Tesla BLE HTTP Proxy port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional) advanced: | type: template @@ -20,11 +20,11 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional vin: W... # Fahrzeugidentifikationsnummer, Erforderlich für BLE-Verbindung - url: http://192.168.178.27 # URL des Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL des Tesla BLE HTTP Proxy port: 8080 # Port, Port des Tesla BLE HTTP Proxy (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -62,7 +62,7 @@ params: default: choice: [] unit: - description: + description: URL help: URL des Tesla BLE HTTP Proxy advanced: false optional: false @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/tesla.yaml b/templates/release/de/vehicle/tesla.yaml index 663ee1253d..0c931612b0 100644 --- a/templates/release/de/vehicle/tesla.yaml +++ b/templates/release/de/vehicle/tesla.yaml @@ -25,28 +25,28 @@ render: template: tesla title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, von [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, von [myteslamate.com](https://app.myteslamate.com/). vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template template: tesla title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - clientId: # Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # von [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # von [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, von [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, von [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, von [myteslamate.com](https://app.myteslamate.com/). vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) priority: # Priorität, Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional) - commandProxy: https://api.myteslamate.com # Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) - proxyToken: # Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) + commandProxy: https://api.myteslamate.com # Command Proxy, Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. (optional) + proxyToken: # Proxy Token, Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. (optional) cache: 15m # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional) params: - name: title @@ -72,8 +72,8 @@ params: default: choice: [] unit: - description: - help: Kunden ID deiner [Tesla Developer App](https://developer.tesla.com/dashboard). + description: Client ID + help: von [Tesla Developer App](https://developer.tesla.com/dashboard). advanced: false optional: false - name: accessToken @@ -81,7 +81,7 @@ params: default: choice: [] unit: - description: + description: Access token help: von [myteslamate.com](https://app.myteslamate.com/). advanced: false optional: false @@ -90,7 +90,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: von [myteslamate.com](https://app.myteslamate.com/). advanced: false optional: false @@ -126,8 +126,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent @@ -171,7 +171,7 @@ params: default: https://api.myteslamate.com choice: [] unit: - description: + description: Command Proxy help: Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der [myteslamate.com](https://app.myteslamate.com/) Proxy verwendet. Mit diesem Parameter kannst du die Basis-URL ändern. Siehe zum Beispiel [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) für einen Proxy, der Kommandos über Bluetooth sendet. advanced: true optional: true @@ -180,7 +180,7 @@ params: default: choice: [] unit: - description: + description: Proxy Token help: Token für den Command Proxy von [myteslamate.com](https://app.myteslamate.com/) (nutzungsbasiert). Stelle sicher, dass du den Virtual Key installiert hast und die Berechtigungen 'Ladung starten', 'Ladung stoppen' und 'Ladestrom setzen' erteilt hast. advanced: true optional: true diff --git a/templates/release/de/vehicle/teslalogger.yaml b/templates/release/de/vehicle/teslalogger.yaml index de2ba86769..f2100f80b2 100644 --- a/templates/release/de/vehicle/teslalogger.yaml +++ b/templates/release/de/vehicle/teslalogger.yaml @@ -12,7 +12,7 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional advanced: | type: template @@ -20,11 +20,11 @@ render: title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -62,7 +62,7 @@ params: default: choice: [] unit: - description: + description: URL help: advanced: false optional: false @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/teslamate.yaml b/templates/release/de/vehicle/teslamate.yaml index 3d4e07f24d..4e9a7bfb71 100644 --- a/templates/release/de/vehicle/teslamate.yaml +++ b/templates/release/de/vehicle/teslamate.yaml @@ -20,7 +20,7 @@ render: id: 1 # Fahrzeug-ID, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -76,8 +76,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/tessie.yaml b/templates/release/de/vehicle/tessie.yaml index b4e4566bd7..cceb610772 100644 --- a/templates/release/de/vehicle/tessie.yaml +++ b/templates/release/de/vehicle/tessie.yaml @@ -22,7 +22,7 @@ render: token: # Tessie API Token icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -87,8 +87,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/toyota.yaml b/templates/release/de/vehicle/toyota.yaml index 3581408db7..e8cd6a7fe3 100644 --- a/templates/release/de/vehicle/toyota.yaml +++ b/templates/release/de/vehicle/toyota.yaml @@ -24,7 +24,7 @@ render: vin: JT... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/tronity.yaml b/templates/release/de/vehicle/tronity.yaml index 83086466e5..e8ea882595 100644 --- a/templates/release/de/vehicle/tronity.yaml +++ b/templates/release/de/vehicle/tronity.yaml @@ -23,7 +23,7 @@ render: vin: W... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/volkswagen-we-connect-id.yaml b/templates/release/de/vehicle/volkswagen-we-connect-id.yaml index 5cfa81e579..1157d4ccd6 100644 --- a/templates/release/de/vehicle/volkswagen-we-connect-id.yaml +++ b/templates/release/de/vehicle/volkswagen-we-connect-id.yaml @@ -26,7 +26,7 @@ render: timeout: 10s # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -112,8 +112,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/volvo.yaml b/templates/release/de/vehicle/volvo.yaml index a226d2ca91..5293520ffe 100644 --- a/templates/release/de/vehicle/volvo.yaml +++ b/templates/release/de/vehicle/volvo.yaml @@ -18,24 +18,24 @@ render: template: volvo-connected title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vccapikey: # VCC API Key, aus [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, aus [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, aus [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) advanced: | type: template template: volvo-connected title: # Titel, Wird in der Benutzeroberfläche angezeigt (optional) capacity: 50 # Akkukapazität (kWh), optional - vccapikey: # VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. + vccapikey: # VCC API Key, aus [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, aus [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, aus [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist. vin: WF0FXX... # Fahrzeugidentifikationsnummer, Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind (optional) icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -64,8 +64,8 @@ params: default: choice: [] unit: - description: - help: VCC API Key deiner [Volvo Developer App](https://developer.volvocars.com/). + description: VCC API Key + help: aus [Volvo Developer App](https://developer.volvocars.com/). advanced: false optional: false - name: clientId @@ -73,8 +73,8 @@ params: default: choice: [] unit: - description: - help: Client ID deiner [Volvo Developer App](https://developer.volvocars.com/). + description: Client ID + help: aus [Volvo Developer App](https://developer.volvocars.com/). advanced: false optional: false - name: clientSecret @@ -82,8 +82,8 @@ params: default: choice: [] unit: - description: - help: Client Secret deiner [Volvo Developer App](https://developer.volvocars.com/). + description: Client Secret + help: aus [Volvo Developer App](https://developer.volvocars.com/). advanced: false optional: false - name: redirectUri @@ -91,8 +91,8 @@ params: default: choice: [] unit: - description: - help: 'Redirect-URI deiner EVCC-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist.' + description: Redirect URI + help: 'Redirect-URI deiner evcc-Instanz, Format: http://evcc.local:7070/oauth/callback. Muss mit der Redirect-URI übereinstimmen, die in deiner Volvo Developer App festgelegt ist.' advanced: false optional: false - name: vin @@ -127,8 +127,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/volvo2mqtt.yaml b/templates/release/de/vehicle/volvo2mqtt.yaml index 4f8e5f526b..6a80abd750 100644 --- a/templates/release/de/vehicle/volvo2mqtt.yaml +++ b/templates/release/de/vehicle/volvo2mqtt.yaml @@ -22,7 +22,7 @@ render: timeout: 720h # Zeitüberschreitung, optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -87,8 +87,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/de/vehicle/zero-motorcycles.yaml b/templates/release/de/vehicle/zero-motorcycles.yaml index 1d993229b2..39cfb45ffd 100644 --- a/templates/release/de/vehicle/zero-motorcycles.yaml +++ b/templates/release/de/vehicle/zero-motorcycles.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Akkukapazität (kWh), optional icon: car # Icon, Wird in der Benutzeroberfläche angezeigt [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximale Phasenanzahl, Die maximale Anzahl der Phasen welche genutzt werden können (optional) - mode: # Standardlademodus, wenn ein Fahrzeug angeschlossen ist, Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) + mode: # Standardlademodus, Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional) minCurrent: 6 # Minimale Stromstärke (A), Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) maxCurrent: 16 # Maximale Stromstärke (A), Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional) identifiers: # Identifikation, Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional) @@ -96,8 +96,8 @@ params: default: choice: [] unit: - description: Standardlademodus, wenn ein Fahrzeug angeschlossen ist - help: Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll + description: Standardlademodus + help: Wird beim Anschließen eines Fahrzeugs verwendet. Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/charger/abb-terra-ac-ocpp.yaml b/templates/release/en/charger/abb-terra-ac-ocpp.yaml index 505840e5b6..e2c39fd72f 100644 --- a/templates/release/en/charger/abb-terra-ac-ocpp.yaml +++ b/templates/release/en/charger/abb-terra-ac-ocpp.yaml @@ -11,17 +11,17 @@ render: - default: | type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-abb-tac - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -29,7 +29,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -46,8 +46,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -55,8 +55,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -64,8 +64,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -73,8 +73,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abb-terra-ac.yaml b/templates/release/en/charger/abb-terra-ac.yaml index 3ec6b2dc6d..8d9a0766f3 100644 --- a/templates/release/en/charger/abb-terra-ac.yaml +++ b/templates/release/en/charger/abb-terra-ac.yaml @@ -36,7 +36,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/abl-em4-single-ocpp.yaml b/templates/release/en/charger/abl-em4-single-ocpp.yaml index 2a27db733b..6ca1d7a53d 100644 --- a/templates/release/en/charger/abl-em4-single-ocpp.yaml +++ b/templates/release/en/charger/abl-em4-single-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-em4-single-sbcx.yaml b/templates/release/en/charger/abl-em4-single-sbcx.yaml index 58bf11b5fc..0a49ad871b 100644 --- a/templates/release/en/charger/abl-em4-single-sbcx.yaml +++ b/templates/release/en/charger/abl-em4-single-sbcx.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/abl-em4-twin-ocpp.yaml b/templates/release/en/charger/abl-em4-twin-ocpp.yaml index a39d79ae65..94a6852784 100644 --- a/templates/release/en/charger/abl-em4-twin-ocpp.yaml +++ b/templates/release/en/charger/abl-em4-twin-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-em4-twin-sbcx.yaml b/templates/release/en/charger/abl-em4-twin-sbcx.yaml index 1c06f607cb..3136c61462 100644 --- a/templates/release/en/charger/abl-em4-twin-sbcx.yaml +++ b/templates/release/en/charger/abl-em4-twin-sbcx.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/abl-emh1.yaml b/templates/release/en/charger/abl-emh1.yaml index 43e451e43f..9aaa9791cb 100644 --- a/templates/release/en/charger/abl-emh1.yaml +++ b/templates/release/en/charger/abl-emh1.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/abl-emh2-ocpp.yaml b/templates/release/en/charger/abl-emh2-ocpp.yaml index cf4fde1953..0999ff4122 100644 --- a/templates/release/en/charger/abl-emh2-ocpp.yaml +++ b/templates/release/en/charger/abl-emh2-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/abl-emh2.yaml b/templates/release/en/charger/abl-emh2.yaml index 78b98d1562..733c3bbdc9 100644 --- a/templates/release/en/charger/abl-emh2.yaml +++ b/templates/release/en/charger/abl-emh2.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/abl-emh3-ocpp.yaml b/templates/release/en/charger/abl-emh3-ocpp.yaml index f90cd7eaf0..bc23a8849b 100644 --- a/templates/release/en/charger/abl-emh3-ocpp.yaml +++ b/templates/release/en/charger/abl-emh3-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-abl - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/alfen-eve-ocpp.yaml b/templates/release/en/charger/alfen-eve-ocpp.yaml index 45494e94f5..7285fd8fb8 100644 --- a/templates/release/en/charger/alfen-eve-ocpp.yaml +++ b/templates/release/en/charger/alfen-eve-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-alfen - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/alfen-eve.yaml b/templates/release/en/charger/alfen-eve.yaml index 58fa1c24e7..325130e815 100644 --- a/templates/release/en/charger/alfen-eve.yaml +++ b/templates/release/en/charger/alfen-eve.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/alpha-innotec.yaml b/templates/release/en/charger/alpha-innotec.yaml index d95a0e30c0..b7f9dbbd8d 100644 --- a/templates/release/en/charger/alpha-innotec.yaml +++ b/templates/release/en/charger/alpha-innotec.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -25,15 +25,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -42,8 +42,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -51,7 +51,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/alphatec-ladesaule-twin.yaml b/templates/release/en/charger/alphatec-ladesaule-twin.yaml index c378d83016..37d2916ba3 100644 --- a/templates/release/en/charger/alphatec-ladesaule-twin.yaml +++ b/templates/release/en/charger/alphatec-ladesaule-twin.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/alphatec-wallbox-mini.yaml b/templates/release/en/charger/alphatec-wallbox-mini.yaml index 641654116a..8b63c918d5 100644 --- a/templates/release/en/charger/alphatec-wallbox-mini.yaml +++ b/templates/release/en/charger/alphatec-wallbox-mini.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/alphatec-wallbox-power.yaml b/templates/release/en/charger/alphatec-wallbox-power.yaml index 3abd75d11e..475d1775c1 100644 --- a/templates/release/en/charger/alphatec-wallbox-power.yaml +++ b/templates/release/en/charger/alphatec-wallbox-power.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/amperfied-wallbox-connect-business.yaml b/templates/release/en/charger/amperfied-wallbox-connect-business.yaml index 9aa1661f93..d90ffbdd4c 100644 --- a/templates/release/en/charger/amperfied-wallbox-connect-business.yaml +++ b/templates/release/en/charger/amperfied-wallbox-connect-business.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/amperfied-wallbox-connect-home.yaml b/templates/release/en/charger/amperfied-wallbox-connect-home.yaml index 31f18ff3e1..dd614b25c5 100644 --- a/templates/release/en/charger/amperfied-wallbox-connect-home.yaml +++ b/templates/release/en/charger/amperfied-wallbox-connect-home.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/amperfied-wallbox-connect-solar.yaml b/templates/release/en/charger/amperfied-wallbox-connect-solar.yaml index 976171a73b..7e24581fb2 100644 --- a/templates/release/en/charger/amperfied-wallbox-connect-solar.yaml +++ b/templates/release/en/charger/amperfied-wallbox-connect-solar.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/amperfied-wallbox-energy-control.yaml b/templates/release/en/charger/amperfied-wallbox-energy-control.yaml index 5d6ea17fd3..7f88aeb8cc 100644 --- a/templates/release/en/charger/amperfied-wallbox-energy-control.yaml +++ b/templates/release/en/charger/amperfied-wallbox-energy-control.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/ampure-unite.yaml b/templates/release/en/charger/ampure-unite.yaml index 7fd4097f24..bc76a79c22 100644 --- a/templates/release/en/charger/ampure-unite.yaml +++ b/templates/release/en/charger/ampure-unite.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/autel-ac-compact.yaml b/templates/release/en/charger/autel-ac-compact.yaml index a3e29d425d..724569cd7d 100644 --- a/templates/release/en/charger/autel-ac-compact.yaml +++ b/templates/release/en/charger/autel-ac-compact.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/autel-ac-maxicharger.yaml b/templates/release/en/charger/autel-ac-maxicharger.yaml index 988a1c35b0..b0456088d0 100644 --- a/templates/release/en/charger/autel-ac-maxicharger.yaml +++ b/templates/release/en/charger/autel-ac-maxicharger.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-autel - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/autoaid-business-wallbox.yaml b/templates/release/en/charger/autoaid-business-wallbox.yaml index d88e519b42..c43974a141 100644 --- a/templates/release/en/charger/autoaid-business-wallbox.yaml +++ b/templates/release/en/charger/autoaid-business-wallbox.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/autoaid-intelligent-wallbox.yaml b/templates/release/en/charger/autoaid-intelligent-wallbox.yaml index 7a8e721f02..0a0645ded8 100644 --- a/templates/release/en/charger/autoaid-intelligent-wallbox.yaml +++ b/templates/release/en/charger/autoaid-intelligent-wallbox.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-autoaid - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/bender-cc612.yaml b/templates/release/en/charger/bender-cc612.yaml index e71c6d81d6..1d64022057 100644 --- a/templates/release/en/charger/bender-cc612.yaml +++ b/templates/release/en/charger/bender-cc612.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/bender-cc613.yaml b/templates/release/en/charger/bender-cc613.yaml index e27ab70912..80fbebe435 100644 --- a/templates/release/en/charger/bender-cc613.yaml +++ b/templates/release/en/charger/bender-cc613.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/bender-icc1314.yaml b/templates/release/en/charger/bender-icc1314.yaml index ddda4ca25d..bc0a3fc425 100644 --- a/templates/release/en/charger/bender-icc1314.yaml +++ b/templates/release/en/charger/bender-icc1314.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/bender-icc1324.yaml b/templates/release/en/charger/bender-icc1324.yaml index d7de6d3c99..924d961831 100644 --- a/templates/release/en/charger/bender-icc1324.yaml +++ b/templates/release/en/charger/bender-icc1324.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/bmw-i-wallbox.yaml b/templates/release/en/charger/bmw-i-wallbox.yaml index 8326efb604..80f046763b 100644 --- a/templates/release/en/charger/bmw-i-wallbox.yaml +++ b/templates/release/en/charger/bmw-i-wallbox.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/bosch-sg-ready.yaml b/templates/release/en/charger/bosch-sg-ready.yaml index 16810941b4..dabf1c238d 100644 --- a/templates/release/en/charger/bosch-sg-ready.yaml +++ b/templates/release/en/charger/bosch-sg-ready.yaml @@ -11,7 +11,7 @@ render: type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional) params: @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true diff --git a/templates/release/en/charger/bosch-x-change.yaml b/templates/release/en/charger/bosch-x-change.yaml index 99d9fcde39..3f81ede886 100644 --- a/templates/release/en/charger/bosch-x-change.yaml +++ b/templates/release/en/charger/bosch-x-change.yaml @@ -15,7 +15,7 @@ render: template: kermi host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -40,7 +40,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml b/templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml index 324cfb12e1..62cb2d515e 100644 --- a/templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml +++ b/templates/release/en/charger/buderus-logamatic-hmc-20-z.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/buderus-logamatic-hmc-20.yaml b/templates/release/en/charger/buderus-logamatic-hmc-20.yaml index a9a1e3a5d5..90d2f501d1 100644 --- a/templates/release/en/charger/buderus-logamatic-hmc-20.yaml +++ b/templates/release/en/charger/buderus-logamatic-hmc-20.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/buderus-sg-ready.yaml b/templates/release/en/charger/buderus-sg-ready.yaml index 40dfd311cb..f905d22595 100644 --- a/templates/release/en/charger/buderus-sg-ready.yaml +++ b/templates/release/en/charger/buderus-sg-ready.yaml @@ -11,7 +11,7 @@ render: type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional) params: @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true diff --git a/templates/release/en/charger/charge-amps-halo.yaml b/templates/release/en/charger/charge-amps-halo.yaml index 15983194fe..433aaaa726 100644 --- a/templates/release/en/charger/charge-amps-halo.yaml +++ b/templates/release/en/charger/charge-amps-halo.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-chargeamps - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/compleo-ebox.yaml b/templates/release/en/charger/compleo-ebox.yaml index 7f5a029899..18d2ca4568 100644 --- a/templates/release/en/charger/compleo-ebox.yaml +++ b/templates/release/en/charger/compleo-ebox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/cta-all-in-one-aeroplus.yaml b/templates/release/en/charger/cta-all-in-one-aeroplus.yaml index 18b2131213..d12fab7945 100644 --- a/templates/release/en/charger/cta-all-in-one-aeroplus.yaml +++ b/templates/release/en/charger/cta-all-in-one-aeroplus.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/cubos-c11e.yaml b/templates/release/en/charger/cubos-c11e.yaml index 82181dc117..1dba6f8a45 100644 --- a/templates/release/en/charger/cubos-c11e.yaml +++ b/templates/release/en/charger/cubos-c11e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/cubos-c22e.yaml b/templates/release/en/charger/cubos-c22e.yaml index 7dc41128d5..c5fc0eb7eb 100644 --- a/templates/release/en/charger/cubos-c22e.yaml +++ b/templates/release/en/charger/cubos-c22e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/dadapower-premium-wallbox.yaml b/templates/release/en/charger/dadapower-premium-wallbox.yaml index 8774b672ed..fa69fc587f 100644 --- a/templates/release/en/charger/dadapower-premium-wallbox.yaml +++ b/templates/release/en/charger/dadapower-premium-wallbox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/daikin-homehub-sg-ready.yaml b/templates/release/en/charger/daikin-homehub-sg-ready.yaml index e853bbab96..a68a2feb71 100644 --- a/templates/release/en/charger/daikin-homehub-sg-ready.yaml +++ b/templates/release/en/charger/daikin-homehub-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/delta-ac-max-basic.yaml b/templates/release/en/charger/delta-ac-max-basic.yaml index 914ee2fadf..f1fc8c7044 100644 --- a/templates/release/en/charger/delta-ac-max-basic.yaml +++ b/templates/release/en/charger/delta-ac-max-basic.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/delta-ac-max-smart.yaml b/templates/release/en/charger/delta-ac-max-smart.yaml index bff5b8e4ef..928dc34aa2 100644 --- a/templates/release/en/charger/delta-ac-max-smart.yaml +++ b/templates/release/en/charger/delta-ac-max-smart.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/delta-slim-charger.yaml b/templates/release/en/charger/delta-slim-charger.yaml index 445a3a7a10..43189d2fec 100644 --- a/templates/release/en/charger/delta-slim-charger.yaml +++ b/templates/release/en/charger/delta-slim-charger.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/delta-ultra-fast-charger.yaml b/templates/release/en/charger/delta-ultra-fast-charger.yaml index 0fefe6ee67..26a6da0106 100644 --- a/templates/release/en/charger/delta-ultra-fast-charger.yaml +++ b/templates/release/en/charger/delta-ultra-fast-charger.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/e-on-drive-ebox.yaml b/templates/release/en/charger/e-on-drive-ebox.yaml index 932f0f1f8c..328ea1207b 100644 --- a/templates/release/en/charger/e-on-drive-ebox.yaml +++ b/templates/release/en/charger/e-on-drive-ebox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/e-on-drive-vbox.yaml b/templates/release/en/charger/e-on-drive-vbox.yaml index f5f5f857c8..c31520291e 100644 --- a/templates/release/en/charger/e-on-drive-vbox.yaml +++ b/templates/release/en/charger/e-on-drive-vbox.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/e3-dc-easy-connect.yaml b/templates/release/en/charger/e3-dc-easy-connect.yaml index 34f8650441..b9e30c8b06 100644 --- a/templates/release/en/charger/e3-dc-easy-connect.yaml +++ b/templates/release/en/charger/e3-dc-easy-connect.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/easee-charge-core.yaml b/templates/release/en/charger/easee-charge-core.yaml index 24ebb5b7cc..eb0d2bcaaa 100644 --- a/templates/release/en/charger/easee-charge-core.yaml +++ b/templates/release/en/charger/easee-charge-core.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger serial number help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentication enabled help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/charger/easee-charge-lite.yaml b/templates/release/en/charger/easee-charge-lite.yaml index a59992e01c..8297dd763c 100644 --- a/templates/release/en/charger/easee-charge-lite.yaml +++ b/templates/release/en/charger/easee-charge-lite.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger serial number help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentication enabled help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/charger/easee-charge.yaml b/templates/release/en/charger/easee-charge.yaml index ac65e51964..9082e05491 100644 --- a/templates/release/en/charger/easee-charge.yaml +++ b/templates/release/en/charger/easee-charge.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger serial number help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentication enabled help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/charger/easee-home.yaml b/templates/release/en/charger/easee-home.yaml index 1b87517dcb..8160c69aeb 100644 --- a/templates/release/en/charger/easee-home.yaml +++ b/templates/release/en/charger/easee-home.yaml @@ -11,9 +11,9 @@ render: template: easee user: # Username, Email address password: # Password, same as Easee app or the web portal (https://easee.cloud) - charger: EH______ + charger: EH______ # Charger serial number timeout: 20s # Timeout, Timeout specifically for Easee API interactions. Can reduce warnings and errors in case of lagging Easee API. (optional) - authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) + authorize: # Authentication enabled, Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional) params: - name: user example: @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Charger serial number help: advanced: false optional: false @@ -56,7 +56,7 @@ params: default: choice: [] unit: - description: + description: Authentication enabled help: Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/charger/ebee-wallbox.yaml b/templates/release/en/charger/ebee-wallbox.yaml index 3cf64f9b1f..0eda4cf81a 100644 --- a/templates/release/en/charger/ebee-wallbox.yaml +++ b/templates/release/en/charger/ebee-wallbox.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml b/templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml index d648bddcec..257f0d1cd5 100644 --- a/templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml +++ b/templates/release/en/charger/ecoharmony-evse-epc-2-0-plus.yaml @@ -32,7 +32,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/edgetech-smart-evse.yaml b/templates/release/en/charger/edgetech-smart-evse.yaml index c34cb02e76..6c58917f3b 100644 --- a/templates/release/en/charger/edgetech-smart-evse.yaml +++ b/templates/release/en/charger/edgetech-smart-evse.yaml @@ -27,7 +27,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/elco.yaml b/templates/release/en/charger/elco.yaml index 81b2395070..7f10785ee7 100644 --- a/templates/release/en/charger/elco.yaml +++ b/templates/release/en/charger/elco.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -25,15 +25,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -42,8 +42,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -51,7 +51,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/elecq-biz.yaml b/templates/release/en/charger/elecq-biz.yaml index 429fda9d37..e060d9ed5f 100644 --- a/templates/release/en/charger/elecq-biz.yaml +++ b/templates/release/en/charger/elecq-biz.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elecq-home.yaml b/templates/release/en/charger/elecq-home.yaml index dad2cfd2d7..d34574978d 100644 --- a/templates/release/en/charger/elecq-home.yaml +++ b/templates/release/en/charger/elecq-home.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/elecq-station.yaml b/templates/release/en/charger/elecq-station.yaml index 0fd4eef97e..ad230b0433 100644 --- a/templates/release/en/charger/elecq-station.yaml +++ b/templates/release/en/charger/elecq-station.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-elecq - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/eledio-go.yaml b/templates/release/en/charger/eledio-go.yaml index 0c24bb5cc2..3fe1f1c1f7 100644 --- a/templates/release/en/charger/eledio-go.yaml +++ b/templates/release/en/charger/eledio-go.yaml @@ -12,17 +12,17 @@ render: - default: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -30,7 +30,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -47,8 +47,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -56,8 +56,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -65,8 +65,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -74,8 +74,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -83,7 +83,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml b/templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml index 40c98dfd6e..8484ecc504 100644 --- a/templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml +++ b/templates/release/en/charger/em2go-pro-power-ocpp-onc.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/enercab-smart.yaml b/templates/release/en/charger/enercab-smart.yaml index 6e38d0a6c5..39fa64dc5a 100644 --- a/templates/release/en/charger/enercab-smart.yaml +++ b/templates/release/en/charger/enercab-smart.yaml @@ -12,17 +12,17 @@ render: - default: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-enercab - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -30,7 +30,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -47,8 +47,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -56,8 +56,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -65,8 +65,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -74,8 +74,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -83,7 +83,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/enplus-ac-ev-charger.yaml b/templates/release/en/charger/enplus-ac-ev-charger.yaml index 8b811c9b4f..8e76d4283b 100644 --- a/templates/release/en/charger/enplus-ac-ev-charger.yaml +++ b/templates/release/en/charger/enplus-ac-ev-charger.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-enplus - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/ensto-chago-wallbox.yaml b/templates/release/en/charger/ensto-chago-wallbox.yaml index 7ccf03073e..977b1804df 100644 --- a/templates/release/en/charger/ensto-chago-wallbox.yaml +++ b/templates/release/en/charger/ensto-chago-wallbox.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/entratek-power-dot-fix.yaml b/templates/release/en/charger/entratek-power-dot-fix.yaml index 5927676fd9..856663b827 100644 --- a/templates/release/en/charger/entratek-power-dot-fix.yaml +++ b/templates/release/en/charger/entratek-power-dot-fix.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/entratek-power-dot-pro-2.yaml b/templates/release/en/charger/entratek-power-dot-pro-2.yaml index cf26d709e1..e65d14cd9d 100644 --- a/templates/release/en/charger/entratek-power-dot-pro-2.yaml +++ b/templates/release/en/charger/entratek-power-dot-pro-2.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-entratek - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/esl-walli-light.yaml b/templates/release/en/charger/esl-walli-light.yaml index 1dd5790664..d09e4bf090 100644 --- a/templates/release/en/charger/esl-walli-light.yaml +++ b/templates/release/en/charger/esl-walli-light.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/evbox-elvi.yaml b/templates/release/en/charger/evbox-elvi.yaml index 482c84ae1f..698e02e66b 100644 --- a/templates/release/en/charger/evbox-elvi.yaml +++ b/templates/release/en/charger/evbox-elvi.yaml @@ -8,18 +8,18 @@ render: - default: | type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) + meter: true # Meter ID, optional advanced: | type: template template: ocpp-evbox-elvi - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) - meter: true # optional + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) + meter: true # Meter ID, optional connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: meter @@ -35,7 +35,7 @@ params: default: true choice: [] unit: - description: + description: Meter ID help: advanced: false optional: true @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -62,8 +62,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -71,8 +71,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/evse-din.yaml b/templates/release/en/charger/evse-din.yaml index 782107d0b0..a7f83a5263 100644 --- a/templates/release/en/charger/evse-din.yaml +++ b/templates/release/en/charger/evse-din.yaml @@ -25,7 +25,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/free2move-eprowallbox-move.yaml b/templates/release/en/charger/free2move-eprowallbox-move.yaml index 1e8b314567..6eb60d4fe4 100644 --- a/templates/release/en/charger/free2move-eprowallbox-move.yaml +++ b/templates/release/en/charger/free2move-eprowallbox-move.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/free2move-eprowallbox.yaml b/templates/release/en/charger/free2move-eprowallbox.yaml index 095c5fd108..540f8046bb 100644 --- a/templates/release/en/charger/free2move-eprowallbox.yaml +++ b/templates/release/en/charger/free2move-eprowallbox.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/free2move-esolutions-eprowallbox.yaml b/templates/release/en/charger/free2move-esolutions-eprowallbox.yaml index 6d6a946c05..28c58aadd1 100644 --- a/templates/release/en/charger/free2move-esolutions-eprowallbox.yaml +++ b/templates/release/en/charger/free2move-esolutions-eprowallbox.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-esolutions - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/fronius-wattpilot-ocpp.yaml b/templates/release/en/charger/fronius-wattpilot-ocpp.yaml index 4e78bbd58e..3498f8bc7a 100644 --- a/templates/release/en/charger/fronius-wattpilot-ocpp.yaml +++ b/templates/release/en/charger/fronius-wattpilot-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/garo-glb.yaml b/templates/release/en/charger/garo-glb.yaml index cdb2b7ec35..483836c624 100644 --- a/templates/release/en/charger/garo-glb.yaml +++ b/templates/release/en/charger/garo-glb.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/garo-glbplus.yaml b/templates/release/en/charger/garo-glbplus.yaml index 66e57286c8..a01f952800 100644 --- a/templates/release/en/charger/garo-glbplus.yaml +++ b/templates/release/en/charger/garo-glbplus.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/garo-ls4-compact.yaml b/templates/release/en/charger/garo-ls4-compact.yaml index 99aeb05fa1..d396cb53a8 100644 --- a/templates/release/en/charger/garo-ls4-compact.yaml +++ b/templates/release/en/charger/garo-ls4-compact.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/garo-ls4.yaml b/templates/release/en/charger/garo-ls4.yaml index d299feef7d..3c22075bf6 100644 --- a/templates/release/en/charger/garo-ls4.yaml +++ b/templates/release/en/charger/garo-ls4.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/go-e-charger-gemini-ocpp.yaml b/templates/release/en/charger/go-e-charger-gemini-ocpp.yaml index 16e1e68c17..4b6a66be08 100644 --- a/templates/release/en/charger/go-e-charger-gemini-ocpp.yaml +++ b/templates/release/en/charger/go-e-charger-gemini-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-pro-ocpp.yaml b/templates/release/en/charger/go-e-charger-pro-ocpp.yaml index 0ed39bb987..68fda4ef77 100644 --- a/templates/release/en/charger/go-e-charger-pro-ocpp.yaml +++ b/templates/release/en/charger/go-e-charger-pro-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/go-e-charger-v3-ocpp.yaml b/templates/release/en/charger/go-e-charger-v3-ocpp.yaml index d24b717b59..80bad9b382 100644 --- a/templates/release/en/charger/go-e-charger-v3-ocpp.yaml +++ b/templates/release/en/charger/go-e-charger-v3-ocpp.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-goe - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/heidelberg-energy-control.yaml b/templates/release/en/charger/heidelberg-energy-control.yaml index c298a4b722..7ea04dd791 100644 --- a/templates/release/en/charger/heidelberg-energy-control.yaml +++ b/templates/release/en/charger/heidelberg-energy-control.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/hesotec-ebox.yaml b/templates/release/en/charger/hesotec-ebox.yaml index 5c80164d4a..9e626fdd04 100644 --- a/templates/release/en/charger/hesotec-ebox.yaml +++ b/templates/release/en/charger/hesotec-ebox.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/hesotec-esat.yaml b/templates/release/en/charger/hesotec-esat.yaml index 4c93f63fa0..d6c99a979f 100644 --- a/templates/release/en/charger/hesotec-esat.yaml +++ b/templates/release/en/charger/hesotec-esat.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/homecharge-homecharger.yaml b/templates/release/en/charger/homecharge-homecharger.yaml index acb7086b89..33fb517e5d 100644 --- a/templates/release/en/charger/homecharge-homecharger.yaml +++ b/templates/release/en/charger/homecharge-homecharger.yaml @@ -13,17 +13,17 @@ render: - default: | type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-homecharge - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -31,7 +31,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -48,8 +48,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -57,8 +57,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -66,8 +66,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -75,8 +75,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -84,7 +84,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/homematic-ip.yaml b/templates/release/en/charger/homematic-ip.yaml index 38325c66b2..3e395ea6df 100644 --- a/templates/release/en/charger/homematic-ip.yaml +++ b/templates/release/en/charger/homematic-ip.yaml @@ -8,7 +8,7 @@ render: type: template template: homematic host: 192.0.2.2 # IP address or hostname - port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC server port number, optional device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) @@ -17,14 +17,14 @@ render: type: template template: homematic host: 192.0.2.2 # IP address or hostname - port: 2010 # XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010), optional + port: 2010 # XML-RPC server port number, optional device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2), Homematic meter channel number like shown in the CCU web user interface. - switchchannel: 3 # Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1), Homematic switch actor channel number like shown in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown in the CCU web user interface. + switchchannel: 3 # Switch/Actor channel number, Homematic switch actor channel number like shown in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) icon: # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) @@ -39,11 +39,11 @@ params: advanced: false optional: false - name: port - example: + example: BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010 default: 2010 choice: [] unit: - description: XML-RPC server port number (BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010) + description: XML-RPC server port number help: advanced: false optional: true @@ -84,20 +84,20 @@ params: advanced: false optional: true - name: meterchannel - example: + example: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2 default: 6 choice: [] unit: - description: Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2) + description: Meter channel number help: Homematic meter channel number like shown in the CCU web user interface. advanced: true optional: false - name: switchchannel - example: + example: HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1 default: 3 choice: [] unit: - description: Switch/Actor channel number (HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1) + description: Switch/Actor channel number help: Homematic switch actor channel number like shown in the CCU web user interface. advanced: true optional: false @@ -106,7 +106,7 @@ params: default: 1s choice: [] unit: - description: XML-RPC api cache duration - Default 1s. (valid units are s,m,h) + description: XML-RPC API cache duration help: In case of duty cycle problems try a cache setting of 30s. advanced: true optional: true diff --git a/templates/release/en/charger/huawei-scharger-22kt-s0.yaml b/templates/release/en/charger/huawei-scharger-22kt-s0.yaml index 4596d621f3..52f0bb5434 100644 --- a/templates/release/en/charger/huawei-scharger-22kt-s0.yaml +++ b/templates/release/en/charger/huawei-scharger-22kt-s0.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/huawei-scharger-7ks-s0.yaml b/templates/release/en/charger/huawei-scharger-7ks-s0.yaml index b147a22584..ba66d59eac 100644 --- a/templates/release/en/charger/huawei-scharger-7ks-s0.yaml +++ b/templates/release/en/charger/huawei-scharger-7ks-s0.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-huawei - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/idm.yaml b/templates/release/en/charger/idm.yaml index 1c94b7a8cc..f6260fba92 100644 --- a/templates/release/en/charger/idm.yaml +++ b/templates/release/en/charger/idm.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/innogy-ebox.yaml b/templates/release/en/charger/innogy-ebox.yaml index 4d8616ac7e..004843e2b5 100644 --- a/templates/release/en/charger/innogy-ebox.yaml +++ b/templates/release/en/charger/innogy-ebox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/juice-charger-me.yaml b/templates/release/en/charger/juice-charger-me.yaml index 51a7b93f7f..9f22708322 100644 --- a/templates/release/en/charger/juice-charger-me.yaml +++ b/templates/release/en/charger/juice-charger-me.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/junkers-sg-ready.yaml b/templates/release/en/charger/junkers-sg-ready.yaml index 6b0049bb08..50f42cfaf1 100644 --- a/templates/release/en/charger/junkers-sg-ready.yaml +++ b/templates/release/en/charger/junkers-sg-ready.yaml @@ -11,7 +11,7 @@ render: type: template template: emsesp host: 192.0.2.2 # IP address or hostname - token: # optional + token: # Token, optional powersource: hpcurrpower # Power source, [hpcurrpower, hppower] (optional) tempsource: # Temperature source, [warmwater] (optional) params: @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true diff --git a/templates/release/en/charger/kathrein-kwb-ac20.yaml b/templates/release/en/charger/kathrein-kwb-ac20.yaml index 5028dd5e05..898362ebb6 100644 --- a/templates/release/en/charger/kathrein-kwb-ac20.yaml +++ b/templates/release/en/charger/kathrein-kwb-ac20.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/kathrein-kwb-ac35.yaml b/templates/release/en/charger/kathrein-kwb-ac35.yaml index bd31023595..17b7afa7a2 100644 --- a/templates/release/en/charger/kathrein-kwb-ac35.yaml +++ b/templates/release/en/charger/kathrein-kwb-ac35.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/kathrein-kwb-ac40-e.yaml b/templates/release/en/charger/kathrein-kwb-ac40-e.yaml index 0b795f3734..bfe949479b 100644 --- a/templates/release/en/charger/kathrein-kwb-ac40-e.yaml +++ b/templates/release/en/charger/kathrein-kwb-ac40-e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/kathrein-kwb-ac40.yaml b/templates/release/en/charger/kathrein-kwb-ac40.yaml index 07a252b7c4..986a01f8fc 100644 --- a/templates/release/en/charger/kathrein-kwb-ac40.yaml +++ b/templates/release/en/charger/kathrein-kwb-ac40.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/kathrein-kwb-ac60-e.yaml b/templates/release/en/charger/kathrein-kwb-ac60-e.yaml index d226dc0204..5455e1e5fc 100644 --- a/templates/release/en/charger/kathrein-kwb-ac60-e.yaml +++ b/templates/release/en/charger/kathrein-kwb-ac60-e.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/kathrein-kwb-ac60.yaml b/templates/release/en/charger/kathrein-kwb-ac60.yaml index e36ff55fe7..7017c59b8a 100644 --- a/templates/release/en/charger/kathrein-kwb-ac60.yaml +++ b/templates/release/en/charger/kathrein-kwb-ac60.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/keba-kecontact-p20.yaml b/templates/release/en/charger/keba-kecontact-p20.yaml index b26307061d..4fd1f524da 100644 --- a/templates/release/en/charger/keba-kecontact-p20.yaml +++ b/templates/release/en/charger/keba-kecontact-p20.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/keba-kecontact-p30-c-series.yaml b/templates/release/en/charger/keba-kecontact-p30-c-series.yaml index 498bad6c24..f085038fa5 100644 --- a/templates/release/en/charger/keba-kecontact-p30-c-series.yaml +++ b/templates/release/en/charger/keba-kecontact-p30-c-series.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/keba-kecontact-p30-x-series.yaml b/templates/release/en/charger/keba-kecontact-p30-x-series.yaml index 1bb21b4672..44f6062839 100644 --- a/templates/release/en/charger/keba-kecontact-p30-x-series.yaml +++ b/templates/release/en/charger/keba-kecontact-p30-x-series.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/keba-kecontact-p40-pro.yaml b/templates/release/en/charger/keba-kecontact-p40-pro.yaml index a632a837ea..aa133df2a8 100644 --- a/templates/release/en/charger/keba-kecontact-p40-pro.yaml +++ b/templates/release/en/charger/keba-kecontact-p40-pro.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/keba-kecontact-p40.yaml b/templates/release/en/charger/keba-kecontact-p40.yaml index 1ba138f981..1bdebf15d6 100644 --- a/templates/release/en/charger/keba-kecontact-p40.yaml +++ b/templates/release/en/charger/keba-kecontact-p40.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/kermi-x-center-pro.yaml b/templates/release/en/charger/kermi-x-center-pro.yaml index c9c86a94ed..0d4de2b510 100644 --- a/templates/release/en/charger/kermi-x-center-pro.yaml +++ b/templates/release/en/charger/kermi-x-center-pro.yaml @@ -15,7 +15,7 @@ render: template: kermi host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater, buffer] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -40,7 +40,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/kostal-enector.yaml b/templates/release/en/charger/kostal-enector.yaml index 6ec447a413..1ca33876ea 100644 --- a/templates/release/en/charger/kostal-enector.yaml +++ b/templates/release/en/charger/kostal-enector.yaml @@ -33,7 +33,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/kse-wbx16.yaml b/templates/release/en/charger/kse-wbx16.yaml index c562f20efd..5de347ad38 100644 --- a/templates/release/en/charger/kse-wbx16.yaml +++ b/templates/release/en/charger/kse-wbx16.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/ladefoxx-evload.yaml b/templates/release/en/charger/ladefoxx-evload.yaml index 2b3d505acb..0093c1e939 100644 --- a/templates/release/en/charger/ladefoxx-evload.yaml +++ b/templates/release/en/charger/ladefoxx-evload.yaml @@ -29,7 +29,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/ladefoxx-mikro-2-0.yaml b/templates/release/en/charger/ladefoxx-mikro-2-0.yaml index bb15c9c9e8..4d9ce8af2d 100644 --- a/templates/release/en/charger/ladefoxx-mikro-2-0.yaml +++ b/templates/release/en/charger/ladefoxx-mikro-2-0.yaml @@ -29,7 +29,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/lambda-eu-l-series.yaml b/templates/release/en/charger/lambda-eu-l-series.yaml index d90d02721f..17b060aef1 100644 --- a/templates/release/en/charger/lambda-eu-l-series.yaml +++ b/templates/release/en/charger/lambda-eu-l-series.yaml @@ -21,7 +21,7 @@ render: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -46,7 +46,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/lrt-home-essentialplus.yaml b/templates/release/en/charger/lrt-home-essentialplus.yaml index e772fa61d8..75ed42b7fc 100644 --- a/templates/release/en/charger/lrt-home-essentialplus.yaml +++ b/templates/release/en/charger/lrt-home-essentialplus.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amedio-professional.yaml b/templates/release/en/charger/mennekes-amedio-professional.yaml index 36add13db9..65dd31808f 100644 --- a/templates/release/en/charger/mennekes-amedio-professional.yaml +++ b/templates/release/en/charger/mennekes-amedio-professional.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-4business-700.yaml b/templates/release/en/charger/mennekes-amtron-4business-700.yaml index 2e89144629..7e829fb746 100644 --- a/templates/release/en/charger/mennekes-amtron-4business-700.yaml +++ b/templates/release/en/charger/mennekes-amtron-4business-700.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-4you-300.yaml b/templates/release/en/charger/mennekes-amtron-4you-300.yaml index 3a8cc64988..ed13de10f3 100644 --- a/templates/release/en/charger/mennekes-amtron-4you-300.yaml +++ b/templates/release/en/charger/mennekes-amtron-4you-300.yaml @@ -33,7 +33,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-4you-500.yaml b/templates/release/en/charger/mennekes-amtron-4you-500.yaml index d61ecc493b..b0b25cbee5 100644 --- a/templates/release/en/charger/mennekes-amtron-4you-500.yaml +++ b/templates/release/en/charger/mennekes-amtron-4you-500.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-chargecontrol.yaml b/templates/release/en/charger/mennekes-amtron-chargecontrol.yaml index f9551c603c..7d6e15501c 100644 --- a/templates/release/en/charger/mennekes-amtron-chargecontrol.yaml +++ b/templates/release/en/charger/mennekes-amtron-chargecontrol.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml b/templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml index 9ec9376da4..3288a95474 100644 --- a/templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml +++ b/templates/release/en/charger/mennekes-amtron-compact-2-0s.yaml @@ -33,7 +33,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-premium.yaml b/templates/release/en/charger/mennekes-amtron-premium.yaml index 4d919d93dc..7cb5aed88a 100644 --- a/templates/release/en/charger/mennekes-amtron-premium.yaml +++ b/templates/release/en/charger/mennekes-amtron-premium.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-professional.yaml b/templates/release/en/charger/mennekes-amtron-professional.yaml index 32802f436d..daedc6723f 100644 --- a/templates/release/en/charger/mennekes-amtron-professional.yaml +++ b/templates/release/en/charger/mennekes-amtron-professional.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-amtron-xtra.yaml b/templates/release/en/charger/mennekes-amtron-xtra.yaml index 1669a80f46..3474ca33d7 100644 --- a/templates/release/en/charger/mennekes-amtron-xtra.yaml +++ b/templates/release/en/charger/mennekes-amtron-xtra.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/mennekes-emobility-gateway-acu.yaml b/templates/release/en/charger/mennekes-emobility-gateway-acu.yaml index 8c86d3d8ef..4b9c44d726 100644 --- a/templates/release/en/charger/mennekes-emobility-gateway-acu.yaml +++ b/templates/release/en/charger/mennekes-emobility-gateway-acu.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-smart-acu.yaml b/templates/release/en/charger/mennekes-smart-acu.yaml index ee8c14ea55..147cc0a13b 100644 --- a/templates/release/en/charger/mennekes-smart-acu.yaml +++ b/templates/release/en/charger/mennekes-smart-acu.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/mennekes-smart-t-acu.yaml b/templates/release/en/charger/mennekes-smart-t-acu.yaml index 0881909243..d5a49285cc 100644 --- a/templates/release/en/charger/mennekes-smart-t-acu.yaml +++ b/templates/release/en/charger/mennekes-smart-t-acu.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-mennekes-acu - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/my-pv-ac-elwa-2.yaml b/templates/release/en/charger/my-pv-ac-elwa-2.yaml index 4a97e43e27..594db41648 100644 --- a/templates/release/en/charger/my-pv-ac-elwa-2.yaml +++ b/templates/release/en/charger/my-pv-ac-elwa-2.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/my-pv-ac-thor-9s.yaml b/templates/release/en/charger/my-pv-ac-thor-9s.yaml index 27e4da3e20..77775768b6 100644 --- a/templates/release/en/charger/my-pv-ac-thor-9s.yaml +++ b/templates/release/en/charger/my-pv-ac-thor-9s.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + tempsource: 1 # Temperature source, [1, 2, 3] (optional) scale: 1 # Scale factor for power limit, optional params: - name: modbus @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -32,7 +32,7 @@ params: default: 1 choice: ['1', '2', '3'] unit: - description: Temperature sensor + description: Temperature source help: advanced: false optional: true diff --git a/templates/release/en/charger/my-pv-ac-thor.yaml b/templates/release/en/charger/my-pv-ac-thor.yaml index 7a240c5ef2..1ceb501af0 100644 --- a/templates/release/en/charger/my-pv-ac-thor.yaml +++ b/templates/release/en/charger/my-pv-ac-thor.yaml @@ -15,7 +15,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - tempsource: 1 # Temperature sensor, [1, 2, 3] (optional) + tempsource: 1 # Temperature source, [1, 2, 3] (optional) scale: 1 # Scale factor for power limit, optional params: - name: modbus @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -32,7 +32,7 @@ params: default: 1 choice: ['1', '2', '3'] unit: - description: Temperature sensor + description: Temperature source help: advanced: false optional: true diff --git a/templates/release/en/charger/nibe-ap-aw10.yaml b/templates/release/en/charger/nibe-ap-aw10.yaml index 867b468dce..79a58e3caa 100644 --- a/templates/release/en/charger/nibe-ap-aw10.yaml +++ b/templates/release/en/charger/nibe-ap-aw10.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/novelan-wpr-net.yaml b/templates/release/en/charger/novelan-wpr-net.yaml index 9aca44539d..4a1eb53637 100644 --- a/templates/release/en/charger/novelan-wpr-net.yaml +++ b/templates/release/en/charger/novelan-wpr-net.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/nrgkick-connect.yaml b/templates/release/en/charger/nrgkick-connect.yaml index 4c0e2d7bce..f240d0b922 100644 --- a/templates/release/en/charger/nrgkick-connect.yaml +++ b/templates/release/en/charger/nrgkick-connect.yaml @@ -10,7 +10,7 @@ render: type: template template: nrgkick-connect host: 192.0.2.2 # IP address or hostname - mac: + mac: # MAC Address password: # Password, Use single quotes in case of leading zeros params: - name: host @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: MAC Address help: advanced: false optional: false diff --git a/templates/release/en/charger/nrgkick-gen2.yaml b/templates/release/en/charger/nrgkick-gen2.yaml index 4a807075d6..30f6889d79 100644 --- a/templates/release/en/charger/nrgkick-gen2.yaml +++ b/templates/release/en/charger/nrgkick-gen2.yaml @@ -24,14 +24,14 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - phases1p3p: false # Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. (optional) + phases1p3p: false # Phase Switching enabled, Extended feature "Phase Switching" must be activated in the NRGKick app. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -40,8 +40,8 @@ params: default: false choice: [] unit: - description: - help: Activates phase switching. Extended feature "Phase Switching" must be activated in the NRGKick app. + description: Phase Switching enabled + help: Extended feature "Phase Switching" must be activated in the NRGKick app. advanced: true optional: true modbus: diff --git a/templates/release/en/charger/obo-bettermann-ion.yaml b/templates/release/en/charger/obo-bettermann-ion.yaml index f0eb202144..bb1946c942 100644 --- a/templates/release/en/charger/obo-bettermann-ion.yaml +++ b/templates/release/en/charger/obo-bettermann-ion.yaml @@ -32,7 +32,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml b/templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml index 406f9c4a3b..6a32a552b0 100644 --- a/templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml +++ b/templates/release/en/charger/ocpp-1-6j-compatible-smart-charging.yaml @@ -30,17 +30,17 @@ render: - default: | type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -48,7 +48,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -65,8 +65,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -74,8 +74,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -83,8 +83,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -92,8 +92,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -101,7 +101,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/openwb-software-2-x.yaml b/templates/release/en/charger/openwb-software-2-x.yaml index 67481d919f..c064a4fd67 100644 --- a/templates/release/en/charger/openwb-software-2-x.yaml +++ b/templates/release/en/charger/openwb-software-2-x.yaml @@ -38,7 +38,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/optec-mobility-one.yaml b/templates/release/en/charger/optec-mobility-one.yaml index 9ebb1648ad..892d0e5d12 100644 --- a/templates/release/en/charger/optec-mobility-one.yaml +++ b/templates/release/en/charger/optec-mobility-one.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/orbis-viaris.yaml b/templates/release/en/charger/orbis-viaris.yaml index 16e797ffa5..dc9d92daab 100644 --- a/templates/release/en/charger/orbis-viaris.yaml +++ b/templates/release/en/charger/orbis-viaris.yaml @@ -8,17 +8,17 @@ render: - default: | type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-orbis - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -26,7 +26,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -43,8 +43,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -61,8 +61,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -70,8 +70,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -79,7 +79,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/peblar-business.yaml b/templates/release/en/charger/peblar-business.yaml index 4e05b5a4df..84f56ce2c9 100644 --- a/templates/release/en/charger/peblar-business.yaml +++ b/templates/release/en/charger/peblar-business.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/peblar-home-plus.yaml b/templates/release/en/charger/peblar-home-plus.yaml index a289474e50..2f2ac7031a 100644 --- a/templates/release/en/charger/peblar-home-plus.yaml +++ b/templates/release/en/charger/peblar-home-plus.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/peblar-home.yaml b/templates/release/en/charger/peblar-home.yaml index 4d94c82455..76a4aa2a27 100644 --- a/templates/release/en/charger/peblar-home.yaml +++ b/templates/release/en/charger/peblar-home.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/phoenix-contact-charx.yaml b/templates/release/en/charger/phoenix-contact-charx.yaml index ddd15513c8..ebaada4ad4 100644 --- a/templates/release/en/charger/phoenix-contact-charx.yaml +++ b/templates/release/en/charger/phoenix-contact-charx.yaml @@ -29,7 +29,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml b/templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml index 61f1ab493f..91c9681fd3 100644 --- a/templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml +++ b/templates/release/en/charger/phoenix-contact-em-cp-pp-eth.yaml @@ -19,7 +19,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml index f649ef2acb..32456f424f 100644 --- a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml index 99b79a1724..902579d23b 100644 --- a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml index 5d18695bda..eef29ed1cc 100644 --- a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml index 2d7353b28a..90cf8bd000 100644 --- a/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml +++ b/templates/release/en/charger/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/phoenix-contact-ev-ser.yaml b/templates/release/en/charger/phoenix-contact-ev-ser.yaml index ff1e20eb68..19e7d37fc9 100644 --- a/templates/release/en/charger/phoenix-contact-ev-ser.yaml +++ b/templates/release/en/charger/phoenix-contact-ev-ser.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/plugchoice.yaml b/templates/release/en/charger/plugchoice.yaml index 2288c51f42..b394db8eda 100644 --- a/templates/release/en/charger/plugchoice.yaml +++ b/templates/release/en/charger/plugchoice.yaml @@ -18,39 +18,39 @@ render: - default: | type: template template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456) + token: # Token, API Token + identity: AA123456 # Charger identity advanced: | type: template template: plugchoice - token: # API Token - identity: # Charger identity (e.g. AA123456) - connector: 1 # Loadpoint (if >1 loadpoint), Connector ID (usually 1) + token: # Token, API Token + identity: AA123456 # Charger identity + connector: 1 # Connector ID params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token advanced: false optional: false - name: identity - example: + example: AA123456 default: choice: [] unit: - description: - help: Charger identity (e.g. AA123456) + description: Charger identity + help: advanced: false optional: false - name: connector - example: + example: 1 default: 1 choice: [] unit: - description: Loadpoint (if >1 loadpoint) - help: Connector ID (usually 1) + description: Connector ID + help: advanced: true optional: false \ No newline at end of file diff --git a/templates/release/en/charger/pracht-alpha-xt.yaml b/templates/release/en/charger/pracht-alpha-xt.yaml index 691bd21ded..d4df709364 100644 --- a/templates/release/en/charger/pracht-alpha-xt.yaml +++ b/templates/release/en/charger/pracht-alpha-xt.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/pracht-mono-xt.yaml b/templates/release/en/charger/pracht-mono-xt.yaml index 28323f4f86..fa1efec002 100644 --- a/templates/release/en/charger/pracht-mono-xt.yaml +++ b/templates/release/en/charger/pracht-mono-xt.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/pracht-pni.yaml b/templates/release/en/charger/pracht-pni.yaml index cb145e826c..a94a49a843 100644 --- a/templates/release/en/charger/pracht-pni.yaml +++ b/templates/release/en/charger/pracht-pni.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/pracht-xtplus.yaml b/templates/release/en/charger/pracht-xtplus.yaml index 3e44cdb035..8dcd17f27e 100644 --- a/templates/release/en/charger/pracht-xtplus.yaml +++ b/templates/release/en/charger/pracht-xtplus.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/pulsares-simplebox.yaml b/templates/release/en/charger/pulsares-simplebox.yaml index 089c80a4d5..dba6e89741 100644 --- a/templates/release/en/charger/pulsares-simplebox.yaml +++ b/templates/release/en/charger/pulsares-simplebox.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/qcells-q-home-edrive-a.yaml b/templates/release/en/charger/qcells-q-home-edrive-a.yaml index 0292ea895a..80ea8dcec7 100644 --- a/templates/release/en/charger/qcells-q-home-edrive-a.yaml +++ b/templates/release/en/charger/qcells-q-home-edrive-a.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/roth-thermoaura.yaml b/templates/release/en/charger/roth-thermoaura.yaml index 0fae90c9fd..45f8b6972d 100644 --- a/templates/release/en/charger/roth-thermoaura.yaml +++ b/templates/release/en/charger/roth-thermoaura.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/roth-thermoterra.yaml b/templates/release/en/charger/roth-thermoterra.yaml index 62cc89cb8a..095a26c78c 100644 --- a/templates/release/en/charger/roth-thermoterra.yaml +++ b/templates/release/en/charger/roth-thermoterra.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/schneider-evlink-pro.yaml b/templates/release/en/charger/schneider-evlink-pro.yaml index 2204af38ba..13dd023ebb 100644 --- a/templates/release/en/charger/schneider-evlink-pro.yaml +++ b/templates/release/en/charger/schneider-evlink-pro.yaml @@ -20,7 +20,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/schrack-i-charge-cion.yaml b/templates/release/en/charger/schrack-i-charge-cion.yaml index 921cd93531..f3f3b77e27 100644 --- a/templates/release/en/charger/schrack-i-charge-cion.yaml +++ b/templates/release/en/charger/schrack-i-charge-cion.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/senec-wallbox-pro-s.yaml b/templates/release/en/charger/senec-wallbox-pro-s.yaml index 4db76c3745..3fa08b9276 100644 --- a/templates/release/en/charger/senec-wallbox-pro-s.yaml +++ b/templates/release/en/charger/senec-wallbox-pro-s.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/senec-wallbox-pro.yaml b/templates/release/en/charger/senec-wallbox-pro.yaml index 8dd32cad59..8369de9742 100644 --- a/templates/release/en/charger/senec-wallbox-pro.yaml +++ b/templates/release/en/charger/senec-wallbox-pro.yaml @@ -29,7 +29,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/shelly-1.yaml b/templates/release/en/charger/shelly-1.yaml index 2725ecee02..6845a753a0 100644 --- a/templates/release/en/charger/shelly-1.yaml +++ b/templates/release/en/charger/shelly-1.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true diff --git a/templates/release/en/charger/shelly-plug-s.yaml b/templates/release/en/charger/shelly-plug-s.yaml index 4450095afd..f14470ad3d 100644 --- a/templates/release/en/charger/shelly-plug-s.yaml +++ b/templates/release/en/charger/shelly-plug-s.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true diff --git a/templates/release/en/charger/shelly-plus-1.yaml b/templates/release/en/charger/shelly-plus-1.yaml index baf2926e51..fc6c272947 100644 --- a/templates/release/en/charger/shelly-plus-1.yaml +++ b/templates/release/en/charger/shelly-plus-1.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true diff --git a/templates/release/en/charger/shelly-pro-1.yaml b/templates/release/en/charger/shelly-pro-1.yaml index b7d6bcba1f..673757551c 100644 --- a/templates/release/en/charger/shelly-pro-1.yaml +++ b/templates/release/en/charger/shelly-pro-1.yaml @@ -11,7 +11,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) advanced: | type: template @@ -19,7 +19,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional standbypower: 15 # Standby power (W), Power values above this value will be considered as charging power (optional) integrateddevice: # Integrated device, Integrated device. No charging sessions (optional) heating: # Heating device, Shows °C instead of % (optional) @@ -57,7 +57,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true diff --git a/templates/release/en/charger/siemens-versicharge-gen3.yaml b/templates/release/en/charger/siemens-versicharge-gen3.yaml index c52fe42c88..827b7f6fac 100644 --- a/templates/release/en/charger/siemens-versicharge-gen3.yaml +++ b/templates/release/en/charger/siemens-versicharge-gen3.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/smartfox-pro-charger.yaml b/templates/release/en/charger/smartfox-pro-charger.yaml index 488e3de539..c8e953c58b 100644 --- a/templates/release/en/charger/smartfox-pro-charger.yaml +++ b/templates/release/en/charger/smartfox-pro-charger.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/solaredge-home-ev-charger.yaml b/templates/release/en/charger/solaredge-home-ev-charger.yaml index d554fb8398..5b36897a13 100644 --- a/templates/release/en/charger/solaredge-home-ev-charger.yaml +++ b/templates/release/en/charger/solaredge-home-ev-charger.yaml @@ -33,7 +33,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/solax-x3-evc.yaml b/templates/release/en/charger/solax-x3-evc.yaml index 8887f4b2e0..f1985343e3 100644 --- a/templates/release/en/charger/solax-x3-evc.yaml +++ b/templates/release/en/charger/solax-x3-evc.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml b/templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml index abc08a8588..8aa2892f07 100644 --- a/templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml +++ b/templates/release/en/charger/spelsberg-wallbox-smart-pro.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/stark-in-strom-easy.yaml b/templates/release/en/charger/stark-in-strom-easy.yaml index 34909a8afe..dcd81a44ad 100644 --- a/templates/release/en/charger/stark-in-strom-easy.yaml +++ b/templates/release/en/charger/stark-in-strom-easy.yaml @@ -26,7 +26,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml b/templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml index ee82bee39f..a503571e04 100644 --- a/templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml +++ b/templates/release/en/charger/stiebel-eltron-lwa-lwz-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml b/templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml index 1f6a7d687e..79e55c1b51 100644 --- a/templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml +++ b/templates/release/en/charger/stiebel-eltron-wpm-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/sungrow-ac011e-01.yaml b/templates/release/en/charger/sungrow-ac011e-01.yaml index 5b3e3e81ce..c36cbe7541 100644 --- a/templates/release/en/charger/sungrow-ac011e-01.yaml +++ b/templates/release/en/charger/sungrow-ac011e-01.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/sungrow-ac011e.yaml b/templates/release/en/charger/sungrow-ac011e.yaml index fdfd054a4d..938c861ce2 100644 --- a/templates/release/en/charger/sungrow-ac011e.yaml +++ b/templates/release/en/charger/sungrow-ac011e.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-sungrow - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/sungrow-ac22e-01.yaml b/templates/release/en/charger/sungrow-ac22e-01.yaml index 64254227f2..610b97a91f 100644 --- a/templates/release/en/charger/sungrow-ac22e-01.yaml +++ b/templates/release/en/charger/sungrow-ac22e-01.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/tecalor-thz-sg-ready.yaml b/templates/release/en/charger/tecalor-thz-sg-ready.yaml index 511f40d926..424187bf67 100644 --- a/templates/release/en/charger/tecalor-thz-sg-ready.yaml +++ b/templates/release/en/charger/tecalor-thz-sg-ready.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/technisat-technivolt.yaml b/templates/release/en/charger/technisat-technivolt.yaml index a9a31fa574..be218ebced 100644 --- a/templates/release/en/charger/technisat-technivolt.yaml +++ b/templates/release/en/charger/technisat-technivolt.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/tessie.yaml b/templates/release/en/charger/tessie.yaml index 136d61a5cb..743ead340d 100644 --- a/templates/release/en/charger/tessie.yaml +++ b/templates/release/en/charger/tessie.yaml @@ -10,7 +10,7 @@ render: template: tessie vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer token: # Tessie API Token - location: tessiehome # Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) + location: tessiehome # Location, Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) params: - name: vin example: W... @@ -35,7 +35,7 @@ params: default: choice: [] unit: - description: Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) - help: + description: Location + help: Define a location where the Tessie charger will work (always = always, no geofence) or a custom location (exact name) as defined in Tessie (Case sensitive) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/charger/tigo-go-ev-charger.yaml b/templates/release/en/charger/tigo-go-ev-charger.yaml index c1f1f2d9c4..fad2eede59 100644 --- a/templates/release/en/charger/tigo-go-ev-charger.yaml +++ b/templates/release/en/charger/tigo-go-ev-charger.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/tinkerforge-warp-charger-pro.yaml b/templates/release/en/charger/tinkerforge-warp-charger-pro.yaml index b915054b81..09dce1a799 100644 --- a/templates/release/en/charger/tinkerforge-warp-charger-pro.yaml +++ b/templates/release/en/charger/tinkerforge-warp-charger-pro.yaml @@ -15,7 +15,7 @@ render: port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) advanced: | type: template template: tinkerforge-warp @@ -23,7 +23,7 @@ render: port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) params: @@ -68,8 +68,8 @@ params: default: choice: [] unit: - description: - help: WEM Firmware v2 required. EnergyManager MQTT topic (if installed) + description: Energy manager MQTT topic + help: WEM Firmware v2 required. advanced: false optional: true - name: user diff --git a/templates/release/en/charger/tinkerforge-warp-charger-smart.yaml b/templates/release/en/charger/tinkerforge-warp-charger-smart.yaml index b61bb6c102..ced63797ec 100644 --- a/templates/release/en/charger/tinkerforge-warp-charger-smart.yaml +++ b/templates/release/en/charger/tinkerforge-warp-charger-smart.yaml @@ -15,7 +15,7 @@ render: port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) advanced: | type: template template: tinkerforge-warp @@ -23,7 +23,7 @@ render: port: 1883 # Port, MQTT broker port (optional) topic: warp # Topic, Topic (omit leading /) (optional) timeout: 30s # Timeout, Don't accept values older than this value (optional) - energymanager: # WEM Firmware v2 required. EnergyManager MQTT topic (if installed) (optional) + energymanager: # Energy manager MQTT topic, WEM Firmware v2 required. (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) params: @@ -68,8 +68,8 @@ params: default: choice: [] unit: - description: - help: WEM Firmware v2 required. EnergyManager MQTT topic (if installed) + description: Energy manager MQTT topic + help: WEM Firmware v2 required. advanced: false optional: true - name: user diff --git a/templates/release/en/charger/ubitricity-heinz.yaml b/templates/release/en/charger/ubitricity-heinz.yaml index 90db352a18..1d46571166 100644 --- a/templates/release/en/charger/ubitricity-heinz.yaml +++ b/templates/release/en/charger/ubitricity-heinz.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/vaillant-sensonet-sg-ready.yaml b/templates/release/en/charger/vaillant-sensonet-sg-ready.yaml index 833f97a34d..f90047a5dd 100644 --- a/templates/release/en/charger/vaillant-sensonet-sg-ready.yaml +++ b/templates/release/en/charger/vaillant-sensonet-sg-ready.yaml @@ -12,9 +12,9 @@ render: template: vaillant user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - realm: DE # [DE, AT] (optional) - zone: # Boost zone id (optional) - setpoint: # Boost temperature setpoint (optional) + realm: DE # Region, [DE, AT] (optional) + zone: # Boost zone ID, optional + setpoint: # Boost temperature, optional params: - name: user example: @@ -39,7 +39,7 @@ params: default: DE choice: ['DE', 'AT'] unit: - description: + description: Region help: advanced: false optional: true @@ -48,8 +48,8 @@ params: default: choice: [] unit: - description: - help: Boost zone id + description: Boost zone ID + help: advanced: false optional: true - name: setpoint @@ -57,7 +57,7 @@ params: default: choice: [] unit: - description: - help: Boost temperature setpoint + description: Boost temperature + help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/charger/vestel-connect-plus.yaml b/templates/release/en/charger/vestel-connect-plus.yaml index be8156c353..2af0da46f5 100644 --- a/templates/release/en/charger/vestel-connect-plus.yaml +++ b/templates/release/en/charger/vestel-connect-plus.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/vestel-evc04-home-smart.yaml b/templates/release/en/charger/vestel-evc04-home-smart.yaml index 760817a31e..3393b21dc7 100644 --- a/templates/release/en/charger/vestel-evc04-home-smart.yaml +++ b/templates/release/en/charger/vestel-evc04-home-smart.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/victron-ev-charging-station-via-gx.yaml b/templates/release/en/charger/victron-ev-charging-station-via-gx.yaml index eb034f66f4..6cdc5748b6 100644 --- a/templates/release/en/charger/victron-ev-charging-station-via-gx.yaml +++ b/templates/release/en/charger/victron-ev-charging-station-via-gx.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/victron-ev-charging-station.yaml b/templates/release/en/charger/victron-ev-charging-station.yaml index ae75ee2247..741728cee4 100644 --- a/templates/release/en/charger/victron-ev-charging-station.yaml +++ b/templates/release/en/charger/victron-ev-charging-station.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml b/templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml index 53ecd1be96..063c22860d 100644 --- a/templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml +++ b/templates/release/en/charger/viridian-ev-evse-epc-2-0-plus.yaml @@ -32,7 +32,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/volt-time-one.yaml b/templates/release/en/charger/volt-time-one.yaml index 8aecc3c621..cca658f6b9 100644 --- a/templates/release/en/charger/volt-time-one.yaml +++ b/templates/release/en/charger/volt-time-one.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Serial Number help: Serial number (e.g. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/charger/volt-time-source-2.yaml b/templates/release/en/charger/volt-time-source-2.yaml index 04f687ad64..7225175023 100644 --- a/templates/release/en/charger/volt-time-source-2.yaml +++ b/templates/release/en/charger/volt-time-source-2.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Serial Number help: Serial number (e.g. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/charger/volt-time-source-2s.yaml b/templates/release/en/charger/volt-time-source-2s.yaml index 61f89cfd7c..ea2251686b 100644 --- a/templates/release/en/charger/volt-time-source-2s.yaml +++ b/templates/release/en/charger/volt-time-source-2s.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Serial Number help: Serial number (e.g. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/charger/volt-time-source.yaml b/templates/release/en/charger/volt-time-source.yaml index de310e8817..ca00dfca69 100644 --- a/templates/release/en/charger/volt-time-source.yaml +++ b/templates/release/en/charger/volt-time-source.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: volttime - token: # API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) - serial_number: # Serial number (e.g. 1008621) + token: # Token, API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) + serial_number: # Serial Number, Serial number (e.g. 1008621) params: - name: token example: default: choice: [] unit: - description: + description: Token help: API Token (https://developer.volttime.com/api-reference/authentication#personal-access-tokens) advanced: false optional: false @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Serial Number help: Serial number (e.g. 1008621) advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/charger/wallbe-eco-2-0-s.yaml b/templates/release/en/charger/wallbe-eco-2-0-s.yaml index 8ffe2e48e5..84fa3c97df 100644 --- a/templates/release/en/charger/wallbe-eco-2-0-s.yaml +++ b/templates/release/en/charger/wallbe-eco-2-0-s.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/wallbe-eco.yaml b/templates/release/en/charger/wallbe-eco.yaml index 61e02c6596..ae291e41bb 100644 --- a/templates/release/en/charger/wallbe-eco.yaml +++ b/templates/release/en/charger/wallbe-eco.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/wallbe-pro.yaml b/templates/release/en/charger/wallbe-pro.yaml index d1eb089d38..ab7a5da040 100644 --- a/templates/release/en/charger/wallbe-pro.yaml +++ b/templates/release/en/charger/wallbe-pro.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml b/templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml index 64b0edd567..d7383fe142 100644 --- a/templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml +++ b/templates/release/en/charger/wallbox-commander-2-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-commander-2.yaml b/templates/release/en/charger/wallbox-commander-2.yaml index c08f1d2efb..a75d41b579 100644 --- a/templates/release/en/charger/wallbox-commander-2.yaml +++ b/templates/release/en/charger/wallbox-commander-2.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml b/templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml index 19ec95449a..51285f365b 100644 --- a/templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml +++ b/templates/release/en/charger/wallbox-copper-sb-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-copper-sb.yaml b/templates/release/en/charger/wallbox-copper-sb.yaml index 86add4d82e..c4ba8b3b7c 100644 --- a/templates/release/en/charger/wallbox-copper-sb.yaml +++ b/templates/release/en/charger/wallbox-copper-sb.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml b/templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml index ebcb93e080..007378062a 100644 --- a/templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml +++ b/templates/release/en/charger/wallbox-pulsar-max-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-pulsar-max.yaml b/templates/release/en/charger/wallbox-pulsar-max.yaml index 15ca5c98f4..4b0ad9fb5c 100644 --- a/templates/release/en/charger/wallbox-pulsar-max.yaml +++ b/templates/release/en/charger/wallbox-pulsar-max.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml b/templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml index 00f8478604..73bb44a9e9 100644 --- a/templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml +++ b/templates/release/en/charger/wallbox-pulsar-plus-fw-5-x.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: wallbox-fw5 - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: -Current.Offered,Power.Offered # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: -Current.Offered,Power.Offered # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: -Current.Offered,Power.Offered choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/wallbox-pulsar-plus.yaml b/templates/release/en/charger/wallbox-pulsar-plus.yaml index cf8d4ec7b8..17ccbfafab 100644 --- a/templates/release/en/charger/wallbox-pulsar-plus.yaml +++ b/templates/release/en/charger/wallbox-pulsar-plus.yaml @@ -17,17 +17,17 @@ render: - default: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-wallbox - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -35,7 +35,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -52,8 +52,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -61,8 +61,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -70,8 +70,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -79,8 +79,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -88,7 +88,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/walther-werke-basic-evo-pro.yaml b/templates/release/en/charger/walther-werke-basic-evo-pro.yaml index 8ffbf630b9..32d5c08608 100644 --- a/templates/release/en/charger/walther-werke-basic-evo-pro.yaml +++ b/templates/release/en/charger/walther-werke-basic-evo-pro.yaml @@ -30,7 +30,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/webasto-live.yaml b/templates/release/en/charger/webasto-live.yaml index e52353bc38..356d293af3 100644 --- a/templates/release/en/charger/webasto-live.yaml +++ b/templates/release/en/charger/webasto-live.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/webasto-unite.yaml b/templates/release/en/charger/webasto-unite.yaml index 7814e557be..9ae5423105 100644 --- a/templates/release/en/charger/webasto-unite.yaml +++ b/templates/release/en/charger/webasto-unite.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/charger/wolf-bwl.yaml b/templates/release/en/charger/wolf-bwl.yaml index e83fb23818..1896377474 100644 --- a/templates/release/en/charger/wolf-bwl.yaml +++ b/templates/release/en/charger/wolf-bwl.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/wolf-bws.yaml b/templates/release/en/charger/wolf-bws.yaml index 221c1a7d08..916d60e9fb 100644 --- a/templates/release/en/charger/wolf-bws.yaml +++ b/templates/release/en/charger/wolf-bws.yaml @@ -16,7 +16,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional advanced: | type: template template: luxtronik @@ -26,15 +26,15 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - heatoffset: 0.0 # Temperature boost offset for heating. (optional) - wwoffset: 0.0 # Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) + heatoffset: 0.0 # Heating temperature boost (K), optional + wwoffset: 0.0 # Hot water temperature boost (K), Temperature boost offset for hot water. Possibly increases wear on compressor. (optional) params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -43,8 +43,8 @@ params: default: '0.0' choice: [] unit: K - description: - help: Temperature boost offset for heating. + description: Heating temperature boost + help: advanced: false optional: true - name: wwoffset @@ -52,7 +52,7 @@ params: default: '0.0' choice: [] unit: K - description: + description: Hot water temperature boost help: Temperature boost offset for hot water. Possibly increases wear on compressor. advanced: true optional: true diff --git a/templates/release/en/charger/zaptec-go-2.yaml b/templates/release/en/charger/zaptec-go-2.yaml index 850df29718..0e941c48c9 100644 --- a/templates/release/en/charger/zaptec-go-2.yaml +++ b/templates/release/en/charger/zaptec-go-2.yaml @@ -9,7 +9,7 @@ render: - default: | type: template template: zaptec - id: # Charger ID (optional) + id: # ID, Charger ID (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) params: @@ -18,7 +18,7 @@ params: default: choice: [] unit: - description: + description: ID help: Charger ID advanced: false optional: true diff --git a/templates/release/en/charger/zaptec-go-ocpp.yaml b/templates/release/en/charger/zaptec-go-ocpp.yaml index ca2c300b30..0d5cc72ae0 100644 --- a/templates/release/en/charger/zaptec-go-ocpp.yaml +++ b/templates/release/en/charger/zaptec-go-ocpp.yaml @@ -14,17 +14,17 @@ render: - default: | type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-zaptec - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -32,7 +32,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -49,8 +49,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -58,8 +58,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -67,8 +67,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -76,8 +76,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/zaptec-go.yaml b/templates/release/en/charger/zaptec-go.yaml index e5681a3d88..b123aba613 100644 --- a/templates/release/en/charger/zaptec-go.yaml +++ b/templates/release/en/charger/zaptec-go.yaml @@ -9,7 +9,7 @@ render: - default: | type: template template: zaptec - id: # Charger ID (optional) + id: # ID, Charger ID (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) params: @@ -18,7 +18,7 @@ params: default: choice: [] unit: - description: + description: ID help: Charger ID advanced: false optional: true diff --git a/templates/release/en/charger/zaptec-pro.yaml b/templates/release/en/charger/zaptec-pro.yaml index c17b01a024..a606a0dbab 100644 --- a/templates/release/en/charger/zaptec-pro.yaml +++ b/templates/release/en/charger/zaptec-pro.yaml @@ -9,7 +9,7 @@ render: - default: | type: template template: zaptec - id: # Charger ID (optional) + id: # ID, Charger ID (optional) user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) params: @@ -18,7 +18,7 @@ params: default: choice: [] unit: - description: + description: ID help: Charger ID advanced: false optional: true diff --git a/templates/release/en/charger/zewotherm-eu-l-series.yaml b/templates/release/en/charger/zewotherm-eu-l-series.yaml index 5d8b273aef..50bff3aa77 100644 --- a/templates/release/en/charger/zewotherm-eu-l-series.yaml +++ b/templates/release/en/charger/zewotherm-eu-l-series.yaml @@ -21,7 +21,7 @@ render: template: lambda-zewotherm host: 192.0.2.2 # IP address or hostname tempsource: # Temperature source, [warmwater_top, warmwater_bottom, buffer_top, buffer_bottom] (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: host example: 192.0.2.2 @@ -46,7 +46,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/charger/zj-beny-bcp-ev-charger.yaml b/templates/release/en/charger/zj-beny-bcp-ev-charger.yaml index d36a5375db..1db243ed12 100644 --- a/templates/release/en/charger/zj-beny-bcp-ev-charger.yaml +++ b/templates/release/en/charger/zj-beny-bcp-ev-charger.yaml @@ -9,17 +9,17 @@ render: - default: | type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) advanced: | type: template template: ocpp-beny - stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally. (optional) + stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally. (optional) connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional) - remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional) - idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional) - connecttimeout: 5m # Timeout for the registration of the charging point, optional - meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional - metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional + remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional) + idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional) + connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional) + meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional) + metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional) params: - name: stationid example: EVB-P12354 @@ -27,7 +27,7 @@ params: choice: [] unit: description: Station ID - help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://:8887/. Most charging stations automatically add the ID internally.' + help: 'Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form `ws://:8887/`. Most charging stations automatically add the ID internally.' advanced: false optional: true - name: connector @@ -44,8 +44,8 @@ params: default: choice: [] unit: - description: Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected - help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! + description: Start remote transaction on vehicle connection + help: Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: idtag @@ -53,8 +53,8 @@ params: default: choice: [] unit: - description: Identifier used for authentication of external transactions (RemoteStartTransaction) - help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. + description: Authentication token + help: This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) advanced: true optional: true - name: connecttimeout @@ -62,8 +62,8 @@ params: default: 5m choice: [] unit: - description: Timeout for the registration of the charging point - help: + description: Timeout for registration + help: Timeout for the registration of the charging point advanced: true optional: true - name: meterinterval @@ -71,8 +71,8 @@ params: default: 10s choice: [] unit: - description: Transmission interval of meter values (MeterValueSampleInterval) - help: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) advanced: true optional: true - name: metervalues @@ -80,7 +80,7 @@ params: default: choice: [] unit: - description: Manual specification of the meter values to be configured (MeterValuesSampledData) - help: + description: Meter values for transmission + help: Manual specification of the meter values to be configured (MeterValuesSampledData) advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/meter/a-tronix.yaml b/templates/release/en/meter/a-tronix.yaml index 1e00b96fce..b312970ffd 100644 --- a/templates/release/en/meter/a-tronix.yaml +++ b/templates/release/en/meter/a-tronix.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional + delay: 100ms # Delay, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Delay help: advanced: true optional: true diff --git a/templates/release/en/meter/abb-a43.yaml b/templates/release/en/meter/abb-a43.yaml index b8f9cde212..b5dbd4a4e3 100644 --- a/templates/release/en/meter/abb-a43.yaml +++ b/templates/release/en/meter/abb-a43.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/abb-a44.yaml b/templates/release/en/meter/abb-a44.yaml index 73a54d0f01..6e9fc7102e 100644 --- a/templates/release/en/meter/abb-a44.yaml +++ b/templates/release/en/meter/abb-a44.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/abb-b23.yaml b/templates/release/en/meter/abb-b23.yaml index 064db6b31f..dd8613f6dd 100644 --- a/templates/release/en/meter/abb-b23.yaml +++ b/templates/release/en/meter/abb-b23.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/abb-b24.yaml b/templates/release/en/meter/abb-b24.yaml index b82fd16671..9bd16074e8 100644 --- a/templates/release/en/meter/abb-b24.yaml +++ b/templates/release/en/meter/abb-b24.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/acrel-adw300.yaml b/templates/release/en/meter/acrel-adw300.yaml index ed0f7ea506..9f3078c41c 100644 --- a/templates/release/en/meter/acrel-adw300.yaml +++ b/templates/release/en/meter/acrel-adw300.yaml @@ -82,7 +82,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/ads-tec-storaxe.yaml b/templates/release/en/meter/ads-tec-storaxe.yaml index f7afea8d69..0654e8308a 100644 --- a/templates/release/en/meter/ads-tec-storaxe.yaml +++ b/templates/release/en/meter/ads-tec-storaxe.yaml @@ -32,7 +32,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/alpha-ess-storion-smile.yaml b/templates/release/en/meter/alpha-ess-storion-smile.yaml index f474beffca..be2082a371 100644 --- a/templates/release/en/meter/alpha-ess-storion-smile.yaml +++ b/templates/release/en/meter/alpha-ess-storion-smile.yaml @@ -55,8 +55,6 @@ render: id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: pv default: | type: template @@ -104,8 +102,6 @@ render: id: 85 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -163,7 +159,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/ampere-ampere-storagepro.yaml b/templates/release/en/meter/ampere-ampere-storagepro.yaml index 94721883fe..48fd91e340 100644 --- a/templates/release/en/meter/ampere-ampere-storagepro.yaml +++ b/templates/release/en/meter/ampere-ampere-storagepro.yaml @@ -51,8 +51,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: pv default: | type: template @@ -100,8 +98,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: battery default: | type: template @@ -159,7 +155,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/anker-micro-inverter.yaml b/templates/release/en/meter/anker-micro-inverter.yaml index c2b07840a3..5cd504828d 100644 --- a/templates/release/en/meter/anker-micro-inverter.yaml +++ b/templates/release/en/meter/anker-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: true optional: true diff --git a/templates/release/en/meter/axitec-axihycon-12-15h.yaml b/templates/release/en/meter/axitec-axihycon-12-15h.yaml index 86ff1a7b81..7dcb482c60 100644 --- a/templates/release/en/meter/axitec-axihycon-12-15h.yaml +++ b/templates/release/en/meter/axitec-axihycon-12-15h.yaml @@ -117,7 +117,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/bernecker-engineering-mpm3pm.yaml b/templates/release/en/meter/bernecker-engineering-mpm3pm.yaml index 7d3910399f..3a4f510e3d 100644 --- a/templates/release/en/meter/bernecker-engineering-mpm3pm.yaml +++ b/templates/release/en/meter/bernecker-engineering-mpm3pm.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/bgetech-ds100.yaml b/templates/release/en/meter/bgetech-ds100.yaml index c4718cb5cc..340b9051e8 100644 --- a/templates/release/en/meter/bgetech-ds100.yaml +++ b/templates/release/en/meter/bgetech-ds100.yaml @@ -106,7 +106,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/bgetech-ws100.yaml b/templates/release/en/meter/bgetech-ws100.yaml index b1f7bbd153..c1dfd9ed86 100644 --- a/templates/release/en/meter/bgetech-ws100.yaml +++ b/templates/release/en/meter/bgetech-ws100.yaml @@ -106,7 +106,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/bosswerk-micro-inverter.yaml b/templates/release/en/meter/bosswerk-micro-inverter.yaml index 0434da45af..70a3679c18 100644 --- a/templates/release/en/meter/bosswerk-micro-inverter.yaml +++ b/templates/release/en/meter/bosswerk-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: true optional: true diff --git a/templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml b/templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml index b75d465d27..be034a3b4c 100644 --- a/templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml +++ b/templates/release/en/meter/carlo-gavazzi-em110-111-112.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/carlo-gavazzi-em24.yaml b/templates/release/en/meter/carlo-gavazzi-em24.yaml index 4d1ac3ffcb..0656c42993 100644 --- a/templates/release/en/meter/carlo-gavazzi-em24.yaml +++ b/templates/release/en/meter/carlo-gavazzi-em24.yaml @@ -49,7 +49,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/carlo-gavazzi-em24_e1.yaml b/templates/release/en/meter/carlo-gavazzi-em24_e1.yaml index 8dae3ab2d9..45b3fd48e3 100644 --- a/templates/release/en/meter/carlo-gavazzi-em24_e1.yaml +++ b/templates/release/en/meter/carlo-gavazzi-em24_e1.yaml @@ -36,7 +36,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/carlo-gavazzi-em330-em340.yaml b/templates/release/en/meter/carlo-gavazzi-em330-em340.yaml index 71771d9771..8006af0dd3 100644 --- a/templates/release/en/meter/carlo-gavazzi-em330-em340.yaml +++ b/templates/release/en/meter/carlo-gavazzi-em330-em340.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/carlo-gavazzi-em530-em540.yaml b/templates/release/en/meter/carlo-gavazzi-em530-em540.yaml index d0f5a82c17..146c7f9506 100644 --- a/templates/release/en/meter/carlo-gavazzi-em530-em540.yaml +++ b/templates/release/en/meter/carlo-gavazzi-em530-em540.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/carlo-gavazzi-et112.yaml b/templates/release/en/meter/carlo-gavazzi-et112.yaml index 16680813b5..7828a40721 100644 --- a/templates/release/en/meter/carlo-gavazzi-et112.yaml +++ b/templates/release/en/meter/carlo-gavazzi-et112.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/carlo-gavazzi-et330-et340.yaml b/templates/release/en/meter/carlo-gavazzi-et330-et340.yaml index da396ac6cc..57a0294ef9 100644 --- a/templates/release/en/meter/carlo-gavazzi-et330-et340.yaml +++ b/templates/release/en/meter/carlo-gavazzi-et330-et340.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/cfos-powerbrain-meter.yaml b/templates/release/en/meter/cfos-powerbrain-meter.yaml index 3eb38abc45..cc9894df2e 100644 --- a/templates/release/en/meter/cfos-powerbrain-meter.yaml +++ b/templates/release/en/meter/cfos-powerbrain-meter.yaml @@ -22,7 +22,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/deye-3p-hybrid-inverter.yaml b/templates/release/en/meter/deye-3p-hybrid-inverter.yaml index 2bd7dc2adc..fb0feffdfc 100644 --- a/templates/release/en/meter/deye-3p-hybrid-inverter.yaml +++ b/templates/release/en/meter/deye-3p-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml b/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml index 921e126e6f..9d7e020046 100644 --- a/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml +++ b/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml @@ -52,9 +52,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional includegenport: # Treat GEN port as solar input, optional - usage: pv default: | @@ -103,9 +101,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional includegenport: # Treat GEN port as solar input, optional - usage: battery @@ -155,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -166,7 +162,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -175,7 +171,7 @@ params: default: 1 choice: [] unit: - description: + description: Battery storage unit index help: advanced: true optional: true diff --git a/templates/release/en/meter/deye-micro-inverter.yaml b/templates/release/en/meter/deye-micro-inverter.yaml index b8ec8bd1dc..ca9436d71c 100644 --- a/templates/release/en/meter/deye-micro-inverter.yaml +++ b/templates/release/en/meter/deye-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: true optional: true diff --git a/templates/release/en/meter/deye-storage-hybrid-inverter.yaml b/templates/release/en/meter/deye-storage-hybrid-inverter.yaml index 0d650decbf..746820ee6e 100644 --- a/templates/release/en/meter/deye-storage-hybrid-inverter.yaml +++ b/templates/release/en/meter/deye-storage-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/deye-string-inverter.yaml b/templates/release/en/meter/deye-string-inverter.yaml index 5c65be54c8..59b67a8436 100644 --- a/templates/release/en/meter/deye-string-inverter.yaml +++ b/templates/release/en/meter/deye-string-inverter.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/discovergy.yaml b/templates/release/en/meter/discovergy.yaml index 517fc0be1b..b9d80d1d6b 100644 --- a/templates/release/en/meter/discovergy.yaml +++ b/templates/release/en/meter/discovergy.yaml @@ -10,7 +10,7 @@ render: usage: grid user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886 + meter: 1ESY1161229886 # Meter ID - usage: pv default: | type: template @@ -18,7 +18,7 @@ render: usage: pv user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - meter: 1ESY1161229886 + meter: 1ESY1161229886 # Meter ID params: - name: user example: @@ -43,7 +43,7 @@ params: default: choice: [] unit: - description: + description: Meter ID help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/meter/dzg-dvh4013.yaml b/templates/release/en/meter/dzg-dvh4013.yaml index 8a56066ec7..a0e6464cfa 100644 --- a/templates/release/en/meter/dzg-dvh4013.yaml +++ b/templates/release/en/meter/dzg-dvh4013.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/e3-dc.yaml b/templates/release/en/meter/e3-dc.yaml index 2fa2918a06..5965cb45c7 100644 --- a/templates/release/en/meter/e3-dc.yaml +++ b/templates/release/en/meter/e3-dc.yaml @@ -18,7 +18,7 @@ render: port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password advanced: | type: template template: e3dc-rscp @@ -27,7 +27,7 @@ render: port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) - usage: pv default: | @@ -38,7 +38,7 @@ render: port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password advanced: | type: template template: e3dc-rscp @@ -47,7 +47,7 @@ render: port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery @@ -59,7 +59,7 @@ render: port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password advanced: | type: template template: e3dc-rscp @@ -68,7 +68,7 @@ render: port: 5033 # Port, optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - key: + key: # RSCP-Password dischargelimit: # Discharge limit in W, Limits discharge power in 'Hold' battery mode (optional) capacity: 50 # Battery capacity (kWh), optional params: @@ -113,7 +113,7 @@ params: default: choice: [] unit: - description: + description: RSCP-Password help: advanced: false optional: false diff --git a/templates/release/en/meter/eastron-sdm120-modbus.yaml b/templates/release/en/meter/eastron-sdm120-modbus.yaml index 73b2709021..37a9ba7324 100644 --- a/templates/release/en/meter/eastron-sdm120-modbus.yaml +++ b/templates/release/en/meter/eastron-sdm120-modbus.yaml @@ -64,7 +64,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/eastron-sdm220-230.yaml b/templates/release/en/meter/eastron-sdm220-230.yaml index c6cf09acf7..cff5f62d92 100644 --- a/templates/release/en/meter/eastron-sdm220-230.yaml +++ b/templates/release/en/meter/eastron-sdm220-230.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/eastron-sdm630-modbus.yaml b/templates/release/en/meter/eastron-sdm630-modbus.yaml index bb5ee3cccb..a5d9c36792 100644 --- a/templates/release/en/meter/eastron-sdm630-modbus.yaml +++ b/templates/release/en/meter/eastron-sdm630-modbus.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/eastron-sdm72d-m.yaml b/templates/release/en/meter/eastron-sdm72d-m.yaml index 9ebaf66503..dc8385803b 100644 --- a/templates/release/en/meter/eastron-sdm72d-m.yaml +++ b/templates/release/en/meter/eastron-sdm72d-m.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/eastron-sdm72dm-v2.yaml b/templates/release/en/meter/eastron-sdm72dm-v2.yaml index 552313a71d..7470ba821b 100644 --- a/templates/release/en/meter/eastron-sdm72dm-v2.yaml +++ b/templates/release/en/meter/eastron-sdm72dm-v2.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/enphase-iq-envoy.yaml b/templates/release/en/meter/enphase-iq-envoy.yaml index 49ffc4000a..6bf24e2e02 100644 --- a/templates/release/en/meter/enphase-iq-envoy.yaml +++ b/templates/release/en/meter/enphase-iq-envoy.yaml @@ -12,13 +12,13 @@ render: template: enphase usage: grid host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) advanced: | type: template template: enphase usage: grid host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - usage: pv default: | @@ -26,13 +26,13 @@ render: template: enphase usage: pv host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) advanced: | type: template template: enphase usage: pv host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - usage: battery default: | @@ -40,13 +40,13 @@ render: template: enphase usage: battery host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) advanced: | type: template template: enphase usage: battery host: 192.0.2.2 # IP address or hostname - token: # Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) + token: # Token, Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (optional) capacity: 50 # Battery capacity (kWh), optional cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) params: @@ -64,7 +64,7 @@ params: default: choice: [] unit: - description: + description: Token help: 'Required if Envoy Firmware D7.x.xxx. Token is valid for one year. Instructions for obtaining a token via web UI: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication' advanced: false optional: true diff --git a/templates/release/en/meter/fenecon.yaml b/templates/release/en/meter/fenecon.yaml index f3b1a45f63..c2061fc6b8 100644 --- a/templates/release/en/meter/fenecon.yaml +++ b/templates/release/en/meter/fenecon.yaml @@ -44,8 +44,8 @@ render: usage: battery host: 192.0.2.2 # IP address or hostname password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) + battery: ess0 # Controllable battery component, optional + watchdog: 60s # Watchdog, adjusted to the API timeout (optional) capacity: 50 # Battery capacity (kWh), optional params: - name: host @@ -71,8 +71,8 @@ params: default: choice: [] unit: - description: - help: controllable battery component + description: Controllable battery component + help: advanced: true optional: true - name: watchdog @@ -80,7 +80,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: adjusted to the API timeout advanced: true optional: true diff --git a/templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml b/templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml index d696651368..a9af8da1ac 100644 --- a/templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml +++ b/templates/release/en/meter/foxess-h1-series-hybrid-inverter.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml b/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml index a57f0bb0fa..09c26e8562 100644 --- a/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml +++ b/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml b/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml index a0f8fa93d1..77d10b6694 100644 --- a/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml +++ b/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/fronius-primo-gen24-plus.yaml b/templates/release/en/meter/fronius-primo-gen24-plus.yaml index b37dd4decf..aa72871f9d 100644 --- a/templates/release/en/meter/fronius-primo-gen24-plus.yaml +++ b/templates/release/en/meter/fronius-primo-gen24-plus.yaml @@ -18,7 +18,7 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) + id: 200 # ID, Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) - usage: pv default: | type: template @@ -72,7 +72,7 @@ params: default: 200 choice: [] unit: - description: + description: ID help: Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). advanced: true optional: true diff --git a/templates/release/en/meter/fronius-smartmeter-via-inverter.yaml b/templates/release/en/meter/fronius-smartmeter-via-inverter.yaml index 4c5d51fd7b..10040648e7 100644 --- a/templates/release/en/meter/fronius-smartmeter-via-inverter.yaml +++ b/templates/release/en/meter/fronius-smartmeter-via-inverter.yaml @@ -32,7 +32,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/fronius-solar-api-v1.yaml b/templates/release/en/meter/fronius-solar-api-v1.yaml index 6b9ed47cfa..e696dafc02 100644 --- a/templates/release/en/meter/fronius-solar-api-v1.yaml +++ b/templates/release/en/meter/fronius-solar-api-v1.yaml @@ -27,7 +27,7 @@ render: host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional) + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional) - usage: pv default: | type: template @@ -43,7 +43,7 @@ render: host: 192.0.2.2 # IP address or hostname user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional) + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional) - usage: battery default: | type: template @@ -60,7 +60,7 @@ render: user: customer # Username (for active battery control), e.g. email address, user id, etc. (optional) password: # Password (for active battery control), Use single quotes in case of leading zeros (optional) capacity: 50 # Battery capacity (kWh), optional - batteryconfiguri: /config # Firmware starting with 1.36.5-1 require /api/config., [/config, /api/config] (optional) + batteryconfiguri: /config # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional) params: - name: host example: 192.0.2.2 @@ -103,7 +103,7 @@ params: default: /config choice: ['/config', '/api/config'] unit: - description: Firmware starting with 1.36.5-1 require /api/config. - help: + description: Battery configuration URI + help: Firmware starting with 1.36.5-1 requires /api/config. advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/meter/fronius-symo-gen24-plus.yaml b/templates/release/en/meter/fronius-symo-gen24-plus.yaml index 9a31470159..f64a7c5f63 100644 --- a/templates/release/en/meter/fronius-symo-gen24-plus.yaml +++ b/templates/release/en/meter/fronius-symo-gen24-plus.yaml @@ -18,7 +18,7 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 200 # Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) + id: 200 # ID, Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). (optional) - usage: pv default: | type: template @@ -72,7 +72,7 @@ params: default: 200 choice: [] unit: - description: + description: ID help: Meter address of primary or secondary meters. On the web interface of the inverter, only the address of the first meter (e.g., 200) can be set. Additional meters receive an ascending number (e.g., 201). advanced: true optional: true diff --git a/templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml b/templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml index 5083c97a71..59cc75f109 100644 --- a/templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml +++ b/templates/release/en/meter/ginlong-solis-hybrid-inverter-rhi-series.yaml @@ -117,7 +117,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml b/templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml index 09352aef15..1e986b0a4c 100644 --- a/templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml +++ b/templates/release/en/meter/ginlong-solis-hybrid-inverter-s-series.yaml @@ -117,7 +117,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/ginlong-solis-inverter.yaml b/templates/release/en/meter/ginlong-solis-inverter.yaml index 92f207ca67..40a7fa71d5 100644 --- a/templates/release/en/meter/ginlong-solis-inverter.yaml +++ b/templates/release/en/meter/ginlong-solis-inverter.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml b/templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml index 773793b710..aee67434b9 100644 --- a/templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml +++ b/templates/release/en/meter/goodwe-et-eh-bh-bt-hybrid-inverter.yaml @@ -29,7 +29,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) advanced: | type: template template: goodwe-hybrid @@ -53,7 +53,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) - usage: pv default: | type: template @@ -78,7 +78,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) advanced: | type: template template: goodwe-hybrid @@ -102,7 +102,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -128,7 +128,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) advanced: | type: template template: goodwe-hybrid @@ -152,7 +152,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - battery: 1 # [1, 2] (optional) + battery: 1 # Battery number, [1, 2] (optional) capacity: 50 # Battery capacity (kWh), optional params: - name: modbus @@ -160,7 +160,7 @@ params: default: choice: ['rs485', 'tcpip', 'udp'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -169,7 +169,7 @@ params: default: 1 choice: ['1', '2'] unit: - description: + description: Battery number help: advanced: false optional: true diff --git a/templates/release/en/meter/goodwe-sdt-dt-inverter.yaml b/templates/release/en/meter/goodwe-sdt-dt-inverter.yaml index 9780442ace..560792a7fd 100644 --- a/templates/release/en/meter/goodwe-sdt-dt-inverter.yaml +++ b/templates/release/en/meter/goodwe-sdt-dt-inverter.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/growatt-hybrid-inverter.yaml b/templates/release/en/meter/growatt-hybrid-inverter.yaml index 60bc5252a7..a772ccb289 100644 --- a/templates/release/en/meter/growatt-hybrid-inverter.yaml +++ b/templates/release/en/meter/growatt-hybrid-inverter.yaml @@ -160,7 +160,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml b/templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml index 8ab8d64824..7690e0f7c8 100644 --- a/templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml +++ b/templates/release/en/meter/growatt-tl-x-h-hybrid-inverter.yaml @@ -154,7 +154,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/homematic-ip.yaml b/templates/release/en/meter/homematic-ip.yaml index 9d382eaff5..541899f73e 100644 --- a/templates/release/en/meter/homematic-ip.yaml +++ b/templates/release/en/meter/homematic-ip.yaml @@ -13,7 +13,7 @@ render: device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. advanced: | type: template template: homematic @@ -22,8 +22,8 @@ render: device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional) - usage: pv default: | type: template @@ -33,7 +33,7 @@ render: device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. advanced: | type: template template: homematic @@ -42,8 +42,8 @@ render: device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional) - usage: charge default: | type: template @@ -53,7 +53,7 @@ render: device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. advanced: | type: template template: homematic @@ -62,8 +62,8 @@ render: device: 0001EE89AAD848 # Device address/Serial number, Homematic device id like shown in the CCU web user interface. user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - meterchannel: 6 # Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1), Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. - cache: 1s # XML-RPC api cache duration - Default 1s. (valid units are s,m,h), In case of duty cycle problems try a cache setting of 30s. (optional) + meterchannel: 6 # Meter channel number, Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. + cache: 1s # XML-RPC API cache duration, In case of duty cycle problems try a cache setting of 30s. (optional) params: - name: host example: 192.0.2.2 @@ -102,11 +102,11 @@ params: advanced: false optional: true - name: meterchannel - example: + example: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1 default: 6 choice: [] unit: - description: Meter channel number (HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1) + description: Meter channel number help: Homematic meter channel number like shown after the device id separated with a colon in the CCU web user interface. advanced: false optional: false @@ -115,7 +115,7 @@ params: default: 1s choice: [] unit: - description: XML-RPC api cache duration - Default 1s. (valid units are s,m,h) + description: XML-RPC API cache duration help: In case of duty cycle problems try a cache setting of 30s. advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml b/templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml index 15971602c5..c270bc7f9f 100644 --- a/templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml +++ b/templates/release/en/meter/hoymiles-hm-and-hms-series-via-ahoydtu.yaml @@ -10,7 +10,7 @@ render: template: hoymiles-ahoydtu usage: pv host: 192.0.2.2 # IP address or hostname - id: 0 # Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID], optional + id: 0 # Inverter ID, If multiple exist. The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID] (optional) params: - name: host example: 192.0.2.2 @@ -26,7 +26,7 @@ params: default: 0 choice: [] unit: - description: 'Inverter ID (if multiple exist). The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID]' - help: + description: Inverter ID + help: 'If multiple exist. The numbering starts at 0. See AhoyDTU webinterface -> Inverter #[ID]' advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/huawei-emma.yaml b/templates/release/en/meter/huawei-emma.yaml index d6cd38e178..df2a19126e 100644 --- a/templates/release/en/meter/huawei-emma.yaml +++ b/templates/release/en/meter/huawei-emma.yaml @@ -74,7 +74,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/huawei-smartlogger.yaml b/templates/release/en/meter/huawei-smartlogger.yaml index 4c2ebff76e..8bdab39425 100644 --- a/templates/release/en/meter/huawei-smartlogger.yaml +++ b/templates/release/en/meter/huawei-smartlogger.yaml @@ -28,7 +28,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional - usage: pv default: | type: template @@ -52,7 +52,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -77,7 +77,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional params: - name: modbus @@ -85,7 +85,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -103,7 +103,7 @@ params: default: 1 choice: [] unit: - description: + description: Battery storage unit index help: advanced: true optional: true diff --git a/templates/release/en/meter/huawei-sun2000-sdongle.yaml b/templates/release/en/meter/huawei-sun2000-sdongle.yaml index 2a58eed667..1fcc53cae3 100644 --- a/templates/release/en/meter/huawei-sun2000-sdongle.yaml +++ b/templates/release/en/meter/huawei-sun2000-sdongle.yaml @@ -26,7 +26,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/huawei-sun2000.yaml b/templates/release/en/meter/huawei-sun2000.yaml index d7924aaf23..309a118992 100644 --- a/templates/release/en/meter/huawei-sun2000.yaml +++ b/templates/release/en/meter/huawei-sun2000.yaml @@ -59,7 +59,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional - usage: pv default: | type: template @@ -109,7 +109,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -160,7 +160,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port timeout: 15s # Timeout, optional - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional maxchargepower: 10000 # Maximum charge power (W), For forced charging of the battery. (optional) capacity: 50 # Battery capacity (kWh), optional forceaccharging: false # Inverter cascade, Keep AC charging active to charge the storage from other inverters via AC. Prevents stand-by. (optional) @@ -170,7 +170,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -188,7 +188,7 @@ params: default: 1 choice: [] unit: - description: + description: Battery storage unit index help: advanced: true optional: true diff --git a/templates/release/en/meter/inepro-pro380-mod.yaml b/templates/release/en/meter/inepro-pro380-mod.yaml index 66c63aefae..2e15d54e91 100644 --- a/templates/release/en/meter/inepro-pro380-mod.yaml +++ b/templates/release/en/meter/inepro-pro380-mod.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/janitza-b-series.yaml b/templates/release/en/meter/janitza-b-series.yaml index 471cd33ce3..f7919f6d0a 100644 --- a/templates/release/en/meter/janitza-b-series.yaml +++ b/templates/release/en/meter/janitza-b-series.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/janitza-umg-series.yaml b/templates/release/en/meter/janitza-umg-series.yaml index c6c3c47f25..9f78ac1b42 100644 --- a/templates/release/en/meter/janitza-umg-series.yaml +++ b/templates/release/en/meter/janitza-umg-series.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/keba-kecontact-e10.yaml b/templates/release/en/meter/keba-kecontact-e10.yaml index 432af7879f..b0a9abd82c 100644 --- a/templates/release/en/meter/keba-kecontact-e10.yaml +++ b/templates/release/en/meter/keba-kecontact-e10.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml b/templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml index fdaed4b63f..ace4a95811 100644 --- a/templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml +++ b/templates/release/en/meter/kostal-energy-meter-c-kem-c.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml b/templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml index a4f8d0cb8f..7fc8eb23c9 100644 --- a/templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml +++ b/templates/release/en/meter/kostal-energy-meter-p-kem-p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml b/templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml index 7a44f32845..8892e5da61 100644 --- a/templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml +++ b/templates/release/en/meter/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.yaml @@ -33,7 +33,7 @@ render: port: 1502 # Port endianness: little # Endianness (Little/Big), [little, big] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -58,14 +58,14 @@ render: endianness: little # Endianness (Little/Big), [little, big] (optional) capacity: 50 # Battery capacity (kWh), optional maxchargerate: 100 # Maximum charge power (%), For forced charging of the battery in percent in relation to the maximum charge power of the battery inverter. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -110,7 +110,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/kostal-plenticore-hybrid.yaml b/templates/release/en/meter/kostal-plenticore-hybrid.yaml index 0e3776852c..61eeb04bc0 100644 --- a/templates/release/en/meter/kostal-plenticore-hybrid.yaml +++ b/templates/release/en/meter/kostal-plenticore-hybrid.yaml @@ -32,9 +32,7 @@ render: port: 1502 # Port endianness: little # Endianness (Little/Big), [little, big] (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -60,14 +58,14 @@ render: capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -121,7 +119,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml b/templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml index 8edeae7571..d5de69cf1c 100644 --- a/templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml +++ b/templates/release/en/meter/kostal-smart-energy-meter-via-inverter.yaml @@ -23,7 +23,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/kostal-smart-energy-meter.yaml b/templates/release/en/meter/kostal-smart-energy-meter.yaml index 63cad3375d..fade7a04d3 100644 --- a/templates/release/en/meter/kostal-smart-energy-meter.yaml +++ b/templates/release/en/meter/kostal-smart-energy-meter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/lg-ess-home-15.yaml b/templates/release/en/meter/lg-ess-home-15.yaml index 2be099f596..d1564d9f8b 100644 --- a/templates/release/en/meter/lg-ess-home-15.yaml +++ b/templates/release/en/meter/lg-ess-home-15.yaml @@ -18,9 +18,7 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) - usage: pv default: | type: template @@ -34,9 +32,7 @@ render: usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) - usage: battery default: | type: template @@ -50,7 +46,7 @@ render: usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -78,8 +74,8 @@ params: default: choice: [] unit: - description: - help: Registration id of the LG ESS HOME inverter. + description: Registration ID + help: ID of the LG ESS HOME inverter. advanced: true optional: true - name: capacity diff --git a/templates/release/en/meter/lg-ess-home-8-10.yaml b/templates/release/en/meter/lg-ess-home-8-10.yaml index 77ffb0ea9e..cc436ef859 100644 --- a/templates/release/en/meter/lg-ess-home-8-10.yaml +++ b/templates/release/en/meter/lg-ess-home-8-10.yaml @@ -21,9 +21,7 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) - usage: pv default: | type: template @@ -37,9 +35,7 @@ render: usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) - usage: battery default: | type: template @@ -53,7 +49,7 @@ render: usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, User password, see https://github.com/Morluktom/ioBroker.lg-ess-home/tree/master#getting-the-password. Alteratively, use registration id for admin login. (optional) - registration: DE200... # Registration id of the LG ESS HOME inverter. (optional) + registration: DE200... # Registration ID, ID of the LG ESS HOME inverter. (optional) capacity: 50 # Battery capacity (kWh), optional minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -81,8 +77,8 @@ params: default: choice: [] unit: - description: - help: Registration id of the LG ESS HOME inverter. + description: Registration ID + help: ID of the LG ESS HOME inverter. advanced: true optional: true - name: capacity diff --git a/templates/release/en/meter/m-tec-energy-butler-gen2.yaml b/templates/release/en/meter/m-tec-energy-butler-gen2.yaml index d4e337c9b1..38c2944785 100644 --- a/templates/release/en/meter/m-tec-energy-butler-gen2.yaml +++ b/templates/release/en/meter/m-tec-energy-butler-gen2.yaml @@ -64,7 +64,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/m-tec-energy-butler-gen3.yaml b/templates/release/en/meter/m-tec-energy-butler-gen3.yaml index 0d3280a1ff..ef06f3074f 100644 --- a/templates/release/en/meter/m-tec-energy-butler-gen3.yaml +++ b/templates/release/en/meter/m-tec-energy-butler-gen3.yaml @@ -153,7 +153,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/marstek-venus-battery-storage.yaml b/templates/release/en/meter/marstek-venus-battery-storage.yaml index a15f840331..e15b56d3d6 100644 --- a/templates/release/en/meter/marstek-venus-battery-storage.yaml +++ b/templates/release/en/meter/marstek-venus-battery-storage.yaml @@ -42,17 +42,17 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 5.12 # Battery capacity (kWh), Venus-E 5.12 kWh, Venus-C 2.56 kWh (optional) - minsoc: 11 # Venus can only be discharged down to 11%. (%), Lower limit when discharging the battery in normal operation (optional) + minsoc: 11 # Minimum charge (%), Venus can only be discharged down to 11%. (optional) maxsoc: 100 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - maxchargepower: 2500 # Charge power in watts for Charge mode. 2500W is the maximum for Venus. (W), For forced charging of the battery. (optional) - work_mode_normal: 1 # Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode., optional + maxchargepower: 2500 # Maximum charge power (W), 2500W is the maximum for Venus. (optional) + work_mode_normal: 1 # Work mode for Normal state, 0=manual, 1=anti-feed, 2=trade mode. (optional) params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -66,12 +66,12 @@ params: advanced: false optional: true - name: minsoc - example: 25 + example: 11 default: 11 choice: [] unit: '%' - description: Venus can only be discharged down to 11%. - help: Lower limit when discharging the battery in normal operation + description: Minimum charge + help: Venus can only be discharged down to 11%. advanced: true optional: true - name: maxsoc @@ -88,8 +88,8 @@ params: default: 2500 choice: [] unit: W - description: Charge power in watts for Charge mode. 2500W is the maximum for Venus. - help: For forced charging of the battery. + description: Maximum charge power + help: 2500W is the maximum for Venus. advanced: true optional: true - name: work_mode_normal @@ -97,8 +97,8 @@ params: default: 1 choice: [] unit: - description: Work mode for Normal state. 0 manual, 1 anti-feed, 2 trade mode. - help: + description: Work mode for Normal state + help: 0=manual, 1=anti-feed, 2=trade mode. advanced: true optional: true modbus: diff --git a/templates/release/en/meter/my-pv-wifi-meter.yaml b/templates/release/en/meter/my-pv-wifi-meter.yaml index 01129aa7e8..451b9df71f 100644 --- a/templates/release/en/meter/my-pv-wifi-meter.yaml +++ b/templates/release/en/meter/my-pv-wifi-meter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/openems.yaml b/templates/release/en/meter/openems.yaml index 806081d47f..df96a9b5bb 100644 --- a/templates/release/en/meter/openems.yaml +++ b/templates/release/en/meter/openems.yaml @@ -44,8 +44,8 @@ render: usage: battery host: 192.0.2.2 # IP address or hostname password: user # Password, Use single quotes in case of leading zeros (optional) - battery: ess0 # controllable battery component (optional) - watchdog: 60s # adjusted to the API timeout (optional) + battery: ess0 # Controllable battery component, optional + watchdog: 60s # Watchdog, adjusted to the API timeout (optional) capacity: 50 # Battery capacity (kWh), optional params: - name: host @@ -71,8 +71,8 @@ params: default: choice: [] unit: - description: - help: controllable battery component + description: Controllable battery component + help: advanced: true optional: true - name: watchdog @@ -80,7 +80,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: adjusted to the API timeout advanced: true optional: true diff --git a/templates/release/en/meter/orno-or-we-516.yaml b/templates/release/en/meter/orno-or-we-516.yaml index e5828f01eb..42d28e1c04 100644 --- a/templates/release/en/meter/orno-or-we-516.yaml +++ b/templates/release/en/meter/orno-or-we-516.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/orno-or-we-517.yaml b/templates/release/en/meter/orno-or-we-517.yaml index 84efc46ba1..8a83b9eeba 100644 --- a/templates/release/en/meter/orno-or-we-517.yaml +++ b/templates/release/en/meter/orno-or-we-517.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/plexlog.yaml b/templates/release/en/meter/plexlog.yaml index cf9e287fb5..d1c2ed7813 100644 --- a/templates/release/en/meter/plexlog.yaml +++ b/templates/release/en/meter/plexlog.yaml @@ -76,7 +76,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/powerdog.yaml b/templates/release/en/meter/powerdog.yaml index 5ec0e5a171..6f15839224 100644 --- a/templates/release/en/meter/powerdog.yaml +++ b/templates/release/en/meter/powerdog.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/powerfox-poweropti.yaml b/templates/release/en/meter/powerfox-poweropti.yaml index 0aa760537a..6b5846524d 100644 --- a/templates/release/en/meter/powerfox-poweropti.yaml +++ b/templates/release/en/meter/powerfox-poweropti.yaml @@ -17,7 +17,7 @@ render: usage: grid user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti + id: main # ID, Id in case of multiple PowerOpti - usage: pv default: | type: template @@ -31,7 +31,7 @@ render: usage: pv user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - id: main # Id in case of multiple PowerOpti + id: main # ID, Id in case of multiple PowerOpti params: - name: user example: @@ -56,7 +56,7 @@ params: default: main choice: [] unit: - description: + description: ID help: Id in case of multiple PowerOpti advanced: true optional: false \ No newline at end of file diff --git a/templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml b/templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml index 4a6599a88a..e2a82f24d3 100644 --- a/templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml +++ b/templates/release/en/meter/qcells-q-home-ess-hyb-g3.yaml @@ -29,7 +29,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) advanced: | type: template template: solax @@ -53,8 +53,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional - usage: pv default: | type: template @@ -79,7 +79,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) advanced: | type: template template: solax @@ -103,8 +103,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -130,7 +130,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) advanced: | type: template template: solax @@ -154,8 +154,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) params: @@ -164,7 +164,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -173,8 +173,8 @@ params: default: false choice: [] unit: - description: The inverter has a third PV input (MPPT3) - help: + description: Third PV input + help: The inverter has a third PV input (MPPT3) advanced: false optional: true - name: storageunit @@ -182,7 +182,7 @@ params: default: 1 choice: [] unit: - description: + description: Battery storage unit index help: advanced: true optional: true diff --git a/templates/release/en/meter/rct-power.yaml b/templates/release/en/meter/rct-power.yaml index 422faadc48..3ba9c2ed54 100644 --- a/templates/release/en/meter/rct-power.yaml +++ b/templates/release/en/meter/rct-power.yaml @@ -16,10 +16,7 @@ render: template: rct-power usage: grid host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional) - usage: pv default: | type: template @@ -31,8 +28,6 @@ render: template: rct-power usage: pv host: 192.0.2.2 # IP address or hostname - minsoc: 7 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) externalpower: # External power, Query external power of all devices connected to S0 (optional) - usage: battery @@ -51,7 +46,6 @@ render: maxsoc: 97 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (optional) maxchargepower: # Maximum charge power (W), For forced charging of the battery. (optional) - externalpower: # External power, Query external power of all devices connected to S0 (optional) params: - name: host example: 192.0.2.2 diff --git a/templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml b/templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml index 7a300b29b2..efe18be511 100644 --- a/templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml +++ b/templates/release/en/meter/saia-burgess-controls-sbc-ale3.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml b/templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml index 5d50d6befe..28103513eb 100644 --- a/templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml +++ b/templates/release/en/meter/saia-burgess-controls-sbc-awd3.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml b/templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml index 6366c2c44d..e41247b896 100644 --- a/templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml +++ b/templates/release/en/meter/saj-h1-series-hybrid-solar-inverter.yaml @@ -80,7 +80,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml b/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml index 660d3368d5..668e920a5a 100644 --- a/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml +++ b/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml @@ -51,8 +51,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: pv default: | type: template @@ -100,8 +98,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: battery default: | type: template @@ -159,7 +155,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/saj-r5-series-solar-inverter.yaml b/templates/release/en/meter/saj-r5-series-solar-inverter.yaml index 7ebc2899e9..dcab8d1d6f 100644 --- a/templates/release/en/meter/saj-r5-series-solar-inverter.yaml +++ b/templates/release/en/meter/saj-r5-series-solar-inverter.yaml @@ -28,7 +28,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sax-homespeicher.yaml b/templates/release/en/meter/sax-homespeicher.yaml index b81b514f91..18e0962f05 100644 --- a/templates/release/en/meter/sax-homespeicher.yaml +++ b/templates/release/en/meter/sax-homespeicher.yaml @@ -32,7 +32,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml b/templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml index c57a0d25eb..bf12208f0c 100644 --- a/templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml +++ b/templates/release/en/meter/schneider-electric-iem3xxx-modbus.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/senec-home.yaml b/templates/release/en/meter/senec-home.yaml index 3ba4623572..259ce5a1a3 100644 --- a/templates/release/en/meter/senec-home.yaml +++ b/templates/release/en/meter/senec-home.yaml @@ -11,39 +11,39 @@ render: template: senec-home usage: grid host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) advanced: | type: template template: senec-home usage: grid host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) - usage: pv default: | type: template template: senec-home usage: pv host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) advanced: | type: template template: senec-home usage: pv host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) - usage: battery default: | type: template template: senec-home usage: battery host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) advanced: | type: template template: senec-home usage: battery host: 192.0.2.2 # IP address or hostname - schema: https # [https, http] (optional) + schema: https # Schema, [https, http] (optional) capacity: 50 # Battery capacity (kWh), optional params: - name: host @@ -60,7 +60,7 @@ params: default: https choice: ['https', 'http'] unit: - description: + description: Schema help: advanced: false optional: true diff --git a/templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml b/templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml index f54338773c..e4f7f023e3 100644 --- a/templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml +++ b/templates/release/en/meter/senergy-se-4-5-6ktl-s1-g2-inverter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/shelly-1pm-mini.yaml b/templates/release/en/meter/shelly-1pm-mini.yaml index 23085f2b03..beb9f06a7e 100644 --- a/templates/release/en/meter/shelly-1pm-mini.yaml +++ b/templates/release/en/meter/shelly-1pm-mini.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-1pm.yaml b/templates/release/en/meter/shelly-1pm.yaml index be2bbbcef0..a2e4754732 100644 --- a/templates/release/en/meter/shelly-1pm.yaml +++ b/templates/release/en/meter/shelly-1pm.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-em.yaml b/templates/release/en/meter/shelly-em.yaml index d23ce01b7d..f7cd403f33 100644 --- a/templates/release/en/meter/shelly-em.yaml +++ b/templates/release/en/meter/shelly-em.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-plug-s.yaml b/templates/release/en/meter/shelly-plug-s.yaml index 854e29da5c..68caf993f8 100644 --- a/templates/release/en/meter/shelly-plug-s.yaml +++ b/templates/release/en/meter/shelly-plug-s.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pm-mini.yaml b/templates/release/en/meter/shelly-pm-mini.yaml index 820ffb553a..b407be8094 100644 --- a/templates/release/en/meter/shelly-pm-mini.yaml +++ b/templates/release/en/meter/shelly-pm-mini.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pro-1pm.yaml b/templates/release/en/meter/shelly-pro-1pm.yaml index 94f2bfc9dc..9728b0e1ad 100644 --- a/templates/release/en/meter/shelly-pro-1pm.yaml +++ b/templates/release/en/meter/shelly-pro-1pm.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml b/templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml index 601becd01f..0b1753c2a9 100644 --- a/templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml +++ b/templates/release/en/meter/shelly-pro-3em-monophase-mode.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/shelly-pro-em.yaml b/templates/release/en/meter/shelly-pro-em.yaml index caf1c024b6..d72024581a 100644 --- a/templates/release/en/meter/shelly-pro-em.yaml +++ b/templates/release/en/meter/shelly-pro-em.yaml @@ -13,7 +13,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: pv default: | type: template @@ -22,7 +22,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional - usage: charge default: | type: template @@ -31,7 +31,7 @@ render: host: 192.0.2.2 # IP address or hostname user: # Username, e.g. email address, user id, etc. (optional) password: # Password, Use single quotes in case of leading zeros (optional) - channel: 0 # optional + channel: 0 # Channel, optional params: - name: host example: 192.0.2.2 @@ -65,7 +65,7 @@ params: default: 0 choice: [] unit: - description: + description: Channel help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/siemens-7kt1665.yaml b/templates/release/en/meter/siemens-7kt1665.yaml index f5dbf9221f..16d64b0efc 100644 --- a/templates/release/en/meter/siemens-7kt1665.yaml +++ b/templates/release/en/meter/siemens-7kt1665.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/siemens-junelight-smart-battery.yaml b/templates/release/en/meter/siemens-junelight-smart-battery.yaml index 4e4e61bdee..cf7a56906f 100644 --- a/templates/release/en/meter/siemens-junelight-smart-battery.yaml +++ b/templates/release/en/meter/siemens-junelight-smart-battery.yaml @@ -77,7 +77,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/siemens-pac-2200.yaml b/templates/release/en/meter/siemens-pac-2200.yaml index d508896cb5..973fde2e64 100644 --- a/templates/release/en/meter/siemens-pac-2200.yaml +++ b/templates/release/en/meter/siemens-pac-2200.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml b/templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml index b408d4ecc9..9d7669f6d5 100644 --- a/templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml +++ b/templates/release/en/meter/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.yaml @@ -13,14 +13,14 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional advanced: | type: template template: sigenergy usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional - usage: pv default: | type: template @@ -28,14 +28,14 @@ render: usage: pv host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional advanced: | type: template template: sigenergy usage: pv host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional - usage: battery default: | type: template @@ -43,14 +43,14 @@ render: usage: battery host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional advanced: | type: template template: sigenergy usage: battery host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - id: 1 # optional + id: 1 # ID, optional capacity: 50 # Battery capacity (kWh), optional params: - name: host @@ -76,7 +76,7 @@ params: default: 1 choice: [] unit: - description: + description: ID help: advanced: false optional: true diff --git a/templates/release/en/meter/sma-data-manager.yaml b/templates/release/en/meter/sma-data-manager.yaml index 3e2d66bbb6..24f4f82051 100644 --- a/templates/release/en/meter/sma-data-manager.yaml +++ b/templates/release/en/meter/sma-data-manager.yaml @@ -76,7 +76,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml b/templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml index f7c2040de9..0bbcc86606 100644 --- a/templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml +++ b/templates/release/en/meter/sma-smart-energy-hybrid-inverter.yaml @@ -50,14 +50,14 @@ render: port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: ModbusTCP server needs to be enabled. advanced: false optional: true @@ -93,7 +93,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml b/templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml index 850e600582..3ee2397bc2 100644 --- a/templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml +++ b/templates/release/en/meter/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.yaml @@ -28,14 +28,14 @@ render: port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: ModbusTCP server needs to be enabled. advanced: false optional: true @@ -62,7 +62,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml b/templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml index 8d1d1531f4..19212b2437 100644 --- a/templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml +++ b/templates/release/en/meter/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.yaml @@ -28,14 +28,14 @@ render: port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: ModbusTCP server needs to be enabled. advanced: false optional: true @@ -62,7 +62,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/sma-sunny-island-modbus.yaml b/templates/release/en/meter/sma-sunny-island-modbus.yaml index 59a9def741..6fe923551f 100644 --- a/templates/release/en/meter/sma-sunny-island-modbus.yaml +++ b/templates/release/en/meter/sma-sunny-island-modbus.yaml @@ -28,14 +28,14 @@ render: port: 502 # Port capacity: 50 # Battery capacity (kWh), optional maxchargepower: 4200 # Maximum charge power (W), For forced charging of the battery. (optional) - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: ModbusTCP server needs to be enabled. advanced: false optional: true @@ -62,7 +62,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/sma-webbox.yaml b/templates/release/en/meter/sma-webbox.yaml index 41feca330a..92f9374c18 100644 --- a/templates/release/en/meter/sma-webbox.yaml +++ b/templates/release/en/meter/sma-webbox.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: ModbusTCP server needs to be enabled. advanced: false optional: true diff --git a/templates/release/en/meter/sma-wechselrichter-modbus.yaml b/templates/release/en/meter/sma-wechselrichter-modbus.yaml index 2350570aa1..87f42dcfcf 100644 --- a/templates/release/en/meter/sma-wechselrichter-modbus.yaml +++ b/templates/release/en/meter/sma-wechselrichter-modbus.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: ModbusTCP server needs to be enabled. advanced: false optional: true diff --git a/templates/release/en/meter/sofarsolar-hybrid-inverter.yaml b/templates/release/en/meter/sofarsolar-hybrid-inverter.yaml index b0ba5822ac..257cd03966 100644 --- a/templates/release/en/meter/sofarsolar-hybrid-inverter.yaml +++ b/templates/release/en/meter/sofarsolar-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml b/templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml index af34a7f69a..b94da7c7f5 100644 --- a/templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml +++ b/templates/release/en/meter/sofarsolar-hyd-3-6k-ep.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + description: Battery storage unit index + help: In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). advanced: true optional: true - name: capacity diff --git a/templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml b/templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml index d800827cfb..c84df68d65 100644 --- a/templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml +++ b/templates/release/en/meter/sofarsolar-hyd-5-20k-3ph.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + description: Battery storage unit index + help: In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). advanced: true optional: true - name: capacity diff --git a/templates/release/en/meter/sofarsolar-inverter.yaml b/templates/release/en/meter/sofarsolar-inverter.yaml index bdfba5d50a..24ca745a3b 100644 --- a/templates/release/en/meter/sofarsolar-inverter.yaml +++ b/templates/release/en/meter/sofarsolar-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml b/templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml index 604ab347fc..2b6dcc0155 100644 --- a/templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml +++ b/templates/release/en/meter/sofarsolar-sofar-5-24ktl-g3.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + description: Battery storage unit index + help: In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). advanced: true optional: true - name: capacity diff --git a/templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml b/templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml index 1a1862c701..c0a3e57ec7 100644 --- a/templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml +++ b/templates/release/en/meter/sofarsolar-sofar-80-136ktl.yaml @@ -54,7 +54,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) - usage: pv default: | type: template @@ -102,7 +102,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -151,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 8899 # Port - storageunit: 1 # Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) + storageunit: 1 # Battery storage unit index, In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). (optional) capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Valid values are 0 (self use), 1 (time of use), 2 (timing mode), 4 (peak-shaving mode) (optional) params: @@ -160,7 +160,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -169,8 +169,8 @@ params: default: 1 choice: [] unit: - description: - help: Number of the battery storage. In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). + description: Battery storage unit index + help: In case of a BTS storage not the address of a BTS 5K battery module, but the storage tower (BTS 5K-BDU control unit with 1-4 BTS 5K modules). advanced: true optional: true - name: capacity diff --git a/templates/release/en/meter/solaredge-hybrid-inverter.yaml b/templates/release/en/meter/solaredge-hybrid-inverter.yaml index 47e8484b7f..0f9ba00cda 100644 --- a/templates/release/en/meter/solaredge-hybrid-inverter.yaml +++ b/templates/release/en/meter/solaredge-hybrid-inverter.yaml @@ -58,7 +58,7 @@ render: host: 192.0.2.2 # Hostname port: 1502 # Port timeout: 10s # Timeout, optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: pv default: | type: template @@ -109,7 +109,7 @@ render: port: 1502 # Port timeout: 10s # Timeout, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -160,14 +160,14 @@ render: port: 1502 # Port timeout: 10s # Timeout, optional capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -203,7 +203,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/solaredge-inverter.yaml b/templates/release/en/meter/solaredge-inverter.yaml index 6a3df4d161..92439e1e4f 100644 --- a/templates/release/en/meter/solaredge-inverter.yaml +++ b/templates/release/en/meter/solaredge-inverter.yaml @@ -62,7 +62,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml b/templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml index 357d3ff7f7..846665c62c 100644 --- a/templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml +++ b/templates/release/en/meter/solarmax-max-storage-max-storage-ultimate.yaml @@ -28,7 +28,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: pv default: | type: template @@ -51,7 +51,7 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional - usage: battery default: | type: template @@ -74,14 +74,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - watchdog: 60s # optional + watchdog: 60s # Watchdog, optional params: - name: modbus example: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -108,7 +108,7 @@ params: default: 60s choice: [] unit: - description: + description: Watchdog help: advanced: true optional: true diff --git a/templates/release/en/meter/solarmax-solarmax-smt.yaml b/templates/release/en/meter/solarmax-solarmax-smt.yaml index f28a6b03f5..5c52c0f6b0 100644 --- a/templates/release/en/meter/solarmax-solarmax-smt.yaml +++ b/templates/release/en/meter/solarmax-solarmax-smt.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/solarmax-sp-series-inverter.yaml b/templates/release/en/meter/solarmax-sp-series-inverter.yaml index 430c460089..1a453e4d2b 100644 --- a/templates/release/en/meter/solarmax-sp-series-inverter.yaml +++ b/templates/release/en/meter/solarmax-sp-series-inverter.yaml @@ -21,7 +21,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml b/templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml index e4abf0bc5f..a22cb55fd9 100644 --- a/templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml +++ b/templates/release/en/meter/solax-hybrid-x1-x3-g3-g4.yaml @@ -29,7 +29,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) advanced: | type: template template: solax @@ -53,8 +53,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional - usage: pv default: | type: template @@ -79,7 +79,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) advanced: | type: template template: solax @@ -103,8 +103,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -130,7 +130,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) advanced: | type: template template: solax @@ -154,8 +154,8 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - mppt3: false # The inverter has a third PV input (MPPT3), optional - storageunit: 1 # optional + mppt3: false # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional defaultmode: 0 # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. (optional) params: @@ -164,7 +164,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -173,8 +173,8 @@ params: default: false choice: [] unit: - description: The inverter has a third PV input (MPPT3) - help: + description: Third PV input + help: The inverter has a third PV input (MPPT3) advanced: false optional: true - name: storageunit @@ -182,7 +182,7 @@ params: default: 1 choice: [] unit: - description: + description: Battery storage unit index help: advanced: true optional: true diff --git a/templates/release/en/meter/solinteng.yaml b/templates/release/en/meter/solinteng.yaml index 9aca1cfd8e..48eb6ffa69 100644 --- a/templates/release/en/meter/solinteng.yaml +++ b/templates/release/en/meter/solinteng.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional + delay: 100ms # Delay, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Delay help: advanced: true optional: true diff --git a/templates/release/en/meter/sonnen-sonnenbatterie.yaml b/templates/release/en/meter/sonnen-sonnenbatterie.yaml index e12e323998..306952ced9 100644 --- a/templates/release/en/meter/sonnen-sonnenbatterie.yaml +++ b/templates/release/en/meter/sonnen-sonnenbatterie.yaml @@ -43,14 +43,14 @@ render: usage: battery host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional) + token: # Token, API Token (required for active battery control) (optional) advanced: | type: template template: sonnenbatterie usage: battery host: 192.0.2.2 # IP address or hostname port: 8080 # Port, optional - token: # API Token (required for active battery control) (optional) + token: # Token, API Token (required for active battery control) (optional) capacity: 50 # Battery capacity (kWh), optional maxchargepower: 3300 # Maximum charge power (W), For forced charging of the battery. (optional) defaultmode: self-consumption # Default mode for battery control, Inverter falls back to this mode after charging the battery or after stopping discharge. [self-consumption, time-of-use] @@ -78,7 +78,7 @@ params: default: choice: [] unit: - description: + description: Token help: API Token (required for active battery control) advanced: false optional: true diff --git a/templates/release/en/meter/st-ems.yaml b/templates/release/en/meter/st-ems.yaml index 9bb492504b..db0124d33d 100644 --- a/templates/release/en/meter/st-ems.yaml +++ b/templates/release/en/meter/st-ems.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional + delay: 100ms # Delay, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Delay help: advanced: true optional: true diff --git a/templates/release/en/meter/sungrow-sg-series-inverter.yaml b/templates/release/en/meter/sungrow-sg-series-inverter.yaml index 5616956caf..46978a33c8 100644 --- a/templates/release/en/meter/sungrow-sg-series-inverter.yaml +++ b/templates/release/en/meter/sungrow-sg-series-inverter.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml b/templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml index 2cd4be840b..3a912101cf 100644 --- a/templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml +++ b/templates/release/en/meter/sungrow-sh-series-hybrid-inverter.yaml @@ -163,7 +163,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunspec-battery-model-124.yaml b/templates/release/en/meter/sunspec-battery-model-124.yaml index cbfedd7b32..41096da822 100644 --- a/templates/release/en/meter/sunspec-battery-model-124.yaml +++ b/templates/release/en/meter/sunspec-battery-model-124.yaml @@ -60,7 +60,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunspec-battery-model-802.yaml b/templates/release/en/meter/sunspec-battery-model-802.yaml index f45126a893..2560e56f83 100644 --- a/templates/release/en/meter/sunspec-battery-model-802.yaml +++ b/templates/release/en/meter/sunspec-battery-model-802.yaml @@ -61,7 +61,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunspec-hybrid-inverter.yaml b/templates/release/en/meter/sunspec-hybrid-inverter.yaml index 99374f041d..66f317f8eb 100644 --- a/templates/release/en/meter/sunspec-hybrid-inverter.yaml +++ b/templates/release/en/meter/sunspec-hybrid-inverter.yaml @@ -153,7 +153,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunspec-inverter.yaml b/templates/release/en/meter/sunspec-inverter.yaml index b75479d342..10dcd6357e 100644 --- a/templates/release/en/meter/sunspec-inverter.yaml +++ b/templates/release/en/meter/sunspec-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['tcpip', 'rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunspec-meter.yaml b/templates/release/en/meter/sunspec-meter.yaml index 7e626429cd..0794d3db43 100644 --- a/templates/release/en/meter/sunspec-meter.yaml +++ b/templates/release/en/meter/sunspec-meter.yaml @@ -31,7 +31,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml b/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml index ab07bd15e0..1c1ef18098 100644 --- a/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml +++ b/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml @@ -52,8 +52,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: pv default: | type: template @@ -101,8 +99,6 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - usage: battery default: | @@ -160,7 +156,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml b/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml index 5c15e7c1ff..7ca495d16f 100644 --- a/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml +++ b/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml @@ -52,9 +52,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional includegenport: # Treat GEN port as solar input, optional - usage: pv default: | @@ -103,9 +101,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional - minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + storageunit: 1 # Battery storage unit index, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional includegenport: # Treat GEN port as solar input, optional - usage: battery @@ -155,7 +151,7 @@ render: id: 1 host: 192.0.2.2 # Hostname port: 502 # Port - storageunit: 1 # optional + storageunit: 1 # Battery storage unit index, optional capacity: 50 # Battery capacity (kWh), optional minsoc: 20 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) @@ -166,7 +162,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -175,7 +171,7 @@ params: default: 1 choice: [] unit: - description: + description: Battery storage unit index help: advanced: true optional: true diff --git a/templates/release/en/meter/sunsynk-micro-inverter.yaml b/templates/release/en/meter/sunsynk-micro-inverter.yaml index 69b8cde633..05c3bd6fd2 100644 --- a/templates/release/en/meter/sunsynk-micro-inverter.yaml +++ b/templates/release/en/meter/sunsynk-micro-inverter.yaml @@ -57,7 +57,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: true optional: true diff --git a/templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml b/templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml index 77cc7a0a8a..4ac1e2a40b 100644 --- a/templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml +++ b/templates/release/en/meter/sunsynk-storage-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunsynk-string-inverter.yaml b/templates/release/en/meter/sunsynk-string-inverter.yaml index ed15c76121..7ab4c4858f 100644 --- a/templates/release/en/meter/sunsynk-string-inverter.yaml +++ b/templates/release/en/meter/sunsynk-string-inverter.yaml @@ -34,7 +34,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/sunway.yaml b/templates/release/en/meter/sunway.yaml index be374737ea..fa3de4ae9f 100644 --- a/templates/release/en/meter/sunway.yaml +++ b/templates/release/en/meter/sunway.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional + delay: 100ms # Delay, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Delay help: advanced: true optional: true diff --git a/templates/release/en/meter/tesla-powerwall.yaml b/templates/release/en/meter/tesla-powerwall.yaml index 9d19d7b9b4..469a327ddd 100644 --- a/templates/release/en/meter/tesla-powerwall.yaml +++ b/templates/release/en/meter/tesla-powerwall.yaml @@ -20,18 +20,16 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) advanced: | type: template template: tesla-powerwall usage: grid host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) - usage: pv default: | type: template @@ -39,18 +37,16 @@ render: usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) advanced: | type: template template: tesla-powerwall usage: pv host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) - usage: battery default: | type: template @@ -58,16 +54,16 @@ render: usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) advanced: | type: template template: tesla-powerwall usage: battery host: 192.0.2.2 # IP address or hostname password: # Password, Password of the user "customer". By default this is the last 5 characters of password stated on the Tesla Gateway. - refreshToken: # optional - siteId: # optional product identifier of the energy site, use to override autodectction (optional) + refreshToken: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (optional) minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) params: @@ -94,7 +90,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: true @@ -103,7 +99,7 @@ params: default: choice: [] unit: - description: + description: Site ID help: optional product identifier of the energy site, use to override autodectction advanced: false optional: true diff --git a/templates/release/en/meter/tibber-pulse.yaml b/templates/release/en/meter/tibber-pulse.yaml index a81ed20044..ef324fdd33 100644 --- a/templates/release/en/meter/tibber-pulse.yaml +++ b/templates/release/en/meter/tibber-pulse.yaml @@ -10,15 +10,15 @@ render: type: template template: tibber-pulse usage: grid - token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE - homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # optional + token: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional params: - name: token example: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: Home ID help: advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/meter/victron-em24.yaml b/templates/release/en/meter/victron-em24.yaml index 7bc995f01d..53e03f6e53 100644 --- a/templates/release/en/meter/victron-em24.yaml +++ b/templates/release/en/meter/victron-em24.yaml @@ -49,7 +49,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/victron-em24_e1.yaml b/templates/release/en/meter/victron-em24_e1.yaml index ce3ea0b240..54fe30cefa 100644 --- a/templates/release/en/meter/victron-em24_e1.yaml +++ b/templates/release/en/meter/victron-em24_e1.yaml @@ -36,7 +36,7 @@ params: default: choice: ['tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/victron-em530-em540.yaml b/templates/release/en/meter/victron-em530-em540.yaml index 57fc28e720..c7202109bd 100644 --- a/templates/release/en/meter/victron-em530-em540.yaml +++ b/templates/release/en/meter/victron-em530-em540.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/victron-energy.yaml b/templates/release/en/meter/victron-energy.yaml index 8008ced095..27dc15404a 100644 --- a/templates/release/en/meter/victron-energy.yaml +++ b/templates/release/en/meter/victron-energy.yaml @@ -14,16 +14,14 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) + meterid: # Grid meter VRM instance, Can be read out in VRM portal or via remoteUI. (optional) advanced: | type: template template: victron-energy usage: grid host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional - meterid: # Grid meter VRM instance- can be read out in VRM portal or via remoteUI. (optional) - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) + meterid: # Grid meter VRM instance, Can be read out in VRM portal or via remoteUI. (optional) - usage: pv default: | type: template @@ -38,8 +36,6 @@ render: host: 192.0.2.2 # IP address or hostname port: 502 # Port, optional maxacpower: 0 # Maximum AC power of the hybrid inverter (W), optional - minsoc: 25 # Minimum charge (%), Lower limit when discharging the battery in normal operation (optional) - maxsoc: 95 # Maximum charge (%), Upper limit when charging the battery from the grid (optional) - usage: battery default: | type: template @@ -80,8 +76,8 @@ params: default: choice: [] unit: - description: - help: Grid meter VRM instance- can be read out in VRM portal or via remoteUI. + description: Grid meter VRM instance + help: Can be read out in VRM portal or via remoteUI. advanced: false optional: true - name: capacity diff --git a/templates/release/en/meter/victron-et340.yaml b/templates/release/en/meter/victron-et340.yaml index 0f3d3b8836..775147ce40 100644 --- a/templates/release/en/meter/victron-et340.yaml +++ b/templates/release/en/meter/victron-et340.yaml @@ -58,7 +58,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/volkszahler-http-api-import-and-export.yaml b/templates/release/en/meter/volkszahler-http-api-import-and-export.yaml index a479cab3c2..442889e920 100644 --- a/templates/release/en/meter/volkszahler-http-api-import-and-export.yaml +++ b/templates/release/en/meter/volkszahler-http-api-import-and-export.yaml @@ -10,17 +10,17 @@ render: type: template template: volkszaehler-importexport usage: grid - url: # URL of the middleware's "data" context, The URL is for example: http://zaehler.network.local:8080/api/data (optional) - importuuid: - exportuuid: + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID params: - name: url - example: + example: http://zaehler.network.local:8080/api/data default: choice: [] unit: - description: URL of the middleware's "data" context - help: 'The URL is for example: http://zaehler.network.local:8080/api/data' + description: Middleware URL + help: advanced: false optional: true - name: importuuid @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Import UUID help: advanced: false optional: false @@ -37,7 +37,7 @@ params: default: choice: [] unit: - description: + description: Export UUID help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/meter/volkszahler-http-api.yaml b/templates/release/en/meter/volkszahler-http-api.yaml index 99c37ef933..b477cc1a5c 100644 --- a/templates/release/en/meter/volkszahler-http-api.yaml +++ b/templates/release/en/meter/volkszahler-http-api.yaml @@ -10,16 +10,16 @@ render: type: template template: volkszaehler-http usage: grid - url: # URL of the middleware's "data" context, Example: http://zaehler.network.local:8080/api/data (optional) - uuid: + url: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID params: - name: url - example: + example: http://zaehler.network.local:8080/api/data default: choice: [] unit: - description: URL of the middleware's "data" context - help: 'Example: http://zaehler.network.local:8080/api/data' + description: Middleware URL + help: advanced: false optional: true - name: uuid @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: UUID help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/meter/volkszahler-websocket-api.yaml b/templates/release/en/meter/volkszahler-websocket-api.yaml index 8b7127e2ab..85053d4b0f 100644 --- a/templates/release/en/meter/volkszahler-websocket-api.yaml +++ b/templates/release/en/meter/volkszahler-websocket-api.yaml @@ -13,7 +13,7 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname port: 8082 # Port, optional - uuid: + uuid: # UUID params: - name: host example: 192.0.2.2 @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: UUID help: advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/meter/vzlogger.yaml b/templates/release/en/meter/vzlogger.yaml index f561382def..dcd661affb 100644 --- a/templates/release/en/meter/vzlogger.yaml +++ b/templates/release/en/meter/vzlogger.yaml @@ -11,24 +11,24 @@ render: usage: grid host: 192.0.2.2 # IP address or hostname port: 8081 # Port, optional - uuid: + uuid: # UUID advanced: | type: template template: vzlogger usage: grid host: 192.0.2.2 # IP address or hostname port: 8081 # Port, optional - uuid: + uuid: # UUID scale: 1 # Scale factor, Multiply by this value (optional) - l1currentuuid: # The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0), optional - l2currentuuid: # The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0), optional - l3currentuuid: # The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0), optional - l1poweruuid: # The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0), optional - l2poweruuid: # The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0), optional - l3poweruuid: # The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0), optional - l1voltageuuid: # The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0), optional - l2voltageuuid: # The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0), optional - l3voltageuuid: # The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0), optional + l1currentuuid: # Current on phase 1, The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0) (optional) + l2currentuuid: # Current on phase 2, The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0) (optional) + l3currentuuid: # Current on phase 3, The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0) (optional) + l1poweruuid: # Power on phase 1, The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0) (optional) + l2poweruuid: # Power on phase 2, The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0) (optional) + l3poweruuid: # Power on phase 3, The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0) (optional) + l1voltageuuid: # Voltage on phase 1, The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0) (optional) + l2voltageuuid: # Voltage on phase 2, The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0) (optional) + l3voltageuuid: # Voltage on phase 3, The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0) (optional) cache: 1s # Cache, Time interval with when data should be reloaded from the vehicle (optional) params: - name: host @@ -54,7 +54,7 @@ params: default: choice: [] unit: - description: + description: UUID help: advanced: false optional: false @@ -72,8 +72,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0) - help: + description: Current on phase 1 + help: The vzlogger channel uuid for current on phase 1 (OBIS Code 31.7.0) advanced: true optional: true - name: l2currentuuid @@ -81,8 +81,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0) - help: + description: Current on phase 2 + help: The vzlogger channel uuid for current on phase 2 (OBIS Code 51.7.0) advanced: true optional: true - name: l3currentuuid @@ -90,8 +90,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0) - help: + description: Current on phase 3 + help: The vzlogger channel uuid for current on phase 3 (OBIS Code 71.7.0) advanced: true optional: true - name: l1poweruuid @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0) - help: + description: Power on phase 1 + help: The vzlogger channel uuid for power on phase 1 (OBIS Code 36.7.0) advanced: true optional: true - name: l2poweruuid @@ -108,8 +108,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0) - help: + description: Power on phase 2 + help: The vzlogger channel uuid for power on phase 2 (OBIS Code 56.7.0) advanced: true optional: true - name: l3poweruuid @@ -117,8 +117,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0) - help: + description: Power on phase 3 + help: The vzlogger channel uuid for power on phase 3 (OBIS Code 76.7.0) advanced: true optional: true - name: l1voltageuuid @@ -126,8 +126,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0) - help: + description: Voltage on phase 1 + help: The vzlogger channel uuid for voltage on phase 1 (OBIS Code 32.7.0) advanced: true optional: true - name: l2voltageuuid @@ -135,8 +135,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0) - help: + description: Voltage on phase 2 + help: The vzlogger channel uuid for voltage on phase 2 (OBIS Code 52.7.0) advanced: true optional: true - name: l3voltageuuid @@ -144,8 +144,8 @@ params: default: choice: [] unit: - description: The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0) - help: + description: Voltage on phase 3 + help: The vzlogger channel uuid for voltage on phase 3 (OBIS Code 72.7.0) advanced: true optional: true - name: cache diff --git a/templates/release/en/meter/wago-879-30xx.yaml b/templates/release/en/meter/wago-879-30xx.yaml index 9e3a3ece70..31c6137595 100644 --- a/templates/release/en/meter/wago-879-30xx.yaml +++ b/templates/release/en/meter/wago-879-30xx.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/wattsonic.yaml b/templates/release/en/meter/wattsonic.yaml index 9aae7f95f2..7d4239f1d7 100644 --- a/templates/release/en/meter/wattsonic.yaml +++ b/templates/release/en/meter/wattsonic.yaml @@ -38,7 +38,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: pv default: | type: template @@ -74,7 +74,7 @@ render: id: 247 host: 192.0.2.2 # Hostname port: 502 # Port - delay: 100ms # optional + delay: 100ms # Delay, optional - usage: battery default: | type: template @@ -111,14 +111,14 @@ render: host: 192.0.2.2 # Hostname port: 502 # Port capacity: 50 # Battery capacity (kWh), optional - delay: 100ms # optional + delay: 100ms # Delay, optional params: - name: modbus example: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true @@ -136,7 +136,7 @@ params: default: 100ms choice: [] unit: - description: + description: Delay help: advanced: true optional: true diff --git a/templates/release/en/meter/weidmuller-em110-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em110-rtu-2p.yaml index e5d38d0886..5eccef8015 100644 --- a/templates/release/en/meter/weidmuller-em110-rtu-2p.yaml +++ b/templates/release/en/meter/weidmuller-em110-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/weidmuller-em111-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em111-rtu-2p.yaml index 07c0b80e23..54e881fb95 100644 --- a/templates/release/en/meter/weidmuller-em111-rtu-2p.yaml +++ b/templates/release/en/meter/weidmuller-em111-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/weidmuller-em120-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em120-rtu-2p.yaml index b1cb3fc002..f90c99712b 100644 --- a/templates/release/en/meter/weidmuller-em120-rtu-2p.yaml +++ b/templates/release/en/meter/weidmuller-em120-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/weidmuller-em122-rtu-2p.yaml b/templates/release/en/meter/weidmuller-em122-rtu-2p.yaml index 415863aac2..ad100e329b 100644 --- a/templates/release/en/meter/weidmuller-em122-rtu-2p.yaml +++ b/templates/release/en/meter/weidmuller-em122-rtu-2p.yaml @@ -46,7 +46,7 @@ params: default: choice: ['rs485'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml b/templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml index 8755b73e99..ce0286b0ff 100644 --- a/templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml +++ b/templates/release/en/meter/zcs-azzurro-hybrid-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/zcs-azzurro-inverter.yaml b/templates/release/en/meter/zcs-azzurro-inverter.yaml index c4df9aa401..c382b4a2eb 100644 --- a/templates/release/en/meter/zcs-azzurro-inverter.yaml +++ b/templates/release/en/meter/zcs-azzurro-inverter.yaml @@ -152,7 +152,7 @@ params: default: choice: ['rs485', 'tcpip'] unit: - description: + description: Modbus Type help: advanced: false optional: true diff --git a/templates/release/en/meter/zendure-hyper-2000.yaml b/templates/release/en/meter/zendure-hyper-2000.yaml index c4ac734274..1acf6753d2 100644 --- a/templates/release/en/meter/zendure-hyper-2000.yaml +++ b/templates/release/en/meter/zendure-hyper-2000.yaml @@ -10,34 +10,34 @@ render: type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional advanced: | type: template template: zendure usage: pv - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional - usage: battery default: | type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional advanced: | type: template template: zendure usage: battery - account: dev@zendure.com - serial: VU5D99F74021B04 # You can find this in the Zendure App in the settings of the device - region: EU # [EU, Global] + account: dev@zendure.com # Account ID + serial: VU5D99F74021B04 # Serial, You can find this in the Zendure App in the settings of the device + region: EU # Region, [EU, Global] timeout: 10s # Timeout, optional capacity: 2 # Battery capacity (kWh), optional params: @@ -46,7 +46,7 @@ params: default: choice: [] unit: - description: + description: Account ID help: advanced: false optional: false @@ -55,7 +55,7 @@ params: default: choice: [] unit: - description: + description: Serial help: You can find this in the Zendure App in the settings of the device advanced: false optional: false @@ -64,7 +64,7 @@ params: default: EU choice: ['EU', 'Global'] unit: - description: + description: Region help: advanced: false optional: false diff --git a/templates/release/en/tariff/amber-electric.yaml b/templates/release/en/tariff/amber-electric.yaml index 73847d9b8b..c30fd68c8b 100644 --- a/templates/release/en/tariff/amber-electric.yaml +++ b/templates/release/en/tariff/amber-electric.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: amber - token: # optional - siteid: # optional - channel: # optional + token: # Token, optional + siteid: # Site ID, optional + channel: # Channel, optional advanced: | type: template template: amber - token: # optional - siteid: # optional - channel: # optional + token: # Token, optional + siteid: # Site ID, optional + channel: # Channel, optional charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -26,7 +26,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: true @@ -35,7 +35,7 @@ params: default: choice: [] unit: - description: + description: Site ID help: advanced: false optional: true @@ -44,7 +44,7 @@ params: default: choice: [] unit: - description: + description: Channel help: advanced: false optional: true diff --git a/templates/release/en/tariff/awattar.yaml b/templates/release/en/tariff/awattar.yaml index 625ef55c35..40bc60a97d 100644 --- a/templates/release/en/tariff/awattar.yaml +++ b/templates/release/en/tariff/awattar.yaml @@ -8,11 +8,11 @@ render: - default: | type: template template: awattar - region: AT # [DE, AT] + region: AT # Region, [DE, AT] advanced: | type: template template: awattar - region: AT # [DE, AT] + region: AT # Region, [DE, AT] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -22,7 +22,7 @@ params: default: choice: ['DE', 'AT'] unit: - description: + description: Region help: advanced: false optional: false diff --git a/templates/release/en/tariff/electricity-maps-commercial-api.yaml b/templates/release/en/tariff/electricity-maps-commercial-api.yaml index fe9a867ea9..dffcd0ff34 100644 --- a/templates/release/en/tariff/electricity-maps-commercial-api.yaml +++ b/templates/release/en/tariff/electricity-maps-commercial-api.yaml @@ -12,8 +12,8 @@ render: type: template template: electricitymaps uri: https://api-access.electricitymaps.com/2w...1g/ # URI, HTTP(S) address - token: - zone: DE # see https://api.electricitymap.org/v3/zones + token: # Token + zone: DE # Zone, see https://api.electricitymap.org/v3/zones params: - name: uri example: https://api-access.electricitymaps.com/2w...1g/ @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Zone help: see https://api.electricitymap.org/v3/zones advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/tariff/electricity-maps-free-api.yaml b/templates/release/en/tariff/electricity-maps-free-api.yaml index 1baf6253c0..7738d19283 100644 --- a/templates/release/en/tariff/electricity-maps-free-api.yaml +++ b/templates/release/en/tariff/electricity-maps-free-api.yaml @@ -11,15 +11,15 @@ render: - default: | type: template template: electricitymaps-free - token: - zone: DE # see https://api.electricitymap.org/v3/zones + token: # Token + zone: DE # Zone, see https://api.electricitymap.org/v3/zones params: - name: token example: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Zone help: see https://api.electricitymap.org/v3/zones advanced: false optional: false \ No newline at end of file diff --git a/templates/release/en/tariff/energinet.yaml b/templates/release/en/tariff/energinet.yaml index bf3d80f1b3..9961d6bf86 100644 --- a/templates/release/en/tariff/energinet.yaml +++ b/templates/release/en/tariff/energinet.yaml @@ -9,11 +9,11 @@ render: - default: | type: template template: energinet - region: dk1 # [dk1, dk2] + region: dk1 # Region, [dk1, dk2] advanced: | type: template template: energinet - region: dk1 # [dk1, dk2] + region: dk1 # Region, [dk1, dk2] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -23,7 +23,7 @@ params: default: choice: ['dk1', 'dk2'] unit: - description: + description: Region help: advanced: false optional: false diff --git a/templates/release/en/tariff/enever.yaml b/templates/release/en/tariff/enever.yaml index 130da727b6..04ee26c10a 100644 --- a/templates/release/en/tariff/enever.yaml +++ b/templates/release/en/tariff/enever.yaml @@ -9,24 +9,24 @@ render: - default: | type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + token: # Token + provider: # Provider, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] advanced: | type: template template: enever - token: - provider: # [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] + token: # Token + provider: # Provider, [, AA, AIP, ANWB, BE, EE, EN, EVO, EZ, FR, GSL, MDE, NE, PE, TI, VDB, VON, WE, ZG, ZP] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) - interval: 3h # optional + interval: 3h # Interval, optional params: - name: token example: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -35,7 +35,7 @@ params: default: choice: ['', 'AA', 'AIP', 'ANWB', 'BE', 'EE', 'EN', 'EVO', 'EZ', 'FR', 'GSL', 'MDE', 'NE', 'PE', 'TI', 'VDB', 'VON', 'WE', 'ZG', 'ZP'] unit: - description: + description: Provider help: advanced: false optional: false @@ -71,7 +71,7 @@ params: default: 3h choice: [] unit: - description: + description: Interval help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/entso-e.yaml b/templates/release/en/tariff/entso-e.yaml index b17690125a..7b34aa46ad 100644 --- a/templates/release/en/tariff/entso-e.yaml +++ b/templates/release/en/tariff/entso-e.yaml @@ -12,13 +12,13 @@ render: - default: | type: template template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) advanced: | type: template template: entsoe - securitytoken: # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) - domain: BZN|DE-LU # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) + securitytoken: # Security token, Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional) + domain: BZN|DE-LU # Domain, see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional) charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Security token help: Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation advanced: false optional: true @@ -37,7 +37,7 @@ params: default: choice: [] unit: - description: + description: Domain help: see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas advanced: false optional: true diff --git a/templates/release/en/tariff/forecast-solar.yaml b/templates/release/en/tariff/forecast-solar.yaml index e5adec0c06..16fb101e9a 100644 --- a/templates/release/en/tariff/forecast-solar.yaml +++ b/templates/release/en/tariff/forecast-solar.yaml @@ -24,8 +24,8 @@ render: kwp: 9.8 # Maximum generator power (kWp) az: 180 # Azimuth, -180 = north, -90 = east, 0 = south, 90 = west, 180 = north horizon: 0,0,15,30,45,60,60,60,45,30,15,0 # Horizon, Simulates terrain shadows, [more information](https://doc.forecast.solar/horizon) (optional) - apikey: # API key, optional - interval: 1h # optional + apikey: # API Key, optional + interval: 1h # Interval, optional params: - name: lat example: 55.7351 @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: API key + description: API Key help: advanced: true optional: true @@ -95,7 +95,7 @@ params: default: 1h choice: [] unit: - description: + description: Interval help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/fraunhofer-ise.yaml b/templates/release/en/tariff/fraunhofer-ise.yaml index 643fd3b6f5..213272af3c 100644 --- a/templates/release/en/tariff/fraunhofer-ise.yaml +++ b/templates/release/en/tariff/fraunhofer-ise.yaml @@ -11,11 +11,11 @@ render: - default: | type: template template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Bidding zone, see https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] advanced: | type: template template: energy-charts-api - bzn: DE-LU # Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] + bzn: DE-LU # Bidding zone, see https://api.energy-charts.info/#/prices/day_ahead_price_price_get [AT, BE, CH, CZ, DE-LU, DE-AT-LU, DK1, DK2, FR, HU, IT-NORTH, NL, NO2, PL, SE4, SI] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -25,8 +25,8 @@ params: default: DE-LU choice: ['AT', 'BE', 'CH', 'CZ', 'DE-LU', 'DE-AT-LU', 'DK1', 'DK2', 'FR', 'HU', 'IT-NORTH', 'NL', 'NO2', 'PL', 'SE4', 'SI'] unit: - description: - help: Bidding zones - https://api.energy-charts.info/#/prices/day_ahead_price_price_get + description: Bidding zone + help: see https://api.energy-charts.info/#/prices/day_ahead_price_price_get advanced: false optional: false - name: charges diff --git a/templates/release/en/tariff/grunstromindex.yaml b/templates/release/en/tariff/grunstromindex.yaml index 890a2a7656..e4e4dc9a97 100644 --- a/templates/release/en/tariff/grunstromindex.yaml +++ b/templates/release/en/tariff/grunstromindex.yaml @@ -11,15 +11,15 @@ render: - default: | type: template template: grünstromindex - zip: - token: # Token for accessing the API from https://console.corrently.io (optional) + zip: # ZIP code + token: # Token, Token for accessing the API from https://console.corrently.io (optional) params: - name: zip example: default: choice: [] unit: - description: + description: ZIP code help: advanced: false optional: false @@ -28,7 +28,7 @@ params: default: choice: [] unit: - description: + description: Token help: Token for accessing the API from https://console.corrently.io advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/national-grid-eso.yaml b/templates/release/en/tariff/national-grid-eso.yaml index be12f4b89a..fc7c387d1b 100644 --- a/templates/release/en/tariff/national-grid-eso.yaml +++ b/templates/release/en/tariff/national-grid-eso.yaml @@ -8,15 +8,15 @@ render: - default: | type: template template: ngeso - region: 1 # Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list (optional) - postalcode: SW1 # Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. (optional) + region: 1 # Region, Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list (optional) + postalcode: SW1 # Postcode, Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. (optional) params: - name: region example: 1 default: choice: [] unit: - description: + description: Region help: Coarser than using a postcode. See https://carbon-intensity.github.io/api-definitions/#region-list advanced: false optional: true @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Postcode help: Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/nordpool-spot-prices.yaml b/templates/release/en/tariff/nordpool-spot-prices.yaml index a304828912..220a55685a 100644 --- a/templates/release/en/tariff/nordpool-spot-prices.yaml +++ b/templates/release/en/tariff/nordpool-spot-prices.yaml @@ -11,13 +11,13 @@ render: - default: | type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Currency, [DKK, EUR, NOK, PLN, RON, SEK] advanced: | type: template template: nordpool - region: GER # [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) - currency: EUR # [DKK, EUR, NOK, PLN, RON, SEK] + region: GER # Region, [EE, LT, LV, AT, BE, FR, GER, NL, PL, DK1, DK2, FI, NO1, NO2, NO3, NO4, NO5, SE1, SE2, SE3, SE4, TEL, SYS] (optional) + currency: EUR # Currency, [DKK, EUR, NOK, PLN, RON, SEK] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -27,7 +27,7 @@ params: default: choice: ['EE', 'LT', 'LV', 'AT', 'BE', 'FR', 'GER', 'NL', 'PL', 'DK1', 'DK2', 'FI', 'NO1', 'NO2', 'NO3', 'NO4', 'NO5', 'SE1', 'SE2', 'SE3', 'SE4', 'TEL', 'SYS'] unit: - description: + description: Region help: advanced: false optional: true @@ -36,7 +36,7 @@ params: default: EUR choice: ['DKK', 'EUR', 'NOK', 'PLN', 'RON', 'SEK'] unit: - description: + description: Currency help: advanced: false optional: false diff --git a/templates/release/en/tariff/octopus-energy-api.yaml b/templates/release/en/tariff/octopus-energy-api.yaml index ed9f3801c6..e7e5f3cf84 100644 --- a/templates/release/en/tariff/octopus-energy-api.yaml +++ b/templates/release/en/tariff/octopus-energy-api.yaml @@ -11,24 +11,24 @@ render: - default: | type: template template: octopus-api - apiKey: # Octopus Energy API Key. - accountNumber: # Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. (optional) + apiKey: # API Key + accountNumber: X-XXXXXXXX # Account Number, Only required if you have multiple accounts. (optional) params: - name: apiKey example: default: choice: [] unit: - description: - help: Octopus Energy API Key. + description: API Key + help: advanced: false optional: false - name: accountNumber - example: + example: X-XXXXXXXX default: choice: [] unit: - description: - help: Optional Account Number (usually in the format X-XXXXXXXX). Only required if you have multiple Accounts. + description: Account Number + help: Only required if you have multiple accounts. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/octopus-energy-product-code.yaml b/templates/release/en/tariff/octopus-energy-product-code.yaml index 353df8d8b0..b71886e830 100644 --- a/templates/release/en/tariff/octopus-energy-product-code.yaml +++ b/templates/release/en/tariff/octopus-energy-product-code.yaml @@ -9,16 +9,16 @@ render: - default: | type: template template: octopus-productcode - productCode: AGILE-FLEX-22-11-25 # The tariff code for your energy contract. Make sure this is set to your import tariff code. - region: # The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] - directDebit: true # Use Direct Debit tariff rates. (optional) + productCode: AGILE-FLEX-22-11-25 # Product Code, The tariff code for your energy contract. Make sure this is set to your import tariff code. + region: # Region, The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/ [A, B, C, D, E, F, G, H, J, K, L, M, N, P] + directDebit: true # Direct debit tariff, Use Direct Debit tariff rates. (optional) params: - name: productCode example: AGILE-FLEX-22-11-25 default: choice: [] unit: - description: + description: Product Code help: The tariff code for your energy contract. Make sure this is set to your import tariff code. advanced: false optional: false @@ -27,7 +27,7 @@ params: default: choice: ['A', 'B', 'C', 'D', 'E', 'F', 'G', 'H', 'J', 'K', 'L', 'M', 'N', 'P'] unit: - description: + description: Region help: 'The DNO region you are located in. More information: https://www.energy-stats.uk/dno-region-codes-explained/' advanced: false optional: false @@ -36,7 +36,7 @@ params: default: true choice: [] unit: - description: + description: Direct debit tariff help: Use Direct Debit tariff rates. advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/open-meteo.yaml b/templates/release/en/tariff/open-meteo.yaml index d5c0eeea1b..673db71d1b 100644 --- a/templates/release/en/tariff/open-meteo.yaml +++ b/templates/release/en/tariff/open-meteo.yaml @@ -29,7 +29,7 @@ render: efficiency: 100 # Efficiency [%], optional alphatemp: -0.004 # Temperature coefficient, optional rossmodel: 0.0342 # Cooling type [Ross Model], Well Cooled (0.0200), Free Standing (0.0208), Flat on Roof (0.0260), Not So Well Cooled (0.0342), Transparent PV (0.0455), Facade Integrated (0.0538), On Sloped Roof (0.0563) [Paper](https://www.sciencedirect.com/science/article/pii/S0038092X20309107) (optional) - interval: 1h # optional + interval: 1h # Interval, optional params: - name: lat example: 55.7351 @@ -135,7 +135,7 @@ params: default: 1h choice: [] unit: - description: + description: Interval help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/ostrom.yaml b/templates/release/en/tariff/ostrom.yaml index 15626ba8fa..0c9d4e720c 100644 --- a/templates/release/en/tariff/ostrom.yaml +++ b/templates/release/en/tariff/ostrom.yaml @@ -11,16 +11,16 @@ render: - default: | type: template template: ostrom - clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a - contract: 100523456 # Only required if multiple contracts belong to the same user (optional) + clientid: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # Client ID + clientsecret: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a # Client Secret + contract: 100523456 # Contract number, Only required if multiple contracts belong to the same user (optional) params: - name: clientid example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 default: choice: [] unit: - description: + description: Client ID help: advanced: false optional: false @@ -29,7 +29,7 @@ params: default: choice: [] unit: - description: + description: Client Secret help: advanced: false optional: false @@ -38,7 +38,7 @@ params: default: choice: [] unit: - description: + description: Contract number help: Only required if multiple contracts belong to the same user advanced: false optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/smartenergy-smartcontrol.yaml b/templates/release/en/tariff/smartenergy-smartcontrol.yaml index 916d1de694..f6c6bd8b9b 100644 --- a/templates/release/en/tariff/smartenergy-smartcontrol.yaml +++ b/templates/release/en/tariff/smartenergy-smartcontrol.yaml @@ -5,6 +5,7 @@ product: description: smartCONTROL group: Dynamic electricity price countries: ["AT"] +requirements: ["skiptest"] render: - default: | type: template diff --git a/templates/release/en/tariff/solcast.yaml b/templates/release/en/tariff/solcast.yaml index bfa625b557..cb0f461069 100644 --- a/templates/release/en/tariff/solcast.yaml +++ b/templates/release/en/tariff/solcast.yaml @@ -10,24 +10,24 @@ render: - default: | type: template template: solcast - site: # ressource ID of your site - token: # Solcast API Token + site: # Ressource ID of your site + token: # API Token advanced: | type: template template: solcast - site: # ressource ID of your site - token: # Solcast API Token - from: # Start time of data retrieval, specified in full hours, e.g. "6" (optional) - to: # End time of data retrieval, specified in full hours, e.g. "20" (optional) - interval: 3h # optional + site: # Ressource ID of your site + token: # API Token + from: # Start time, Start time of data retrieval, specified in full hours, e.g. "6" (optional) + to: # End time, End time of data retrieval, specified in full hours, e.g. "20" (optional) + interval: 3h # Interval, optional params: - name: site example: default: choice: [] unit: - description: - help: ressource ID of your site + description: Ressource ID of your site + help: advanced: false optional: false - name: token @@ -35,8 +35,8 @@ params: default: choice: [] unit: - description: - help: Solcast API Token + description: API Token + help: advanced: false optional: false - name: from @@ -44,7 +44,7 @@ params: default: choice: [] unit: - description: + description: Start time help: Start time of data retrieval, specified in full hours, e.g. "6" advanced: true optional: true @@ -53,7 +53,7 @@ params: default: choice: [] unit: - description: + description: End time help: End time of data retrieval, specified in full hours, e.g. "20" advanced: true optional: true @@ -62,7 +62,7 @@ params: default: 3h choice: [] unit: - description: + description: Interval help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/tariff/spotty-energie.yaml b/templates/release/en/tariff/spotty-energie.yaml index ef4a03dcda..4b5937ba9b 100644 --- a/templates/release/en/tariff/spotty-energie.yaml +++ b/templates/release/en/tariff/spotty-energie.yaml @@ -9,13 +9,13 @@ render: - default: | type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Contract ID, You can get your contract id from the customer portal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Price type, Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] advanced: | type: template template: spottyenergy - contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # You can get your contract id from the customer portal https://i.spottyenergie.at/ - pricetype: CONSUMPTION # Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] + contractid: ffffffff-4444-6666-2222-aaaaaabbbbbb # Contract ID, You can get your contract id from the customer portal https://i.spottyenergie.at/ + pricetype: CONSUMPTION # Price type, Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren [MARKET, CONSUMPTION, GENERATION] charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -25,7 +25,7 @@ params: default: choice: [] unit: - description: + description: Contract ID help: You can get your contract id from the customer portal https://i.spottyenergie.at/ advanced: false optional: false @@ -34,7 +34,7 @@ params: default: CONSUMPTION choice: ['MARKET', 'CONSUMPTION', 'GENERATION'] unit: - description: + description: Price type help: Price type, either spotmarket price, consumption price or generation compensation (if contractually agreed), more info at https://www.spottyenergie.at/blog/energie-smart-produzieren advanced: false optional: false diff --git a/templates/release/en/tariff/tibber.yaml b/templates/release/en/tariff/tibber.yaml index ef2f5fa520..13961ca5b7 100644 --- a/templates/release/en/tariff/tibber.yaml +++ b/templates/release/en/tariff/tibber.yaml @@ -11,13 +11,13 @@ render: - default: | type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Only required if you have multiple homes in your Tibber account. (optional) advanced: | type: template template: tibber - token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 - homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Only required if you have multiple homes in your Tibber account. (optional) + token: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 # API Token + homeid: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c # Home ID, Only required if you have multiple homes in your Tibber account. (optional) charges: # Charge, Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional) tax: # Tax, Additional percentage charge (e.g. 0.2 for 20%) (optional) formula: math.Max((price + charges) * (1 + tax), 0.0) # Formula, Individual formula for calculating the price (optional) @@ -27,7 +27,7 @@ params: default: choice: [] unit: - description: + description: API Token help: advanced: false optional: false @@ -36,7 +36,7 @@ params: default: choice: [] unit: - description: + description: Home ID help: Only required if you have multiple homes in your Tibber account. advanced: false optional: true diff --git a/templates/release/en/tariff/victron-vrm-solar-forecast.yaml b/templates/release/en/tariff/victron-vrm-solar-forecast.yaml index 24e32e57de..91a7b532d8 100644 --- a/templates/release/en/tariff/victron-vrm-solar-forecast.yaml +++ b/templates/release/en/tariff/victron-vrm-solar-forecast.yaml @@ -18,7 +18,7 @@ render: template: victron idsite: 123456 # VRM Site ID of the installation, The VRM Site ID is displayed in the installation settings under "General" token: # API access token, Tokens can be created in VRM in Preferences->Integrations - interval: 1h # optional + interval: 1h # Interval, optional params: - name: idsite example: 123456 @@ -43,7 +43,7 @@ params: default: 1h choice: [] unit: - description: + description: Interval help: advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/aiways.yaml b/templates/release/en/vehicle/aiways.yaml index 6011abd9bc..5145bed7f5 100644 --- a/templates/release/en/vehicle/aiways.yaml +++ b/templates/release/en/vehicle/aiways.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -96,8 +96,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/audi.yaml b/templates/release/en/vehicle/audi.yaml index e00ee032e6..bfba6a04d8 100644 --- a/templates/release/en/vehicle/audi.yaml +++ b/templates/release/en/vehicle/audi.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -96,8 +96,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/bmw.yaml b/templates/release/en/vehicle/bmw.yaml index faa2414262..2c93a90c36 100644 --- a/templates/release/en/vehicle/bmw.yaml +++ b/templates/release/en/vehicle/bmw.yaml @@ -14,7 +14,7 @@ render: vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token advanced: | type: template template: bmw @@ -23,10 +23,10 @@ render: vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: + description: Captcha Token help: advanced: false optional: false @@ -113,8 +113,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/citroen.yaml b/templates/release/en/vehicle/citroen.yaml index bc67559ae4..7291cb42a4 100644 --- a/templates/release/en/vehicle/citroen.yaml +++ b/templates/release/en/vehicle/citroen.yaml @@ -12,8 +12,8 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/dacia.yaml b/templates/release/en/vehicle/dacia.yaml index 57810bdcd3..554a1386b1 100644 --- a/templates/release/en/vehicle/dacia.yaml +++ b/templates/release/en/vehicle/dacia.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/ds.yaml b/templates/release/en/vehicle/ds.yaml index 9781f34f42..fc5f7c3791 100644 --- a/templates/release/en/vehicle/ds.yaml +++ b/templates/release/en/vehicle/ds.yaml @@ -12,8 +12,8 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/evnotify.yaml b/templates/release/en/vehicle/evnotify.yaml index 8b712a999b..820c3ae80b 100644 --- a/templates/release/en/vehicle/evnotify.yaml +++ b/templates/release/en/vehicle/evnotify.yaml @@ -7,20 +7,20 @@ render: - default: | type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional advanced: | type: template template: evnotify - akey: - token: + akey: # API Key + token: # Token title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -31,7 +31,7 @@ params: default: choice: [] unit: - description: + description: API Key help: advanced: false optional: false @@ -40,7 +40,7 @@ params: default: choice: [] unit: - description: + description: Token help: advanced: false optional: false @@ -85,8 +85,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/fiat.yaml b/templates/release/en/vehicle/fiat.yaml index 0de8fa06a2..921bfcde43 100644 --- a/templates/release/en/vehicle/fiat.yaml +++ b/templates/release/en/vehicle/fiat.yaml @@ -11,7 +11,7 @@ render: vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) advanced: | type: template template: fiat @@ -20,10 +20,10 @@ render: vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: + description: PIN help: Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. advanced: false optional: true @@ -109,8 +109,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/ford.yaml b/templates/release/en/vehicle/ford.yaml index 714e7caafc..d3be290139 100644 --- a/templates/release/en/vehicle/ford.yaml +++ b/templates/release/en/vehicle/ford.yaml @@ -10,8 +10,8 @@ render: capacity: 50 # Battery capacity (kWh), optional clientid: # FordConnect API Client ID, Setup at https://developer.ford.com clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template @@ -20,12 +20,12 @@ render: capacity: 50 # Battery capacity (kWh), optional clientid: # FordConnect API Client ID, Setup at https://developer.ford.com clientsecret: # FordConnect API Client Secret, Setup at https://developer.ford.com - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -73,7 +73,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -118,8 +118,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/generic-vehicle-without-api.yaml b/templates/release/en/vehicle/generic-vehicle-without-api.yaml index 94705d2660..bf74ba3d14 100644 --- a/templates/release/en/vehicle/generic-vehicle-without-api.yaml +++ b/templates/release/en/vehicle/generic-vehicle-without-api.yaml @@ -16,7 +16,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -63,8 +63,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/hyundai-bluelink.yaml b/templates/release/en/vehicle/hyundai-bluelink.yaml index 0a140715bf..fa205c133d 100644 --- a/templates/release/en/vehicle/hyundai-bluelink.yaml +++ b/templates/release/en/vehicle/hyundai-bluelink.yaml @@ -26,7 +26,7 @@ render: language: en # Language, [en, de] (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/iobroker-bmw.yaml b/templates/release/en/vehicle/iobroker-bmw.yaml index b8b5041571..b4b4994f25 100644 --- a/templates/release/en/vehicle/iobroker-bmw.yaml +++ b/templates/release/en/vehicle/iobroker-bmw.yaml @@ -12,17 +12,17 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber - uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address + uri: # ioBroker URL, including ioBroker.simple-api Port advanced: | type: template template: ioBroker.bmw title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: WBA8E9G50GM091234 # Vehicle Identification Number, BMW VehicleIdentificationNumber - uri: # ioBroker URL inlcuding ioBroker.simple-api Port, HTTP(S) address + uri: # ioBroker URL, including ioBroker.simple-api Port icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -63,8 +63,8 @@ params: default: choice: [] unit: - description: ioBroker URL inlcuding ioBroker.simple-api Port - help: HTTP(S) address + description: ioBroker URL + help: including ioBroker.simple-api Port advanced: false optional: false - name: icon @@ -90,8 +90,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/iso15118.yaml b/templates/release/en/vehicle/iso15118.yaml index 4ecf1d1a5d..ecc5abc9a7 100644 --- a/templates/release/en/vehicle/iso15118.yaml +++ b/templates/release/en/vehicle/iso15118.yaml @@ -23,7 +23,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -70,8 +70,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/jeep.yaml b/templates/release/en/vehicle/jeep.yaml index 9f71e55cd2..272fab74f0 100644 --- a/templates/release/en/vehicle/jeep.yaml +++ b/templates/release/en/vehicle/jeep.yaml @@ -11,7 +11,7 @@ render: vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) advanced: | type: template template: fiat @@ -20,10 +20,10 @@ render: vin: ZFAE... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - pin: # Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) + pin: # PIN, Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -82,7 +82,7 @@ params: default: choice: [] unit: - description: + description: PIN help: Required for evcc to wake up the vehicle for charging and to refresh the SoC while charging. When connected to TWC3, used to start/stop charging. advanced: false optional: true @@ -109,8 +109,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/kia-bluelink.yaml b/templates/release/en/vehicle/kia-bluelink.yaml index aaf74064cf..46a33ae752 100644 --- a/templates/release/en/vehicle/kia-bluelink.yaml +++ b/templates/release/en/vehicle/kia-bluelink.yaml @@ -26,7 +26,7 @@ render: language: en # Language, [en, de] (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/mercedes-benz.yaml b/templates/release/en/vehicle/mercedes-benz.yaml index 9bdecd8e82..c3b557fb78 100644 --- a/templates/release/en/vehicle/mercedes-benz.yaml +++ b/templates/release/en/vehicle/mercedes-benz.yaml @@ -12,9 +12,9 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template @@ -22,13 +22,13 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -67,7 +67,7 @@ params: default: EMEA choice: ['EMEA', 'APAC', 'NORAM'] unit: - description: + description: Region help: advanced: false optional: false @@ -76,7 +76,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -85,7 +85,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -121,8 +121,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/mg.yaml b/templates/release/en/vehicle/mg.yaml index 5e0c7dcb7e..ddd6acf4e8 100644 --- a/templates/release/en/vehicle/mg.yaml +++ b/templates/release/en/vehicle/mg.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/mg2mqtt.yaml b/templates/release/en/vehicle/mg2mqtt.yaml index 193bf3c45d..af8f0fa803 100644 --- a/templates/release/en/vehicle/mg2mqtt.yaml +++ b/templates/release/en/vehicle/mg2mqtt.yaml @@ -24,7 +24,7 @@ render: timeout: 1h # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/mini.yaml b/templates/release/en/vehicle/mini.yaml index e5cf44b35a..2d01ab6fff 100644 --- a/templates/release/en/vehicle/mini.yaml +++ b/templates/release/en/vehicle/mini.yaml @@ -14,7 +14,7 @@ render: vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token advanced: | type: template template: mini @@ -23,10 +23,10 @@ render: vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - hcaptcha: + hcaptcha: # Captcha Token icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: + description: Captcha Token help: advanced: false optional: false @@ -113,8 +113,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/mz2mqtt.yaml b/templates/release/en/vehicle/mz2mqtt.yaml index a8c49a69ba..c9adbf935e 100644 --- a/templates/release/en/vehicle/mz2mqtt.yaml +++ b/templates/release/en/vehicle/mz2mqtt.yaml @@ -20,7 +20,7 @@ render: vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -77,8 +77,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/nissan-ariya.yaml b/templates/release/en/vehicle/nissan-ariya.yaml index bc93ff337c..24f45cbc97 100644 --- a/templates/release/en/vehicle/nissan-ariya.yaml +++ b/templates/release/en/vehicle/nissan-ariya.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/nissan-leaf-pre-2019.yaml b/templates/release/en/vehicle/nissan-leaf-pre-2019.yaml index 0d850e95ac..83518cecce 100644 --- a/templates/release/en/vehicle/nissan-leaf-pre-2019.yaml +++ b/templates/release/en/vehicle/nissan-leaf-pre-2019.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/nissan-leaf.yaml b/templates/release/en/vehicle/nissan-leaf.yaml index 5de281e9d2..e305ff7f9d 100644 --- a/templates/release/en/vehicle/nissan-leaf.yaml +++ b/templates/release/en/vehicle/nissan-leaf.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/opel.yaml b/templates/release/en/vehicle/opel.yaml index 6d8a4f306e..f6ec11d4f7 100644 --- a/templates/release/en/vehicle/opel.yaml +++ b/templates/release/en/vehicle/opel.yaml @@ -12,8 +12,8 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/open-vehicle-monitoring-system.yaml b/templates/release/en/vehicle/open-vehicle-monitoring-system.yaml index 86d9085d80..002ae0cac0 100644 --- a/templates/release/en/vehicle/open-vehicle-monitoring-system.yaml +++ b/templates/release/en/vehicle/open-vehicle-monitoring-system.yaml @@ -13,7 +13,7 @@ render: capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - vehicleid: + vehicleid: # Vehicle ID advanced: | type: template template: ovms @@ -21,15 +21,15 @@ render: capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. password: # Password, Use single quotes in case of leading zeros - vehicleid: + vehicleid: # Vehicle ID icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - server: dexters-web.de + server: dexters-web.de # Server cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) params: - name: title @@ -73,7 +73,7 @@ params: default: choice: [] unit: - description: + description: Vehicle ID help: advanced: false optional: false @@ -100,8 +100,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent @@ -145,7 +145,7 @@ params: default: dexters-web.de choice: [] unit: - description: + description: Server help: advanced: true optional: false diff --git a/templates/release/en/vehicle/peugeot.yaml b/templates/release/en/vehicle/peugeot.yaml index f2622de083..99222be8ae 100644 --- a/templates/release/en/vehicle/peugeot.yaml +++ b/templates/release/en/vehicle/peugeot.yaml @@ -12,8 +12,8 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template @@ -21,12 +21,12 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - accessToken: - refreshToken: + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -65,7 +65,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -74,7 +74,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -110,8 +110,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/polestar.yaml b/templates/release/en/vehicle/polestar.yaml index 1244dd845e..b05f19a3de 100644 --- a/templates/release/en/vehicle/polestar.yaml +++ b/templates/release/en/vehicle/polestar.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/psa-car-controller.yaml b/templates/release/en/vehicle/psa-car-controller.yaml index 7992d4b0f3..51c85ece17 100644 --- a/templates/release/en/vehicle/psa-car-controller.yaml +++ b/templates/release/en/vehicle/psa-car-controller.yaml @@ -9,32 +9,32 @@ render: - default: | type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional advanced: | type: template template: flobz - url: http://192.0.2.2 + url: http://192.0.2.2 # URL vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - wakeup_alt: false # alternative wakeup-code; could lead to increased discharge of the 12V battery. (optional) + wakeup_alt: false # Alternative wakeup code, Can lead to increased discharge of the 12V battery. (optional) params: - name: url example: http://192.0.2.2 default: choice: [] unit: - description: + description: URL help: advanced: false optional: false @@ -88,8 +88,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent @@ -133,7 +133,7 @@ params: default: false choice: [] unit: - description: - help: alternative wakeup-code; could lead to increased discharge of the 12V battery. + description: Alternative wakeup code + help: Can lead to increased discharge of the 12V battery. advanced: true optional: true \ No newline at end of file diff --git a/templates/release/en/vehicle/renault.yaml b/templates/release/en/vehicle/renault.yaml index 81aa25d38f..7908ecd9de 100644 --- a/templates/release/en/vehicle/renault.yaml +++ b/templates/release/en/vehicle/renault.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml b/templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml index 19202486c1..e3ca4aca60 100644 --- a/templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml +++ b/templates/release/en/vehicle/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -97,8 +97,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml b/templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml index a4e6c170cb..928db2d78d 100644 --- a/templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml +++ b/templates/release/en/vehicle/seat-cupraconnect-gen4-born-formentor-tavascan.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/skoda-enyaq.yaml b/templates/release/en/vehicle/skoda-enyaq.yaml index 86029b5336..121e0beace 100644 --- a/templates/release/en/vehicle/skoda-enyaq.yaml +++ b/templates/release/en/vehicle/skoda-enyaq.yaml @@ -24,7 +24,7 @@ render: timeout: 10s # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -108,8 +108,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/smart-1.yaml b/templates/release/en/vehicle/smart-1.yaml index ae72f16b08..e5f20a635a 100644 --- a/templates/release/en/vehicle/smart-1.yaml +++ b/templates/release/en/vehicle/smart-1.yaml @@ -22,7 +22,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/smart-eq.yaml b/templates/release/en/vehicle/smart-eq.yaml index b7c25837eb..4bad511b98 100644 --- a/templates/release/en/vehicle/smart-eq.yaml +++ b/templates/release/en/vehicle/smart-eq.yaml @@ -13,9 +13,9 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template @@ -23,13 +23,13 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional user: # Username, e.g. email address, user id, etc. - region: EMEA # [EMEA, APAC, NORAM] - accessToken: - refreshToken: + region: EMEA # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token vin: V... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -68,7 +68,7 @@ params: default: EMEA choice: ['EMEA', 'APAC', 'NORAM'] unit: - description: + description: Region help: advanced: false optional: false @@ -77,7 +77,7 @@ params: default: choice: [] unit: - description: + description: Access token help: advanced: false optional: false @@ -86,7 +86,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: advanced: false optional: false @@ -122,8 +122,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/tesla-ble.yaml b/templates/release/en/vehicle/tesla-ble.yaml index d769cb2b5b..94ada0edf0 100644 --- a/templates/release/en/vehicle/tesla-ble.yaml +++ b/templates/release/en/vehicle/tesla-ble.yaml @@ -12,7 +12,7 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: W... # Vehicle Identification Number, Required for BLE connection - url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL of the Tesla BLE HTTP Proxy port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional) advanced: | type: template @@ -20,11 +20,11 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional vin: W... # Vehicle Identification Number, Required for BLE connection - url: http://192.168.178.27 # URL of the Tesla BLE HTTP Proxy + url: http://192.168.178.27 # URL, URL of the Tesla BLE HTTP Proxy port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -62,7 +62,7 @@ params: default: choice: [] unit: - description: + description: URL help: URL of the Tesla BLE HTTP Proxy advanced: false optional: false @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/tesla.yaml b/templates/release/en/vehicle/tesla.yaml index a1e3eff967..444740c9f1 100644 --- a/templates/release/en/vehicle/tesla.yaml +++ b/templates/release/en/vehicle/tesla.yaml @@ -25,28 +25,28 @@ render: template: tesla title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, from [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, from [myteslamate.com](https://app.myteslamate.com/). vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template template: tesla title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - clientId: # Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). - accessToken: # from [myteslamate.com](https://app.myteslamate.com/). - refreshToken: # from [myteslamate.com](https://app.myteslamate.com/). + clientId: # Client ID, from [Tesla Developer App](https://developer.tesla.com/dashboard). + accessToken: # Access token, from [myteslamate.com](https://app.myteslamate.com/). + refreshToken: # Refresh token, from [myteslamate.com](https://app.myteslamate.com/). vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional) - commandProxy: https://api.myteslamate.com # When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) - proxyToken: # Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) + commandProxy: https://api.myteslamate.com # Command Proxy, When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. (optional) + proxyToken: # Proxy Token, Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. (optional) cache: 15m # Cache, Time interval with when data should be reloaded from the vehicle (optional) params: - name: title @@ -72,8 +72,8 @@ params: default: choice: [] unit: - description: - help: Client ID of your [Tesla Developer App](https://developer.tesla.com/dashboard). + description: Client ID + help: from [Tesla Developer App](https://developer.tesla.com/dashboard). advanced: false optional: false - name: accessToken @@ -81,7 +81,7 @@ params: default: choice: [] unit: - description: + description: Access token help: from [myteslamate.com](https://app.myteslamate.com/). advanced: false optional: false @@ -90,7 +90,7 @@ params: default: choice: [] unit: - description: + description: Refresh token help: from [myteslamate.com](https://app.myteslamate.com/). advanced: false optional: false @@ -126,8 +126,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent @@ -171,7 +171,7 @@ params: default: https://api.myteslamate.com choice: [] unit: - description: + description: Command Proxy help: When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default the [myteslamate.com](https://app.myteslamate.com/) proxy is used. With this parameter, you set the base URL of a custom Command Proxy. See for example [TeslaBleHttpProxy](https://github.com/wimaha/TeslaBleHttpProxy) for a proxy sending commands via bluetooth. advanced: true optional: true @@ -180,7 +180,7 @@ params: default: choice: [] unit: - description: + description: Proxy Token help: Token for the [myteslamate.com](https://app.myteslamate.com/) command proxy (pay-per use). Ensure, that you've installed their Virtual Key and granted 'Charge Start', 'Charge Stop' and 'Set Charging Amps' permissions. advanced: true optional: true diff --git a/templates/release/en/vehicle/teslalogger.yaml b/templates/release/en/vehicle/teslalogger.yaml index dec22ff5b9..06d1c2df62 100644 --- a/templates/release/en/vehicle/teslalogger.yaml +++ b/templates/release/en/vehicle/teslalogger.yaml @@ -12,7 +12,7 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional advanced: | type: template @@ -20,11 +20,11 @@ render: title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional id: 1 # TeslaLogger CarID, optional - url: http://192.0.2.2 + url: http://192.0.2.2 # URL port: 5000 # Port, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -62,7 +62,7 @@ params: default: choice: [] unit: - description: + description: URL help: advanced: false optional: false @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/teslamate.yaml b/templates/release/en/vehicle/teslamate.yaml index 7bcbb792a0..1e05c0aade 100644 --- a/templates/release/en/vehicle/teslamate.yaml +++ b/templates/release/en/vehicle/teslamate.yaml @@ -20,7 +20,7 @@ render: id: 1 # Vehicle ID, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -76,8 +76,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/tessie.yaml b/templates/release/en/vehicle/tessie.yaml index 2537768787..9f5633f57e 100644 --- a/templates/release/en/vehicle/tessie.yaml +++ b/templates/release/en/vehicle/tessie.yaml @@ -22,7 +22,7 @@ render: token: # Tessie API Token icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -87,8 +87,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/toyota.yaml b/templates/release/en/vehicle/toyota.yaml index 894885f7a4..96ee894ebf 100644 --- a/templates/release/en/vehicle/toyota.yaml +++ b/templates/release/en/vehicle/toyota.yaml @@ -24,7 +24,7 @@ render: vin: JT... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -99,8 +99,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/tronity.yaml b/templates/release/en/vehicle/tronity.yaml index 3496a1588f..0afcbc6c84 100644 --- a/templates/release/en/vehicle/tronity.yaml +++ b/templates/release/en/vehicle/tronity.yaml @@ -23,7 +23,7 @@ render: vin: W... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -98,8 +98,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/volkswagen-we-connect-id.yaml b/templates/release/en/vehicle/volkswagen-we-connect-id.yaml index 666a370180..44f00466b5 100644 --- a/templates/release/en/vehicle/volkswagen-we-connect-id.yaml +++ b/templates/release/en/vehicle/volkswagen-we-connect-id.yaml @@ -26,7 +26,7 @@ render: timeout: 10s # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -112,8 +112,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/volvo.yaml b/templates/release/en/vehicle/volvo.yaml index 547f65c537..462c33905f 100644 --- a/templates/release/en/vehicle/volvo.yaml +++ b/templates/release/en/vehicle/volvo.yaml @@ -18,24 +18,24 @@ render: template: volvo-connected title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. + vccapikey: # VCC API Key, from [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, from [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, from [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect URI of your evcc instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) advanced: | type: template template: volvo-connected title: # Title, Will be displayed in the user interface (optional) capacity: 50 # Battery capacity (kWh), optional - vccapikey: # VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). - clientId: # Client ID of your [Volvo Developer App](https://developer.volvocars.com/). - clientSecret: # Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). - redirectUri: # Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. + vccapikey: # VCC API Key, from [Volvo Developer App](https://developer.volvocars.com/). + clientId: # Client ID, from [Volvo Developer App](https://developer.volvocars.com/). + clientSecret: # Client Secret, from [Volvo Developer App](https://developer.volvocars.com/). + redirectUri: # Redirect URI, Redirect URI of your evcc instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App. vin: WF0FXX... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer (optional) icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -64,8 +64,8 @@ params: default: choice: [] unit: - description: - help: VCC API Key of your [Volvo Developer App](https://developer.volvocars.com/). + description: VCC API Key + help: from [Volvo Developer App](https://developer.volvocars.com/). advanced: false optional: false - name: clientId @@ -73,8 +73,8 @@ params: default: choice: [] unit: - description: - help: Client ID of your [Volvo Developer App](https://developer.volvocars.com/). + description: Client ID + help: from [Volvo Developer App](https://developer.volvocars.com/). advanced: false optional: false - name: clientSecret @@ -82,8 +82,8 @@ params: default: choice: [] unit: - description: - help: Client Secret of your [Volvo Developer App](https://developer.volvocars.com/). + description: Client Secret + help: from [Volvo Developer App](https://developer.volvocars.com/). advanced: false optional: false - name: redirectUri @@ -91,8 +91,8 @@ params: default: choice: [] unit: - description: - help: 'Redirect URI of your EVCC instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App.' + description: Redirect URI + help: 'Redirect URI of your evcc instance, format: `http://evcc.local:7070/oauth/callback`. Must match the redirect URI set in your Volvo Developer App.' advanced: false optional: false - name: vin @@ -127,8 +127,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/volvo2mqtt.yaml b/templates/release/en/vehicle/volvo2mqtt.yaml index df37953874..d5176ea385 100644 --- a/templates/release/en/vehicle/volvo2mqtt.yaml +++ b/templates/release/en/vehicle/volvo2mqtt.yaml @@ -22,7 +22,7 @@ render: timeout: 720h # Timeout, optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -87,8 +87,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent diff --git a/templates/release/en/vehicle/zero-motorcycles.yaml b/templates/release/en/vehicle/zero-motorcycles.yaml index 6ea42caee5..88939083c8 100644 --- a/templates/release/en/vehicle/zero-motorcycles.yaml +++ b/templates/release/en/vehicle/zero-motorcycles.yaml @@ -21,7 +21,7 @@ render: capacity: 50 # Battery capacity (kWh), optional icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional) phases: 3 # Maximum number of phases, The maximum number of phases which can be used (optional) - mode: # Default charging mode when a vehicle is connected, Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) + mode: # Default charging mode, Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional) minCurrent: 6 # Minimum amperage (A), The minimum amperage per connected phase with which the car should be charged (optional) maxCurrent: 16 # Maximum amperage (A), The maximum amperage per connected phase with which the car shuold be charged (optional) identifiers: # Identification, Mostly this can be added later, see: https://docs.evcc.io/en/docs/features/vehicle (optional) @@ -96,8 +96,8 @@ params: default: choice: [] unit: - description: Default charging mode when a vehicle is connected - help: Possible values are Off, Now, MinPV and PV, or empty if none should be set + description: Default charging mode + help: Used when a vehicle is connected. Possible values are Off, Now, MinPV and PV, or empty if none should be set advanced: true optional: true - name: minCurrent From 37d4e86ef253115db17cf0ac68dec3971b4e31d4 Mon Sep 17 00:00:00 2001 From: Michael Geers Date: Fri, 13 Jun 2025 21:05:10 +0200 Subject: [PATCH 10/10] hide detail pages from nav --- docs/devices-next/chargers/abb-terra-ac-ocpp.mdx | 1 + docs/devices-next/chargers/abb-terra-ac.mdx | 1 + docs/devices-next/chargers/abl-em4-single-ocpp.mdx | 1 + docs/devices-next/chargers/abl-em4-single-sbcx.mdx | 1 + docs/devices-next/chargers/abl-em4-twin-ocpp.mdx | 1 + docs/devices-next/chargers/abl-em4-twin-sbcx.mdx | 1 + docs/devices-next/chargers/abl-emh1.mdx | 1 + docs/devices-next/chargers/abl-emh2-ocpp.mdx | 1 + docs/devices-next/chargers/abl-emh2.mdx | 1 + docs/devices-next/chargers/abl-emh3-ocpp.mdx | 1 + docs/devices-next/chargers/alfen-eve-ocpp.mdx | 1 + docs/devices-next/chargers/alfen-eve.mdx | 1 + docs/devices-next/chargers/alpha-innotec.mdx | 1 + docs/devices-next/chargers/alphatec-ladesaule-twin.mdx | 1 + docs/devices-next/chargers/alphatec-wallbox-mini.mdx | 1 + docs/devices-next/chargers/alphatec-wallbox-power.mdx | 1 + .../chargers/amperfied-wallbox-connect-business.mdx | 1 + .../chargers/amperfied-wallbox-connect-home.mdx | 1 + .../chargers/amperfied-wallbox-connect-solar.mdx | 1 + .../chargers/amperfied-wallbox-energy-control.mdx | 1 + docs/devices-next/chargers/ampure-next.mdx | 1 + docs/devices-next/chargers/ampure-unite.mdx | 1 + docs/devices-next/chargers/audi-wallbox-plus.mdx | 1 + docs/devices-next/chargers/audi-wallbox-pro.mdx | 1 + docs/devices-next/chargers/autel-ac-compact.mdx | 1 + docs/devices-next/chargers/autel-ac-maxicharger.mdx | 1 + docs/devices-next/chargers/autoaid-business-wallbox.mdx | 1 + .../chargers/autoaid-intelligent-wallbox.mdx | 1 + docs/devices-next/chargers/avm-fritzdect.mdx | 1 + docs/devices-next/chargers/bender-cc612.mdx | 1 + docs/devices-next/chargers/bender-cc613.mdx | 1 + docs/devices-next/chargers/bender-icc1314.mdx | 1 + docs/devices-next/chargers/bender-icc1324.mdx | 1 + docs/devices-next/chargers/bmw-i-wallbox.mdx | 1 + docs/devices-next/chargers/bosch-sg-ready.mdx | 1 + docs/devices-next/chargers/bosch-x-change.mdx | 1 + .../devices-next/chargers/buderus-logamatic-hmc-20-z.mdx | 1 + docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx | 1 + docs/devices-next/chargers/buderus-sg-ready.mdx | 1 + docs/devices-next/chargers/cfos-power-brain-solar.mdx | 1 + docs/devices-next/chargers/cfos-power-brain.mdx | 1 + docs/devices-next/chargers/charge-amps-halo.mdx | 1 + docs/devices-next/chargers/compleo-ebox.mdx | 1 + docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx | 1 + docs/devices-next/chargers/cubos-c11e.mdx | 1 + docs/devices-next/chargers/cubos-c22e.mdx | 1 + docs/devices-next/chargers/cupra-charger-connect-2.mdx | 1 + docs/devices-next/chargers/cupra-charger-connect.mdx | 1 + docs/devices-next/chargers/cupra-charger-pro-2.mdx | 1 + .../chargers/cupra-charger-pro-eichrecht-2.mdx | 1 + docs/devices-next/chargers/cupra-charger-pro.mdx | 1 + docs/devices-next/chargers/dadapower-premium-wallbox.mdx | 1 + docs/devices-next/chargers/daheimladen-wallbox.mdx | 1 + docs/devices-next/chargers/daikin-homehub-sg-ready.mdx | 1 + docs/devices-next/chargers/delta-ac-max-basic.mdx | 1 + docs/devices-next/chargers/delta-ac-max-smart.mdx | 1 + docs/devices-next/chargers/delta-slim-charger.mdx | 1 + docs/devices-next/chargers/delta-ultra-fast-charger.mdx | 1 + docs/devices-next/chargers/demo-charger.mdx | 1 + docs/devices-next/chargers/e-on-drive-ebox.mdx | 1 + docs/devices-next/chargers/e-on-drive-vbox.mdx | 1 + docs/devices-next/chargers/e3-dc-easy-connect.mdx | 1 + docs/devices-next/chargers/easee-charge-core.mdx | 1 + docs/devices-next/chargers/easee-charge-lite.mdx | 1 + docs/devices-next/chargers/easee-charge.mdx | 1 + docs/devices-next/chargers/easee-home.mdx | 1 + docs/devices-next/chargers/ebee-wallbox.mdx | 1 + docs/devices-next/chargers/echarge-cph1.mdx | 1 + docs/devices-next/chargers/echarge-cph2.mdx | 1 + docs/devices-next/chargers/echarge-cpm2.mdx | 1 + .../chargers/ecoharmony-evse-epc-2-0-plus.mdx | 1 + docs/devices-next/chargers/edgetech-smart-evse.mdx | 1 + docs/devices-next/chargers/eebus-compatible.mdx | 1 + docs/devices-next/chargers/elco.mdx | 1 + docs/devices-next/chargers/elecq-biz.mdx | 1 + docs/devices-next/chargers/elecq-home.mdx | 1 + docs/devices-next/chargers/elecq-station.mdx | 1 + docs/devices-next/chargers/eledio-go.mdx | 1 + docs/devices-next/chargers/elli-charger-connect-2.mdx | 1 + docs/devices-next/chargers/elli-charger-connect.mdx | 1 + docs/devices-next/chargers/elli-charger-pro-2.mdx | 1 + .../chargers/elli-charger-pro-eichrecht-2.mdx | 1 + docs/devices-next/chargers/elli-charger-pro.mdx | 1 + docs/devices-next/chargers/em2go-home.mdx | 1 + docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx | 1 + docs/devices-next/chargers/enercab-smart.mdx | 1 + docs/devices-next/chargers/enplus-ac-ev-charger.mdx | 1 + docs/devices-next/chargers/ensto-chago-wallbox.mdx | 1 + docs/devices-next/chargers/entratek-power-dot-fix.mdx | 1 + docs/devices-next/chargers/entratek-power-dot-pro-2.mdx | 1 + docs/devices-next/chargers/esl-walli-light.mdx | 1 + docs/devices-next/chargers/esystems-ghostone.mdx | 1 + docs/devices-next/chargers/etrel-inch-duo.mdx | 1 + docs/devices-next/chargers/etrel-inch.mdx | 1 + docs/devices-next/chargers/evbox-elvi.mdx | 1 + docs/devices-next/chargers/evbox-livo.mdx | 1 + docs/devices-next/chargers/evse-din.mdx | 1 + docs/devices-next/chargers/evse-wifi.mdx | 1 + .../devices-next/chargers/free2move-eprowallbox-move.mdx | 1 + docs/devices-next/chargers/free2move-eprowallbox.mdx | 1 + .../chargers/free2move-esolutions-eprowallbox.mdx | 1 + docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx | 1 + docs/devices-next/chargers/garo-glb.mdx | 1 + docs/devices-next/chargers/garo-glbplus.mdx | 1 + docs/devices-next/chargers/garo-ls4-compact.mdx | 1 + docs/devices-next/chargers/garo-ls4.mdx | 1 + docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx | 1 + docs/devices-next/chargers/go-e-charger-gemini.mdx | 1 + docs/devices-next/chargers/go-e-charger-homefix.mdx | 1 + docs/devices-next/chargers/go-e-charger-homeplus.mdx | 1 + docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx | 1 + docs/devices-next/chargers/go-e-charger-pro.mdx | 1 + docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx | 1 + docs/devices-next/chargers/go-e-charger-v3.mdx | 1 + docs/devices-next/chargers/hardy-barth-cph1.mdx | 1 + docs/devices-next/chargers/hardy-barth-cph2.mdx | 1 + docs/devices-next/chargers/hardy-barth-cpm2.mdx | 1 + docs/devices-next/chargers/heidelberg-energy-control.mdx | 1 + docs/devices-next/chargers/hesotec-ebox.mdx | 1 + docs/devices-next/chargers/hesotec-esat.mdx | 1 + docs/devices-next/chargers/home-assistant-switch.mdx | 1 + docs/devices-next/chargers/homecharge-homecharger.mdx | 1 + docs/devices-next/chargers/homematic-ip.mdx | 1 + docs/devices-next/chargers/homewizard.mdx | 1 + docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx | 1 + docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx | 1 + docs/devices-next/chargers/idm.mdx | 1 + docs/devices-next/chargers/index.mdx | 1 + docs/devices-next/chargers/innogy-ebox.mdx | 1 + docs/devices-next/chargers/inro-pantabox.mdx | 1 + docs/devices-next/chargers/juice-charger-me.mdx | 1 + docs/devices-next/chargers/junkers-sg-ready.mdx | 1 + docs/devices-next/chargers/kathrein-kwb-ac20.mdx | 1 + docs/devices-next/chargers/kathrein-kwb-ac35.mdx | 1 + docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx | 1 + docs/devices-next/chargers/kathrein-kwb-ac40.mdx | 1 + docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx | 1 + docs/devices-next/chargers/kathrein-kwb-ac60.mdx | 1 + docs/devices-next/chargers/keba-kecontact-p20.mdx | 1 + .../chargers/keba-kecontact-p30-c-series.mdx | 1 + .../chargers/keba-kecontact-p30-x-series.mdx | 1 + docs/devices-next/chargers/keba-kecontact-p40-pro.mdx | 1 + docs/devices-next/chargers/keba-kecontact-p40.mdx | 1 + docs/devices-next/chargers/kermi-x-center-pro.mdx | 1 + docs/devices-next/chargers/kontron-solar-charger.mdx | 1 + docs/devices-next/chargers/kostal-enector.mdx | 1 + docs/devices-next/chargers/kse-wbx16.mdx | 1 + docs/devices-next/chargers/ladefoxx-evload.mdx | 1 + docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx | 1 + docs/devices-next/chargers/lambda-eu-l-series.mdx | 1 + docs/devices-next/chargers/lrt-home-essentialplus.mdx | 1 + .../chargers/mennekes-amedio-professional.mdx | 1 + .../chargers/mennekes-amtron-4business-700.mdx | 1 + docs/devices-next/chargers/mennekes-amtron-4you-300.mdx | 1 + docs/devices-next/chargers/mennekes-amtron-4you-500.mdx | 1 + .../chargers/mennekes-amtron-chargecontrol.mdx | 1 + .../chargers/mennekes-amtron-compact-2-0s.mdx | 1 + docs/devices-next/chargers/mennekes-amtron-premium.mdx | 1 + .../chargers/mennekes-amtron-professional.mdx | 1 + docs/devices-next/chargers/mennekes-amtron-xtra.mdx | 1 + .../chargers/mennekes-emobility-gateway-acu.mdx | 1 + docs/devices-next/chargers/mennekes-smart-acu.mdx | 1 + docs/devices-next/chargers/mennekes-smart-t-acu.mdx | 1 + docs/devices-next/chargers/my-pv-ac-elwa-2.mdx | 1 + docs/devices-next/chargers/my-pv-ac-thor-9s.mdx | 1 + docs/devices-next/chargers/my-pv-ac-thor.mdx | 1 + docs/devices-next/chargers/mystrom-switch.mdx | 1 + docs/devices-next/chargers/nibe-ap-aw10.mdx | 1 + docs/devices-next/chargers/novelan-wpr-net.mdx | 1 + docs/devices-next/chargers/nrgkick-connect.mdx | 1 + docs/devices-next/chargers/nrgkick-gen2.mdx | 1 + docs/devices-next/chargers/obo-bettermann-ion.mdx | 1 + .../chargers/ocpp-1-6j-compatible-smart-charging.mdx | 1 + docs/devices-next/chargers/openevse.mdx | 1 + docs/devices-next/chargers/openwb-pro.mdx | 1 + docs/devices-next/chargers/openwb-series2.mdx | 1 + docs/devices-next/chargers/openwb-software-2-x.mdx | 1 + docs/devices-next/chargers/optec-mobility-one.mdx | 1 + docs/devices-next/chargers/orbis-viaris.mdx | 1 + docs/devices-next/chargers/pc-electric-garo.mdx | 1 + docs/devices-next/chargers/peblar-business.mdx | 1 + docs/devices-next/chargers/peblar-home-plus.mdx | 1 + docs/devices-next/chargers/peblar-home.mdx | 1 + docs/devices-next/chargers/phoenix-contact-charx.mdx | 1 + .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 1 + .../phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 1 + .../phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 1 + .../phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 1 + .../chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 1 + docs/devices-next/chargers/phoenix-contact-ev-ser.mdx | 1 + docs/devices-next/chargers/plugchoice.mdx | 1 + .../chargers/porsche-mobile-charger-connect.mdx | 1 + .../chargers/porsche-mobile-charger-plus.mdx | 1 + docs/devices-next/chargers/porsche-wallbox.mdx | 1 + docs/devices-next/chargers/pracht-alpha-xt.mdx | 1 + docs/devices-next/chargers/pracht-mono-xt.mdx | 1 + docs/devices-next/chargers/pracht-pni.mdx | 1 + docs/devices-next/chargers/pracht-xtplus.mdx | 1 + docs/devices-next/chargers/pulsares-simplebox.mdx | 1 + docs/devices-next/chargers/pulsatrix.mdx | 1 + docs/devices-next/chargers/qcells-q-home-edrive-a.mdx | 1 + docs/devices-next/chargers/roth-thermoaura.mdx | 1 + docs/devices-next/chargers/roth-thermoterra.mdx | 1 + docs/devices-next/chargers/schneider-evlink-pro.mdx | 1 + docs/devices-next/chargers/schrack-i-charge-cion.mdx | 1 + docs/devices-next/chargers/senec-wallbox-pro-s.mdx | 1 + docs/devices-next/chargers/senec-wallbox-pro.mdx | 1 + docs/devices-next/chargers/shelly-1.mdx | 1 + docs/devices-next/chargers/shelly-plug-s.mdx | 1 + docs/devices-next/chargers/shelly-plus-1.mdx | 1 + docs/devices-next/chargers/shelly-pro-1.mdx | 1 + docs/devices-next/chargers/siemens-versicharge-gen3.mdx | 1 + docs/devices-next/chargers/skoda-charger-connect.mdx | 1 + .../chargers/skoda-charger-pro-eichrecht.mdx | 1 + docs/devices-next/chargers/skoda-charger-pro.mdx | 1 + docs/devices-next/chargers/skoda-iv-charger-connect.mdx | 1 + .../chargers/skoda-iv-charger-connectplus.mdx | 1 + docs/devices-next/chargers/sma-echarger.mdx | 1 + docs/devices-next/chargers/sma-ev-charger.mdx | 1 + docs/devices-next/chargers/smartfox-pro-charger.mdx | 1 + docs/devices-next/chargers/smartwb.mdx | 1 + docs/devices-next/chargers/solaredge-home-ev-charger.mdx | 1 + docs/devices-next/chargers/solax-x3-evc.mdx | 1 + docs/devices-next/chargers/sonnen-sonnencharger.mdx | 1 + .../chargers/spelsberg-wallbox-smart-pro.mdx | 1 + docs/devices-next/chargers/stark-in-strom-easy.mdx | 1 + .../chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx | 1 + .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 1 + docs/devices-next/chargers/sungrow-ac011e-01.mdx | 1 + docs/devices-next/chargers/sungrow-ac011e.mdx | 1 + docs/devices-next/chargers/sungrow-ac22e-01.mdx | 1 + docs/devices-next/chargers/tasmota-single-phase.mdx | 1 + docs/devices-next/chargers/tecalor-thz-sg-ready.mdx | 1 + docs/devices-next/chargers/technisat-technivolt.mdx | 1 + .../devices-next/chargers/tesla-wall-connector-gen-3.mdx | 1 + docs/devices-next/chargers/tessie.mdx | 1 + docs/devices-next/chargers/tigo-go-ev-charger.mdx | 1 + .../chargers/tinkerforge-warp-charger-pro.mdx | 1 + .../chargers/tinkerforge-warp-charger-smart.mdx | 1 + .../chargers/tinkerforge-warp3-charger-pro.mdx | 1 + .../chargers/tinkerforge-warp3-charger-smart.mdx | 1 + .../chargers/tp-link-h-series-smart-plug.mdx | 1 + .../chargers/tp-link-tapo-p-series-smart-plug.mdx | 1 + docs/devices-next/chargers/ubitricity-heinz.mdx | 1 + docs/devices-next/chargers/v2c-trydan.mdx | 1 + .../devices-next/chargers/vaillant-sensonet-sg-ready.mdx | 1 + docs/devices-next/chargers/vestel-connect-plus.mdx | 1 + docs/devices-next/chargers/vestel-evc04-home-smart.mdx | 1 + .../chargers/victron-ev-charging-station-via-gx.mdx | 1 + .../chargers/victron-ev-charging-station.mdx | 1 + .../chargers/viessmann-heatpump-sg-ready.mdx | 1 + .../chargers/viridian-ev-evse-epc-2-0-plus.mdx | 1 + .../chargers/volkswagen-charger-connect-2.mdx | 1 + docs/devices-next/chargers/volkswagen-charger-pro-2.mdx | 1 + .../chargers/volkswagen-charger-pro-eichrecht-2.mdx | 1 + .../chargers/volkswagen-id-charger-connect.mdx | 1 + docs/devices-next/chargers/volkswagen-id-charger-pro.mdx | 1 + docs/devices-next/chargers/volt-time-one.mdx | 1 + docs/devices-next/chargers/volt-time-source-2.mdx | 1 + docs/devices-next/chargers/volt-time-source-2s.mdx | 1 + docs/devices-next/chargers/volt-time-source.mdx | 1 + docs/devices-next/chargers/wallbe-eco-2-0-s.mdx | 1 + docs/devices-next/chargers/wallbe-eco.mdx | 1 + docs/devices-next/chargers/wallbe-pro.mdx | 1 + .../devices-next/chargers/wallbox-commander-2-fw-5-x.mdx | 1 + docs/devices-next/chargers/wallbox-commander-2.mdx | 1 + docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx | 1 + docs/devices-next/chargers/wallbox-copper-sb.mdx | 1 + docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx | 1 + docs/devices-next/chargers/wallbox-pulsar-max.mdx | 1 + .../devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx | 1 + docs/devices-next/chargers/wallbox-pulsar-plus.mdx | 1 + .../chargers/walther-werke-basic-evo-pro.mdx | 1 + docs/devices-next/chargers/webasto-live.mdx | 1 + docs/devices-next/chargers/webasto-next.mdx | 1 + docs/devices-next/chargers/webasto-unite.mdx | 1 + docs/devices-next/chargers/weidmuller-ac-smart.mdx | 1 + docs/devices-next/chargers/wolf-bwl.mdx | 1 + docs/devices-next/chargers/wolf-bws.mdx | 1 + docs/devices-next/chargers/zaptec-go-2.mdx | 1 + docs/devices-next/chargers/zaptec-go-ocpp.mdx | 1 + docs/devices-next/chargers/zaptec-go.mdx | 1 + docs/devices-next/chargers/zaptec-pro.mdx | 1 + docs/devices-next/chargers/zewotherm-eu-l-series.mdx | 1 + docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx | 1 + docs/devices-next/meters/a-tronix.mdx | 1 + docs/devices-next/meters/abb-a43.mdx | 1 + docs/devices-next/meters/abb-a44.mdx | 1 + docs/devices-next/meters/abb-b23.mdx | 1 + docs/devices-next/meters/abb-b24.mdx | 1 + docs/devices-next/meters/acrel-adw300.mdx | 1 + docs/devices-next/meters/ads-tec-storaxe.mdx | 1 + docs/devices-next/meters/alpha-ess-storion-smile.mdx | 1 + docs/devices-next/meters/ampere-ampere-storagepro.mdx | 1 + docs/devices-next/meters/anker-micro-inverter.mdx | 1 + docs/devices-next/meters/apsystems-ez1.mdx | 1 + docs/devices-next/meters/avm-fritzdect.mdx | 1 + docs/devices-next/meters/axitec-axihycon-12-15h.mdx | 1 + .../devices-next/meters/bernecker-engineering-mpm3pm.mdx | 1 + docs/devices-next/meters/bgetech-ds100.mdx | 1 + docs/devices-next/meters/bgetech-ws100.mdx | 1 + docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx | 1 + docs/devices-next/meters/bosswerk-micro-inverter.mdx | 1 + docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx | 1 + docs/devices-next/meters/carlo-gavazzi-em24.mdx | 1 + docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx | 1 + docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx | 1 + docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx | 1 + docs/devices-next/meters/carlo-gavazzi-et112.mdx | 1 + docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx | 1 + docs/devices-next/meters/cfos-powerbrain-meter.mdx | 1 + docs/devices-next/meters/demo-battery.mdx | 1 + docs/devices-next/meters/demo-meter.mdx | 1 + docs/devices-next/meters/deye-3p-hybrid-inverter.mdx | 1 + docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx | 1 + docs/devices-next/meters/deye-micro-inverter.mdx | 1 + .../devices-next/meters/deye-storage-hybrid-inverter.mdx | 1 + docs/devices-next/meters/deye-string-inverter.mdx | 1 + docs/devices-next/meters/discovergy.mdx | 1 + docs/devices-next/meters/dsmr.mdx | 1 + docs/devices-next/meters/dzg-dvh4013.mdx | 1 + docs/devices-next/meters/e3-dc.mdx | 1 + docs/devices-next/meters/eastron-sdm120-modbus.mdx | 1 + docs/devices-next/meters/eastron-sdm220-230.mdx | 1 + docs/devices-next/meters/eastron-sdm630-modbus.mdx | 1 + docs/devices-next/meters/eastron-sdm72d-m.mdx | 1 + docs/devices-next/meters/eastron-sdm72dm-v2.mdx | 1 + docs/devices-next/meters/enphase-iq-envoy.mdx | 1 + docs/devices-next/meters/esphome-dlms-meter-austria.mdx | 1 + docs/devices-next/meters/esphome-dsmr.mdx | 1 + docs/devices-next/meters/fenecon.mdx | 1 + .../meters/foxess-h1-series-hybrid-inverter.mdx | 1 + .../meters/foxess-h3-series-hybrid-inverter.mdx | 1 + .../meters/foxess-h3-smart-series-hybrid-inverter.mdx | 1 + docs/devices-next/meters/fronius-ohmpilot.mdx | 1 + docs/devices-next/meters/fronius-primo-gen24-plus.mdx | 1 + .../meters/fronius-smartmeter-via-inverter.mdx | 1 + docs/devices-next/meters/fronius-solar-api-v1.mdx | 1 + docs/devices-next/meters/fronius-symo-gen24-plus.mdx | 1 + .../meters/ginlong-solis-hybrid-inverter-rhi-series.mdx | 1 + .../meters/ginlong-solis-hybrid-inverter-s-series.mdx | 1 + docs/devices-next/meters/ginlong-solis-inverter.mdx | 1 + docs/devices-next/meters/go-e-controller.mdx | 1 + .../meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx | 1 + docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx | 1 + docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx | 1 + docs/devices-next/meters/growatt-hybrid-inverter.mdx | 1 + .../meters/growatt-tl-x-h-hybrid-inverter.mdx | 1 + docs/devices-next/meters/homematic-ip.mdx | 1 + docs/devices-next/meters/homewizard-kwh-meter.mdx | 1 + docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx | 1 + .../meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 1 + .../meters/hoymiles-hm-and-hms-series-via-opendtu.mdx | 1 + docs/devices-next/meters/huawei-emma.mdx | 1 + docs/devices-next/meters/huawei-smartlogger.mdx | 1 + docs/devices-next/meters/huawei-sun2000-sdongle.mdx | 1 + docs/devices-next/meters/huawei-sun2000.mdx | 1 + docs/devices-next/meters/iammeter-wem3080.mdx | 1 + .../meters/iammeter-wem3080t-wem3046t-wem3050t.mdx | 1 + docs/devices-next/meters/igen-tech-solarman-logger.mdx | 1 + docs/devices-next/meters/index.mdx | 1 + docs/devices-next/meters/inepro-pro380-mod.mdx | 1 + docs/devices-next/meters/iometer.mdx | 1 + docs/devices-next/meters/janitza-b-series.mdx | 1 + docs/devices-next/meters/janitza-umg-series.mdx | 1 + docs/devices-next/meters/keba-kecontact-e10.mdx | 1 + docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx | 1 + docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx | 1 + docs/devices-next/meters/kostal-piko-ba.mdx | 1 + docs/devices-next/meters/kostal-piko-hybrid.mdx | 1 + docs/devices-next/meters/kostal-piko-legacy.mdx | 1 + docs/devices-next/meters/kostal-piko-mp-plus.mdx | 1 + docs/devices-next/meters/kostal-piko.mdx | 1 + ...re-hybrid-incl-grid-charging-of-the-house-battery.mdx | 1 + docs/devices-next/meters/kostal-plenticore-hybrid.mdx | 1 + .../meters/kostal-smart-energy-meter-via-inverter.mdx | 1 + docs/devices-next/meters/kostal-smart-energy-meter.mdx | 1 + docs/devices-next/meters/lg-ess-home-15.mdx | 1 + docs/devices-next/meters/lg-ess-home-8-10.mdx | 1 + docs/devices-next/meters/loxone-miniserver.mdx | 1 + docs/devices-next/meters/m-tec-energy-butler-gen2.mdx | 1 + docs/devices-next/meters/m-tec-energy-butler-gen3.mdx | 1 + .../meters/marstek-venus-battery-storage.mdx | 1 + docs/devices-next/meters/mhendriks-p1-dongle.mdx | 1 + docs/devices-next/meters/my-pv-ac-elwa-2.mdx | 1 + docs/devices-next/meters/my-pv-ac-elwa-e.mdx | 1 + docs/devices-next/meters/my-pv-ac-thor.mdx | 1 + docs/devices-next/meters/my-pv-wifi-meter.mdx | 1 + docs/devices-next/meters/mystrom-switch.mdx | 1 + docs/devices-next/meters/openems.mdx | 1 + docs/devices-next/meters/orno-or-we-516.mdx | 1 + docs/devices-next/meters/orno-or-we-517.mdx | 1 + docs/devices-next/meters/p1monitor-p1-monitor.mdx | 1 + docs/devices-next/meters/plexlog.mdx | 1 + docs/devices-next/meters/powerdog.mdx | 1 + docs/devices-next/meters/powerfox-poweropti.mdx | 1 + .../devices-next/meters/qcells-hybrid-inverter-cloud.mdx | 1 + docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx | 1 + docs/devices-next/meters/rct-power.mdx | 1 + .../meters/saia-burgess-controls-sbc-ale3.mdx | 1 + .../meters/saia-burgess-controls-sbc-awd3.mdx | 1 + .../meters/saj-h1-series-hybrid-solar-inverter.mdx | 1 + .../meters/saj-h2-series-hybrid-solar-inverter.mdx | 1 + .../devices-next/meters/saj-r5-series-solar-inverter.mdx | 1 + docs/devices-next/meters/sax-homespeicher.mdx | 1 + .../meters/schneider-electric-iem3xxx-modbus.mdx | 1 + docs/devices-next/meters/senec-home.mdx | 1 + .../meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx | 1 + docs/devices-next/meters/shelly-1pm-mini.mdx | 1 + docs/devices-next/meters/shelly-1pm.mdx | 1 + docs/devices-next/meters/shelly-3em.mdx | 1 + docs/devices-next/meters/shelly-em.mdx | 1 + docs/devices-next/meters/shelly-plug-s.mdx | 1 + docs/devices-next/meters/shelly-pm-mini.mdx | 1 + docs/devices-next/meters/shelly-pro-1pm.mdx | 1 + docs/devices-next/meters/shelly-pro-3-em.mdx | 1 + .../meters/shelly-pro-3em-monophase-mode.mdx | 1 + docs/devices-next/meters/shelly-pro-em.mdx | 1 + docs/devices-next/meters/siemens-7kt1665.mdx | 1 + .../meters/siemens-junelight-smart-battery.mdx | 1 + docs/devices-next/meters/siemens-pac-2200.mdx | 1 + ...sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx | 1 + docs/devices-next/meters/sma-data-manager.mdx | 1 + docs/devices-next/meters/sma-energy-meter.mdx | 1 + docs/devices-next/meters/sma-inverter-speedwire.mdx | 1 + .../meters/sma-smart-energy-hybrid-inverter.mdx | 1 + .../meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx | 1 + .../meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx | 1 + docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx | 1 + docs/devices-next/meters/sma-sunny-island-modbus.mdx | 1 + docs/devices-next/meters/sma-webbox.mdx | 1 + docs/devices-next/meters/sma-wechselrichter-modbus.mdx | 1 + docs/devices-next/meters/smartfox-box.mdx | 1 + docs/devices-next/meters/smartfox-light-em2-firmware.mdx | 1 + docs/devices-next/meters/smartfox-pro-2.mdx | 1 + docs/devices-next/meters/smartfox-pro-light-2.mdx | 1 + docs/devices-next/meters/smartfox-pro-light.mdx | 1 + docs/devices-next/meters/smartfox-pro.mdx | 1 + docs/devices-next/meters/smartfox-reg-extended.mdx | 1 + docs/devices-next/meters/smartfox-reg.mdx | 1 + docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx | 1 + docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx | 1 + docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx | 1 + docs/devices-next/meters/sofarsolar-inverter.mdx | 1 + docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx | 1 + docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx | 1 + docs/devices-next/meters/solaranzeige-solaranzeige.mdx | 1 + docs/devices-next/meters/solaredge-hybrid-inverter.mdx | 1 + docs/devices-next/meters/solaredge-inverter.mdx | 1 + docs/devices-next/meters/solarlog.mdx | 1 + .../meters/solarmax-max-storage-max-storage-ultimate.mdx | 1 + docs/devices-next/meters/solarmax-solarmax-smt.mdx | 1 + docs/devices-next/meters/solarmax-sp-series-inverter.mdx | 1 + docs/devices-next/meters/solarwatt-energymanager-pro.mdx | 1 + docs/devices-next/meters/solarwatt-energymanager.mdx | 1 + docs/devices-next/meters/solarwatt-manager-flex.mdx | 1 + .../solarwatt-myreserve-matrix-lan-oder-powergateway.mdx | 1 + docs/devices-next/meters/solarwatt-myreserve.mdx | 1 + docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx | 1 + docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx | 1 + docs/devices-next/meters/solax-inverter-cloud.mdx | 1 + docs/devices-next/meters/solinteng.mdx | 1 + docs/devices-next/meters/sonnen-comfort.mdx | 1 + docs/devices-next/meters/sonnen-eco-5.mdx | 1 + docs/devices-next/meters/sonnen-eco-6.mdx | 1 + docs/devices-next/meters/sonnen-oem-6-5.mdx | 1 + docs/devices-next/meters/sonnen-sonnenbatterie.mdx | 1 + docs/devices-next/meters/st-ems.mdx | 1 + docs/devices-next/meters/steca-coolcept-flex.mdx | 1 + docs/devices-next/meters/sungrow-sg-series-inverter.mdx | 1 + .../meters/sungrow-sh-series-hybrid-inverter.mdx | 1 + docs/devices-next/meters/sunspec-battery-model-124.mdx | 1 + docs/devices-next/meters/sunspec-battery-model-802.mdx | 1 + docs/devices-next/meters/sunspec-hybrid-inverter.mdx | 1 + docs/devices-next/meters/sunspec-inverter.mdx | 1 + docs/devices-next/meters/sunspec-meter.mdx | 1 + docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx | 1 + docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx | 1 + docs/devices-next/meters/sunsynk-micro-inverter.mdx | 1 + .../meters/sunsynk-storage-hybrid-inverter.mdx | 1 + docs/devices-next/meters/sunsynk-string-inverter.mdx | 1 + docs/devices-next/meters/sunway.mdx | 1 + .../tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx | 1 + .../meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx | 1 + docs/devices-next/meters/tasmota-three-phase.mdx | 1 + docs/devices-next/meters/tesla-powerwall.mdx | 1 + docs/devices-next/meters/tibber-pulse.mdx | 1 + docs/devices-next/meters/tp-link-h-series-smart-plug.mdx | 1 + .../meters/tp-link-tapo-p-series-smart-plug.mdx | 1 + .../meters/tq-energy-manager-em2xx-em3xx.mdx | 1 + docs/devices-next/meters/tq-energy-manager-em420.mdx | 1 + docs/devices-next/meters/varta-element.mdx | 1 + docs/devices-next/meters/varta-pulse-neo.mdx | 1 + docs/devices-next/meters/varta-pulse.mdx | 1 + docs/devices-next/meters/victron-em24.mdx | 1 + docs/devices-next/meters/victron-em24_e1.mdx | 1 + docs/devices-next/meters/victron-em530-em540.mdx | 1 + docs/devices-next/meters/victron-energy.mdx | 1 + docs/devices-next/meters/victron-et340.mdx | 1 + .../meters/volkszahler-http-api-import-and-export.mdx | 1 + docs/devices-next/meters/volkszahler-http-api.mdx | 1 + docs/devices-next/meters/volkszahler-websocket-api.mdx | 1 + docs/devices-next/meters/vzlogger.mdx | 1 + docs/devices-next/meters/wago-879-30xx.mdx | 1 + docs/devices-next/meters/wattsonic.mdx | 1 + docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx | 1 + docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx | 1 + docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx | 1 + docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx | 1 + docs/devices-next/meters/youless-energy-monitor.mdx | 1 + docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx | 1 + docs/devices-next/meters/zcs-azzurro-inverter.mdx | 1 + docs/devices-next/meters/zendure-hyper-2000.mdx | 1 + .../meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx | 1 + .../devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx | 1 + docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx | 1 + docs/devices-next/tariffs/amber-electric.mdx | 1 + docs/devices-next/tariffs/awattar.mdx | 1 + .../tariffs/electricity-maps-commercial-api.mdx | 1 + docs/devices-next/tariffs/electricity-maps-free-api.mdx | 1 + docs/devices-next/tariffs/energinet.mdx | 1 + docs/devices-next/tariffs/enever.mdx | 1 + docs/devices-next/tariffs/entso-e.mdx | 1 + docs/devices-next/tariffs/forecast-solar.mdx | 1 + docs/devices-next/tariffs/fraunhofer-ise.mdx | 1 + docs/devices-next/tariffs/green-grid-compass.mdx | 1 + docs/devices-next/tariffs/groupe-e-vario-plus.mdx | 1 + docs/devices-next/tariffs/grunstromindex.mdx | 1 + docs/devices-next/tariffs/index.mdx | 1 + docs/devices-next/tariffs/national-grid-eso.mdx | 1 + docs/devices-next/tariffs/nordpool-spot-prices.mdx | 1 + docs/devices-next/tariffs/octopus-energy-api.mdx | 1 + .../devices-next/tariffs/octopus-energy-product-code.mdx | 1 + docs/devices-next/tariffs/open-meteo.mdx | 1 + docs/devices-next/tariffs/ostrom.mdx | 1 + docs/devices-next/tariffs/pun-orario.mdx | 1 + docs/devices-next/tariffs/smartenergy-smartcontrol.mdx | 1 + docs/devices-next/tariffs/solcast.mdx | 1 + docs/devices-next/tariffs/spotty-energie.mdx | 1 + docs/devices-next/tariffs/tibber.mdx | 1 + docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx | 1 + docs/devices-next/vehicles/aiways.mdx | 1 + docs/devices-next/vehicles/audi.mdx | 1 + docs/devices-next/vehicles/bmw.mdx | 1 + docs/devices-next/vehicles/citroen.mdx | 1 + docs/devices-next/vehicles/dacia.mdx | 1 + docs/devices-next/vehicles/ds.mdx | 1 + docs/devices-next/vehicles/evnotify.mdx | 1 + docs/devices-next/vehicles/fiat.mdx | 1 + docs/devices-next/vehicles/ford.mdx | 1 + .../vehicles/generic-vehicle-without-api.mdx | 1 + docs/devices-next/vehicles/hyundai-bluelink.mdx | 1 + docs/devices-next/vehicles/index.mdx | 1 + docs/devices-next/vehicles/iobroker-bmw.mdx | 1 + docs/devices-next/vehicles/iso15118.mdx | 1 + docs/devices-next/vehicles/jeep.mdx | 1 + docs/devices-next/vehicles/kia-bluelink.mdx | 1 + docs/devices-next/vehicles/mercedes-benz.mdx | 1 + docs/devices-next/vehicles/mg.mdx | 1 + docs/devices-next/vehicles/mg2mqtt.mdx | 1 + docs/devices-next/vehicles/mini.mdx | 1 + docs/devices-next/vehicles/mz2mqtt.mdx | 1 + docs/devices-next/vehicles/nissan-ariya.mdx | 1 + docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx | 1 + docs/devices-next/vehicles/nissan-leaf.mdx | 1 + docs/devices-next/vehicles/niu-e-scooter.mdx | 1 + docs/devices-next/vehicles/opel.mdx | 1 + .../vehicles/open-vehicle-monitoring-system.mdx | 1 + docs/devices-next/vehicles/peugeot.mdx | 1 + docs/devices-next/vehicles/polestar.mdx | 1 + docs/devices-next/vehicles/psa-car-controller.mdx | 1 + docs/devices-next/vehicles/renault.mdx | 1 + ...at-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx | 1 + .../seat-cupraconnect-gen4-born-formentor-tavascan.mdx | 1 + docs/devices-next/vehicles/skoda-enyaq.mdx | 1 + docs/devices-next/vehicles/smart-1.mdx | 1 + docs/devices-next/vehicles/smart-eq.mdx | 1 + docs/devices-next/vehicles/tesla-ble.mdx | 1 + docs/devices-next/vehicles/tesla.mdx | 1 + docs/devices-next/vehicles/teslalogger.mdx | 1 + docs/devices-next/vehicles/teslamate.mdx | 1 + docs/devices-next/vehicles/tessie.mdx | 1 + docs/devices-next/vehicles/toyota.mdx | 1 + docs/devices-next/vehicles/tronity.mdx | 1 + docs/devices-next/vehicles/volkswagen-we-connect-id.mdx | 1 + docs/devices-next/vehicles/volvo.mdx | 1 + docs/devices-next/vehicles/volvo2mqtt.mdx | 1 + docs/devices-next/vehicles/zero-motorcycles.mdx | 1 + .../current/devices-next/chargers/abb-terra-ac-ocpp.mdx | 1 + .../current/devices-next/chargers/abb-terra-ac.mdx | 1 + .../devices-next/chargers/abl-em4-single-ocpp.mdx | 1 + .../devices-next/chargers/abl-em4-single-sbcx.mdx | 1 + .../current/devices-next/chargers/abl-em4-twin-ocpp.mdx | 1 + .../current/devices-next/chargers/abl-em4-twin-sbcx.mdx | 1 + .../current/devices-next/chargers/abl-emh1.mdx | 1 + .../current/devices-next/chargers/abl-emh2-ocpp.mdx | 1 + .../current/devices-next/chargers/abl-emh2.mdx | 1 + .../current/devices-next/chargers/abl-emh3-ocpp.mdx | 1 + .../current/devices-next/chargers/alfen-eve-ocpp.mdx | 1 + .../current/devices-next/chargers/alfen-eve.mdx | 1 + .../current/devices-next/chargers/alpha-innotec.mdx | 1 + .../devices-next/chargers/alphatec-ladesaule-twin.mdx | 1 + .../devices-next/chargers/alphatec-wallbox-mini.mdx | 1 + .../devices-next/chargers/alphatec-wallbox-power.mdx | 1 + .../chargers/amperfied-wallbox-connect-business.mdx | 1 + .../chargers/amperfied-wallbox-connect-home.mdx | 1 + .../chargers/amperfied-wallbox-connect-solar.mdx | 1 + .../chargers/amperfied-wallbox-energy-control.mdx | 1 + .../current/devices-next/chargers/ampure-next.mdx | 1 + .../current/devices-next/chargers/ampure-unite.mdx | 1 + .../current/devices-next/chargers/audi-wallbox-plus.mdx | 1 + .../current/devices-next/chargers/audi-wallbox-pro.mdx | 1 + .../current/devices-next/chargers/autel-ac-compact.mdx | 1 + .../devices-next/chargers/autel-ac-maxicharger.mdx | 1 + .../devices-next/chargers/autoaid-business-wallbox.mdx | 1 + .../chargers/autoaid-intelligent-wallbox.mdx | 1 + .../current/devices-next/chargers/avm-fritzdect.mdx | 1 + .../current/devices-next/chargers/bender-cc612.mdx | 1 + .../current/devices-next/chargers/bender-cc613.mdx | 1 + .../current/devices-next/chargers/bender-icc1314.mdx | 1 + .../current/devices-next/chargers/bender-icc1324.mdx | 1 + .../current/devices-next/chargers/bmw-i-wallbox.mdx | 1 + .../current/devices-next/chargers/bosch-sg-ready.mdx | 1 + .../current/devices-next/chargers/bosch-x-change.mdx | 1 + .../devices-next/chargers/buderus-logamatic-hmc-20-z.mdx | 1 + .../devices-next/chargers/buderus-logamatic-hmc-20.mdx | 1 + .../current/devices-next/chargers/buderus-sg-ready.mdx | 1 + .../devices-next/chargers/cfos-power-brain-solar.mdx | 1 + .../current/devices-next/chargers/cfos-power-brain.mdx | 1 + .../current/devices-next/chargers/charge-amps-halo.mdx | 1 + .../current/devices-next/chargers/compleo-ebox.mdx | 1 + .../devices-next/chargers/cta-all-in-one-aeroplus.mdx | 1 + .../current/devices-next/chargers/cubos-c11e.mdx | 1 + .../current/devices-next/chargers/cubos-c22e.mdx | 1 + .../devices-next/chargers/cupra-charger-connect-2.mdx | 1 + .../devices-next/chargers/cupra-charger-connect.mdx | 1 + .../devices-next/chargers/cupra-charger-pro-2.mdx | 1 + .../chargers/cupra-charger-pro-eichrecht-2.mdx | 1 + .../current/devices-next/chargers/cupra-charger-pro.mdx | 1 + .../devices-next/chargers/dadapower-premium-wallbox.mdx | 1 + .../devices-next/chargers/daheimladen-wallbox.mdx | 1 + .../devices-next/chargers/daikin-homehub-sg-ready.mdx | 1 + .../current/devices-next/chargers/delta-ac-max-basic.mdx | 1 + .../current/devices-next/chargers/delta-ac-max-smart.mdx | 1 + .../current/devices-next/chargers/delta-slim-charger.mdx | 1 + .../devices-next/chargers/delta-ultra-fast-charger.mdx | 1 + .../current/devices-next/chargers/demo-charger.mdx | 1 + .../current/devices-next/chargers/e-on-drive-ebox.mdx | 1 + .../current/devices-next/chargers/e-on-drive-vbox.mdx | 1 + .../current/devices-next/chargers/e3-dc-easy-connect.mdx | 1 + .../current/devices-next/chargers/easee-charge-core.mdx | 1 + .../current/devices-next/chargers/easee-charge-lite.mdx | 1 + .../current/devices-next/chargers/easee-charge.mdx | 1 + .../current/devices-next/chargers/easee-home.mdx | 1 + .../current/devices-next/chargers/ebee-wallbox.mdx | 1 + .../current/devices-next/chargers/echarge-cph1.mdx | 1 + .../current/devices-next/chargers/echarge-cph2.mdx | 1 + .../current/devices-next/chargers/echarge-cpm2.mdx | 1 + .../chargers/ecoharmony-evse-epc-2-0-plus.mdx | 1 + .../devices-next/chargers/edgetech-smart-evse.mdx | 1 + .../current/devices-next/chargers/eebus-compatible.mdx | 1 + .../current/devices-next/chargers/elco.mdx | 1 + .../current/devices-next/chargers/elecq-biz.mdx | 1 + .../current/devices-next/chargers/elecq-home.mdx | 1 + .../current/devices-next/chargers/elecq-station.mdx | 1 + .../current/devices-next/chargers/eledio-go.mdx | 1 + .../devices-next/chargers/elli-charger-connect-2.mdx | 1 + .../devices-next/chargers/elli-charger-connect.mdx | 1 + .../current/devices-next/chargers/elli-charger-pro-2.mdx | 1 + .../chargers/elli-charger-pro-eichrecht-2.mdx | 1 + .../current/devices-next/chargers/elli-charger-pro.mdx | 1 + .../current/devices-next/chargers/em2go-home.mdx | 1 + .../devices-next/chargers/em2go-pro-power-ocpp-onc.mdx | 1 + .../current/devices-next/chargers/enercab-smart.mdx | 1 + .../devices-next/chargers/enplus-ac-ev-charger.mdx | 1 + .../devices-next/chargers/ensto-chago-wallbox.mdx | 1 + .../devices-next/chargers/entratek-power-dot-fix.mdx | 1 + .../devices-next/chargers/entratek-power-dot-pro-2.mdx | 1 + .../current/devices-next/chargers/esl-walli-light.mdx | 1 + .../current/devices-next/chargers/esystems-ghostone.mdx | 1 + .../current/devices-next/chargers/etrel-inch-duo.mdx | 1 + .../current/devices-next/chargers/etrel-inch.mdx | 1 + .../current/devices-next/chargers/evbox-elvi.mdx | 1 + .../current/devices-next/chargers/evbox-livo.mdx | 1 + .../current/devices-next/chargers/evse-din.mdx | 1 + .../current/devices-next/chargers/evse-wifi.mdx | 1 + .../devices-next/chargers/free2move-eprowallbox-move.mdx | 1 + .../devices-next/chargers/free2move-eprowallbox.mdx | 1 + .../chargers/free2move-esolutions-eprowallbox.mdx | 1 + .../devices-next/chargers/fronius-wattpilot-ocpp.mdx | 1 + .../current/devices-next/chargers/garo-glb.mdx | 1 + .../current/devices-next/chargers/garo-glbplus.mdx | 1 + .../current/devices-next/chargers/garo-ls4-compact.mdx | 1 + .../current/devices-next/chargers/garo-ls4.mdx | 1 + .../devices-next/chargers/go-e-charger-gemini-ocpp.mdx | 1 + .../devices-next/chargers/go-e-charger-gemini.mdx | 1 + .../devices-next/chargers/go-e-charger-homefix.mdx | 1 + .../devices-next/chargers/go-e-charger-homeplus.mdx | 1 + .../devices-next/chargers/go-e-charger-pro-ocpp.mdx | 1 + .../current/devices-next/chargers/go-e-charger-pro.mdx | 1 + .../devices-next/chargers/go-e-charger-v3-ocpp.mdx | 1 + .../current/devices-next/chargers/go-e-charger-v3.mdx | 1 + .../current/devices-next/chargers/hardy-barth-cph1.mdx | 1 + .../current/devices-next/chargers/hardy-barth-cph2.mdx | 1 + .../current/devices-next/chargers/hardy-barth-cpm2.mdx | 1 + .../devices-next/chargers/heidelberg-energy-control.mdx | 1 + .../current/devices-next/chargers/hesotec-ebox.mdx | 1 + .../current/devices-next/chargers/hesotec-esat.mdx | 1 + .../devices-next/chargers/home-assistant-switch.mdx | 1 + .../devices-next/chargers/homecharge-homecharger.mdx | 1 + .../current/devices-next/chargers/homematic-ip.mdx | 1 + .../current/devices-next/chargers/homewizard.mdx | 1 + .../devices-next/chargers/huawei-scharger-22kt-s0.mdx | 1 + .../devices-next/chargers/huawei-scharger-7ks-s0.mdx | 1 + .../current/devices-next/chargers/idm.mdx | 1 + .../current/devices-next/chargers/index.mdx | 1 + .../current/devices-next/chargers/innogy-ebox.mdx | 1 + .../current/devices-next/chargers/inro-pantabox.mdx | 1 + .../current/devices-next/chargers/juice-charger-me.mdx | 1 + .../current/devices-next/chargers/junkers-sg-ready.mdx | 1 + .../current/devices-next/chargers/kathrein-kwb-ac20.mdx | 1 + .../current/devices-next/chargers/kathrein-kwb-ac35.mdx | 1 + .../devices-next/chargers/kathrein-kwb-ac40-e.mdx | 1 + .../current/devices-next/chargers/kathrein-kwb-ac40.mdx | 1 + .../devices-next/chargers/kathrein-kwb-ac60-e.mdx | 1 + .../current/devices-next/chargers/kathrein-kwb-ac60.mdx | 1 + .../current/devices-next/chargers/keba-kecontact-p20.mdx | 1 + .../chargers/keba-kecontact-p30-c-series.mdx | 1 + .../chargers/keba-kecontact-p30-x-series.mdx | 1 + .../devices-next/chargers/keba-kecontact-p40-pro.mdx | 1 + .../current/devices-next/chargers/keba-kecontact-p40.mdx | 1 + .../current/devices-next/chargers/kermi-x-center-pro.mdx | 1 + .../devices-next/chargers/kontron-solar-charger.mdx | 1 + .../current/devices-next/chargers/kostal-enector.mdx | 1 + .../current/devices-next/chargers/kse-wbx16.mdx | 1 + .../current/devices-next/chargers/ladefoxx-evload.mdx | 1 + .../current/devices-next/chargers/ladefoxx-mikro-2-0.mdx | 1 + .../current/devices-next/chargers/lambda-eu-l-series.mdx | 1 + .../devices-next/chargers/lrt-home-essentialplus.mdx | 1 + .../chargers/mennekes-amedio-professional.mdx | 1 + .../chargers/mennekes-amtron-4business-700.mdx | 1 + .../devices-next/chargers/mennekes-amtron-4you-300.mdx | 1 + .../devices-next/chargers/mennekes-amtron-4you-500.mdx | 1 + .../chargers/mennekes-amtron-chargecontrol.mdx | 1 + .../chargers/mennekes-amtron-compact-2-0s.mdx | 1 + .../devices-next/chargers/mennekes-amtron-premium.mdx | 1 + .../chargers/mennekes-amtron-professional.mdx | 1 + .../devices-next/chargers/mennekes-amtron-xtra.mdx | 1 + .../chargers/mennekes-emobility-gateway-acu.mdx | 1 + .../current/devices-next/chargers/mennekes-smart-acu.mdx | 1 + .../devices-next/chargers/mennekes-smart-t-acu.mdx | 1 + .../current/devices-next/chargers/my-pv-ac-elwa-2.mdx | 1 + .../current/devices-next/chargers/my-pv-ac-thor-9s.mdx | 1 + .../current/devices-next/chargers/my-pv-ac-thor.mdx | 1 + .../current/devices-next/chargers/mystrom-switch.mdx | 1 + .../current/devices-next/chargers/nibe-ap-aw10.mdx | 1 + .../current/devices-next/chargers/novelan-wpr-net.mdx | 1 + .../current/devices-next/chargers/nrgkick-connect.mdx | 1 + .../current/devices-next/chargers/nrgkick-gen2.mdx | 1 + .../current/devices-next/chargers/obo-bettermann-ion.mdx | 1 + .../chargers/ocpp-1-6j-compatible-smart-charging.mdx | 1 + .../current/devices-next/chargers/openevse.mdx | 1 + .../current/devices-next/chargers/openwb-pro.mdx | 1 + .../current/devices-next/chargers/openwb-series2.mdx | 1 + .../devices-next/chargers/openwb-software-2-x.mdx | 1 + .../current/devices-next/chargers/optec-mobility-one.mdx | 1 + .../current/devices-next/chargers/orbis-viaris.mdx | 1 + .../current/devices-next/chargers/pc-electric-garo.mdx | 1 + .../current/devices-next/chargers/peblar-business.mdx | 1 + .../current/devices-next/chargers/peblar-home-plus.mdx | 1 + .../current/devices-next/chargers/peblar-home.mdx | 1 + .../devices-next/chargers/phoenix-contact-charx.mdx | 1 + .../chargers/phoenix-contact-em-cp-pp-eth.mdx | 1 + .../phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx | 1 + .../phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx | 1 + .../phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx | 1 + .../chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx | 1 + .../devices-next/chargers/phoenix-contact-ev-ser.mdx | 1 + .../current/devices-next/chargers/plugchoice.mdx | 1 + .../chargers/porsche-mobile-charger-connect.mdx | 1 + .../chargers/porsche-mobile-charger-plus.mdx | 1 + .../current/devices-next/chargers/porsche-wallbox.mdx | 1 + .../current/devices-next/chargers/pracht-alpha-xt.mdx | 1 + .../current/devices-next/chargers/pracht-mono-xt.mdx | 1 + .../current/devices-next/chargers/pracht-pni.mdx | 1 + .../current/devices-next/chargers/pracht-xtplus.mdx | 1 + .../current/devices-next/chargers/pulsares-simplebox.mdx | 1 + .../current/devices-next/chargers/pulsatrix.mdx | 1 + .../devices-next/chargers/qcells-q-home-edrive-a.mdx | 1 + .../current/devices-next/chargers/roth-thermoaura.mdx | 1 + .../current/devices-next/chargers/roth-thermoterra.mdx | 1 + .../devices-next/chargers/schneider-evlink-pro.mdx | 1 + .../devices-next/chargers/schrack-i-charge-cion.mdx | 1 + .../devices-next/chargers/senec-wallbox-pro-s.mdx | 1 + .../current/devices-next/chargers/senec-wallbox-pro.mdx | 1 + .../current/devices-next/chargers/shelly-1.mdx | 1 + .../current/devices-next/chargers/shelly-plug-s.mdx | 1 + .../current/devices-next/chargers/shelly-plus-1.mdx | 1 + .../current/devices-next/chargers/shelly-pro-1.mdx | 1 + .../devices-next/chargers/siemens-versicharge-gen3.mdx | 1 + .../devices-next/chargers/skoda-charger-connect.mdx | 1 + .../chargers/skoda-charger-pro-eichrecht.mdx | 1 + .../current/devices-next/chargers/skoda-charger-pro.mdx | 1 + .../devices-next/chargers/skoda-iv-charger-connect.mdx | 1 + .../chargers/skoda-iv-charger-connectplus.mdx | 1 + .../current/devices-next/chargers/sma-echarger.mdx | 1 + .../current/devices-next/chargers/sma-ev-charger.mdx | 1 + .../devices-next/chargers/smartfox-pro-charger.mdx | 1 + .../current/devices-next/chargers/smartwb.mdx | 1 + .../devices-next/chargers/solaredge-home-ev-charger.mdx | 1 + .../current/devices-next/chargers/solax-x3-evc.mdx | 1 + .../devices-next/chargers/sonnen-sonnencharger.mdx | 1 + .../chargers/spelsberg-wallbox-smart-pro.mdx | 1 + .../devices-next/chargers/stark-in-strom-easy.mdx | 1 + .../chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx | 1 + .../chargers/stiebel-eltron-wpm-sg-ready.mdx | 1 + .../current/devices-next/chargers/sungrow-ac011e-01.mdx | 1 + .../current/devices-next/chargers/sungrow-ac011e.mdx | 1 + .../current/devices-next/chargers/sungrow-ac22e-01.mdx | 1 + .../devices-next/chargers/tasmota-single-phase.mdx | 1 + .../devices-next/chargers/tecalor-thz-sg-ready.mdx | 1 + .../devices-next/chargers/technisat-technivolt.mdx | 1 + .../devices-next/chargers/tesla-wall-connector-gen-3.mdx | 1 + .../current/devices-next/chargers/tessie.mdx | 1 + .../current/devices-next/chargers/tigo-go-ev-charger.mdx | 1 + .../chargers/tinkerforge-warp-charger-pro.mdx | 1 + .../chargers/tinkerforge-warp-charger-smart.mdx | 1 + .../chargers/tinkerforge-warp3-charger-pro.mdx | 1 + .../chargers/tinkerforge-warp3-charger-smart.mdx | 1 + .../chargers/tp-link-h-series-smart-plug.mdx | 1 + .../chargers/tp-link-tapo-p-series-smart-plug.mdx | 1 + .../current/devices-next/chargers/ubitricity-heinz.mdx | 1 + .../current/devices-next/chargers/v2c-trydan.mdx | 1 + .../devices-next/chargers/vaillant-sensonet-sg-ready.mdx | 1 + .../devices-next/chargers/vestel-connect-plus.mdx | 1 + .../devices-next/chargers/vestel-evc04-home-smart.mdx | 1 + .../chargers/victron-ev-charging-station-via-gx.mdx | 1 + .../chargers/victron-ev-charging-station.mdx | 1 + .../chargers/viessmann-heatpump-sg-ready.mdx | 1 + .../chargers/viridian-ev-evse-epc-2-0-plus.mdx | 1 + .../chargers/volkswagen-charger-connect-2.mdx | 1 + .../devices-next/chargers/volkswagen-charger-pro-2.mdx | 1 + .../chargers/volkswagen-charger-pro-eichrecht-2.mdx | 1 + .../chargers/volkswagen-id-charger-connect.mdx | 1 + .../devices-next/chargers/volkswagen-id-charger-pro.mdx | 1 + .../current/devices-next/chargers/volt-time-one.mdx | 1 + .../current/devices-next/chargers/volt-time-source-2.mdx | 1 + .../devices-next/chargers/volt-time-source-2s.mdx | 1 + .../current/devices-next/chargers/volt-time-source.mdx | 1 + .../current/devices-next/chargers/wallbe-eco-2-0-s.mdx | 1 + .../current/devices-next/chargers/wallbe-eco.mdx | 1 + .../current/devices-next/chargers/wallbe-pro.mdx | 1 + .../devices-next/chargers/wallbox-commander-2-fw-5-x.mdx | 1 + .../devices-next/chargers/wallbox-commander-2.mdx | 1 + .../devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx | 1 + .../current/devices-next/chargers/wallbox-copper-sb.mdx | 1 + .../devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx | 1 + .../current/devices-next/chargers/wallbox-pulsar-max.mdx | 1 + .../devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx | 1 + .../devices-next/chargers/wallbox-pulsar-plus.mdx | 1 + .../chargers/walther-werke-basic-evo-pro.mdx | 1 + .../current/devices-next/chargers/webasto-live.mdx | 1 + .../current/devices-next/chargers/webasto-next.mdx | 1 + .../current/devices-next/chargers/webasto-unite.mdx | 1 + .../devices-next/chargers/weidmuller-ac-smart.mdx | 1 + .../current/devices-next/chargers/wolf-bwl.mdx | 1 + .../current/devices-next/chargers/wolf-bws.mdx | 1 + .../current/devices-next/chargers/zaptec-go-2.mdx | 1 + .../current/devices-next/chargers/zaptec-go-ocpp.mdx | 1 + .../current/devices-next/chargers/zaptec-go.mdx | 1 + .../current/devices-next/chargers/zaptec-pro.mdx | 1 + .../devices-next/chargers/zewotherm-eu-l-series.mdx | 1 + .../devices-next/chargers/zj-beny-bcp-ev-charger.mdx | 1 + .../current/devices-next/meters/a-tronix.mdx | 1 + .../current/devices-next/meters/abb-a43.mdx | 1 + .../current/devices-next/meters/abb-a44.mdx | 1 + .../current/devices-next/meters/abb-b23.mdx | 1 + .../current/devices-next/meters/abb-b24.mdx | 1 + .../current/devices-next/meters/acrel-adw300.mdx | 1 + .../current/devices-next/meters/ads-tec-storaxe.mdx | 1 + .../devices-next/meters/alpha-ess-storion-smile.mdx | 1 + .../devices-next/meters/ampere-ampere-storagepro.mdx | 1 + .../current/devices-next/meters/anker-micro-inverter.mdx | 1 + .../current/devices-next/meters/apsystems-ez1.mdx | 1 + .../current/devices-next/meters/avm-fritzdect.mdx | 1 + .../devices-next/meters/axitec-axihycon-12-15h.mdx | 1 + .../devices-next/meters/bernecker-engineering-mpm3pm.mdx | 1 + .../current/devices-next/meters/bgetech-ds100.mdx | 1 + .../current/devices-next/meters/bgetech-ws100.mdx | 1 + .../current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx | 1 + .../devices-next/meters/bosswerk-micro-inverter.mdx | 1 + .../devices-next/meters/carlo-gavazzi-em110-111-112.mdx | 1 + .../current/devices-next/meters/carlo-gavazzi-em24.mdx | 1 + .../devices-next/meters/carlo-gavazzi-em24_e1.mdx | 1 + .../devices-next/meters/carlo-gavazzi-em330-em340.mdx | 1 + .../devices-next/meters/carlo-gavazzi-em530-em540.mdx | 1 + .../current/devices-next/meters/carlo-gavazzi-et112.mdx | 1 + .../devices-next/meters/carlo-gavazzi-et330-et340.mdx | 1 + .../devices-next/meters/cfos-powerbrain-meter.mdx | 1 + .../current/devices-next/meters/demo-battery.mdx | 1 + .../current/devices-next/meters/demo-meter.mdx | 1 + .../devices-next/meters/deye-3p-hybrid-inverter.mdx | 1 + .../devices-next/meters/deye-hp3-hybrid-inverter.mdx | 1 + .../current/devices-next/meters/deye-micro-inverter.mdx | 1 + .../devices-next/meters/deye-storage-hybrid-inverter.mdx | 1 + .../current/devices-next/meters/deye-string-inverter.mdx | 1 + .../current/devices-next/meters/discovergy.mdx | 1 + .../current/devices-next/meters/dsmr.mdx | 1 + .../current/devices-next/meters/dzg-dvh4013.mdx | 1 + .../current/devices-next/meters/e3-dc.mdx | 1 + .../devices-next/meters/eastron-sdm120-modbus.mdx | 1 + .../current/devices-next/meters/eastron-sdm220-230.mdx | 1 + .../devices-next/meters/eastron-sdm630-modbus.mdx | 1 + .../current/devices-next/meters/eastron-sdm72d-m.mdx | 1 + .../current/devices-next/meters/eastron-sdm72dm-v2.mdx | 1 + .../current/devices-next/meters/enphase-iq-envoy.mdx | 1 + .../devices-next/meters/esphome-dlms-meter-austria.mdx | 1 + .../current/devices-next/meters/esphome-dsmr.mdx | 1 + .../current/devices-next/meters/fenecon.mdx | 1 + .../meters/foxess-h1-series-hybrid-inverter.mdx | 1 + .../meters/foxess-h3-series-hybrid-inverter.mdx | 1 + .../meters/foxess-h3-smart-series-hybrid-inverter.mdx | 1 + .../current/devices-next/meters/fronius-ohmpilot.mdx | 1 + .../devices-next/meters/fronius-primo-gen24-plus.mdx | 1 + .../meters/fronius-smartmeter-via-inverter.mdx | 1 + .../current/devices-next/meters/fronius-solar-api-v1.mdx | 1 + .../devices-next/meters/fronius-symo-gen24-plus.mdx | 1 + .../meters/ginlong-solis-hybrid-inverter-rhi-series.mdx | 1 + .../meters/ginlong-solis-hybrid-inverter-s-series.mdx | 1 + .../devices-next/meters/ginlong-solis-inverter.mdx | 1 + .../current/devices-next/meters/go-e-controller.mdx | 1 + .../meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx | 1 + .../devices-next/meters/goodwe-goodwe-over-wifi.mdx | 1 + .../devices-next/meters/goodwe-sdt-dt-inverter.mdx | 1 + .../devices-next/meters/growatt-hybrid-inverter.mdx | 1 + .../meters/growatt-tl-x-h-hybrid-inverter.mdx | 1 + .../current/devices-next/meters/homematic-ip.mdx | 1 + .../current/devices-next/meters/homewizard-kwh-meter.mdx | 1 + .../devices-next/meters/homewizard-wi-fi-p1-meter.mdx | 1 + .../meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx | 1 + .../meters/hoymiles-hm-and-hms-series-via-opendtu.mdx | 1 + .../current/devices-next/meters/huawei-emma.mdx | 1 + .../current/devices-next/meters/huawei-smartlogger.mdx | 1 + .../devices-next/meters/huawei-sun2000-sdongle.mdx | 1 + .../current/devices-next/meters/huawei-sun2000.mdx | 1 + .../current/devices-next/meters/iammeter-wem3080.mdx | 1 + .../meters/iammeter-wem3080t-wem3046t-wem3050t.mdx | 1 + .../devices-next/meters/igen-tech-solarman-logger.mdx | 1 + .../current/devices-next/meters/index.mdx | 1 + .../current/devices-next/meters/inepro-pro380-mod.mdx | 1 + .../current/devices-next/meters/iometer.mdx | 1 + .../current/devices-next/meters/janitza-b-series.mdx | 1 + .../current/devices-next/meters/janitza-umg-series.mdx | 1 + .../current/devices-next/meters/keba-kecontact-e10.mdx | 1 + .../devices-next/meters/kostal-energy-meter-c-kem-c.mdx | 1 + .../devices-next/meters/kostal-energy-meter-p-kem-p.mdx | 1 + .../current/devices-next/meters/kostal-piko-ba.mdx | 1 + .../current/devices-next/meters/kostal-piko-hybrid.mdx | 1 + .../current/devices-next/meters/kostal-piko-legacy.mdx | 1 + .../current/devices-next/meters/kostal-piko-mp-plus.mdx | 1 + .../current/devices-next/meters/kostal-piko.mdx | 1 + ...re-hybrid-incl-grid-charging-of-the-house-battery.mdx | 1 + .../devices-next/meters/kostal-plenticore-hybrid.mdx | 1 + .../meters/kostal-smart-energy-meter-via-inverter.mdx | 1 + .../devices-next/meters/kostal-smart-energy-meter.mdx | 1 + .../current/devices-next/meters/lg-ess-home-15.mdx | 1 + .../current/devices-next/meters/lg-ess-home-8-10.mdx | 1 + .../current/devices-next/meters/loxone-miniserver.mdx | 1 + .../devices-next/meters/m-tec-energy-butler-gen2.mdx | 1 + .../devices-next/meters/m-tec-energy-butler-gen3.mdx | 1 + .../meters/marstek-venus-battery-storage.mdx | 1 + .../current/devices-next/meters/mhendriks-p1-dongle.mdx | 1 + .../current/devices-next/meters/my-pv-ac-elwa-2.mdx | 1 + .../current/devices-next/meters/my-pv-ac-elwa-e.mdx | 1 + .../current/devices-next/meters/my-pv-ac-thor.mdx | 1 + .../current/devices-next/meters/my-pv-wifi-meter.mdx | 1 + .../current/devices-next/meters/mystrom-switch.mdx | 1 + .../current/devices-next/meters/openems.mdx | 1 + .../current/devices-next/meters/orno-or-we-516.mdx | 1 + .../current/devices-next/meters/orno-or-we-517.mdx | 1 + .../current/devices-next/meters/p1monitor-p1-monitor.mdx | 1 + .../current/devices-next/meters/plexlog.mdx | 1 + .../current/devices-next/meters/powerdog.mdx | 1 + .../current/devices-next/meters/powerfox-poweropti.mdx | 1 + .../devices-next/meters/qcells-hybrid-inverter-cloud.mdx | 1 + .../devices-next/meters/qcells-q-home-ess-hyb-g3.mdx | 1 + .../current/devices-next/meters/rct-power.mdx | 1 + .../meters/saia-burgess-controls-sbc-ale3.mdx | 1 + .../meters/saia-burgess-controls-sbc-awd3.mdx | 1 + .../meters/saj-h1-series-hybrid-solar-inverter.mdx | 1 + .../meters/saj-h2-series-hybrid-solar-inverter.mdx | 1 + .../devices-next/meters/saj-r5-series-solar-inverter.mdx | 1 + .../current/devices-next/meters/sax-homespeicher.mdx | 1 + .../meters/schneider-electric-iem3xxx-modbus.mdx | 1 + .../current/devices-next/meters/senec-home.mdx | 1 + .../meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx | 1 + .../current/devices-next/meters/shelly-1pm-mini.mdx | 1 + .../current/devices-next/meters/shelly-1pm.mdx | 1 + .../current/devices-next/meters/shelly-3em.mdx | 1 + .../current/devices-next/meters/shelly-em.mdx | 1 + .../current/devices-next/meters/shelly-plug-s.mdx | 1 + .../current/devices-next/meters/shelly-pm-mini.mdx | 1 + .../current/devices-next/meters/shelly-pro-1pm.mdx | 1 + .../current/devices-next/meters/shelly-pro-3-em.mdx | 1 + .../meters/shelly-pro-3em-monophase-mode.mdx | 1 + .../current/devices-next/meters/shelly-pro-em.mdx | 1 + .../current/devices-next/meters/siemens-7kt1665.mdx | 1 + .../meters/siemens-junelight-smart-battery.mdx | 1 + .../current/devices-next/meters/siemens-pac-2200.mdx | 1 + ...sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx | 1 + .../current/devices-next/meters/sma-data-manager.mdx | 1 + .../current/devices-next/meters/sma-energy-meter.mdx | 1 + .../devices-next/meters/sma-inverter-speedwire.mdx | 1 + .../meters/sma-smart-energy-hybrid-inverter.mdx | 1 + .../meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx | 1 + .../meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx | 1 + .../devices-next/meters/sma-sunny-home-manager-2-0.mdx | 1 + .../devices-next/meters/sma-sunny-island-modbus.mdx | 1 + .../current/devices-next/meters/sma-webbox.mdx | 1 + .../devices-next/meters/sma-wechselrichter-modbus.mdx | 1 + .../current/devices-next/meters/smartfox-box.mdx | 1 + .../devices-next/meters/smartfox-light-em2-firmware.mdx | 1 + .../current/devices-next/meters/smartfox-pro-2.mdx | 1 + .../current/devices-next/meters/smartfox-pro-light-2.mdx | 1 + .../current/devices-next/meters/smartfox-pro-light.mdx | 1 + .../current/devices-next/meters/smartfox-pro.mdx | 1 + .../devices-next/meters/smartfox-reg-extended.mdx | 1 + .../current/devices-next/meters/smartfox-reg.mdx | 1 + .../devices-next/meters/sofarsolar-hybrid-inverter.mdx | 1 + .../devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx | 1 + .../devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx | 1 + .../current/devices-next/meters/sofarsolar-inverter.mdx | 1 + .../devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx | 1 + .../devices-next/meters/sofarsolar-sofar-80-136ktl.mdx | 1 + .../devices-next/meters/solaranzeige-solaranzeige.mdx | 1 + .../devices-next/meters/solaredge-hybrid-inverter.mdx | 1 + .../current/devices-next/meters/solaredge-inverter.mdx | 1 + .../current/devices-next/meters/solarlog.mdx | 1 + .../meters/solarmax-max-storage-max-storage-ultimate.mdx | 1 + .../devices-next/meters/solarmax-solarmax-smt.mdx | 1 + .../devices-next/meters/solarmax-sp-series-inverter.mdx | 1 + .../devices-next/meters/solarwatt-energymanager-pro.mdx | 1 + .../devices-next/meters/solarwatt-energymanager.mdx | 1 + .../devices-next/meters/solarwatt-manager-flex.mdx | 1 + .../solarwatt-myreserve-matrix-lan-oder-powergateway.mdx | 1 + .../current/devices-next/meters/solarwatt-myreserve.mdx | 1 + .../devices-next/meters/solax-hybrid-inverter-cloud.mdx | 1 + .../devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx | 1 + .../current/devices-next/meters/solax-inverter-cloud.mdx | 1 + .../current/devices-next/meters/solinteng.mdx | 1 + .../current/devices-next/meters/sonnen-comfort.mdx | 1 + .../current/devices-next/meters/sonnen-eco-5.mdx | 1 + .../current/devices-next/meters/sonnen-eco-6.mdx | 1 + .../current/devices-next/meters/sonnen-oem-6-5.mdx | 1 + .../devices-next/meters/sonnen-sonnenbatterie.mdx | 1 + .../current/devices-next/meters/st-ems.mdx | 1 + .../current/devices-next/meters/steca-coolcept-flex.mdx | 1 + .../devices-next/meters/sungrow-sg-series-inverter.mdx | 1 + .../meters/sungrow-sh-series-hybrid-inverter.mdx | 1 + .../devices-next/meters/sunspec-battery-model-124.mdx | 1 + .../devices-next/meters/sunspec-battery-model-802.mdx | 1 + .../devices-next/meters/sunspec-hybrid-inverter.mdx | 1 + .../current/devices-next/meters/sunspec-inverter.mdx | 1 + .../current/devices-next/meters/sunspec-meter.mdx | 1 + .../devices-next/meters/sunsynk-3p-hybrid-inverter.mdx | 1 + .../devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx | 1 + .../devices-next/meters/sunsynk-micro-inverter.mdx | 1 + .../meters/sunsynk-storage-hybrid-inverter.mdx | 1 + .../devices-next/meters/sunsynk-string-inverter.mdx | 1 + .../current/devices-next/meters/sunway.mdx | 1 + .../tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx | 1 + .../meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx | 1 + .../current/devices-next/meters/tasmota-three-phase.mdx | 1 + .../current/devices-next/meters/tesla-powerwall.mdx | 1 + .../current/devices-next/meters/tibber-pulse.mdx | 1 + .../devices-next/meters/tp-link-h-series-smart-plug.mdx | 1 + .../meters/tp-link-tapo-p-series-smart-plug.mdx | 1 + .../meters/tq-energy-manager-em2xx-em3xx.mdx | 1 + .../devices-next/meters/tq-energy-manager-em420.mdx | 1 + .../current/devices-next/meters/varta-element.mdx | 1 + .../current/devices-next/meters/varta-pulse-neo.mdx | 1 + .../current/devices-next/meters/varta-pulse.mdx | 1 + .../current/devices-next/meters/victron-em24.mdx | 1 + .../current/devices-next/meters/victron-em24_e1.mdx | 1 + .../current/devices-next/meters/victron-em530-em540.mdx | 1 + .../current/devices-next/meters/victron-energy.mdx | 1 + .../current/devices-next/meters/victron-et340.mdx | 1 + .../meters/volkszahler-http-api-import-and-export.mdx | 1 + .../current/devices-next/meters/volkszahler-http-api.mdx | 1 + .../devices-next/meters/volkszahler-websocket-api.mdx | 1 + .../current/devices-next/meters/vzlogger.mdx | 1 + .../current/devices-next/meters/wago-879-30xx.mdx | 1 + .../current/devices-next/meters/wattsonic.mdx | 1 + .../devices-next/meters/weidmuller-em110-rtu-2p.mdx | 1 + .../devices-next/meters/weidmuller-em111-rtu-2p.mdx | 1 + .../devices-next/meters/weidmuller-em120-rtu-2p.mdx | 1 + .../devices-next/meters/weidmuller-em122-rtu-2p.mdx | 1 + .../devices-next/meters/youless-energy-monitor.mdx | 1 + .../devices-next/meters/zcs-azzurro-hybrid-inverter.mdx | 1 + .../current/devices-next/meters/zcs-azzurro-inverter.mdx | 1 + .../current/devices-next/meters/zendure-hyper-2000.mdx | 1 + .../meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx | 1 + .../devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx | 1 + .../devices-next/meters/zuidwijk-slimmelezer-plus.mdx | 1 + .../current/devices-next/tariffs/amber-electric.mdx | 1 + .../current/devices-next/tariffs/awattar.mdx | 1 + .../tariffs/electricity-maps-commercial-api.mdx | 1 + .../devices-next/tariffs/electricity-maps-free-api.mdx | 1 + .../current/devices-next/tariffs/energinet.mdx | 1 + .../current/devices-next/tariffs/enever.mdx | 1 + .../current/devices-next/tariffs/entso-e.mdx | 1 + .../current/devices-next/tariffs/forecast-solar.mdx | 1 + .../current/devices-next/tariffs/fraunhofer-ise.mdx | 1 + .../current/devices-next/tariffs/green-grid-compass.mdx | 1 + .../current/devices-next/tariffs/groupe-e-vario-plus.mdx | 1 + .../current/devices-next/tariffs/grunstromindex.mdx | 1 + .../current/devices-next/tariffs/index.mdx | 1 + .../current/devices-next/tariffs/national-grid-eso.mdx | 1 + .../devices-next/tariffs/nordpool-spot-prices.mdx | 1 + .../current/devices-next/tariffs/octopus-energy-api.mdx | 1 + .../devices-next/tariffs/octopus-energy-product-code.mdx | 1 + .../current/devices-next/tariffs/open-meteo.mdx | 1 + .../current/devices-next/tariffs/ostrom.mdx | 1 + .../current/devices-next/tariffs/pun-orario.mdx | 1 + .../devices-next/tariffs/smartenergy-smartcontrol.mdx | 1 + .../current/devices-next/tariffs/solcast.mdx | 1 + .../current/devices-next/tariffs/spotty-energie.mdx | 1 + .../current/devices-next/tariffs/tibber.mdx | 1 + .../devices-next/tariffs/victron-vrm-solar-forecast.mdx | 1 + .../current/devices-next/vehicles/aiways.mdx | 1 + .../current/devices-next/vehicles/audi.mdx | 1 + .../current/devices-next/vehicles/bmw.mdx | 1 + .../current/devices-next/vehicles/citroen.mdx | 1 + .../current/devices-next/vehicles/dacia.mdx | 1 + .../current/devices-next/vehicles/ds.mdx | 1 + .../current/devices-next/vehicles/evnotify.mdx | 1 + .../current/devices-next/vehicles/fiat.mdx | 1 + .../current/devices-next/vehicles/ford.mdx | 1 + .../vehicles/generic-vehicle-without-api.mdx | 1 + .../current/devices-next/vehicles/hyundai-bluelink.mdx | 1 + .../current/devices-next/vehicles/index.mdx | 1 + .../current/devices-next/vehicles/iobroker-bmw.mdx | 1 + .../current/devices-next/vehicles/iso15118.mdx | 1 + .../current/devices-next/vehicles/jeep.mdx | 1 + .../current/devices-next/vehicles/kia-bluelink.mdx | 1 + .../current/devices-next/vehicles/mercedes-benz.mdx | 1 + .../current/devices-next/vehicles/mg.mdx | 1 + .../current/devices-next/vehicles/mg2mqtt.mdx | 1 + .../current/devices-next/vehicles/mini.mdx | 1 + .../current/devices-next/vehicles/mz2mqtt.mdx | 1 + .../current/devices-next/vehicles/nissan-ariya.mdx | 1 + .../devices-next/vehicles/nissan-leaf-pre-2019.mdx | 1 + .../current/devices-next/vehicles/nissan-leaf.mdx | 1 + .../current/devices-next/vehicles/niu-e-scooter.mdx | 1 + .../current/devices-next/vehicles/opel.mdx | 1 + .../vehicles/open-vehicle-monitoring-system.mdx | 1 + .../current/devices-next/vehicles/peugeot.mdx | 1 + .../current/devices-next/vehicles/polestar.mdx | 1 + .../current/devices-next/vehicles/psa-car-controller.mdx | 1 + .../current/devices-next/vehicles/renault.mdx | 1 + ...at-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx | 1 + .../seat-cupraconnect-gen4-born-formentor-tavascan.mdx | 1 + .../current/devices-next/vehicles/skoda-enyaq.mdx | 1 + .../current/devices-next/vehicles/smart-1.mdx | 1 + .../current/devices-next/vehicles/smart-eq.mdx | 1 + .../current/devices-next/vehicles/tesla-ble.mdx | 1 + .../current/devices-next/vehicles/tesla.mdx | 1 + .../current/devices-next/vehicles/teslalogger.mdx | 1 + .../current/devices-next/vehicles/teslamate.mdx | 1 + .../current/devices-next/vehicles/tessie.mdx | 1 + .../current/devices-next/vehicles/toyota.mdx | 1 + .../current/devices-next/vehicles/tronity.mdx | 1 + .../devices-next/vehicles/volkswagen-we-connect-id.mdx | 1 + .../current/devices-next/vehicles/volvo.mdx | 1 + .../current/devices-next/vehicles/volvo2mqtt.mdx | 1 + .../current/devices-next/vehicles/zero-motorcycles.mdx | 1 + sidebars.js | 2 +- src/css/custom.css | 9 +++++++++ src/generateDevicesNext.ts | 2 ++ 1179 files changed, 1188 insertions(+), 1 deletion(-) diff --git a/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx b/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx index c207444d09..60be96ea34 100644 --- a/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx +++ b/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -2,6 +2,7 @@ title: ABB Terra AC (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abb-terra-ac.mdx b/docs/devices-next/chargers/abb-terra-ac.mdx index 5d7df7d230..8e72560233 100644 --- a/docs/devices-next/chargers/abb-terra-ac.mdx +++ b/docs/devices-next/chargers/abb-terra-ac.mdx @@ -2,6 +2,7 @@ title: ABB Terra AC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-em4-single-ocpp.mdx b/docs/devices-next/chargers/abl-em4-single-ocpp.mdx index aa1e225117..52b0e9764f 100644 --- a/docs/devices-next/chargers/abl-em4-single-ocpp.mdx +++ b/docs/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Single (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-em4-single-sbcx.mdx b/docs/devices-next/chargers/abl-em4-single-sbcx.mdx index 619b44735f..bcf4875afa 100644 --- a/docs/devices-next/chargers/abl-em4-single-sbcx.mdx +++ b/docs/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Single (SBCx) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx b/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx index 01c60fb005..a436258836 100644 --- a/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx +++ b/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Twin (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx b/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx index bbaa775fa2..d2d0b0e47c 100644 --- a/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx +++ b/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Twin (SBCx) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-emh1.mdx b/docs/devices-next/chargers/abl-emh1.mdx index 06e9d7a6d8..83fc283b91 100644 --- a/docs/devices-next/chargers/abl-emh1.mdx +++ b/docs/devices-next/chargers/abl-emh1.mdx @@ -2,6 +2,7 @@ title: ABL eMH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-emh2-ocpp.mdx b/docs/devices-next/chargers/abl-emh2-ocpp.mdx index d89cc30e2b..bb41536cee 100644 --- a/docs/devices-next/chargers/abl-emh2-ocpp.mdx +++ b/docs/devices-next/chargers/abl-emh2-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eMH2 (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-emh2.mdx b/docs/devices-next/chargers/abl-emh2.mdx index 23fff9bef2..a6f929ada3 100644 --- a/docs/devices-next/chargers/abl-emh2.mdx +++ b/docs/devices-next/chargers/abl-emh2.mdx @@ -2,6 +2,7 @@ title: ABL eMH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/abl-emh3-ocpp.mdx b/docs/devices-next/chargers/abl-emh3-ocpp.mdx index ef917c67c4..b66a416479 100644 --- a/docs/devices-next/chargers/abl-emh3-ocpp.mdx +++ b/docs/devices-next/chargers/abl-emh3-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eMH3 (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/alfen-eve-ocpp.mdx b/docs/devices-next/chargers/alfen-eve-ocpp.mdx index 6cafdc100f..a1c81b858a 100644 --- a/docs/devices-next/chargers/alfen-eve-ocpp.mdx +++ b/docs/devices-next/chargers/alfen-eve-ocpp.mdx @@ -2,6 +2,7 @@ title: Alfen Eve (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/alfen-eve.mdx b/docs/devices-next/chargers/alfen-eve.mdx index 58c1138c1d..9de797d0e8 100644 --- a/docs/devices-next/chargers/alfen-eve.mdx +++ b/docs/devices-next/chargers/alfen-eve.mdx @@ -2,6 +2,7 @@ title: Alfen Eve custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alfen.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/alpha-innotec.mdx b/docs/devices-next/chargers/alpha-innotec.mdx index 24b2ef820d..72674e9ba1 100644 --- a/docs/devices-next/chargers/alpha-innotec.mdx +++ b/docs/devices-next/chargers/alpha-innotec.mdx @@ -2,6 +2,7 @@ title: alpha innotec custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx index 18ae9888ce..9a12b61cd4 100644 --- a/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx +++ b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -2,6 +2,7 @@ title: Alphatec Ladesäule Twin custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/alphatec-wallbox-mini.mdx b/docs/devices-next/chargers/alphatec-wallbox-mini.mdx index 056e41c29c..722f405eb8 100644 --- a/docs/devices-next/chargers/alphatec-wallbox-mini.mdx +++ b/docs/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -2,6 +2,7 @@ title: Alphatec Wallbox Mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/alphatec-wallbox-power.mdx b/docs/devices-next/chargers/alphatec-wallbox-power.mdx index f6ae0bb6c6..ded259ea82 100644 --- a/docs/devices-next/chargers/alphatec-wallbox-power.mdx +++ b/docs/devices-next/chargers/alphatec-wallbox-power.mdx @@ -2,6 +2,7 @@ title: Alphatec Wallbox Power custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx index e0f7823780..df9e946a24 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox connect.business custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx index 019bf3680d..f350300845 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox connect.home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx b/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx index d08f71244b..eb0bf2a49d 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox connect.solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx index 5a1575e4bd..66059a3826 100644 --- a/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx +++ b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ampure-next.mdx b/docs/devices-next/chargers/ampure-next.mdx index 66c5256bea..ba167b1d61 100644 --- a/docs/devices-next/chargers/ampure-next.mdx +++ b/docs/devices-next/chargers/ampure-next.mdx @@ -2,6 +2,7 @@ title: Ampure NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ampure-unite.mdx b/docs/devices-next/chargers/ampure-unite.mdx index 22e2090dcc..d76470da1d 100644 --- a/docs/devices-next/chargers/ampure-unite.mdx +++ b/docs/devices-next/chargers/ampure-unite.mdx @@ -2,6 +2,7 @@ title: Ampure Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/audi-wallbox-plus.mdx b/docs/devices-next/chargers/audi-wallbox-plus.mdx index 1550e79233..2f8efc24b2 100644 --- a/docs/devices-next/chargers/audi-wallbox-plus.mdx +++ b/docs/devices-next/chargers/audi-wallbox-plus.mdx @@ -2,6 +2,7 @@ title: Audi Wallbox plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/audi-wallbox-pro.mdx b/docs/devices-next/chargers/audi-wallbox-pro.mdx index 63a7479c93..26d8b7824f 100644 --- a/docs/devices-next/chargers/audi-wallbox-pro.mdx +++ b/docs/devices-next/chargers/audi-wallbox-pro.mdx @@ -2,6 +2,7 @@ title: Audi Wallbox pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/autel-ac-compact.mdx b/docs/devices-next/chargers/autel-ac-compact.mdx index e163800445..742306ff62 100644 --- a/docs/devices-next/chargers/autel-ac-compact.mdx +++ b/docs/devices-next/chargers/autel-ac-compact.mdx @@ -2,6 +2,7 @@ title: AUTEL AC Compact custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/autel-ac-maxicharger.mdx b/docs/devices-next/chargers/autel-ac-maxicharger.mdx index ae3dcfae90..925ef26b6f 100644 --- a/docs/devices-next/chargers/autel-ac-maxicharger.mdx +++ b/docs/devices-next/chargers/autel-ac-maxicharger.mdx @@ -2,6 +2,7 @@ title: AUTEL AC MaxiCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/autoaid-business-wallbox.mdx b/docs/devices-next/chargers/autoaid-business-wallbox.mdx index 4df185c4e9..666bef2c79 100644 --- a/docs/devices-next/chargers/autoaid-business-wallbox.mdx +++ b/docs/devices-next/chargers/autoaid-business-wallbox.mdx @@ -2,6 +2,7 @@ title: Autoaid Business Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx index 563a5d04a5..1973533d1e 100644 --- a/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx +++ b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -2,6 +2,7 @@ title: Autoaid Intelligent Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/avm-fritzdect.mdx b/docs/devices-next/chargers/avm-fritzdect.mdx index d8286b2edf..d09bf01d4c 100644 --- a/docs/devices-next/chargers/avm-fritzdect.mdx +++ b/docs/devices-next/chargers/avm-fritzdect.mdx @@ -2,6 +2,7 @@ title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/fritzdect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/bender-cc612.mdx b/docs/devices-next/chargers/bender-cc612.mdx index 596a177a65..d4790df516 100644 --- a/docs/devices-next/chargers/bender-cc612.mdx +++ b/docs/devices-next/chargers/bender-cc612.mdx @@ -2,6 +2,7 @@ title: Bender CC612 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/bender-cc613.mdx b/docs/devices-next/chargers/bender-cc613.mdx index 42d6ec21ca..e97d16a6ef 100644 --- a/docs/devices-next/chargers/bender-cc613.mdx +++ b/docs/devices-next/chargers/bender-cc613.mdx @@ -2,6 +2,7 @@ title: Bender CC613 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/bender-icc1314.mdx b/docs/devices-next/chargers/bender-icc1314.mdx index 7a6eac5f7c..238fd077b4 100644 --- a/docs/devices-next/chargers/bender-icc1314.mdx +++ b/docs/devices-next/chargers/bender-icc1314.mdx @@ -2,6 +2,7 @@ title: Bender ICC1314 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/bender-icc1324.mdx b/docs/devices-next/chargers/bender-icc1324.mdx index f120728021..df7f6adec7 100644 --- a/docs/devices-next/chargers/bender-icc1324.mdx +++ b/docs/devices-next/chargers/bender-icc1324.mdx @@ -2,6 +2,7 @@ title: Bender ICC1324 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/bmw-i-wallbox.mdx b/docs/devices-next/chargers/bmw-i-wallbox.mdx index 3c01e87ef7..dc43e78d69 100644 --- a/docs/devices-next/chargers/bmw-i-wallbox.mdx +++ b/docs/devices-next/chargers/bmw-i-wallbox.mdx @@ -2,6 +2,7 @@ title: BMW i Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/bosch-sg-ready.mdx b/docs/devices-next/chargers/bosch-sg-ready.mdx index abc528da35..3b82360bea 100644 --- a/docs/devices-next/chargers/bosch-sg-ready.mdx +++ b/docs/devices-next/chargers/bosch-sg-ready.mdx @@ -2,6 +2,7 @@ title: Bosch SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/bosch-x-change.mdx b/docs/devices-next/chargers/bosch-x-change.mdx index f35810a642..d1cf43665f 100644 --- a/docs/devices-next/chargers/bosch-x-change.mdx +++ b/docs/devices-next/chargers/bosch-x-change.mdx @@ -2,6 +2,7 @@ title: Bösch x-change custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx b/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx index e8759cca1a..75fb04d2bc 100644 --- a/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -2,6 +2,7 @@ title: Buderus Logamatic HMC 20 Z custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx b/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx index 1ee7c8309a..49bb5b3156 100644 --- a/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -2,6 +2,7 @@ title: Buderus Logamatic HMC 20 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/buderus-sg-ready.mdx b/docs/devices-next/chargers/buderus-sg-ready.mdx index e01b55a4d8..03269f36ac 100644 --- a/docs/devices-next/chargers/buderus-sg-ready.mdx +++ b/docs/devices-next/chargers/buderus-sg-ready.mdx @@ -2,6 +2,7 @@ title: Buderus SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cfos-power-brain-solar.mdx b/docs/devices-next/chargers/cfos-power-brain-solar.mdx index 1d5547fe56..3b28e8d052 100644 --- a/docs/devices-next/chargers/cfos-power-brain-solar.mdx +++ b/docs/devices-next/chargers/cfos-power-brain-solar.mdx @@ -2,6 +2,7 @@ title: cFos Power Brain Solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cfos-power-brain.mdx b/docs/devices-next/chargers/cfos-power-brain.mdx index a699759914..0673ffce63 100644 --- a/docs/devices-next/chargers/cfos-power-brain.mdx +++ b/docs/devices-next/chargers/cfos-power-brain.mdx @@ -2,6 +2,7 @@ title: cFos Power Brain custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/charge-amps-halo.mdx b/docs/devices-next/chargers/charge-amps-halo.mdx index 16547a6053..f19b666519 100644 --- a/docs/devices-next/chargers/charge-amps-halo.mdx +++ b/docs/devices-next/chargers/charge-amps-halo.mdx @@ -2,6 +2,7 @@ title: Charge Amps Halo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-chargeamps.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/compleo-ebox.mdx b/docs/devices-next/chargers/compleo-ebox.mdx index 4fdd8cb101..f361056bb0 100644 --- a/docs/devices-next/chargers/compleo-ebox.mdx +++ b/docs/devices-next/chargers/compleo-ebox.mdx @@ -2,6 +2,7 @@ title: Compleo eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx b/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx index cb02000da5..58b229a281 100644 --- a/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx +++ b/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -2,6 +2,7 @@ title: CTA All-In-One Aeroplus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cubos-c11e.mdx b/docs/devices-next/chargers/cubos-c11e.mdx index 70908a7f2f..5b5b7f6f4b 100644 --- a/docs/devices-next/chargers/cubos-c11e.mdx +++ b/docs/devices-next/chargers/cubos-c11e.mdx @@ -2,6 +2,7 @@ title: CUBOS C11E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cubos-c22e.mdx b/docs/devices-next/chargers/cubos-c22e.mdx index ee423598af..88e84f5b37 100644 --- a/docs/devices-next/chargers/cubos-c22e.mdx +++ b/docs/devices-next/chargers/cubos-c22e.mdx @@ -2,6 +2,7 @@ title: CUBOS C22E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cupra-charger-connect-2.mdx b/docs/devices-next/chargers/cupra-charger-connect-2.mdx index 30ab77ec2d..4fa2bab616 100644 --- a/docs/devices-next/chargers/cupra-charger-connect-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-connect-2.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cupra-charger-connect.mdx b/docs/devices-next/chargers/cupra-charger-connect.mdx index 989510a5ce..023182bde2 100644 --- a/docs/devices-next/chargers/cupra-charger-connect.mdx +++ b/docs/devices-next/chargers/cupra-charger-connect.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cupra-charger-pro-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-2.mdx index 5ac13c3577..c91a846114 100644 --- a/docs/devices-next/chargers/cupra-charger-pro-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro-2.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx index a44de36579..df315d2943 100644 --- a/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/cupra-charger-pro.mdx b/docs/devices-next/chargers/cupra-charger-pro.mdx index 8bc66dd45d..96e72d97f8 100644 --- a/docs/devices-next/chargers/cupra-charger-pro.mdx +++ b/docs/devices-next/chargers/cupra-charger-pro.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/dadapower-premium-wallbox.mdx b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx index 3da55d93d6..034e39fb84 100644 --- a/docs/devices-next/chargers/dadapower-premium-wallbox.mdx +++ b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -2,6 +2,7 @@ title: Dadapower Premium Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/dadapower.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/daheimladen-wallbox.mdx b/docs/devices-next/chargers/daheimladen-wallbox.mdx index 4211393b48..5fd562df43 100644 --- a/docs/devices-next/chargers/daheimladen-wallbox.mdx +++ b/docs/devices-next/chargers/daheimladen-wallbox.mdx @@ -2,6 +2,7 @@ title: DaheimLaden Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daheimladen-mb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx index 27ca6dd03d..fdda9e4b4c 100644 --- a/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx +++ b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -2,6 +2,7 @@ title: Daikin HomeHub (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daikin-homehub.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/delta-ac-max-basic.mdx b/docs/devices-next/chargers/delta-ac-max-basic.mdx index 0be6734cf8..735e5ff24e 100644 --- a/docs/devices-next/chargers/delta-ac-max-basic.mdx +++ b/docs/devices-next/chargers/delta-ac-max-basic.mdx @@ -2,6 +2,7 @@ title: Delta AC Max Basic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/delta-ac-max-smart.mdx b/docs/devices-next/chargers/delta-ac-max-smart.mdx index ea40457e09..80351850d2 100644 --- a/docs/devices-next/chargers/delta-ac-max-smart.mdx +++ b/docs/devices-next/chargers/delta-ac-max-smart.mdx @@ -2,6 +2,7 @@ title: Delta AC MAX Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/delta-slim-charger.mdx b/docs/devices-next/chargers/delta-slim-charger.mdx index 7202fa9d9a..15e80918fd 100644 --- a/docs/devices-next/chargers/delta-slim-charger.mdx +++ b/docs/devices-next/chargers/delta-slim-charger.mdx @@ -2,6 +2,7 @@ title: Delta SLIM Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/delta-ultra-fast-charger.mdx b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx index b2d9e473a4..ad5af23764 100644 --- a/docs/devices-next/chargers/delta-ultra-fast-charger.mdx +++ b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -2,6 +2,7 @@ title: Delta Ultra Fast Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/demo-charger.mdx b/docs/devices-next/chargers/demo-charger.mdx index 7fd3a0a700..fdd553e7ce 100644 --- a/docs/devices-next/chargers/demo-charger.mdx +++ b/docs/devices-next/chargers/demo-charger.mdx @@ -2,6 +2,7 @@ title: Demo charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/demo-charger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/e-on-drive-ebox.mdx b/docs/devices-next/chargers/e-on-drive-ebox.mdx index 7a5b22206f..f21e85ea70 100644 --- a/docs/devices-next/chargers/e-on-drive-ebox.mdx +++ b/docs/devices-next/chargers/e-on-drive-ebox.mdx @@ -2,6 +2,7 @@ title: E.ON Drive eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/e-on-drive-vbox.mdx b/docs/devices-next/chargers/e-on-drive-vbox.mdx index 2ce06571f0..a9d38b447f 100644 --- a/docs/devices-next/chargers/e-on-drive-vbox.mdx +++ b/docs/devices-next/chargers/e-on-drive-vbox.mdx @@ -2,6 +2,7 @@ title: E.ON Drive vBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/e3-dc-easy-connect.mdx b/docs/devices-next/chargers/e3-dc-easy-connect.mdx index ae687d5e1b..875c7ba217 100644 --- a/docs/devices-next/chargers/e3-dc-easy-connect.mdx +++ b/docs/devices-next/chargers/e3-dc-easy-connect.mdx @@ -2,6 +2,7 @@ title: E3/DC Easy Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/easee-charge-core.mdx b/docs/devices-next/chargers/easee-charge-core.mdx index 09ed4394fe..640283b97e 100644 --- a/docs/devices-next/chargers/easee-charge-core.mdx +++ b/docs/devices-next/chargers/easee-charge-core.mdx @@ -2,6 +2,7 @@ title: Easee Charge Core custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/easee-charge-lite.mdx b/docs/devices-next/chargers/easee-charge-lite.mdx index 848a0a9617..9281f67ede 100644 --- a/docs/devices-next/chargers/easee-charge-lite.mdx +++ b/docs/devices-next/chargers/easee-charge-lite.mdx @@ -2,6 +2,7 @@ title: Easee Charge Lite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/easee-charge.mdx b/docs/devices-next/chargers/easee-charge.mdx index 3bfff7bc18..b100563943 100644 --- a/docs/devices-next/chargers/easee-charge.mdx +++ b/docs/devices-next/chargers/easee-charge.mdx @@ -2,6 +2,7 @@ title: Easee Charge custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/easee-home.mdx b/docs/devices-next/chargers/easee-home.mdx index 3f80d94390..4a1fe3c301 100644 --- a/docs/devices-next/chargers/easee-home.mdx +++ b/docs/devices-next/chargers/easee-home.mdx @@ -2,6 +2,7 @@ title: Easee Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ebee-wallbox.mdx b/docs/devices-next/chargers/ebee-wallbox.mdx index 5d02827758..66b83e51a6 100644 --- a/docs/devices-next/chargers/ebee-wallbox.mdx +++ b/docs/devices-next/chargers/ebee-wallbox.mdx @@ -2,6 +2,7 @@ title: Ebee Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/echarge-cph1.mdx b/docs/devices-next/chargers/echarge-cph1.mdx index 82d76b7d51..bfa1f689d0 100644 --- a/docs/devices-next/chargers/echarge-cph1.mdx +++ b/docs/devices-next/chargers/echarge-cph1.mdx @@ -2,6 +2,7 @@ title: echarge cPH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/echarge-cph2.mdx b/docs/devices-next/chargers/echarge-cph2.mdx index b636f7fb83..afb92ecabf 100644 --- a/docs/devices-next/chargers/echarge-cph2.mdx +++ b/docs/devices-next/chargers/echarge-cph2.mdx @@ -2,6 +2,7 @@ title: echarge cPH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/echarge-cpm2.mdx b/docs/devices-next/chargers/echarge-cpm2.mdx index edfccf903c..4ee3d8e0a7 100644 --- a/docs/devices-next/chargers/echarge-cpm2.mdx +++ b/docs/devices-next/chargers/echarge-cpm2.mdx @@ -2,6 +2,7 @@ title: echarge cPμ2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx b/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx index 0585d3648e..2074d3283c 100644 --- a/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx +++ b/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -2,6 +2,7 @@ title: EcoHarmony EVSE EPC 2.0 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/edgetech-smart-evse.mdx b/docs/devices-next/chargers/edgetech-smart-evse.mdx index 7b8d59de3f..4657d6d47d 100644 --- a/docs/devices-next/chargers/edgetech-smart-evse.mdx +++ b/docs/devices-next/chargers/edgetech-smart-evse.mdx @@ -2,6 +2,7 @@ title: Edgetech Smart EVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartevse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/eebus-compatible.mdx b/docs/devices-next/chargers/eebus-compatible.mdx index 7a65ff5f53..5364b67684 100644 --- a/docs/devices-next/chargers/eebus-compatible.mdx +++ b/docs/devices-next/chargers/eebus-compatible.mdx @@ -2,6 +2,7 @@ title: EEBUS compatible custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eebus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elco.mdx b/docs/devices-next/chargers/elco.mdx index 0e31e2b41d..d15f05119c 100644 --- a/docs/devices-next/chargers/elco.mdx +++ b/docs/devices-next/chargers/elco.mdx @@ -2,6 +2,7 @@ title: Elco custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elecq-biz.mdx b/docs/devices-next/chargers/elecq-biz.mdx index 8269dfea42..0e30190af8 100644 --- a/docs/devices-next/chargers/elecq-biz.mdx +++ b/docs/devices-next/chargers/elecq-biz.mdx @@ -2,6 +2,7 @@ title: Elecq Biz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elecq-home.mdx b/docs/devices-next/chargers/elecq-home.mdx index ac97483875..ce45e09f93 100644 --- a/docs/devices-next/chargers/elecq-home.mdx +++ b/docs/devices-next/chargers/elecq-home.mdx @@ -2,6 +2,7 @@ title: Elecq Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elecq-station.mdx b/docs/devices-next/chargers/elecq-station.mdx index 06aa971bfa..16b99fe07d 100644 --- a/docs/devices-next/chargers/elecq-station.mdx +++ b/docs/devices-next/chargers/elecq-station.mdx @@ -2,6 +2,7 @@ title: Elecq Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/eledio-go.mdx b/docs/devices-next/chargers/eledio-go.mdx index 478c3e9074..90d8681e26 100644 --- a/docs/devices-next/chargers/eledio-go.mdx +++ b/docs/devices-next/chargers/eledio-go.mdx @@ -2,6 +2,7 @@ title: eledio go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elli-charger-connect-2.mdx b/docs/devices-next/chargers/elli-charger-connect-2.mdx index 6ec54ff0b7..9ac9b7eafb 100644 --- a/docs/devices-next/chargers/elli-charger-connect-2.mdx +++ b/docs/devices-next/chargers/elli-charger-connect-2.mdx @@ -2,6 +2,7 @@ title: Elli Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elli-charger-connect.mdx b/docs/devices-next/chargers/elli-charger-connect.mdx index 6d466b3821..55b20fb33b 100644 --- a/docs/devices-next/chargers/elli-charger-connect.mdx +++ b/docs/devices-next/chargers/elli-charger-connect.mdx @@ -2,6 +2,7 @@ title: Elli Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elli-charger-pro-2.mdx b/docs/devices-next/chargers/elli-charger-pro-2.mdx index a5bb341a84..8774f9cb1b 100644 --- a/docs/devices-next/chargers/elli-charger-pro-2.mdx +++ b/docs/devices-next/chargers/elli-charger-pro-2.mdx @@ -2,6 +2,7 @@ title: Elli Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx index 363ccfc913..81bfab39d7 100644 --- a/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -2,6 +2,7 @@ title: Elli Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/elli-charger-pro.mdx b/docs/devices-next/chargers/elli-charger-pro.mdx index 22d7801e35..1510d23b41 100644 --- a/docs/devices-next/chargers/elli-charger-pro.mdx +++ b/docs/devices-next/chargers/elli-charger-pro.mdx @@ -2,6 +2,7 @@ title: Elli Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/em2go-home.mdx b/docs/devices-next/chargers/em2go-home.mdx index a752a6f523..9b1386eb2c 100644 --- a/docs/devices-next/chargers/em2go-home.mdx +++ b/docs/devices-next/chargers/em2go-home.mdx @@ -2,6 +2,7 @@ title: EM2GO Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go-home.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx b/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx index c7b5cfc074..16dd03fb38 100644 --- a/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx +++ b/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -2,6 +2,7 @@ title: EM2GO Pro Power (OCPP/ONC) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/enercab-smart.mdx b/docs/devices-next/chargers/enercab-smart.mdx index b91e729816..fba830a354 100644 --- a/docs/devices-next/chargers/enercab-smart.mdx +++ b/docs/devices-next/chargers/enercab-smart.mdx @@ -2,6 +2,7 @@ title: enercab smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/enplus-ac-ev-charger.mdx b/docs/devices-next/chargers/enplus-ac-ev-charger.mdx index da0518c07c..a54f60ce1c 100644 --- a/docs/devices-next/chargers/enplus-ac-ev-charger.mdx +++ b/docs/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -2,6 +2,7 @@ title: EN+ AC EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ensto-chago-wallbox.mdx b/docs/devices-next/chargers/ensto-chago-wallbox.mdx index 80b9a86f6c..bdd7dcfdca 100644 --- a/docs/devices-next/chargers/ensto-chago-wallbox.mdx +++ b/docs/devices-next/chargers/ensto-chago-wallbox.mdx @@ -2,6 +2,7 @@ title: Ensto Chago Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/entratek-power-dot-fix.mdx b/docs/devices-next/chargers/entratek-power-dot-fix.mdx index 7846ca8356..46fb1a546c 100644 --- a/docs/devices-next/chargers/entratek-power-dot-fix.mdx +++ b/docs/devices-next/chargers/entratek-power-dot-fix.mdx @@ -2,6 +2,7 @@ title: EntraTek Power Dot Fix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx index c89da73200..71d8a749fd 100644 --- a/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx +++ b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -2,6 +2,7 @@ title: EntraTek Power Dot Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/esl-walli-light.mdx b/docs/devices-next/chargers/esl-walli-light.mdx index 02bd45981d..95b0af1985 100644 --- a/docs/devices-next/chargers/esl-walli-light.mdx +++ b/docs/devices-next/chargers/esl-walli-light.mdx @@ -2,6 +2,7 @@ title: ESL Walli LIGHT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/esystems-ghostone.mdx b/docs/devices-next/chargers/esystems-ghostone.mdx index 40b59171fd..656f480c48 100644 --- a/docs/devices-next/chargers/esystems-ghostone.mdx +++ b/docs/devices-next/chargers/esystems-ghostone.mdx @@ -2,6 +2,7 @@ title: eSystems ghostONE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/etrel-inch-duo.mdx b/docs/devices-next/chargers/etrel-inch-duo.mdx index bbfc3ce3dc..1abb809dec 100644 --- a/docs/devices-next/chargers/etrel-inch-duo.mdx +++ b/docs/devices-next/chargers/etrel-inch-duo.mdx @@ -2,6 +2,7 @@ title: Etrel INCH Duo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel-duo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/etrel-inch.mdx b/docs/devices-next/chargers/etrel-inch.mdx index e430efacf6..3fcfaa1a80 100644 --- a/docs/devices-next/chargers/etrel-inch.mdx +++ b/docs/devices-next/chargers/etrel-inch.mdx @@ -2,6 +2,7 @@ title: Etrel INCH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/evbox-elvi.mdx b/docs/devices-next/chargers/evbox-elvi.mdx index b474d1664b..a1725cf342 100644 --- a/docs/devices-next/chargers/evbox-elvi.mdx +++ b/docs/devices-next/chargers/evbox-elvi.mdx @@ -2,6 +2,7 @@ title: EVBox Elvi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-evbox-elvi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/evbox-livo.mdx b/docs/devices-next/chargers/evbox-livo.mdx index 9db3e05714..c051a79be8 100644 --- a/docs/devices-next/chargers/evbox-livo.mdx +++ b/docs/devices-next/chargers/evbox-livo.mdx @@ -2,6 +2,7 @@ title: EVBox Livo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/livo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/evse-din.mdx b/docs/devices-next/chargers/evse-din.mdx index 4d9d870732..90e02cec37 100644 --- a/docs/devices-next/chargers/evse-din.mdx +++ b/docs/devices-next/chargers/evse-din.mdx @@ -2,6 +2,7 @@ title: EVSE DIN custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/evse-wifi.mdx b/docs/devices-next/chargers/evse-wifi.mdx index fe1ea0d753..3ab825742e 100644 --- a/docs/devices-next/chargers/evse-wifi.mdx +++ b/docs/devices-next/chargers/evse-wifi.mdx @@ -2,6 +2,7 @@ title: EVSE-WiFi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evsewifi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/free2move-eprowallbox-move.mdx b/docs/devices-next/chargers/free2move-eprowallbox-move.mdx index ac987f7820..929cee03b7 100644 --- a/docs/devices-next/chargers/free2move-eprowallbox-move.mdx +++ b/docs/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -2,6 +2,7 @@ title: Free2Move eProWallbox Move custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/free2move-eprowallbox.mdx b/docs/devices-next/chargers/free2move-eprowallbox.mdx index b24c6260a3..0ca80e897f 100644 --- a/docs/devices-next/chargers/free2move-eprowallbox.mdx +++ b/docs/devices-next/chargers/free2move-eprowallbox.mdx @@ -2,6 +2,7 @@ title: Free2Move eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx index 8df3f589cc..472f0e6e9b 100644 --- a/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx +++ b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -2,6 +2,7 @@ title: Free2move eSolutions eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-esolutions.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx b/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx index a418118665..54162875a8 100644 --- a/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx +++ b/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -2,6 +2,7 @@ title: Fronius Wattpilot (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/garo-glb.mdx b/docs/devices-next/chargers/garo-glb.mdx index 0294cbc05f..b816afe90c 100644 --- a/docs/devices-next/chargers/garo-glb.mdx +++ b/docs/devices-next/chargers/garo-glb.mdx @@ -2,6 +2,7 @@ title: Garo GLB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/garo-glbplus.mdx b/docs/devices-next/chargers/garo-glbplus.mdx index e4de43c2af..f4a0be692a 100644 --- a/docs/devices-next/chargers/garo-glbplus.mdx +++ b/docs/devices-next/chargers/garo-glbplus.mdx @@ -2,6 +2,7 @@ title: Garo GLB+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/garo-ls4-compact.mdx b/docs/devices-next/chargers/garo-ls4-compact.mdx index db7de3644d..9681b1769c 100644 --- a/docs/devices-next/chargers/garo-ls4-compact.mdx +++ b/docs/devices-next/chargers/garo-ls4-compact.mdx @@ -2,6 +2,7 @@ title: Garo LS4 compact custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/garo-ls4.mdx b/docs/devices-next/chargers/garo-ls4.mdx index 758b21a9ef..fd903e6a8c 100644 --- a/docs/devices-next/chargers/garo-ls4.mdx +++ b/docs/devices-next/chargers/garo-ls4.mdx @@ -2,6 +2,7 @@ title: Garo LS4 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx index 45f81e0b68..3b22d87c4b 100644 --- a/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx +++ b/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -2,6 +2,7 @@ title: go-e Charger Gemini (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-gemini.mdx b/docs/devices-next/chargers/go-e-charger-gemini.mdx index 0c19bef48e..43576e6da9 100644 --- a/docs/devices-next/chargers/go-e-charger-gemini.mdx +++ b/docs/devices-next/chargers/go-e-charger-gemini.mdx @@ -2,6 +2,7 @@ title: go-e Charger Gemini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-homefix.mdx b/docs/devices-next/chargers/go-e-charger-homefix.mdx index 1063311749..dd49fa1c9b 100644 --- a/docs/devices-next/chargers/go-e-charger-homefix.mdx +++ b/docs/devices-next/chargers/go-e-charger-homefix.mdx @@ -2,6 +2,7 @@ title: go-e Charger HOMEfix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-homeplus.mdx b/docs/devices-next/chargers/go-e-charger-homeplus.mdx index 28499013cf..fde6551ae2 100644 --- a/docs/devices-next/chargers/go-e-charger-homeplus.mdx +++ b/docs/devices-next/chargers/go-e-charger-homeplus.mdx @@ -2,6 +2,7 @@ title: go-e Charger HOME+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx index 815f147e9b..a4b68888cb 100644 --- a/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx +++ b/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -2,6 +2,7 @@ title: go-e Charger PRO (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-pro.mdx b/docs/devices-next/chargers/go-e-charger-pro.mdx index 3c0b621fd8..bcca58b067 100644 --- a/docs/devices-next/chargers/go-e-charger-pro.mdx +++ b/docs/devices-next/chargers/go-e-charger-pro.mdx @@ -2,6 +2,7 @@ title: go-e Charger PRO custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx b/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx index 169c34c44c..8b5e3fa119 100644 --- a/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx +++ b/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -2,6 +2,7 @@ title: go-e Charger V3 (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/go-e-charger-v3.mdx b/docs/devices-next/chargers/go-e-charger-v3.mdx index 135133d195..4b19551689 100644 --- a/docs/devices-next/chargers/go-e-charger-v3.mdx +++ b/docs/devices-next/chargers/go-e-charger-v3.mdx @@ -2,6 +2,7 @@ title: go-e Charger V3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/hardy-barth-cph1.mdx b/docs/devices-next/chargers/hardy-barth-cph1.mdx index ce24a121f6..a6e7486f0c 100644 --- a/docs/devices-next/chargers/hardy-barth-cph1.mdx +++ b/docs/devices-next/chargers/hardy-barth-cph1.mdx @@ -2,6 +2,7 @@ title: Hardy Barth cPH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/hardy-barth-cph2.mdx b/docs/devices-next/chargers/hardy-barth-cph2.mdx index bb3a2c5dbd..c855f9c6ac 100644 --- a/docs/devices-next/chargers/hardy-barth-cph2.mdx +++ b/docs/devices-next/chargers/hardy-barth-cph2.mdx @@ -2,6 +2,7 @@ title: Hardy Barth cPH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/hardy-barth-cpm2.mdx b/docs/devices-next/chargers/hardy-barth-cpm2.mdx index 516ce26e64..5461accef1 100644 --- a/docs/devices-next/chargers/hardy-barth-cpm2.mdx +++ b/docs/devices-next/chargers/hardy-barth-cpm2.mdx @@ -2,6 +2,7 @@ title: Hardy Barth cPμ2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/heidelberg-energy-control.mdx b/docs/devices-next/chargers/heidelberg-energy-control.mdx index 3f5527a242..8a55164bb5 100644 --- a/docs/devices-next/chargers/heidelberg-energy-control.mdx +++ b/docs/devices-next/chargers/heidelberg-energy-control.mdx @@ -2,6 +2,7 @@ title: Heidelberg Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/hesotec-ebox.mdx b/docs/devices-next/chargers/hesotec-ebox.mdx index 7293267089..4ade854e77 100644 --- a/docs/devices-next/chargers/hesotec-ebox.mdx +++ b/docs/devices-next/chargers/hesotec-ebox.mdx @@ -2,6 +2,7 @@ title: Hesotec eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/hesotec-esat.mdx b/docs/devices-next/chargers/hesotec-esat.mdx index 30c38c7647..fc8c94f015 100644 --- a/docs/devices-next/chargers/hesotec-esat.mdx +++ b/docs/devices-next/chargers/hesotec-esat.mdx @@ -2,6 +2,7 @@ title: Hesotec eSat custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/home-assistant-switch.mdx b/docs/devices-next/chargers/home-assistant-switch.mdx index 1c781a513f..71b5162852 100644 --- a/docs/devices-next/chargers/home-assistant-switch.mdx +++ b/docs/devices-next/chargers/home-assistant-switch.mdx @@ -2,6 +2,7 @@ title: Home Assistant Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homeassistant-switch.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/homecharge-homecharger.mdx b/docs/devices-next/chargers/homecharge-homecharger.mdx index 7eb78b2036..a415749063 100644 --- a/docs/devices-next/chargers/homecharge-homecharger.mdx +++ b/docs/devices-next/chargers/homecharge-homecharger.mdx @@ -2,6 +2,7 @@ title: Homecharge Homecharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-homecharge.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/homematic-ip.mdx b/docs/devices-next/chargers/homematic-ip.mdx index 041576f696..7bd57444d7 100644 --- a/docs/devices-next/chargers/homematic-ip.mdx +++ b/docs/devices-next/chargers/homematic-ip.mdx @@ -2,6 +2,7 @@ title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homematic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/homewizard.mdx b/docs/devices-next/chargers/homewizard.mdx index 23f16e4bc7..f376fade9f 100644 --- a/docs/devices-next/chargers/homewizard.mdx +++ b/docs/devices-next/chargers/homewizard.mdx @@ -2,6 +2,7 @@ title: HomeWizard custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homewizard.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx b/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx index 0f76010b87..19973f8092 100644 --- a/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx +++ b/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -2,6 +2,7 @@ title: Huawei SCharger-22KT-S0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx b/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx index 53187b5d6b..850fe1827b 100644 --- a/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx +++ b/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -2,6 +2,7 @@ title: Huawei SCharger-7KS-S0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/idm.mdx b/docs/devices-next/chargers/idm.mdx index 6836b14f83..d5d4f73d00 100644 --- a/docs/devices-next/chargers/idm.mdx +++ b/docs/devices-next/chargers/idm.mdx @@ -2,6 +2,7 @@ title: IDM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/idm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/index.mdx b/docs/devices-next/chargers/index.mdx index e0a7fe557e..873924cd41 100644 --- a/docs/devices-next/chargers/index.mdx +++ b/docs/devices-next/chargers/index.mdx @@ -1,6 +1,7 @@ --- title: Chargers hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/docs/devices-next/chargers/innogy-ebox.mdx b/docs/devices-next/chargers/innogy-ebox.mdx index d203e58862..b0c089795d 100644 --- a/docs/devices-next/chargers/innogy-ebox.mdx +++ b/docs/devices-next/chargers/innogy-ebox.mdx @@ -2,6 +2,7 @@ title: Innogy eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/inro-pantabox.mdx b/docs/devices-next/chargers/inro-pantabox.mdx index 158c98063b..a2f84f980d 100644 --- a/docs/devices-next/chargers/inro-pantabox.mdx +++ b/docs/devices-next/chargers/inro-pantabox.mdx @@ -2,6 +2,7 @@ title: INRO Pantabox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pantabox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/juice-charger-me.mdx b/docs/devices-next/chargers/juice-charger-me.mdx index 10d6bf265f..c5c666e2af 100644 --- a/docs/devices-next/chargers/juice-charger-me.mdx +++ b/docs/devices-next/chargers/juice-charger-me.mdx @@ -2,6 +2,7 @@ title: Juice Charger Me custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/junkers-sg-ready.mdx b/docs/devices-next/chargers/junkers-sg-ready.mdx index e468bc27a2..ffddbe002f 100644 --- a/docs/devices-next/chargers/junkers-sg-ready.mdx +++ b/docs/devices-next/chargers/junkers-sg-ready.mdx @@ -2,6 +2,7 @@ title: Junkers SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kathrein-kwb-ac20.mdx b/docs/devices-next/chargers/kathrein-kwb-ac20.mdx index 8b715f3592..23065d5ccf 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac20.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC20 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kathrein-kwb-ac35.mdx b/docs/devices-next/chargers/kathrein-kwb-ac35.mdx index 4e24e81e4a..d490e298ef 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac35.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC35 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx index 3655e81074..2cdd5890c7 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC40 E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kathrein-kwb-ac40.mdx b/docs/devices-next/chargers/kathrein-kwb-ac40.mdx index 92f99c1085..a46778ed73 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac40.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC40 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx b/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx index 3e942b71ad..e16f10982e 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC60 E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kathrein-kwb-ac60.mdx b/docs/devices-next/chargers/kathrein-kwb-ac60.mdx index 86826f1a4b..73f1669eb8 100644 --- a/docs/devices-next/chargers/kathrein-kwb-ac60.mdx +++ b/docs/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC60 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/keba-kecontact-p20.mdx b/docs/devices-next/chargers/keba-kecontact-p20.mdx index 148ffba4e6..5824fc6555 100644 --- a/docs/devices-next/chargers/keba-kecontact-p20.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p20.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P20 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx b/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx index 5ed52f8895..fe912bfb0d 100644 --- a/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P30 C-Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx b/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx index dbf95dc12c..e00b2f574f 100644 --- a/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P30 X-Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx b/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx index bff59a3d7c..c3cae38041 100644 --- a/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P40 Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/keba-kecontact-p40.mdx b/docs/devices-next/chargers/keba-kecontact-p40.mdx index e90428d240..9134f4aaa4 100644 --- a/docs/devices-next/chargers/keba-kecontact-p40.mdx +++ b/docs/devices-next/chargers/keba-kecontact-p40.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P40 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kermi-x-center-pro.mdx b/docs/devices-next/chargers/kermi-x-center-pro.mdx index 53d76d9877..41f0a661ef 100644 --- a/docs/devices-next/chargers/kermi-x-center-pro.mdx +++ b/docs/devices-next/chargers/kermi-x-center-pro.mdx @@ -2,6 +2,7 @@ title: Kermi x-center pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kontron-solar-charger.mdx b/docs/devices-next/chargers/kontron-solar-charger.mdx index 4532bd3c0f..331a4aa12e 100644 --- a/docs/devices-next/chargers/kontron-solar-charger.mdx +++ b/docs/devices-next/chargers/kontron-solar-charger.mdx @@ -2,6 +2,7 @@ title: Kontron Solar Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kostal-enector.mdx b/docs/devices-next/chargers/kostal-enector.mdx index 3959aed5b2..4f8e58f232 100644 --- a/docs/devices-next/chargers/kostal-enector.mdx +++ b/docs/devices-next/chargers/kostal-enector.mdx @@ -2,6 +2,7 @@ title: Kostal Enector custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/kse-wbx16.mdx b/docs/devices-next/chargers/kse-wbx16.mdx index 81f3f27dab..ce84b915b9 100644 --- a/docs/devices-next/chargers/kse-wbx16.mdx +++ b/docs/devices-next/chargers/kse-wbx16.mdx @@ -2,6 +2,7 @@ title: KSE wBX16 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ladefoxx-evload.mdx b/docs/devices-next/chargers/ladefoxx-evload.mdx index b3c5b7a24c..e512073eb4 100644 --- a/docs/devices-next/chargers/ladefoxx-evload.mdx +++ b/docs/devices-next/chargers/ladefoxx-evload.mdx @@ -2,6 +2,7 @@ title: LadeFoxx EvLoad custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx b/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx index 5f6bfaf433..51ad7ecc79 100644 --- a/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx +++ b/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -2,6 +2,7 @@ title: LadeFoxx Mikro 2.0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/lambda-eu-l-series.mdx b/docs/devices-next/chargers/lambda-eu-l-series.mdx index 741941cd6e..a881d6a22e 100644 --- a/docs/devices-next/chargers/lambda-eu-l-series.mdx +++ b/docs/devices-next/chargers/lambda-eu-l-series.mdx @@ -2,6 +2,7 @@ title: Lambda EU-L Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/lrt-home-essentialplus.mdx b/docs/devices-next/chargers/lrt-home-essentialplus.mdx index df3416d7e0..2926496137 100644 --- a/docs/devices-next/chargers/lrt-home-essentialplus.mdx +++ b/docs/devices-next/chargers/lrt-home-essentialplus.mdx @@ -2,6 +2,7 @@ title: LRT HOME Essential+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amedio-professional.mdx b/docs/devices-next/chargers/mennekes-amedio-professional.mdx index f9652a542c..492b2a5f7e 100644 --- a/docs/devices-next/chargers/mennekes-amedio-professional.mdx +++ b/docs/devices-next/chargers/mennekes-amedio-professional.mdx @@ -2,6 +2,7 @@ title: Mennekes AMEDIO Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx index 51d250b7d3..72392fae6c 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON 4Business 700 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx index d918d6a2da..fcd791fff1 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON 4You 300 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx index 81b880263b..ce8d1addef 100644 --- a/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON 4You 500 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx index b3e4735b28..3f412d2d33 100644 --- a/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON ChargeControl custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx b/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx index bab95a3195..7821357b2f 100644 --- a/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Compact 2.0s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-premium.mdx b/docs/devices-next/chargers/mennekes-amtron-premium.mdx index 3d950381dc..022f906ab2 100644 --- a/docs/devices-next/chargers/mennekes-amtron-premium.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-premium.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Premium custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-professional.mdx b/docs/devices-next/chargers/mennekes-amtron-professional.mdx index 32f55b4d06..e0427d76cf 100644 --- a/docs/devices-next/chargers/mennekes-amtron-professional.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-professional.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-amtron-xtra.mdx b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx index f54e8d70ed..2353c03c39 100644 --- a/docs/devices-next/chargers/mennekes-amtron-xtra.mdx +++ b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Xtra custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx index 97353d26d1..13e712a877 100644 --- a/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx +++ b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -2,6 +2,7 @@ title: Mennekes eMobility Gateway (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-smart-acu.mdx b/docs/devices-next/chargers/mennekes-smart-acu.mdx index 869f246263..690adaa88b 100644 --- a/docs/devices-next/chargers/mennekes-smart-acu.mdx +++ b/docs/devices-next/chargers/mennekes-smart-acu.mdx @@ -2,6 +2,7 @@ title: Mennekes Smart (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mennekes-smart-t-acu.mdx b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx index ada58add4c..8a67f82259 100644 --- a/docs/devices-next/chargers/mennekes-smart-t-acu.mdx +++ b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -2,6 +2,7 @@ title: Mennekes Smart T (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx index 36e25847b6..ef35db5e32 100644 --- a/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx +++ b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -2,6 +2,7 @@ title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-elwa-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx b/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx index b4f7193412..db72ea1b59 100644 --- a/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx +++ b/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -2,6 +2,7 @@ title: my-PV AC•THOR 9s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/my-pv-ac-thor.mdx b/docs/devices-next/chargers/my-pv-ac-thor.mdx index fdf8e2f1f4..56b6869e8a 100644 --- a/docs/devices-next/chargers/my-pv-ac-thor.mdx +++ b/docs/devices-next/chargers/my-pv-ac-thor.mdx @@ -2,6 +2,7 @@ title: my-PV AC•THOR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/mystrom-switch.mdx b/docs/devices-next/chargers/mystrom-switch.mdx index 782699fbfe..6c4d265486 100644 --- a/docs/devices-next/chargers/mystrom-switch.mdx +++ b/docs/devices-next/chargers/mystrom-switch.mdx @@ -2,6 +2,7 @@ title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mystrom.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/nibe-ap-aw10.mdx b/docs/devices-next/chargers/nibe-ap-aw10.mdx index 84ef9a7d71..5234311b3f 100644 --- a/docs/devices-next/chargers/nibe-ap-aw10.mdx +++ b/docs/devices-next/chargers/nibe-ap-aw10.mdx @@ -2,6 +2,7 @@ title: Nibe AP-AW10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/novelan-wpr-net.mdx b/docs/devices-next/chargers/novelan-wpr-net.mdx index 0df911d277..b371a72160 100644 --- a/docs/devices-next/chargers/novelan-wpr-net.mdx +++ b/docs/devices-next/chargers/novelan-wpr-net.mdx @@ -2,6 +2,7 @@ title: Novelan WPR NET custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/nrgkick-connect.mdx b/docs/devices-next/chargers/nrgkick-connect.mdx index 1e03bf5c57..1e986ab1f5 100644 --- a/docs/devices-next/chargers/nrgkick-connect.mdx +++ b/docs/devices-next/chargers/nrgkick-connect.mdx @@ -2,6 +2,7 @@ title: NRGkick Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrgkick-connect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/nrgkick-gen2.mdx b/docs/devices-next/chargers/nrgkick-gen2.mdx index c1502b44c8..731254e32b 100644 --- a/docs/devices-next/chargers/nrgkick-gen2.mdx +++ b/docs/devices-next/chargers/nrgkick-gen2.mdx @@ -2,6 +2,7 @@ title: NRGkick Gen2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrggen2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/obo-bettermann-ion.mdx b/docs/devices-next/chargers/obo-bettermann-ion.mdx index d0f6acbea3..e32c8685f3 100644 --- a/docs/devices-next/chargers/obo-bettermann-ion.mdx +++ b/docs/devices-next/chargers/obo-bettermann-ion.mdx @@ -2,6 +2,7 @@ title: OBO Bettermann Ion custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx b/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx index 420d8f8650..e9af002d68 100644 --- a/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx +++ b/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -2,6 +2,7 @@ title: OCPP 1.6J compatible (Smart Charging) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/openevse.mdx b/docs/devices-next/chargers/openevse.mdx index 59c8306e53..1781e83291 100644 --- a/docs/devices-next/chargers/openevse.mdx +++ b/docs/devices-next/chargers/openevse.mdx @@ -2,6 +2,7 @@ title: OpenEVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openevse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/openwb-pro.mdx b/docs/devices-next/chargers/openwb-pro.mdx index 3cdb09701b..10128a8b73 100644 --- a/docs/devices-next/chargers/openwb-pro.mdx +++ b/docs/devices-next/chargers/openwb-pro.mdx @@ -2,6 +2,7 @@ title: openWB Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-pro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/openwb-series2.mdx b/docs/devices-next/chargers/openwb-series2.mdx index 4e13e80c45..0055c2a510 100644 --- a/docs/devices-next/chargers/openwb-series2.mdx +++ b/docs/devices-next/chargers/openwb-series2.mdx @@ -2,6 +2,7 @@ title: openWB series2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/openwb-software-2-x.mdx b/docs/devices-next/chargers/openwb-software-2-x.mdx index 158c874d1a..414e7305f6 100644 --- a/docs/devices-next/chargers/openwb-software-2-x.mdx +++ b/docs/devices-next/chargers/openwb-software-2-x.mdx @@ -2,6 +2,7 @@ title: openWB Software 2.x custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/optec-mobility-one.mdx b/docs/devices-next/chargers/optec-mobility-one.mdx index 0dba6ee631..8e62156d64 100644 --- a/docs/devices-next/chargers/optec-mobility-one.mdx +++ b/docs/devices-next/chargers/optec-mobility-one.mdx @@ -2,6 +2,7 @@ title: Optec Mobility One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/orbis-viaris.mdx b/docs/devices-next/chargers/orbis-viaris.mdx index 0edacc846f..a14c17ebdd 100644 --- a/docs/devices-next/chargers/orbis-viaris.mdx +++ b/docs/devices-next/chargers/orbis-viaris.mdx @@ -2,6 +2,7 @@ title: Orbis Viaris custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-orbis.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/pc-electric-garo.mdx b/docs/devices-next/chargers/pc-electric-garo.mdx index d014eca50a..c7846c1b54 100644 --- a/docs/devices-next/chargers/pc-electric-garo.mdx +++ b/docs/devices-next/chargers/pc-electric-garo.mdx @@ -2,6 +2,7 @@ title: PC Electric Garo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pcelectric-garo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/peblar-business.mdx b/docs/devices-next/chargers/peblar-business.mdx index b9f227d1d3..bd59abdf09 100644 --- a/docs/devices-next/chargers/peblar-business.mdx +++ b/docs/devices-next/chargers/peblar-business.mdx @@ -2,6 +2,7 @@ title: Peblar Business custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/peblar-home-plus.mdx b/docs/devices-next/chargers/peblar-home-plus.mdx index f424afe937..1a394245f6 100644 --- a/docs/devices-next/chargers/peblar-home-plus.mdx +++ b/docs/devices-next/chargers/peblar-home-plus.mdx @@ -2,6 +2,7 @@ title: Peblar Home Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/peblar-home.mdx b/docs/devices-next/chargers/peblar-home.mdx index 0c6daddb66..a5477b7c17 100644 --- a/docs/devices-next/chargers/peblar-home.mdx +++ b/docs/devices-next/chargers/peblar-home.mdx @@ -2,6 +2,7 @@ title: Peblar Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/phoenix-contact-charx.mdx b/docs/devices-next/chargers/phoenix-contact-charx.mdx index d8642a8bf0..240914c6a4 100644 --- a/docs/devices-next/chargers/phoenix-contact-charx.mdx +++ b/docs/devices-next/chargers/phoenix-contact-charx.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact CHARX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx index 66165fc6bb..bb788fb620 100644 --- a/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx +++ b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EM-CP-PP-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-em-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx index 899023e13b..1f188c1989 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx index 67613f0437..fea82ca044 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx index 974be4f994..938d809aab 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx index 80722e8e24..d0f6788146 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx index 511d1fd0e2..1829844f56 100644 --- a/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx +++ b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-SER custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-ser.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/plugchoice.mdx b/docs/devices-next/chargers/plugchoice.mdx index 079781b064..47d43d6a42 100644 --- a/docs/devices-next/chargers/plugchoice.mdx +++ b/docs/devices-next/chargers/plugchoice.mdx @@ -2,6 +2,7 @@ title: Plugchoice custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/plugchoice.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx index 681d0ec47a..8da6c0122e 100644 --- a/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx +++ b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -2,6 +2,7 @@ title: Porsche Mobile Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx index c892a96ae9..96740a3b3f 100644 --- a/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx +++ b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -2,6 +2,7 @@ title: Porsche Mobile Charger Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/porsche-wallbox.mdx b/docs/devices-next/chargers/porsche-wallbox.mdx index 925f0a56bb..4758fbfb75 100644 --- a/docs/devices-next/chargers/porsche-wallbox.mdx +++ b/docs/devices-next/chargers/porsche-wallbox.mdx @@ -2,6 +2,7 @@ title: Porsche Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/porsche-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/pracht-alpha-xt.mdx b/docs/devices-next/chargers/pracht-alpha-xt.mdx index b2c812290d..8703e415d4 100644 --- a/docs/devices-next/chargers/pracht-alpha-xt.mdx +++ b/docs/devices-next/chargers/pracht-alpha-xt.mdx @@ -2,6 +2,7 @@ title: Pracht Alpha XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/pracht-mono-xt.mdx b/docs/devices-next/chargers/pracht-mono-xt.mdx index 96a4281876..2cc9c234c8 100644 --- a/docs/devices-next/chargers/pracht-mono-xt.mdx +++ b/docs/devices-next/chargers/pracht-mono-xt.mdx @@ -2,6 +2,7 @@ title: Pracht Mono XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/pracht-pni.mdx b/docs/devices-next/chargers/pracht-pni.mdx index 3cd2e02e45..f141479da2 100644 --- a/docs/devices-next/chargers/pracht-pni.mdx +++ b/docs/devices-next/chargers/pracht-pni.mdx @@ -2,6 +2,7 @@ title: Pracht PNI custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/pracht-xtplus.mdx b/docs/devices-next/chargers/pracht-xtplus.mdx index 56ffe7520a..6224084440 100644 --- a/docs/devices-next/chargers/pracht-xtplus.mdx +++ b/docs/devices-next/chargers/pracht-xtplus.mdx @@ -2,6 +2,7 @@ title: Pracht XT+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/pulsares-simplebox.mdx b/docs/devices-next/chargers/pulsares-simplebox.mdx index acc0357ae4..a66ceed5eb 100644 --- a/docs/devices-next/chargers/pulsares-simplebox.mdx +++ b/docs/devices-next/chargers/pulsares-simplebox.mdx @@ -2,6 +2,7 @@ title: Pulsares SimpleBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsares.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/pulsatrix.mdx b/docs/devices-next/chargers/pulsatrix.mdx index 0009e7d965..f4cff6d585 100644 --- a/docs/devices-next/chargers/pulsatrix.mdx +++ b/docs/devices-next/chargers/pulsatrix.mdx @@ -2,6 +2,7 @@ title: Pulsatrix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsatrix.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx b/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx index b468bcfa31..3e038e75e6 100644 --- a/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx +++ b/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -2,6 +2,7 @@ title: Qcells Q.HOME EDRIVE A custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/roth-thermoaura.mdx b/docs/devices-next/chargers/roth-thermoaura.mdx index 1b9596c38d..eddd224c44 100644 --- a/docs/devices-next/chargers/roth-thermoaura.mdx +++ b/docs/devices-next/chargers/roth-thermoaura.mdx @@ -2,6 +2,7 @@ title: Roth ThermoAura custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/roth-thermoterra.mdx b/docs/devices-next/chargers/roth-thermoterra.mdx index 8775bec4ff..e070ca710a 100644 --- a/docs/devices-next/chargers/roth-thermoterra.mdx +++ b/docs/devices-next/chargers/roth-thermoterra.mdx @@ -2,6 +2,7 @@ title: Roth ThermoTerra custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/schneider-evlink-pro.mdx b/docs/devices-next/chargers/schneider-evlink-pro.mdx index 40413cca72..75934dd0a2 100644 --- a/docs/devices-next/chargers/schneider-evlink-pro.mdx +++ b/docs/devices-next/chargers/schneider-evlink-pro.mdx @@ -2,6 +2,7 @@ title: Schneider EVlink Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/schneider-evlink-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/schrack-i-charge-cion.mdx b/docs/devices-next/chargers/schrack-i-charge-cion.mdx index 1c2c1819b7..c05e28898a 100644 --- a/docs/devices-next/chargers/schrack-i-charge-cion.mdx +++ b/docs/devices-next/chargers/schrack-i-charge-cion.mdx @@ -2,6 +2,7 @@ title: Schrack i-CHARGE CION custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/senec-wallbox-pro-s.mdx b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx index ae101d0e1f..da05661cea 100644 --- a/docs/devices-next/chargers/senec-wallbox-pro-s.mdx +++ b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -2,6 +2,7 @@ title: SENEC Wallbox pro s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/senec-wallbox-pro.mdx b/docs/devices-next/chargers/senec-wallbox-pro.mdx index 407f763caf..0f184ee5b8 100644 --- a/docs/devices-next/chargers/senec-wallbox-pro.mdx +++ b/docs/devices-next/chargers/senec-wallbox-pro.mdx @@ -2,6 +2,7 @@ title: SENEC Wallbox pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/shelly-1.mdx b/docs/devices-next/chargers/shelly-1.mdx index 5d073869b9..53f90b1b15 100644 --- a/docs/devices-next/chargers/shelly-1.mdx +++ b/docs/devices-next/chargers/shelly-1.mdx @@ -2,6 +2,7 @@ title: Shelly 1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/shelly-plug-s.mdx b/docs/devices-next/chargers/shelly-plug-s.mdx index 05e35d074a..3268edd48c 100644 --- a/docs/devices-next/chargers/shelly-plug-s.mdx +++ b/docs/devices-next/chargers/shelly-plug-s.mdx @@ -2,6 +2,7 @@ title: Shelly Plug S custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/shelly-plus-1.mdx b/docs/devices-next/chargers/shelly-plus-1.mdx index bc88d47635..f30c032b24 100644 --- a/docs/devices-next/chargers/shelly-plus-1.mdx +++ b/docs/devices-next/chargers/shelly-plus-1.mdx @@ -2,6 +2,7 @@ title: Shelly Plus 1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/shelly-pro-1.mdx b/docs/devices-next/chargers/shelly-pro-1.mdx index 5c9647949b..401e8a2046 100644 --- a/docs/devices-next/chargers/shelly-pro-1.mdx +++ b/docs/devices-next/chargers/shelly-pro-1.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/siemens-versicharge-gen3.mdx b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx index 64134b9b6b..55292881e3 100644 --- a/docs/devices-next/chargers/siemens-versicharge-gen3.mdx +++ b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -2,6 +2,7 @@ title: Siemens Versicharge GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/versicharge.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/skoda-charger-connect.mdx b/docs/devices-next/chargers/skoda-charger-connect.mdx index 915340ab81..5d196237b5 100644 --- a/docs/devices-next/chargers/skoda-charger-connect.mdx +++ b/docs/devices-next/chargers/skoda-charger-connect.mdx @@ -2,6 +2,7 @@ title: Skoda Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx index 7b31c2212a..8c46d9f0ff 100644 --- a/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx +++ b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -2,6 +2,7 @@ title: Skoda Charger Pro Eichrecht custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/skoda-charger-pro.mdx b/docs/devices-next/chargers/skoda-charger-pro.mdx index 61afd2d35b..f643ea4cb9 100644 --- a/docs/devices-next/chargers/skoda-charger-pro.mdx +++ b/docs/devices-next/chargers/skoda-charger-pro.mdx @@ -2,6 +2,7 @@ title: Skoda Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/skoda-iv-charger-connect.mdx b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx index f27ffcaed7..0cac23d8bd 100644 --- a/docs/devices-next/chargers/skoda-iv-charger-connect.mdx +++ b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -2,6 +2,7 @@ title: Skoda iV Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx b/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx index fb0d284362..548e495629 100644 --- a/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx +++ b/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -2,6 +2,7 @@ title: Skoda iV Charger Connect+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/sma-echarger.mdx b/docs/devices-next/chargers/sma-echarger.mdx index 60e0b27ca3..6d767cf838 100644 --- a/docs/devices-next/chargers/sma-echarger.mdx +++ b/docs/devices-next/chargers/sma-echarger.mdx @@ -2,6 +2,7 @@ title: SMA eCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/sma-ev-charger.mdx b/docs/devices-next/chargers/sma-ev-charger.mdx index 4ce9787aa4..ab28c270ec 100644 --- a/docs/devices-next/chargers/sma-ev-charger.mdx +++ b/docs/devices-next/chargers/sma-ev-charger.mdx @@ -2,6 +2,7 @@ title: SMA EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/smartfox-pro-charger.mdx b/docs/devices-next/chargers/smartfox-pro-charger.mdx index 393fddf830..91dcc717ba 100644 --- a/docs/devices-next/chargers/smartfox-pro-charger.mdx +++ b/docs/devices-next/chargers/smartfox-pro-charger.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/smartwb.mdx b/docs/devices-next/chargers/smartwb.mdx index 9a428cc30c..ac159049c8 100644 --- a/docs/devices-next/chargers/smartwb.mdx +++ b/docs/devices-next/chargers/smartwb.mdx @@ -2,6 +2,7 @@ title: smartWB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartwb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/solaredge-home-ev-charger.mdx b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx index f463826deb..454f2f7898 100644 --- a/docs/devices-next/chargers/solaredge-home-ev-charger.mdx +++ b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -2,6 +2,7 @@ title: SolarEdge Home EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/solax-x3-evc.mdx b/docs/devices-next/chargers/solax-x3-evc.mdx index a860c57922..a482e58abd 100644 --- a/docs/devices-next/chargers/solax-x3-evc.mdx +++ b/docs/devices-next/chargers/solax-x3-evc.mdx @@ -2,6 +2,7 @@ title: Solax X3-EVC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/sonnen-sonnencharger.mdx b/docs/devices-next/chargers/sonnen-sonnencharger.mdx index 17ed87e054..8534d5ad54 100644 --- a/docs/devices-next/chargers/sonnen-sonnencharger.mdx +++ b/docs/devices-next/chargers/sonnen-sonnencharger.mdx @@ -2,6 +2,7 @@ title: Sonnen sonnenCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx index 3b3ffde47c..92b0a3e738 100644 --- a/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx +++ b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -2,6 +2,7 @@ title: Spelsberg Wallbox Smart Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/stark-in-strom-easy.mdx b/docs/devices-next/chargers/stark-in-strom-easy.mdx index e9023e2c65..7dde8b794a 100644 --- a/docs/devices-next/chargers/stark-in-strom-easy.mdx +++ b/docs/devices-next/chargers/stark-in-strom-easy.mdx @@ -2,6 +2,7 @@ title: Stark in Strom Easy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx index 13c5adc519..7315fa8f2a 100644 --- a/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx +++ b/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -2,6 +2,7 @@ title: Stiebel Eltron LWA/LWZ (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx index 0c9d2497e0..76a75de3d5 100644 --- a/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx +++ b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -2,6 +2,7 @@ title: Stiebel Eltron WPM (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-wpm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/sungrow-ac011e-01.mdx b/docs/devices-next/chargers/sungrow-ac011e-01.mdx index bfb2fa3c7d..2616e2105d 100644 --- a/docs/devices-next/chargers/sungrow-ac011e-01.mdx +++ b/docs/devices-next/chargers/sungrow-ac011e-01.mdx @@ -2,6 +2,7 @@ title: Sungrow AC011E-01 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/sungrow-ac011e.mdx b/docs/devices-next/chargers/sungrow-ac011e.mdx index 42cc2284bb..10d6fe4642 100644 --- a/docs/devices-next/chargers/sungrow-ac011e.mdx +++ b/docs/devices-next/chargers/sungrow-ac011e.mdx @@ -2,6 +2,7 @@ title: Sungrow AC011E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-sungrow.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/sungrow-ac22e-01.mdx b/docs/devices-next/chargers/sungrow-ac22e-01.mdx index 4ac74b61d6..a2de97b657 100644 --- a/docs/devices-next/chargers/sungrow-ac22e-01.mdx +++ b/docs/devices-next/chargers/sungrow-ac22e-01.mdx @@ -2,6 +2,7 @@ title: Sungrow AC22E-01 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tasmota-single-phase.mdx b/docs/devices-next/chargers/tasmota-single-phase.mdx index e28dafcdc4..ebfdf52e22 100644 --- a/docs/devices-next/chargers/tasmota-single-phase.mdx +++ b/docs/devices-next/chargers/tasmota-single-phase.mdx @@ -2,6 +2,7 @@ title: Tasmota single phase custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tasmota.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx index bb47bc9436..c2eb2754e2 100644 --- a/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx +++ b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -2,6 +2,7 @@ title: Tecalor THZ (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/technisat-technivolt.mdx b/docs/devices-next/chargers/technisat-technivolt.mdx index 9039ec9e59..cca6abc85f 100644 --- a/docs/devices-next/chargers/technisat-technivolt.mdx +++ b/docs/devices-next/chargers/technisat-technivolt.mdx @@ -2,6 +2,7 @@ title: TechniSat Technivolt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx b/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx index ab90caf96a..90c54de745 100644 --- a/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx +++ b/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -2,6 +2,7 @@ title: Tesla Wall Connector (Gen 3) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tessie.mdx b/docs/devices-next/chargers/tessie.mdx index 347ca4636f..fb3948f5b2 100644 --- a/docs/devices-next/chargers/tessie.mdx +++ b/docs/devices-next/chargers/tessie.mdx @@ -2,6 +2,7 @@ title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tessie.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tigo-go-ev-charger.mdx b/docs/devices-next/chargers/tigo-go-ev-charger.mdx index c242506442..670a1a0183 100644 --- a/docs/devices-next/chargers/tigo-go-ev-charger.mdx +++ b/docs/devices-next/chargers/tigo-go-ev-charger.mdx @@ -2,6 +2,7 @@ title: Tigo GO EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx index c6e355e4b0..9ea1d15322 100644 --- a/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx index e19188b079..e1b17ecd30 100644 --- a/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx index edd323e908..a9fb515a06 100644 --- a/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP3 Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx index e97839fecd..46ff740d07 100644 --- a/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP3 Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3-smart.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx index 30e059f678..ece700ec98 100644 --- a/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx +++ b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tplink.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx index eb0483332e..e8b259f627 100644 --- a/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx +++ b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tapo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/ubitricity-heinz.mdx b/docs/devices-next/chargers/ubitricity-heinz.mdx index 81861d988a..17964e1032 100644 --- a/docs/devices-next/chargers/ubitricity-heinz.mdx +++ b/docs/devices-next/chargers/ubitricity-heinz.mdx @@ -2,6 +2,7 @@ title: Ubitricity Heinz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/v2c-trydan.mdx b/docs/devices-next/chargers/v2c-trydan.mdx index 467fd32db2..767ea9d46b 100644 --- a/docs/devices-next/chargers/v2c-trydan.mdx +++ b/docs/devices-next/chargers/v2c-trydan.mdx @@ -2,6 +2,7 @@ title: V2C Trydan custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/trydan.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx index d750546402..965d5edea1 100644 --- a/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx +++ b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -2,6 +2,7 @@ title: Vaillant SensoNET (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vaillant.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/vestel-connect-plus.mdx b/docs/devices-next/chargers/vestel-connect-plus.mdx index d2a7a2bfd5..8e93ef5f77 100644 --- a/docs/devices-next/chargers/vestel-connect-plus.mdx +++ b/docs/devices-next/chargers/vestel-connect-plus.mdx @@ -2,6 +2,7 @@ title: Vestel Connect Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/vestel-evc04-home-smart.mdx b/docs/devices-next/chargers/vestel-evc04-home-smart.mdx index fbc2c5472f..614bc35630 100644 --- a/docs/devices-next/chargers/vestel-evc04-home-smart.mdx +++ b/docs/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -2,6 +2,7 @@ title: Vestel EVC04 Home Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx index 02a066b0d0..1164cd519d 100644 --- a/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx +++ b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -2,6 +2,7 @@ title: Victron EV Charging Station (via GX) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/victron-ev-charging-station.mdx b/docs/devices-next/chargers/victron-ev-charging-station.mdx index 97e127c0a4..075d4daf0e 100644 --- a/docs/devices-next/chargers/victron-ev-charging-station.mdx +++ b/docs/devices-next/chargers/victron-ev-charging-station.mdx @@ -2,6 +2,7 @@ title: Victron EV Charging Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron-evcs.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx index d03acd4453..db1f8afe3b 100644 --- a/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx +++ b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -2,6 +2,7 @@ title: Viessmann Heatpump (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/viessmann.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx b/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx index a90ebdfdb3..32d53a928c 100644 --- a/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx +++ b/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -2,6 +2,7 @@ title: Viridian EV EVSE EPC 2.0 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx index bb32a8ef04..b13cbc5ff7 100644 --- a/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -2,6 +2,7 @@ title: Volkswagen Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx index cdb67df507..8f7d29b541 100644 --- a/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -2,6 +2,7 @@ title: Volkswagen Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx index e3c86db9d6..b351b2d27c 100644 --- a/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx +++ b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -2,6 +2,7 @@ title: Volkswagen Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx index f2eca1b062..5777e27a6c 100644 --- a/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx +++ b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -2,6 +2,7 @@ title: Volkswagen ID. Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx index 2e5a20ae0b..637e6696c9 100644 --- a/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx +++ b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -2,6 +2,7 @@ title: Volkswagen ID. Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volt-time-one.mdx b/docs/devices-next/chargers/volt-time-one.mdx index 519b0f9f5d..6988fe1d8a 100644 --- a/docs/devices-next/chargers/volt-time-one.mdx +++ b/docs/devices-next/chargers/volt-time-one.mdx @@ -2,6 +2,7 @@ title: Volt Time One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volt-time-source-2.mdx b/docs/devices-next/chargers/volt-time-source-2.mdx index f20033673e..1ddde96b1d 100644 --- a/docs/devices-next/chargers/volt-time-source-2.mdx +++ b/docs/devices-next/chargers/volt-time-source-2.mdx @@ -2,6 +2,7 @@ title: Volt Time Source 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volt-time-source-2s.mdx b/docs/devices-next/chargers/volt-time-source-2s.mdx index 9415de0424..1a2fee8add 100644 --- a/docs/devices-next/chargers/volt-time-source-2s.mdx +++ b/docs/devices-next/chargers/volt-time-source-2s.mdx @@ -2,6 +2,7 @@ title: Volt Time Source 2s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/volt-time-source.mdx b/docs/devices-next/chargers/volt-time-source.mdx index aebc8ffcf2..e73d414010 100644 --- a/docs/devices-next/chargers/volt-time-source.mdx +++ b/docs/devices-next/chargers/volt-time-source.mdx @@ -2,6 +2,7 @@ title: Volt Time Source custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx b/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx index febada156c..72a31261ec 100644 --- a/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx +++ b/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -2,6 +2,7 @@ title: Wallbe Eco 2.0(s) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbe-eco.mdx b/docs/devices-next/chargers/wallbe-eco.mdx index 2cebd97384..e96635cb44 100644 --- a/docs/devices-next/chargers/wallbe-eco.mdx +++ b/docs/devices-next/chargers/wallbe-eco.mdx @@ -2,6 +2,7 @@ title: Wallbe Eco custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbe-pro.mdx b/docs/devices-next/chargers/wallbe-pro.mdx index 153aa3976a..4d415aa32e 100644 --- a/docs/devices-next/chargers/wallbe-pro.mdx +++ b/docs/devices-next/chargers/wallbe-pro.mdx @@ -2,6 +2,7 @@ title: Wallbe Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx index d55e6802cf..d66b58d6cc 100644 --- a/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Commander 2 (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-commander-2.mdx b/docs/devices-next/chargers/wallbox-commander-2.mdx index d616f97ea4..64363b10ee 100644 --- a/docs/devices-next/chargers/wallbox-commander-2.mdx +++ b/docs/devices-next/chargers/wallbox-commander-2.mdx @@ -2,6 +2,7 @@ title: wallbox Commander 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx index 19d12d793a..c003d7a72f 100644 --- a/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Copper SB (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-copper-sb.mdx b/docs/devices-next/chargers/wallbox-copper-sb.mdx index 143b6a2d6b..c687f70f4c 100644 --- a/docs/devices-next/chargers/wallbox-copper-sb.mdx +++ b/docs/devices-next/chargers/wallbox-copper-sb.mdx @@ -2,6 +2,7 @@ title: wallbox Copper SB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx index ea40329e66..4663ff9652 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Max (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-pulsar-max.mdx b/docs/devices-next/chargers/wallbox-pulsar-max.mdx index 4c43f37793..54b1a0869a 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-max.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-max.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Max custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx index f7e9a34936..d42137578f 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Plus (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wallbox-pulsar-plus.mdx b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx index e29f17bd2d..d87bbf1741 100644 --- a/docs/devices-next/chargers/wallbox-pulsar-plus.mdx +++ b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx index e5bed4d64b..ff2f4deeac 100644 --- a/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx +++ b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -2,6 +2,7 @@ title: Walther Werke Basic Evo Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/webasto-live.mdx b/docs/devices-next/chargers/webasto-live.mdx index 57fb6dfd85..d2662515af 100644 --- a/docs/devices-next/chargers/webasto-live.mdx +++ b/docs/devices-next/chargers/webasto-live.mdx @@ -2,6 +2,7 @@ title: Webasto Live custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/webasto-next.mdx b/docs/devices-next/chargers/webasto-next.mdx index 44f100a274..79c26b5273 100644 --- a/docs/devices-next/chargers/webasto-next.mdx +++ b/docs/devices-next/chargers/webasto-next.mdx @@ -2,6 +2,7 @@ title: Webasto NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/webasto-unite.mdx b/docs/devices-next/chargers/webasto-unite.mdx index f95c127900..4034c485d5 100644 --- a/docs/devices-next/chargers/webasto-unite.mdx +++ b/docs/devices-next/chargers/webasto-unite.mdx @@ -2,6 +2,7 @@ title: Webasto Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/weidmuller-ac-smart.mdx b/docs/devices-next/chargers/weidmuller-ac-smart.mdx index 4ee5702aa2..49eef9a31a 100644 --- a/docs/devices-next/chargers/weidmuller-ac-smart.mdx +++ b/docs/devices-next/chargers/weidmuller-ac-smart.mdx @@ -2,6 +2,7 @@ title: Weidmüller AC Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/weidmüller.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wolf-bwl.mdx b/docs/devices-next/chargers/wolf-bwl.mdx index a1b8d02d05..11e9e70fa4 100644 --- a/docs/devices-next/chargers/wolf-bwl.mdx +++ b/docs/devices-next/chargers/wolf-bwl.mdx @@ -2,6 +2,7 @@ title: Wolf BWL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/wolf-bws.mdx b/docs/devices-next/chargers/wolf-bws.mdx index 01349f6b10..c25106189b 100644 --- a/docs/devices-next/chargers/wolf-bws.mdx +++ b/docs/devices-next/chargers/wolf-bws.mdx @@ -2,6 +2,7 @@ title: Wolf BWS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/zaptec-go-2.mdx b/docs/devices-next/chargers/zaptec-go-2.mdx index 90e6b39ffc..dd6daf2bef 100644 --- a/docs/devices-next/chargers/zaptec-go-2.mdx +++ b/docs/devices-next/chargers/zaptec-go-2.mdx @@ -2,6 +2,7 @@ title: Zaptec Go 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/zaptec-go-ocpp.mdx b/docs/devices-next/chargers/zaptec-go-ocpp.mdx index 1194d8ac71..eeedfc5029 100644 --- a/docs/devices-next/chargers/zaptec-go-ocpp.mdx +++ b/docs/devices-next/chargers/zaptec-go-ocpp.mdx @@ -2,6 +2,7 @@ title: Zaptec Go (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/zaptec-go.mdx b/docs/devices-next/chargers/zaptec-go.mdx index fec735b046..1fdcad4810 100644 --- a/docs/devices-next/chargers/zaptec-go.mdx +++ b/docs/devices-next/chargers/zaptec-go.mdx @@ -2,6 +2,7 @@ title: Zaptec Go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/zaptec-pro.mdx b/docs/devices-next/chargers/zaptec-pro.mdx index fb34a57e89..2c16060533 100644 --- a/docs/devices-next/chargers/zaptec-pro.mdx +++ b/docs/devices-next/chargers/zaptec-pro.mdx @@ -2,6 +2,7 @@ title: Zaptec Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/zewotherm-eu-l-series.mdx b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx index 296f781e3d..83d9f14e02 100644 --- a/docs/devices-next/chargers/zewotherm-eu-l-series.mdx +++ b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -2,6 +2,7 @@ title: Zewotherm EU-L Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx index 1af25fb0a1..992e47c295 100644 --- a/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx +++ b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -2,6 +2,7 @@ title: ZJ Beny BCP EV charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-beny.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/a-tronix.mdx b/docs/devices-next/meters/a-tronix.mdx index 8368246cad..8ac4e621ee 100644 --- a/docs/devices-next/meters/a-tronix.mdx +++ b/docs/devices-next/meters/a-tronix.mdx @@ -2,6 +2,7 @@ title: A-Tronix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/abb-a43.mdx b/docs/devices-next/meters/abb-a43.mdx index 2e8bf17e12..64fea3c433 100644 --- a/docs/devices-next/meters/abb-a43.mdx +++ b/docs/devices-next/meters/abb-a43.mdx @@ -2,6 +2,7 @@ title: ABB A43 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/abb-a44.mdx b/docs/devices-next/meters/abb-a44.mdx index f9db613bf4..cb074be960 100644 --- a/docs/devices-next/meters/abb-a44.mdx +++ b/docs/devices-next/meters/abb-a44.mdx @@ -2,6 +2,7 @@ title: ABB A44 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/abb-b23.mdx b/docs/devices-next/meters/abb-b23.mdx index cb53d42922..6989f0f205 100644 --- a/docs/devices-next/meters/abb-b23.mdx +++ b/docs/devices-next/meters/abb-b23.mdx @@ -2,6 +2,7 @@ title: ABB B23 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/abb-b24.mdx b/docs/devices-next/meters/abb-b24.mdx index 50b4245af8..7303cb6b43 100644 --- a/docs/devices-next/meters/abb-b24.mdx +++ b/docs/devices-next/meters/abb-b24.mdx @@ -2,6 +2,7 @@ title: ABB B24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/acrel-adw300.mdx b/docs/devices-next/meters/acrel-adw300.mdx index ac1ce4737f..cbf325c0a6 100644 --- a/docs/devices-next/meters/acrel-adw300.mdx +++ b/docs/devices-next/meters/acrel-adw300.mdx @@ -2,6 +2,7 @@ title: Acrel ADW300 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/ads-tec-storaxe.mdx b/docs/devices-next/meters/ads-tec-storaxe.mdx index 2d4d6ea66a..56cc7b5a3b 100644 --- a/docs/devices-next/meters/ads-tec-storaxe.mdx +++ b/docs/devices-next/meters/ads-tec-storaxe.mdx @@ -2,6 +2,7 @@ title: Ads-tec StoraXe custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/storaxe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/alpha-ess-storion-smile.mdx b/docs/devices-next/meters/alpha-ess-storion-smile.mdx index 9ceb8e2480..b0d2bee81f 100644 --- a/docs/devices-next/meters/alpha-ess-storion-smile.mdx +++ b/docs/devices-next/meters/alpha-ess-storion-smile.mdx @@ -2,6 +2,7 @@ title: Alpha ESS Storion SMILE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/alpha-ess-smile.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/ampere-ampere-storagepro.mdx b/docs/devices-next/meters/ampere-ampere-storagepro.mdx index 47bdbad243..9a180a26a9 100644 --- a/docs/devices-next/meters/ampere-ampere-storagepro.mdx +++ b/docs/devices-next/meters/ampere-ampere-storagepro.mdx @@ -2,6 +2,7 @@ title: Ampere Ampere.StoragePro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/anker-micro-inverter.mdx b/docs/devices-next/meters/anker-micro-inverter.mdx index 826fbb4c10..76cf9be305 100644 --- a/docs/devices-next/meters/anker-micro-inverter.mdx +++ b/docs/devices-next/meters/anker-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Anker Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/apsystems-ez1.mdx b/docs/devices-next/meters/apsystems-ez1.mdx index fdb1665080..7eb95ad3cd 100644 --- a/docs/devices-next/meters/apsystems-ez1.mdx +++ b/docs/devices-next/meters/apsystems-ez1.mdx @@ -2,6 +2,7 @@ title: APsystems EZ1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/apsystems-ez1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/avm-fritzdect.mdx b/docs/devices-next/meters/avm-fritzdect.mdx index 7ff2791747..21bc25f14a 100644 --- a/docs/devices-next/meters/avm-fritzdect.mdx +++ b/docs/devices-next/meters/avm-fritzdect.mdx @@ -2,6 +2,7 @@ title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fritzdect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/axitec-axihycon-12-15h.mdx b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx index a8f7a3410f..046baec477 100644 --- a/docs/devices-next/meters/axitec-axihycon-12-15h.mdx +++ b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -2,6 +2,7 @@ title: Axitec AXIhycon 12-15H custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx index 8d1447c448..fd44bcb700 100644 --- a/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx +++ b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -2,6 +2,7 @@ title: Bernecker Engineering MPM3PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mpm3pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/bgetech-ds100.mdx b/docs/devices-next/meters/bgetech-ds100.mdx index af5ad487aa..122cfc51ee 100644 --- a/docs/devices-next/meters/bgetech-ds100.mdx +++ b/docs/devices-next/meters/bgetech-ds100.mdx @@ -2,6 +2,7 @@ title: BGEtech DS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ds100.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/bgetech-ws100.mdx b/docs/devices-next/meters/bgetech-ws100.mdx index d9e1c4c45e..a01029eaa3 100644 --- a/docs/devices-next/meters/bgetech-ws100.mdx +++ b/docs/devices-next/meters/bgetech-ws100.mdx @@ -2,6 +2,7 @@ title: BGEtech WS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ws100.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx index 8fb670c1f8..da5eb214ed 100644 --- a/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx +++ b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -2,6 +2,7 @@ title: Bosch BPT-S 5 Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bosch-bpt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/bosswerk-micro-inverter.mdx b/docs/devices-next/meters/bosswerk-micro-inverter.mdx index 0cc961fb94..f1b79c0285 100644 --- a/docs/devices-next/meters/bosswerk-micro-inverter.mdx +++ b/docs/devices-next/meters/bosswerk-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Bosswerk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx b/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx index 9b63cdb8a6..e4de293258 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM110/111/112 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/carlo-gavazzi-em24.mdx b/docs/devices-next/meters/carlo-gavazzi-em24.mdx index f72b725bf6..c204e6ffda 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em24.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em24.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx b/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx index 13165e7624..c48f233310 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM24_E1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx b/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx index a3ae1a4820..15ed7c16ef 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM330/EM340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx b/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx index f29cdc133a..2723409dbe 100644 --- a/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM530/EM540 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/carlo-gavazzi-et112.mdx b/docs/devices-next/meters/carlo-gavazzi-et112.mdx index 1cdaad8208..0c2ef82c51 100644 --- a/docs/devices-next/meters/carlo-gavazzi-et112.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-et112.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi ET112 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx b/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx index d46f7eaced..6e035b568d 100644 --- a/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx +++ b/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi ET330/ET340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/cfos-powerbrain-meter.mdx b/docs/devices-next/meters/cfos-powerbrain-meter.mdx index 65a89062ac..24af96067f 100644 --- a/docs/devices-next/meters/cfos-powerbrain-meter.mdx +++ b/docs/devices-next/meters/cfos-powerbrain-meter.mdx @@ -2,6 +2,7 @@ title: cFos PowerBrain Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cfos.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/demo-battery.mdx b/docs/devices-next/meters/demo-battery.mdx index 8bbaf95c5d..2ef01e847c 100644 --- a/docs/devices-next/meters/demo-battery.mdx +++ b/docs/devices-next/meters/demo-battery.mdx @@ -2,6 +2,7 @@ title: Demo battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-battery.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/demo-meter.mdx b/docs/devices-next/meters/demo-meter.mdx index 43964be755..0616e95044 100644 --- a/docs/devices-next/meters/demo-meter.mdx +++ b/docs/devices-next/meters/demo-meter.mdx @@ -2,6 +2,7 @@ title: Demo meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx index d43d5b1735..587bb235d0 100644 --- a/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Deye 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx index 0b7178e0be..470bb7f2d6 100644 --- a/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Deye hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/deye-micro-inverter.mdx b/docs/devices-next/meters/deye-micro-inverter.mdx index 82772666da..0d3b9ce82a 100644 --- a/docs/devices-next/meters/deye-micro-inverter.mdx +++ b/docs/devices-next/meters/deye-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Deye Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx index 1908f23b9c..1d1f171df5 100644 --- a/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx +++ b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Deye Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/deye-string-inverter.mdx b/docs/devices-next/meters/deye-string-inverter.mdx index 910034f2fa..d96606b1b0 100644 --- a/docs/devices-next/meters/deye-string-inverter.mdx +++ b/docs/devices-next/meters/deye-string-inverter.mdx @@ -2,6 +2,7 @@ title: Deye String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/discovergy.mdx b/docs/devices-next/meters/discovergy.mdx index 1029c2a334..33f1e2f2a6 100644 --- a/docs/devices-next/meters/discovergy.mdx +++ b/docs/devices-next/meters/discovergy.mdx @@ -2,6 +2,7 @@ title: Discovergy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/discovergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/dsmr.mdx b/docs/devices-next/meters/dsmr.mdx index fbec6d3f02..140b5ead54 100644 --- a/docs/devices-next/meters/dsmr.mdx +++ b/docs/devices-next/meters/dsmr.mdx @@ -2,6 +2,7 @@ title: DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dsmr.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/dzg-dvh4013.mdx b/docs/devices-next/meters/dzg-dvh4013.mdx index 605ff0dbb7..907cdd736f 100644 --- a/docs/devices-next/meters/dzg-dvh4013.mdx +++ b/docs/devices-next/meters/dzg-dvh4013.mdx @@ -2,6 +2,7 @@ title: DZG DVH4013 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dzg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/e3-dc.mdx b/docs/devices-next/meters/e3-dc.mdx index 545b1cc883..cf753bab14 100644 --- a/docs/devices-next/meters/e3-dc.mdx +++ b/docs/devices-next/meters/e3-dc.mdx @@ -2,6 +2,7 @@ title: E3/DC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/eastron-sdm120-modbus.mdx b/docs/devices-next/meters/eastron-sdm120-modbus.mdx index 312e54abf6..2d77f6085c 100644 --- a/docs/devices-next/meters/eastron-sdm120-modbus.mdx +++ b/docs/devices-next/meters/eastron-sdm120-modbus.mdx @@ -2,6 +2,7 @@ title: Eastron SDM120-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm120.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/eastron-sdm220-230.mdx b/docs/devices-next/meters/eastron-sdm220-230.mdx index 4a0c3ebf52..ec04c65f97 100644 --- a/docs/devices-next/meters/eastron-sdm220-230.mdx +++ b/docs/devices-next/meters/eastron-sdm220-230.mdx @@ -2,6 +2,7 @@ title: Eastron SDM220/230 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/eastron-sdm630-modbus.mdx b/docs/devices-next/meters/eastron-sdm630-modbus.mdx index c8e83a7756..6b09c84d78 100644 --- a/docs/devices-next/meters/eastron-sdm630-modbus.mdx +++ b/docs/devices-next/meters/eastron-sdm630-modbus.mdx @@ -2,6 +2,7 @@ title: Eastron SDM630-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/eastron-sdm72d-m.mdx b/docs/devices-next/meters/eastron-sdm72d-m.mdx index d4eb83b76b..293f5c2333 100644 --- a/docs/devices-next/meters/eastron-sdm72d-m.mdx +++ b/docs/devices-next/meters/eastron-sdm72d-m.mdx @@ -2,6 +2,7 @@ title: Eastron SDM72D-M custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm72.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/eastron-sdm72dm-v2.mdx b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx index ac8d30343e..b1dc237242 100644 --- a/docs/devices-next/meters/eastron-sdm72dm-v2.mdx +++ b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -2,6 +2,7 @@ title: Eastron SDM72DM-V2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/enphase-iq-envoy.mdx b/docs/devices-next/meters/enphase-iq-envoy.mdx index ea97dce4b8..db1e8ce8b6 100644 --- a/docs/devices-next/meters/enphase-iq-envoy.mdx +++ b/docs/devices-next/meters/enphase-iq-envoy.mdx @@ -2,6 +2,7 @@ title: Enphase IQ Envoy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/enphase.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/esphome-dlms-meter-austria.mdx b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx index a1977fb70b..adebe541db 100644 --- a/docs/devices-next/meters/esphome-dlms-meter-austria.mdx +++ b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -2,6 +2,7 @@ title: ESPHome DLMS Meter Austria custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/esphome-dlms-austria.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/esphome-dsmr.mdx b/docs/devices-next/meters/esphome-dsmr.mdx index 855ac6f273..e1659a5a2b 100644 --- a/docs/devices-next/meters/esphome-dsmr.mdx +++ b/docs/devices-next/meters/esphome-dsmr.mdx @@ -2,6 +2,7 @@ title: ESPHome DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/fenecon.mdx b/docs/devices-next/meters/fenecon.mdx index e8b136d8b3..09e1210fee 100644 --- a/docs/devices-next/meters/fenecon.mdx +++ b/docs/devices-next/meters/fenecon.mdx @@ -2,6 +2,7 @@ title: FENECON custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx index cc4dc2bb24..33a0a378ff 100644 --- a/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: FoxESS H1 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx index 249da7abb8..f1a77c2974 100644 --- a/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: FoxESS H3 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx index 1a3a76defd..f31f72ac79 100644 --- a/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: FoxESS H3-Smart Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3-smart.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/fronius-ohmpilot.mdx b/docs/devices-next/meters/fronius-ohmpilot.mdx index 00cd422db3..26f1b548bb 100644 --- a/docs/devices-next/meters/fronius-ohmpilot.mdx +++ b/docs/devices-next/meters/fronius-ohmpilot.mdx @@ -2,6 +2,7 @@ title: Fronius Ohmpilot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-ohmpilot.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/fronius-primo-gen24-plus.mdx b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx index 6c224fd967..c82c534882 100644 --- a/docs/devices-next/meters/fronius-primo-gen24-plus.mdx +++ b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -2,6 +2,7 @@ title: Fronius Primo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx index e9a5a9bf0c..60ebe4d5f6 100644 --- a/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx +++ b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -2,6 +2,7 @@ title: Fronius Smartmeter (via Inverter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/fronius-solar-api-v1.mdx b/docs/devices-next/meters/fronius-solar-api-v1.mdx index 04de90d186..3f1226139a 100644 --- a/docs/devices-next/meters/fronius-solar-api-v1.mdx +++ b/docs/devices-next/meters/fronius-solar-api-v1.mdx @@ -2,6 +2,7 @@ title: Fronius Solar API V1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-solarapi-v1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/fronius-symo-gen24-plus.mdx b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx index 950ede817b..60b75d0556 100644 --- a/docs/devices-next/meters/fronius-symo-gen24-plus.mdx +++ b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -2,6 +2,7 @@ title: Fronius Symo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx index 9a7be65fb2..5a248084dc 100644 --- a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -2,6 +2,7 @@ title: Ginlong Solis Hybrid Inverter (RHI series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx index b139ae9ff2..e6241f14f0 100644 --- a/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -2,6 +2,7 @@ title: Ginlong Solis Hybrid Inverter (S Series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/ginlong-solis-inverter.mdx b/docs/devices-next/meters/ginlong-solis-inverter.mdx index d8081be5d6..e0a03f6944 100644 --- a/docs/devices-next/meters/ginlong-solis-inverter.mdx +++ b/docs/devices-next/meters/ginlong-solis-inverter.mdx @@ -2,6 +2,7 @@ title: Ginlong Solis Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/go-e-controller.mdx b/docs/devices-next/meters/go-e-controller.mdx index 616f25c861..b91abf2197 100644 --- a/docs/devices-next/meters/go-e-controller.mdx +++ b/docs/devices-next/meters/go-e-controller.mdx @@ -2,6 +2,7 @@ title: go-e Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/go-e-controller.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx b/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx index 0d70392e73..4dd75ad404 100644 --- a/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx +++ b/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: GoodWe ET/EH/BH/BT Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx index 53165a3351..026458125f 100644 --- a/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx +++ b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -2,6 +2,7 @@ title: GoodWe GoodWe over Wifi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-wifi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx b/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx index 6b8b5d600a..00af33301a 100644 --- a/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx +++ b/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -2,6 +2,7 @@ title: GoodWe SDT/DT Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/growatt-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-hybrid-inverter.mdx index 1f3a51ec7b..cc452e4b23 100644 --- a/docs/devices-next/meters/growatt-hybrid-inverter.mdx +++ b/docs/devices-next/meters/growatt-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Growatt Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx b/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx index 4cf4f6af0d..88a03fb3d8 100644 --- a/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx +++ b/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Growatt TL-X(H) Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/homematic-ip.mdx b/docs/devices-next/meters/homematic-ip.mdx index 77f1089b45..19b7ab86c7 100644 --- a/docs/devices-next/meters/homematic-ip.mdx +++ b/docs/devices-next/meters/homematic-ip.mdx @@ -2,6 +2,7 @@ title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homematic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/homewizard-kwh-meter.mdx b/docs/devices-next/meters/homewizard-kwh-meter.mdx index ce9b142298..8f635e0e3f 100644 --- a/docs/devices-next/meters/homewizard-kwh-meter.mdx +++ b/docs/devices-next/meters/homewizard-kwh-meter.mdx @@ -2,6 +2,7 @@ title: HomeWizard kWh Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard-kwh.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx index b7ba9ccc30..d5062e7c66 100644 --- a/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx +++ b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -2,6 +2,7 @@ title: HomeWizard Wi-Fi P1 Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx index d9813432cf..5c9be5cff8 100644 --- a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -2,6 +2,7 @@ title: Hoymiles HM & HMS Series (via AhoyDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-ahoydtu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx index a7bda354e5..7c439a374b 100644 --- a/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -2,6 +2,7 @@ title: Hoymiles HM & HMS Series (via OpenDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-opendtu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/huawei-emma.mdx b/docs/devices-next/meters/huawei-emma.mdx index ab0a3218de..aa804313dc 100644 --- a/docs/devices-next/meters/huawei-emma.mdx +++ b/docs/devices-next/meters/huawei-emma.mdx @@ -2,6 +2,7 @@ title: Huawei EMMA custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-emma.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/huawei-smartlogger.mdx b/docs/devices-next/meters/huawei-smartlogger.mdx index 34b57a6b60..abc5f557bf 100644 --- a/docs/devices-next/meters/huawei-smartlogger.mdx +++ b/docs/devices-next/meters/huawei-smartlogger.mdx @@ -2,6 +2,7 @@ title: Huawei SmartLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-smartlogger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/huawei-sun2000-sdongle.mdx b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx index 0b23cbfa12..4c8c2f8c23 100644 --- a/docs/devices-next/meters/huawei-sun2000-sdongle.mdx +++ b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -2,6 +2,7 @@ title: Huawei SUN2000 (SDongle) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-dongle.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/huawei-sun2000.mdx b/docs/devices-next/meters/huawei-sun2000.mdx index 97261c3b2a..e843c2f9c6 100644 --- a/docs/devices-next/meters/huawei-sun2000.mdx +++ b/docs/devices-next/meters/huawei-sun2000.mdx @@ -2,6 +2,7 @@ title: Huawei SUN2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-sun2000.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/iammeter-wem3080.mdx b/docs/devices-next/meters/iammeter-wem3080.mdx index 5cdee38c3f..2a9d10167e 100644 --- a/docs/devices-next/meters/iammeter-wem3080.mdx +++ b/docs/devices-next/meters/iammeter-wem3080.mdx @@ -2,6 +2,7 @@ title: IAMMETER WEM3080 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx b/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx index 93ab517abc..cf6392f494 100644 --- a/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx +++ b/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -2,6 +2,7 @@ title: IAMMETER WEM3080T/WEM3046T/WEM3050T custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/igen-tech-solarman-logger.mdx b/docs/devices-next/meters/igen-tech-solarman-logger.mdx index 87d074c10e..117426db66 100644 --- a/docs/devices-next/meters/igen-tech-solarman-logger.mdx +++ b/docs/devices-next/meters/igen-tech-solarman-logger.mdx @@ -2,6 +2,7 @@ title: IGEN Tech Solarman Logger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarman.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/index.mdx b/docs/devices-next/meters/index.mdx index dae6e986c9..5dd85826df 100644 --- a/docs/devices-next/meters/index.mdx +++ b/docs/devices-next/meters/index.mdx @@ -1,6 +1,7 @@ --- title: Meters hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/docs/devices-next/meters/inepro-pro380-mod.mdx b/docs/devices-next/meters/inepro-pro380-mod.mdx index fce3407793..540458223e 100644 --- a/docs/devices-next/meters/inepro-pro380-mod.mdx +++ b/docs/devices-next/meters/inepro-pro380-mod.mdx @@ -2,6 +2,7 @@ title: inepro PRO380-MOD custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/inepro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/iometer.mdx b/docs/devices-next/meters/iometer.mdx index 8bf9978b8a..e47b6c8583 100644 --- a/docs/devices-next/meters/iometer.mdx +++ b/docs/devices-next/meters/iometer.mdx @@ -2,6 +2,7 @@ title: IOmeter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iometer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/janitza-b-series.mdx b/docs/devices-next/meters/janitza-b-series.mdx index eb0e3c3a97..d7e55d4db2 100644 --- a/docs/devices-next/meters/janitza-b-series.mdx +++ b/docs/devices-next/meters/janitza-b-series.mdx @@ -2,6 +2,7 @@ title: Janitza B series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/janitza-umg-series.mdx b/docs/devices-next/meters/janitza-umg-series.mdx index 1df501492c..af72d1c073 100644 --- a/docs/devices-next/meters/janitza-umg-series.mdx +++ b/docs/devices-next/meters/janitza-umg-series.mdx @@ -2,6 +2,7 @@ title: Janitza UMG series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/keba-kecontact-e10.mdx b/docs/devices-next/meters/keba-kecontact-e10.mdx index 0588f43f08..cc696a968f 100644 --- a/docs/devices-next/meters/keba-kecontact-e10.mdx +++ b/docs/devices-next/meters/keba-kecontact-e10.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact E10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/keba-kecontact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx index f486848d92..7d03b92fc3 100644 --- a/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx +++ b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -2,6 +2,7 @@ title: Kostal Energy Meter C (KEM-C) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx index 0cac9ea36d..ee4065b5e0 100644 --- a/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx +++ b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -2,6 +2,7 @@ title: Kostal Energy Meter P (KEM-P) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-piko-ba.mdx b/docs/devices-next/meters/kostal-piko-ba.mdx index 282b2cbb91..60a3fbfdfa 100644 --- a/docs/devices-next/meters/kostal-piko-ba.mdx +++ b/docs/devices-next/meters/kostal-piko-ba.mdx @@ -2,6 +2,7 @@ title: Kostal Piko BA custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-piko-hybrid.mdx b/docs/devices-next/meters/kostal-piko-hybrid.mdx index d4cf92ac3d..a26c42ee02 100644 --- a/docs/devices-next/meters/kostal-piko-hybrid.mdx +++ b/docs/devices-next/meters/kostal-piko-hybrid.mdx @@ -2,6 +2,7 @@ title: Kostal Piko Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-piko-legacy.mdx b/docs/devices-next/meters/kostal-piko-legacy.mdx index 8d9f7609d7..1f9685b3d4 100644 --- a/docs/devices-next/meters/kostal-piko-legacy.mdx +++ b/docs/devices-next/meters/kostal-piko-legacy.mdx @@ -2,6 +2,7 @@ title: Kostal Piko (legacy) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-legacy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-piko-mp-plus.mdx b/docs/devices-next/meters/kostal-piko-mp-plus.mdx index 2c4bd68f77..95d1306b39 100644 --- a/docs/devices-next/meters/kostal-piko-mp-plus.mdx +++ b/docs/devices-next/meters/kostal-piko-mp-plus.mdx @@ -2,6 +2,7 @@ title: Kostal Piko MP Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-piko.mdx b/docs/devices-next/meters/kostal-piko.mdx index 57b409c2ca..a99dda3ac4 100644 --- a/docs/devices-next/meters/kostal-piko.mdx +++ b/docs/devices-next/meters/kostal-piko.mdx @@ -2,6 +2,7 @@ title: Kostal Piko custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx index 31f3da614c..67eb3096a4 100644 --- a/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx +++ b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -2,6 +2,7 @@ title: Kostal Plenticore Hybrid, incl. grid charging of the house battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore-gen2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-plenticore-hybrid.mdx b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx index 672d56556d..56fc32a2e4 100644 --- a/docs/devices-next/meters/kostal-plenticore-hybrid.mdx +++ b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -2,6 +2,7 @@ title: Kostal Plenticore Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx index f7880234e1..1cff62400d 100644 --- a/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx +++ b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -2,6 +2,7 @@ title: Kostal Smart Energy Meter (via inverter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/kostal-smart-energy-meter.mdx b/docs/devices-next/meters/kostal-smart-energy-meter.mdx index aacf8adc47..067caf6b95 100644 --- a/docs/devices-next/meters/kostal-smart-energy-meter.mdx +++ b/docs/devices-next/meters/kostal-smart-energy-meter.mdx @@ -2,6 +2,7 @@ title: Kostal Smart Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/lg-ess-home-15.mdx b/docs/devices-next/meters/lg-ess-home-15.mdx index 2f5914f8e1..30abb9f4ec 100644 --- a/docs/devices-next/meters/lg-ess-home-15.mdx +++ b/docs/devices-next/meters/lg-ess-home-15.mdx @@ -2,6 +2,7 @@ title: LG ESS Home 15 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-15.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/lg-ess-home-8-10.mdx b/docs/devices-next/meters/lg-ess-home-8-10.mdx index 0485549582..3c71b4b19a 100644 --- a/docs/devices-next/meters/lg-ess-home-8-10.mdx +++ b/docs/devices-next/meters/lg-ess-home-8-10.mdx @@ -2,6 +2,7 @@ title: LG ESS Home 8/10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/loxone-miniserver.mdx b/docs/devices-next/meters/loxone-miniserver.mdx index d168b01077..a4d0911985 100644 --- a/docs/devices-next/meters/loxone-miniserver.mdx +++ b/docs/devices-next/meters/loxone-miniserver.mdx @@ -2,6 +2,7 @@ title: Loxone Miniserver custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/loxone.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx index db134f8722..62c81e7288 100644 --- a/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx +++ b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -2,6 +2,7 @@ title: M-TEC Energy Butler GEN2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx index 33a0fad342..2a49bc90e1 100644 --- a/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx +++ b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -2,6 +2,7 @@ title: M-TEC Energy Butler GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/marstek-venus-battery-storage.mdx b/docs/devices-next/meters/marstek-venus-battery-storage.mdx index 1b9af288b8..e0d29e62a8 100644 --- a/docs/devices-next/meters/marstek-venus-battery-storage.mdx +++ b/docs/devices-next/meters/marstek-venus-battery-storage.mdx @@ -2,6 +2,7 @@ title: Marstek Venus Battery Storage custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/marstek-venus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/mhendriks-p1-dongle.mdx b/docs/devices-next/meters/mhendriks-p1-dongle.mdx index 5b63e51bd5..631725fef0 100644 --- a/docs/devices-next/meters/mhendriks-p1-dongle.mdx +++ b/docs/devices-next/meters/mhendriks-p1-dongle.mdx @@ -2,6 +2,7 @@ title: mhendriks P1 dongle custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/my-pv-ac-elwa-2.mdx b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx index cdbc5ab1dc..646e22ca4b 100644 --- a/docs/devices-next/meters/my-pv-ac-elwa-2.mdx +++ b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -2,6 +2,7 @@ title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/my-pv-ac-elwa-e.mdx b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx index f6eeafa70d..992fc8c917 100644 --- a/docs/devices-next/meters/my-pv-ac-elwa-e.mdx +++ b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -2,6 +2,7 @@ title: my-PV AC ELWA-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/my-pv-ac-thor.mdx b/docs/devices-next/meters/my-pv-ac-thor.mdx index 8e04b88dac..cc5b23183f 100644 --- a/docs/devices-next/meters/my-pv-ac-thor.mdx +++ b/docs/devices-next/meters/my-pv-ac-thor.mdx @@ -2,6 +2,7 @@ title: my-PV AC•THOR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/my-pv-wifi-meter.mdx b/docs/devices-next/meters/my-pv-wifi-meter.mdx index dbdb5bc9b2..0992598773 100644 --- a/docs/devices-next/meters/my-pv-wifi-meter.mdx +++ b/docs/devices-next/meters/my-pv-wifi-meter.mdx @@ -2,6 +2,7 @@ title: my-PV WiFi Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mypv-wifi-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/mystrom-switch.mdx b/docs/devices-next/meters/mystrom-switch.mdx index 805963bd76..f0ec9bb24f 100644 --- a/docs/devices-next/meters/mystrom-switch.mdx +++ b/docs/devices-next/meters/mystrom-switch.mdx @@ -2,6 +2,7 @@ title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mystrom.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/openems.mdx b/docs/devices-next/meters/openems.mdx index 8e21a40d6d..fd9db58a72 100644 --- a/docs/devices-next/meters/openems.mdx +++ b/docs/devices-next/meters/openems.mdx @@ -2,6 +2,7 @@ title: OpenEMS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/orno-or-we-516.mdx b/docs/devices-next/meters/orno-or-we-516.mdx index 0402342539..93f2846ae5 100644 --- a/docs/devices-next/meters/orno-or-we-516.mdx +++ b/docs/devices-next/meters/orno-or-we-516.mdx @@ -2,6 +2,7 @@ title: ORNO OR-WE-516 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/orno-or-we-517.mdx b/docs/devices-next/meters/orno-or-we-517.mdx index 026cd5b403..2b26d673d4 100644 --- a/docs/devices-next/meters/orno-or-we-517.mdx +++ b/docs/devices-next/meters/orno-or-we-517.mdx @@ -2,6 +2,7 @@ title: ORNO OR-WE-517 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/p1monitor-p1-monitor.mdx b/docs/devices-next/meters/p1monitor-p1-monitor.mdx index 7c6f0ef956..83b9915c2c 100644 --- a/docs/devices-next/meters/p1monitor-p1-monitor.mdx +++ b/docs/devices-next/meters/p1monitor-p1-monitor.mdx @@ -2,6 +2,7 @@ title: P1Monitor P1 Monitor custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/plexlog.mdx b/docs/devices-next/meters/plexlog.mdx index 41b0562e26..dc6537f0ff 100644 --- a/docs/devices-next/meters/plexlog.mdx +++ b/docs/devices-next/meters/plexlog.mdx @@ -2,6 +2,7 @@ title: Plexlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/plexlog.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/powerdog.mdx b/docs/devices-next/meters/powerdog.mdx index 369aeaa887..b84e6c6786 100644 --- a/docs/devices-next/meters/powerdog.mdx +++ b/docs/devices-next/meters/powerdog.mdx @@ -2,6 +2,7 @@ title: Powerdog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerdog.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/powerfox-poweropti.mdx b/docs/devices-next/meters/powerfox-poweropti.mdx index 55b08db0cf..1648fe5f16 100644 --- a/docs/devices-next/meters/powerfox-poweropti.mdx +++ b/docs/devices-next/meters/powerfox-poweropti.mdx @@ -2,6 +2,7 @@ title: Powerfox Poweropti custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerfox-poweropti.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx index 431b4ef604..6124a27a51 100644 --- a/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx +++ b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -2,6 +2,7 @@ title: Qcells Hybrid-Inverter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/qcells-hybrid-cloud.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx b/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx index dde94a2681..6219a6f56b 100644 --- a/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx +++ b/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -2,6 +2,7 @@ title: Qcells Q.HOME ESS HYB-G3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/rct-power.mdx b/docs/devices-next/meters/rct-power.mdx index 7e5065aff2..880c3a4f30 100644 --- a/docs/devices-next/meters/rct-power.mdx +++ b/docs/devices-next/meters/rct-power.mdx @@ -2,6 +2,7 @@ title: RCT Power custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/rct-power.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx index 9482cf2818..615e9b0089 100644 --- a/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -2,6 +2,7 @@ title: Saia-Burgess Controls (SBC) ALE3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx b/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx index 0b735a0722..1698d8570f 100644 --- a/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -2,6 +2,7 @@ title: Saia-Burgess Controls (SBC) AWD3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx index 38140ad741..6c9037f9e6 100644 --- a/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -2,6 +2,7 @@ title: SAJ H1 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx index 62ef79a1b9..56b7685460 100644 --- a/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -2,6 +2,7 @@ title: SAJ H2 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx index 4aa4e4a30c..c0e7b7f683 100644 --- a/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx +++ b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -2,6 +2,7 @@ title: SAJ R5 Series Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-r5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sax-homespeicher.mdx b/docs/devices-next/meters/sax-homespeicher.mdx index 7be939fea2..14faeaaaf5 100644 --- a/docs/devices-next/meters/sax-homespeicher.mdx +++ b/docs/devices-next/meters/sax-homespeicher.mdx @@ -2,6 +2,7 @@ title: SAX Homespeicher custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx index 9468581252..05a667a607 100644 --- a/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx +++ b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -2,6 +2,7 @@ title: Schneider Electric iEM3xxx Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/schneider-iem3000.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/senec-home.mdx b/docs/devices-next/meters/senec-home.mdx index df2fde141f..6f6fd168fc 100644 --- a/docs/devices-next/meters/senec-home.mdx +++ b/docs/devices-next/meters/senec-home.mdx @@ -2,6 +2,7 @@ title: SENEC .Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senec-home.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx b/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx index beb03c94b1..9aa0cdb2bb 100644 --- a/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx +++ b/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx @@ -2,6 +2,7 @@ title: Senergy SE 4/5/6KTL-S1/G2 Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-1pm-mini.mdx b/docs/devices-next/meters/shelly-1pm-mini.mdx index b7553c0a92..bf552975d6 100644 --- a/docs/devices-next/meters/shelly-1pm-mini.mdx +++ b/docs/devices-next/meters/shelly-1pm-mini.mdx @@ -2,6 +2,7 @@ title: Shelly 1PM mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-1pm.mdx b/docs/devices-next/meters/shelly-1pm.mdx index 8dea667115..4106381fbd 100644 --- a/docs/devices-next/meters/shelly-1pm.mdx +++ b/docs/devices-next/meters/shelly-1pm.mdx @@ -2,6 +2,7 @@ title: Shelly 1PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-3em.mdx b/docs/devices-next/meters/shelly-3em.mdx index 256eb277c3..0ce521a066 100644 --- a/docs/devices-next/meters/shelly-3em.mdx +++ b/docs/devices-next/meters/shelly-3em.mdx @@ -2,6 +2,7 @@ title: Shelly 3EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-3em.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-em.mdx b/docs/devices-next/meters/shelly-em.mdx index 8616b3ce7f..bb9da022bf 100644 --- a/docs/devices-next/meters/shelly-em.mdx +++ b/docs/devices-next/meters/shelly-em.mdx @@ -2,6 +2,7 @@ title: Shelly EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-plug-s.mdx b/docs/devices-next/meters/shelly-plug-s.mdx index a28c4de0a7..72249db1c4 100644 --- a/docs/devices-next/meters/shelly-plug-s.mdx +++ b/docs/devices-next/meters/shelly-plug-s.mdx @@ -2,6 +2,7 @@ title: Shelly Plug S custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-pm-mini.mdx b/docs/devices-next/meters/shelly-pm-mini.mdx index a4915c02d5..f3e18d0332 100644 --- a/docs/devices-next/meters/shelly-pm-mini.mdx +++ b/docs/devices-next/meters/shelly-pm-mini.mdx @@ -2,6 +2,7 @@ title: Shelly PM mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-pro-1pm.mdx b/docs/devices-next/meters/shelly-pro-1pm.mdx index 8b29ddd75e..a7f4ece343 100644 --- a/docs/devices-next/meters/shelly-pro-1pm.mdx +++ b/docs/devices-next/meters/shelly-pro-1pm.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 1PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-pro-3-em.mdx b/docs/devices-next/meters/shelly-pro-3-em.mdx index 7d14b0272e..28b60203e7 100644 --- a/docs/devices-next/meters/shelly-pro-3-em.mdx +++ b/docs/devices-next/meters/shelly-pro-3-em.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 3 EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-pro-3em.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx b/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx index e6ef3db824..9f51a88034 100644 --- a/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx +++ b/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 3EM (monophase mode) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/shelly-pro-em.mdx b/docs/devices-next/meters/shelly-pro-em.mdx index 159cde1718..b9ad4e7c24 100644 --- a/docs/devices-next/meters/shelly-pro-em.mdx +++ b/docs/devices-next/meters/shelly-pro-em.mdx @@ -2,6 +2,7 @@ title: Shelly Pro EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/siemens-7kt1665.mdx b/docs/devices-next/meters/siemens-7kt1665.mdx index 9c97b8ae23..b937eb0d23 100644 --- a/docs/devices-next/meters/siemens-7kt1665.mdx +++ b/docs/devices-next/meters/siemens-7kt1665.mdx @@ -2,6 +2,7 @@ title: Siemens 7KT1665 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-7kt1665.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/siemens-junelight-smart-battery.mdx b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx index 119dcf8517..191d1fc1a5 100644 --- a/docs/devices-next/meters/siemens-junelight-smart-battery.mdx +++ b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -2,6 +2,7 @@ title: Siemens Junelight Smart Battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-junelight.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/siemens-pac-2200.mdx b/docs/devices-next/meters/siemens-pac-2200.mdx index fdc646dc25..ecde93f847 100644 --- a/docs/devices-next/meters/siemens-pac-2200.mdx +++ b/docs/devices-next/meters/siemens-pac-2200.mdx @@ -2,6 +2,7 @@ title: Siemens PAC 2200 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-pac2200.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx b/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx index 04d404335c..b8681cc233 100644 --- a/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx +++ b/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx @@ -2,6 +2,7 @@ title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-data-manager.mdx b/docs/devices-next/meters/sma-data-manager.mdx index a48f216f5b..9464f7d696 100644 --- a/docs/devices-next/meters/sma-data-manager.mdx +++ b/docs/devices-next/meters/sma-data-manager.mdx @@ -2,6 +2,7 @@ title: SMA Data Manager custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-data-manager.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-energy-meter.mdx b/docs/devices-next/meters/sma-energy-meter.mdx index d32a4834bf..9a624890a1 100644 --- a/docs/devices-next/meters/sma-energy-meter.mdx +++ b/docs/devices-next/meters/sma-energy-meter.mdx @@ -2,6 +2,7 @@ title: SMA Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-energy-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-inverter-speedwire.mdx b/docs/devices-next/meters/sma-inverter-speedwire.mdx index 970e7177b5..cdb5448c4a 100644 --- a/docs/devices-next/meters/sma-inverter-speedwire.mdx +++ b/docs/devices-next/meters/sma-inverter-speedwire.mdx @@ -2,6 +2,7 @@ title: SMA Inverter (Speedwire) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-speedwire.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx index d8a47fbdd4..7c2444e79b 100644 --- a/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SMA Smart Energy Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx index 1ccc3215fe..2188d47955 100644 --- a/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx +++ b/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx b/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx index 735b1b2065..139af3c5a1 100644 --- a/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx +++ b/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx b/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx index b7ca55961a..3c3b4704a3 100644 --- a/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx +++ b/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Home Manager 2.0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-sunny-island-modbus.mdx b/docs/devices-next/meters/sma-sunny-island-modbus.mdx index ada673ed6f..d5ebe3109e 100644 --- a/docs/devices-next/meters/sma-sunny-island-modbus.mdx +++ b/docs/devices-next/meters/sma-sunny-island-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Island (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-si-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-webbox.mdx b/docs/devices-next/meters/sma-webbox.mdx index 99ab778191..c727c50a15 100644 --- a/docs/devices-next/meters/sma-webbox.mdx +++ b/docs/devices-next/meters/sma-webbox.mdx @@ -2,6 +2,7 @@ title: SMA WebBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-webbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sma-wechselrichter-modbus.mdx b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx index fcd29f9c93..7241638247 100644 --- a/docs/devices-next/meters/sma-wechselrichter-modbus.mdx +++ b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Wechselrichter (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-box.mdx b/docs/devices-next/meters/smartfox-box.mdx index b6a15af3cd..16d5ad962e 100644 --- a/docs/devices-next/meters/smartfox-box.mdx +++ b/docs/devices-next/meters/smartfox-box.mdx @@ -2,6 +2,7 @@ title: Smartfox Box custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-light-em2-firmware.mdx b/docs/devices-next/meters/smartfox-light-em2-firmware.mdx index 3c2879514b..60e2f79100 100644 --- a/docs/devices-next/meters/smartfox-light-em2-firmware.mdx +++ b/docs/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -2,6 +2,7 @@ title: Smartfox Light (EM2 firmware) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-pro-2.mdx b/docs/devices-next/meters/smartfox-pro-2.mdx index 124fa5e93c..e34f428df8 100644 --- a/docs/devices-next/meters/smartfox-pro-2.mdx +++ b/docs/devices-next/meters/smartfox-pro-2.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-pro-light-2.mdx b/docs/devices-next/meters/smartfox-pro-light-2.mdx index 7966381266..559bd645ec 100644 --- a/docs/devices-next/meters/smartfox-pro-light-2.mdx +++ b/docs/devices-next/meters/smartfox-pro-light-2.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro Light 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-pro-light.mdx b/docs/devices-next/meters/smartfox-pro-light.mdx index b4bdcdc659..0c7df080b4 100644 --- a/docs/devices-next/meters/smartfox-pro-light.mdx +++ b/docs/devices-next/meters/smartfox-pro-light.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro Light custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-pro.mdx b/docs/devices-next/meters/smartfox-pro.mdx index f99fb3073f..4f33a694df 100644 --- a/docs/devices-next/meters/smartfox-pro.mdx +++ b/docs/devices-next/meters/smartfox-pro.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-reg-extended.mdx b/docs/devices-next/meters/smartfox-reg-extended.mdx index f42c49f1bd..6424965563 100644 --- a/docs/devices-next/meters/smartfox-reg-extended.mdx +++ b/docs/devices-next/meters/smartfox-reg-extended.mdx @@ -2,6 +2,7 @@ title: Smartfox Reg extended custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/smartfox-reg.mdx b/docs/devices-next/meters/smartfox-reg.mdx index 027fff3e8f..c5cf199d21 100644 --- a/docs/devices-next/meters/smartfox-reg.mdx +++ b/docs/devices-next/meters/smartfox-reg.mdx @@ -2,6 +2,7 @@ title: Smartfox Reg custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx b/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx index cc5a544ce3..6ed43958ef 100644 --- a/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SofarSolar Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx b/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx index 41df8075eb..e1ae7038de 100644 --- a/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx +++ b/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -2,6 +2,7 @@ title: SofarSolar HYD 3…6K-EP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx b/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx index 139d037a28..03a48c8903 100644 --- a/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx +++ b/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -2,6 +2,7 @@ title: SofarSolar HYD 5…20K-3PH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sofarsolar-inverter.mdx b/docs/devices-next/meters/sofarsolar-inverter.mdx index a29048bd50..f1625b359b 100644 --- a/docs/devices-next/meters/sofarsolar-inverter.mdx +++ b/docs/devices-next/meters/sofarsolar-inverter.mdx @@ -2,6 +2,7 @@ title: SofarSolar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx b/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx index 6515f8c45e..11501b72e0 100644 --- a/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx +++ b/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -2,6 +2,7 @@ title: SofarSolar SOFAR 5…24KTL-G3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx b/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx index d06fb170ec..afdddd98f9 100644 --- a/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx +++ b/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -2,6 +2,7 @@ title: SofarSolar SOFAR 80…136KTL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solaranzeige-solaranzeige.mdx b/docs/devices-next/meters/solaranzeige-solaranzeige.mdx index 548fe5869d..6776263cfa 100644 --- a/docs/devices-next/meters/solaranzeige-solaranzeige.mdx +++ b/docs/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -2,6 +2,7 @@ title: Solaranzeige Solaranzeige custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solaredge-hybrid-inverter.mdx b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx index b93f4bdd5f..dd2ee4232d 100644 --- a/docs/devices-next/meters/solaredge-hybrid-inverter.mdx +++ b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SolarEdge Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solaredge-inverter.mdx b/docs/devices-next/meters/solaredge-inverter.mdx index a540748517..88c359e1df 100644 --- a/docs/devices-next/meters/solaredge-inverter.mdx +++ b/docs/devices-next/meters/solaredge-inverter.mdx @@ -2,6 +2,7 @@ title: SolarEdge Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarlog.mdx b/docs/devices-next/meters/solarlog.mdx index ab26f17bd0..4245881d05 100644 --- a/docs/devices-next/meters/solarlog.mdx +++ b/docs/devices-next/meters/solarlog.mdx @@ -2,6 +2,7 @@ title: Solarlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarlog.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx b/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx index a7454e87df..b066dd1c81 100644 --- a/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx +++ b/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -2,6 +2,7 @@ title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarmax-solarmax-smt.mdx b/docs/devices-next/meters/solarmax-solarmax-smt.mdx index ac4e3a13ec..a05c6f9d54 100644 --- a/docs/devices-next/meters/solarmax-solarmax-smt.mdx +++ b/docs/devices-next/meters/solarmax-solarmax-smt.mdx @@ -2,6 +2,7 @@ title: SolarMax SolarMax SMT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-smt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarmax-sp-series-inverter.mdx b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx index 2a2c1f014f..50f430aa81 100644 --- a/docs/devices-next/meters/solarmax-sp-series-inverter.mdx +++ b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -2,6 +2,7 @@ title: SolarMax SP Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarwatt-energymanager-pro.mdx b/docs/devices-next/meters/solarwatt-energymanager-pro.mdx index bca4fc8c03..bd36a9e39f 100644 --- a/docs/devices-next/meters/solarwatt-energymanager-pro.mdx +++ b/docs/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -2,6 +2,7 @@ title: Solarwatt EnergyManager Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarwatt-energymanager.mdx b/docs/devices-next/meters/solarwatt-energymanager.mdx index cec7c37a94..5c45838c47 100644 --- a/docs/devices-next/meters/solarwatt-energymanager.mdx +++ b/docs/devices-next/meters/solarwatt-energymanager.mdx @@ -2,6 +2,7 @@ title: Solarwatt EnergyManager custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarwatt-manager-flex.mdx b/docs/devices-next/meters/solarwatt-manager-flex.mdx index 4d59036d6a..bfe74ca714 100644 --- a/docs/devices-next/meters/solarwatt-manager-flex.mdx +++ b/docs/devices-next/meters/solarwatt-manager-flex.mdx @@ -2,6 +2,7 @@ title: Solarwatt Manager flex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-flex.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx index 6362688a8a..4d2838b556 100644 --- a/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx +++ b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -2,6 +2,7 @@ title: Solarwatt MyReserve Matrix (LAN oder PowerGateway) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-myreserve-matrix.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solarwatt-myreserve.mdx b/docs/devices-next/meters/solarwatt-myreserve.mdx index 91a3d9c580..567e24d320 100644 --- a/docs/devices-next/meters/solarwatt-myreserve.mdx +++ b/docs/devices-next/meters/solarwatt-myreserve.mdx @@ -2,6 +2,7 @@ title: Solarwatt MyReserve custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx index 493b3a069a..bb9c9e654e 100644 --- a/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx +++ b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -2,6 +2,7 @@ title: Solax Hybrid-Inverter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-hybrid-cloud.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx b/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx index 57834d2a3c..9762186fc7 100644 --- a/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx +++ b/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -2,6 +2,7 @@ title: Solax Hybrid X1/X3 G3/G4 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solax-inverter-cloud.mdx b/docs/devices-next/meters/solax-inverter-cloud.mdx index d6e2184487..68d2064f80 100644 --- a/docs/devices-next/meters/solax-inverter-cloud.mdx +++ b/docs/devices-next/meters/solax-inverter-cloud.mdx @@ -2,6 +2,7 @@ title: Solax Inverter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-inverter-cloud.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/solinteng.mdx b/docs/devices-next/meters/solinteng.mdx index 7974b05180..6cd847049f 100644 --- a/docs/devices-next/meters/solinteng.mdx +++ b/docs/devices-next/meters/solinteng.mdx @@ -2,6 +2,7 @@ title: Solinteng custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sonnen-comfort.mdx b/docs/devices-next/meters/sonnen-comfort.mdx index 9778789aba..b5381ef9e8 100644 --- a/docs/devices-next/meters/sonnen-comfort.mdx +++ b/docs/devices-next/meters/sonnen-comfort.mdx @@ -2,6 +2,7 @@ title: Sonnen comfort custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sonnen-eco-5.mdx b/docs/devices-next/meters/sonnen-eco-5.mdx index 483807f3e8..1a606993a0 100644 --- a/docs/devices-next/meters/sonnen-eco-5.mdx +++ b/docs/devices-next/meters/sonnen-eco-5.mdx @@ -2,6 +2,7 @@ title: Sonnen eco 5 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sonnen-eco-6.mdx b/docs/devices-next/meters/sonnen-eco-6.mdx index 39023ca6fc..9a25b5cafb 100644 --- a/docs/devices-next/meters/sonnen-eco-6.mdx +++ b/docs/devices-next/meters/sonnen-eco-6.mdx @@ -2,6 +2,7 @@ title: Sonnen eco 6 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sonnen-oem-6-5.mdx b/docs/devices-next/meters/sonnen-oem-6-5.mdx index 8f294eaa80..398363002c 100644 --- a/docs/devices-next/meters/sonnen-oem-6-5.mdx +++ b/docs/devices-next/meters/sonnen-oem-6-5.mdx @@ -2,6 +2,7 @@ title: Sonnen oem 6.5 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sonnen-sonnenbatterie.mdx b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx index 24c187cb97..9033184774 100644 --- a/docs/devices-next/meters/sonnen-sonnenbatterie.mdx +++ b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -2,6 +2,7 @@ title: Sonnen sonnenBatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/st-ems.mdx b/docs/devices-next/meters/st-ems.mdx index 6bd31afc4f..4bdc46294e 100644 --- a/docs/devices-next/meters/st-ems.mdx +++ b/docs/devices-next/meters/st-ems.mdx @@ -2,6 +2,7 @@ title: St-ems custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/steca-coolcept-flex.mdx b/docs/devices-next/meters/steca-coolcept-flex.mdx index 4a4cdcdb91..37b35c6c21 100644 --- a/docs/devices-next/meters/steca-coolcept-flex.mdx +++ b/docs/devices-next/meters/steca-coolcept-flex.mdx @@ -2,6 +2,7 @@ title: Steca coolcept fleX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sungrow-sg-series-inverter.mdx b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx index 0597176918..6b443ec4df 100644 --- a/docs/devices-next/meters/sungrow-sg-series-inverter.mdx +++ b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -2,6 +2,7 @@ title: Sungrow SG Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx index c4816b56dd..5f1d8ea4aa 100644 --- a/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sungrow SH Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunspec-battery-model-124.mdx b/docs/devices-next/meters/sunspec-battery-model-124.mdx index b8e3f4f913..49f10291f8 100644 --- a/docs/devices-next/meters/sunspec-battery-model-124.mdx +++ b/docs/devices-next/meters/sunspec-battery-model-124.mdx @@ -2,6 +2,7 @@ title: SunSpec Battery (Model 124) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter-control.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunspec-battery-model-802.mdx b/docs/devices-next/meters/sunspec-battery-model-802.mdx index 5383f5fc07..b8491464d4 100644 --- a/docs/devices-next/meters/sunspec-battery-model-802.mdx +++ b/docs/devices-next/meters/sunspec-battery-model-802.mdx @@ -2,6 +2,7 @@ title: SunSpec Battery (Model 802) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-battery-control.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunspec-hybrid-inverter.mdx b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx index 48dab01eea..5f56a78897 100644 --- a/docs/devices-next/meters/sunspec-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SunSpec Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunspec-inverter.mdx b/docs/devices-next/meters/sunspec-inverter.mdx index d0fa66a1b8..6c2fb7e12f 100644 --- a/docs/devices-next/meters/sunspec-inverter.mdx +++ b/docs/devices-next/meters/sunspec-inverter.mdx @@ -2,6 +2,7 @@ title: SunSpec Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunspec-meter.mdx b/docs/devices-next/meters/sunspec-meter.mdx index 51c0e80210..0f2da8f17e 100644 --- a/docs/devices-next/meters/sunspec-meter.mdx +++ b/docs/devices-next/meters/sunspec-meter.mdx @@ -2,6 +2,7 @@ title: SunSpec Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx index c241316a32..3a58d86e63 100644 --- a/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx index db72673352..f772dfd98f 100644 --- a/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunsynk-micro-inverter.mdx b/docs/devices-next/meters/sunsynk-micro-inverter.mdx index 158a3da870..b5d05c9043 100644 --- a/docs/devices-next/meters/sunsynk-micro-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx index fc0e1c29a1..5fd8a30c3e 100644 --- a/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunsynk-string-inverter.mdx b/docs/devices-next/meters/sunsynk-string-inverter.mdx index a3fa141614..e88f300265 100644 --- a/docs/devices-next/meters/sunsynk-string-inverter.mdx +++ b/docs/devices-next/meters/sunsynk-string-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/sunway.mdx b/docs/devices-next/meters/sunway.mdx index 18dec73bcc..1551aa08d9 100644 --- a/docs/devices-next/meters/sunway.mdx +++ b/docs/devices-next/meters/sunway.mdx @@ -2,6 +2,7 @@ title: Sunway custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx index 89048a63d4..6b5abc608c 100644 --- a/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx +++ b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx @@ -2,6 +2,7 @@ title: Tasmota SML IR-reader for smartmeters e.g. Hichi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx b/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx index ec6b3f7621..5e1dc685ba 100644 --- a/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx +++ b/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -2,6 +2,7 @@ title: Tasmota Tasmota (1 Phase + SML Meter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tasmota-three-phase.mdx b/docs/devices-next/meters/tasmota-three-phase.mdx index af3536b161..e777d9d85e 100644 --- a/docs/devices-next/meters/tasmota-three-phase.mdx +++ b/docs/devices-next/meters/tasmota-three-phase.mdx @@ -2,6 +2,7 @@ title: Tasmota three phase custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-3p.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tesla-powerwall.mdx b/docs/devices-next/meters/tesla-powerwall.mdx index 5dd371f575..03b2bde32f 100644 --- a/docs/devices-next/meters/tesla-powerwall.mdx +++ b/docs/devices-next/meters/tesla-powerwall.mdx @@ -2,6 +2,7 @@ title: Tesla Powerwall custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tesla-powerwall.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tibber-pulse.mdx b/docs/devices-next/meters/tibber-pulse.mdx index ed245cfa67..36a912bee1 100644 --- a/docs/devices-next/meters/tibber-pulse.mdx +++ b/docs/devices-next/meters/tibber-pulse.mdx @@ -2,6 +2,7 @@ title: Tibber Pulse custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tibber-pulse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx index 060a54b5f6..1312e4ab5f 100644 --- a/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx +++ b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tplink.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx index 3cf65ae1bf..e96e18da76 100644 --- a/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx +++ b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tapo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx b/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx index 68f71d7e6d..ac26786217 100644 --- a/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx +++ b/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -2,6 +2,7 @@ title: TQ Energy Manager EM2xx/EM3xx custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/tq-energy-manager-em420.mdx b/docs/devices-next/meters/tq-energy-manager-em420.mdx index 21bf495ca8..aecef83d02 100644 --- a/docs/devices-next/meters/tq-energy-manager-em420.mdx +++ b/docs/devices-next/meters/tq-energy-manager-em420.mdx @@ -2,6 +2,7 @@ title: TQ Energy Manager EM420 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em420.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/varta-element.mdx b/docs/devices-next/meters/varta-element.mdx index 7377527786..0187220995 100644 --- a/docs/devices-next/meters/varta-element.mdx +++ b/docs/devices-next/meters/varta-element.mdx @@ -2,6 +2,7 @@ title: VARTA element custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/varta-pulse-neo.mdx b/docs/devices-next/meters/varta-pulse-neo.mdx index e3acc11ab0..c71555cac6 100644 --- a/docs/devices-next/meters/varta-pulse-neo.mdx +++ b/docs/devices-next/meters/varta-pulse-neo.mdx @@ -2,6 +2,7 @@ title: VARTA pulse neo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/varta-pulse.mdx b/docs/devices-next/meters/varta-pulse.mdx index 251514e49c..fc2a0da405 100644 --- a/docs/devices-next/meters/varta-pulse.mdx +++ b/docs/devices-next/meters/varta-pulse.mdx @@ -2,6 +2,7 @@ title: VARTA pulse custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/victron-em24.mdx b/docs/devices-next/meters/victron-em24.mdx index 0380d187b8..5639bd7e75 100644 --- a/docs/devices-next/meters/victron-em24.mdx +++ b/docs/devices-next/meters/victron-em24.mdx @@ -2,6 +2,7 @@ title: Victron EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/victron-em24_e1.mdx b/docs/devices-next/meters/victron-em24_e1.mdx index 0d6e7a0bc5..680a897763 100644 --- a/docs/devices-next/meters/victron-em24_e1.mdx +++ b/docs/devices-next/meters/victron-em24_e1.mdx @@ -2,6 +2,7 @@ title: Victron EM24_E1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/victron-em530-em540.mdx b/docs/devices-next/meters/victron-em530-em540.mdx index 19085770b4..d5c2d6a243 100644 --- a/docs/devices-next/meters/victron-em530-em540.mdx +++ b/docs/devices-next/meters/victron-em530-em540.mdx @@ -2,6 +2,7 @@ title: Victron EM530/EM540 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/victron-energy.mdx b/docs/devices-next/meters/victron-energy.mdx index 692b270154..d57fcc32be 100644 --- a/docs/devices-next/meters/victron-energy.mdx +++ b/docs/devices-next/meters/victron-energy.mdx @@ -2,6 +2,7 @@ title: Victron Energy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/victron-energy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/victron-et340.mdx b/docs/devices-next/meters/victron-et340.mdx index 3986b664f4..8f1e27bcec 100644 --- a/docs/devices-next/meters/victron-et340.mdx +++ b/docs/devices-next/meters/victron-et340.mdx @@ -2,6 +2,7 @@ title: Victron ET340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx index ca17c6ba18..041be7169b 100644 --- a/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx +++ b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -2,6 +2,7 @@ title: Volkszähler HTTP API, Import & Export custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-importexport.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/volkszahler-http-api.mdx b/docs/devices-next/meters/volkszahler-http-api.mdx index 11d897da09..6ee490ead4 100644 --- a/docs/devices-next/meters/volkszahler-http-api.mdx +++ b/docs/devices-next/meters/volkszahler-http-api.mdx @@ -2,6 +2,7 @@ title: Volkszähler HTTP API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-http.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/volkszahler-websocket-api.mdx b/docs/devices-next/meters/volkszahler-websocket-api.mdx index cbb39318eb..c3b2d5b6c0 100644 --- a/docs/devices-next/meters/volkszahler-websocket-api.mdx +++ b/docs/devices-next/meters/volkszahler-websocket-api.mdx @@ -2,6 +2,7 @@ title: Volkszähler WebSocket API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-ws.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/vzlogger.mdx b/docs/devices-next/meters/vzlogger.mdx index d4d18c7214..2b8d2dbb08 100644 --- a/docs/devices-next/meters/vzlogger.mdx +++ b/docs/devices-next/meters/vzlogger.mdx @@ -2,6 +2,7 @@ title: vzlogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/vzlogger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/wago-879-30xx.mdx b/docs/devices-next/meters/wago-879-30xx.mdx index 34e5e731b2..99c6722d82 100644 --- a/docs/devices-next/meters/wago-879-30xx.mdx +++ b/docs/devices-next/meters/wago-879-30xx.mdx @@ -2,6 +2,7 @@ title: Wago 879-30xx custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wago-879-30xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/wattsonic.mdx b/docs/devices-next/meters/wattsonic.mdx index 49e45eb806..d9e5bef6a3 100644 --- a/docs/devices-next/meters/wattsonic.mdx +++ b/docs/devices-next/meters/wattsonic.mdx @@ -2,6 +2,7 @@ title: Wattsonic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx index d64def5380..17f9887c19 100644 --- a/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM110-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx index af44e1e367..44c8cb21f2 100644 --- a/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM111-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx index fb30b0ad7a..4e0bf0a926 100644 --- a/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM120-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx index 5e97dbf67e..4ab0bf3d42 100644 --- a/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx +++ b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM122-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/youless-energy-monitor.mdx b/docs/devices-next/meters/youless-energy-monitor.mdx index f9bd671196..3469f9cd26 100644 --- a/docs/devices-next/meters/youless-energy-monitor.mdx +++ b/docs/devices-next/meters/youless-energy-monitor.mdx @@ -2,6 +2,7 @@ title: Youless Energy Monitor custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/youless.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx index 95bde4cbab..a6590f0c82 100644 --- a/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx +++ b/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: ZCS Azzurro Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/zcs-azzurro-inverter.mdx b/docs/devices-next/meters/zcs-azzurro-inverter.mdx index 46f44f9482..44661ba0ce 100644 --- a/docs/devices-next/meters/zcs-azzurro-inverter.mdx +++ b/docs/devices-next/meters/zcs-azzurro-inverter.mdx @@ -2,6 +2,7 @@ title: ZCS Azzurro Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/zendure-hyper-2000.mdx b/docs/devices-next/meters/zendure-hyper-2000.mdx index 546f91641e..9295f6fb86 100644 --- a/docs/devices-next/meters/zendure-hyper-2000.mdx +++ b/docs/devices-next/meters/zendure-hyper-2000.mdx @@ -2,6 +2,7 @@ title: Zendure Hyper 2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/zendure.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx index 4f9a1386a9..38ac3ab6fb 100644 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -2,6 +2,7 @@ title: Zuidwijk SlimmeLezer(+) in Luxembourg custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx index d8c559670a..0430085b37 100644 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -2,6 +2,7 @@ title: Zuidwijk SlimmeLezer(+) V2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx b/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx index d1d844e41e..b80de19cdd 100644 --- a/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -2,6 +2,7 @@ title: Zuidwijk SlimmeLezer(+) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/amber-electric.mdx b/docs/devices-next/tariffs/amber-electric.mdx index f73bcfd2aa..933c2286e1 100644 --- a/docs/devices-next/tariffs/amber-electric.mdx +++ b/docs/devices-next/tariffs/amber-electric.mdx @@ -2,6 +2,7 @@ title: Amber Electric custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/amber.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/awattar.mdx b/docs/devices-next/tariffs/awattar.mdx index 6efe4038bb..052a9a9872 100644 --- a/docs/devices-next/tariffs/awattar.mdx +++ b/docs/devices-next/tariffs/awattar.mdx @@ -2,6 +2,7 @@ title: Awattar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/awattar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx index 20a5c85031..498b9de887 100644 --- a/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx +++ b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -2,6 +2,7 @@ title: Electricity Maps Commercial API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/electricity-maps-free-api.mdx b/docs/devices-next/tariffs/electricity-maps-free-api.mdx index 0013da1fba..0e58a05ec4 100644 --- a/docs/devices-next/tariffs/electricity-maps-free-api.mdx +++ b/docs/devices-next/tariffs/electricity-maps-free-api.mdx @@ -2,6 +2,7 @@ title: Electricity Maps Free API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps-free.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/energinet.mdx b/docs/devices-next/tariffs/energinet.mdx index 4691b84e55..9f6a32d113 100644 --- a/docs/devices-next/tariffs/energinet.mdx +++ b/docs/devices-next/tariffs/energinet.mdx @@ -2,6 +2,7 @@ title: Energinet custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energinet.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/enever.mdx b/docs/devices-next/tariffs/enever.mdx index 6970506e3a..d660faf03f 100644 --- a/docs/devices-next/tariffs/enever.mdx +++ b/docs/devices-next/tariffs/enever.mdx @@ -2,6 +2,7 @@ title: Enever custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/enever.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/entso-e.mdx b/docs/devices-next/tariffs/entso-e.mdx index b35a19c8a9..5abbcce5c8 100644 --- a/docs/devices-next/tariffs/entso-e.mdx +++ b/docs/devices-next/tariffs/entso-e.mdx @@ -2,6 +2,7 @@ title: ENTSO-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/entsoe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/forecast-solar.mdx b/docs/devices-next/tariffs/forecast-solar.mdx index 576dc50e20..040753235d 100644 --- a/docs/devices-next/tariffs/forecast-solar.mdx +++ b/docs/devices-next/tariffs/forecast-solar.mdx @@ -2,6 +2,7 @@ title: Forecast.Solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/fraunhofer-ise.mdx b/docs/devices-next/tariffs/fraunhofer-ise.mdx index ecdda8254d..f4454f1a7c 100644 --- a/docs/devices-next/tariffs/fraunhofer-ise.mdx +++ b/docs/devices-next/tariffs/fraunhofer-ise.mdx @@ -2,6 +2,7 @@ title: Fraunhofer ISE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energy-charts-api.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/green-grid-compass.mdx b/docs/devices-next/tariffs/green-grid-compass.mdx index eef8bc2a03..6fa9141298 100644 --- a/docs/devices-next/tariffs/green-grid-compass.mdx +++ b/docs/devices-next/tariffs/green-grid-compass.mdx @@ -2,6 +2,7 @@ title: Green Grid Compass custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/green-grid-compass.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/groupe-e-vario-plus.mdx b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx index 6cbba1ac06..ec5c64e8bc 100644 --- a/docs/devices-next/tariffs/groupe-e-vario-plus.mdx +++ b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -2,6 +2,7 @@ title: Groupe E Vario Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/groupe-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/grunstromindex.mdx b/docs/devices-next/tariffs/grunstromindex.mdx index af0df49b25..52da151949 100644 --- a/docs/devices-next/tariffs/grunstromindex.mdx +++ b/docs/devices-next/tariffs/grunstromindex.mdx @@ -2,6 +2,7 @@ title: Grünstromindex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/grünstromindex.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/index.mdx b/docs/devices-next/tariffs/index.mdx index f75f1d80c9..a57cb00b62 100644 --- a/docs/devices-next/tariffs/index.mdx +++ b/docs/devices-next/tariffs/index.mdx @@ -1,6 +1,7 @@ --- title: Tariffs hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/docs/devices-next/tariffs/national-grid-eso.mdx b/docs/devices-next/tariffs/national-grid-eso.mdx index 0e34302899..0fe17a02ff 100644 --- a/docs/devices-next/tariffs/national-grid-eso.mdx +++ b/docs/devices-next/tariffs/national-grid-eso.mdx @@ -2,6 +2,7 @@ title: National Grid ESO custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ngeso.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/nordpool-spot-prices.mdx b/docs/devices-next/tariffs/nordpool-spot-prices.mdx index 0234f8f0b7..34836ad0ac 100644 --- a/docs/devices-next/tariffs/nordpool-spot-prices.mdx +++ b/docs/devices-next/tariffs/nordpool-spot-prices.mdx @@ -2,6 +2,7 @@ title: Nordpool spot prices custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/nordpool.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/octopus-energy-api.mdx b/docs/devices-next/tariffs/octopus-energy-api.mdx index 8c5546faaf..7bb107ce18 100644 --- a/docs/devices-next/tariffs/octopus-energy-api.mdx +++ b/docs/devices-next/tariffs/octopus-energy-api.mdx @@ -2,6 +2,7 @@ title: Octopus Energy API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-api.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/octopus-energy-product-code.mdx b/docs/devices-next/tariffs/octopus-energy-product-code.mdx index 9c9f4f233d..e68f6003ce 100644 --- a/docs/devices-next/tariffs/octopus-energy-product-code.mdx +++ b/docs/devices-next/tariffs/octopus-energy-product-code.mdx @@ -2,6 +2,7 @@ title: Octopus Energy Product Code custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-productcode.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/open-meteo.mdx b/docs/devices-next/tariffs/open-meteo.mdx index 2672e3444f..5bac053bb0 100644 --- a/docs/devices-next/tariffs/open-meteo.mdx +++ b/docs/devices-next/tariffs/open-meteo.mdx @@ -2,6 +2,7 @@ title: Open-Meteo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/open-meteo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/ostrom.mdx b/docs/devices-next/tariffs/ostrom.mdx index 8be10c196f..f4085af75c 100644 --- a/docs/devices-next/tariffs/ostrom.mdx +++ b/docs/devices-next/tariffs/ostrom.mdx @@ -2,6 +2,7 @@ title: Ostrom custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ostrom.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/pun-orario.mdx b/docs/devices-next/tariffs/pun-orario.mdx index 33d6ff9da7..cad4ea15ea 100644 --- a/docs/devices-next/tariffs/pun-orario.mdx +++ b/docs/devices-next/tariffs/pun-orario.mdx @@ -2,6 +2,7 @@ title: PUN Orario custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/pun.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx index ff6b6db802..405ec95353 100644 --- a/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx +++ b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -2,6 +2,7 @@ title: SmartEnergy smartCONTROL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/smartenergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/solcast.mdx b/docs/devices-next/tariffs/solcast.mdx index 89282cee7d..08efc85f14 100644 --- a/docs/devices-next/tariffs/solcast.mdx +++ b/docs/devices-next/tariffs/solcast.mdx @@ -2,6 +2,7 @@ title: Solcast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/solcast.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/spotty-energie.mdx b/docs/devices-next/tariffs/spotty-energie.mdx index 47268540de..d8f72e8a5e 100644 --- a/docs/devices-next/tariffs/spotty-energie.mdx +++ b/docs/devices-next/tariffs/spotty-energie.mdx @@ -2,6 +2,7 @@ title: Spotty Energie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/spottyenergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/tibber.mdx b/docs/devices-next/tariffs/tibber.mdx index 53b45613de..e1ddc5fa2e 100644 --- a/docs/devices-next/tariffs/tibber.mdx +++ b/docs/devices-next/tariffs/tibber.mdx @@ -2,6 +2,7 @@ title: Tibber custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/tibber.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx index ef4392bc2b..9ddd628132 100644 --- a/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx +++ b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -2,6 +2,7 @@ title: Victron VRM Solar Forecast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/victron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/aiways.mdx b/docs/devices-next/vehicles/aiways.mdx index 9f4598895b..41f63fd314 100644 --- a/docs/devices-next/vehicles/aiways.mdx +++ b/docs/devices-next/vehicles/aiways.mdx @@ -2,6 +2,7 @@ title: Aiways custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/aiways.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/audi.mdx b/docs/devices-next/vehicles/audi.mdx index 79c3c42c78..9ffa02e7d2 100644 --- a/docs/devices-next/vehicles/audi.mdx +++ b/docs/devices-next/vehicles/audi.mdx @@ -2,6 +2,7 @@ title: Audi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/audi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/bmw.mdx b/docs/devices-next/vehicles/bmw.mdx index bfecdead27..80d3096c0f 100644 --- a/docs/devices-next/vehicles/bmw.mdx +++ b/docs/devices-next/vehicles/bmw.mdx @@ -2,6 +2,7 @@ title: BMW custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/bmw.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/citroen.mdx b/docs/devices-next/vehicles/citroen.mdx index c4e7da9672..e9f4d38e9f 100644 --- a/docs/devices-next/vehicles/citroen.mdx +++ b/docs/devices-next/vehicles/citroen.mdx @@ -2,6 +2,7 @@ title: Citroën custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/citroen.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/dacia.mdx b/docs/devices-next/vehicles/dacia.mdx index 2484ffc17b..a6fb489708 100644 --- a/docs/devices-next/vehicles/dacia.mdx +++ b/docs/devices-next/vehicles/dacia.mdx @@ -2,6 +2,7 @@ title: Dacia custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/dacia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/ds.mdx b/docs/devices-next/vehicles/ds.mdx index 30da4f9eaf..675e1a663e 100644 --- a/docs/devices-next/vehicles/ds.mdx +++ b/docs/devices-next/vehicles/ds.mdx @@ -2,6 +2,7 @@ title: DS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ds.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/evnotify.mdx b/docs/devices-next/vehicles/evnotify.mdx index 5338560111..a7aec9f8bf 100644 --- a/docs/devices-next/vehicles/evnotify.mdx +++ b/docs/devices-next/vehicles/evnotify.mdx @@ -2,6 +2,7 @@ title: evNotify custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/evnotify.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/fiat.mdx b/docs/devices-next/vehicles/fiat.mdx index 8dca70a9e8..e2ea62a999 100644 --- a/docs/devices-next/vehicles/fiat.mdx +++ b/docs/devices-next/vehicles/fiat.mdx @@ -2,6 +2,7 @@ title: Fiat custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/ford.mdx b/docs/devices-next/vehicles/ford.mdx index 1d13fa0a2f..6228e05fbb 100644 --- a/docs/devices-next/vehicles/ford.mdx +++ b/docs/devices-next/vehicles/ford.mdx @@ -2,6 +2,7 @@ title: Ford custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ford-connect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/generic-vehicle-without-api.mdx b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx index 4793ccec9f..bcf54e6e46 100644 --- a/docs/devices-next/vehicles/generic-vehicle-without-api.mdx +++ b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -2,6 +2,7 @@ title: Generic vehicle (without API) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/offline.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/hyundai-bluelink.mdx b/docs/devices-next/vehicles/hyundai-bluelink.mdx index 58ff10bfae..9629cec65e 100644 --- a/docs/devices-next/vehicles/hyundai-bluelink.mdx +++ b/docs/devices-next/vehicles/hyundai-bluelink.mdx @@ -2,6 +2,7 @@ title: Hyundai Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/hyundai.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/index.mdx b/docs/devices-next/vehicles/index.mdx index d5d2e93d85..6497e8b840 100644 --- a/docs/devices-next/vehicles/index.mdx +++ b/docs/devices-next/vehicles/index.mdx @@ -1,6 +1,7 @@ --- title: Vehicles hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/docs/devices-next/vehicles/iobroker-bmw.mdx b/docs/devices-next/vehicles/iobroker-bmw.mdx index f7aad5547c..0b046c0242 100644 --- a/docs/devices-next/vehicles/iobroker-bmw.mdx +++ b/docs/devices-next/vehicles/iobroker-bmw.mdx @@ -2,6 +2,7 @@ title: ioBroker.bmw custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ioBroker.bmw.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/iso15118.mdx b/docs/devices-next/vehicles/iso15118.mdx index de933abd69..1bd1425f9a 100644 --- a/docs/devices-next/vehicles/iso15118.mdx +++ b/docs/devices-next/vehicles/iso15118.mdx @@ -2,6 +2,7 @@ title: ISO15118 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/iso15118.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/jeep.mdx b/docs/devices-next/vehicles/jeep.mdx index 7578580071..0c1113bcf8 100644 --- a/docs/devices-next/vehicles/jeep.mdx +++ b/docs/devices-next/vehicles/jeep.mdx @@ -2,6 +2,7 @@ title: Jeep custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/kia-bluelink.mdx b/docs/devices-next/vehicles/kia-bluelink.mdx index 680dbedc66..311b5bc018 100644 --- a/docs/devices-next/vehicles/kia-bluelink.mdx +++ b/docs/devices-next/vehicles/kia-bluelink.mdx @@ -2,6 +2,7 @@ title: Kia Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/kia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/mercedes-benz.mdx b/docs/devices-next/vehicles/mercedes-benz.mdx index c2727e6bd0..a798a5e57f 100644 --- a/docs/devices-next/vehicles/mercedes-benz.mdx +++ b/docs/devices-next/vehicles/mercedes-benz.mdx @@ -2,6 +2,7 @@ title: Mercedes-Benz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mercedes.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/mg.mdx b/docs/devices-next/vehicles/mg.mdx index d994ca0e0f..b35a5980af 100644 --- a/docs/devices-next/vehicles/mg.mdx +++ b/docs/devices-next/vehicles/mg.mdx @@ -2,6 +2,7 @@ title: MG custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/mg2mqtt.mdx b/docs/devices-next/vehicles/mg2mqtt.mdx index a02144f32d..3df70f2c74 100644 --- a/docs/devices-next/vehicles/mg2mqtt.mdx +++ b/docs/devices-next/vehicles/mg2mqtt.mdx @@ -2,6 +2,7 @@ title: mg2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg2mqtt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/mini.mdx b/docs/devices-next/vehicles/mini.mdx index 322d9915ed..613be80d46 100644 --- a/docs/devices-next/vehicles/mini.mdx +++ b/docs/devices-next/vehicles/mini.mdx @@ -2,6 +2,7 @@ title: Mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mini.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/mz2mqtt.mdx b/docs/devices-next/vehicles/mz2mqtt.mdx index e80041d23b..be73ba320d 100644 --- a/docs/devices-next/vehicles/mz2mqtt.mdx +++ b/docs/devices-next/vehicles/mz2mqtt.mdx @@ -2,6 +2,7 @@ title: mz2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mz2mqtt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/nissan-ariya.mdx b/docs/devices-next/vehicles/nissan-ariya.mdx index 4c5d24ce5c..f12699a470 100644 --- a/docs/devices-next/vehicles/nissan-ariya.mdx +++ b/docs/devices-next/vehicles/nissan-ariya.mdx @@ -2,6 +2,7 @@ title: Nissan Ariya custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan-ariya.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx index 23d8478d78..b3e7f07889 100644 --- a/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx +++ b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -2,6 +2,7 @@ title: Nissan Leaf (pre 2019) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/carwings.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/nissan-leaf.mdx b/docs/devices-next/vehicles/nissan-leaf.mdx index 5f45726671..5250647a3c 100644 --- a/docs/devices-next/vehicles/nissan-leaf.mdx +++ b/docs/devices-next/vehicles/nissan-leaf.mdx @@ -2,6 +2,7 @@ title: Nissan Leaf custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/niu-e-scooter.mdx b/docs/devices-next/vehicles/niu-e-scooter.mdx index bb5e560c6c..930abf9a24 100644 --- a/docs/devices-next/vehicles/niu-e-scooter.mdx +++ b/docs/devices-next/vehicles/niu-e-scooter.mdx @@ -2,6 +2,7 @@ title: NIU E-Scooter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/niu-e-scooter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/opel.mdx b/docs/devices-next/vehicles/opel.mdx index 6e5fa48187..e79bbe0f29 100644 --- a/docs/devices-next/vehicles/opel.mdx +++ b/docs/devices-next/vehicles/opel.mdx @@ -2,6 +2,7 @@ title: Opel custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/opel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx index d1dec8ba23..bcb9c6695b 100644 --- a/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx +++ b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -2,6 +2,7 @@ title: Open Vehicle Monitoring System custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ovms.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/peugeot.mdx b/docs/devices-next/vehicles/peugeot.mdx index 8426456057..c98164212d 100644 --- a/docs/devices-next/vehicles/peugeot.mdx +++ b/docs/devices-next/vehicles/peugeot.mdx @@ -2,6 +2,7 @@ title: Peugeot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/peugeot.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/polestar.mdx b/docs/devices-next/vehicles/polestar.mdx index 3cf2a1d002..108c5270ad 100644 --- a/docs/devices-next/vehicles/polestar.mdx +++ b/docs/devices-next/vehicles/polestar.mdx @@ -2,6 +2,7 @@ title: Polestar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/polestar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/psa-car-controller.mdx b/docs/devices-next/vehicles/psa-car-controller.mdx index 0a9414c5e2..4cd8054ffe 100644 --- a/docs/devices-next/vehicles/psa-car-controller.mdx +++ b/docs/devices-next/vehicles/psa-car-controller.mdx @@ -2,6 +2,7 @@ title: PSA Car Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/flobz.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/renault.mdx b/docs/devices-next/vehicles/renault.mdx index 73b974f095..fc6c8915c2 100644 --- a/docs/devices-next/vehicles/renault.mdx +++ b/docs/devices-next/vehicles/renault.mdx @@ -2,6 +2,7 @@ title: Renault custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/renault.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx index d2b03b7a7d..7272fec6e0 100644 --- a/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -2,6 +2,7 @@ title: Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/seat.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx index a6d85c5e62..46f8dcbc5b 100644 --- a/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -2,6 +2,7 @@ title: Seat CupraConnect Gen4 (Born, Formentor, Tavascan) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/cupra.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/skoda-enyaq.mdx b/docs/devices-next/vehicles/skoda-enyaq.mdx index b18fccad75..52af19af45 100644 --- a/docs/devices-next/vehicles/skoda-enyaq.mdx +++ b/docs/devices-next/vehicles/skoda-enyaq.mdx @@ -2,6 +2,7 @@ title: Skoda Enyaq custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/enyaq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/smart-1.mdx b/docs/devices-next/vehicles/smart-1.mdx index 48647c51a6..23269b35e9 100644 --- a/docs/devices-next/vehicles/smart-1.mdx +++ b/docs/devices-next/vehicles/smart-1.mdx @@ -2,6 +2,7 @@ title: Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/smart-eq.mdx b/docs/devices-next/vehicles/smart-eq.mdx index fa63588d1a..8e59a9ff4d 100644 --- a/docs/devices-next/vehicles/smart-eq.mdx +++ b/docs/devices-next/vehicles/smart-eq.mdx @@ -2,6 +2,7 @@ title: Smart EQ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/tesla-ble.mdx b/docs/devices-next/vehicles/tesla-ble.mdx index 81bbdc3c97..515f423fe4 100644 --- a/docs/devices-next/vehicles/tesla-ble.mdx +++ b/docs/devices-next/vehicles/tesla-ble.mdx @@ -2,6 +2,7 @@ title: Tesla BLE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla-ble.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/tesla.mdx b/docs/devices-next/vehicles/tesla.mdx index 79b45c098f..a6a0ff7da3 100644 --- a/docs/devices-next/vehicles/tesla.mdx +++ b/docs/devices-next/vehicles/tesla.mdx @@ -2,6 +2,7 @@ title: Tesla custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/teslalogger.mdx b/docs/devices-next/vehicles/teslalogger.mdx index 8e5d95f218..e956724d34 100644 --- a/docs/devices-next/vehicles/teslalogger.mdx +++ b/docs/devices-next/vehicles/teslalogger.mdx @@ -2,6 +2,7 @@ title: TeslaLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslalogger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/teslamate.mdx b/docs/devices-next/vehicles/teslamate.mdx index dd434feb92..800f3aacd1 100644 --- a/docs/devices-next/vehicles/teslamate.mdx +++ b/docs/devices-next/vehicles/teslamate.mdx @@ -2,6 +2,7 @@ title: TeslaMate custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslamate.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/tessie.mdx b/docs/devices-next/vehicles/tessie.mdx index 3470ae35bd..9e186d2457 100644 --- a/docs/devices-next/vehicles/tessie.mdx +++ b/docs/devices-next/vehicles/tessie.mdx @@ -2,6 +2,7 @@ title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tessie.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/toyota.mdx b/docs/devices-next/vehicles/toyota.mdx index f35d461b3b..e05b136c31 100644 --- a/docs/devices-next/vehicles/toyota.mdx +++ b/docs/devices-next/vehicles/toyota.mdx @@ -2,6 +2,7 @@ title: Toyota custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/toyota.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/tronity.mdx b/docs/devices-next/vehicles/tronity.mdx index 9e2f0f53ac..51afeae9f8 100644 --- a/docs/devices-next/vehicles/tronity.mdx +++ b/docs/devices-next/vehicles/tronity.mdx @@ -2,6 +2,7 @@ title: Tronity custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tronity.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx index 16ffaf4bea..7221a05181 100644 --- a/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx +++ b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -2,6 +2,7 @@ title: Volkswagen We Connect ID custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/vw.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/volvo.mdx b/docs/devices-next/vehicles/volvo.mdx index bf13b49a66..431f5eea2a 100644 --- a/docs/devices-next/vehicles/volvo.mdx +++ b/docs/devices-next/vehicles/volvo.mdx @@ -2,6 +2,7 @@ title: Volvo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo-connected.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/volvo2mqtt.mdx b/docs/devices-next/vehicles/volvo2mqtt.mdx index dee134d77f..c81f318ceb 100644 --- a/docs/devices-next/vehicles/volvo2mqtt.mdx +++ b/docs/devices-next/vehicles/volvo2mqtt.mdx @@ -2,6 +2,7 @@ title: volvo2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo2mqtt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/docs/devices-next/vehicles/zero-motorcycles.mdx b/docs/devices-next/vehicles/zero-motorcycles.mdx index 510a5157ff..fa76e2a2fc 100644 --- a/docs/devices-next/vehicles/zero-motorcycles.mdx +++ b/docs/devices-next/vehicles/zero-motorcycles.mdx @@ -2,6 +2,7 @@ title: Zero Motorcycles custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/zero.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx index 8da8aceb23..eb9c9dced2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -2,6 +2,7 @@ title: ABB Terra AC (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx index 23e754ed77..1f5371ad70 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx @@ -2,6 +2,7 @@ title: ABB Terra AC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx index 35445ee036..215eac9dde 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Single (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx index 5045ee7359..c26d12ffb4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Single (SBCx) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx index 8f80ed18f7..f083ad4db9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Twin (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx index f25dfdf3d3..03264144e9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -2,6 +2,7 @@ title: ABL eM4 Twin (SBCx) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx index 6f75ded4fa..837e50a262 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx @@ -2,6 +2,7 @@ title: ABL eMH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx index cc7395d1dd..0f04e32c70 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eMH2 (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx index 42e7f8b44a..37d2e6df59 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx @@ -2,6 +2,7 @@ title: ABL eMH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx index 6798304376..79d12248e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx @@ -2,6 +2,7 @@ title: ABL eMH3 (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx index 323f6ec9ea..24b4cfe487 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx @@ -2,6 +2,7 @@ title: Alfen Eve (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-alfen.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx index 607de1ea69..601fc9b837 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx @@ -2,6 +2,7 @@ title: Alfen Eve custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alfen.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx index 9e4c7e001a..3a7495458f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx @@ -2,6 +2,7 @@ title: alpha innotec custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx index 4cebe39820..7f2522499a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -2,6 +2,7 @@ title: Alphatec Ladesäule Twin custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx index a2224d44b3..c318efeb53 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -2,6 +2,7 @@ title: Alphatec Wallbox Mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx index d78d0412ce..e0367dec3e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx @@ -2,6 +2,7 @@ title: Alphatec Wallbox Power custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx index ffffcfe33c..62d47649b7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox connect.business custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx index 54a9b63bfb..8c75608b65 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox connect.home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx index d9bb8a8f14..39133c4bdf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox connect.solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/amperfied-solar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx index 729cece3bb..f5265b22e3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -2,6 +2,7 @@ title: Amperfied Wallbox Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx index 8d0ff62616..54262686f5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx @@ -2,6 +2,7 @@ title: Ampure NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx index a6cb398b5e..a3fd11bccd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx @@ -2,6 +2,7 @@ title: Ampure Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx index b6a5623714..1687e33968 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx @@ -2,6 +2,7 @@ title: Audi Wallbox plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx index 7cc023124e..2bfe5dae28 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx @@ -2,6 +2,7 @@ title: Audi Wallbox pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx index 3cde1c47c3..06c2d9180e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx @@ -2,6 +2,7 @@ title: AUTEL AC Compact custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx index 6bd8334b82..5a18a7ec9a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx @@ -2,6 +2,7 @@ title: AUTEL AC MaxiCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx index 1f1e8c0e5c..bfa0989dd9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx @@ -2,6 +2,7 @@ title: Autoaid Business Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx index 3cfc018a6e..67a4e32a3a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -2,6 +2,7 @@ title: Autoaid Intelligent Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-autoaid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx index b608d0cce0..4c319ba178 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx @@ -2,6 +2,7 @@ title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/fritzdect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx index 72dc90c737..9d14adc43d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx @@ -2,6 +2,7 @@ title: Bender CC612 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx index d9db8b83b1..431267b7db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx @@ -2,6 +2,7 @@ title: Bender CC613 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx index b2ec9fd26e..12183c9409 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx @@ -2,6 +2,7 @@ title: Bender ICC1314 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx index 8038016b66..ed8c7ee32b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx @@ -2,6 +2,7 @@ title: Bender ICC1324 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx index 2964dcc96a..68b06cbfef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx @@ -2,6 +2,7 @@ title: BMW i Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx index 83a647545b..45a496d4d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx @@ -2,6 +2,7 @@ title: Bosch SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx index 38bed8603e..2ad656474d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx @@ -2,6 +2,7 @@ title: Bösch x-change custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx index d0013b757b..83ed41a5d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -2,6 +2,7 @@ title: Buderus Logamatic HMC 20 Z custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx index 7d7728175e..77c839a79a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -2,6 +2,7 @@ title: Buderus Logamatic HMC 20 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx index 5a9b000bfe..e2893fbbe4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx @@ -2,6 +2,7 @@ title: Buderus SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx index fe82fe0e2c..611dae2a12 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx @@ -2,6 +2,7 @@ title: cFos Power Brain Solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx index f4971380b4..e5d27d6a7f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx @@ -2,6 +2,7 @@ title: cFos Power Brain custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/cfos.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx index 1d23003415..1b2bb2b961 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx @@ -2,6 +2,7 @@ title: Charge Amps Halo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-chargeamps.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx index 21c8d2392a..ad7f78d612 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx @@ -2,6 +2,7 @@ title: Compleo eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx index 69fe088cce..4b6965fed6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -2,6 +2,7 @@ title: CTA All-In-One Aeroplus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx index d51a7a05f0..e71db218b0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx @@ -2,6 +2,7 @@ title: CUBOS C11E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx index e189388123..ad52c7b5f9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx @@ -2,6 +2,7 @@ title: CUBOS C22E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx index 534265d7d6..e856d89e04 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx index bfeb888f0c..ed5be4e83a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx index f077dd5a90..ddb7369e6a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx index f40a00c312..6de3018972 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx index 45155311be..e88570a320 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx @@ -2,6 +2,7 @@ title: Cupra Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx index 7875d02839..46c63557d6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -2,6 +2,7 @@ title: Dadapower Premium Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/dadapower.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx index 2bc6d87db1..d2d17132a6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx @@ -2,6 +2,7 @@ title: DaheimLaden Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daheimladen-mb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx index 12169287de..2c28a06175 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -2,6 +2,7 @@ title: Daikin HomeHub (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/daikin-homehub.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx index 6ffd01ebf3..78b070701d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx @@ -2,6 +2,7 @@ title: Delta AC Max Basic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx index 7aadd9517a..523a00eed1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx @@ -2,6 +2,7 @@ title: Delta AC MAX Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx index bf8951a6f2..5f9ad31fc6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx @@ -2,6 +2,7 @@ title: Delta SLIM Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx index edc8b5b43a..d954f3b8bd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -2,6 +2,7 @@ title: Delta Ultra Fast Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/delta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx index faf3118716..4e59329695 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx @@ -2,6 +2,7 @@ title: Demowallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/demo-charger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx index f3cbdd8c12..bce3f671c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx @@ -2,6 +2,7 @@ title: E.ON Drive eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx index 5ef2aa5e6d..22e42e4ccf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx @@ -2,6 +2,7 @@ title: E.ON Drive vBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx index b84530f6cc..f4ffe5146b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx @@ -2,6 +2,7 @@ title: E3/DC Easy Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx index 0c116a9456..65d31baec6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx @@ -2,6 +2,7 @@ title: Easee Charge Core custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx index faae4ece76..778b21e17a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx @@ -2,6 +2,7 @@ title: Easee Charge Lite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx index 7191beae15..3c9d91fa64 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx @@ -2,6 +2,7 @@ title: Easee Charge custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx index abe17c3af2..718b1ea63a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx @@ -2,6 +2,7 @@ title: Easee Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/easee.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx index e4fe1520d8..c16f20ced4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx @@ -2,6 +2,7 @@ title: Ebee Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx index 0b50e8d653..2e24f258b3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx @@ -2,6 +2,7 @@ title: echarge cPH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx index 48b41d8f24..9416ccbb7c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx @@ -2,6 +2,7 @@ title: echarge cPH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx index 8412e64e6e..8ad6ebb780 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx @@ -2,6 +2,7 @@ title: echarge cPμ2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx index 09ef0cf3ea..7286a38a8b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -2,6 +2,7 @@ title: EcoHarmony EVSE EPC 2.0 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx index 099824580f..46984c25a1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx @@ -2,6 +2,7 @@ title: Edgetech Smart EVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartevse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx index 4294d7a5ec..8ea63fcc14 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx @@ -2,6 +2,7 @@ title: EEBUS kompatibel custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eebus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx index 5945cb3c34..d5155fa921 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx @@ -2,6 +2,7 @@ title: Elco custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx index c1b2af17b0..f69af41c02 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx @@ -2,6 +2,7 @@ title: Elecq Biz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx index 4fcce7a343..109ab94575 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx @@ -2,6 +2,7 @@ title: Elecq Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx index 16b4d55b31..05226e1cec 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx @@ -2,6 +2,7 @@ title: Elecq Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-elecq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx index cce097b4d8..5504f1f6cf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx @@ -2,6 +2,7 @@ title: eledio go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx index 64f84dd82e..ead107c1bc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx @@ -2,6 +2,7 @@ title: Elli Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx index 5a6b5a7597..6ca9a98271 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx @@ -2,6 +2,7 @@ title: Elli Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx index 224958e1cf..a1fb7caa0e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx @@ -2,6 +2,7 @@ title: Elli Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx index 3924c2fa19..bca5529eea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -2,6 +2,7 @@ title: Elli Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx index e8e2fc7ade..824cf765df 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx @@ -2,6 +2,7 @@ title: Elli Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx index aa432ee3b9..e70d501b33 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx @@ -2,6 +2,7 @@ title: EM2GO Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go-home.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx index 81cdbd179b..d831706fdd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -2,6 +2,7 @@ title: EM2GO Pro Power (OCPP/ONC) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/em2go.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx index 534a199967..1dfefa8fff 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx @@ -2,6 +2,7 @@ title: enercab smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enercab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx index 13fcbf6a14..3c5e3fc109 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -2,6 +2,7 @@ title: EN+ AC EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-enplus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx index 4ef000a027..212b27020f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx @@ -2,6 +2,7 @@ title: Ensto Chago Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx index 17020b66ca..f8357f333a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx @@ -2,6 +2,7 @@ title: EntraTek Power Dot Fix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx index f722481c8b..0f87e1b7cd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -2,6 +2,7 @@ title: EntraTek Power Dot Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-entratek.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx index e38bca9ea3..f52bb1761a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx @@ -2,6 +2,7 @@ title: ESL Walli LIGHT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx index ee25834f16..887d3a1c66 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx @@ -2,6 +2,7 @@ title: eSystems ghostONE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx index 6e1d420caa..15b9fe6f03 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx @@ -2,6 +2,7 @@ title: Etrel INCH Duo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel-duo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx index f1acf853c1..c9ff10cd4c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx @@ -2,6 +2,7 @@ title: Etrel INCH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx index f9ddd93f87..de588800e7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx @@ -2,6 +2,7 @@ title: EVBox Elvi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-evbox-elvi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx index 53647b8851..49fd5c4ad3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx @@ -2,6 +2,7 @@ title: EVBox Livo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/livo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx index a81b1db013..d0ed0352ee 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx @@ -2,6 +2,7 @@ title: EVSE DIN custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx index 10ba1cadf6..c15af73202 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx @@ -2,6 +2,7 @@ title: EVSE-WiFi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evsewifi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx index 251c587201..759cdc93dd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -2,6 +2,7 @@ title: Free2Move eProWallbox Move custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx index 7e6a5c67f4..17e10158a9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx @@ -2,6 +2,7 @@ title: Free2Move eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/eprowallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx index c42bdb49b9..a1887fcf9c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -2,6 +2,7 @@ title: Free2move eSolutions eProWallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-esolutions.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx index 96cd34ae53..4f17cd21e7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -2,6 +2,7 @@ title: Fronius Wattpilot (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx index 807af1078d..f75744b732 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx @@ -2,6 +2,7 @@ title: Garo GLB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx index 5186dcc0d8..6c989e1068 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx @@ -2,6 +2,7 @@ title: Garo GLB+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx index 4a7f22e70c..ee53dda142 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx @@ -2,6 +2,7 @@ title: Garo LS4 compact custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx index 630c815ec7..5dc0a36eda 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx @@ -2,6 +2,7 @@ title: Garo LS4 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx index 1738dbef63..59c3e4376e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -2,6 +2,7 @@ title: go-e Charger Gemini (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx index 065db795d5..908ad2d3f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx @@ -2,6 +2,7 @@ title: go-e Charger Gemini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx index 20549d9b7c..79133d2a18 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx @@ -2,6 +2,7 @@ title: go-e Charger HOMEfix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx index 3f0d84fd57..2f20380c62 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx @@ -2,6 +2,7 @@ title: go-e Charger HOME+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx index ecff298031..ea5824b543 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -2,6 +2,7 @@ title: go-e Charger PRO (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx index a94b5224d3..78c8d9ec19 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx @@ -2,6 +2,7 @@ title: go-e Charger PRO custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx index 23c5426ae1..6457b1adad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -2,6 +2,7 @@ title: go-e Charger V3 (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-goe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx index 7cc7300daa..4edcb0b13f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx @@ -2,6 +2,7 @@ title: go-e Charger V3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/go-e-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx index 70da3ab065..1c224da0f5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx @@ -2,6 +2,7 @@ title: Hardy Barth cPH1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-ecb1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx index 8dde5fc3c3..92822040fe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx @@ -2,6 +2,7 @@ title: Hardy Barth cPH2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx index e6ad64f4d2..6477fc14ee 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx @@ -2,6 +2,7 @@ title: Hardy Barth cPμ2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hardybarth-salia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx index 90538c5293..b6c4b2df3c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx @@ -2,6 +2,7 @@ title: Heidelberg Energy Control custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx index 542535e19b..57cbc52884 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx @@ -2,6 +2,7 @@ title: Hesotec eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx index 17345aa334..8b4f54a6dc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx @@ -2,6 +2,7 @@ title: Hesotec eSat custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/hesotec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx index 03e401f368..02023a3ea2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx @@ -2,6 +2,7 @@ title: Home Assistant Schalter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homeassistant-switch.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx index 017794bc49..b998da2263 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx @@ -2,6 +2,7 @@ title: Homecharge Homecharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-homecharge.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx index 5f777d25d2..a90a442f3c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx @@ -2,6 +2,7 @@ title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homematic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx index ae1510c35e..cbcc390031 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx @@ -2,6 +2,7 @@ title: HomeWizard custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/homewizard.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx index 649fabd58b..4ba6be806e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -2,6 +2,7 @@ title: Huawei SCharger-22KT-S0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx index ea0d5105ca..b9ff9d4e48 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -2,6 +2,7 @@ title: Huawei SCharger-7KS-S0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-huawei.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx index ea1f46574e..11c0d694be 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx @@ -2,6 +2,7 @@ title: IDM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/idm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx index 9fb0a72ef7..cd1fe588b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx @@ -1,6 +1,7 @@ --- title: Chargers hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx index 8b84dc3dc2..d62ceefb4d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx @@ -2,6 +2,7 @@ title: Innogy eBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/innogy-ebox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx index 19cafca252..481426edcb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx @@ -2,6 +2,7 @@ title: INRO Pantabox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pantabox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx index d40882cbe4..f352a34b99 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx @@ -2,6 +2,7 @@ title: Juice Charger Me custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx index 5f931fdc06..c39fd8af7d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx @@ -2,6 +2,7 @@ title: Junkers SG Ready custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/emsesp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx index 49802b058b..2343709d01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC20 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx index b377f6c5d7..6586d9ae03 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC35 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx index ff8fda6a3b..773d5c1f28 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC40 E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx index 8965d2ac2c..5bfd9f86b6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC40 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx index ab2d246aba..c8b26930b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC60 E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx index 2d87213740..38cdd5697f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -2,6 +2,7 @@ title: Kathrein KWB-AC60 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/Kathrein.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx index 0d8c492bdb..e63eab5922 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P20 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx index 2af5ac5576..2c53994246 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P30 C-Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx index dca77d2497..5a98d18632 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P30 X-Series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx index 99c80a52fb..1005240360 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P40 Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx index 2b9f3f7b7d..0ba22c6aba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact P40 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx index 44c0a6ca01..23274fc5eb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx @@ -2,6 +2,7 @@ title: Kermi x-center pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kermi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx index 9cf5de0dd3..a3a8ec3ced 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx @@ -2,6 +2,7 @@ title: Kontron Solar Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ghost.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx index b8f8a6a668..f56aac9e5f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx @@ -2,6 +2,7 @@ title: Kostal Enector custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx index da73d59d0a..af15a4eae9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx @@ -2,6 +2,7 @@ title: KSE wBX16 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/kse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx index 67bb2e18ea..ba356d7fb5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx @@ -2,6 +2,7 @@ title: LadeFoxx EvLoad custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx index 4d4705633f..23801b9871 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -2,6 +2,7 @@ title: LadeFoxx Mikro 2.0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx index 5627f97e7c..583cc9a1d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx @@ -2,6 +2,7 @@ title: Lambda EU-L Serie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx index a5bb045e02..cb0f023a9f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx @@ -2,6 +2,7 @@ title: LRT HOME Essential+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/alphatec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx index 41f5020b9a..81907f208c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx @@ -2,6 +2,7 @@ title: Mennekes AMEDIO Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx index 95eaaede5b..2c351bc456 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON 4Business 700 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx index fccc759a8c..451370cf61 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON 4You 300 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx index e3b00945bc..09974dca04 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON 4You 500 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-icc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx index 3bae2447d3..ea20228034 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON ChargeControl custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx index b068e8fe08..f937326210 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Compact 2.0s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-compact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx index 5d155b95e8..bc9a6c1506 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Premium custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx index 53ecb7ea1b..27f3fd96f9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Professional custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx index c2a1fd38e9..1c548c621e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -2,6 +2,7 @@ title: Mennekes AMTRON Xtra custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mennekes-hcc3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx index 06ed75f290..dd32742387 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -2,6 +2,7 @@ title: Mennekes eMobility Gateway (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx index 6824c5ce3a..f52a873a7c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx @@ -2,6 +2,7 @@ title: Mennekes Smart (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx index 1ab6352708..a88b835d6d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -2,6 +2,7 @@ title: Mennekes Smart T (ACU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-mennekes-acu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx index ba8ae6c694..a988755efe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -2,6 +2,7 @@ title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-elwa-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx index d390c87182..15ab258d81 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -2,6 +2,7 @@ title: my-PV AC•THOR 9s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx index f72982dc32..aa49ca04ec 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx @@ -2,6 +2,7 @@ title: my-PV AC•THOR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ac-thor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx index 74ed9fc035..b614eec0ff 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx @@ -2,6 +2,7 @@ title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/mystrom.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx index 46284de9e7..e1b13f95b2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx @@ -2,6 +2,7 @@ title: Nibe AP-AW10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx index 9696db2604..c61b76b31f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx @@ -2,6 +2,7 @@ title: Novelan WPR NET custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx index 48471bc65b..ebd7b80029 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx @@ -2,6 +2,7 @@ title: NRGkick Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrgkick-connect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx index 87342ea3d7..5ca8c00f20 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx @@ -2,6 +2,7 @@ title: NRGkick Gen2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/nrggen2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx index a4ad366ef1..48a7ab3b5c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx @@ -2,6 +2,7 @@ title: OBO Bettermann Ion custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx index 0c53c4923a..bd025239aa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -2,6 +2,7 @@ title: OCPP 1.6J kompatibel (Smart Charging) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx index bda62a28ad..60430be3b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx @@ -2,6 +2,7 @@ title: OpenEVSE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openevse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx index 5abe203a6b..0fd8043eac 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx @@ -2,6 +2,7 @@ title: openWB Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-pro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx index 5398a4f732..42f12680fe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx @@ -2,6 +2,7 @@ title: openWB series2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx index 20a03929a2..e9cd8143ef 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx @@ -2,6 +2,7 @@ title: openWB Software 2.x custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/openwb-2.0.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx index 0d389bf5b2..e5824700e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx @@ -2,6 +2,7 @@ title: Optec Mobility One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx index 3d9b59e4a6..7b01d523fd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx @@ -2,6 +2,7 @@ title: Orbis Viaris custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-orbis.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx index 4d596472fa..fd95ea699c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx @@ -2,6 +2,7 @@ title: PC Electric Garo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pcelectric-garo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx index f324e2c4db..230d02cc20 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx @@ -2,6 +2,7 @@ title: Peblar Business custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx index 04aa540331..17172f0859 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx @@ -2,6 +2,7 @@ title: Peblar Home Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx index 79fa3761c9..f12bf248e8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx @@ -2,6 +2,7 @@ title: Peblar Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/peblar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx index 8ef549b5c5..1097a75016 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact CHARX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-charx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx index 178c09982e..6eb290ca33 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EM-CP-PP-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-em-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx index 10dc565de0..52582b42f8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH-3G custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx index c8cbed0c87..282bcb2395 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx index ecea5865f6..dc8de927db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-3G-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx index 170408d6ba..cee8aba9c4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-CC-AC1-M3-RCM-ETH-XP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx index 446f9edcc2..094b35515b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -2,6 +2,7 @@ title: Phoenix Contact EV-SER custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-ser.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx index e7623af210..fe590d0232 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx @@ -2,6 +2,7 @@ title: Plugchoice custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/plugchoice.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx index 4bb3be9cad..1845bc0125 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -2,6 +2,7 @@ title: Porsche Mobile Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx index a4dd7956c1..fa42b0a528 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -2,6 +2,7 @@ title: Porsche Mobile Charger Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pmcp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx index 6030beff18..181772c78e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx @@ -2,6 +2,7 @@ title: Porsche Wallbox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/porsche-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx index 73eeaceda9..5f74c84111 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx @@ -2,6 +2,7 @@ title: Pracht Alpha XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx index c964b86945..f3e6e61ecf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx @@ -2,6 +2,7 @@ title: Pracht Mono XT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx index 179062e818..24dbd62a09 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx @@ -2,6 +2,7 @@ title: Pracht PNI custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx index c2a49cd70c..32dd5f3586 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx @@ -2,6 +2,7 @@ title: Pracht XT+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pracht-alpha.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx index 8b03100ae6..e51557cf69 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx @@ -2,6 +2,7 @@ title: Pulsares SimpleBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsares.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx index d59f1c0280..58e63bf78f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx @@ -2,6 +2,7 @@ title: Pulsatrix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/pulsatrix.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx index ba5ee09dd4..5805719658 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -2,6 +2,7 @@ title: Qcells Q.HOME EDRIVE A custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx index f46649c9dc..f9951fa2f8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx @@ -2,6 +2,7 @@ title: Roth ThermoAura custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx index beb46a3538..1604e9c81b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx @@ -2,6 +2,7 @@ title: Roth ThermoTerra custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx index 41b8f47b92..bdaff220b0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx @@ -2,6 +2,7 @@ title: Schneider EVlink Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/schneider-evlink-v3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx index a9b518b755..71f98529d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx @@ -2,6 +2,7 @@ title: Schrack i-CHARGE CION custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx index 90ff79a5f3..43a43b771f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -2,6 +2,7 @@ title: SENEC Wallbox pro s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx index 8bf773be5d..a4ab52f849 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx @@ -2,6 +2,7 @@ title: SENEC Wallbox pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx index cfdc1a8ea4..c988c82216 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx @@ -2,6 +2,7 @@ title: Shelly 1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx index 60cf8b1e39..db1945a942 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx @@ -2,6 +2,7 @@ title: Shelly Plug S custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx index eda715d6e8..1768ac53ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx @@ -2,6 +2,7 @@ title: Shelly Plus 1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx index 78e87805ce..bd7135b5d4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/shelly.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx index fd4a9e0584..91ad3d4d3c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -2,6 +2,7 @@ title: Siemens Versicharge GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/versicharge.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx index 9c547f7712..12528ddee3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx @@ -2,6 +2,7 @@ title: Skoda Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx index 443d563e10..9025ad820d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -2,6 +2,7 @@ title: Skoda Charger Pro Eichrecht custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx index 50751e06c6..540fc43b48 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx @@ -2,6 +2,7 @@ title: Skoda Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx index d304ae52ab..fe1b5d1811 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -2,6 +2,7 @@ title: Skoda iV Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx index 3e39bb7821..3e1b8b148c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -2,6 +2,7 @@ title: Skoda iV Charger Connect+ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx index abe7fd7d50..17985f4e12 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx @@ -2,6 +2,7 @@ title: SMA eCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx index 1bb5c2de01..662b76d061 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx @@ -2,6 +2,7 @@ title: SMA EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smaevcharger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx index dc432f7b68..43a0a35626 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ichargecion.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx index 85effba909..42ef60dfa8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx @@ -2,6 +2,7 @@ title: smartWB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/smartwb.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx index edb37affe5..4824eddc1a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -2,6 +2,7 @@ title: SolarEdge Home EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/keba-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx index e106366c44..3c8a4558af 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx @@ -2,6 +2,7 @@ title: Solax X3-EVC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx index bfcccba85b..2cf9ec38e4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx @@ -2,6 +2,7 @@ title: Sonnen sonnenCharger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/etrel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx index 6de9e50f2f..8d9274a81a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -2,6 +2,7 @@ title: Spelsberg Wallbox Smart Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx index 71c966a2b3..8b25b98732 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx @@ -2,6 +2,7 @@ title: Stark in Strom Easy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/evse-din.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx index 8448597a8f..9105ad609d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -2,6 +2,7 @@ title: Stiebel Eltron LWA/LWZ (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx index fdd5567199..eb778a3ae7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -2,6 +2,7 @@ title: Stiebel Eltron WPM (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-wpm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx index bed181b7d5..3266b46b8e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx @@ -2,6 +2,7 @@ title: Sungrow AC011E-01 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx index 2e7684ded6..e31f80da31 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx @@ -2,6 +2,7 @@ title: Sungrow AC011E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-sungrow.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx index 87de9170f8..7cfdc6fc86 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx @@ -2,6 +2,7 @@ title: Sungrow AC22E-01 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/sungrow.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx index c2ae4c5bca..33a81207e7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx @@ -2,6 +2,7 @@ title: Tasmota einphasig custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tasmota.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx index 9e7534f104..d48157ae70 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -2,6 +2,7 @@ title: Tecalor THZ (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/stiebel-lwa.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx index 17dd3035e7..dd6186a95b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx @@ -2,6 +2,7 @@ title: TechniSat Technivolt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx index f969a6aefc..dcdb3c996d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -2,6 +2,7 @@ title: Tesla Wall Connector (Gen 3) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/twc3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx index 6961af7bea..87ffb87cdf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx @@ -2,6 +2,7 @@ title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tessie.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx index b6c428d99b..3f140e474e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx @@ -2,6 +2,7 @@ title: Tigo GO EV Charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx index 46d765d723..446907c2a6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx index 375ad41c63..c4018251be 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx index 83b3e88165..a9b9a2d1a7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP3 Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx index 9494ce109e..06d858eadd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -2,6 +2,7 @@ title: TinkerForge WARP3 Charger Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tinkerforge-warp3-smart.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx index 0a33069ca2..cad9d36894 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tplink.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx index a84de8f53a..679ed312fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/tapo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx index c745473352..1757e89a11 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx @@ -2,6 +2,7 @@ title: Ubitricity Heinz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx index 3245c0c169..d15970facd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx @@ -2,6 +2,7 @@ title: V2C Trydan custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/trydan.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx index 9d383a1ad6..1d0ffb8cda 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -2,6 +2,7 @@ title: Vaillant SensoNET (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vaillant.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx index aa9424a550..f051dc3373 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx @@ -2,6 +2,7 @@ title: Vestel Connect Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx index 484c79a68b..9ab23cfd05 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -2,6 +2,7 @@ title: Vestel EVC04 Home Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx index fd9c0f49a3..f3472bd55b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -2,6 +2,7 @@ title: Victron EV Charging Station (via GX) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx index 675eea781b..2e1cc34d82 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx @@ -2,6 +2,7 @@ title: Victron EV Charging Station custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/victron-evcs.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx index 3a25e38ddd..4f5467e4a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -2,6 +2,7 @@ title: Viessmann Heatpump (SG Ready) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/viessmann.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx index ca5e5a9317..0082269c92 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -2,6 +2,7 @@ title: Viridian EV EVSE EPC 2.0 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/obo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx index c831676464..d276258cbd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -2,6 +2,7 @@ title: Volkswagen Charger Connect 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx index d80c9001fc..f7afb03d90 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -2,6 +2,7 @@ title: Volkswagen Charger Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx index ae70fd7b57..2b7747ca8f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -2,6 +2,7 @@ title: Volkswagen Charger Pro Eichrecht 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elli-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx index f92b1b22db..c64e14e3d8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -2,6 +2,7 @@ title: Volkswagen ID. Charger Connect custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/elliconnect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx index 5746c13803..98a40ec3b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -2,6 +2,7 @@ title: Volkswagen ID. Charger Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ellipro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx index ce5ff880e2..b117613053 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx @@ -2,6 +2,7 @@ title: Volt Time One custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx index 67fea3ab6b..849b89e1ee 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx @@ -2,6 +2,7 @@ title: Volt Time Source 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx index 4edc1d7cef..c21696c61b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx @@ -2,6 +2,7 @@ title: Volt Time Source 2s custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx index c6e22d360c..54453eae31 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx @@ -2,6 +2,7 @@ title: Volt Time Source custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/volttime.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx index fbf224f27f..1e6cd3e138 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -2,6 +2,7 @@ title: Wallbe Eco 2.0(s) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx index 9a681807e6..52cfa41967 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx @@ -2,6 +2,7 @@ title: Wallbe Eco custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx index 3f800e0d76..79fb8894b4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx @@ -2,6 +2,7 @@ title: Wallbe Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/phoenix-ev-eth.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx index 8d3653109f..98a9f5b964 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Commander 2 (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx index 7e12c61427..aecf9a8c1a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx @@ -2,6 +2,7 @@ title: wallbox Commander 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx index aa999045eb..6fcc70a1ae 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Copper SB (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx index e08b90c18d..c6f6ac59b6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx @@ -2,6 +2,7 @@ title: wallbox Copper SB custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx index a8dc4cc102..f483a66d66 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Max (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx index 944021fecc..508ed9ca2e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Max custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx index 0a8aeba2cc..0b03bdafa7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Plus (FW 5.x) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/wallbox-fw5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx index 66bc5253e6..7bd989ba81 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -2,6 +2,7 @@ title: wallbox Pulsar Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-wallbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx index 5351ec3b97..2f5587ecb5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -2,6 +2,7 @@ title: Walther Werke Basic Evo Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/heidelberg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx index 7848d808db..d784fdef08 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx @@ -2,6 +2,7 @@ title: Webasto Live custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/bender-cc.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx index 1d354c72c4..ada8617afc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx @@ -2,6 +2,7 @@ title: Webasto NEXT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/webasto-next.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx index b79f18d189..26f9fead87 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx @@ -2,6 +2,7 @@ title: Webasto Unite custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/vestel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx index 9bc42407a3..ebbdf88932 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx @@ -2,6 +2,7 @@ title: Weidmüller AC Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/weidmüller.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx index 9e59bd25a2..76e1706c97 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx @@ -2,6 +2,7 @@ title: Wolf BWL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx index aa81f3c4fe..1e82a3cdd9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx @@ -2,6 +2,7 @@ title: Wolf BWS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/luxtronik.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx index 6fd598dc1c..a32e8869fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx @@ -2,6 +2,7 @@ title: Zaptec Go 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx index 36e47170a5..0a6627bf33 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx @@ -2,6 +2,7 @@ title: Zaptec Go (OCPP) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx index 9643c93a87..a832c480c8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx @@ -2,6 +2,7 @@ title: Zaptec Go custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx index 64cbf223e3..efcd62721b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx @@ -2,6 +2,7 @@ title: Zaptec Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/zaptec.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx index abe80cbd71..f5bd6ffe36 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -2,6 +2,7 @@ title: Zewotherm EU-L Serie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/lambda-zewotherm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx index 0d735214aa..0091e8f6f2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -2,6 +2,7 @@ title: ZJ Beny BCP EV charger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-beny.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx index 1d1ddd0d31..76b45b4858 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx @@ -2,6 +2,7 @@ title: A-Tronix custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx index 7336a35c69..59b2e85a31 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx @@ -2,6 +2,7 @@ title: ABB A43 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx index d6f93a63de..bf0388cabb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx @@ -2,6 +2,7 @@ title: ABB A44 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx index e4b3a7d84f..4f4760d368 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx @@ -2,6 +2,7 @@ title: ABB B23 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx index dec66ce8bc..bfd9e147b9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx @@ -2,6 +2,7 @@ title: ABB B24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/abb-ab.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx index 1ddfcd5482..54bcb3ce63 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx @@ -2,6 +2,7 @@ title: Acrel ADW300 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/acrel-adw300.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx index 32cb1afc74..5bb1a8fd61 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx @@ -2,6 +2,7 @@ title: Ads-tec StoraXe custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/storaxe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx index 516608234e..ec2baf6526 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx @@ -2,6 +2,7 @@ title: Alpha ESS Storion SMILE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/alpha-ess-smile.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx index 3a8582919b..ed01b8e14e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx @@ -2,6 +2,7 @@ title: Ampere Ampere.StoragePro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx index 0c9df6561d..a8642085b4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Anker Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx index 77a8ae29c1..cc0236fd5b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx @@ -2,6 +2,7 @@ title: APsystems EZ1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/apsystems-ez1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx index afd89e8a16..ad427f531d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx @@ -2,6 +2,7 @@ title: AVM FritzDECT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fritzdect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx index 30cd69fd87..2a91809bf8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -2,6 +2,7 @@ title: Axitec AXIhycon 12-15H custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx index 1fee7376a3..b5067f5c73 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -2,6 +2,7 @@ title: Bernecker Engineering MPM3PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mpm3pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx index 5814b49dbc..6b41657ed8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx @@ -2,6 +2,7 @@ title: BGEtech DS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ds100.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx index 3398cc6fae..19b89ee72f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx @@ -2,6 +2,7 @@ title: BGEtech WS100 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bge_tech_ws100.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx index f650baa3f9..c827f45f67 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -2,6 +2,7 @@ title: Bosch BPT-S 5 Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/bosch-bpt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx index a1aa34fb2b..4d16d6d32e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Bosswerk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx index 8d7ee5b3aa..919e000ffc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM110/111/112 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx index 565af3a34a..38b45a0803 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx index 29c1635fae..c004cce03b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM24_E1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx index 231561dd2b..91491b50a9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM330/EM340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx index 3801e1399f..3532326151 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi EM530/EM540 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx index 7af05774cc..bbca817e88 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi ET112 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt1xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx index b514d8e6da..7d5810e1fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -2,6 +2,7 @@ title: Carlo Gavazzi ET330/ET340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx index d3895df9c6..5556fb201a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx @@ -2,6 +2,7 @@ title: cFos PowerBrain Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cfos.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx index fd2ac6c12b..01ec5183b2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx @@ -2,6 +2,7 @@ title: Demobatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-battery.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx index 2db0010ff6..1e6ace29a5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx @@ -2,6 +2,7 @@ title: Demozähler custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/demo-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx index ddc0c73f62..26ee75ee1a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Deye 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx index 92bf506f97..fb8ac9b255 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Deye hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx index 3e54052ee5..63e8a52033 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Deye Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx index f6caa324fb..c853ebf948 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Deye Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx index 2863f6f380..3934cbc986 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx @@ -2,6 +2,7 @@ title: Deye String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx index 379ecd5a57..3dd7dc5799 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx @@ -2,6 +2,7 @@ title: Discovergy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/discovergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx index 754caff198..a53a34d562 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx @@ -2,6 +2,7 @@ title: DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dsmr.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx index 3a31bc6b7f..9976bc5ced 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx @@ -2,6 +2,7 @@ title: DZG DVH4013 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/dzg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx index bb056ad8c1..6bd6b8c397 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx @@ -2,6 +2,7 @@ title: E3/DC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/e3dc-rscp.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx index b3191afc61..a1922d6ee9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx @@ -2,6 +2,7 @@ title: Eastron SDM120-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm120.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx index 14b5a7ecd9..88923abc6f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx @@ -2,6 +2,7 @@ title: Eastron SDM220/230 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx index 577b3b6b01..d9bdce1c0b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx @@ -2,6 +2,7 @@ title: Eastron SDM630-Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx index 75d90bcab8..2e6b8c0c15 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx @@ -2,6 +2,7 @@ title: Eastron SDM72D-M custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm72.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx index 6a07411c9c..6435ebecc8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -2,6 +2,7 @@ title: Eastron SDM72DM-V2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx index 68344ef039..16004ea6fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx @@ -2,6 +2,7 @@ title: Enphase IQ Envoy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/enphase.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx index f8b5fd6b49..cc4da14008 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -2,6 +2,7 @@ title: ESPHome DLMS Meter Austria custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/esphome-dlms-austria.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx index 974de29a34..6f30b1dc08 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx @@ -2,6 +2,7 @@ title: ESPHome DSMR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx index 9481afbb8f..5dd584c45d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx @@ -2,6 +2,7 @@ title: FENECON custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx index 479707b33a..062582bc27 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: FoxESS H1 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx index 836600ac4d..3d36272142 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: FoxESS H3 Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx index 11b7475239..448c237168 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: FoxESS H3-Smart Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fox-ess-h3-smart.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx index b822a14b50..d32081492c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx @@ -2,6 +2,7 @@ title: Fronius Ohmpilot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-ohmpilot.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx index ea56f6d8e5..229a29ede4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -2,6 +2,7 @@ title: Fronius Primo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx index b0c7b9dcda..d9799027cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -2,6 +2,7 @@ title: Fronius Smartmeter (über Wechselrichter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx index 8b3e772d82..70777942be 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx @@ -2,6 +2,7 @@ title: Fronius Solar API V1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-solarapi-v1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx index bf5444b5de..49b0d0b04a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -2,6 +2,7 @@ title: Fronius Symo GEN24 Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/fronius-gen24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx index 699debbe14..46019fd296 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -2,6 +2,7 @@ title: Ginlong Solis Hybrid Inverter (RHI series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx index df66b18ac8..1cae979d94 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -2,6 +2,7 @@ title: Ginlong Solis Hybrid Inverter (S Series) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis-hybrid-s.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx index 6e881bc7fb..e76cef2c6d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx @@ -2,6 +2,7 @@ title: Ginlong Solis Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solis.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx index fd0027ab47..0a44de418c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx @@ -2,6 +2,7 @@ title: go-e Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/go-e-controller.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx index 52031f7205..66c9cc58fa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: GoodWe ET/EH/BH/BT Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx index c189421338..f33914b63c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -2,6 +2,7 @@ title: GoodWe GoodWe over Wifi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-wifi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx index 263e7ee931..3b04863aa6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -2,6 +2,7 @@ title: GoodWe SDT/DT Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx index edb469666f..384fdd916e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Growatt Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx index 169e74eca9..2cb58c4ca2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Growatt TL-X(H) Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/growatt-hybrid-tlxh.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx index 32d17e045a..90d31a4fa7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx @@ -2,6 +2,7 @@ title: Homematic IP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homematic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx index 650c378b0d..fc80d83009 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx @@ -2,6 +2,7 @@ title: HomeWizard kWh Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard-kwh.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx index 92198ee56a..5f8b01cca4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -2,6 +2,7 @@ title: HomeWizard Wi-Fi P1 Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/homewizard.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx index 98f1298d61..7c8507fd2e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -2,6 +2,7 @@ title: Hoymiles HM & HMS Series (via AhoyDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-ahoydtu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx index 16a56ee9dd..ab0bc7e82d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -2,6 +2,7 @@ title: Hoymiles HM & HMS Series (via OpenDTU) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/hoymiles-opendtu.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx index 9a3e6b570b..cae7caf8d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx @@ -2,6 +2,7 @@ title: Huawei EMMA custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-emma.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx index 2a50a2da19..e0a4999744 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx @@ -2,6 +2,7 @@ title: Huawei SmartLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-smartlogger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx index b63111c67c..653fc8a65c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -2,6 +2,7 @@ title: Huawei SUN2000 (SDongle) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-dongle.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx index 73b494d53d..63fbbb19be 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx @@ -2,6 +2,7 @@ title: Huawei SUN2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-sun2000.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx index f51809b626..ca0a3661b9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx @@ -2,6 +2,7 @@ title: IAMMETER WEM3080 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx index 30e34656a0..cd046625d9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -2,6 +2,7 @@ title: IAMMETER WEM3080T/WEM3046T/WEM3050T custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iammeter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx index f3e8c31ca3..9d08e2608f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx @@ -2,6 +2,7 @@ title: IGEN Tech Solarman Logger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarman.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx index 8ef5ae3917..fdc9f67511 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx @@ -1,6 +1,7 @@ --- title: Meters hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx index f0a833c903..132ebada95 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx @@ -2,6 +2,7 @@ title: inepro PRO380-MOD custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/inepro.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx index e15b20accf..b174c9ba34 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx @@ -2,6 +2,7 @@ title: IOmeter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/iometer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx index e293e3d9ea..38c808ea91 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx @@ -2,6 +2,7 @@ title: Janitza B series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx index 6fd8a6e4b3..736f300978 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx @@ -2,6 +2,7 @@ title: Janitza UMG series custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/janitza.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx index 67859de438..fa7be6d12c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx @@ -2,6 +2,7 @@ title: KEBA KeContact E10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/keba-kecontact.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx index a82921d16e..ac2d3be659 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -2,6 +2,7 @@ title: Kostal Energy Meter C (KEM-C) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx index f26440158b..29d7653545 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -2,6 +2,7 @@ title: Kostal Energy Meter P (KEM-P) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx index 2954511f44..b7cf46a568 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx @@ -2,6 +2,7 @@ title: Kostal Piko BA custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx index 2b84242e6b..57a4c7706f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx @@ -2,6 +2,7 @@ title: Kostal Piko Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx index 8fe92836ec..076504422d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx @@ -2,6 +2,7 @@ title: Kostal Piko (legacy) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-legacy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx index 8836d7572e..202b35774b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx @@ -2,6 +2,7 @@ title: Kostal Piko MP Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx index 2b23da4c03..c277017d6c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx @@ -2,6 +2,7 @@ title: Kostal Piko custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-pv.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx index 3847430f6a..0501f56837 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -2,6 +2,7 @@ title: Kostal Plenticore Hybrid, inkl. Netzladung der Hausbatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore-gen2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx index f0592ad055..b8c3c7eb55 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -2,6 +2,7 @@ title: Kostal Plenticore Hybrid custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-plenticore.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx index 6e17b7b2de..f1f7710780 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -2,6 +2,7 @@ title: Kostal Smart Energy Meter (über den Wechselrichter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx index 1a4610c975..a5fbcb405b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx @@ -2,6 +2,7 @@ title: Kostal Smart Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-ksem.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx index dd7787ec9e..051d3e261f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx @@ -2,6 +2,7 @@ title: LG ESS Home 15 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-15.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx index 7e3ad9344d..9318ce5735 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx @@ -2,6 +2,7 @@ title: LG ESS Home 8/10 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/lg-ess-home-8-10.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx index b57d37453c..5db72ef60e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx @@ -2,6 +2,7 @@ title: Loxone Miniserver custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/loxone.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx index 0a07a905ef..6df440ce72 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -2,6 +2,7 @@ title: M-TEC Energy Butler GEN2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx index 387ef71493..6a0861c614 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -2,6 +2,7 @@ title: M-TEC Energy Butler GEN3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mtec-eb-gen3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx index 96ed33ef27..81184e0522 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx @@ -2,6 +2,7 @@ title: Marstek Venus Battery Storage custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/marstek-venus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx index 7a555ee2f1..4d8d03be5c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx @@ -2,6 +2,7 @@ title: mhendriks P1 dongle custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx index d004b2caac..0b05978225 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -2,6 +2,7 @@ title: my-PV AC ELWA 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx index 7c106663d7..2c77d05e20 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -2,6 +2,7 @@ title: my-PV AC ELWA-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/ac-elwa-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx index 55b0dc01f3..359f89c111 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx @@ -2,6 +2,7 @@ title: my-PV AC•THOR custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/thor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx index 6f52dba1a3..de52195d7a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx @@ -2,6 +2,7 @@ title: my-PV WiFi Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mypv-wifi-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx index bdf273c975..757bdc0cc1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx @@ -2,6 +2,7 @@ title: myStrom Switch custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/mystrom.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx index 1623633d39..8338c9dca6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx @@ -2,6 +2,7 @@ title: OpenEMS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/openems.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx index b386556b57..6da6de773a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx @@ -2,6 +2,7 @@ title: ORNO OR-WE-516 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx index 19aedcba2f..ee26596efe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx @@ -2,6 +2,7 @@ title: ORNO OR-WE-517 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/orno.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx index 9bed8a0ef0..31be98c146 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx @@ -2,6 +2,7 @@ title: P1Monitor P1 Monitor custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/p1monitor.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx index 539c15339c..320c72839b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx @@ -2,6 +2,7 @@ title: Plexlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/plexlog.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx index 44f01f04e4..da3ad73ad3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx @@ -2,6 +2,7 @@ title: Powerdog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerdog.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx index 0ac7fce06f..98a7a4625c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx @@ -2,6 +2,7 @@ title: Powerfox Poweropti custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/powerfox-poweropti.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx index 7791d6ac4a..af16c39e91 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -2,6 +2,7 @@ title: Qcells Hybrid-Wechselrichter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/qcells-hybrid-cloud.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx index 2ac4334f61..c176818661 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -2,6 +2,7 @@ title: Qcells Q.HOME ESS HYB-G3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx index 28a9000efa..6a49f5b5ca 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx @@ -2,6 +2,7 @@ title: RCT Power custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/rct-power.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx index 8d9cda4b09..f379ea16c0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -2,6 +2,7 @@ title: Saia-Burgess Controls (SBC) ALE3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx index e6fd2e9ebe..3b4163d166 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -2,6 +2,7 @@ title: Saia-Burgess Controls (SBC) AWD3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sbc-axx3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx index f1b6f10842..0681500a25 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -2,6 +2,7 @@ title: SAJ H1 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx index 6df6750909..fdda5a668a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -2,6 +2,7 @@ title: SAJ H2 Series Hybrid Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-h2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx index 098bf3c1a2..26a95df6b9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -2,6 +2,7 @@ title: SAJ R5 Series Solar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/saj-r5.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx index 3f39fed86f..a6069badde 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx @@ -2,6 +2,7 @@ title: SAX Homespeicher custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx index 94c68cd6f3..168b25ed49 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -2,6 +2,7 @@ title: Schneider Electric iEM3xxx Modbus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/schneider-iem3000.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx index 98b8a002f7..57aff49fc4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx @@ -2,6 +2,7 @@ title: SENEC .Home custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senec-home.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx index e913fc350e..2e8924e9ad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx @@ -2,6 +2,7 @@ title: Senergy SE 4/5/6KTL-S1/G2 Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx index ac11591742..5a351a3230 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx @@ -2,6 +2,7 @@ title: Shelly 1PM mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx index c349c94fc9..c632d43770 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx @@ -2,6 +2,7 @@ title: Shelly 1PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx index 3fb158cead..57fa1dd0b0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx @@ -2,6 +2,7 @@ title: Shelly 3EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-3em.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx index 68109fd546..ef8a756c9d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx @@ -2,6 +2,7 @@ title: Shelly EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx index 13fa8a0be1..f0362f87d6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx @@ -2,6 +2,7 @@ title: Shelly Plug S custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx index 1e7c5e1992..73432a903d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx @@ -2,6 +2,7 @@ title: Shelly PM mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx index a24c116526..17a182452a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 1PM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx index 1ac7b1d9d2..a4e1ad8419 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 3 EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-pro-3em.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx index de59ff9569..11a5ff157e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -2,6 +2,7 @@ title: Shelly Pro 3EM (monophase mode) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx index 0ebefe75f0..d504634bd0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx @@ -2,6 +2,7 @@ title: Shelly Pro EM custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/shelly-1pm.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx index d7f613fe93..5417f0681e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx @@ -2,6 +2,7 @@ title: Siemens 7KT1665 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-7kt1665.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx index a1f2454b77..9d09f09d1c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -2,6 +2,7 @@ title: Siemens Junelight Smart Battery custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-junelight.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx index 9718062c3a..d3dbf703de 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx @@ -2,6 +2,7 @@ title: Siemens PAC 2200 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/siemens-pac2200.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx index 6540c016b3..6236a86d21 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx @@ -2,6 +2,7 @@ title: Sigenergy Sigen Hybrid/Sigen PV Max/SigenStore EC custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sigenergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx index 7266d6f5c9..24a3504f8d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx @@ -2,6 +2,7 @@ title: SMA Data Manager custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-data-manager.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx index 2a0fc72cfa..3e52aad7f7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx @@ -2,6 +2,7 @@ title: SMA Energy Meter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-energy-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx index 7119d57682..ed3b127eba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx @@ -2,6 +2,7 @@ title: SMA Wechselrichter (Speedwire) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-speedwire.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx index fe22948e94..97611dff8d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SMA Smart Energy Hybrid-Wechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx index 65a8f6a2b8..e42d35d257 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Boy Storage 1.5/2.0/2.5 (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-15-25-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx index b9668c6333..2b2ed4b718 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Boy Storage 3.7/5.0/6.0 (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-sbs-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx index dd17a69d4c..094ac3dce4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Home Manager 2.0 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-home-manager.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx index 0db187ee6b..970cc4bcd2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Sunny Island (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-si-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx index b1c6ff4fb6..4aaffd07a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx @@ -2,6 +2,7 @@ title: SMA WebBox custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-webbox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx index f0e1f1f8d2..d48b4f3fa3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -2,6 +2,7 @@ title: SMA Wechselrichter (Modbus) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sma-inverter-modbus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx index 75f07e247d..e3ca69095f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx @@ -2,6 +2,7 @@ title: Smartfox Box custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx index 32a19fb63d..f59eba1ebf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -2,6 +2,7 @@ title: Smartfox Light (EM2 firmware) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx index 44771b7de0..fe8c9d5d9b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx index 2c85ff06c4..26d3273c5e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro Light 2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx index b7e045a785..f87d04923e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro Light custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx index 4d8202e3a2..c95240d5d4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx @@ -2,6 +2,7 @@ title: Smartfox Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox-em2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx index 8f456258d2..a7dfcab75f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx @@ -2,6 +2,7 @@ title: Smartfox Reg extended custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx index a3167a4330..44f02487e8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx @@ -2,6 +2,7 @@ title: Smartfox Reg custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/smartfox.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx index 2a79fa1333..70f1467bae 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SofarSolar Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx index 60f5740b67..c3bc503afd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -2,6 +2,7 @@ title: SofarSolar HYD 3…6K-EP custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx index 03da65580d..5451ae32fd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -2,6 +2,7 @@ title: SofarSolar HYD 5…20K-3PH custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx index 8d5481dc83..4491e75388 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx @@ -2,6 +2,7 @@ title: SofarSolar Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx index c272554669..bcf3b47104 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -2,6 +2,7 @@ title: SofarSolar SOFAR 5…24KTL-G3 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx index 57b0a23afc..2476e1ea61 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -2,6 +2,7 @@ title: SofarSolar SOFAR 80…136KTL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar-g3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx index 0be7ee3d47..0af4b0002c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -2,6 +2,7 @@ title: Solaranzeige Solaranzeige custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaranzeige.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx index 884bed6e7e..840bbb252f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SolarEdge Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx index 7b5551d7c3..bafd87d128 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx @@ -2,6 +2,7 @@ title: SolarEdge Wechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solaredge-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx index e38848d776..c7f51d12b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx @@ -2,6 +2,7 @@ title: Solarlog custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarlog.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx index ad36c2ddfa..2355dfde14 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -2,6 +2,7 @@ title: SolarMax MAX.STORAGE / MAX.STORAGE Ultimate custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-maxstorage.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx index 33789ab640..24351b66a6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx @@ -2,6 +2,7 @@ title: SolarMax SolarMax SMT custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarmax-smt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx index 4d809774f1..cea7dac468 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -2,6 +2,7 @@ title: SolarMax SP Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/senergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx index f2700c4ae6..855729cba9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -2,6 +2,7 @@ title: Solarwatt EnergyManager Pro custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx index a06b99ec28..0425bc1d99 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx @@ -2,6 +2,7 @@ title: Solarwatt EnergyManager custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx index aeb7a9b3ef..5ca755697e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx @@ -2,6 +2,7 @@ title: Solarwatt Manager flex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-flex.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx index 88b2e0460c..18fa6998bf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -2,6 +2,7 @@ title: Solarwatt MyReserve Matrix (LAN oder PowerGateway) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt-myreserve-matrix.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx index 01b5f5090b..c77461d4f2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx @@ -2,6 +2,7 @@ title: Solarwatt MyReserve custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solarwatt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx index e950c5d1a4..08df19eb81 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -2,6 +2,7 @@ title: Solax Hybrid-Wechselrichter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-hybrid-cloud.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx index 54b513e620..9cbef9c386 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -2,6 +2,7 @@ title: Solax Hybrid X1/X3 G3/G4 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx index 72c945039c..99032fe893 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx @@ -2,6 +2,7 @@ title: Solax PV-Wechselrichter (Cloud) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/solax-inverter-cloud.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx index 2129485e01..2c56eada03 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx @@ -2,6 +2,7 @@ title: Solinteng custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx index 8519710a02..6b731b3aed 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx @@ -2,6 +2,7 @@ title: Sonnen comfort custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx index 1252c7f947..1fa601c753 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx @@ -2,6 +2,7 @@ title: Sonnen eco 5 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx index 2acfdcd0f8..3346326c88 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx @@ -2,6 +2,7 @@ title: Sonnen eco 6 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx index 4dec02324e..2330b8bc30 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx @@ -2,6 +2,7 @@ title: Sonnen oem 6.5 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie-eco56.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx index 38fe4f92f8..7c35431e12 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -2,6 +2,7 @@ title: Sonnen sonnenBatterie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sonnenbatterie.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx index 1d8d0fe590..51b1ddd3df 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx @@ -2,6 +2,7 @@ title: St-ems custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx index 4edc1a1738..6a045107c0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx @@ -2,6 +2,7 @@ title: Steca coolcept fleX custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/kostal-piko-mp-plus.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx index 2da6d64f2d..d970631135 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -2,6 +2,7 @@ title: Sungrow SG Series Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx index b1e7873e72..3f110b9a05 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sungrow SH Series Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx index 4a33b51bcd..cd851c45d3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx @@ -2,6 +2,7 @@ title: SunSpec Batterie (Model 124) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter-control.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx index a42af80181..2083087a79 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx @@ -2,6 +2,7 @@ title: SunSpec Batterie (Model 802) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-battery-control.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx index c13963e595..da2285b414 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: SunSpec Hybridwechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-hybrid.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx index b284817729..2e2b605673 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx @@ -2,6 +2,7 @@ title: SunSpec Wechselrichter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-inverter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx index 51f1623c71..8c5c9dccbb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx @@ -2,6 +2,7 @@ title: SunSpec Zähler custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sunspec-meter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx index a4bed14d60..9917089232 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk 3p hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-3p.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx index 6f647ae705..3664f6e337 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk hp3 hybrid inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-hybrid-hp3.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx index 20ad572719..99d0ed6a2e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk Micro inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-mi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx index d54785c283..a9d8d877a9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk Storage (hybrid) inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-storage.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx index 0dd35c3c42..b0bf992253 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx @@ -2,6 +2,7 @@ title: Sunsynk String inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/deye-string.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx index 41eda964d5..f0a3b0eaaf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx @@ -2,6 +2,7 @@ title: Sunway custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx index 840cf89753..d0c243f364 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx @@ -2,6 +2,7 @@ title: Tasmota SML IR-Lesekopf für smarte Stromzähler bspw Hichi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-sml.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx index ee0395df34..13890a2443 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -2,6 +2,7 @@ title: Tasmota Tasmota (1 Phase + SML Meter) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx index 27c8c52362..4ad402cd54 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx @@ -2,6 +2,7 @@ title: Tasmota dreiphasig custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tasmota-3p.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx index 45c3a0ce96..09e80e593c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx @@ -2,6 +2,7 @@ title: Tesla Powerwall custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tesla-powerwall.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx index c10cb5dd3b..83e8be0dad 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx @@ -2,6 +2,7 @@ title: Tibber Pulse custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tibber-pulse.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx index 88b554a20e..2c164b292d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link H-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tplink.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx index 1c1ffcb6c8..6d8f726ff1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -2,6 +2,7 @@ title: TP-Link Tapo P-Series Smart Plug custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tapo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx index 105bd75093..2896091e97 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -2,6 +2,7 @@ title: TQ Energy Manager EM2xx/EM3xx custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx index 1850eeadf9..e3edc6d943 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx @@ -2,6 +2,7 @@ title: TQ Energy Manager EM420 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/tq-em420.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx index 944ab445d3..45212338a5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx @@ -2,6 +2,7 @@ title: VARTA element custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx index 45932f4895..549c0f2744 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx @@ -2,6 +2,7 @@ title: VARTA pulse neo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx index ee49684823..7c38abc188 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx @@ -2,6 +2,7 @@ title: VARTA pulse custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/varta.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx index 3d0e997b10..78424500e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx @@ -2,6 +2,7 @@ title: Victron EM24 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx index 9225c3e68b..b3c9966866 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx @@ -2,6 +2,7 @@ title: Victron EM24_E1 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-em24_e1.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx index d108093e66..bbe16c47d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx @@ -2,6 +2,7 @@ title: Victron EM530/EM540 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx index d1951ace5a..09af053a3e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx @@ -2,6 +2,7 @@ title: Victron Energy custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/victron-energy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx index ba2498efb0..57b2a06f0c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx @@ -2,6 +2,7 @@ title: Victron ET340 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/cg-emt3xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx index f8f43e521d..173cf8e33c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -2,6 +2,7 @@ title: Volkszähler HTTP API, Import & Export custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-importexport.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx index 7afc7ca952..a2246beafc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx @@ -2,6 +2,7 @@ title: Volkszähler HTTP API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-http.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx index 54702ec557..fbb51ebef0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx @@ -2,6 +2,7 @@ title: Volkszähler WebSocket API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/volkszaehler-ws.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx index 64896b95c2..2c21594442 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx @@ -2,6 +2,7 @@ title: vzlogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/vzlogger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx index 6cc6a6e730..b64b2fe2cc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx @@ -2,6 +2,7 @@ title: Wago 879-30xx custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wago-879-30xx.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx index e41a58b043..074436e355 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx @@ -2,6 +2,7 @@ title: Wattsonic custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/wattsonic.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx index e111432037..3a16756199 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM110-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx index aadc1e7e68..c72505c0fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM111-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron-sdm220_230.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx index 0c68f069c8..c68b746f4f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM120-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx index 2c5d4f76c5..01b59ca1bd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -2,6 +2,7 @@ title: Weidmüller EM122-RTU-2P custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/eastron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx index 99998aaa9c..def028904c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx @@ -2,6 +2,7 @@ title: Youless Energy Monitor custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/youless.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx index c4836e6404..f30dbfe213 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -2,6 +2,7 @@ title: ZCS Azzurro Hybrid Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx index ad7cc447bd..4dc9e9b17f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx @@ -2,6 +2,7 @@ title: ZCS Azzurro Inverter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/sofarsolar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx index ecdd794a4b..883696c126 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx @@ -2,6 +2,7 @@ title: Zendure Hyper 2000 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/zendure.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx index 0c2b4af582..d4cde9eccf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -2,6 +2,7 @@ title: Zuidwijk SlimmeLezer(+) in Luxembourg custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-luxembourg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx index 7a2be16da6..51c4d61107 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -2,6 +2,7 @@ title: Zuidwijk SlimmeLezer(+) V2 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer-V2.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx index 03a9339b4c..79e84aaa53 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -2,6 +2,7 @@ title: Zuidwijk SlimmeLezer(+) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/slimmelezer.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx index 1f2e308d91..3b81be7b8b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx @@ -2,6 +2,7 @@ title: Amber Electric custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/amber.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx index 981996ea6a..fc4209204b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx @@ -2,6 +2,7 @@ title: Awattar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/awattar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx index 84d3f32f93..e9f2933dd3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -2,6 +2,7 @@ title: Electricity Maps Commercial API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx index 80a90cf1eb..cc1a4f138d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx @@ -2,6 +2,7 @@ title: Electricity Maps Free API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/electricitymaps-free.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx index 4d2e167050..1f2874d2b4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx @@ -2,6 +2,7 @@ title: Energinet custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energinet.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx index a9b6bea1c2..74876e5325 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx @@ -2,6 +2,7 @@ title: Enever custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/enever.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx index be3808cbdc..0bd2d74598 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx @@ -2,6 +2,7 @@ title: ENTSO-E custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/entsoe.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx index 5bbbfd42de..3cd03044eb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx @@ -2,6 +2,7 @@ title: Forecast.Solar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/forecast-solar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx index 02b39afacb..223daac2fb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx @@ -2,6 +2,7 @@ title: Fraunhofer ISE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/energy-charts-api.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx index 021577e0aa..9ca2e03f1c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx @@ -2,6 +2,7 @@ title: Green Grid Compass custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/green-grid-compass.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx index 1c6a310b51..6fe6023b0d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -2,6 +2,7 @@ title: Groupe E Vario Plus custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/groupe-e.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx index 20c8164cb5..e6cb8c0022 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx @@ -2,6 +2,7 @@ title: Grünstromindex custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/grünstromindex.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx index a9f34dab47..8a501750df 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx @@ -1,6 +1,7 @@ --- title: Tariffs hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx index a400b736b1..590d9a9f4e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx @@ -2,6 +2,7 @@ title: National Grid ESO custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ngeso.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx index 4abe321c34..46d69a3d32 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx @@ -2,6 +2,7 @@ title: Nordpool spot prices custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/nordpool.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx index cd4383755a..1d58ebc264 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx @@ -2,6 +2,7 @@ title: Octopus Energy API custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-api.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx index 47c4c2dd7d..ca73db5c3c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx @@ -2,6 +2,7 @@ title: Octopus Energy Product Code custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/octopus-productcode.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx index 223332167d..b31e793515 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx @@ -2,6 +2,7 @@ title: Open-Meteo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/open-meteo.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx index 14082294c5..d3c2658e0c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx @@ -2,6 +2,7 @@ title: Ostrom custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/ostrom.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx index 3d87b71c36..1612e05a8d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx @@ -2,6 +2,7 @@ title: PUN Orario custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/pun.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx index 4f480fb733..c47492d5af 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -2,6 +2,7 @@ title: SmartEnergy smartCONTROL custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/smartenergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx index e3f0e23c50..022871ccc0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx @@ -2,6 +2,7 @@ title: Solcast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/solcast.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx index 166080e0dd..59dcf4db73 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx @@ -2,6 +2,7 @@ title: Spotty Energie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/spottyenergy.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx index 9255192e07..bb9c3fa841 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx @@ -2,6 +2,7 @@ title: Tibber custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/tibber.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx index 554ef7d252..11769a5321 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -2,6 +2,7 @@ title: Victron VRM Solar Forecast custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/tariff/victron.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx index f207e371f7..7a2b4da2e1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx @@ -2,6 +2,7 @@ title: Aiways custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/aiways.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx index c9f7dc1ba8..ecfb244ba0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx @@ -2,6 +2,7 @@ title: Audi custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/audi.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx index fe5d84cd04..3b821d2db3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx @@ -2,6 +2,7 @@ title: BMW custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/bmw.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx index 78ebf7df96..d130826672 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx @@ -2,6 +2,7 @@ title: Citroën custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/citroen.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx index d55a9b21dd..3dac52151c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx @@ -2,6 +2,7 @@ title: Dacia custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/dacia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx index 89586d0112..b113ed7072 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx @@ -2,6 +2,7 @@ title: DS custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ds.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx index e8b623f030..0569d03076 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx @@ -2,6 +2,7 @@ title: evNotify custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/evnotify.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx index 2546bc773a..cae1ff8b02 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx @@ -2,6 +2,7 @@ title: Fiat custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx index d04b5e69ef..0be69439b4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx @@ -2,6 +2,7 @@ title: Ford custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ford-connect.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx index eea6c19d76..d2cd74579f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -2,6 +2,7 @@ title: Generisches Fahrzeug (ohne API) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/offline.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx index 9c7b36a4ad..63c2afa4bc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx @@ -2,6 +2,7 @@ title: Hyundai Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/hyundai.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx index a319516ae8..3842ed404e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx @@ -1,6 +1,7 @@ --- title: Vehicles hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx index 0d73560a41..95d13a13d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx @@ -2,6 +2,7 @@ title: ioBroker.bmw custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ioBroker.bmw.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx index e9210f5746..0c7daac578 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx @@ -2,6 +2,7 @@ title: ISO15118 custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/iso15118.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx index ee039c5bca..c23b5c61e6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx @@ -2,6 +2,7 @@ title: Jeep custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/fiat.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx index 69a9f8079a..5218bc372c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx @@ -2,6 +2,7 @@ title: Kia Bluelink custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/kia.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx index a97d3f8b59..b652e223a5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx @@ -2,6 +2,7 @@ title: Mercedes-Benz custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mercedes.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx index 5398101bb5..d72171ea4f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx @@ -2,6 +2,7 @@ title: MG custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx index 3f9afcd6c9..4b971de09c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx @@ -2,6 +2,7 @@ title: mg2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mg2mqtt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx index 70934a3932..4c893894e1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx @@ -2,6 +2,7 @@ title: Mini custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mini.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx index e8b04f2d7e..dbb53448ed 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx @@ -2,6 +2,7 @@ title: mz2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/mz2mqtt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx index b189a038f7..f66a39979f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx @@ -2,6 +2,7 @@ title: Nissan Ariya custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan-ariya.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx index 52826892e6..4e2762f782 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -2,6 +2,7 @@ title: Nissan Leaf (pre 2019) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/carwings.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx index 9f5af7bc77..e103f01a65 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx @@ -2,6 +2,7 @@ title: Nissan Leaf custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/nissan.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx index 2f33836e2f..33d64e8abc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx @@ -2,6 +2,7 @@ title: NIU E-Scooter custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/niu-e-scooter.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx index 4429eb7e01..5daa42913c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx @@ -2,6 +2,7 @@ title: Opel custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/opel.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx index 917aac9be1..c9778bb244 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -2,6 +2,7 @@ title: Open Vehicle Monitoring System custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/ovms.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx index e5f44aa136..60854d7184 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx @@ -2,6 +2,7 @@ title: Peugeot custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/peugeot.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx index 6f1f302694..c83d15363e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx @@ -2,6 +2,7 @@ title: Polestar custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/polestar.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx index 4d08b5f53a..a7761b45c9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx @@ -2,6 +2,7 @@ title: PSA Car Controller custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/flobz.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx index 2e79b059e8..d16af0eca4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx @@ -2,6 +2,7 @@ title: Renault custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/renault.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx index 6d6970869f..1437306a03 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -2,6 +2,7 @@ title: Seat CupraConnect Gen3 (Ateca, Leon, Formentor, Tarraco) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/seat.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx index 9c3934618e..35b6e85550 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -2,6 +2,7 @@ title: Seat CupraConnect Gen4 (Born, Formentor, Tavascan) custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/cupra.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx index 8de4a50b01..8851140a36 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx @@ -2,6 +2,7 @@ title: Skoda Enyaq custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/enyaq.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx index 7c3c1a745c..dd190b3783 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx @@ -2,6 +2,7 @@ title: Smart custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart-hello.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx index bb9718ff17..1c108a1c84 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx @@ -2,6 +2,7 @@ title: Smart EQ custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/smart.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx index 089d811293..7f84697632 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx @@ -2,6 +2,7 @@ title: Tesla BLE custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla-ble.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx index b77dae8e51..1e38cea002 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx @@ -2,6 +2,7 @@ title: Tesla custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tesla.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx index 54a0b9e7e8..77ec7aadb7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx @@ -2,6 +2,7 @@ title: TeslaLogger custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslalogger.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx index 47f4efde90..79f1636e19 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx @@ -2,6 +2,7 @@ title: TeslaMate custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/teslamate.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx index 10a45a596c..94ad95fc4d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx @@ -2,6 +2,7 @@ title: Tessie custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tessie.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx index fc768b1aba..4f259f9f30 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx @@ -2,6 +2,7 @@ title: Toyota custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/toyota.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx index cb9ec66fc2..c22daacb79 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx @@ -2,6 +2,7 @@ title: Tronity custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/tronity.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx index 88d0258dde..84dfa62c85 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -2,6 +2,7 @@ title: Volkswagen We Connect ID custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/vw.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx index 0edf78b607..c65a3d4ca4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx @@ -2,6 +2,7 @@ title: Volvo custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo-connected.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx index 70576b93f8..4b84951fb7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx @@ -2,6 +2,7 @@ title: volvo2mqtt custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/volvo2mqtt.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx index a54049e9f9..167eff1e98 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx @@ -2,6 +2,7 @@ title: Zero Motorcycles custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/vehicle/zero.yaml hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig'; diff --git a/sidebars.js b/sidebars.js index bb40178b77..70c047fea8 100644 --- a/sidebars.js +++ b/sidebars.js @@ -11,5 +11,5 @@ module.exports = { // By default, Docusaurus generates a sidebar from the docs folder structure - tutorialSidebar: [{ type: "autogenerated", dirName: "." }], + sidebar: [{ type: "autogenerated", dirName: "." }], }; diff --git a/src/css/custom.css b/src/css/custom.css index 4c5a47050b..85f3b55ab6 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -202,3 +202,12 @@ table th { height: auto; } } + +.sidebar-item-hidden { + display: none; +} + +.sidebar-item-no-expand .menu__list, +.sidebar-item-no-expand .clean-btn.menu__caret { + display: none; +} diff --git a/src/generateDevicesNext.ts b/src/generateDevicesNext.ts index 219a06a379..c9af5278f3 100644 --- a/src/generateDevicesNext.ts +++ b/src/generateDevicesNext.ts @@ -206,6 +206,7 @@ const generateOverviewPage = ( return `--- title: ${title} hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand --- import DeviceCard from '@site/src/components/DeviceCard'; @@ -436,6 +437,7 @@ ${block.code} title: ${title} custom_edit_url: ${editUrl} hide_table_of_contents: true +sidebar_class_name: sidebar-item-hidden --- import DeviceConfig from '@site/src/components/DeviceConfig';